From owner-freebsd-current Sun Feb 20 0:13:20 2000 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 2147337BD80; Sun, 20 Feb 2000 00:13:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA88790; Sun, 20 Feb 2000 00:13:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 23:41:22 PST." Date: Sun, 20 Feb 2000 00:13:10 -0800 Message-ID: <88758.951034390@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Given that we can't import rsaref into FreeBSD and we can't depend on it > as a port, that about rules out any options for installing from > sysinstall. The remaining possibility is what we have now, namely manual > installation of the package post-installation, which is documented in the > handbook and referred to when they try and install a port which requires > it. Well, I guess I'll be less frantic about this when I see the ports infrastructure working properly with this - having openssh fail came as a rude shock. :) I'm also assuming that if I have openssl installed via the base system and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will cause it to build rsaref on my behalf just like it used to? I'd hate to have something become manual which was formerly automated. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 0:31:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0623937BE7D; Sun, 20 Feb 2000 00:31:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA12397; Sun, 20 Feb 2000 09:31:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Kris Kennaway , Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 20:06:52 PST." <42144.951019612@zippy.cdrom.com> Date: Sun, 20 Feb 2000 09:31:10 +0100 Message-ID: <12395.951035470@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <42144.951019612@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out >at this point. The situation with RSA makes this far more problematic >than I think anyone first thought, and I've seen a lot of breakage so >far for what appears to be comparatively little gain over what we had >before with the ports collection version. > >- Jordan I agree. It's not that hard to install a port. -- 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 Feb 20 0:52:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0ED5B37BE80; Sun, 20 Feb 2000 00:52:50 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA19351; Sun, 20 Feb 2000 00:52:49 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 00:52:49 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <88758.951034390@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Jordan K. Hubbard wrote: > Well, I guess I'll be less frantic about this when I see the ports > infrastructure working properly with this - having openssh fail > came as a rude shock. :) See Jim Bloom's patch of earlier this evening. > I'm also assuming that if I have openssl installed via the base system > and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will > cause it to build rsaref on my behalf just like it used to? I'd hate > to have something become manual which was formerly automated. No, because openssl is compiled differently if rsaref is present or not - it's not just a matter of dropping in librsaref.so (we can't always just build the version with RSAref stubs because it references symbols in librsaref and so binaries don't link). What will happen is that you'll get a message pointing you to the handbook which explains how to add the relevant openssl package. When you do this (once) you'll be able to build openssh. Is this clear now? Kris > - Jordan ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 1:20: 2 2000 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 1FA6A37BE51; Sun, 20 Feb 2000 01:20:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA94894; Sun, 20 Feb 2000 01:19:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sun, 20 Feb 2000 00:52:49 PST." Date: Sun, 20 Feb 2000 01:19:50 -0800 Message-ID: <94717.951038390@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 20 Feb 2000, Jordan K. Hubbard wrote: > > > Well, I guess I'll be less frantic about this when I see the ports > > infrastructure working properly with this - having openssh fail > > came as a rude shock. :) > > See Jim Bloom's patch of earlier this evening. Sorry, I'm the release engineer - I only "see" something as fixed when it's actually committed to the tree and in my current build. :) > > I'm also assuming that if I have openssl installed via the base system > > and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will > > cause it to build rsaref on my behalf just like it used to? I'd hate > > to have something become manual which was formerly automated. > > No, because openssl is compiled differently if rsaref is present or not - > it's not just a matter of dropping in librsaref.so (we can't always just > build the version with RSAref stubs because it references symbols in > librsaref and so binaries don't link). What will happen is that you'll get > a message pointing you to the handbook which explains how to add the > relevant openssl package. When you do this (once) you'll be able to build > openssh. Is this clear now? Yes, it's clear that this is more evil than I thought. :-) This is just wrong. If I go to build openssh then I expect it to DTRT with openssl whether or not openssl depends on RSA, I don't expect to go have to install a package manually and then continue with my build. That's not how openssh or other RSA-using ports *used* to work and I and many others were quite pleased with the previous behavior, we would prefer to keep it. I also have to wonder about your assertion that we can't just have librsaref.so as either a set of stubs or "the real deal" - can you tell me more exactly why couldn't you do this with a little help from our friendly weak symbol support? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 1:20:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 8DBDB37BEDF; Sun, 20 Feb 2000 01:20:20 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12MSXG-000N19-0A; Sun, 20 Feb 2000 09:20:15 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA11486; Sun, 20 Feb 2000 09:21:00 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 09:18:57 +0000 (GMT) From: Doug Rabson To: Jose Gabriel Marcelino Cc: Soren Schmidt , current@freebsd.org, freebsd-isdn@freebsd.org, hm@hcs.de Subject: Re: Big ATA problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote: > atapci0: port 0xe000-0xe00f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ... > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > While I was able to use the Teles again by changing it's default IO port I > think there will be some people who will find it cumbersome to have to > change the IO on a card that was working fine before. > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > driver doesn't really need that many IO ports so I'm sending this email to > both parties. This is a bug in the isic driver. I'm sure it doesn't use every port in that range so it needs to split the range in to two or more pieces and only allocate ports which it actually needs. -- 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 Feb 20 1:29:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A7CB437BE7D; Sun, 20 Feb 2000 01:29:51 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA22653; Sun, 20 Feb 2000 01:29:51 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 01:29:50 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <94717.951038390@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Jordan K. Hubbard wrote: > > See Jim Bloom's patch of earlier this evening. > > Sorry, I'm the release engineer - I only "see" something as fixed when > it's actually committed to the tree and in my current build. :) Well, I'm not allowed to commit to that file :) I also haven't sent in the patch yet because I'm waiting on the outcome of this discussion about whether we're even going to keep it. > Yes, it's clear that this is more evil than I thought. :-) > > This is just wrong. If I go to build openssh then I expect it to DTRT > with openssl whether or not openssl depends on RSA, I don't expect to > go have to install a package manually and then continue with my build. > That's not how openssh or other RSA-using ports *used* to work and I > and many others were quite pleased with the previous behavior, we > would prefer to keep it. I also have to wonder about your assertion > that we can't just have librsaref.so as either a set of stubs or "the > real deal" - can you tell me more exactly why couldn't you do this > with a little help from our friendly weak symbol support? The problem is that as things are now, when you compile libcrypto with RSAref support, it has two symbol dependencies on librsaglue, which in turn has a whole lot of dependencies on librsaref. I don't know how weak symbols work - someone with more experience in such matters would have to help me understand it :-) Kris > - Jordan ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 1:42:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id B7F8437BE51; Sun, 20 Feb 2000 01:42:35 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id KAA13880; Sun, 20 Feb 2000 10:42:21 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id KAA11716; Sun, 20 Feb 2000 10:35:42 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 21BF252AA3; Sun, 20 Feb 2000 10:10:54 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 599161F17; Sun, 20 Feb 2000 10:10:45 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Jose Gabriel Marcelino at "Feb 19, 2000 11:48:52 pm" To: gabriel@maquina.com (Jose Gabriel Marcelino) Date: Sun, 20 Feb 2000 10:10:45 +0100 (CET) Cc: sos@freebsd.dk, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220091045.599161F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jose Gabriel Marcelino wrote: > This obviously conflicts with the secondary IDE controller which lies at > 0x170, however this has not been a problem till this day and no driver > complained about this. Now, with the newer kernel I get this: > > atapci0: port 0xe000-0xe00f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ... > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > While I was able to use the Teles again by changing it's default IO port I > think there will be some people who will find it cumbersome to have to > change the IO on a card that was working fine before. > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > driver doesn't really need that many IO ports so I'm sending this email to > both parties. This type of error with the 2nd IDE controller was reported also by other people, mostly the reports were "working sometimes". First of all, Teles refuses to give out any docs about their hardware, so it might be that not all addresses are used but this is 100% speculation. What you are recognizing is the real nice thing about newbus: you can't allocate a resource twice. I admit, this might be a bit cumbersome in the single case but it saves us from the "working sometimes" and "working sometimes not" and "sometimes, very seldom and unreproducible" error reports in the general case. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 3: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 36E4437BBB1; Sun, 20 Feb 2000 03:02:23 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id MAA14616; Sun, 20 Feb 2000 12:02:21 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id LAA12305; Sun, 20 Feb 2000 11:59:02 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 0D21B52AA3; Sun, 20 Feb 2000 11:37:54 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id EB14A1F17; Sun, 20 Feb 2000 11:37:45 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Doug Rabson at "Feb 20, 2000 9:18:57 am" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 20 Feb 2000 11:37:45 +0100 (CET) Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220103745.EB14A1F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > atapci0: port 0xe000-0xe00f at device 7.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ... > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > While I was able to use the Teles again by changing it's default IO port I > > think there will be some people who will find it cumbersome to have to > > change the IO on a card that was working fine before. > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > driver doesn't really need that many IO ports so I'm sending this email to > > both parties. > > This is a bug in the isic driver. I'm sure it doesn't use every port in > that range so it needs to split the range in to two or more pieces and > only allocate ports which it actually needs. How do you come to that conclusion ? A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. The card in question allocates 3 portranges for this uses with each 0x40 bytes in length. In case there is is already an IDE controller allocated at 0x170 and a Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. So where is the bug ? This all looks perfectly reasonable to me with the exception that we could start argueing about whether it would be reasonable to split the allocation ranges for the ISAC and to save (if at all possible, there are some more registers at the end of the HSCX on the card) some bytes in the HSCX case. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 3:38:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 4EAA437BA81; Sun, 20 Feb 2000 03:38:39 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12MUhA-000MIb-0K; Sun, 20 Feb 2000 11:38:36 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA23236; Sun, 20 Feb 2000 11:40:55 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 11:38:51 +0000 (GMT) From: Doug Rabson To: Hellmuth Michaelis Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > Doug Rabson wrote: > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > pci0 > > > ata0: at 0x1f0 irq 14 on atapci0 > > > ata1: at 0x170 irq 15 on atapci0 > > > ... > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > think there will be some people who will find it cumbersome to have to > > > change the IO on a card that was working fine before. > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > driver doesn't really need that many IO ports so I'm sending this email to > > > both parties. > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > that range so it needs to split the range in to two or more pieces and > > only allocate ports which it actually needs. > > How do you come to that conclusion ? > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > The card in question allocates 3 portranges for this uses with each 0x40 > bytes in length. > > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > So where is the bug ? > > This all looks perfectly reasonable to me with the exception that we could > start argueing about whether it would be reasonable to split the allocation > ranges for the ISAC and to save (if at all possible, there are some more > registers at the end of the HSCX on the card) some bytes in the HSCX case. So you are saying that what we really have here is a simple i/o conflict and possibly the ISDN card can be reconfigured to use a non-conflicting address? If so, then everything is working correctly and the resource manager has pointed a possible hardware problem :-). -- 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 Feb 20 3:40:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 02A2137BD35 for ; Sun, 20 Feb 2000 03:40:06 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 21471 invoked from network); 20 Feb 2000 11:39:51 -0000 Received: from lcm208.cvzoom.net (208.230.69.208) by ns.cvzoom.net with SMTP; 20 Feb 2000 11:39:51 -0000 Date: Sun, 20 Feb 2000 06:39:25 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Question about atapi cdrom behavior (BTC 24X) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Say I do something like find /cdrom is the HD light supposed to be blinking as if the hard drives are being accessed? I did the above command (note that it doesn't involve finding files on the hard drives at all), and basically the HD light and the cdrom activity light were flashing together. I have a BTC 24X ATAPI cdrom drive. I'd like to check to see if anyone on this list has one of these, and if so, have you had any problems? For example, if I do dd if=/dev/racd0c of=cd.img the file cd.img is zero-length, dd hangs (ignores ^C totally), and I get messages like acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done acd0: READ_BIG command timeout - resetting ata1: resetting devices .. done Even if I do killall -9 dd, dd refuses to die. I haven't yet tried this with the old wd driver (I probably should), but I will if I'm requested. Anyone else have a BTC 24X or similar ATAPI drive? Thanks. Here's my dmesg, BTW: ad0: 3093MB [6704/15/63] at ata0-master using UDMA33 ad1: 1040MB [2114/16/63] at ata0-slave using WDMA2 acd0: CDROM at ata1-master using WDMA2 - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 3:55:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 5BFD037BB7C for ; Sun, 20 Feb 2000 03:55:00 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12MUwo-000IUH-0X; Sun, 20 Feb 2000 11:54:46 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA38612; Sun, 20 Feb 2000 11:57:05 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 11:55:01 +0000 (GMT) From: Doug Rabson To: Jose Gabriel Marcelino Cc: current@freebsd.org Subject: Re: Many PCI buses and probes on recent kernels 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, 19 Feb 2000, Jose Gabriel Marcelino wrote: > > > Hi, > > Apart from the more recently broken ATA stuff I started getting the > following (cosmetic only really, but it leaves me wondering..) in kernels > compiled around the 12th this month. This machine really just has one pci > bus (this is a simple K6 VIA MVP3 motherboard). Also the unknow (to > FreeBSD) PCI card is probed too many times (I just have one). > > This unkown card btw is Realmagic's Hollywood+ DVD card (only supported in > Windows unfortunately since it's a great great card). Everything works > great apart from that using this kernel so I think this is cosmetic > only... Please send me a verbose dmesg output. It looks like we need a workaround for this chipset in the code which tries to detect host-pci bridges. Isn't PC hardware wonderful :-). -- 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 Feb 20 4: 7: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id CDCAC37BB7C for ; Sun, 20 Feb 2000 04:07:01 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id NAA27043; Sun, 20 Feb 2000 13:06:28 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id NAA19791; Sun, 20 Feb 2000 13:06:28 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id NAA13469; Sun, 20 Feb 2000 13:06:27 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: Omachonu Ogali Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world References: From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Date: 20 Feb 2000 13:06:27 +0100 In-Reply-To: Omachonu Ogali's message of "Sat, 19 Feb 2000 22:02:01 -0500 (EST)" Message-ID: Lines: 17 User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Omachonu Ogali writes: > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development tools.' > Try `install-info --help' for a complete list of options. I did `make -k install-world', then `make installworld'. The first make will install the new install-info binary which has the new options, the second make will use that binary to install the info files. I hope this isn't wrong... kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 4:18:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-107.max3-du-ws.dialnetwork.pavilion.co.uk [212.74.9.107]) by hub.freebsd.org (Postfix) with ESMTP id DF2A737BB9A; Sun, 20 Feb 2000 04:18:43 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA41882; Sun, 20 Feb 2000 12:10:15 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA78505; Sun, 20 Feb 2000 12:10:06 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002201210.MAA78505@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Rabson Cc: Hellmuth Michaelis , current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Big ATA problems In-Reply-To: Message from Doug Rabson of "Sun, 20 Feb 2000 11:38:51 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Feb 2000 12:10:05 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > > Doug Rabson wrote: > > > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > > pci0 > > > > ata0: at 0x1f0 irq 14 on atapci0 > > > > ata1: at 0x170 irq 15 on atapci0 > > > > ... > > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > > think there will be some people who will find it cumbersome to have to > > > > change the IO on a card that was working fine before. > > > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > > driver doesn't really need that many IO ports so I'm sending this email to > > > > both parties. > > > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > > that range so it needs to split the range in to two or more pieces and > > > only allocate ports which it actually needs. > > > > How do you come to that conclusion ? > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > The card in question allocates 3 portranges for this uses with each 0x40 > > bytes in length. > > > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > > > So where is the bug ? > > > > This all looks perfectly reasonable to me with the exception that we could > > start argueing about whether it would be reasonable to split the allocation > > ranges for the ISAC and to save (if at all possible, there are some more > > registers at the end of the HSCX on the card) some bytes in the HSCX case. > > So you are saying that what we really have here is a simple i/o conflict > and possibly the ISDN card can be reconfigured to use a non-conflicting > address? If so, then everything is working correctly and the resource > manager has pointed a possible hardware problem :-). So it would seem, *but*, before moving from wd to ata I had both working 100% reliably. I had to move the Teles card to get it to work (allocate resources successfully) once I changed to ata. I would be pretty sure that the Teles S0/16.3 doesn't actually go near the I/O range @ 0x170. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 4:38:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A75D937BD03 for ; Sun, 20 Feb 2000 04:38:11 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA91290; Sun, 20 Feb 2000 13:37:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002201237.NAA91290@freebsd.dk> Subject: Re: Question about atapi cdrom behavior (BTC 24X) In-Reply-To: from Donn Miller at "Feb 20, 2000 06:39:25 am" To: dmmiller@cvzoom.net (Donn Miller) Date: Sun, 20 Feb 2000 13:37:57 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Donn Miller wrote: > Say I do something like > > find /cdrom > > is the HD light supposed to be blinking as if the hard drives are being > accessed? I did the above command (note that it doesn't involve finding > files on the hard drives at all), and basically the HD light and the cdrom > activity light were flashing together. Depends, some ATAPI devices use the activity LED some dont... > I have a BTC 24X ATAPI cdrom drive. I'd like to check to see if anyone > on this list has one of these, and if so, have you had any problems? For > example, if I do > > dd if=/dev/racd0c of=cd.img > > the file cd.img is zero-length, dd hangs (ignores ^C totally), and I get > messages like That because you miss a bs=2k, a CDROM has a 2k sector size, and depending on the drives firmware you get different results when you try a blocksize that is no modulo 2k, your's apparently looses its whits. -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 Feb 20 5:12:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id 510DC37BB5E; Sun, 20 Feb 2000 05:12:07 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id NAA54664; Sun, 20 Feb 2000 13:12:01 GMT (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Sun, 20 Feb 2000 13:12:01 +0000 (WET) From: Jose Gabriel Marcelino To: current@freebsd.org, freebsd-isdn@freebsd.org Cc: Hellmuth Michaelis , Doug Rabson Subject: Greedy Teles card was Re: Big ATA problems In-Reply-To: <200002201210.MAA78505@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So you are saying that what we really have here is a simple i/o conflict > > and possibly the ISDN card can be reconfigured to use a non-conflicting > > address? If so, then everything is working correctly and the resource > > manager has pointed a possible hardware problem :-). > > So it would seem, *but*, before moving from wd to ata I had both > working 100% reliably. I had to move the Teles card to get it to > work (allocate resources successfully) once I changed to ata. > > I would be pretty sure that the Teles S0/16.3 doesn't actually go > near the I/O range @ 0x170. Yes, it also worked like that for quite some time in my FreeBSD box for more than 2 years on the my company's old Linux internet gateway/small server, with IDE disks and a network mounted CDrom running on the secondary channel.. No problems whatsoever.. I understand this resource allocation assures perfect compliance with the hardware specs and if so it should really be done this way, however I think this will brake many Teles cards out there once people start changing to FreeBSD 4.x so it should be at least documented, preferably with the switch settings since the card is old and people tend to lose the docs (I didn't have mine's so it took some trial and error to match IO and switches.. some people will surely have problem with that) Regards Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 5:12:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 5DB9D37BCAF; Sun, 20 Feb 2000 05:12:28 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id OAA15746; Sun, 20 Feb 2000 14:12:22 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id OAA13195; Sun, 20 Feb 2000 14:07:05 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 93CF152AA3; Sun, 20 Feb 2000 14:04:36 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id E22391F17; Sun, 20 Feb 2000 14:04:35 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Doug Rabson at "Feb 20, 2000 11:38:51 am" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 20 Feb 2000 14:04:35 +0100 (CET) Cc: hm@kts.org, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220130435.E22391F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > > pci0 > > > > ata0: at 0x1f0 irq 14 on atapci0 > > > > ata1: at 0x170 irq 15 on atapci0 > > > > ... > > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > > think there will be some people who will find it cumbersome to have to > > > > change the IO on a card that was working fine before. > > > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > > driver doesn't really need that many IO ports so I'm sending this email to > > > > both parties. > > > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > > that range so it needs to split the range in to two or more pieces and > > > only allocate ports which it actually needs. > > > > How do you come to that conclusion ? > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > The card in question allocates 3 portranges for this uses with each 0x40 > > bytes in length. > > > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > > > So where is the bug ? > > > > This all looks perfectly reasonable to me with the exception that we could > > start argueing about whether it would be reasonable to split the allocation > > ranges for the ISAC and to save (if at all possible, there are some more > > registers at the end of the HSCX on the card) some bytes in the HSCX case. > > So you are saying that what we really have here is a simple i/o conflict > and possibly the ISDN card can be reconfigured to use a non-conflicting > address? Yes. > If so, then everything is working correctly and the resource > manager has pointed a possible hardware problem :-). Exactly! :-) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 5:17:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from prince.net.ebina.hitachi.co.jp (sagami134136.allnet.ne.jp [210.251.134.136]) by hub.freebsd.org (Postfix) with ESMTP id 3B17137BCD5 for ; Sun, 20 Feb 2000 05:17:18 -0800 (PST) (envelope-from sumikawa@ebina.hitachi.co.jp) Received: from ebina.hitachi.co.jp (localhost [127.0.0.1]) by prince.net.ebina.hitachi.co.jp (8.9.3/3.7W) with SMTP id WAA10583; Sun, 20 Feb 2000 22:15:56 +0900 (JST) From: sumikawa@ebina.hitachi.co.jp Message-Id: <200002201315.WAA10583@prince.net.ebina.hitachi.co.jp> Date: Sun, 20 Feb 2000 22:15:56 +0900 (JST) To: dgilbert@velocet.ca Cc: cpiazza@jaxon.net, freebsd-current@FreeBSD.ORG Cc: sumikawa@ebina.hitachi.co.jp Subject: Re: ipv6 default in current ports? In-Reply-To: <14509.52933.883241.459866@trooper.velocet.net> References: <14509.50981.963519.987797@trooper.velocet.net> <20000218145710.A831@norn.ca.eu.org> <14509.52933.883241.459866@trooper.velocet.net> X-Mailer: xcite1.31> Mew version 1.95b10 on Emacs 20.4 / Mule 4.0 (HANANOEN) 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 Chris> It doesn't need kernel support to build with ipv6 support. Chris> Trying to use the ipv6 support without it in the kernel is the Chris> only problem. dgilbert> Well... ruby refuses to build with IPv6 if it's not enabled and mtr dgilbert> dies with a "cannot open socket". dgilbert> In escence, both ports (and possibly others) don't work in 4.0 without dgilbert> INET6 in your kernel. Thanks for the reporting. I attach the patch for ruby. I've already send it to the maintainer. As for mtr, I'll check it. --- Munechika SUMIKAWA @ KAME Project / FreeBSD.org Index: patches/patch-aa =================================================================== RCS file: /home/ncvs/ports/lang/ruby/patches/patch-aa,v retrieving revision 1.1 diff -u -r1.1 patch-aa --- patches/patch-aa 2000/01/12 19:16:44 1.1 +++ patches/patch-aa 2000/02/20 13:06:46 @@ -1,5 +1,5 @@ --- ext/socket/extconf.rb.orig Fri Oct 29 13:45:41 1999 -+++ ext/socket/extconf.rb Wed Jan 12 17:15:03 2000 ++++ ext/socket/extconf.rb Sun Feb 20 22:04:32 2000 @@ -57,8 +57,6 @@ #endif EOF @@ -9,3 +9,14 @@ $CFLAGS="-DINET6 "+$CFLAGS elsif File.directory? "/usr/inet6" $ipv6type = "linux" +@@ -225,7 +223,9 @@ + } + } + +- if (inet6 != 2 || inet4 != 2) ++ if (!(inet4 == 0 || inet4 == 2)) ++ goto bad; ++ if (!(inet6 == 0 || inet6 == 2)) + goto bad; + + if (aitop) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 5:22:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id DB00737BD69; Sun, 20 Feb 2000 05:22:35 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id OAA15855; Sun, 20 Feb 2000 14:22:22 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id OAA13294; Sun, 20 Feb 2000 14:19:56 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id AAB6352AA3; Sun, 20 Feb 2000 14:15:00 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 479301F17; Sun, 20 Feb 2000 14:14:55 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: <200002201210.MAA78505@hak.lan.Awfulhak.org> from Brian Somers at "Feb 20, 2000 12:10: 5 pm" To: brian@Awfulhak.org (Brian Somers) Date: Sun, 20 Feb 2000 14:14:55 +0100 (CET) Cc: dfr@nlsystems.com, hm@kts.org, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220131455.479301F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > So you are saying that what we really have here is a simple i/o conflict > > and possibly the ISDN card can be reconfigured to use a non-conflicting > > address? If so, then everything is working correctly and the resource > > manager has pointed a possible hardware problem :-). > > So it would seem, *but*, before moving from wd to ata I had both > working 100% reliably. I had to move the Teles card to get it to > work (allocate resources successfully) once I changed to ata. > > I would be pretty sure that the Teles S0/16.3 doesn't actually go > near the I/O range @ 0x170. It depends. Assuming that the 16.3 allocates 0x40 bytes from 0x160 on, it has 32 bytes r/w fifo from 0x160. This fifo may be accessed directly at each location or indirectly in autoincrement mode. The isic driver (IIRC) accesses it in autoincrement mode, this results in using only the first byte for read/write of the fifo. This may be the reason why it succeeds until now. Anyhow - the fifo in non-autoincrement mode is _still_ there (it might also be, that Teles does not decode the last 30 bytes of this range, but i have no idea since the chance to get docs is nearly equal to zero) how this behaves cannot be predicted for shure, so IMHO there is a resource clash and the isic driver behaves correctly unless i overlooked something. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 5:52:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1276037BCD5; Sun, 20 Feb 2000 05:52:34 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA17728; Mon, 21 Feb 2000 00:54:39 +1100 Date: Mon, 21 Feb 2000 00:50:45 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Ruslan Ermilov Cc: Garrett Wollman , Peter Wemm , committers@FreeBSD.org, current@FreeBSD.org, dcs@FreeBSD.org Subject: Re: pstat(8) depends on loader(8)??? In-Reply-To: <20000218142846.A14682@relay.ucb.crimea.ua> Message-ID: 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, 18 Feb 2000, Ruslan Ermilov wrote: > Hi! > > Why then it works on 3.4-STABLE (booting without loader(8) and > having kvm(3) programs like pstat(8) and top(1) working). > What makes a difference here? RCS file: /home/ncvs/src/lib/libkvm/kvm_file.c,v Working file: kvm_file.c head: 1.10 ... ---------------------------- revision 1.9 date: 1999/12/27 07:14:57; author: peter; state: Exp; lines: +5 -0 Use kldsym(2) to lookup symbol values. This avoids the kvm_mkdb juggling and is module aware. Yes, this means that kvm_nlist(3) will find symbols in loaded modules. The emulation of the nlist struct is pretty crude but seems to work well enough for all the users in the tree that I found. ---------------------------- > On Mon, Feb 07, 2000 at 10:14:29PM +0800, Peter Wemm wrote: > > More to the point, a non-stripped kernel has *two* symbol tables. One that > > has the global symbols and is used for dynamic linking, and the other that > > has the debugging info in it including static symbols. loader(8) goes to a > > great deal of trouble to get the second table - it's very hard to get it > > when reading from a zlib decompression stream that can't be seek'ed. The ELF > > format defines a convenient 'load segment' table which defines (usually) > > two chunks of the file to be loaded into memory and at what addresses. The > > verbose symbol table is not part of this, but the global table is and we get > > it for free. > > > > Anyway, the correct fix is to make numvnodes global or to change it to a > > sysctl. Nothing that is referred to by the common libkvm applications > > should be static - this warning has been given before. running a strip on / > > kernel has the same effect as using boot2 - only global symbols are > > accessible. The former would be a very incorrect fix. C linkage shouldn't be weakened to work around deficiencies in binary utilities. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 6:44:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 1584337BCDA for ; Sun, 20 Feb 2000 06:44:51 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:AvqDLVx39kIvd5PiubtOXJWVHbU9D8Iw@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA22076; Sun, 20 Feb 2000 23:44:25 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA17612; Sun, 20 Feb 2000 23:50:21 +0900 (JST) Message-Id: <200002201450.XAA17612@zodiac.mech.utsunomiya-u.ac.jp> To: Blaz Zupan Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: CGA instead of VGA In-reply-to: Your message of "Sat, 19 Feb 2000 17:57:43 +0100." References: Date: Sun, 20 Feb 2000 23:50:20 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On -current my VGA card is being used as a CGA card. It is correctly >recognized as a VGA: > >vga-pci0: mem 0xf8000000-0xfbffffff irq 11 at d >evice 15.0 on pci0 The above message simply means that a PCI card classified as VGA is found. This does not necessarily means that the card can be used as VGA. >vga0: at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0 > >but then used as a CGA: > >sc0: CGA <16 virtual consoles, flags=0x200> The BIOS setup menu usually has an entry to specify the type of the installed video card. If this item is set to CGA, the BIOS and the vga driver will initialize the card, even if it is a VGA, as the CGA card. Are you sure that this doesn't happen to be the case with your system? >The problem is, that I can't set fonts: > ># vidcontrol vidcontrol: can't load font: Device not configured If the card is recognized as CGA, you cannot load font or switch video modes. >I vaguely remember seing a commit from Kazu that supposedly fixed this, >although I still experience it with a -current machine as of a couple of >days ago. That commit fixed the problem where the vga driver wrongly thought the card is CGA when the BIOS DOES initialize the card as VGA. If the BIOS initialize the card as CGA, the vga driver is still led to believe the card is CGA. (And I believe that is the reasonable behavior.) Kazu >The motherboard is an Intel AN430TX, the graphics card is a S3 Trio 64V+ >based card. Below is the full dmesg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 7:22:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 74F7737BD54 for ; Sun, 20 Feb 2000 07:22:11 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12MWNi-0002Jq-00; Sun, 20 Feb 2000 13:26:38 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12MWNh-0008A0-00; Sun, 20 Feb 2000 13:26:37 +0000 Date: Sun, 20 Feb 2000 13:26:37 +0000 From: Ben Smithurst To: =?iso-8859-1?Q?Kai_Gro=DFjohann?= Cc: Omachonu Ogali , freebsd-current@FreeBSD.ORG Subject: Re: make world Message-ID: <20000220132637.I28660@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kai Großjohann wrote: > Omachonu Ogali writes: > >> ===> lib/libcom_err/doc >> install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir >> install-info: unrecognized option `--defsection=Programming & development tools.' >> Try `install-info --help' for a complete list of options. > > I did `make -k install-world', then `make installworld'. The first > make will install the new install-info binary which has the new > options, the second make will use that binary to install the info > files. Isn't that overkill? I just did "cd /usr/src/gnu/usr.bin/texinfo/install-info; make install" before a normal "make installworld". > I hope this isn't wrong... ditto :-) -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 8: 1:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 7043F37BBB1 for ; Sun, 20 Feb 2000 08:01:21 -0800 (PST) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id E5DE66BA7; Sun, 20 Feb 2000 17:00:08 +0100 (CET) Date: Sun, 20 Feb 2000 17:00:08 +0100 (CET) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Kazutaka YOKOTA Cc: freebsd-current@freebsd.org Subject: Re: CGA instead of VGA In-Reply-To: <200002201450.XAA17612@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The BIOS setup menu usually has an entry to specify the type of the > installed video card. If this item is set to CGA, the BIOS and the > vga driver will initialize the card, even if it is a VGA, as the CGA > card. Are you sure that this doesn't happen to be the case with > your system? My BIOS does not have this entry. I can only select if this is a PnP operating system. I have set it to "no" because if I select "yes" my PCI NE-2000 network card is not recognized because the BIOS does not assign resources to it (I was told on this list that FreeBSD is not yet a full PnP system in this sense). If I set PnP to "yes" the card is correctly recognized as a VGA card. > That commit fixed the problem where the vga driver wrongly thought the > card is CGA when the BIOS DOES initialize the card as VGA. If the > BIOS initialize the card as CGA, the vga driver is still led to believe > the card is CGA. (And I believe that is the reasonable behavior.) So how can I force the card to VGA in my situation? :) I have flashed the latest BIOS into the motherboard and I still can't find any setting mentioning CGA or VGA. More info about the motherboard can be found here: http://support.intel.com/support/motherboards/desktop/an430tx/index.htm Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 8:44:39 2000 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 3031E37BBB1; Sun, 20 Feb 2000 08:44:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p20-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.85]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA06646; Mon, 21 Feb 2000 01:44:24 +0900 (JST) Message-ID: <38B0114D.ED1BF29C@newsguy.com> Date: Mon, 21 Feb 2000 01:07:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: Garance A Drosihn , "Jordan K. Hubbard" , Doug Barton , Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Except it's not just this release, it's "for the life of the 4.x branch" > given the rules of what should get put into -stable. I really don't want > to have to wait another year or more for 5.0-RELEASE before we can start > making use of crypto in the recommended version of FreeBSD. This argument is not valid, sorry. OpenSSL, as it stands right now in the tree, is just another library and a set of include files (and configuration?). _Nothing_ in the system depends on OpenSSL, no part of the system has been modified to allow for it. It's basically a "plug-in" library, which, in fact, can be done through the ports. Given all that, there is absolutely _no_ reason why you shouldn't be able to MFC this later on. OTOH, if bigger changes, interface changes and the like will be following this, you will STILL be subject to the merging rules. Just because OpenSSL is there in 4.x won't give you any breaks on current -> stable rules. On the gripping hand, we have more than once brought to -stable changes that were deemed to important to wait until the next major version which would, otherwise, never be merged. So, there isn't really any rule saying that this _won't_ get into the 4.x branch if this single library doesn't get in right now. So... what _other_ reasons do you have to get OpenSSL in at any costs? There are disadvantages. There is the patent problem, there is the requirement of DES if you want OpenSSL (and I _don't_ want DES), which effectively _reduces_ our flexibility versus what we had before OpenSSL was added to the tree, and the handbook chapter you keep referencing is helpful, I imagine, in _some_ situations, but it just doesn't cut it yet. It didn't help me in the least, for instance. I see no gain, and lots of pain. For some, granted, things will work flawlessly and painlessly. For others, it can be a real headache. And all this discussion about what sysinstall should do or not goes to show that this just isn't ready yet. We are 20 days into code freeze, months into feature freeze, and it's just not time to get in things that are not ready. If OpenSSL in the tree is not working out right, and for some it isn't, it's better to just back it off, get back to the drawing board, and wait until the code freeze is over. There is still time even for this to get into 4.x-STABLE, since we won't change the 4.x branch to -stable for some time. And, from all I have seen up to now, it would seem 4.0-RELEASE will be better served with OpenSSL in the ports. IMHO, this is the right direction, but the wrong time. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 8:48:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 247D937BC20; Sun, 20 Feb 2000 08:48:08 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id RAA03748; Sun, 20 Feb 2000 17:48:04 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.9.3/8.8.8) id RAA01128; Sun, 20 Feb 2000 17:44:04 +0100 (MET) From: Martin Husemann Message-Id: <200002201644.RAA01128@rumolt.teuto.de> Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> from Hellmuth Michaelis at "Feb 20, 2000 11:37:45 am" To: hm@kts.org Date: Sun, 20 Feb 2000 17:44:04 +0100 (MET) Cc: dfr@nlsystems.com (Doug Rabson), current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. This is a PnP card, right? So what does the PnP info say about needed memory ranges? > So where is the bug ? Depends. If the drivers allocation is coherent with the vendors description in the PnP configuration data, it's a newbus error (it shouldn't try to allocate the card there in the first place). If the PnP info differs from the drivers view of the card, it's either the vendors fault for providing wrong infos (this wouldn't be the only card suffering) [fix: provide a quirk entry], or the drivers fault: it should obey what the vendor tells PnP about the card. Which case applies? Simple: if it's possible to change the driver to obey the cards infos, that should be done. If the driver couldn't be made to work support for that card should be removed :-) If I'm wrong and this isn't a PnP card: it's pilot error. The card can't work at the specified address, so everything works as expected. Paraphrased in a sentence often heard as a reply from technical support persons for a big commercial OS vendor: "Status: This behaviour is by design." Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 9:28:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 76C5437BED4; Sun, 20 Feb 2000 09:28:49 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1514 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sun, 20 Feb 2000 18:28:45 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 53B513890; Sun, 20 Feb 2000 18:28:36 +0100 (MET) Subject: Re: Big ATA problems In-Reply-To: <200002201644.RAA01128@rumolt.teuto.de> from Martin Husemann at "Feb 20, 0 05:44:04 pm" To: martin@rumolt.teuto.de (Martin Husemann) Date: Sun, 20 Feb 2000 18:28:35 +0100 (MET) Cc: hm@kts.org, dfr@nlsystems.com, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 551 Message-Id: <20000220172836.53B513890@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Martin Husemann: > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > This is a PnP card, right? No. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 9:48:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 510AD37BEF4; Sun, 20 Feb 2000 09:48:33 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id MAA33578; Sun, 20 Feb 2000 12:48:26 -0500 (EST) Date: Sun, 20 Feb 2000 12:48:25 -0500 (EST) From: jack To: Kris Kennaway Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Kris Kennaway wrote: > > I'm also assuming that if I have openssl installed via the base system > > and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will > > cause it to build rsaref on my behalf just like it used to? I'd hate > > to have something become manual which was formerly automated. > > No, because openssl is compiled differently if rsaref is present or not - > it's not just a matter of dropping in librsaref.so (we can't always just > build the version with RSAref stubs because it references symbols in > librsaref and so binaries don't link). What will happen is that you'll get > a message pointing you to the handbook which explains how to add the > relevant openssl package. When is this message you keep talking about supposed to happen? All I got was: [snip] ===> Registering installation for rsaref-2.0 ===> Returning to build of OpenSSH-1.2.2 [snip] In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:21, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../rsa.h:22: openssl/rsa.h: No such file or directory /usr/ports/security/openssh/work/ssh/lib/../authfd.c:27: openssl/rsa.h: No such file or directory >When you do this (once) you'll be able to build openssh. Is this clear now? After a make world after rsaref was installed openssh did build (and work :). -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 10: 6:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 6487C37BF4F for ; Sun, 20 Feb 2000 10:06:45 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 180CC1FC; Sun, 20 Feb 2000 21:06:43 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id F10631D6; Sun, 20 Feb 2000 21:06:42 +0300 (MSK) From: Nikolai Saoukh To: Martin Husemann Cc: current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: Your message of "Sun, 20 Feb 2000 17:44:04 +0100." <200002201644.RAA01128@rumolt.teuto.de> Date: Sun, 20 Feb 2000 21:06:37 +0300 Message-Id: <20000220180643.180CC1FC@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Depends. If the drivers allocation is coherent with the vendors description > in the PnP configuration data, it's a newbus error (it shouldn't try to > allocate the card there in the first place). If the PnP info differs from > the drivers view of the card, it's either the vendors fault for providing wrong > infos (this wouldn't be the only card suffering) [fix: provide a quirk entry], > or the drivers fault: it should obey what the vendor tells PnP about the > card. Which case applies? Simple: if it's possible to change the driver to > obey the cards infos, that should be done. If the driver couldn't be made > to work support for that card should be removed :-) Well, current PnP code has own problems with parsing card data: * wrong calculation of memory range size (PR: kern/16712 with path). This bug will hit any card with io memory (ed driver for example). * inability to parse a little bit complicated config like in 'IBM Auto 16/4 Token-Ring ISA Adapter' -- I am still fighting with this bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 10:17:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id E23A337B784; Sun, 20 Feb 2000 10:17:29 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id SAA20221; Sun, 20 Feb 2000 18:17:30 GMT (envelope-from arg@arg1.demon.co.uk) Date: Sun, 20 Feb 2000 18:17:29 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Hellmuth Michaelis Cc: Doug Rabson , current@freebsd.org, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in the HSCX or ISAC: the ASIC on the card has 'folded' the address space so that the fifo appears at an address 3 bytes after the last register (0x3e with the current scheme - see tels0163_read_fifo()). The existing driver only uses offsets 0x20-0x3e relative to its assumed base address (and offsets 0x40 upwards are mapped separately). Note that the base address of 0x160 is a figment of the driver's imagination: the card is labelled as occupying 0xd80, and hence occupies 0x180/0x580/0x980 due to ISA address decoding rules. The 0x160 is only a convenience to make the driver's address calculations the same as the other cards - which is no longer necessary now that the driver has been restructured to have sc->readreg/writereg and can do things differently for each type of card. > The card in question allocates 3 portranges for this uses with each 0x40 > bytes in length. > > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > So where is the bug ? There is definitely a bug that it doesn't seem to allocate a (larger) portrange at 0xd80 - the output shown in an earlier message in this thread suggested that only a single byte at 0xd80 was allocated. The probe code accesses 0xd80, 0xd81, 0xd82, and testing indicates that it goes up to at least 0xd87, probably in fact all the way to 0xd1f. I am 99% certain that it is also incorrect to protect 0x160-0x17f (etc.). The driver certainly doesn't access registers in these ranges, and simple testing suggests that the card doesn't drive the bus for these regions. Unfortunately, my only 16.3 card is in a machine that is in use, so I can only do non-destructive testing on it. I will be able to test it properly in a couple of weeks when this machine has been retired. > This all looks perfectly reasonable to me with the exception that we > could start argueing about whether it would be reasonable to split the > allocation ranges for the ISAC and to save (if at all possible, there > are some more registers at the end of the HSCX on the card) some bytes > in the HSCX case. This would be wrong - the driver needs to protect all the address space occupied by the card, since it will be driving the bus for all these addresses and so another (PnP) device must not be assigned addresses in the "hole". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 11: 5:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 282DB37BF4F; Sun, 20 Feb 2000 11:05:38 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id UAA11429; Sun, 20 Feb 2000 20:05:35 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.9.3/8.8.8) id UAA02117; Sun, 20 Feb 2000 20:07:11 +0100 (MET) From: Martin Husemann Message-Id: <200002201907.UAA02117@rumolt.teuto.de> Subject: Re: Big ATA problems In-Reply-To: from Andrew Gordon at "Feb 20, 2000 06:17:29 pm" To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Sun, 20 Feb 2000 20:07:11 +0100 (MET) Cc: hm@kts.org (Hellmuth Michaelis), dfr@nlsystems.com (Doug Rabson), current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > that the fifo appears at an address 3 bytes after the last register (0x3e > with the current scheme - see tels0163_read_fifo()). Ah, then the driver should map the region the correct way and access it without offsets. This kind of stuff is why the NetBSD port uses an extra "offset" field in its private map/region array, so it can map something offset from the expected range and map the generic register offsets to the mapped-region-offsets efficiently. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 11:23: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 05FF337BF03; Sun, 20 Feb 2000 11:22:43 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id UAA19226; Sun, 20 Feb 2000 20:22:24 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id UAA15458; Sun, 20 Feb 2000 20:19:59 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 5227252AA3; Sun, 20 Feb 2000 20:19:52 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id A58381F17; Sun, 20 Feb 2000 20:19:47 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Andrew Gordon at "Feb 20, 2000 6:17:29 pm" To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Sun, 20 Feb 2000 20:19:47 +0100 (CET) Cc: dfr@nlsystems.com, current@freebsd.org, freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220191947.A58381F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gordon wrote: > On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > that the fifo appears at an address 3 bytes after the last register (0x3e > with the current scheme - see tels0163_read_fifo()). Oh yes, you are right! I was (and am still a bit) confused. So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX and at least three bytes at its base address, right ? This makes sense. Now the real question left is are this the only locations where the card is driving the bus ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 12: 6:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id E04BE37BF9A for ; Sun, 20 Feb 2000 12:06:33 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA09207; Sun, 20 Feb 2000 20:05:46 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id TAA18559; Sun, 20 Feb 2000 19:51:17 GMT (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <20000219171950.A81155@panzer.kdm.org> References: ; from rb@gid.co.uk on Sat, Feb 19, 2000 at 07:28:23PM +0000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 20 Feb 2000 19:51:19 +0000 To: "Kenneth D. Merry" From: Bob Bishop Subject: Re: cdrecord problem with current current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 17:19 -0700 19/2/00, Kenneth D. Merry wrote: >On Sat, Feb 19, 2000 at 19:28:23 +0000, Bob Bishop wrote: >> Hi, >> >> cdrecord, freshly built on last night's -current: > >Freshly built? That's cdrecord 1.8a21, which is several versions old. I >think you should be using cdrecord 1.8 release from the ports tree. Uh, yes, it would have helped enormously if I'd actually installed it. Works just fine, sorry for the false alarm. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 12:57:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragonstar.dhs.org (dsl-028-a.resnet.purdue.edu [128.211.161.178]) by hub.freebsd.org (Postfix) with ESMTP id C4A7237BED6 for ; Sun, 20 Feb 2000 12:57:45 -0800 (PST) (envelope-from jonsmith@dragonstar.dhs.org) Received: from localhost (jonsmith@localhost) by dragonstar.dhs.org (8.9.3/8.9.3) with ESMTP id PAA33979 for ; Sun, 20 Feb 2000 15:52:00 -0500 (EST) (envelope-from jonsmith@dragonstar.dhs.org) Date: Sun, 20 Feb 2000 15:51:59 -0500 (EST) From: Jonathan Smith To: freebsd-current@freebsd.org Subject: quickie atapi dvd question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First, no I haven't been reading the big ATA problem thread. I should be *ponders switching to digest list ;) * This has been the case over three buildworlds in the past three days. Is it a general problem that audio CD's fail to play in a dvd drive (or cd drive, for that matter ;) via cdcontrol as of the past few days and/or dvd's not being accessed properly, ie. with DeCSS? Cdcontrol would not eject, but would close until the buildworld that I just did. Now it will sometimes eject. On the other hand, I did try mounting a data CD and use it with no trouble. If it is not, I'll be more than happy to submit gobs and gobs of dmesg's, kernel configs (as if they would really tell much since someone(s) have done a WONDERFUL job with the ata configuration in the kernel conf (my compliment for the day ;)) error logs etc. If it is a common problem, I'll sit back and watch and profusely apollogise in advance. ;) Jon Smith -- Close your eyes. Now forget what you see. What do you feel? -- My heart. -- Come here. -- Your heart. -- See? We're exactly the same. Jon Smith -- Senior Math Major @ Purdue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:12:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 59E0A37BEF5; Sun, 20 Feb 2000 13:12:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66311; Sun, 20 Feb 2000 13:12:43 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14767; Sun, 20 Feb 2000 13:12:48 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:12:48 -0800 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <20000220131247.C14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <58727.951031902@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sat, Feb 19, 2000 at 11:41:22PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 11:41:22PM -0800, Kris Kennaway wrote: > Given that we can't import rsaref into FreeBSD and we can't depend on it > as a port, that about rules out any options for installing from > sysinstall. How does OpenBSD deal with it? Why is it so easy for them? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:17:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 958D237BEF5; Sun, 20 Feb 2000 13:17:49 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 20-145.008.popsite.net ([209.69.77.145] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12Mdj7-00051w-00; Sun, 20 Feb 2000 14:17:14 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 910801AB2; Sun, 20 Feb 2000 16:17:11 -0500 (EST) Date: Sun, 20 Feb 2000 16:17:11 -0500 From: Will Andrews To: David O'Brien Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000220161711.H44834@shadow.blackdawn.com> References: <58727.951031902@zippy.cdrom.com> <20000220131247.C14682@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000220131247.C14682@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sun, Feb 20, 2000 at 01:12:48PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:12:48PM -0800, David O'Brien wrote: > How does OpenBSD deal with it? Why is it so easy for them? Their main repositories lie in Canada and not the United States of Anti-encryption? :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:18:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7434137C082; Sun, 20 Feb 2000 13:18:19 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66340; Sun, 20 Feb 2000 13:18:09 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14821; Sun, 20 Feb 2000 13:18:13 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:18:13 -0800 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <20000220131813.E14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <88758.951034390@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sun, Feb 20, 2000 at 12:52:49AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 12:52:49AM -0800, Kris Kennaway wrote: > No, because openssl is compiled differently if rsaref is present or not - > it's not just a matter of dropping in librsaref.so (we can't always just > build the version with RSAref stubs because it references symbols in > librsaref and so binaries don't link). It sounds like we haven't made suffient RSAglue with suffient stubs that are weak symbols. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:24:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8B01137BFE8; Sun, 20 Feb 2000 13:24:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66355; Sun, 20 Feb 2000 13:22:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14841; Sun, 20 Feb 2000 13:22:15 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:22:15 -0800 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <20000220132215.F14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <38AF5F59.A0BEC49@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sat, Feb 19, 2000 at 07:46:50PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 07:46:50PM -0800, Kris Kennaway wrote: > > Having _a_ general-purpose cryptography toolkit in the base system allows > us to add in all sorts of cool things to FreeBSD (https support for fetch, > openssh, random cryptographic enhancements elsewhere). Which OpenBSD has done -- so why was it so easy for them? They have the *same* rules to live by that we have -- even though they are Canadian, the rsaref libs came from USA, thus they cannot be exported from Canada. It sounds like we just need to do more engineering -- maybe step back from the issue and look to see if we took a wrong turn in the way we've set things up. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:27: 0 2000 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 536D637C000; Sun, 20 Feb 2000 13:26:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA13205; Sun, 20 Feb 2000 13:23:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sun, 20 Feb 2000 13:12:48 PST." <20000220131247.C14682@dragon.nuxi.com> Date: Sun, 20 Feb 2000 13:23:40 -0800 Message-ID: <13202.951081820@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How does OpenBSD deal with it? Why is it so easy for them? It isn't. Go look for yourself. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:27:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5EA2F37C000; Sun, 20 Feb 2000 13:27:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66381; Sun, 20 Feb 2000 13:24:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14854; Sun, 20 Feb 2000 13:24:33 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:24:33 -0800 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <20000220132433.G14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sat, Feb 19, 2000 at 08:27:48PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 08:27:48PM -0800, Kris Kennaway wrote: > > How does OpenBSD do it? Cant we do what they do? > > They do a worse job than us is the short answer. That is not a very helpful answer. Care to provide details? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0CB8C37BFEA for ; Sun, 20 Feb 2000 13:28:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66403; Sun, 20 Feb 2000 13:26:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14870; Sun, 20 Feb 2000 13:26:47 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:26:47 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000220132647.H14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <42333.951021282@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <42333.951021282@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Sat, Feb 19, 2000 at 08:34:42PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote: > > 1. They're in Canada What does that buy them? They have the same restrictions on rsaref since it originated from the USA. > 2. What they do appears to be kind of icky, e.g. it requires more > "hand work" than I think the average FreeBSD user would be willing > to accept By handwork you man building, or installing? When I put OpenBSD 2.6 on my sparc5, I did a normal install and then ftp'ed down the proper ssl-base package. Then a simple pkg_add. Since OpenBSD does not have our ``pkg_add -r'' functionalitiy, it wasn't as simple as we could make it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:36:27 2000 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 6464E37BFAD; Sun, 20 Feb 2000 13:36:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA13365; Sun, 20 Feb 2000 13:32:22 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sun, 20 Feb 2000 13:26:47 PST." <20000220132647.H14682@dragon.nuxi.com> Date: Sun, 20 Feb 2000 13:32:22 -0800 Message-ID: <13362.951082342@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote: > > > > 1. They're in Canada > > What does that buy them? They have the same restrictions on rsaref since > it originated from the USA. I don't believe they're under the same legal gun when it comes to the patent issues. This isn't a crypto export issue, again, this is an issue of what people in the USA are technically allowed to do with the RSA reference code. If Canada has reciprocal rights on patents or something then they're indeed no better off than we are and I rescind the above statement. > By handwork you man building, or installing? When I put OpenBSD 2.6 on > my sparc5, I did a normal install and then ftp'ed down the proper > ssl-base package. Then a simple pkg_add. Since OpenBSD does not have > our ``pkg_add -r'' functionalitiy, it wasn't as simple as we could make > it. Yes, I think anybody can do the pkg_add step manually, but that's the kind of "handwork" I was referring to. What the ports collection and sysinstall both offer is a degree of "transparency" which is supposed to go beyond this, however. Even pkg_add -r only helps if you have a working network connection at the time. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:37: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 3820037C03A; Sun, 20 Feb 2000 13:37:01 -0800 (PST) Date: Sun, 20 Feb 2000 13:37:01 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000220133701.A27747@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org> <20000219181917Q.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000219181917Q.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Feb 19, 2000 at 06:19:17PM +0900 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 06:19:17PM +0900, Yoshinobu Inoue wrote: > EPSV is just enhanced version of PASV, and I think it needs to > check same kind of errors. Maybe same check as getreply() in > ftp/ftp.c will be necessary. About the spec, please check RFC2428. > > But the problem is that the error message is printed in > getreply() which is called from command(), because the error > message is sent from server. I don't look at the code deeply yet, but it looks from your words that EPSV command must be issued _only_ if ftp called as pftp or 'passive' command given or FTP_PASIVE_MODE env. variable is set and must be not issued in normal ftp mode at all, so it seems another bug found... -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:38:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 084C237BFD0 for ; Sun, 20 Feb 2000 13:38:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66432; Sun, 20 Feb 2000 13:35:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14899; Sun, 20 Feb 2000 13:35:12 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:35:12 -0800 From: "David O'Brien" To: Matthew Dillon Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 Message-ID: <20000220133512.I14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <56014.950933236@zippy.cdrom.com> <200002190431.UAA91173@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002190431.UAA91173@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Feb 18, 2000 at 08:31:06PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 08:31:06PM -0800, Matthew Dillon wrote: > > I wound up having to rm -rf /compat/linux and /usr/compat/linux and > then doing the make install, which worked. It created /usr/compat/linux > and didn't seem to care that no /compat/linux existed. However, > other linux programs (e.g. the linux netscape) still look in /compat so > I had to create a softlink from /compat/linux to /usr/compat/linux > in order for netscape to run. The /compat symlink should just die. compat bits should not be on the root partition, so why are we pretending? /usr/compat should be the only supported place. Peroid. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:41:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1298537BFCF; Sun, 20 Feb 2000 13:41:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA66439; Sun, 20 Feb 2000 13:38:54 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA14910; Sun, 20 Feb 2000 13:38:48 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 13:38:48 -0800 From: "David O'Brien" To: Kris Kennaway Cc: Robert Watson , freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? Message-ID: <20000220133848.J14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Fri, Feb 18, 2000 at 01:18:48PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 01:18:48PM -0800, Kris Kennaway wrote: > > Nope -- my make was in the top level /usr/src tree, in the form of ``make > > -j 3 all''. > > You need to make depend first..perhaps the makefile could be improved You should not need to. If it is required you have a broken Makefile and you need to add more dependacies. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:51:42 2000 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 CF6FE37C02C; Sun, 20 Feb 2000 13:51:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA14948; Sun, 20 Feb 2000 13:47:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 In-reply-to: Your message of "Sun, 20 Feb 2000 13:35:12 PST." <20000220133512.I14682@dragon.nuxi.com> Date: Sun, 20 Feb 2000 13:47:30 -0800 Message-ID: <14945.951083250@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The /compat symlink should just die. compat bits should not be on the > root partition, so why are we pretending? /usr/compat should be the only > supported place. Peroid. You miss the point entirely. Compat bits aren't intended for the root partition, they're intended for wherever you happen to have enough space for all that crap (and it can get quite large if you're "compat" with a number of different systems). For some people that's /usr. For others that's anywhere but since /usr is a comparatively small, read-only partition which they share amongst multiple boxes and they want the compat stuff to go in /usr/local/share/compat or something. The symlink gives you that flexibility and the fact that sysinstall points it at /usr/compat is simply a quick shortcut. It should probably *ask* where you want it to point, in fact, and I've just been too lazy to add that question to sysinstall. I should also point out that making it a non-symlink would also completely break the linux_base port (for one) on those systems where /usr (and hence /usr/compat) is a read-only volume. Ports aren't even technically supposed to touch anything outside of /usr/local, /usr/X11R6 and (on rare occasion) /etc/shells, and with a compat symlink you can still make sure they don't. - Jordan P.S. /usr/local/etc/shells anyone? :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 13:56: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 0D80B37BFBD; Sun, 20 Feb 2000 13:56:06 -0800 (PST) Date: Sun, 20 Feb 2000 13:56:06 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000220135605.A38025@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org> <20000219181917Q.shin@nd.net.fujitsu.co.jp> <20000220133701.A27747@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000220133701.A27747@freebsd.org>; from ache@freebsd.org on Sun, Feb 20, 2000 at 01:37:01PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:37:01PM -0800, Andrey A. Chernov wrote: > I don't look at the code deeply yet, but it looks from > your words that EPSV command must be issued _only_ if ftp called > as pftp or 'passive' command given or FTP_PASIVE_MODE > env. variable is set and must be not issued in normal ftp mode at all, > so it seems another bug found... Sorry, this place (EPSV == PASV) is right excepting proxy mode is not covered by EPSV (see PASV usage for proxy). -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4401237C1BB for ; Sun, 20 Feb 2000 14:06:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA66538; Sun, 20 Feb 2000 14:02:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA15171; Sun, 20 Feb 2000 14:02:11 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 14:02:11 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000220140211.K14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000220132647.H14682@dragon.nuxi.com> <13362.951082342@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <13362.951082342@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Sun, Feb 20, 2000 at 01:32:22PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:32:22PM -0800, Jordan K. Hubbard wrote: > > > 1. They're in Canada > > > > What does that buy them? They have the same restrictions on rsaref since > > it originated from the USA. > > I don't believe they're under the same legal gun when it comes to the > patent issues. This isn't a crypto export issue, again, this is an > issue of what people in the USA are technically allowed to do with the > RSA reference code. Then I am really missing the point and I wish it would be stated in suffient detail for one to be able to understand. * OpenBSD has the same distribution restraints concerning rsaref we do. * As an OpenBSD user in the USA, I have the same restrictions that I do as a FreeBSD user in the USA. Thus the patent issues are the same. I don't see where any reciprocal rights on patents between the USA and Canada comes into play here. While I don't know is how OpenBSD builds the two sets of bits, I do know how easy it was for me as a user to install 2.6 and get a RSA enabled crypto lib. > Yes, I think anybody can do the pkg_add step manually, but that's the > kind of "handwork" I was referring to. Ok, now we're getting on the same page of music. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14: 9:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id BF51537BF08; Sun, 20 Feb 2000 14:09:48 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 20-145.008.popsite.net ([209.69.77.145] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12MeVT-0007li-00; Sun, 20 Feb 2000 15:07:11 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id B9C531AC0; Sun, 20 Feb 2000 17:06:46 -0500 (EST) Date: Sun, 20 Feb 2000 17:06:46 -0500 From: Will Andrews To: "Jordan K. Hubbard" Cc: obrien@FreeBSD.ORG, Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 Message-ID: <20000220170646.J44834@shadow.blackdawn.com> References: <20000220133512.I14682@dragon.nuxi.com> <14945.951083250@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14945.951083250@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Sun, Feb 20, 2000 at 01:47:30PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote: > P.S. /usr/local/etc/shells anyone? :) I second this. As there becomes more ports around, this would simplify the job of ports since we would now modify a ${PREFIX}-based file instead of /etc/shells. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:11:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9632E37BEFD for ; Sun, 20 Feb 2000 14:11:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA66562; Sun, 20 Feb 2000 14:10:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA15195; Sun, 20 Feb 2000 14:10:35 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 14:10:35 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 Message-ID: <20000220141035.L14682@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000220133512.I14682@dragon.nuxi.com> <14945.951083250@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14945.951083250@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Sun, Feb 20, 2000 at 01:47:30PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote: > > You miss the point entirely. Possibly. > For others that's anywhere but since /usr is a comparatively small, > read-only partition which they share amongst multiple boxes and they > want the compat stuff to go in /usr/local/share/compat or something. > The symlink gives you that flexibility and the fact that sysinstall So they make /usr/compat be a symlink to where ever. As they may do for /usr/X11R6. Buy why not reduce the complexity for the 90% case? If we really imagine people wanting to put the compat bits elsewhere, then we should make the location a knob in /etc/rc.conf and a sysctl to tell the linux and osf1 image activators where to find the compat bits. > I should also point out that making it a non-symlink would also > completely break the linux_base port (for one) on those systems where > /usr (and hence /usr/compat) is a read-only volume. How did those read-only volumes get populated? How was the initial install done? Build worlds? I don't see where installing compat bits is any different. > Ports aren't even technically supposed to touch anything outside of > /usr/local, A mistake, but that's too far gone to fix. [should have been /usr/pkg] -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:14:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id F370437BF08; Sun, 20 Feb 2000 14:14:42 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id BAA08617; Mon, 21 Feb 2000 01:14:04 +0300 (MSK) (envelope-from ache) Date: Mon, 21 Feb 2000 01:14:04 +0300 From: "Andrey A. Chernov" To: jkh@freebsd.org, current@freebsd.org Subject: wrong default in login.conf Message-ID: <20000221011404.A8609@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, please approve this patch. It seems not good to have FTP_PASSIVE_MODE On as default while ftp program itself have it Off by default. Lets either change ftp program defaults to Passive On or login.conf defaults to Passive Off. I prefer second variant: --- login.conf.bak Wed Sep 15 04:09:22 1999 +++ login.conf Mon Feb 21 01:10:53 2000 @@ -22,7 +22,7 @@ default:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ - :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ + :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ :path=~/bin /bin /usr/bin /usr/local/bin /usr/X11R6/bin:\ :nologin=/var/run/nologin:\ :cputime=unlimited:\ -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:16:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 4FF5637BFF4; Sun, 20 Feb 2000 14:16:27 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA42409; Sun, 20 Feb 2000 14:14:22 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 14:14:21 -0800 (PST) From: Kris Kennaway To: "David O'Brien" Cc: Robert Watson , freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? In-Reply-To: <20000220133848.J14682@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > On Fri, Feb 18, 2000 at 01:18:48PM -0800, Kris Kennaway wrote: > > > Nope -- my make was in the top level /usr/src tree, in the form of ``make > > > -j 3 all''. > > > > You need to make depend first..perhaps the makefile could be improved > > You should not need to. If it is required you have a broken Makefile and > you need to add more dependacies. I'll try and look at it tonight - if you could too it would be helpful. I stand by my comment that 'make depend' is needed generally, though - things often fail elsewhere in the tree (e.g. gcc, perl) when it's not done. I'll make a log for you next time it happens if you like. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8248137BFF5; Sun, 20 Feb 2000 14:18:01 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA42492; Sun, 20 Feb 2000 14:15:21 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 14:15:20 -0800 (PST) From: Kris Kennaway To: "David O'Brien" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <20000220132647.H14682@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > > 2. What they do appears to be kind of icky, e.g. it requires more > > "hand work" than I think the average FreeBSD user would be willing > > to accept > > By handwork you man building, or installing? When I put OpenBSD 2.6 on > my sparc5, I did a normal install and then ftp'ed down the proper > ssl-base package. Then a simple pkg_add. Since OpenBSD does not have > our ``pkg_add -r'' functionalitiy, it wasn't as simple as we could make > it. Err, David, that's exactly the same as our system then. OpenBSD's handling of OpenSSL is bad in other ways, but in this regard it's exactly what we do now. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:20:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1BD1837C01F; Sun, 20 Feb 2000 14:20:52 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA42695; Sun, 20 Feb 2000 14:18:23 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 14:18:23 -0800 (PST) From: Kris Kennaway To: "David O'Brien" Cc: freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <20000220131813.E14682@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > On Sun, Feb 20, 2000 at 12:52:49AM -0800, Kris Kennaway wrote: > > No, because openssl is compiled differently if rsaref is present or not - > > it's not just a matter of dropping in librsaref.so (we can't always just > > build the version with RSAref stubs because it references symbols in > > librsaref and so binaries don't link). > > It sounds like we haven't made suffient RSAglue with suffient stubs that > are weak symbols. Could be, could be. Like I said, I don't know enough about weak symbols to know whether they'd help. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:42:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6079037C027; Sun, 20 Feb 2000 14:42:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA66633; Sun, 20 Feb 2000 14:37:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA15611; Sun, 20 Feb 2000 14:37:45 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 14:37:45 -0800 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? Message-ID: <20000220143745.A15548@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20000220133848.J14682@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sun, Feb 20, 2000 at 02:14:21PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 02:14:21PM -0800, Kris Kennaway wrote: > stand by my comment that 'make depend' is needed generally, though - > things often fail elsewhere in the tree (e.g. gcc, perl) Yes, give a log. Look at all the gunk in src/gnu/usr.bin/cc/cc_tools/Makefile to keep a `make depend' from being required. Perl? Well, that's just perl for you. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:42:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 737F837C0CD for ; Sun, 20 Feb 2000 14:42:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA66639 for ; Sun, 20 Feb 2000 14:39:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA15637 for current@freebsd.org; Sun, 20 Feb 2000 14:39:20 -0800 (PST) (envelope-from obrien) Date: Sun, 20 Feb 2000 14:39:20 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: wrong default in login.conf Message-ID: <20000220143920.B15548@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000221011404.A8609@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221011404.A8609@nagual.pp.ru>; from ache@nagual.pp.ru on Mon, Feb 21, 2000 at 01:14:04AM +0300 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 01:14:04AM +0300, Andrey A. Chernov wrote: > > It seems not good to have FTP_PASSIVE_MODE On as default while ftp program > itself have it Off by default. Agreed. > Lets either change ftp program defaults to Passive On or login.conf /usr/bin/ftp should default to Passive On. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:43:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 4843637BFEA; Sun, 20 Feb 2000 14:43:10 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA43829; Sun, 20 Feb 2000 14:31:43 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 14:31:43 -0800 (PST) From: Kris Kennaway To: Jonathan Smith Cc: freebsd-current@freebsd.org Subject: Re: quickie atapi dvd question 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, 20 Feb 2000, Jonathan Smith wrote: > Is it a general problem that audio CD's fail to play in a dvd drive (or > cd drive, for that matter ;) via cdcontrol as of the past few days and/or > dvd's not being accessed properly, ie. with DeCSS? Cdcontrol would not > eject, but would close until the buildworld that I just did. Now it will > sometimes eject. On the other hand, I did try mounting a data CD and use > it with no trouble. I've not been able to play audio CDs ever since switching to the new ATA drivers. Soren tells me there are two different ways to encode commands to the drive, and no easy way to tell which one the drive expects :-( Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 14:52:44 2000 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 8D08337C0C9; Sun, 20 Feb 2000 14:52:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA17059; Sun, 20 Feb 2000 14:29:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Andrey A. Chernov" Cc: jkh@FreeBSD.org, current@FreeBSD.org Subject: Re: wrong default in login.conf In-reply-to: Your message of "Mon, 21 Feb 2000 01:14:04 +0300." <20000221011404.A8609@nagual.pp.ru> Date: Sun, 20 Feb 2000 14:29:30 -0800 Message-ID: <17056.951085770@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, please approve this patch. > > It seems not good to have FTP_PASSIVE_MODE On as default while ftp program > itself have it Off by default. Lets either change ftp program defaults to > Passive On or login.conf defaults to Passive Off. I prefer second variant: Um, the point of turning FTP_PASSIVE_MODE on by default is that it's not just one "client" which uses it. The ftpio(3) library uses it, for one, and hence pkg_add, sysinstall and fetch do too. I can count at least 4 "ftp programs" here which would all need to be changed independently and I don't much like that idea during code freeze, even if you could convince me that it was a good idea. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15: 1:28 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id F16CD37C08D; Sun, 20 Feb 2000 15:01:26 -0800 (PST) Date: Sun, 20 Feb 2000 15:01:26 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000220150126.A54323@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org> <20000219181917Q.shin@nd.net.fujitsu.co.jp> <20000220133701.A27747@freebsd.org> <20000220135605.A38025@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000220135605.A38025@freebsd.org>; from ache@freebsd.org on Sun, Feb 20, 2000 at 01:56:06PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:56:06PM -0800, Andrey A. Chernov wrote: > Sorry, this place (EPSV == PASV) is right excepting proxy mode is not covered by > EPSV (see PASV usage for proxy). Another error is that static int try_epsv = 1; is set globally for all connections made by ftp instead of current one only. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15: 5:10 2000 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 24DCB37C02C; Sun, 20 Feb 2000 15:04:48 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id JAA03224; Sun, 20 Feb 2000 09:15:43 GMT (envelope-from nik) Date: Sun, 20 Feb 2000 09:15:41 +0000 From: Nik Clayton To: current@freebsd.org, ports@freebsd.org Subject: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS Message-ID: <20000220091540.A2628@catkin.nothing-going-on.org> Reply-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Sent to -current and -ports, followups set to -current ] Here's another trivial patch that people might like to comment on before I commit it. I'm doing more and more FreeBSD installs recently at various client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of those standard things you have to do if there's a firewall in place. Any one got any objection to mentioning that fact, with the included patch? N Index: make.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/make.conf,v retrieving revision 1.91 diff -u -r1.91 make.conf --- make.conf 2000/02/09 04:08:18 1.91 +++ make.conf 2000/02/20 09:10:25 @@ -113,6 +113,10 @@ # #MOTIFLIB= -L${X11BASE}/lib -lXm # +# If you are behind a firewall, this will force port fetching to use +# passive mode, which is required for most types of firewall. +# +#FETCH_BEFORE_ARGS= -p # # If you're resident in the USA, this will help various ports to determine # whether or not they should attempt to comply with the various U.S. -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15: 6:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D25837C078; Sun, 20 Feb 2000 15:06:40 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA16572; Sun, 20 Feb 2000 17:06:13 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-75.max1.wa.cyberlynk.net(207.227.118.75) by peak.mountin.net via smap (V1.3) id sma016567; Sun Feb 20 17:06:02 2000 Message-Id: <3.0.3.32.20000220170538.009084b0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 20 Feb 2000 17:05:38 -0600 To: Kris Kennaway From: "Jeffrey J. Mountin" Subject: RE: openssl in -current Cc: current@FreeBSD.ORG In-Reply-To: References: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.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 10:17 PM 2/19/00 -0800, Kris Kennaway wrote: >This doesn't help. The RSA source not being there isn't the problem, the >problem is that there are two different binary versions depending on how >you build it (with rsaref or not). Source code builds aren't a problem, >they already work fine, it's people who install binary snapshots (e.g. >from the CD). As one that was bit by this, at a minimum we would need an errata entry, so that that want need RSA support will need to build the port and rebuild openssl on the base system, which requires both src/secure and src/crypto. While I don't have a problem with the cumbersome way of installing a fully function openssl, it does make more work for the ports guys, and so I'd vote to drop openssl from the base for the reason that the goal is a "good" point-oh release. Ports that depend on RSA should be made to check for the includes, which is the most obvious error when building. This being addressed. Just commenting. Considering that building and installing world takes quite a while, it would be nice to have a simple way, so wonder if a simple 'make all install' in secure/usr.bin/openssl will do it for everything that depends on openssl. Chapter 6.5 of the handbook implies that a make world is needed. Doesn't bother me (much), but might be considered cruel and unusual punishment to those not familiar with building. This whole deal is adding a lot of confusion. While many of us can work with/around these problems, it isn't really streamlined. My big question is - Do we really want to force a 'make world' on the those that want RSA support in openssl? That would be ugly, when before it was simply the matter of building only two ports. my .02 Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:13: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B43CC37BFEA for ; Sun, 20 Feb 2000 15:12:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12MfX3-00007v-00 for current@FreeBSD.ORG; Mon, 21 Feb 2000 01:12:53 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS In-reply-to: Your message of "Sun, 20 Feb 2000 09:15:41 GMT." <20000220091540.A2628@catkin.nothing-going-on.org> Date: Mon, 21 Feb 2000 01:12:53 +0200 Message-ID: <490.951088373@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000 09:15:41 GMT, Nik Clayton wrote: > Here's another trivial patch that people might like to comment on before I > commit it. I'm doing more and more FreeBSD installs recently at various > client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of > those standard things you have to do if there's a firewall in place. I thought we'd all pretty much agreed that things like this don't belong in /etc/make.conf. I would have thought that this would be more at home in the system profile (as an environment variable) or in some ports-specific Makefile. I can remember discussions about such a Makefile, but I can't remember any resolution. Did we ever decide on a file to polute, other than /etc/make.conf? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:15:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 2506537C0B9 for ; Sun, 20 Feb 2000 15:15:43 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 6AB48137F83 for ; Sun, 20 Feb 2000 18:15:31 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id SAA66448; Sun, 20 Feb 2000 18:15:50 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14512.30118.185254.159934@trooper.velocet.net> Date: Sun, 20 Feb 2000 18:15:50 -0500 (EST) To: freebsd-current@freebsd.org Subject: camcontrol rescan and sym0 X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to have an Adaptec 2940UW in this machine, but I now have a: sym0: <895> port 0xd800-0xd8ff mem 0xefffe000-0xefffefff,0xefffff00-0xefffffff irq 11 at device 13.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking This attaches: sa0 at sym0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 31) sa1 at sym0 bus 0 target 9 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Mounting root from ufs:/dev/ad0s1a cd1 at sym0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: cd present [1 x 2048 byte records] ... now sa1 is an external drive that I sometimes take somewhere else. I've found that camcontrol rescan on this card can wedge the scsi bus for a number of seconds. This didn't happen on the adaptec, so I'm assuming that this isn't normal behavior. When things return to normal, the rescan is successful, but the 30ish second wait isn't pleasant. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:26: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id C923937BFCD; Sun, 20 Feb 2000 15:26:05 -0800 (PST) Date: Sun, 20 Feb 2000 15:26:05 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: EPSV patch for review (was Re: Broken FTP) Message-ID: <20000220152605.A59931@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org> <20000219181917Q.shin@nd.net.fujitsu.co.jp> <20000220133701.A27747@freebsd.org> <20000220135605.A38025@freebsd.org> <20000220150126.A54323@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000220150126.A54323@freebsd.org>; from ache@freebsd.org on Sun, Feb 20, 2000 at 03:01:26PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please review this patch. It fix all problems I mention. --- ftp.c.old Sun Feb 20 23:30:29 2000 +++ ftp.c Mon Feb 21 02:21:01 2000 @@ -1173,8 +1173,6 @@ #endif if (passivemode) { - static int try_epsv = 1; - data_addr = myctladdr; data = socket(data_addr.su_family, SOCK_STREAM, 0); if (data < 0) { @@ -1206,10 +1204,16 @@ warn("setsockopt (ignored)"); switch (data_addr.su_family) { case AF_INET: - if (try_epsv != 0) { + if (try_epsv) { + int overbose; + + overbose = verbose; + if (debug == 0) + verbose = -1; result = command(pasvcmd = "EPSV"); + verbose = overbose; if (code / 10 == 22 && code != 229) { - puts("wrong server: return code must be 229"); + puts("wrong server: EPSV return code must be 229"); result = COMPLETE + 1; } } else @@ -1223,7 +1227,7 @@ case AF_INET6: result = command(pasvcmd = "EPSV"); if (code / 10 == 22 && code != 229) { - puts("wrong server: return code must be 229"); + puts("wrong server: EPSV return code must be 229"); result = COMPLETE + 1; } if (result != COMPLETE) @@ -1711,7 +1715,9 @@ } if (curtype != prox_type) changetype(prox_type, 1); - if (command("PASV") != COMPLETE) { + if (try_epsv && command("EPSV") != COMPLETE) + try_epsv = 0; + if (!try_epsv && command("PASV") != COMPLETE) { puts("proxy server does not support third party transfers."); return; } --- util.c.old Mon Feb 7 08:53:26 2000 +++ util.c Mon Feb 21 02:13:20 2000 @@ -117,6 +117,7 @@ } connected = 1; + try_epsv = 1; /* * Set up defaults for FTP. */ --- ftp_var.h.old Mon Feb 14 21:31:56 2000 +++ ftp_var.h Mon Feb 21 02:13:20 2000 @@ -120,6 +120,7 @@ int dirchange; /* remote directory changed by cd command */ int ttywidth; /* width of tty */ char *tmpdir; /* temporary directory */ +int try_epsv; /* try EPSV for this session */ #ifndef SMALL int editing; /* command line editing enabled */ -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:26:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E7DA637C089; Sun, 20 Feb 2000 15:26:17 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12Mfju-0000CB-00; Mon, 21 Feb 2000 01:26:10 +0200 From: Sheldon Hearn To: Kris Kennaway Cc: Jonathan Smith , freebsd-current@FreeBSD.ORG Subject: Re: quickie atapi dvd question In-reply-to: Your message of "Sun, 20 Feb 2000 14:31:43 PST." Date: Mon, 21 Feb 2000 01:26:10 +0200 Message-ID: <754.951089170@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000 14:31:43 PST, Kris Kennaway wrote: > I've not been able to play audio CDs ever since switching to the new ATA > drivers. Soren tells me there are two different ways to encode commands to > the drive, and no easy way to tell which one the drive expects :-( Welcome to it. This has been the case for me since the ata driver was first introduced. In my case, it's a cheap Creative labs piece of rubbish which says ATAPI on the casing but doesn't fully comply with the standard. Of course, this _is_ audio CD's we're talking about. Hardly mission-critical for the kind of person who buys cheap Creative Labs almost-ATAPI crap. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:38:25 2000 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 015BE37C003 for ; Sun, 20 Feb 2000 15:38:21 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA16005 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 00:38:16 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA71839 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 00:36:49 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: openssl in -current Date: 21 Feb 2000 00:36:49 +0100 Message-ID: <88ptqh$264i$1@bigeye.rhein-neckar.de> References: <58727.951031902@zippy.cdrom.com> <20000220131247.C14682@dragon.nuxi.com> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > How does OpenBSD deal with it? Why is it so easy for them? 0. RSA situation In the USA, the RSA algorithm(!) is patented by RSA Inc. It doesn't matter where the actual code is from, any use of RSA needs permission by the patent holder. RSA Inc. provides a reference implentation (RSAREF), which is free for private/educational/whatever use. Other implementations are not covered by this license, i.e. their use infringes on the patent. Commercial users need to get an explicit license from RSA Inc., which from what I hear you can't get in practice. The American RSA patent does not affect the rest of the world, which can freely use the algorithm in whatever implementation. In short again: - USA, non-commercial: must use RSAREF - USA, commercial: no RSA - international: free RSA 1. Installation As distributed on CD/FTP, OpenBSD ships with a shared libcrypto in /usr/lib that doesn't contain RSA. It has some stubs that will abort the program with an error message, if it tries to call the RSA routines. In order to provide RSA, the user needs to install an additional package from the net. This exists in two versions, the international one containing OpenSSL's own RSA implementation, and the USA one with RSAREF. This package installs a new libcrypto in /usr/local/lib. The RSA-enabled shared library has a higher version number, so on program start-up it will be picked up in preference to the non-RSA one. (This whole setup collapses for those architectures that don't support shared libraries, but I don't think I need to get into this now as it doesn't concern FreeBSD.) In short again: - no RSA out of the box - must add international or USA package with RSA after installation 2. Source OpenSSL is integrated into the OpenBSD source tree. However, the RSA routines are missing and are not in the CVS repository. A separate source package--again in international and USA versions--is available by FTP. This can simply be dropped at the appropriate place into the OpenBSD source tree and will be automatically picked up by a world build to produce an RSA-enabled libcrypto. Otherwise a non-RSA library will be built. In short again: - no RSA in OpenBSD repository - source available as drop-in external package 3. Commentary The OpenBSD solution is not all that easy. However, it is not that difficult from a user's perspective either. The install script (OpenBSD uses a comprehensive shell script in place of sysinstall) asks the user whether to install the RSA-enabled libraries and as an alternative points to ssl(8) for information on how to do this later. If we want to have OpenSSL in the base system, we necessarily will need to use an approach similar to the OpenBSD one. I would like to point out that OpenBSD has made it a major advocacy point that they ship with OpenSSL and OpenSSH out of the box, nicely omitting the fact that you need to install a separate package off the net to actually make it work. However, the favorable user comments/reviews I see seem to suggest that people very much like the OpenBSD approach. Again and again it is mentioned that contrary to other operating systems OpenBSD ships with encryption out of the box, that you don't need to install additional ports or packages, and the additional install step either isn't even mentioned or only in passing, with a remark how easy this is. There's also the argument that OpenBSD is optimally prepared for the running out of the RSA patent at the end of the year. Now, I'm the first to agree that OpenBSD's OpenSSL integration doesn't buy all that much. Users seem to disagree though. It's a perception thing, I guess. Of course, if you want to actually integrate OpenSSL-using software into the base system (OpenBSD has OpenSSH and Apache), then you obviously also need to have OpenSSL or at least a stub for it in the base system. FWIW, I support Kris' push to put OpenSSL in the base system. -- Christian "naddy" Weisgerber naddy@mips.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 Sun Feb 20 15:45:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id CB7CA37C003 for ; Sun, 20 Feb 2000 15:45:51 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e1KNjBB18121; Sun, 20 Feb 2000 16:45:11 -0700 (MST) Message-Id: <200002202345.e1KNjBB18121@orthanc.ab.ca> To: naddy@mips.rhein-neckar.de (Christian Weisgerber) Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "21 Feb 2000 00:36:49 +0100." <88ptqh$264i$1@bigeye.rhein-neckar.de> Date: Sun, 20 Feb 2000 16:45:10 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Christian" == Christian Weisgerber writes: Christian> Commercial users need to get Christian> an explicit license from RSA Inc., which from what I Christian> hear you can't get in practice. Correct. The only option for commercial software (in the US) is to license the BSAFE libraries from RSA. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 15:46:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.knf.beldin.net (kibby.knf.beldin.net [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 1675737C0A5 for ; Sun, 20 Feb 2000 15:46:02 -0800 (PST) (envelope-from kibbet@kibby.knf.beldin.net) Received: (from kibbet@localhost) by kibby.knf.beldin.net (8.9.3/8.9.3) id XAA10780 for freebsd-current@freebsd.org; Sun, 20 Feb 2000 23:22:37 +1030 (CST) (envelope-from kibbet) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 20 Feb 2000 23:22:36 +1030 (CST) From: kibbet To: freebsd-current@freebsd.org Subject: Re: make world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Feb-00 kibbet wrote: > Hey all, > > I got this error, and the 20000205 entry in UPDATING didn't seem to cover > enough for me, I was comming from a clean bin install of 3.2. > > UPDATING - 20000205 entry; > > make buildworld > make installworld This will fail > cd usr.bin/xinstall > make clean all install NOSHARED=YES > cd ../.. > XXX make installworld > > (2) cd gnu/usr.bin/texinfo > (3) make clean all install NOSHARED=YES > (4) cd ../../.. > (5) make installworld > Whoops, I read my install-log, it was actually; (2) cd gnu/usr.bin/texinfo/install-info (4) cd ../../../.. There's of course no need to build everything under gnu/usr.bin/texinfo :) Cheers, Kent Ibbetson KNF Publishing kibbet@knfpub.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 16: 5:58 2000 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 72F9C37BF5B for ; Sun, 20 Feb 2000 16:05:55 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id BAA23666 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 01:05:54 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA71904 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 00:44:46 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: openssl in -current Date: 21 Feb 2000 00:44:46 +0100 Message-ID: <88pu9e$266o$1@bigeye.rhein-neckar.de> References: <20000220132647.H14682@dragon.nuxi.com> <13362.951082342@zippy.cdrom.com> <20000220140211.K14682@dragon.nuxi.com> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > While I don't know is how OpenBSD builds the two sets of bits, I do know > how easy it was for me as a user to install 2.6 and get a RSA enabled > crypto lib. Alas, if I understand Jordan correctly, he objects exactly to this additional installation step (adding a ssl package) as being too difficult. -- Christian "naddy" Weisgerber naddy@mips.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 Sun Feb 20 16: 6: 4 2000 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 69B2E37C072 for ; Sun, 20 Feb 2000 16:05:58 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id BAA23945 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 01:05:57 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA72462 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 01:05:31 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: openssl in -current Date: 21 Feb 2000 01:05:31 +0100 Message-ID: <88pvgb$26o5$1@bigeye.rhein-neckar.de> References: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> <3.0.3.32.20000220170538.009084b0@207.227.119.2> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey J. Mountin wrote: > My big question is - Do we really want to force a 'make world' on the those > that want RSA support in openssl? We don't want to and WE DON'T DO. > That would be ugly, when before it was simply the matter of building only > two ports. binary installation: - before: user needs to install openssl port - now: user needs to install openssl package make world: - before: user needs to install openssl port - now: openssl is built as part of the world This thread suffers from people yelling objection without even understanding the situation. There are a few teething problems which are blown up way out of proportion: - Some people outside the US get their crypto source from a US mirror. They shouldn't do this in the first place. In the presence of USA_RESIDENT=NO, OpenSSL than proceeds to build without RSA. - Apparently, there currently is a bug where bsd.port.mk fails to recognize that the RSA-enabled package hasn't been installed. I'm sure this can easily be fixed, but tying up Kris in endless discussions here won't accelerate the process. -- Christian "naddy" Weisgerber naddy@mips.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 Sun Feb 20 16:23:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-84.max2-du-ws.dialnetwork.pavilion.co.uk [212.74.8.212]) by hub.freebsd.org (Postfix) with ESMTP id D495537BF7D for ; Sun, 20 Feb 2000 16:23:11 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@shift.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA43258; Mon, 21 Feb 2000 00:00:43 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA82640; Mon, 21 Feb 2000 00:00:31 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002210000.AAA82640@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas Dean Cc: current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: Problems with Recent PPP Changes In-Reply-To: Message from Thomas Dean of "Wed, 16 Feb 2000 06:59:57 PST." <200002161459.GAA01965@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Feb 2000 00:00:31 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the reply. > > > Date: Wed, 16 Feb 2000 01:16:25 -0700 > > From: Warner Losh > > > > In message <200002160421.UAA00933@ix.netcom.com> Thomas Dean writes: > > : What change to ppp did I miss? > > > > There were some quoting and comment recognition changes at one > > point... > > > > That is the problem. My ISP requires a '#' as a leading delimiter for > the login name. ppp determines the '#' is the start of a line-end > comment. From the log: > > Phase: bundle: Authenticate > Phase: deflink: his = PAP, mine = none > Phase: Pap Output: ******** > Warning: Sending empty PAP authname! > Phase: Pap Input: FAILURE (Invalid Login) > Phase: deflink: Disconnected! > Phase: deflink: lcp -> logout > > How do I handle the required leading '#' on the login name? Escaping > it doesn't work. Sorry for the delay... you need to quote your password. > tomdean -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 16:45:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from Stalker.Alfacom.net (SAT.Alfacom.net [207.241.164.112]) by hub.freebsd.org (Postfix) with ESMTP id 4C9B437BF7D for ; Sun, 20 Feb 2000 16:44:52 -0800 (PST) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (dup-47.alfacom.net [62.244.36.47]) by Stalker.Alfacom.net (8.9.0/8.9.0) with ESMTP id CAA11756 for ; Mon, 21 Feb 2000 02:43:08 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.9.3/8.9.3) with ESMTP id CAA00308 for ; Mon, 21 Feb 2000 02:41:47 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Mon, 21 Feb 2000 02:41:47 +0200 (EET) From: Vladimir Kushnir To: freebsd-current@FreeBSD.ORG Subject: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002182057.MAA23327@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I dont't know if this is some HW problem, but after the last update system became unbootable if I load modules by /boot/loader rather them kldload. > sos 2000/02/18 12:57:33 PST > > Modified files: > sys/alpha/include md_var.h > sys/alpha/pci pcibus.c > sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-disk.h > ata-dma.c atapi-all.c atapi-all.h > atapi-cd.c atapi-cd.h atapi-fd.c > atapi-fd.h atapi-tape.c atapi-tape.h > sys/kern subr_disk.c Sorry I can't give details of kernel message (BTW, how do I catch them in such a case?) but system stops at ATA devices probe with ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa0400000) Mounting root from ufs:/dev/ad0s3a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 If I load modules by /etc/rc - everything goes all right, except sysctl hw.atamodes hw.atamodes: dma,dma,---,---, while I have UDMA CD-ROM (and system sets UDMA2 on it if required manually). System: PIII/450, MB CT-6BTM with BX440 chipset,ata0-master: QUANTUM FIREBALL CX10.2A, ata0-slave: Delta UDMA 44x CDROM. uname-a: FreeBSD kushnir1.kiev.ua 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb 21 02:01:39 EET 2000 root@kushnir1.kiev.ua:/usr/src/sys/compile/KUSHNIR i386 Dmesg output (sorry, it's long): Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Feb 21 02:01:39 EET 2000 root@kushnir1.kiev.ua:/usr/src/sys/compile/KUSHNIR Calibrating clock(s) ... TSC clock: 451075452 Hz, i8254 clock: 1193323 Hz Press a key on the console to abort clock calibration Timecounter "i8254" frequency 1193323 Hz CPU: Pentium III/Pentium III Xeon (451.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ff real memory = 67043328 (65472K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x0028a000 - 0x03fe5fff, 64339968 bytes (15708 pages) avail memory = 62402560 (60940K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fac40 bios32: Entry = 0xfb0c0 (c00fb0c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb2a0 pnpbios: Found PnP BIOS data at 0xc00fbea0 pnpbios: Entry = f0000:bec8 Rev = 1.0 Other BIOS signatures found: ACPI: 000f6c10 Preloaded elf kernel "kernel.TEST2" at 0xc0271000. Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e0000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000f000, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[20]: type 1, range 32, base 0000e000, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00005000, size 4 found-> vendor=0x1073, dev=0x000d, revid=0x03 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base e8000000, size 15 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10de, dev=0x002c, revid=0x11 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e4000000, size 24 map[14]: type 1, range 32, base e6000000, size 25 pci1: on pcib1 pci1: NVidia Riva Vanta TNT2 graphics accelerator (vendor=0x10de, dev=0x002c) at 0.0 irq 11 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 2.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=10 ata0: mask=03 status0=50 status1=10 ata0: devices = 0x9 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 ata1: mask=03 status0=0a status1=0a ata1: mask=03 status0=29 status1=29 ata1: devices = 0x0 ata1: probe allocation failed pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 2.2 irq 10 intpm0: port 0x5000-0x500f irq 9 at device 2.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pci0: unknown card (vendor=0x1073, dev=0x000d) at 14.0 irq 12 pnpbios: 14 devices, largest 69 bytes PNP0000: adding irq mask 00x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: start dependant pnpbios: handle 0 device ID PNP0000 (0000d041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: start dependant pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: start dependant pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: start dependant pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: start dependant pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 PNP0800: start dependant pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 PNP0c04: start dependant pnpbios: handle 6 device ID PNP0c04 (040cd041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000 PNP0c01: adding memory range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding memory range 0x100000-0x3ffffff, size=0x3f00000 PNP0c01: start dependant pnpbios: handle 7 device ID PNP0c01 (010cd041) PNP0c02: adding memory range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding memory range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding memory range 0xf8000-0xfbfff, size=0x4000 PNP0c02: adding memory range 0xfc000-0xfffff, size=0x4000 PNP0c02: start dependant pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x294-0x297, size=0x4, align=0 PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x480-0x48f, size=0x10, align=0 PNP0a03: adding io range 0x4000-0x403f, size=0x40, align=0 PNP0a03: adding io range 0x5000-0x501f, size=0x20, align=0 PNP0a03: start dependant pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: adding irq mask 0x40 PNP0700: start dependant pnpbios: handle 13 device ID PNP0700 (0007d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: start dependant pnpbios: handle 14 device ID PNP0400 (0004d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 16 device ID PNP0501 (0105d041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port found at 0x378 ppc0: SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode pps0: on ppbus0 ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A isa_probe_children: probing PnP devices unknown: can't assign resources unknown0: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0xf0-0xff irq 13 on isa0 unknown4: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x3ffffff on isa0 unknown5: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata0-slave: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata0-slave: success setting up PIO4 mode on generic chip acd0: CDROM drive at ata0 as slave acd0: 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s3a ad0s1: type 0xc, start 63, end = 8193149, size 8193087 : OK ad0s2: type 0x5, start 8209215, end = 10265534, size 2056320 : OK ad0s3: type 0xa5, start 10265535, end = 20033054, size 9767520 : OK ad0s5: type 0xb, start 8209278, end = 10265534, size 2056257 : OK start_init: trying /sbin/init VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 05 02 07 01 00 01 0e 01 00 01 17 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 33 mode(s) found VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc089afa2 (1000022) VESA: NVidia VESA: NVidia Riva TNT B1 ata0-slave: success setting up UDMA2 mode on PIIX4 chip Linux-ELF exec handler installed splash: image decoder found: green_saver bpf: tun0 attached -- ===========================|======================= Vladimir Kushnir | vkushnir@Alfacom.net | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 17: 4:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 336AD37BD43 for ; Sun, 20 Feb 2000 17:04:47 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 3807 invoked from network); 21 Feb 2000 00:59:44 -0000 Received: from lcm208.cvzoom.net (HELO cvzoom.net) (208.230.69.208) by ns.cvzoom.net with SMTP; 21 Feb 2000 00:59:44 -0000 Message-ID: <38B08DE3.7080906@cvzoom.net> Date: Sun, 20 Feb 2000 19:59:15 -0500 From: Donn Miller User-Agent: Netscape 5.0 X-Accept-Language: en MIME-Version: 1.0 To: Vladimir Kushnir Cc: freebsd-current@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vladimir Kushnir wrote: > = > Hello, > I dont't know if this is some HW problem, but after the last update sys= tem > became unbootable if I load modules by /boot/loader rather them kldload= =2E = That seems to be a bug -- I'd just load the modules via /etc/rc.conf for = now.=A0 Other people have reported problems when loading modules via the = boot loader.=A0 My advice would be to just load them via /etc/rc.conf - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 17:44:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 0DBE637BBEB; Sun, 20 Feb 2000 17:44:41 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA06234; Sun, 20 Feb 2000 17:43:21 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B0981D.DC2FCCEC@gorean.org> Date: Sun, 20 Feb 2000 17:42:53 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Cc: nik@freebsd.org Subject: Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS References: <20000220091540.A2628@catkin.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > > [ Sent to -current and -ports, followups set to -current ] > > Here's another trivial patch that people might like to comment on before I > commit it. I'm doing more and more FreeBSD installs recently at various > client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of > those standard things you have to do if there's a firewall in place. > > Any one got any objection to mentioning that fact, with the included patch? I agree that this doesn't belong in make.conf. What does this modification do that FTP_PASSIVE_MODE in login.conf doesn't? Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 18: 6:40 2000 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 758BE37BBD1 for ; Sun, 20 Feb 2000 18:06:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA19350; Sun, 20 Feb 2000 18:06:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: naddy@mips.rhein-neckar.de (Christian Weisgerber) Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "21 Feb 2000 00:36:49 +0100." <88ptqh$264i$1@bigeye.rhein-neckar.de> Date: Sun, 20 Feb 2000 18:06:17 -0800 Message-ID: <19347.951098777@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 0. RSA situation > [ a very nice point-for-point analysis of the situation elided ] Christian, Thank you for this summary; it helps a lot to have all the relevant information presented in one place like this. Now we can begin cutting to the heart of this matter, which I'll do in the form of excerps from your own message with my own commentary attached. > - USA, non-commercial: must use RSAREF > - USA, commercial: no RSA > - international: free RSA And how to "get the appropriate RSA" (assuming you're not a U.S. commercial interest) in a what would be a sufficiently user-friendly fashion (that being something FreeBSD's known for) has sort of been point #1 in this little debate. Simply swapping one openssl library for another is, I think we can all agree, the wrong approach if openssl is to have any justification for being bundled with the system. If we're going to go with that level of packaging granularity then openssl belongs as a package and should not be part of the bindist, end of story (the RE draws his line in the sand there :-). That still leaves us with the option of contining to bundle openssl but making rsaref the switchable component so that this is all layered correctly. Looking at the needs of openssl, I see that the following list constitutes the important external references from the RSA glue code: RSAPrivateDecrypt RSAPrivateEncrypt RSAPublicDecrypt RSAPublicEncrypt R_GetRandomBytesNeeded R_RandomFinal R_RandomInit R_RandomUpdate It would obviously not be hard to write a set of stubs for these things, getting those stubs called selectively in the "no real RSA" case also not being very difficult. One way would be to put them in a lower version-numbered shared lib, like OpenBSD did it, so that the application would fall through to link against the stub version if librsaref.so.2 was not found. Another, better way, would be to use weak symbols and a dlopen(), e.g.: #pragma weak RSAPrivateEncrypt=_RSAPrivateEncrypt_stub .. _RSAPrivateEncrypt_stub(...) { if (lib = dlopen("librsaref.so", RTLD_LAZY)) if (sym = dlsym(lib, "RSAPrivateEncrypt")) return (*sym)(...); /* We've fallen through, emit the "go get RSA" message */ } That way it's not an error to link against the openssl library without librsa, though if you do link with -lrsa and -lssl then you can also skip the stubs entirely and not encur the dlopen() overhead, something which makes the -static (or stand-alone) linkers happy. I'm just annoyed enough by this that I may go and implement option #2 right now myself. I wrote up a little test version of this and it worked great, so how hard can 8 little symbols be? :-) Whether openssl is bundled or not, it seems a reasonable thing to try and do. > If we want to have OpenSSL in the base system, we necessarily will > need to use an approach similar to the OpenBSD one. > > I would like to point out that OpenBSD has made it a major advocacy > point that they ship with OpenSSL and OpenSSH out of the box, nicely And now we come to the second major point of this discussion: Just what the hell is openssl good for? In the OpenBSD case, this is a clear and easy question to answer: It's good right now for running openssh under OpenBSD and, as a heck of a lot of people use openssh, that's a clearly justifiable decision. In FreeBSD's case, however, the conservative approach has landed us in "no man's land", where openssl can neither be wholly justified or dismissed, and I think that's a fundamental issue which needs to be addressed. I've seen Kris's arguments about how integrating openssl is a useful first step, but that's not actually as strong an arguing position as it sounds. Just stepping back a bit, in fact, one can easily see a whole pile of incremental things which one could do to FreeBSD as good "first steps" towards some greater good but, in and of themselves, are kinda worthless in the short term. These are projects which you want to by all means encourage but not actually bring into FreeBSD until they've reached a minimal standard of functionality and usefulness to the population at large. To do otherwise quickly leads to a system which can be best characterized as a pile of dangling hacks-in-progress, driven more by engineering than user interests. I'm not totally inflexible about making the engineering vs user argument either, don't get me wrong, but this one is perilously in the middle and bringing something like openssh in as a companion to openssl would certainly raise my estimation of openssl as a 4.0 candidate. Yes, I'd even be willing to delay the release date for something like that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 18:35:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 8676F37B6BA for ; Sun, 20 Feb 2000 18:35:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id VAA00623; Sun, 20 Feb 2000 21:32:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002210232.VAA00623@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000220132637.I28660@strontium.scientia.demon.co.uk> Date: Sun, 20 Feb 2000 21:32:01 -0500 (EST) From: John Baldwin To: Ben Smithurst Subject: Re: make world Cc: freebsd-current@FreeBSD.org, Omachonu Ogali , =?iso-8859-1?Q?Kai_Gro=DFjohann?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Feb-00 Ben Smithurst wrote: > Kai Großjohann wrote: > >> Omachonu Ogali writes: >> >>> ===> lib/libcom_err/doc >>> install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: >>> (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir >>> install-info: unrecognized option `--defsection=Programming & development tools.' >>> Try `install-info --help' for a complete list of options. >> >> I did `make -k install-world', then `make installworld'. The first >> make will install the new install-info binary which has the new >> options, the second make will use that binary to install the info >> files. > > Isn't that overkill? I just did "cd > /usr/src/gnu/usr.bin/texinfo/install-info; make install" before a normal > "make installworld". It is a bit of overkill, but it's simpler to just type in one more command. :) And yes, your fixing step was necessary. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 19:45:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (law-f270.hotmail.com [209.185.130.186]) by hub.freebsd.org (Postfix) with SMTP id 2985A37BCE3 for ; Sun, 20 Feb 2000 19:45:35 -0800 (PST) (envelope-from k_snr@hotmail.com) Received: (qmail 4486 invoked by uid 0); 21 Feb 2000 03:45:34 -0000 Message-ID: <20000221034534.4485.qmail@hotmail.com> Received: from 146.163.194.96 by www.hotmail.com with HTTP; Sun, 20 Feb 2000 19:45:34 PST X-Originating-IP: [146.163.194.96] From: "sunny kiran" To: current@FreeBSD.ORG Subject: Re: current-digest V4 #815 Date: Mon, 21 Feb 2000 03:45:34 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 19:45:57 2000 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 7500937BC16 for ; Sun, 20 Feb 2000 19:45:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA61407 for ; Sun, 20 Feb 2000 19:45:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd-current@FreeBSD.ORG Subject: A potential fix [was Re: openssl in -current] In-reply-to: Your message of "Sun, 20 Feb 2000 18:06:17 PST." <19347.951098777@zippy.cdrom.com> Date: Sun, 20 Feb 2000 19:45:38 -0800 Message-ID: <61404.951104738@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I've dinked around with this some more and I think I might have at least a partial solution to this whole mess (it still doesn't make openssl actually useful to us, it just makes it less annoying :). First, apply the following patch: Index: Makefile =================================================================== RCS file: /home/ncvs/src/secure/lib/librsaglue/Makefile,v retrieving revision 1.1 diff -u -u -r1.1 Makefile --- Makefile 2000/01/20 07:24:40 1.1 +++ Makefile 2000/02/21 03:01:09 @@ -11,7 +11,7 @@ CFLAGS+= -I${.OBJDIR} # rsaref -SRCS+= rsar_err.c rsaref.c +SRCS+= rsar_err.c rsaref.c rsaref_stubs.c HDRS= asn1/asn1.h asn1/asn1_mac.h bio/bio.h bf/blowfish.h bn/bn.h \ buffer/buffer.h cast/cast.h comp/comp.h conf/conf.h crypto.h \ Then stick the code below in /usr/src/crypto/openssl/rsaref/rsaref_stubs.c and rebuild/install from /usr/src/secure/lib/librsaglue. If you then proceed to /usr/ports/security/openssh and make this change: Index: Makefile =================================================================== RCS file: /home/ncvs/ports/security/openssh/Makefile,v retrieving revision 1.45 diff -u -u -r1.45 Makefile --- Makefile 2000/02/16 04:52:59 1.45 +++ Makefile 2000/02/21 03:30:44 @@ -31,7 +31,7 @@ :pserver:anoncvs@anoncvs1.usa.openbsd.org:/cvs CRYPTOLIBS= -L${OPENSSLLIB} -lcrypto .if defined(OPENSSL_RSAREF) -CRYPTOLIBS+= -lRSAglue -L${LOCALBASE}/lib -lrsaref +CRYPTOLIBS+= -lRSAglue .endif # Here, MANDIR is concetenated to DESTDIR which all forms the man install dir... MAKE_ENV+= DESTDIR=${PREFIX} MANDIR=/man/man CRYPTOLIBS="${CRYPTOLIBS}" You'll create an ssh which either whines at you for having no librsaref.so or, if you do have one, will load and use it seamlessly. - Jordan /* * $FreeBSD$ * * Copyright (c) 2000 * Jordan Hubbard. All rights reserved. * * Stub functions for RSA code. If you link with this code, you will * get a full set of weak symbol references to the rsaref library * functions which are required by openssl. These can then be occluded * by the real rsaref library by implicitly linking with it or, failing * that, these stub functions will attempt to dlopen() the appropriate * rsaref library if it can be found in the library search path. * * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer, * verbatim and that no modifications are made prior to this * point in the file. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY JORDAN HUBBARD ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL JORDAN HUBBARD OR HIS PETS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, LIFE OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * */ #ifndef NO_RSA #include #include #define RSA_SHLIB "librsaref.so" /* be more exact if you need to */ #define VERBOSE_STUBS /* undef if you don't want missing rsaref reported */ static void * getsym(const char *sym) { static void *rsalib; static int whined; void *ret = NULL; if (!rsalib) rsalib = dlopen(RSA_SHLIB, RTLD_LAZY); if (rsalib) ret = dlsym(rsalib, sym); #ifdef VERBOSE_STUBS if (!ret && !whined) { fprintf(stderr, "** %s: Unable to find an rsaref shared library (%s).\n", sym, RSA_SHLIB); fprintf(stderr, "** Install an RSA package on your system and run this program again\n", RSA_SHLIB); whined = 1; } #endif return ret; } #pragma weak RSAPrivateDecrypt=RSAPrivateDecrypt_stub int RSAPrivateDecrypt_stub(unsigned char *output, unsigned int *outlen, unsigned char *input, int inputlen, void *RSAkey) { static int (*sym)(unsigned char *, unsigned int *, unsigned char *, int, void *); if (sym || (sym = getsym("RSAPrivateDecrypt"))) return sym(output, outlen, input, inputlen, RSAkey); return 0; } #pragma weak RSAPrivateEncrypt=RSAPrivateEncrypt_stub int RSAPrivateEncrypt_stub(unsigned char *output, unsigned int *outlen, unsigned char *input, int inputlen, void *RSAkey) { static int (*sym)(unsigned char *, unsigned int *, unsigned char *, int, void *); if (sym || (sym = getsym("RSAPrivateEncrypt"))) return sym(output, outlen, input, inputlen, RSAkey); return 0; } #pragma weak RSAPublicDecrypt=RSAPublicDecrypt_stub int RSAPublicDecrypt_stub(unsigned char *output, unsigned int *outlen, unsigned char *input, int inputlen, void *RSAkey) { static int (*sym)(unsigned char *, unsigned int *, unsigned char *, int, void *); if (sym || (sym = getsym("RSAPublicDecrypt"))) return sym(output, outlen, input, inputlen, RSAkey); return 0; } #pragma weak RSAPublicEncrypt=RSAPublicEncrypt_stub int RSAPublicEncrypt_stub(unsigned char *output, unsigned int *outlen, unsigned char *input, int inputlen, void *RSAkey, void *randomStruct) { static int (*sym)(unsigned char *, unsigned int *, unsigned char *, int, void *, void *); if (sym || (sym = getsym("RSAPublicEncrypt"))) return sym(output, outlen, input, inputlen, RSAkey, randomStruct); return 0; } #pragma weak R_GetRandomBytesNeeded=R_GetRandomBytesNeeded_stub int R_GetRandomBytesNeeded_stub(unsigned int *bytesNeeded, void *randomStruct) { static int (*sym)(unsigned int *, void *); if (sym || (sym = getsym("R_GetRandomBytesNeeded"))) return sym(bytesNeeded, randomStruct); return 0; } #pragma weak R_RandomFinal=R_RandomFinal_stub void R_RandomFinal_stub(void *randomStruct) { static void (*sym)(void *); if (sym || (sym = getsym("R_RandomFinal"))) sym(randomStruct); } #pragma weak R_RandomInit=R_RandomInit_stub int R_RandomInit_stub(void *randomStruct) { static int (*sym)(void *); if (sym || (sym = getsym("R_RandomInit"))) sym(randomStruct); } #pragma weak R_RandomUpdate=R_RandomUpdate_stub int R_RandomUpdate_stub(void *randomStruct, unsigned char *block, unsigned int blockLen) { static int (*sym)(void *, unsigned char *, unsigned int); if (sym || (sym = getsym("R_RandomUpdate"))) sym(randomStruct, block, blockLen); } #endif /* NO_RSA */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 19:57:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 0339837BFE7; Sun, 20 Feb 2000 19:57:39 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id MAA16555; Mon, 21 Feb 2000 12:57:36 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id MAA25869; Mon, 21 Feb 2000 12:57:35 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA10752; Mon, 21 Feb 2000 12:57:34 +0900 (JST) To: ache@freebsd.org Cc: saxonww@ufl.edu, current@freebsd.org Subject: Re: EPSV patch for review (was Re: Broken FTP) In-Reply-To: <20000220152605.A59931@freebsd.org> References: <20000220135605.A38025@freebsd.org> <20000220150126.A54323@freebsd.org> <20000220152605.A59931@freebsd.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000221125825S.shin@nd.net.fujitsu.co.jp> Date: Mon, 21 Feb 2000 12:58:25 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please review this patch. It fix all problems I mention. Thanks, as far as I reviewed and actually confirmed, your patches solved every problem. :-) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 20: 8:33 2000 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 C364437C005 for ; Sun, 20 Feb 2000 20:08:26 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA24671 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 05:08:21 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 944FC87AE; Mon, 21 Feb 2000 01:17:26 +0100 (CET) Date: Mon, 21 Feb 2000 01:17:26 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: IPv6 scoped addr format change Message-ID: <20000221011726.A88148@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <20000219182126A.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000219182126A.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Feb 19, 2000 at 06:21:26PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Yoshinobu Inoue: > So now I think of following things. > > -Adopt the format below now, and never change it again > before 4.0 release. > > addr%scope We're getting close to the release so I'd go that way. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 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 Feb 20 20:14:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 0CFF137BC16 for ; Sun, 20 Feb 2000 20:14:46 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115230>; Mon, 21 Feb 2000 15:15:30 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: openssl in -current In-reply-to: <19347.951098777@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Mon, Feb 21, 2000 at 01:09:21PM +1100 To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Feb21.151530est.115230@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <88ptqh$264i$1@bigeye.rhein-neckar.de> <19347.951098777@zippy.cdrom.com> Date: Mon, 21 Feb 2000 15:15:29 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Feb-21 13:09:21 +1100, "Jordan K. Hubbard" wrote: > Simply swapping one openssl library for another ... > If we're going to go with that level of packaging granularity >then openssl belongs as a package and should not be part of the >bindist, end of story This sounds awfully like the way the crypt libraries were (and maybe still are) handled: Depending on how you answer the DES question, you wind up with libdescrypt or libscrypt (and a symlink from libcrypt). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 20:48:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id B309437BFCD for ; Sun, 20 Feb 2000 20:48:06 -0800 (PST) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id XAA06095 for current@freebsd.org; Sun, 20 Feb 2000 23:48:01 -0500 (EST) (envelope-from ray) Date: Sun, 20 Feb 2000 23:48:01 -0500 From: Ray Kohler To: current@freebsd.org Subject: /sys/i386/machdep.c breaks kernel build Message-ID: <20000220234801.A4251@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest commit of /sys/i386/i386/machdep.c breaks the kernel build: cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/machdep.c {standard input}: Assembler messages: {standard input}:2772: Error: operands given don't match any known 386 instruction *** Error code 1 Stop in /usr/src/sys/compile/RJK191. -- Ray Kohler "No, `Eureka' is Greek for `This bath is too hot.'" -- Dr. Who To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 20:59:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 5D84F37BF0B; Sun, 20 Feb 2000 20:59:10 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id UAA57679; Sun, 20 Feb 2000 20:59:05 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002210459.UAA57679@gndrsh.dnsmgr.net> Subject: Re: openssl in -current In-Reply-To: <42144.951019612@zippy.cdrom.com> from "Jordan K. Hubbard" at "Feb 19, 2000 08:06:52 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 20 Feb 2000 20:59:04 -0800 (PST) Cc: kris@FreeBSD.ORG (Kris Kennaway), salaman@teknos.com (Victor Salaman), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out > at this point. The situation with RSA makes this far more problematic > than I think anyone first thought, and I've seen a lot of breakage so > far for what appears to be comparatively little gain over what we had > before with the ports collection version. I'll ack that: ACK ACK ACK!! -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 21: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 8AC1237C11B for ; Sun, 20 Feb 2000 21:00:47 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id OAA07565; Mon, 21 Feb 2000 14:00:43 +0900 (JST) Date: Mon, 21 Feb 2000 14:00:42 +0900 Message-ID: <14512.50810.382596.26482Z@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: rjk191@psu.edu Cc: current@freebsd.org Subject: Re: /sys/i386/machdep.c breaks kernel build In-Reply-To: In your message of "Sun, 20 Feb 2000 23:48:01 -0500" <20000220234801.A4251@rjk191.rh.psu.edu> References: <20000220234801.A4251@rjk191.rh.psu.edu> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: multipart/mixed; boundary="Multipart_Mon_Feb_21_14:00:42_2000-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Mon_Feb_21_14:00:42_2000-1 Content-Type: text/plain; charset=US-ASCII On Sun, 20 Feb 2000 23:48:01 -0500, Ray Kohler said: Ray> cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls Ray> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes Ray> -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi Ray> -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include Ray> opt_global.h -elf -mpreferred-stack-boundary=2 Ray> ../../i386/i386/machdep.c Ray> {standard input}: Assembler messages: Ray> {standard input}:2772: Error: operands given don't match any known Ray> 386 instruction Ray> *** Error code 1 Could you try the following patch(sent to bsd personally)? It prevents movl between a debug register and memory. --Multipart_Mon_Feb_21_14:00:42_2000-1 Content-Type: text/plain; type=patch; charset=US-ASCII Content-Disposition: attachment; filename="cpufunc.h.diff" Content-Transfer-Encoding: 7bit Index: cpufunc.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/cpufunc.h,v retrieving revision 1.95 diff -u -r1.95 cpufunc.h --- cpufunc.h 2000/02/20 20:51:22 1.95 +++ cpufunc.h 2000/02/21 03:44:30 @@ -456,7 +456,7 @@ rdr0(void) { u_int data; - __asm __volatile("movl %%dr0,%0" : "=rm" (data)); + __asm __volatile("movl %%dr0,%0" : "=r" (data)); return (data); } @@ -464,7 +464,7 @@ rdr1(void) { u_int data; - __asm __volatile("movl %%dr1,%0" : "=rm" (data)); + __asm __volatile("movl %%dr1,%0" : "=r" (data)); return (data); } @@ -472,7 +472,7 @@ rdr2(void) { u_int data; - __asm __volatile("movl %%dr2,%0" : "=rm" (data)); + __asm __volatile("movl %%dr2,%0" : "=r" (data)); return (data); } @@ -480,7 +480,7 @@ rdr3(void) { u_int data; - __asm __volatile("movl %%dr3,%0" : "=rm" (data)); + __asm __volatile("movl %%dr3,%0" : "=r" (data)); return (data); } @@ -488,7 +488,7 @@ rdr6(void) { u_int data; - __asm __volatile("movl %%dr6,%0" : "=rm" (data)); + __asm __volatile("movl %%dr6,%0" : "=r" (data)); return (data); } @@ -496,7 +496,7 @@ rdr7(void) { u_int data; - __asm __volatile("movl %%dr7,%0" : "=rm" (data)); + __asm __volatile("movl %%dr7,%0" : "=r" (data)); return (data); } --Multipart_Mon_Feb_21_14:00:42_2000-1 Content-Type: text/plain; charset=US-ASCII -- Seigo Tanimura --Multipart_Mon_Feb_21_14:00:42_2000-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 21:55:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 639A437BA8C; Sun, 20 Feb 2000 21:55:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA07143; Sun, 20 Feb 2000 21:55:22 -0800 (PST) (envelope-from dillon) Date: Sun, 20 Feb 2000 21:55:22 -0800 (PST) From: Matthew Dillon Message-Id: <200002210555.VAA07143@apollo.backplane.com> To: Will Andrews Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 References: <20000220133512.I14682@dragon.nuxi.com> <14945.951083250@zippy.cdrom.com> <20000220170646.J44834@shadow.blackdawn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote: :> P.S. /usr/local/etc/shells anyone? :) : :I second this. As there becomes more ports around, this would simplify :the job of ports since we would now modify a ${PREFIX}-based file :instead of /etc/shells. : :-- :Will Andrews :GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- :?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ :G++>+++ e->++++ h! r-->+++ y? I would be opposed to this for security reasons. The last thing I want to see are /usr/local versions of /etc/ files related to security. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 22: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 4B92737C0AD for ; Sun, 20 Feb 2000 22:01:17 -0800 (PST) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id BAA00236; Mon, 21 Feb 2000 01:01:02 -0500 (EST) (envelope-from ray) Date: Mon, 21 Feb 2000 01:01:02 -0500 From: Ray Kohler To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: /sys/i386/machdep.c breaks kernel build Message-ID: <20000221010102.A203@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu References: <20000220234801.A4251@rjk191.rh.psu.edu> <14512.50810.382596.26482Z@rina.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14512.50810.382596.26482Z@rina.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Mon, Feb 21, 2000 at 02:00:42PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 02:00:42PM +0900, Seigo Tanimura wrote: > On Sun, 20 Feb 2000 23:48:01 -0500, > Ray Kohler said: > > Ray> cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls > Ray> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > Ray> -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi > Ray> -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include > Ray> opt_global.h -elf -mpreferred-stack-boundary=2 > Ray> ../../i386/i386/machdep.c > Ray> {standard input}: Assembler messages: > Ray> {standard input}:2772: Error: operands given don't match any known > Ray> 386 instruction > Ray> *** Error code 1 > > > Could you try the following patch(sent to bsd personally)? It prevents > movl between a debug register and memory. > This patch fixed it. Compiles fine, runs fine. Thanks! -- Ray Kohler May the Fleas of a Thousand Camels infest one of your Erogenous Zones. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 22:28:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id F202937BA8C for ; Sun, 20 Feb 2000 22:28:52 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.32.254]) by piranha.amis.net (Postfix) with ESMTP id B336D5D41; Mon, 21 Feb 2000 07:28:48 +0100 (CET) Date: Mon, 21 Feb 2000 07:28:47 +0100 (CET) From: Blaz Zupan To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <19347.951098777@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 > In FreeBSD's case, however, the conservative approach has landed us in > "no man's land", where openssl can neither be wholly justified or > dismissed, and I think that's a fundamental issue which needs to be > addressed. I've seen Kris's arguments about how integrating openssl > is a useful first step, but that's not actually as strong an arguing > position as it sounds. Just stepping back a bit, in fact, one can I wholly agree. I would just like to remind everybody of the TCL fiasco. If I remember correctly, TCL was also imported on the grounds of "we will need this later" and it caused a whole lot of problems because the software that was supposed to use it never appeared in the tree. I'd say, back it out until we really need it in there. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 22:30:31 2000 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 B4CD737C170 for ; Sun, 20 Feb 2000 22:30:26 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA91652; Sun, 20 Feb 2000 23:30:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA18154; Sun, 20 Feb 2000 23:30:12 -0700 (MST) Message-Id: <200002210630.XAA18154@harmony.village.org> To: tbuswell@acadia.net Subject: Re: pccardd and mapping memory descriptors Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Feb 2000 12:16:09 EST." <14509.31140.445498.751403@localhost.bogus.net> References: <14509.31140.445498.751403@localhost.bogus.net> Date: Sun, 20 Feb 2000 23:30:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14509.31140.445498.751403@localhost.bogus.net> tbuswell@acadia.net writes: : I believe setting MEM_ASSIGNED is the proper fix and attached is the : one line patch. This looks goo.d : PS: anybody know why cardaddr is set to 16k? No. I have no clue.... Maybe a kludge left over from an old card? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 22:37:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from m2.cs.berkeley.edu (m2.CS.Berkeley.EDU [128.32.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 8361137C15A for ; Sun, 20 Feb 2000 22:37:12 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca1-68.ix.netcom.com [209.109.232.68]) by m2.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id WAA47024 for ; Sun, 20 Feb 2000 22:37:06 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id WAA14297; Sun, 20 Feb 2000 22:37:02 -0800 (PST) (envelope-from asami) To: current@freebsd.org Subject: Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS References: <20000220091540.A2628@catkin.nothing-going-on.org> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 20 Feb 2000 22:37:00 -0800 In-Reply-To: Nik Clayton's message of "Sun, 20 Feb 2000 09:15:41 +0000" Message-ID: Lines: 28 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Nik Clayton * [ Sent to -current and -ports, followups set to -current ] (Your Followups-to: didn't survive someone's MTA, so replying to -current manually.) * Here's another trivial patch that people might like to comment on before I * commit it. I'm doing more and more FreeBSD installs recently at various * client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of * those standard things you have to do if there's a firewall in place. * * Any one got any objection to mentioning that fact, with the included patch? /etc/make.conf is not the right place to add it. (Besides, FETCH_BEFORE_ARGS wasn't supposed to be used for site-specific defaults -- this will kill ports that set FETCH_BEFORE_ARGS in their Makefile.) Jordan already fixed this is /etc/login.conf on 1999/5/28. === revision 1.31 date: 1999/05/28 11:07:16; author: jkh; state: Exp; lines: +2 -2 Set FTP_PASSIVE_MODE=YES by default in the default login class. === Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 23: 0:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 1E39237C18C for ; Sun, 20 Feb 2000 23:00:14 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 20949 invoked from network); 21 Feb 2000 07:00:10 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 21 Feb 2000 07:00:10 -0000 Date: Mon, 21 Feb 2000 18:00:07 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: David O'Brien Cc: Matthew Dillon , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 In-Reply-To: <20000220133512.I14682@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > The /compat symlink should just die. compat bits should not be on the > root partition, so why are we pretending? /usr/compat should be the only > supported place. Peroid. /compat is often a symlink or mount point, and "/" is a better place for such things than /usr. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 23:10:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 97CE437C31E; Sun, 20 Feb 2000 23:10:34 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA21984; Mon, 21 Feb 2000 18:14:26 +1100 Date: Mon, 21 Feb 2000 18:10:28 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "David O'Brien" Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: break in libcrypto? In-Reply-To: <20000220143745.A15548@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > On Sun, Feb 20, 2000 at 02:14:21PM -0800, Kris Kennaway wrote: > > stand by my comment that 'make depend' is needed generally, though - > > things often fail elsewhere in the tree (e.g. gcc, perl) Only in broken makefiles. I once fixed all makefiles used by makeworld to work with `make -jLarge' without `make depend' in the NOSECURE case. makeworld used to depend on this (at least in the -jLarge case) until recent pessimisations in it (building dependencies slows it down by 10%). > Yes, give a log. Look at all the gunk in > src/gnu/usr.bin/cc/cc_tools/Makefile to keep a `make depend' from being > required. cc_tools/Makefile too the most work to fix :-). Most of the gunk is required to make dependencies actually work. Once you have correct dependencies (less the ones generated by `make depend'), it is a small step to make the `make depend' step optional. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 23:14: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0A1BE37BBD1; Sun, 20 Feb 2000 23:14:05 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA90110; Sun, 20 Feb 2000 23:14:04 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 23:14:04 -0800 (PST) From: Kris Kennaway To: "Jeffrey J. Mountin" Cc: current@FreeBSD.ORG Subject: RE: openssl in -current In-Reply-To: <3.0.3.32.20000220170538.009084b0@207.227.119.2> Message-ID: 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, 20 Feb 2000, Jeffrey J. Mountin wrote: > Considering that building and installing world takes quite a while, it > would be nice to have a simple way, so wonder if a simple 'make all > install' in secure/usr.bin/openssl will do it for everything that depends > on openssl. Chapter 6.5 of the handbook implies that a make world is > needed. Doesn't bother me (much), but might be considered cruel and > unusual punishment to those not familiar with building. Perhaps you should read it again, and tell me which part caused you the confusion so I can correct it :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 23:56:24 2000 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 52AFB37C188 for ; Sun, 20 Feb 2000 23:56:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p08-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.137]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA29088; Mon, 21 Feb 2000 16:56:07 +0900 (JST) Message-ID: <38B0D9EF.92450B92@newsguy.com> Date: Mon, 21 Feb 2000 15:23:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> <3.0.3.32.20000220170538.009084b0@207.227.119.2> <88pvgb$26o5$1@bigeye.rhein-neckar.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > > binary installation: > - before: user needs to install openssl port > - now: user needs to install openssl package Where is the openssl package, and what it is called? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 20 23:58:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 223FE37BB7F for ; Sun, 20 Feb 2000 23:58:17 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id UAA61844; Mon, 21 Feb 2000 20:58:02 +1300 (NZDT) Message-Id: <200002210758.UAA61844@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: "Daniel C. Sobral" Date: Mon, 21 Feb 2000 20:57:59 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: openssl in -current Reply-To: dan@freebsddiary.org Cc: freebsd-current@FreeBSD.ORG In-reply-to: <38B0D9EF.92450B92@newsguy.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Feb 00, at 15:23, Daniel C. Sobral wrote: > Christian Weisgerber wrote: > > > > binary installation: > > - before: user needs to install openssl port > > - now: user needs to install openssl package > > Where is the openssl package, and what it is called? security/openssl -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/ unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0: 1:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id DF47037BBEF for ; Mon, 21 Feb 2000 00:01:49 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id VAA61893; Mon, 21 Feb 2000 21:01:24 +1300 (NZDT) Message-Id: <200002210801.VAA61893@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: "Daniel C. Sobral" Date: Mon, 21 Feb 2000 21:01:23 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: openssl in -current Reply-To: dan@freebsddiary.org Cc: freebsd-current@FreeBSD.ORG In-reply-to: <200002210758.UAA61844@ducky.nz.freebsd.org> References: <38B0D9EF.92450B92@newsguy.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Feb 00, at 20:57, Dan Langille wrote: > On 21 Feb 00, at 15:23, Daniel C. Sobral wrote: > > > Christian Weisgerber wrote: > > > > > > binary installation: > > > - before: user needs to install openssl port > > > - now: user needs to install openssl package > > > > Where is the openssl package, and what it is called? > > security/openssl I must stop responding when I'm sleep deprived. -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/ unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0: 8:49 2000 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 34EBD37C1D2 for ; Mon, 21 Feb 2000 00:08:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA91984; Mon, 21 Feb 2000 01:08:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19264; Mon, 21 Feb 2000 01:08:31 -0700 (MST) Message-Id: <200002210808.BAA19264@harmony.village.org> To: Anatoly Vorobey Subject: Re: feedback on CD install of 4.0-RC2 Cc: "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Feb 2000 18:34:21 GMT." <20000218183421.A2896@happy.checkpoint.com> References: <20000218183421.A2896@happy.checkpoint.com> <7327.950809955@zippy.cdrom.com> <38ACD908.E756C802@gorean.org> <38AD571D.C5B53079@newsguy.com> Date: Mon, 21 Feb 2000 01:08:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000218183421.A2896@happy.checkpoint.com> Anatoly Vorobey writes: : I'm actually scared by "novice" because it would be inflicting on me : defaults I would almost probably not want. I never run anything but : "custom", and I suspect many people do the same. I'm much too impatient to run anything but express. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:13: 2 2000 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 EFFCA37C1C4; Mon, 21 Feb 2000 00:12:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92004; Mon, 21 Feb 2000 01:12:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19301; Mon, 21 Feb 2000 01:12:43 -0700 (MST) Message-Id: <200002210812.BAA19301@harmony.village.org> To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Subject: Re: feedback on CD install of 4.0-RC2 Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "18 Feb 2000 23:09:16 +0100." References: <79206.950898990@zippy.cdrom.com> Date: Mon, 21 Feb 2000 01:12:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kai=?iso-8859-1?q?_Gro=DFjohann?= writes: : Does this mean that this option should be called `guided'? I know a : little bit about Unix but haven't installed FreeBSD more than five : times or so. And I always thought that the novice install meant that : I didn't get as many choices... "The FreeBSD Installation Wizard" is what you are trying to say... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:15:41 2000 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 9E61737C1FD for ; Mon, 21 Feb 2000 00:15:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92023; Mon, 21 Feb 2000 01:15:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19338; Mon, 21 Feb 2000 01:15:25 -0700 (MST) Message-Id: <200002210815.BAA19338@harmony.village.org> To: Kelvin Farmer Subject: Re: 4.0(current) on a 486SLC2 ? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Feb 2000 22:24:14 EST." <38AE0CDE.2339FD8A@sympatico.ca> References: <38AE0CDE.2339FD8A@sympatico.ca> Date: Mon, 21 Feb 2000 01:15:25 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38AE0CDE.2339FD8A@sympatico.ca> Kelvin Farmer writes: : I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. The village ran its dialin server on this machine using 2.2.5R (and later points on the 2.2.x stable branch) for years w/o problems. If there is a problem, it likely isn't a cpu issue. Oh wait, we had a math co as well... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:17: 9 2000 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 218B737BBEF for ; Mon, 21 Feb 2000 00:17:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92035; Mon, 21 Feb 2000 01:17:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19365; Mon, 21 Feb 2000 01:16:49 -0700 (MST) Message-Id: <200002210816.BAA19365@harmony.village.org> To: R Joseph Wright Subject: Re: devices under 4.0 Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Feb 2000 21:50:49 PST." References: Date: Mon, 21 Feb 2000 01:16:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message R Joseph Wright writes: : I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would : like to know how to change over the devices. I created the new devices : by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running : it, but it didn't create any ata* devices such as is shown in the kernel : config file. : It did make devices ada1, ada2, ada3, and ada4, which would correspond to : the four slices on my disk, but if there are no freebsd partitions shown, : such as ada4a, etc. From src/UPDATING: To rebuild disk /dev entries ---------------------------- MAKEDEV should be copied from src/etc/MAKEDEV to /dev before starting the following: For N in the list of disks MAKEDEV N # eg ad0 for M in the list of slices MAKEDEV NsMa # eg ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:28:51 2000 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 8342837C1DC; Mon, 21 Feb 2000 00:28:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92095; Mon, 21 Feb 2000 01:28:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19494; Mon, 21 Feb 2000 01:28:34 -0700 (MST) Message-Id: <200002210828.BAA19494@harmony.village.org> To: Kris Kennaway Subject: Re: openssl in -current Cc: "Jordan K. Hubbard" , Victor Salaman , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 19 Feb 2000 20:40:39 PST." References: Date: Mon, 21 Feb 2000 01:28:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One thing to keep in mind is that on Sept 8, 2000 the patent for RSA expires and this whole mess goes away. Or at least devolves into the usual crypto export mess rather than the crypto export plus rsa patent law plus rsaref license jumping. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:35:53 2000 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 C60E437C174; Mon, 21 Feb 2000 00:35:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92122; Mon, 21 Feb 2000 01:35:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19537; Mon, 21 Feb 2000 01:35:35 -0700 (MST) Message-Id: <200002210835.BAA19537@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: openssl in -current Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 20 Feb 2000 13:22:15 PST." <20000220132215.F14682@dragon.nuxi.com> References: <20000220132215.F14682@dragon.nuxi.com> <38AF5F59.A0BEC49@gorean.org> Date: Mon, 21 Feb 2000 01:35:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000220132215.F14682@dragon.nuxi.com> "David O'Brien" writes: : Which OpenBSD has done -- so why was it so easy for them? They have the : *same* rules to live by that we have -- even though they are Canadian, : the rsaref libs came from USA, thus they cannot be exported from Canada. No. The RSA that they have does NOT come from rsaref. The default tree that one gets with OpenBSD doesn't have ANY RSA AT ALL. ONE MUST JUST THROUGH UGLY HOOPS TO GET IT. I know. I've just jumped through those hoops for my OpenBSD/arc machine. Otherwise ssh, et al, say something to the effect that this software used rsa functionality and this version of OpenSSL wasn't compiled for it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:38:47 2000 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 232BB37C1B6; Mon, 21 Feb 2000 00:38:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92138; Mon, 21 Feb 2000 01:38:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19577; Mon, 21 Feb 2000 01:38:29 -0700 (MST) Message-Id: <200002210838.BAA19577@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: openssl in -current Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 20 Feb 2000 13:26:47 PST." <20000220132647.H14682@dragon.nuxi.com> References: <20000220132647.H14682@dragon.nuxi.com> <42333.951021282@zippy.cdrom.com> Date: Mon, 21 Feb 2000 01:38:29 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000220132647.H14682@dragon.nuxi.com> "David O'Brien" writes: : On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote: : > : > 1. They're in Canada : : What does that buy them? They have the same restrictions on rsaref since : it originated from the USA. They don't use rsaref. : > 2. What they do appears to be kind of icky, e.g. it requires more : > "hand work" than I think the average FreeBSD user would be willing : > to accept : : By handwork you man building, or installing? When I put OpenBSD 2.6 on : my sparc5, I did a normal install and then ftp'ed down the proper : ssl-base package. Then a simple pkg_add. Since OpenBSD does not have : our ``pkg_add -r'' functionalitiy, it wasn't as simple as we could make : it. First make build will erase that, at least that's what it appears to me. When I built OpenBSD/arc I had to create special extra bits in my tree before I could build an un castrated ssh. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:45: 6 2000 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 1F81A37C1B6 for ; Mon, 21 Feb 2000 00:45:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA92170; Mon, 21 Feb 2000 01:45:00 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA19639; Mon, 21 Feb 2000 01:44:48 -0700 (MST) Message-Id: <200002210844.BAA19639@harmony.village.org> To: Sheldon Hearn Subject: Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 21 Feb 2000 01:12:53 +0200." <490.951088373@axl.noc.iafrica.com> References: <490.951088373@axl.noc.iafrica.com> Date: Mon, 21 Feb 2000 01:44:48 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use the following: FETCH_CMD=runsocks ftp -p in my /etc/make.conf. Too bad ftp and fetch don't have compatible command lines. I sometimes have to add: FETCH_BEFORE_ARGS= FETCH_AFTER_ARGS= to the command line when ports are silly enough to assume too much about the fetch command. This lets me run ports from behind my socks firewall w/o doing anything special... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:53: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4AF0B37BB1C; Mon, 21 Feb 2000 00:53:01 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12MoZr-000BqY-00; Mon, 21 Feb 2000 10:52:23 +0200 From: Sheldon Hearn To: Matthew Dillon Cc: Will Andrews , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 In-reply-to: Your message of "Sun, 20 Feb 2000 21:55:22 PST." <200002210555.VAA07143@apollo.backplane.com> Date: Mon, 21 Feb 2000 10:52:22 +0200 Message-ID: <45529.951123142@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000 21:55:22 PST, Matthew Dillon wrote: > :As there becomes more ports around, this would simplify the job of > :ports since we would now modify a ${PREFIX}-based file instead of > :/etc/shells. > I would be opposed to this for security reasons. The last thing I > want to see are /usr/local versions of /etc/ files related to security. Could you explain _why_? Is this just a matter of taste, or is there a concrete security concern in play? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 0:56: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4AC6037BEB8 for ; Mon, 21 Feb 2000 00:56:04 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12ModD-000DXi-00; Mon, 21 Feb 2000 10:55:51 +0200 From: Sheldon Hearn To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: devices under 4.0 In-reply-to: Your message of "Mon, 21 Feb 2000 01:16:49 MST." <200002210816.BAA19365@harmony.village.org> Date: Mon, 21 Feb 2000 10:55:51 +0200 Message-ID: <52059.951123351@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Feb 2000 01:16:49 MST, Warner Losh wrote: > MAKEDEV should be copied from src/etc/MAKEDEV to /dev before > starting the following: > > For N in the list of disks > MAKEDEV N # eg ad0 > for M in the list of slices > MAKEDEV NsMa # eg ad0s1a Why do we have to make slices ourselves? When this one bites you, it tears out quite a chunk. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1: 0:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 3382137BF59 for ; Mon, 21 Feb 2000 01:00:35 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id KAA12213 for current@FreeBSD.ORG; Mon, 21 Feb 2000 10:00:22 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id GAA18433 for current@FreeBSD.ORG; Mon, 21 Feb 2000 06:54:26 +0100 (CET) (envelope-from andreas) Date: Mon, 21 Feb 2000 06:54:26 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: ATAPI Problem on LAPTOP, resource_list_alloc: resource_entry busy Message-ID: <20000221065426.A1591@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, created a FreeBSD 4.0 SNAP yesterday. Made the experience, that 4.0 can't be booted on my Laptop. Unfortunately the reboot takes in effect after a very short time, too short to write down more lines from the kernel .... Could we perhaps raise the reboot time by default to something like 60 seconds ? Or that you have to hit return ? For an installation kernel this would be a good idea I think ... Hitting Pause didn't help. What informations do you need about the hardware ? I have win95 installed on the machine as well, so I could try to get some hardware info from there ... or wait until I have 3.x installed again. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:31:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3EA5A37BC0B; Mon, 21 Feb 2000 01:31:29 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA98703; Mon, 21 Feb 2000 01:31:28 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 21 Feb 2000 01:31:28 -0800 (PST) From: Kris Kennaway To: "Daniel C. Sobral" Cc: Christian Weisgerber , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <38B0D9EF.92450B92@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Feb 2000, Daniel C. Sobral wrote: > Christian Weisgerber wrote: > > > > binary installation: > > - before: user needs to install openssl port > > - now: user needs to install openssl package > > Where is the openssl package, and what it is called? http://www.freebsd.org/~kris/openssl/ However.. with Jordan's help I'm working on a solution to all of the current kerfuffle, so please stay tuned. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:37: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 9596E37BEEC for ; Mon, 21 Feb 2000 01:36:51 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup4-49.iptelecom.net.ua [212.9.226.241]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA21518 for ; Mon, 21 Feb 2000 11:38:54 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id LAA11246 for ; Mon, 21 Feb 2000 11:35:18 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38B106D0.B416F877@altavista.net> Date: Mon, 21 Feb 2000 11:35:13 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: gcc code generation bug (optimisation related) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When I'm trying to compile kernel from just cvsup'ed sources on system builded/installed last evening I have following error message. This problem could be solved by lowering optimisation to -O, but previously I have no problems with -O2 for kernels. cc -c -O2 -march=pentium -Wall -Wredundant-decls -Wnested-externs -Wstrict-proto types -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-exten sions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include op t_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/machdep.c /tmp/ccfL2694.s: Assembler messages: /tmp/ccfL2694.s:3563: Error: operands given don't match any known 386 instruction *** Error code 1 Following is the assembler code in question: .L659: movl %ecx,%eax jmp .L658 .p2align 2,0x90 .L643: testb $1,%bl je .L644 #APP movl %dr0,-16(%ebp) <-------Line 3563 is here #NO_APP movl $1,%ecx .L644: testb $2,%bl je .L646 #APP movl %dr1,%edx #NO_APP leal -16(%ebp),%eax movl %edx,(%eax,%ecx,4) incl %ecx -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:47: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3B4E837BD0F for ; Mon, 21 Feb 2000 01:47:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA95742; Mon, 21 Feb 2000 10:46:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002210946.KAA95742@freebsd.dk> Subject: Re: quickie atapi dvd question In-Reply-To: from Jonathan Smith at "Feb 20, 2000 03:51:59 pm" To: jonsmith@dragonstar.dhs.org (Jonathan Smith) Date: Mon, 21 Feb 2000 10:46:57 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Jonathan Smith wrote: > Is it a general problem that audio CD's fail to play in a dvd drive (or > cd drive, for that matter ;) via cdcontrol as of the past few days and/or > dvd's not being accessed properly, ie. with DeCSS? Cdcontrol would not > eject, but would close until the buildworld that I just did. Now it will > sometimes eject. On the other hand, I did try mounting a data CD and use > it with no trouble. Hmm, I have seen no such problems here, even on my crappy Creative DVD-ROM drive. Beware that if you have touched the drive with the DVD tools, it _might_ be in a wierd state until the next power down/up. -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 Feb 21 1:49: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from m3.cs.berkeley.edu (m3.CS.Berkeley.EDU [128.32.45.179]) by hub.freebsd.org (Postfix) with ESMTP id 4E73637B960; Mon, 21 Feb 2000 01:49:05 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-68.ix.netcom.com [209.109.232.68]) by m3.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id BAA52787; Mon, 21 Feb 2000 01:49:02 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id BAA84274; Mon, 21 Feb 2000 01:48:57 -0800 (PST) To: Will Andrews Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 References: <20000220133512.I14682@dragon.nuxi.com> <14945.951083250@zippy.cdrom.com> <20000220170646.J44834@shadow.blackdawn.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 21 Feb 2000 01:48:53 -0800 In-Reply-To: Will Andrews's message of "Sun, 20 Feb 2000 17:06:46 -0500" Message-ID: Lines: 19 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Will Andrews * On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote: * > P.S. /usr/local/etc/shells anyone? :) And how exactly are you going to tell /usr/bin/login, /usr/bin/chpass, /usr/local/bin/wu-ftpd, etc., where to find that file? Remember, if it's ports that read the setup file, it can be moved around anywhere by changing PREFIX -- but for files that are read by the system, it is just not passible. That's why shells is in /etc and sudoers is in /usr/local/etc. * I second this. As there becomes more ports around, this would simplify * the job of ports since we would now modify a ${PREFIX}-based file * instead of /etc/shells. Um, how will it make it easier for ports? ;) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:50:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from gruft.de (gate.obh.snafu.de [195.21.6.17]) by hub.freebsd.org (Postfix) with ESMTP id 1347737BCAD for ; Mon, 21 Feb 2000 01:50:31 -0800 (PST) (envelope-from uucp@gruft.de) Received: from localhost (1807 bytes) by gruft.de via rmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Mon, 21 Feb 2000 10:50:09 +0100 (CET) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-May-21) Received: from sauerbruch.evk-koeln.de(localhost.evk-koeln.de[127.0.0.1]) (1411 bytes) by sauerbruch.evk-koeln.de via sendmail with P:esmtp/R:smart_host/T:uux (sender: ) id for ; Mon, 21 Feb 2000 10:46:50 +0100 (CET) (Smail-3.2.0.107 1999-Sep-8 #1 built 2000-Jan-25) Message-Id: Date: Mon, 21 Feb 2000 10:46:46 +0100 (CET) From: Oliver Brandmueller Subject: Re: Installing linux_base 6.1 To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <45529.951123142@axl.noc.iafrica.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On 21 Feb, Sheldon Hearn wrote: >> I would be opposed to this for security reasons. The last thing I >> want to see are /usr/local versions of /etc/ files related to security. > > Could you explain _why_? Is this just a matter of taste, or is there a > concrete security concern in play? Securing one directory is much simpler, than securing two directories. And making /etc secure in times when you sometimes simply don't want users fetch a userlist from your password file is hard enough. I wouldn't like to deal with two directories in that matter. Having /etc mounted read-only can be OK in many cases, but also mount /usr/local/etc read-only would make life much more difficult as you have to remount it read-write for most simple add-on-software or for fiddling in your local configuration. So I agree not to have security related files in /usr/local. Bye, Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:51:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from m3.cs.berkeley.edu (m3.CS.Berkeley.EDU [128.32.45.179]) by hub.freebsd.org (Postfix) with ESMTP id B1E8C37BEEB; Mon, 21 Feb 2000 01:51:52 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-68.ix.netcom.com [209.109.232.68]) by m3.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id BAA52895; Mon, 21 Feb 2000 01:51:50 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id BAA84287; Mon, 21 Feb 2000 01:51:46 -0800 (PST) To: "Jordan K. Hubbard" Cc: Kris Kennaway , Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current References: <94717.951038390@zippy.cdrom.com> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 21 Feb 2000 01:51:42 -0800 In-Reply-To: "Jordan K. Hubbard"'s message of "Sun, 20 Feb 2000 01:19:50 -0800" Message-ID: Lines: 15 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * This is just wrong. If I go to build openssh then I expect it to DTRT * with openssl whether or not openssl depends on RSA, I don't expect to * go have to install a package manually and then continue with my build. In case you can't get that weak symbol thing to work -- why don't you (Kris) create another port that just fetches and installs your package, and add some glue (to bsd.port.mk I guess) to make rsaref-requiring ports depend on it. That way at least the port-builders will have their entire chain of build done by port dependencies only. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 1:52:52 2000 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 B84B637B960; Mon, 21 Feb 2000 01:52:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA88643; Mon, 21 Feb 2000 01:52:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: Will Andrews , obrien@FreeBSD.ORG, Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 In-reply-to: Your message of "21 Feb 2000 01:48:53 PST." Date: Mon, 21 Feb 2000 01:52:35 -0800 Message-ID: <88640.951126755@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And how exactly are you going to tell /usr/bin/login, /usr/bin/chpass, > /usr/local/bin/wu-ftpd, etc., where to find that file? Remember, if > it's ports that read the setup file, it can be moved around anywhere > by changing PREFIX -- but for files that are read by the system, it is If it's PREFIX-agile then the idea won't work, of course. Hmmm. Yeah, OK, scrap the idea. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 2: 8: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id D224D37B960; Mon, 21 Feb 2000 02:07:58 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id LAA83901; Mon, 21 Feb 2000 11:07:52 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 11:07:52 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Cc: freebsd-net@freebsd.org, diablo-list@list.bart.nl Subject: Panic (TCP) Message-ID: <20000221110752.A83583@lucifer.bart.nl> Reply-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this is fun... Just caught panic #3 on my Diablo newstransit box running 4.0 from the 7th of February. This box pushes around 360-380 GB in a weekend on network IO. panic: tcp_setpersist: retransmit pending Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.354 db> trace Debugger(c01e8063) at Debugger+0x35 panic(c01eddc0,d5ce6b60,d8d8bc48,c018bcb6,d5ce6b60) at panic+0x70 tcp_setpersist(d5ce6b60,d5ce6b60,c018bc24,d8d8bc6c,c0149279) at tcp_setpersist+0x2c tcp_timer_persist(d5ce6b60,40000000,160,c1cd0000,cdfae000) at tcp_timer_persist+0x92 softclock(0,c0160010,cc4d0010,cc4d0010,cdfae000) at softclock+0xd1 doreti_swi(c1d7d000,50b0,2000) at doreti_swi+0xf ffs_reallocblks(d8d8be04) at ffs_reallocblks+0x3d0 cluster_write(cc5213e8,4332000,0) at cluster_write+0x15a ffs_write(d8d8bea0,d8cf79c0,fdc,c1f14800,c0201e80) at ffs_write+0x476 vn_write(c1f14800,d8d8beec,c1d30500,0,d8cf79c0) at vn_write+0xda dofilewrite(d8cf79c0,c1f14800,6,280be020,fdc) at dofilewrite+0x91 write(d8cf79c0,d8d8bf80,280be000,15,280be000) at write+0x33 syscall(bfbf002f,280a002f,bfbf002f,280be000,15) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 This is from the serial console. I'm going to dump the memory to swap now and do some gdb with my kernel.debug. Advice is wanted and highly appreciated. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 2:22:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id AA2C037BBCF for ; Mon, 21 Feb 2000 02:22:49 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id LAA92236 for freebsd-current@FreeBSD.ORG; Mon, 21 Feb 2000 11:22:28 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002211022.LAA92236@info.iet.unipi.it> Subject: Re: Panic (TCP) In-Reply-To: <20000221110752.A83583@lucifer.bart.nl> from Jeroen Ruigrok van der Werven at "Feb 21, 2000 11:07:52 am" To: freebsd-current@FreeBSD.ORG Date: Mon, 21 Feb 2000 11:22:28 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (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 is fun... > > Just caught panic #3 on my Diablo newstransit box running 4.0 from the > 7th of February. > > This box pushes around 360-380 GB in a weekend on network IO. this is the right kind of app for -current isn't it :) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 2:53:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.di.uminho.pt (mail.di.uminho.pt [193.136.20.67]) by hub.freebsd.org (Postfix) with SMTP id D5BD237BBCF for ; Mon, 21 Feb 2000 02:53:46 -0800 (PST) (envelope-from jose@di.uminho.pt) Received: (qmail 29809 invoked from network); 21 Feb 2000 11:10:11 -0000 Received: from bogalhinho.di.uminho.pt (HELO di.uminho.pt) (jose@193.136.20.38) by mail.di.uminho.pt with SMTP; 21 Feb 2000 11:10:11 -0000 Message-ID: <38B127F0.48C04CB0@di.uminho.pt> Date: Mon, 21 Feb 2000 11:56:32 +0000 From: =?iso-8859-1?Q?Jos=E9=20Lu=EDs?= Faria Organization: Universidade do Minho-Departamento de =?iso-8859-1?Q?Inform=E1tica?= X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-config@freebsd.org, freebsd-current@freebsd.org Subject: Kernel Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I'm creating a litle update to a freebsd 3.4 kernel. My program is for account some data: number of packets by class, number of packets dropped by class, etc. Now I need to pass this values to another program wich in X-Window display this values on-line. After, I want to save this values in a file. I need some docs about how I can do this. Which are the primitives in the kernel to do this. I use the printf to put this data in /var/log/messages. This inappropriate, I dont want this. This is only for testing now. Can you help me ? Thank you very much. P.S. I'm sorry my english. -- :) cumprimentos -------------------------------- Jose Luis Faria Administrador de Sistemas Universidade do Minho - Departamento de Informática Campus de Gualtar 4710-057 Braga Portugal tel.: +351 253604440 Fax:+351 253604471 http://admin.di.uminho.pt/~jose To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:12:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pouet.noc.fr.clara.net (headache.noc.fr.clara.net [212.43.195.29]) by hub.freebsd.org (Postfix) with ESMTP id EE9E537BC00; Mon, 21 Feb 2000 03:12:30 -0800 (PST) (envelope-from sameh@fr.clara.net) Received: by pouet.noc.fr.clara.net (Postfix, from userid 1000) id EF1D3298; Mon, 21 Feb 2000 12:12:46 +0100 (CET) Date: Mon, 21 Feb 2000 12:12:46 +0100 From: Sameh Ghane To: freebsd-current@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221121246.F18727@noc.fr.clara.net> References: <20000221110752.A83583@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <20000221110752.A83583@lucifer.bart.nl>; from asmodai@bart.nl on Mon, Feb 21, 2000 at 11:07:52AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit: > Well, > > this is fun... > > Just caught panic #3 on my Diablo newstransit box running 4.0 from the > 7th of February. > > This box pushes around 360-380 GB in a weekend on network IO. > > panic: tcp_setpersist: retransmit pending > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.354 This is interesting as we use 4.0 on a transit nntp server also, running diablo. We have 60GB IN/OUT each day, and it runs fine: $ uptime 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000 Try downgrading ? -- Sameh Ghane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:29:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id 21B0F37BBFC; Mon, 21 Feb 2000 03:29:42 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id 02FFB1D12B; Mon, 21 Feb 2000 11:29:40 +0000 (GMT) Message-ID: <38B121AC.B2F0E2E3@originative.co.uk> Date: Mon, 21 Feb 2000 11:29:48 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: Mark Murray Cc: Peter Wemm , current@freebsd.org, committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> <200002180743.JAA26529@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > Mark Murray wrote: > > > > I'm very uncomfortable with requiring Yet Another Daemon to manage > > > > (and screw up) password checking. Generally speaking, if I wouldn't > > > > trust a program with root privileges, I wouldn't trust it with my > > > > password, either (for obvious reasons). > > > > > > If "all those" suid programs could be "de-suid'ed", and replaced with > > > a simple "does this username/password pair check out?" daemon/module, > > > would that make you happier? > > > > As long as there is some sort of rate limiting system so that it doesn't > > provide a trivial online brute force password cracking service... Getting > > this right would be an interesting challenge. :-) > > Easy to do of the daemon is not on by default, or if it is pretty fascist by > default, with lots of options to define the fascism. I think there are risks with this approach and I'm not sure the benefits are clear cut. My main concern is single point of failure. It's only an improvement on what we have now if we can remove suid programs. If you do that then the *only* way to authenticate is via the daemon. If you screw the daemon in some way and you don't already have a root session then your only option is to hit the power switch. At the moment, if you screw login you can su, if you screw su then you can login at the console etc etc. The daemon becomes an obvious target for DOS given how critical it is and any weakness that would cause it to fail would result in a catastrophic system failure. There aren't many (any?) system processes that are that critical. How are you going to deal with single-user boots? I can't really see how you can remove all password related suid programs, only a few of them. The other concern is that at the moment you can't get access to the encrypted password without being root. With a daemon any user can process can access that information. I accept that this might not be a losing position since any user script could run su or password repeatedly but it seems to me that there isn't a *clear* security enhancement here. The daemon approach actually has benfits that I'm keen on that aren't related to security. A single point of access to the data means that the backend can be changed so that passwords can be in a different file or a database, without having to worry about rebuilding all the binaries. You could even split users across different back end systems. It would be interesting to extend the whole idea so that there were username classes e.g. system account, web site user and so on. Then you could use the same database to hold all account information. This is of course what NT does and most people hate that because the web server then has access to the login passwords. If you're going to have a daemon though that any user process can connect to then this is the direction you're moving in so you may as well take the added functionality that comes with it and make it a generic authentication system that can be used for things like web servers. On the whole though, I'm not sure that this is a direction that has a definate win to it. How many binaries are there that have access to the master.passwd file? How many lines of code need to be audited for those binaries, compared to the number of lines of code needed to implement a secure daemon solution? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:39:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 8156337BC2B; Mon, 21 Feb 2000 03:39:21 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA04827; Mon, 21 Feb 2000 20:39:19 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id UAA15500; Mon, 21 Feb 2000 20:39:18 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA00279; Mon, 21 Feb 2000 20:39:17 +0900 (JST) To: asmodai@bart.nl Cc: sameh@fr.clara.net Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000221121246.F18727@noc.fr.clara.net> References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000221204008M.shin@nd.net.fujitsu.co.jp> Date: Mon, 21 Feb 2000 20:40:08 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just caught panic #3 on my Diablo newstransit box running 4.0 from the > > 7th of February. > We have 60GB IN/OUT each day, and it runs fine: > > $ uptime > 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64 > > 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000 > > Try downgrading ? Wmmm, there were much changes to tcp code for IPv6 support after Jan 5. I reviewed tcp_setpersist related code and such problem not seems to happen in correct state. Might there be incorrect memory over writing? Do you have any other date, such as *tt_persist value at panic? And is there any other person who experienced same kind of problem and have any hints to diagnose this? I'll again review my changes. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:39:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ost.eltele.no (relay.ost.eltele.no [195.70.164.132]) by hub.freebsd.org (Postfix) with ESMTP id DB2F937B784 for ; Mon, 21 Feb 2000 03:39:22 -0800 (PST) (envelope-from telde@online.no) Received: from delta.shacknet.nu (ppp-212.125.166.98.sensewave.com [212.125.166.98]) by relay.ost.eltele.no (8.9.3/8.9.3) with ESMTP id MAA12283 for ; Mon, 21 Feb 2000 12:39:19 +0100 (MET) Received: by delta.shacknet.nu (Postfix, from userid 1001) id 67E5A7CF6; Mon, 21 Feb 2000 03:40:20 +0100 (CET) Date: Mon, 21 Feb 2000 03:40:19 +0100 From: Terje Elde To: freebsd-current@freebsd.org Subject: Abit BP6 Message-ID: <20000221034017.A94363@best.xti.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Possibly not the right place to ask about this, but I've been unable to dig up any information about this elsewhere, so I figure it might be worth a shot. This could be interesting for others on the list as well. I've come across a rather nice looking motherboard from Abit, a BP6 to be exact. The nice thing about this motherboard is that in addition to being generally high quality, offering 4 IDE channels and so on, it will allow you to use two Celeron processors in a SMP config, thus making the board ideal for all those situations where you want to build a powerful box, but just don't have the money for the real thing. This all assuming you can get it to work in the first place, which leads me to my question. I FreeBSD needs SMP boards to comply to the Intel MP specs to work, but I've been unable to find out if this board does or not. I'm also not sure if FreeBSD will run with dual Celerons, as the processors was not really intended for SMP. Anyone have any information to contribute? Thanks, Terje Elde -- Jxqda WET squiqh yid'j jxu ijhedwuij shofje qlqybqrbu je VhuuRIT kiuhi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:50:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 6D77337BDC1; Mon, 21 Feb 2000 03:50:17 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id MAA84857; Mon, 21 Feb 2000 12:50:10 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 12:50:10 +0100 From: Jeroen Ruigrok van der Werven To: Yoshinobu Inoue Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221125010.H84100@lucifer.bart.nl> References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net> <20000221204008M.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221204008M.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 08:40:08PM +0900 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 12:45], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote: >> > Just caught panic #3 on my Diablo newstransit box running 4.0 from the >> > 7th of February. > >> We have 60GB IN/OUT each day, and it runs fine: >> >> $ uptime >> 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64 >> >> 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000 >> >> Try downgrading ? > >Wmmm, there were much changes to tcp code for IPv6 support after Jan 5. > >I reviewed tcp_setpersist related code and such problem not >seems to happen in correct state. >Might there be incorrect memory over writing? How you mean? >Do you have any other date, such as *tt_persist value at >panic? This is gdb -k /kernel.debug /var/crash/vmcore.0: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2625536 initial pcb at 21cb00 panicstr: from debugger panic messages: --- panic: tcp_setpersist: retransmit pending panic: from debugger Uptime: 2d20h34m30s amrd0: still open, can't shutdown dumping to dev #da/0x20001, offset 524312 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) backtrace #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc0143f59 in panic (fmt=0xc01e2894 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc01245c1 in db_panic (addr=-1071885851, have_addr=0, count=-1, modif=0xd8d8bac0 "") at ../../ddb/db_command.c:433 #3 0xc0124561 in db_command (last_cmdp=0xc020447c, cmd_table=0xc02042dc, aux_cmd_tablep=0xc021917c) at ../../ddb/db_command.c:333 #4 0xc0124626 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc012673f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc01c4f89 in kdb_trap (type=3, code=0, regs=0xd8d8bbc8) at ../../i386/i386/db_interface.c:158 #7 0xc01d05dc in trap (frame={tf_fs = 16, tf_es = -1053687792, tf_ds = -1072168944, tf_edi = 1073741824, tf_esi = 256, tf_ebp = -656884720, tf_isp = -656884748, tf_ebx = -1071718976, tf_edx = 1073872896, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071885851, tf_cs = 8, tf_eflags = 582, tf_esp = -1071667873, tf_ss = -1071742877}) at ../../i386/i386/trap.c:531 #8 0xc01c51e5 in Debugger (msg=0xc01e8063 "panic") at machine/cpufunc.h:64 #9 0xc0143f50 in panic (fmt=0xc01eddc0 "tcp_setpersist: retransmit pending") at ../../kern/kern_shutdown.c:552 #10 0xc018abc4 in tcp_setpersist (tp=0xd5ce6b60) at ../../netinet/tcp_output.c:893 #11 0xc018bcb6 in tcp_timer_persist (xtp=0xd5ce6b60) at ../../netinet/tcp_timer.c:337 #12 0xc0149279 in softclock () at ../../kern/kern_timeout.c:131 #13 0xc01c6c9b in doreti_swi () #14 0xc0194658 in ffs_reallocblks (ap=0xd8d8be04) at ../../ufs/ffs/ffs_alloc.c:525 #15 0xc016961a in cluster_write (bp=0xcc5213e8, filesize=70459392) at vnode_if.h:1056 #16 0xc019ac02 in ffs_write (ap=0xd8d8bea0) at ../../ufs/ufs/ufs_readwrite.c:495 #17 0xc0173d22 in vn_write (fp=0xc1f14800, uio=0xd8d8beec, cred=0xc1d30500, flags=0, p=0xd8cf79c0) at vnode_if.h:363 #18 0xc0150e5d in dofilewrite (p=0xd8cf79c0, fp=0xc1f14800, fd=6, buf=0x280be020, nbyte=4060, offset=-1, flags=0) at ../../sys/file.h:156 #19 0xc0150d63 in write (p=0xd8cf79c0, uap=0xd8d8bf80) at ../../kern/sys_generic.c:298 #20 0xc01d0e7e in syscall (frame={tf_fs = -1078001617, tf_es = 671744047, tf_ds = -1078001617, tf_edi = 671866880, tf_esi = 21, tf_ebp = -1077971400, tf_isp = -656883756, tf_ebx = 671866880, tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 134595120, tf_cs = 31, tf_eflags = 514, tf_esp = -1077971444, tf_ss = 47}) at ../../i386/i386/trap.c:1055 #21 0xc01c5886 in Xint0x80_syscall () #22 0x804ed66 in ?? () #23 0x804c18e in ?? () #24 0x804abaf in ?? () #25 0x804983d in ?? () #26 0x80490c5 in ?? () ---Type to continue, or q to quit--- #27 0x8048829 in ?? () #28 0x80480f9 in ?? () >And is there any other person who experienced same kind of >problem and have any hints to diagnose this? I am updating the box as we speak to sources of today (which btw don't seem to like a -j4 flag). >I'll again review my changes. Not sure if needed. But I felt the reason to pipe up about this because if it is a genuine bug stil in the system we need to get it out of the system ASAP. Debugging tips are welcome, since I am not the biggest bulb wrt debugging. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:52:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 9A26C37BCC3 for ; Mon, 21 Feb 2000 03:52:27 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id RAA02053; Mon, 21 Feb 2000 17:52:20 +0600 (NOVT) (envelope-from nnd) Date: Mon, 21 Feb 2000 17:52:20 +0600 (NOVT) Message-Id: <200002211152.RAA02053@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: Abit BP6 X-Newsgroups: itfs.freebsd.current In-Reply-To: <20000221034017.A94363@best.xti.org> User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000221034017.A94363@best.xti.org> Terje Elde wrote: > > Anyone have any information to contribute? > There is the 'dmesg' from the system based on the Abit BP6 motherboard. As you can see the OS is very current. (In fact I rebuild world on this system every morning iff it is at all possible due to moon phase ;-) N.Dudorov P.S. Yes, I know about 'overclocking is considered harmfull" ;-( Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Feb 21 12:39:02 NOVT 2000 nnd@wint.itfs.nsk.su:/arch/FreeBSD-current/src/sys/compile/WINTS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 257400832 (251368K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 17 -> irq 5 IOAPIC #0 intpin 18 -> irq 11 IOAPIC #0 intpin 19 -> irq 10 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02eb000. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0296d42 (1000022) VESA: NVidia Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator (vendor=0x10de, dev=0x002d) at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 Timecounter "PIIX" frequency 3579545 Hz intpm0: port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 ed0: port 0xc400-0xc41f irq 5 at device 13.0 on pci0 ed0: address 00:00:01:01:05:9a, type NE2000 (16 bit) pcm0: port 0xc800-0xc83f irq 10 at device 17.0 on pci0 atapci1: port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at device 19.0 on pci0 ata2: at 0xcc00 on atapci1 atapci2: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.1 on pci0 ata3: at 0xd800 on atapci2 fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 12416MB [25228/16/63] at ata0-master using UDMA33 ad1: 12969MB [26351/16/63] at ata1-master using UDMA33 ad2: 14664MB [29795/16/63] at ata2-master using UDMA66 acd0: CD-RW at ata3-master using PIO3 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 3:54:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id E05EA37BC92 for ; Mon, 21 Feb 2000 03:54:52 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id MAA15067 for ; Mon, 21 Feb 2000 12:54:51 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id MAA04414; Mon, 21 Feb 2000 12:54:51 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id MAA20550; Mon, 21 Feb 2000 12:54:51 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: <19347.951098777@zippy.cdrom.com> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Date: 21 Feb 2000 12:54:51 +0100 In-Reply-To: "Jordan K. Hubbard"'s message of "Sun, 20 Feb 2000 18:06:17 -0800" Message-ID: Lines: 25 User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > I'm not totally inflexible about making the engineering vs user > argument either, don't get me wrong, but this one is perilously in the > middle and bringing something like openssh in as a companion to > openssl would certainly raise my estimation of openssl as a 4.0 > candidate. Yes, I'd even be willing to delay the release date for > something like that. So does this mean that the question has now become `do we want OpenSSH in 4.0 (in the base system)'? I'm just a newbie and an outside observer. Apparently, OpenSSH has been available as a port for a while. Do you think it would be useful to think about the hassle the user has to go through to install OpenSSH? Is it any more difficult for the user when OpenSSH is a port? (I gather that it is possible to use pkg_add to install parts of the base system as well as pre-compiled ports. So in general I might not even know whether `pkg_add -r foo' installs a port or a part of the base system?) Feel free to ignore me if this was really stupid. kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 4: 2:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id A326737BC00; Mon, 21 Feb 2000 04:02:26 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id CBDD31D12B; Mon, 21 Feb 2000 12:02:22 +0000 (GMT) Message-ID: <38B12956.33A6303B@originative.co.uk> Date: Mon, 21 Feb 2000 12:02:30 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: Jonathan Lemon Cc: dcs@newsguy.com, freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <200002192226.QAA92457@prism.flugsvamp.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > In article you write: > >Kai Großjohann wrote: > >> > >> "Jordan K. Hubbard" writes: > >> > >> > I really kinda wish you'd point them to Novice^H^H^H^H^HStandard > >> > instead since it does more than be a bit more verbose, it also makes > >> > sure that all the appropriate steps are covered and prevents even > >> > relatively skilled people from hanging themselves. > >> > >> Does this mean that this option should be called `guided'? I know a > >> little bit about Unix but haven't installed FreeBSD more than five > >> times or so. And I always thought that the novice install meant that > >> I didn't get as many choices... > > > >"Guided". I like it. That's *PRECISELY* what this installation option > >is. There is NO difference in the number of choices available in any of > >the three types. > > > >Guided/Express/Expert. That's my vote. > > Cool, seconded. I actually use "novice" most of the time, simply > because I like the hints that help me not to screw up, and I've been > using this option (or equivalent) since 1.1.5 at least. > > Guided sounds like a better description to me. Possibly, the mistake here is to present the "custom" option as an install method at all. Given that "novice" walks you through the install steps but still allows you to do a customised install, it should perhaps be called "installation", the custom option should be changed to something like "maintenance" because really that's where it's useful in that you can go fix any bit of the system without having to walk through all the installation steps. No new users would try and use "maintenance" to do their installation with. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 4:21: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id D7DA137BC9A; Mon, 21 Feb 2000 04:20:53 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id NAA15711; Mon, 21 Feb 2000 13:20:52 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id NAA04836; Mon, 21 Feb 2000 13:20:52 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id NAA21074; Mon, 21 Feb 2000 13:20:52 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> <200002180743.JAA26529@gratis.grondar.za> <38B121AC.B2F0E2E3@originative.co.uk> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Date: 21 Feb 2000 13:20:52 +0100 In-Reply-To: Paul Richards's message of "Mon, 21 Feb 2000 11:29:48 +0000" Message-ID: Lines: 13 User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Richards writes: > The daemon approach actually has benfits that I'm keen on that aren't > related to security. A single point of access to the data means that the > backend can be changed so that passwords can be in a different file or a > database, without having to worry about rebuilding all the binaries. You > could even split users across different back end systems. This sounds like PAM, doesn't it? kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 4:26:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 076C837BBFC; Mon, 21 Feb 2000 04:26:08 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id VAA15904; Mon, 21 Feb 2000 21:26:06 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id VAA23590; Mon, 21 Feb 2000 21:26:05 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id VAA01467; Mon, 21 Feb 2000 21:26:05 +0900 (JST) To: asmodai@bart.nl Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000221125010.H84100@lucifer.bart.nl> References: <20000221121246.F18727@noc.fr.clara.net> <20000221204008M.shin@nd.net.fujitsu.co.jp> <20000221125010.H84100@lucifer.bart.nl> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000221212656L.shin@nd.net.fujitsu.co.jp> Date: Mon, 21 Feb 2000 21:26:56 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 36 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Might there be incorrect memory over writing? > > How you mean? I think one possibility of the problem is that some code is incorrectly overwriting some part of the memory, and a tcpcb's tt_persist->c_flags is happen to overwritten. Now I am very much interested in the value of tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and possibly other flags are just set, or completely broken data is written on it. And if later, I am also interested in other values around tp->tt_persist->c_flags, to check what kind of value is written around there. > Debugging tips are welcome, since I am not the biggest bulb wrt > debugging. I am not also, and you might have already known these things, but in case they are useful, -If DDB is specified in kernel config file, and all src/sys tree including sys/compile dir is saved onto another machine, it will be very useful at next panic, because remote GDB debugging is available by those data. (Though if the bug happens at very delicate timing, it might prevent the bug from happening again.) -Adding some printfs in tcp_output.c:tcp_setpersist() panic case might be useful. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 4:47:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 7121137BBCB; Mon, 21 Feb 2000 04:47:30 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA93976; Mon, 21 Feb 2000 13:47:24 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 13:47:24 +0100 From: Jeroen Ruigrok van der Werven To: Yoshinobu Inoue Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221134724.J84100@lucifer.bart.nl> References: <20000221121246.F18727@noc.fr.clara.net> <20000221204008M.shin@nd.net.fujitsu.co.jp> <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221212656L.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 09:26:56PM +0900 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 13:30], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote: >> >Might there be incorrect memory over writing? >> >> How you mean? > >I think one possibility of the problem is that some code is >incorrectly overwriting some part of the memory, and a tcpcb's >tt_persist->c_flags is happen to overwritten. Hmmm, this box is a real disk io and network io bastard. It serves as a newspeer transit box based on diablo 1.27 with a fxp card and an amr array. Let me know if a dmesg is needed. >Now I am very much interested in the value of >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and >possibly other flags are just set, or completely broken data >is written on it. (kgdb) up 10 #10 0xc018abc4 in tcp_setpersist (tp=0xd5ce6b60) at ../../netinet/tcp_output.c:893 warning: Source file is more recent than executable. 893 (kgdb) print tp->tt_persist->c_flags $1 = 0 [I am upgrading the box to the latest sources as we speak, hence the sourcecode is newer] >And if later, I am also interested in other values around >tp->tt_persist->c_flags, to check what kind of value is >written around there. (kgdb) print tp->tt_persist $2 = (struct callout *) 0xd5ce6c44 (kgdb) print *(tp->tt_persist) $3 = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xcc401640}}, c_time = 22275044, c_arg = 0xd5ce6b60, c_func = 0, c_flags = 0} >> Debugging tips are welcome, since I am not the biggest bulb wrt >> debugging. > >I am not also, and you might have already known these things, >but in case they are useful, > > -If DDB is specified in kernel config file, and all src/sys > tree including sys/compile dir is saved onto another > machine, it will be very useful at next panic, because remote GDB > debugging is available by those data. I have a serial console active so I can do DDB from my workstation. Hence I always have a kernel and kernel.debug from the same sources. > (Though if the bug happens at very delicate timing, it > might prevent the bug from happening again.) > > -Adding some printfs in tcp_output.c:tcp_setpersist() panic > case might be useful. It might. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 4:59:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 6C8D337BAE7; Mon, 21 Feb 2000 04:59:15 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA94103; Mon, 21 Feb 2000 13:59:13 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 13:59:13 +0100 From: Jeroen Ruigrok van der Werven To: Sameh Ghane Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221135913.L84100@lucifer.bart.nl> References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <20000221121246.F18727@noc.fr.clara.net>; from sameh@fr.clara.net on Mon, Feb 21, 2000 at 12:12:46PM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 12:15], Sameh Ghane (sameh@fr.clara.net) wrote: >Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit: >> Just caught panic #3 on my Diablo newstransit box running 4.0 from the >> 7th of February. My first two were ffs related. And I hadn't enabled DDB and dumpdev back then =\ No soft-updates. >> This box pushes around 360-380 GB in a weekend on network IO. >> >> panic: tcp_setpersist: retransmit pending >> Debugger("panic") >> Stopped at Debugger+0x35: movb $0,in_Debugger.354 > >This is interesting as we use 4.0 on a transit nntp server also, running diablo. > >We have 60GB IN/OUT each day, and it runs fine: 60 GB is our daily incoming feed. ;) And add to that between 90-120 GB outgoing a day. >$ uptime >12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64 Nice. I am currently preprocessing the messages with cleanfeed which causes my average to be something like 3.xx 3.xx 3.xx >4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000 > >Try downgrading ? No thanks, I want 4.0 to be bugfree, not work around the problem. ;) -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 5:34:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id DEBA237BC79; Mon, 21 Feb 2000 05:34:13 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id WAA07413; Mon, 21 Feb 2000 22:34:10 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id WAA17034; Mon, 21 Feb 2000 22:34:10 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id WAA03283; Mon, 21 Feb 2000 22:34:08 +0900 (JST) To: asmodai@bart.nl Cc: sameh@fr.clara.net, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000221134724.J84100@lucifer.bart.nl> References: <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp> <20000221134724.J84100@lucifer.bart.nl> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000221223459W.shin@nd.net.fujitsu.co.jp> Date: Mon, 21 Feb 2000 22:34:59 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Now I am very much interested in the value of > >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and > >possibly other flags are just set, or completely broken data > >is written on it. > > 893 > (kgdb) print tp->tt_persist->c_flags > $1 = 0 Woops sorry I was worng. tp->tt_rexmt->c_flags is actually causing the panic, and the necessary data is the contents of the tp->tt_rexmt->c_flags. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 5:49:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id A513437BC1D; Mon, 21 Feb 2000 05:49:03 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id OAA94506; Mon, 21 Feb 2000 14:48:59 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 14:48:59 +0100 From: Jeroen Ruigrok van der Werven To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221144858.O84100@lucifer.bart.nl> References: <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp> <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221223459W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 10:34:59PM +0900 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 14:40], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote: >> >Now I am very much interested in the value of >> >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and >> >possibly other flags are just set, or completely broken data >> >is written on it. >> >> 893 >> (kgdb) print tp->tt_persist->c_flags >> $1 = 0 > >Woops sorry I was worng. >tp->tt_rexmt->c_flags is actually causing the panic, and the >necessary data is the contents of the tp->tt_rexmt->c_flags. (kgdb) print tp->tt_rexmt->c_flags $1 = 6 (kgdb) print tp->tt_rexmt $2 = (struct callout *) 0xd5ce6c2c (kgdb) print (*tp->tt_rexmt) $3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c, tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60, c_func = 0xc018bcdc , c_flags = 6} -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 6: 3:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 8E97D37BCB4 for ; Mon, 21 Feb 2000 06:03:13 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id PAA94650 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 15:03:12 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 15:03:12 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Subject: Panic (ffs) Message-ID: <20000221150312.A94602@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, so I rebuild world from today's sources and since diablo isn't that happy with truncated files I decided to clean up the amr mounted /news/spool. 'lo and behold: dev = #da/0x20003, block = 6560, fs = /news panic: ffs_blkfree: freeing free block Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.372 The joy! =) db> trace Debugger(c01e7ee3) at Debugger+0x35 panic(c01f27e0,c01f27c0,c1ccc914,19a0,c1d0d8d4) at panic+0x70 ffs_blkfree(c1d92200,19a0,2000,d8d11fe0,c1d92200) at ffs_blkfree+0x1dd ffs_truncate(d8d11fe0,0,0,0,0) at ffs_truncate+0x809 ufs_inactive(d8b7feb8,d8b7fec8,c016d0ae,d8b7feb8,0) at ufs_inactive+0x72 ufs_vnoperate(d8b7feb8,0,d8d11fe0,c02020c0,d8d11fe0) at ufs_vnoperate+0x15 vput(d8d11fe0,d8b320c0,c02065b4,d8b7ff80,c0201ec0) at vput+0x8e unlink(d8b320c0,d8b7ff80,8082200,807b000,1) at unlink+0x135 syscall(2f,2f,2f,1,807b000) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 So here I am, waiting for the memory to dump again. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 6:37:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from web119.yahoomail.com (web119.yahoomail.com [205.180.60.120]) by hub.freebsd.org (Postfix) with SMTP id 7628C37BC5A for ; Mon, 21 Feb 2000 06:37:31 -0800 (PST) (envelope-from m_evmenkin@yahoo.com) Received: (qmail 21863 invoked by uid 60001); 21 Feb 2000 14:37:07 -0000 Message-ID: <20000221143707.21862.qmail@web119.yahoomail.com> Received: from [12.20.58.68] by web119.yahoomail.com; Mon, 21 Feb 2000 06:37:07 PST Date: Mon, 21 Feb 2000 06:37:07 -0800 (PST) From: Maksim Yevmenkin Subject: NETGRAPH patches (proposal) To: freebsd-current@freebsd.org Cc: freebsd-hackers@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 Hello All, Here are some small patches for NETGRAPH. These are against -current cvsup'ed yesterday around 8:30pm EST. http://home.earthlink.net/~evmax/ng.tar.gz It also includes small test program (based on nghook). Compile and run it like: # ./a.out -a iface_name: divert NETGRAPH option in kernel config file is required. Here is the description. ng_ether node has two hooks ``divert'' and ``orphan''. It is possible to connect to the one of the hooks and intercept row Ethernet frames. But there is no clean way to intercept frame, do something and return it back to kernel. This patch provides additional hook ``divertin'' (mmm... name is not good, i think) for each ng_ether node. Implementation issues This will not work for ``orphan'' frames. Since kernel drops it anyway, i decided to leave it as it is. But is is possible to intercept ``orphan'' packets, change it, and write back to ``divertin''. Thanks, emax __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 6:47:34 2000 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 D194737BD7B for ; Mon, 21 Feb 2000 06:47:27 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p38-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.39]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA28957; Mon, 21 Feb 2000 23:47:13 +0900 (JST) Message-ID: <38B14FB6.D341CA6D@newsguy.com> Date: Mon, 21 Feb 2000 23:46:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: dan@freebsddiary.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: <200002210758.UAA61844@ducky.nz.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Langille wrote: > > On 21 Feb 00, at 15:23, Daniel C. Sobral wrote: > > > Christian Weisgerber wrote: > > > > > > binary installation: > > > - before: user needs to install openssl port > > > - now: user needs to install openssl package > > > > Where is the openssl package, and what it is called? > > security/openssl Huh? Isn't that the port? Or do I have to go to sysinstall/ftp to get a binary package? Because installing the _port_ openssl doesn't work. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 6:51:11 2000 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 13A1A37BD85; Mon, 21 Feb 2000 06:51:07 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p38-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.39]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA00544; Mon, 21 Feb 2000 23:51:04 +0900 (JST) Message-ID: <38B1509F.87CA3379@newsguy.com> Date: Mon, 21 Feb 2000 23:50:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: Christian Weisgerber , freebsd-current@FreeBSD.org Subject: Re: openssl in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > > Christian Weisgerber wrote: > > > > > > binary installation: > > > - before: user needs to install openssl port > > > - now: user needs to install openssl package > > > > Where is the openssl package, and what it is called? > > http://www.freebsd.org/~kris/openssl/ That's not acceptable to me. I'm not in the US. > However.. with Jordan's help I'm working on a solution to all of the > current kerfuffle, so please stay tuned. Roger Wilco. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:36:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 3634837BD85 for ; Mon, 21 Feb 2000 07:36:20 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id QAA99307 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 16:36:18 +0100 (CET) (envelope-from asmodai) Date: Mon, 21 Feb 2000 16:36:17 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Subject: Re: Panic (ffs) Message-ID: <20000221163617.B94917@lucifer.bart.nl> References: <20000221150312.A94602@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221150312.A94602@lucifer.bart.nl>; from asmodai@bart.nl on Mon, Feb 21, 2000 at 03:03:12PM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [root@tyr] (61) # gdb -k /kernel.debug vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2625536 initial pcb at 21c9e0 panicstr: from debugger panic messages: --- panic: ffs_blkfree: freeing free block panic: from debugger Uptime: 39m4s amrd0: still open, can't shutdown dumping to dev #da/0x20001, offset 524312 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc01244e1 in db_panic (addr=-1071886047, have_addr=0, count=-1, modif=0xd8b7fb88 "") at ../../ddb/db_command.c:433 #3 0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c, aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333 #4 0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc012665f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc01c4ec5 in kdb_trap (type=3, code=0, regs=0xd8b7fc90) at ../../i386/i386/db_interface.c:158 #7 0xc01d05f4 in trap (frame={tf_fs = -1072431088, tf_es = -701956080, tf_ds = -701956080, tf_edi = -838037504, tf_esi = 256, tf_ebp = -659030824, tf_isp = -659030852, tf_ebx = -1071700000, tf_edx = 0, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071886047, tf_cs = 8, tf_eflags = 582, tf_esp = -1071668385, tf_ss = -1071743261}) at ../../i386/i386/trap.c:549 #8 0xc01c5121 in Debugger (msg=0xc01e7ee3 "panic") at machine/cpufunc.h:64 #9 0xc0143d58 in panic (fmt=0xc01f27e0 "ffs_blkfree: freeing free block") at ../../kern/kern_shutdown.c:552 #10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192) at ../../ufs/ffs/ffs_alloc.c:1337 #11 0xc0197be1 in ffs_truncate (vp=0xd8d11fe0, length=0, flags=0, cred=0x0, p=0xd8b320c0) at ../../ufs/ffs/ffs_inode.c:337 #12 0xc019c8e6 in ufs_inactive (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_inode.c:84 #13 0xc01a1985 in ufs_vnoperate (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_vnops.c:2283 #14 0xc016d0ae in vput (vp=0xd8d11fe0) at vnode_if.h:794 #15 0xc01703b9 in unlink (p=0xd8b320c0, uap=0xd8b7ff80) at ../../kern/vfs_syscalls.c:1421 #16 0xc01d0e96 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 1, tf_esi = 134721536, tf_ebp = -1077945076, tf_isp = -659030060, tf_ebx = 134750720, tf_edx = 134750812, tf_ecx = 0, tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 134533504, tf_cs = 31, tf_eflags = 647, tf_esp = -1077945120, tf_ss = 47}) at ../../i386/i386/trap.c:1073 #17 0xc01c57c6 in Xint0x80_syscall () #18 0x80482c3 in ?? () #19 0x80480f9 in ?? () -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:37: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 87A9E37BED6 for ; Mon, 21 Feb 2000 07:36:55 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 589521E37; Mon, 21 Feb 2000 16:36:48 +0100 (CET) Date: Mon, 21 Feb 2000 16:36:48 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: -current hangs HARD Message-ID: <20000221163648.A486@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have been having HARD -current hangs recently and they don't seem to be going away by cvsupping. I've been having two complete lockups (i.e. no response from X, network or serial terminal; no crashdump no whatsoever), which occured both times after approximately 10 days of uptime. The two hangs occurred with differently dated -currents. It seems to be repeatable... My configuration is an Abit BP6 with two 400 Mhz celerons (NO overclocking), and an ATA66 disk. FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb 7 22:46:30 CET 2000 root@relativity.student.utwente.nl:/usr/src/sys/compile/RELATIVITY5 i386 I have no idea what is causing the lockups, does anyone have similar experiences (so far I only read about lockups that occurred more often than once every 10 days or so). I can provide access to the machine and its logfiles, though I doubt that they are very useful (don't contain any obvious hints to what's causing these lockups). One last note: I didn't have these lockups before January 2000. Please, can someone shed some light on this? Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) ----> DMESG <---- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Feb 7 22:46:30 CET 2000 root@relativity.student.utwente.nl:/usr/src/sys/compile/RELATIVITY5 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 127033344 (124056K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02fe000. Preloaded elf module "vesa.ko" at 0xc02fe09c. VESA: v3.0, 7936k memory, flags:0x1, mode table:0xc02fb102 (1000022) VESA: NVidia Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0xe6000000-0xe6ffffff,0xe4000000-0xe4ffffff irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 intpm0: port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 ed0: port 0xa400-0xa41f irq 19 at device 9.0 on pci0 ed0: address /* deleted */, type NE2000 (16 bit) ahc0: port 0xa800-0xa8ff mem 0xeb000000-0xeb000fff irq 18 at device 11.0 on pci0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs pci0: unknown card (vendor=0x10b7, dev=0x9055) at 13.0 irq 17 ata-pci1: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 18 at device 19.0 on pci0 ata2 at 0xb000 irq 11 on ata-pci1 ata-pci2: port 0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07 irq 18 at device 19.1 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: HP ENHANCED PCL5,PJL plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 unknown3: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown4: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown5: at port 0x40-0x43 irq 0 on isa0 unknown6: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown7: at port 0xf0-0xff irq 13 on isa0 unknown8: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0xfec00000-0xfec0ffff,0xfee00000-0xfee0ffff,0x100000-0x7ffffff on isa0 unknown9: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xce800-0xcffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown10: at port 0x208-0x20f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! ad0: 17206MB [34960/16/63] at ata2-master using UDMA66 Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: cd present [309750 x 2048 byte records] cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xac00-0xac7f mem 0xeb001000-0xeb00107f irq 17 at device 13.0 on pci0 xl0: Ethernet address: /* deleted */ miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:40:12 2000 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 8328A37BDF4 for ; Mon, 21 Feb 2000 07:40:04 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA24760; Mon, 21 Feb 2000 10:38:35 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA02820; Mon, 21 Feb 2000 10:38:04 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id KAA00551; Mon, 21 Feb 2000 10:38:03 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200002211538.KAA00551@dean.pc.sas.com> Subject: Re: /sys/i386/machdep.c breaks kernel build In-Reply-To: <14512.50810.382596.26482Z@rina.r.dl.itc.u-tokyo.ac.jp> from Seigo Tanimura at "Feb 21, 2000 02:00:42 pm" To: Seigo Tanimura Date: Mon, 21 Feb 2000 10:38:03 -0500 (EST) Cc: rjk191@psu.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 Thanks for the fix - it has been committed. -Brian -- Brian Dean bsd@freebsd.org brdean@unx.sas.com Seigo Tanimura wrote: > On Sun, 20 Feb 2000 23:48:01 -0500, > Ray Kohler said: > > Ray> cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls > Ray> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > Ray> -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi > Ray> -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include > Ray> opt_global.h -elf -mpreferred-stack-boundary=2 > Ray> ../../i386/i386/machdep.c > Ray> {standard input}: Assembler messages: > Ray> {standard input}:2772: Error: operands given don't match any known > Ray> 386 instruction > Ray> *** Error code 1 > > > Could you try the following patch(sent to bsd personally)? It prevents > movl between a debug register and memory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:44:15 2000 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 0496037BE59 for ; Mon, 21 Feb 2000 07:44:08 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA25035; Mon, 21 Feb 2000 10:44:02 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03302; Mon, 21 Feb 2000 10:43:31 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id KAA00586; Mon, 21 Feb 2000 10:43:31 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200002211543.KAA00586@dean.pc.sas.com> Subject: Re: gcc code generation bug (optimisation related) In-Reply-To: <38B106D0.B416F877@altavista.net> from Maxim Sobolev at "Feb 21, 2000 11:35:13 am" To: sobomax@altavista.net Date: Mon, 21 Feb 2000 10:43:31 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 was my mistake. Seigo Tanimura found the problem and sent me a patch which I committed as soon as I saw it. I had a bad contraint on the destination operand of an __asm inline that did not trigger when I built the kernel at the default optimization level, but does at other optimization levels. -Brian -- Brian Dean bsd@freebsd.org brdean@unx.sas.com Maxim Sobolev wrote: > Hi, > > When I'm trying to compile kernel from just cvsup'ed sources on system > builded/installed last evening I have following error message. This problem > could be solved by lowering optimisation to -O, but previously I have no > problems with -O2 for kernels. > > cc -c -O2 -march=pentium -Wall -Wredundant-decls -Wnested-externs > -Wstrict-proto > types -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-exten > sions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include > op > t_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/machdep.c > /tmp/ccfL2694.s: Assembler messages: > /tmp/ccfL2694.s:3563: Error: operands given don't match any known 386 > instruction > *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:46: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 055E637BA8C for ; Mon, 21 Feb 2000 07:46:02 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from sos (fwuser@fw.merkantildata.dk [194.239.79.3]) by distortion.dk (8.9.3/8.9.1) with SMTP id QAA32145 for ; Mon, 21 Feb 2000 16:55:35 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <00e201bf7c82$fc123e70$16280c0a@sos> From: "Morten Seeberg" To: Subject: Things to consider in CURRENT Date: Mon, 21 Feb 2000 16:47:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed: FreeBSD fw.home 4.0-20000208-CURRENT and have a few comments: It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this out for it self? One day when installing BSD without X (which automatically installs Combat 3.x) I couldnt start it without. Shouldnt config pick up errors when making a new kernel? If I fx forget to remove an SCSI controller, but removes all SCSI peripheral lines, then the make fails, which is naturally, but shouldnt config catch that error? The same thing happens if you mark out device miibus, and compiles one of the cards that need it into the kernel. These things might be logically to some, but new users just might fall into this trap. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 7:48:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-in2.inet.tele.dk (mail-in2.inet.tele.dk [194.182.148.151]) by hub.freebsd.org (Postfix) with ESMTP id 134C537BEB1 for ; Mon, 21 Feb 2000 07:48:25 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from sos (fw.merkantildata.dk [194.239.79.3]) by mail-in2.inet.tele.dk (Postfix) with SMTP id DFAA49B1F for ; Mon, 21 Feb 2000 16:48:18 +0100 (CET) Message-ID: <00f201bf7c83$4ea290e0$16280c0a@sos> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: 0208-CURRENT and CD-Changer Date: Mon, 21 Feb 2000 16:49:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Teac 6 CD changer (acd0: CDROM with 6 CD changer at ata1-master using PIO4), which works just fine in 3.x except for the usual error message when the CD-ROM drive is empty and I start up /stand/sysinstall), but in subj. when starting /stand/sysinstall (this also happens when installing), it takes a LOOOONG time to start, and these are some of the errors that appear: lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x Probing devices, please wait (this can take a while)...Jan 3 00:03: 42 fw /kernel: acd5: Unknown CMD (0xa6) - ILLEGAL REQUEST asc=24 ascq=00 error=0 4 Jan 3 00:03:42 fw /kernel: acd5: Unknown CMD (0xa6) - ILLEGAL REQUEST asc=24 as cq=00 error=04 Jan 3 00:04:42 fw /kernel: acd5: Unknown CMD (0xa6) - ILLEGAL REQUEST asc=24 as cq=00 error=04 Jan 3 00:04:42 fw /kernel: acd5: Unknown CMD (0xa6) - ILLEGAL REQUEST asc=24 as cq=00 error=04 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 8:13:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2F40B37BCAB for ; Mon, 21 Feb 2000 08:13:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA70386; Mon, 21 Feb 2000 08:13:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA27616; Mon, 21 Feb 2000 08:13:39 -0800 (PST) (envelope-from obrien) Date: Mon, 21 Feb 2000 08:13:39 -0800 From: "David O'Brien" To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000221081339.C26109@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000220132647.H14682@dragon.nuxi.com> <42333.951021282@zippy.cdrom.com> <20000220132647.H14682@dragon.nuxi.com> <200002210838.BAA19577@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002210838.BAA19577@harmony.village.org>; from imp@village.org on Mon, Feb 21, 2000 at 01:38:29AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 01:38:29AM -0700, Warner Losh wrote: > : > 1. They're in Canada > : > : What does that buy them? They have the same restrictions on rsaref since > : it originated from the USA. > > They don't use rsaref. Well if they don't use rsaref, they offer it -- or are you telling me sslUSA26.tgz does not contain rsaref? If so, I (and a lot of people) need to remove it ASAP! -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 8:17: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2B98E37B8C9 for ; Mon, 21 Feb 2000 08:16:58 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA70400; Mon, 21 Feb 2000 08:16:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA27632; Mon, 21 Feb 2000 08:16:41 -0800 (PST) (envelope-from obrien) Date: Mon, 21 Feb 2000 08:16:41 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000221081641.D26109@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <88ptqh$264i$1@bigeye.rhein-neckar.de> <19347.951098777@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19347.951098777@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Sun, Feb 20, 2000 at 06:06:17PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 06:06:17PM -0800, Jordan K. Hubbard wrote: > It would obviously not be hard to write a set of stubs for these > things, getting those stubs called selectively in the "no real RSA" > case also not being very difficult. One way would be to put them in a > lower version-numbered shared lib, like OpenBSD did it, Actually we cannot do this. When we moved to ELF, we did away with minor shared lib numbers. (bad IMO, good in Peter's, mixed in JDP's) The RTL will not use a higher numbered [major] version. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 9:15:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5495937BA8C for ; Mon, 21 Feb 2000 09:15:52 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA70681; Mon, 21 Feb 2000 09:15:51 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA28020; Mon, 21 Feb 2000 09:15:56 -0800 (PST) (envelope-from obrien) Date: Mon, 21 Feb 2000 09:15:56 -0800 From: "David O'Brien" To: Morten Seeberg Cc: current@freebsd.org Subject: Re: Things to consider in CURRENT Message-ID: <20000221091556.A27982@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <00e201bf7c82$fc123e70$16280c0a@sos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <00e201bf7c82$fc123e70$16280c0a@sos>; from morten@seeberg.dk on Mon, Feb 21, 2000 at 04:47:40PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 04:47:40PM +0100, Morten Seeberg wrote: > It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this out > for it self? You must have an old package. I just checked the one at ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-current/All bin/bash: libreadline.so.4 => /usr/lib/libreadline.so.4 (0x280af000) libhistory.so.4 => /usr/lib/libhistory.so.4 (0x280d3000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0x280d9000) libc.so.4 => /usr/lib/libc.so.4 (0x28117000) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 9:40:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 42ADB37BC00 for ; Mon, 21 Feb 2000 09:40:28 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id JAA27499; Mon, 21 Feb 2000 09:39:55 -0800 (PST) Message-Id: <200002211739.JAA27499@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue Cc: bmah@california.sandia.gov, bauer@cc.univie.ac.at, current@FreeBSD.ORG Subject: Re: IPv6 In-Reply-To: <20000219182000U.shin@nd.net.fujitsu.co.jp> References: <20000216034713O.shin@nd.net.fujitsu.co.jp> <20000218215940K.shin@nd.net.fujitsu.co.jp> <200002190012.QAA11354@nimitz.ca.sandia.gov> <20000219182000U.shin@nd.net.fujitsu.co.jp> Comments: In-reply-to Yoshinobu Inoue message dated "Sat, 19 Feb 2000 18:20:00 +0900." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1967159241P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 21 Feb 2000 09:39:55 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1967159241P Content-Type: text/plain; charset=us-ascii If memory serves me right, Yoshinobu Inoue wrote: > > I ran across a few problems after I remade world. The new scoped > > address syntax breaks /etc/rc.network6. In particular, some lines that > > look like: > > Sorry not to announce it yet, but scoped addr format will > still change, like below. > > addr%scope > > I'll send another mail to describe it in next to this mail. OK, got it. Some of the breakage went away, in that it looks like all of the invocations to route(8) are now well-formed. This is a Good Thing (TM). > When this change happens, those problems will be resolved. Well...not quite, and I am not sure why. Following is a snippit of the bootup messages from a CURRENT machine (approximately -20000220): dc0: starting DAD for fe80:0001::0200:f8ff:fe10:6ef3 dc0: flags=8843 mtu 1500 inet 146.246.243.57 netmask 0xffffff00 broadcast 146.246.243.255 inet6 fe80::200:f8ff:fe10:6ef3%dc0 prefixlen 64 tentative ether 00:00:f8:10:6e:f3 media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UT P 10baseT/UTP 100baseTX none lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 146.246.243.254 Additional routing options: TCP keepalive=YES. routing daemons:. Doing IPv6 network setup:route: writing to routing socket: Network is unreachable add net fe80::: gateway fe80::1%lo0: Network is unreachable route: writing to routing socket: Network is unreachable add net ff02::: gateway fe80::1%lo0: Network is unreachable add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 net.inet6.ip6.forwarding: 0 -> 0 net.inet6.ip6.accept_rtadv: 0 -> 1 dc0: DAD complete for fe80:0001::0200:f8ff:fe10:6ef3 - no duplicates found dc0: starting DAD for 3ffe:0780:0060:0001:0200:f8ff:fe10:6ef3 dc0: DAD complete for 3ffe:0780:0060:0001:0200:f8ff:fe10:6ef3 - no duplicates found . (Note the error messages from route(8) about mid-way through.) This output was produced from the last version of scripts you posted to -current, and with the only relevent change I made to /etc/rc.conf was to set ipv6_enable="YES". After *completing* a multiuser boot, attempting to set the default scoped route correctly installed an entry in the routing table, using exactly the same command that /etc/rc.network6 would have generated: /sbin/route add -inet6 fe80:: fe80::1%lo0 -prefixlen 10 -interface \ -cloning I was wondering if there was somehow a race condition with the first DAD for dc0 not completing, but I put a long sleep at the start of network6_pass1() and it didn't seem to help. > > Finally, could you say whether or not lo0 should really be the default > > value for ipv6_default_interface in /etc/defaults/rc.conf? I have this > > vague feeling it's wrong but I don't know enough to say why: > > > > > +ipv6_default_interface="lo0" # Default output interface for scoped a > ddrs. > > Maybe your concern is that packets to the default interface > should be sent out to outside of host, at least? I think that's it, yes. > On the other hand, I thought there should be some default > interface by default, but I afraid that an approach of just > choosing some interface as default interface might be end up > to choose non working interface. > But now I feel choosing lo0 approach is also somewhat strange. > > So I'll try following approach. > > -"ipv6_default_interface" is empty by default > -When all of "ipv6_network_interfaces", "gif_interfaces", > and "ipv6_default_interface" are empty, then there will be > no default interface > -When "ipv6_default_interface" are empty but > "ipv6_network_interfaces" and/or "gif_interfaces" is not empty, > then choose one default interface from there. I like your approach, although I admit that I'm learning much of this as we go along. Small nitpick: You might want to move the line for ipv6_default_interface higher in /etc/defaults/rc.conf so that it is just below the rest of the definitions that begin with ipv6_*. Thanks! Bruce. --==_Exmh_1967159241P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 8BTkqFzpNO3aW89CxA+usgMEP4tl3GOI iQA/AwUBOLF4a9jKMXFboFLDEQIgpgCgoVTDdJEGRFJZ3gIvBf7RAK1C4xAAoNe7 cgmgNUvboKaYXxFo6oXckXJh =89pK -----END PGP SIGNATURE----- --==_Exmh_1967159241P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 9:47:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 6629937B528 for ; Mon, 21 Feb 2000 09:47:31 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id JAA27724; Mon, 21 Feb 2000 09:47:31 -0800 (PST) Message-Id: <200002211747.JAA27724@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue , bauer@cc.univie.ac.at, current@FreeBSD.ORG Cc: bmah@california.sandia.gov Subject: Re: IPv6 In-Reply-To: <200002211739.JAA27499@nimitz.ca.sandia.gov> References: <20000216034713O.shin@nd.net.fujitsu.co.jp> <20000218215940K.shin@nd.net.fujitsu.co.jp> <200002190012.QAA11354@nimitz.ca.sandia.gov> <20000219182000U.shin@nd.net.fujitsu.co.jp> <200002211739.JAA27499@nimitz.ca.sandia.gov> Comments: In-reply-to bmah@california.sandia.gov (Bruce A. Mah) message dated "Mon, 21 Feb 2000 09:39:55 -0800." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1986033889P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 21 Feb 2000 09:47:31 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1986033889P Content-Type: text/plain; charset=us-ascii I was babbling on about some problems and somehow got cut off by my mailer: > Well...not quite, and I am not sure why. Following is a snippit of the > bootup messages from a CURRENT machine (approximately -20000220): > > dc0: starting DAD for fe80:0001::0200:f8ff:fe10:6ef3 > dc0: flags=8843 mtu 1500 > inet 146.246.243.57 netmask 0xffffff00 broadcast 146.246.243.255 > inet6 fe80::200:f8ff:fe10:6ef3%dc0 prefixlen 64 tentative > ether 00:00:f8:10:6e:f3 > media: 100baseTX status: active > supported media: autoselect 100baseTX 100baseTX 10baseT > /UT > P 10baseT/UTP 100baseTX none > lo0: flags=8049 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > add net default: gateway 146.246.243.254 > Additional routing options: TCP keepalive=YES. > routing daemons:. > Doing IPv6 network setup:route: writing to routing socket: Network is unreach > able > add net fe80::: gateway fe80::1%lo0: Network is unreachable > route: writing to routing socket: Network is unreachable > add net ff02::: gateway fe80::1%lo0: Network is unreachable > add net ::ffff:0.0.0.0: gateway ::1 > add net ::0.0.0.0: gateway ::1 > net.inet6.ip6.forwarding: 0 -> 0 > net.inet6.ip6.accept_rtadv: 0 -> 1 > dc0: DAD complete for fe80:0001::0200:f8ff:fe10:6ef3 - no duplicates found > dc0: starting DAD for 3ffe:0780:0060:0001:0200:f8ff:fe10:6ef3 > dc0: DAD complete for 3ffe:0780:0060:0001:0200:f8ff:fe10:6ef3 - no duplicates > found Note that two invocations of route(8) failed about mid-way through. I can't figure out why, but manually typing the route commands after boot-up seemed to go just fine (no error messages, and routes installed correctly): route add -inet6 fe80:: fe80:;1%lo0 -prefixlen 10 -interface -cloning route add -inet6 ff02:: fe80::1%lo0 -prefixlen 16 -interface -cloning As far as your plan for determining the default scoped interface route, it sounds good to this newbie. One nitpick might be to move the ipv6_default_interface line in /etc/defaults/rc.conf so that it is next to the other definitions that begin with ipv6_*. Thanks! Bruce. --==_Exmh_1986033889P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 32ZB22PJf/mrjnW5oo0SMQyAH7D3q3Jj iQA/AwUBOLF6MtjKMXFboFLDEQLejQCg8DnEICbwEHLVrw+OPk3WCqAVKTcAoJmf U3PmjWpGhzs2hhxFOU9js8yN =/AxI -----END PGP SIGNATURE----- --==_Exmh_1986033889P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 9:48:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id B1AE037B92D for ; Mon, 21 Feb 2000 09:48:28 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id SAA22827 for ; Mon, 21 Feb 2000 18:40:46 +0100 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id SAA02038 for ; Mon, 21 Feb 2000 18:42:24 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C125688C.0061C582 ; Mon, 21 Feb 2000 18:47:55 +0100 X-Lotus-FromDomain: ALCATEL To: current@freebsd.org Message-ID: Date: Mon, 21 Feb 2000 18:47:48 +0100 Subject: can't load if_xl module at startup Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've just added a 3c900 NIC in my 4.0 machine. Not wanting to recompile my kernel, I've tried to kldload the if_xl module. When I load the if_xl module "by hand", all is well : the miibus is also loaded and everything's fine (xl0 appears in ifconfig -a ...) When I try to load the if_xl and miibus modules via the loader, the loader spins in : "/modules/miibus.ko text=XXXX data=YYYY syms=[ZZZZ] loading required module 'if_miibus' " .... at infinitum my loader.conf : # -- sysinstall generated deltas -- # userconfig_script_load="YES" miibus_load="YES" # miibus support, needed for some drivers if_xl_load="YES" My system version : pc-bsd103% uname -a FreeBSD pc-bsd103.ZZZZ.telspace.alcatel.fr 4.0-20000214-CURRENT FreeBSD 4.0-2 0000214-CURRENT #1: Mon Feb 21 18:36:37 CET 2000 herbelot@pc-bsd103.ZZZZ. telspace.alcatel.fr:/usr/src/sys/compile/P5-ep i386 pc-bsd103% Net result : one more kernel recompile (this time, it works !) TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 10:20: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 91D0337B515 for ; Mon, 21 Feb 2000 10:19:58 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA238716; Mon, 21 Feb 2000 13:19:45 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <00e201bf7c82$fc123e70$16280c0a@sos> References: <00e201bf7c82$fc123e70$16280c0a@sos> Date: Mon, 21 Feb 2000 13:20:08 -0500 To: "Morten Seeberg" , From: Garance A Drosihn Subject: Re: Things to consider in CURRENT Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:47 PM +0100 2/21/00, Morten Seeberg wrote: >Hi, I just installed: FreeBSD fw.home 4.0-20000208-CURRENT and have a few >comments: > >It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this out >for it self? One day when installing BSD without X (which automatically >installs Combat 3.x) I couldnt start it without. How did you do the install? Did you do an "install from scratch", or did you build over a system you already had running a previous release of freebsd? --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 10:56: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from crap.31337.net (p.funk.org [194.109.61.126]) by hub.freebsd.org (Postfix) with ESMTP id 2D7E537B526 for ; Mon, 21 Feb 2000 10:55:56 -0800 (PST) (envelope-from alexlh@z.funk.org) Received: from z.funk.org (z [10.0.0.2]) by crap.31337.net (8.9.3/8.9.1) with ESMTP id TAA16011 for ; Mon, 21 Feb 2000 19:55:51 +0100 (CET) (envelope-from alexlh@z.funk.org) Received: (from alexlh@localhost) by z.funk.org (8.9.3/8.9.1) id TAA52552 for freebsd-current@freebsd.org; Mon, 21 Feb 2000 19:54:07 +0100 (CET) (envelope-from alexlh) Date: Mon, 21 Feb 2000 19:51:37 +0100 From: Alex Le Heux To: freebsd-current@freebsd.org Subject: Crashing netscape? Message-ID: <20000221195137.D50580@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Am I the only one who's experiencing an amzing amount of crashes on Netscape? It's been going on for quite some time now (months), upgrading Netscape or switching from the Linux to the FreeBSD to the BSDI version doesn't help. The most stable version seems to be the Linux version, but that even crashes 5-10 times per day. It will *always* crash when a page uses java, but I've not been able to find a non-java page that will always crash it. Is it just me? All the people I know who run various versions of FreeBSD say it's not so bad. Alex -- "What is this talk of 'release'? We do not make software 'releases'. Our software 'escapes', leaving a bloody trail of designers and quality assurance people in its wake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 11: 2: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0545F37B52E for ; Mon, 21 Feb 2000 11:01:56 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id LAA07173; Mon, 21 Feb 2000 11:30:06 -0800 (PST) Date: Mon, 21 Feb 2000 11:30:06 -0800 From: Alfred Perlstein To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000221113005.R21720@fw.wintelcom.net> References: <20000221195137.D50580@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000221195137.D50580@funk.org>; from alexlh@funk.org on Mon, Feb 21, 2000 at 07:51:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alex Le Heux [000221 11:25] wrote: > Hi, > > Am I the only one who's experiencing an amzing amount of crashes on > Netscape? > > It's been going on for quite some time now (months), upgrading Netscape or > switching from the Linux to the FreeBSD to the BSDI version doesn't help. > The most stable version seems to be the Linux version, but that even > crashes 5-10 times per day. It will *always* crash when a page uses java, > but I've not been able to find a non-java page that will always crash it. > > Is it just me? All the people I know who run various versions of FreeBSD > say it's not so bad. I'm pretty much forced to turn off javascript and java otherwise I have the same problem. Hopefully mozilla will become a viable replacement soon. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 11: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 16D2737BC63 for ; Mon, 21 Feb 2000 11:03:58 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id OAA88366; Mon, 21 Feb 2000 14:02:56 -0500 Date: Mon, 21 Feb 2000 14:02:56 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <20000221195137.D50580@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You arent the only one, I have tried nestcape 4.08 and 4.7 navigator and both exit on signal 10 and coredump quite often. It happens in the middle of page rendering and also everytime I try to close the application (rare since I hardly ever get the chance to do that myself). I dont know why it does that. I can't seem to tell that there is any definite pattern to it, or that anything in particular triggers it. I just deal with it, and lately I just do most of my browsing on a different machine with a different OS :/. Trying Mozilla M13 now, and it doesnt seem to be as bad although it still doesnt render pages correctly most of the time. -Will On Mon, 21 Feb 2000, Alex Le Heux wrote: > Hi, > > Am I the only one who's experiencing an amzing amount of crashes on > Netscape? > > It's been going on for quite some time now (months), upgrading Netscape or > switching from the Linux to the FreeBSD to the BSDI version doesn't help. > The most stable version seems to be the Linux version, but that even > crashes 5-10 times per day. It will *always* crash when a page uses java, > but I've not been able to find a non-java page that will always crash it. > > Is it just me? All the people I know who run various versions of FreeBSD > say it's not so bad. > > Alex > > -- > "What is this talk of 'release'? We do not make software > 'releases'. Our software 'escapes', leaving a > bloody trail of designers and quality assurance people in its > wake." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 11:34: 2 2000 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 CDA3737B517; Mon, 21 Feb 2000 11:33:52 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id OAA01576; Mon, 21 Feb 2000 14:33:45 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA26958; Mon, 21 Feb 2000 14:33:15 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id OAA15574; Mon, 21 Feb 2000 14:33:14 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200002211933.OAA15574@bb01f39.unx.sas.com> Subject: 4.0-current and elm2.4.ME+.68 segv To: freebsd-current@freebsd.org Date: Mon, 21 Feb 2000 14:33:14 -0500 (EST) Cc: ache@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been installing 4.0-current and testing it. One of the problems I've found is with the port elm2.4.ME+.68 ... /usr/ports/mail/elm/work/elm2.4.ME+.68/lib/can_open.c function 'can_open()' checks for the presence of the mail folder (which doesn't exist). It returns an appropriate error. Unfortunately, we seem to loose the bad rc. /usr/ports/mail/elm/work/elm2.4.ME+.68/lib/mail_gets.c function 'mail_gets()' is called later with a NULL filepointer which is then passed to feof() and ferror(). Starting "./bin/elm " elm:\elm.c\main 42 > g SIGSEGV - Segmentation violation. elm:\mail_gets.c\mail_gets 31 (+0x6) int mail_gets(buffer, size, mailfile) char *buffer; int size; FILE *mailfile; { register int line_bytes = 0, ch; register char *c = buffer; size--; /* allow room for zero terminator on end, just in case */ 31->>> while (!feof(mailfile) && !ferror(mailfile) && line_bytes < size) { ch = getc(mailfile); /* Macro, faster than fgetc() ! */ Note, the above all works correctly if you actually have a valid mail folder. The following patch fixes the problem, though I don't beleive it is truely the correct fix. --- lib/mail_gets.c.orig Fri Jan 21 04:26:05 2000 +++ lib/mail_gets.c Mon Feb 21 14:24:40 2000 @@ -26,6 +26,11 @@ register int line_bytes = 0, ch; register char *c = buffer; + if (!mailfile) { + *c = 0; /* Actually this should NOT be needed.. */ + return line_bytes; + } + size--; /* allow room for zero terminator on end, just in case */ while (!feof(mailfile) && !ferror(mailfile) && line_bytes < size) { Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 11:43:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 13CCA37B52E for ; Mon, 21 Feb 2000 11:43:15 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA19131; Mon, 21 Feb 2000 14:12:05 -0500 (EST) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA16536; Mon, 21 Feb 2000 14:11:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA16532; Mon, 21 Feb 2000 14:11:55 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Mon, 21 Feb 2000 14:11:54 -0500 (EST) From: Kenneth Wayne Culver To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <20000221195137.D50580@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may want to try upgrading your linux libraries... they may be old... I don't have these problems though... Netscape rarely crashes for me. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Mon, 21 Feb 2000, Alex Le Heux wrote: > Hi, > > Am I the only one who's experiencing an amzing amount of crashes on > Netscape? > > It's been going on for quite some time now (months), upgrading Netscape or > switching from the Linux to the FreeBSD to the BSDI version doesn't help. > The most stable version seems to be the Linux version, but that even > crashes 5-10 times per day. It will *always* crash when a page uses java, > but I've not been able to find a non-java page that will always crash it. > > Is it just me? All the people I know who run various versions of FreeBSD > say it's not so bad. > > Alex > > -- > "What is this talk of 'release'? We do not make software > 'releases'. Our software 'escapes', leaving a > bloody trail of designers and quality assurance people in its > wake." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 11:54:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5739537BE28 for ; Mon, 21 Feb 2000 11:54:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA22414; Mon, 21 Feb 2000 11:50:58 -0800 Date: Mon, 21 Feb 2000 11:50:46 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It crashes for me a lot. There's some deal about fonts, oddly enough, which causes it to crash right away- see the installation instructions that come out when you install communicator-47- it said something about mkfontdir. It still crashes or wedges for me a lot, though. I tried mozilla, and that was worse. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 12: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 7DEAB37B543 for ; Mon, 21 Feb 2000 12:02:02 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e1LK1a915911 for ; Mon, 21 Feb 2000 13:01:37 -0700 (MST) Message-Id: <200002212001.e1LK1a915911@orthanc.ab.ca> To: current@freebsd.org Subject: status of 'device awe' ? Organization: The Frobozz Magic Homing Pigeon Company Date: Mon, 21 Feb 2000 13:01:36 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG LINT has an entry for an 'awe' device, however there doesn't appear to be any corresponding source code in the tree. Is this device dead? If so, the entry should be removed from LINT, or an appropriate comment added. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 12: 3:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 300DE37B517 for ; Mon, 21 Feb 2000 12:03:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA13460; Mon, 21 Feb 2000 12:03:31 -0800 (PST) (envelope-from dillon) Date: Mon, 21 Feb 2000 12:03:31 -0800 (PST) From: Matthew Dillon Message-Id: <200002212003.MAA13460@apollo.backplane.com> To: Matthew Jacob Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It crashes for me a lot. There's some deal about fonts, oddly enough, which :causes it to crash right away- see the installation instructions that come out :when you install communicator-47- it said something about mkfontdir. : :It still crashes or wedges for me a lot, though. I tried mozilla, and that was :worse. Hmm. This sounds worse then usual. Make sure you are running netscape with appropriate resource limits. unlimit data limit descriptors 200 (The data limit should be at least 128 megabytes) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 12:10:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2D55337BF30 for ; Mon, 21 Feb 2000 12:10:39 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA12001; Mon, 21 Feb 2000 13:09:16 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2000 13:09:16 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000221130916.A11980@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Mon, Feb 21, 2000 at 11:50:46AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 11:50:46 -0800, Matthew Jacob wrote: > > It crashes for me a lot. There's some deal about fonts, oddly enough, which > causes it to crash right away- see the installation instructions that come out > when you install communicator-47- it said something about mkfontdir. > > It still crashes or wedges for me a lot, though. I tried mozilla, and that was > worse. For me at least, slashdot seems to make netscape crash eventually. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 12:20:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A1BE137B63E for ; Mon, 21 Feb 2000 12:20:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA22525; Mon, 21 Feb 2000 12:20:17 -0800 Date: Mon, 21 Feb 2000 12:20:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <200002212003.MAA13460@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :It crashes for me a lot. There's some deal about fonts, oddly enough, which > :causes it to crash right away- see the installation instructions that come out > :when you install communicator-47- it said something about mkfontdir. > : > :It still crashes or wedges for me a lot, though. I tried mozilla, and that was > :worse. > > Hmm. This sounds worse then usual. Make sure you are running netscape > with appropriate resource limits. > > unlimit data > limit descriptors 200 > > (The data limit should be at least 128 megabytes) Yep - 512MB data, 552 file descriptors. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 12:25: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from crap.31337.net (p.funk.org [194.109.61.126]) by hub.freebsd.org (Postfix) with ESMTP id 89C2D37B528 for ; Mon, 21 Feb 2000 12:24:53 -0800 (PST) (envelope-from alexlh@z.funk.org) Received: from z.funk.org (z [10.0.0.2]) by crap.31337.net (8.9.3/8.9.1) with ESMTP id VAA16608; Mon, 21 Feb 2000 21:24:48 +0100 (CET) (envelope-from alexlh@z.funk.org) Received: (from alexlh@localhost) by z.funk.org (8.9.3/8.9.1) id VAA65093; Mon, 21 Feb 2000 21:23:03 +0100 (CET) (envelope-from alexlh) Date: Mon, 21 Feb 2000 21:23:03 +0100 From: Alex Le Heux To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000221212303.F50580@funk.org> References: <200002212003.MAA13460@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1i In-Reply-To: <200002212003.MAA13460@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 21, 2000 at 12:03:31PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My limits are quite high I thinkL z:~ $ limits Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuse infinity kb memorylocked infinity kb maxprocesses 1043 openfiles 2088 sbsize infinity bytes On Mon, Feb 21, 2000 at 12:03:31PM -0800, Matthew Dillon wrote: > > :It crashes for me a lot. There's some deal about fonts, oddly enough, which > :causes it to crash right away- see the installation instructions that come out > :when you install communicator-47- it said something about mkfontdir. > : > :It still crashes or wedges for me a lot, though. I tried mozilla, and that was > :worse. > > Hmm. This sounds worse then usual. Make sure you are running netscape > with appropriate resource limits. > > unlimit data > limit descriptors 200 > > (The data limit should be at least 128 megabytes) > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- "What is this talk of 'release'? We do not make software 'releases'. Our software 'escapes', leaving a bloody trail of designers and quality assurance people in its wake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 13: 6:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id BA67937B591 for ; Mon, 21 Feb 2000 13:06:17 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.freenet.de) by mout0.freenet.de with esmtp (Exim 3.13 #1) id 12N01T-0005uC-00; Mon, 21 Feb 2000 22:05:39 +0100 Received: from [213.6.170.130] (helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.13 #1) id 12N01K-0002AR-00; Mon, 21 Feb 2000 22:05:30 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id VAA00810; Mon, 21 Feb 2000 21:56:50 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200002212056.VAA00810@Magelan.Leidinger.net> Date: Mon, 21 Feb 2000 21:56:49 +0100 (CET) From: Alexander Leidinger Subject: Re: Crashing netscape? To: ken@kdm.org Cc: mjacob@feral.com, alexlh@funk.org, freebsd-current@FreeBSD.ORG In-Reply-To: <20000221130916.A11980@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21 Feb, Kenneth D. Merry wrote: >> It crashes for me a lot. There's some deal about fonts, oddly enough, which >> causes it to crash right away- see the installation instructions that come out >> when you install communicator-47- it said something about mkfontdir. >> >> It still crashes or wedges for me a lot, though. I tried mozilla, and that was >> worse. > > For me at least, slashdot seems to make netscape crash eventually. With Javascript+CSS enabled: Go to /., dig into an article (read more), hit the back button -> crash (most of the time). Turn of Javascript (this disables CSS too), repeat above algorithm -> no crash (most of the time). Bye, Alexander. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 13:18:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id CB32837B891; Mon, 21 Feb 2000 13:18:20 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA63806; Mon, 21 Feb 2000 16:17:57 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000219114547.T21720@fw.wintelcom.net> References: <20000219022149.N21720@fw.wintelcom.net> <20000219114547.T21720@fw.wintelcom.net> Date: Mon, 21 Feb 2000 16:18:21 -0500 To: Alfred Perlstein , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: "Fixing" init. Cc: jkh@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:45 AM -0800 2/19/00, Alfred Perlstein wrote: >* Alfred Perlstein [000219 02:22] wrote: > > I remeber being a newbie and getting burned by the need to explicitly > > turn a line 'off' in my /etc/ttys file instead of simply deleting it. > > > > This fixes it using a trivial mark then collect sweep. > > > > Can a couple people take a look? I'd like to get it into 4.0 because > > it seems to follow POLA better. > > > > "hey i deleted and HUP'd but init keeps spawing them!" > >ok, NetBSD has had this fixed for _several years_, and they use bitmasks >in the se_flags field, here's an updated patch that's essentially the >same as the old one but using NetBSD's se_flags implementation. > >4.0 please? :) For what it's worth, I like this idea. I must admit I have not tested it, because the disk I was *going* to use to build a 4.0 system seems to be utterly dead right now (hardware-wise). Sigh. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 13:54:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 29B1137BF66 for ; Mon, 21 Feb 2000 13:54:34 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 40615 invoked from network); 21 Feb 2000 21:54:31 -0000 Received: from d122.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.122]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 21 Feb 2000 21:54:31 -0000 Message-ID: <38B1B330.E9AF426F@cybercable.fr> Date: Mon, 21 Feb 2000 22:50:40 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? References: <200002212056.VAA00810@Magelan.Leidinger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've found that /. can be very reliably be surfed with the web-board included in the KDE file manager (KFM - at least for my present 1.1.2 release) TfH Alexander Leidinger wrote: > > On 21 Feb, Kenneth D. Merry wrote: > > >> It crashes for me a lot. There's some deal about fonts, oddly enough, which > >> causes it to crash right away- see the installation instructions that come out > >> when you install communicator-47- it said something about mkfontdir. > >> > >> It still crashes or wedges for me a lot, though. I tried mozilla, and that was > >> worse. > > > > For me at least, slashdot seems to make netscape crash eventually. > > With Javascript+CSS enabled: > Go to /., dig into an article (read more), hit the back button > -> crash (most of the time). > > Turn of Javascript (this disables CSS too), repeat above algorithm > -> no crash (most of the time). > > Bye, > Alexander. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 14:11:58 2000 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 9DD3437B706 for ; Mon, 21 Feb 2000 14:11:55 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA05393; Mon, 21 Feb 2000 17:11:44 -0500 (EST) (envelope-from wollman) Date: Mon, 21 Feb 2000 17:11:44 -0500 (EST) From: Garrett Wollman Message-Id: <200002212211.RAA05393@khavrinen.lcs.mit.edu> To: "Victor A. Salaman" Cc: freebsd-current@FreeBSD.ORG Subject: RE: openssl in -current In-Reply-To: <1D45ABC754FB1E4888E508992CE97E4F059CE8@teknos.teknos.com> References: <1D45ABC754FB1E4888E508992CE97E4F059CE8@teknos.teknos.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Perhaps we should send e-mail to RSA to clarify this, and in light of this, > ask for permission to distribute RSA with the base OS. Gee, we can get RSA > anyway, so what's the point on making harder? Heh. A couple of years ago, RSA Data Security, Inc., was purchased by another company, also in the security business. The chairman of the acquiring company told a reporter, ``All we were really after was an RSA license, but it turned out to be easier to just buy the whole company.'' -GAWollman Disclaimer: I work for the assignee (``owner'') of the RSA patent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 14:48:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by hub.freebsd.org (Postfix) with ESMTP id 27DE437B58C for ; Mon, 21 Feb 2000 14:48:14 -0800 (PST) (envelope-from nilsnorden@telia.com) Received: from d1o19.telia.com (d1o19.telia.com [195.67.224.241]) by mailg.telia.com (8.9.3/8.9.3) with ESMTP id XAA01543 for ; Mon, 21 Feb 2000 23:47:58 +0100 (CET) Received: from telia.com (t5o19p19.telia.com [195.67.225.19]) by d1o19.telia.com (8.8.8/8.8.8) with ESMTP id XAA02645 for ; Mon, 21 Feb 2000 23:47:57 +0100 (CET) Message-ID: <38B1C10D.6F21C055@telia.com> Date: Mon, 21 Feb 2000 23:49:49 +0100 From: Nils =?iso-8859-1?Q?Nord=E9n?= X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: When is the estimated release of the FreeBSD-current 4.0? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When is the estimated release of the FreeBSD-current 4.0? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 15: 1:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id C6B1137B58E for ; Mon, 21 Feb 2000 15:01:39 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id AAA07498 for current@FreeBSD.ORG; Tue, 22 Feb 2000 00:01:16 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id XAA01325 for current@FreeBSD.ORG; Mon, 21 Feb 2000 23:55:19 +0100 (CET) (envelope-from andreas) Date: Mon, 21 Feb 2000 23:55:18 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000221235518.A998@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I have hangs and timeouts using the EIDE disk in my computer. The controller is a Abit Hot Rod 66 and Maxtor Diamond Max 54098U8. I use the 80 pin cable from the Abit EIDE controller special for UDMA. Messages are: ad4: READ command timeout - resetting ata2: resetting devices ad4: WRITE command timeout - resetting ata2: resetting devices .. done Sometimes the disk recovers, sometimes the system completely hangs. One time when mounting a 18 GB filesystem I got the panic: ffs_alloc: map corrupted mp_lock=01000001; cpuid=1; lapic_id=01000000 First I thought, it is related to IRQ sharing. My Matrox Millenium PCI card shared the same interrupt as the Abit EIDE controller (BTW, on board EIDE controller - UDMA/33 - is disabled on my Tyan Titan Pro board). dmesg output and kernel config file: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Feb 21 20:40:55 CET 2000 root@:/usr/src/sys/compile/TITAN Calibrating clock(s) ... TSC clock: 199425363 Hz, i8254 clock: 1193142 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 159383552 (155648K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00345000 - 0x097f5fff, 155914240 bytes (38065 pages) avail memory = 150917120 (147380K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 15 IOAPIC #0 intpin 17 -> irq 11 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 19 -> irq 14 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00fac30 bios32: Entry = 0xfb0b0 (c00fb0b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb0e0 pnpbios: Found PnP BIOS data at 0xc00fbc30 pnpbios: Entry = f0000:bc58 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0329000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x10b7, dev=0x9001, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base 00009400, size 6 found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base e0000000, size 14 map[14]: type 1, range 32, base e1000000, size 23 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 00009800, size 8 map[14]: type 1, range 32, base e2000000, size 12 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00009c00, size 3 map[14]: type 1, range 32, base 0000a000, size 2 map[20]: type 1, range 32, base 0000a400, size 8 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 0000a800, size 3 map[14]: type 1, range 32, base 0000ac00, size 2 map[20]: type 1, range 32, base 0000b000, size 8 pci0: on pcib0 isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: IRQ15, B: IRQ11, C: IRQ10, D: IRQ14 MB0: , MB1: isa0: on isab0 atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata0: mask=00 status0=ff status1=ff ata0: probe allocation failed ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0001 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed xl0: <3Com 3c900-COMBO Etherlink XL> port 0x9400-0x943f irq 14 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: media options word: e138 xl0: found 10baseT xl0: found AUI xl0: found BNC xl0: selecting 10baseT transceiver, half duplex bpf: xl0 attached pci0: Matrox MGA Millennium 2064W graphics accelerator (vendor=0x102b, dev=0x0519) at 12.0 irq 10 ahc0: port 0x9800-0x98ff mem 0xe2000000-0xe2000fff irq 11 at device 13.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable not present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: Low byte termination Enabled ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 413 instructions downloaded atapci1: port 0xa400-0xa4ff,0xa000-0xa003,0x9c00-0x9c07 irq 15 at device 14.0 on pci0 ata2: iobase=0x9c00 altiobase=0xa000 bmaddr=0xa400 ata2: mask=03 status0=50 status1=00 ata2: mask=03 status0=50 status1=00 ata2: devices = 0x1 ata2: at 0x9c00 on atapci1 atapci2: port 0xb000-0xb0ff,0xac00-0xac03,0xa800-0xa807 irq 15 at device 14.1 on pci0 ata3: iobase=0xa800 altiobase=0xac00 bmaddr=0xb000 ata3: mask=03 status0=20 status1=30 ata3: mask=03 status0=20 status1=30 ata3: devices = 0x0 ata3: probe allocation failed Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 devclass_alloc_unit: ata0 already exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff fb: new array size 4 sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 5 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) bpf: ed0 attached ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata4: mask=00 status0=ff status1=ff ata4: probe allocation failed isa_probe_children: probing PnP devices SMP: enabled INTs: 1, 3, 4, 5, 6, 7, 11, 12, 14, 15, apic_imen: 0x00ff2705 BIOS Geometries: 0:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 1:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 2:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 3:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 4:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default DUMMYNET initialized (000106) bpf: lo0 attached Linux-ELF exec handler installed SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ata2-master: success setting up UDMA4 mode on HPT366 chip ad4: ATA-5 disk at ata2 as master ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad4 Creating DISK wd4 Waiting 8 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: target 6 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 synchronous at 20.0MHz, offset = 0xf ahc0: target 3 synchronous at 20.0MHz, offset = 0xf ahc0: target 2 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 Creating DISK cd0 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 5U6G6557 pass0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number 5U2N3906 pass1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 5U312691 pass2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled pass3 at ahc0 bus 0 target 3 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number 5U323663 pass3: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled pass4 at ahc0 bus 0 target 6 lun 0 pass4: Removable CD-ROM SCSI-2 device pass4: Serial Number 8704381B pass4: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s2a (cd0:ahc0:0:6:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:6:0): NOT READY asc:3a,0 (cd0:ahc0:0:6:0): Medium not present cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: Serial Number 8704381B cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number 5U2N3906 da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number 5U323663 da3: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 5U6G6557 da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number 5U312691 da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0s1: type 0xb, start 63, end = 1638629, size 1638567 : OK da0s2: type 0xa5, start 1638630, end = 4225094, size 2586465 : OK start_init: trying /sbin/init da1s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK da2s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK da3s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK ad4s1: type 0xb, start 63, end = 8193149, size 8193087 : OK ad4s2: type 0xf, start 8193150, end = 32772599, size 24579450 : OK ad4s3: type 0xa5, start 32772600, end = 80035829, size 47263230 : OK ad4s5: type 0xb, start 8193213, end = 16386299, size 8193087 : OK ad4: type 0x5, start 16386300, end = 24579449, size 8193150 : OK ad4s6: type 0xb, start 16386363, end = 24579449, size 8193087 : OK ad4: type 0x5, start 24579450, end = 32162129, size 7582680 : OK ad4s7: type 0xb, start 24579513, end = 32162129, size 7582617 : OK ad4: type 0x5, start 32162130, end = 32772599, size 610470 : OK ad4s8: type 0x6, start 32162193, end = 32772599, size 610407 : OK ad4s1: type 0xb, start 63, end = 8193149, size 8193087 : OK ad4s2: type 0xf, start 8193150, end = 32772599, size 24579450 : OK ad4s3: type 0xa5, start 32772600, end = 80035829, size 47263230 : OK ad4s5: type 0xb, start 8193213, end = 16386299, size 8193087 : OK ad4: type 0x5, start 16386300, end = 24579449, size 8193150 : OK ad4s6: type 0xb, start 16386363, end = 24579449, size 8193087 : OK ad4: type 0x5, start 24579450, end = 32162129, size 7582680 : OK ad4s7: type 0xb, start 24579513, end = 32162129, size 7582617 : OK ad4: type 0x5, start 32162130, end = 32772599, size 610470 : OK ad4s8: type 0x6, start 32162193, end = 32772599, size 610407 : OK splash: image decoder found: daemon_saver xl0: promiscuous mode enabled xl0: promiscuous mode disabled (da0:ahc0:0:0:0): tagged openings now 32 (da1:ahc0:0:1:0): tagged openings now 32 (da3:ahc0:0:3:0): tagged openings now 32 (da2:ahc0:0:2:0): tagged openings now 32 # # Kernel Config File: TITAN # # by Andreas Klemm, Sat Sep 25 21:30:05 CEST 1999 # machine i386 cpu I686_CPU ident TITAN maxusers 100 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE #Include this file in kernel options INET #Internet communications protocols #option INET6 #IPv6 communications protocols #option IPSEC #IP security #option IPSEC_ESP #IP security (crypto; define w/ IPSEC) #option IPSEC_IPV6FWD #IP security tunnel for IPv6 ##options IPSEC_DEBUG #debug for IP security options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES #Softupdates options MD5 options NSWAPDEV=4 options COMPAT_LINUX options SHOW_BUSYBUFS options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options USER_LDT #options IPX #IPX/SPX communications protocols #options NCP #NetWare Core protocol #options NETATALK #Appletalk communications protocols #options CODA #CODA filesystem. #pseudo-device vcoda 4 #coda minicache <-> venus comm. # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=40960 # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs # Options for the VM subsystem #options PQ_NOOPT # No coloring #options PQ_LARGECACHE # color for 512k/16k cache options PQ_HUGECACHE # color for 1024k/16k cache device isa0 #device pnp0 # PnP support for ISA device pci0 # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. device ahc0 # AHA2940 and onboard AIC7xxx devices # SCSI Options options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options AHC_ALLOW_MEMIO # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. device scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? irq 7 device ppbus0 # Parallel port bus (required) device lpt0 at ppbus? # Printer device plip0 at ppbus? # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device #device vpo0 at ppbus? # Requires scbus and da0 # Network Options options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPDIVERT #divert sockets options ICMP_BANDLIM options DUMMYNET # PCI Ethernet NICs that use the common MII bus controller code. device miibus0 # MII bus support device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # The probe order of these is presently determined by i386/isa/isa_compat.c. device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. # The `gif' pseudo-device implements IPv6 over IP4 tunneling, # IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling and # IPv6 over IPv6 tunneling. # The `faith' pseudo-device captures packets sent to it and diverts them # to the IPv4/IPv6 translation daemon. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # for IPv6 #pseudo-device gif 4 #IPv6 and IPv4 tunneling #pseudo-device faith 1 #for IPv6 and IPv4 translation # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver # Luigis new sound driver #device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 # for lmmon device smbus0 device iicbus0 device iicbb0 device intpm0 device smb0 at smbus? # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 16: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id DD63737B529 for ; Mon, 21 Feb 2000 16:01:59 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-2.blackbox-2.netaxs.com [207.106.60.2]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id SAA26253; Mon, 21 Feb 2000 18:56:58 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id SAA00642; Mon, 21 Feb 2000 18:56:42 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Mon, 21 Feb 2000 18:56:41 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <20000221195137.D50580@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Feb 2000, Alex Le Heux wrote: >Hi, > >Am I the only one who's experiencing an amzing amount of crashes on >Netscape? > >It's been going on for quite some time now (months), upgrading Netscape or >switching from the Linux to the FreeBSD to the BSDI version doesn't help. >The most stable version seems to be the Linux version, but that even >crashes 5-10 times per day. It will *always* crash when a page uses java, >but I've not been able to find a non-java page that will always crash it. Netscape would always crash on me when loading a java applet - I found that if you define both the scaled and unscaled fonts in XF86Config as below that all the java related crashes go away. It still crashes occasionally on complex pages that load up a million different frames, though. Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" ModulePath "/usr/X11R6/lib/modules" EndSection Hope this helps. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 16:19:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id B5A8837B54D for ; Mon, 21 Feb 2000 16:19:23 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id BAA11300; Tue, 22 Feb 2000 01:15:20 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id BAA02082; Tue, 22 Feb 2000 01:13:14 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 01:13:14 +0100 From: Andreas Klemm To: Ken McKittrick Cc: current@freebsd.org Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222011314.A2059@titan.klemm.gtn.com> References: <20000221235518.A998@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from klmac@twcny.rr.com on Mon, Feb 21, 2000 at 06:43:16PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this settings hw.atamodes: ---,---,---,---,pio,---,---,---,---,---, result still in ad4: WRITE command timeout - resetting ata2: resetting devices .. done ad4: timeout waiting for DRQad4: WRITE command timeout - resetting ata2: resetting devices .. done ad4: timeout waiting for DRQ (was a bonnie -s 100) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 16:23:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id DAF6A37B5AD for ; Mon, 21 Feb 2000 16:23:12 -0800 (PST) (envelope-from jeff@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA03615 for ; Mon, 21 Feb 2000 18:18:55 -0600 (CST) (envelope-from jeff@mountin.net) Received: from dial-65.max1.wa.cyberlynk.net(207.227.118.65) by peak.mountin.net via smap (V1.3) id sma003608; Mon Feb 21 18:18:41 2000 Message-Id: <3.0.3.32.20000221181800.00a2d660@207.227.119.2> X-Sender: jeffm@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 21 Feb 2000 18:18:00 -0600 To: current@FreeBSD.org From: "Jeffrey J. Mountin" Subject: minor nit with 4.0-RC2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nothing major.... Finished a build, installed, and mergemaster points out that the $FreeBSD line is missing from the /etc/group binary install. Only a touch irritating. 'Twas the case with RC1 as well, but when I merged the temp and original version it lumped the ID with a comment and the wheel group line and thus removing my account, which I then promptly forgot to fix. Not this time, however. Only expected one file to differ (motd) without a CVSup. Other than this and the OpenSSL/RSA issue, looking good. Still is odd to see so many commits while in a freeze, but so far no real breakage AFAICR. Surely the commits will slow down fairly soon. ;) Shaping up to be a good release. cheers! Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Mon Feb 21 17:29:14 2000 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 85DA837B5CA for ; Mon, 21 Feb 2000 17:29:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA53404; Mon, 21 Feb 2000 17:25:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Nils =?iso-8859-1?Q?Nord=E9n?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: When is the estimated release of the FreeBSD-current 4.0? In-reply-to: Your message of "Mon, 21 Feb 2000 23:49:49 +0100." <38B1C10D.6F21C055@telia.com> Date: Mon, 21 Feb 2000 17:25:57 -0800 Message-ID: <53387.951182757@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When is the estimated release of the FreeBSD-current 4.0? First week of March. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 17:58:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 27D0137B592 for ; Mon, 21 Feb 2000 17:58:14 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA15435; Mon, 21 Feb 2000 17:35:24 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id RAA52238; Mon, 21 Feb 2000 17:35:24 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA29884; Mon, 21 Feb 2000 17:35:23 -0800 (PST) From: Don Lewis Message-Id: <200002220135.RAA29884@salsa.gv.tsc.tdk.com> Date: Mon, 21 Feb 2000 17:35:22 -0800 In-Reply-To: <20000221195137.D50580@funk.org> References: <20000221195137.D50580@funk.org> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Feb 21, 7:51pm, Alex Le Heux wrote: } Subject: Crashing netscape? } Hi, } } Am I the only one who's experiencing an amzing amount of crashes on } Netscape? } } It's been going on for quite some time now (months), upgrading Netscape or } switching from the Linux to the FreeBSD to the BSDI version doesn't help. } The most stable version seems to be the Linux version, but that even } crashes 5-10 times per day. It will *always* crash when a page uses java, } but I've not been able to find a non-java page that will always crash it. Have you tried "netscape -sync"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 18: 3:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 96E9E37B5B9 for ; Mon, 21 Feb 2000 18:03:22 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 37800 invoked by uid 1001); 22 Feb 2000 01:57:14 -0000 Date: 21 Feb 2000 17:57:14 -0800 Date: Mon, 21 Feb 2000 17:57:14 -0800 From: Bill Swingle To: current@freebsd.org Subject: breakage in make release Message-ID: <20000221175714.A37786@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else seeing this? -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little ===> gnu/usr.bin/binutils/size install -c -s -o root -g wheel -m 555 size /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/libexec/elf ===> gnu/usr.bin/binutils/strings install -c -s -o root -g wheel -m 555 strings /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/libexec/elf ===> gnu/usr.bin/binutils/strip install -c -o root -g wheel -m 555 maybe_stripped /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/libexec/elf/strip ===> gnu/usr.bin/binutils/doc install-info --quiet --defsection="Programming & development tools." --defentry="* As: (as). The GNU assembler." as.info /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry="* Ld: (ld). The GNU linker." ld.info /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry="* GDB annotation: (annotate). Annotations for the GNU Debugger (GDB)." annotate.info /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry="* Gasp: (gasp). The GNU Assembler Macro Preprocessor." gasp.info /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/share/info/dir install-info: No such file or directory for gasp.info *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/doc. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 18:36:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 0E34B37B5F4 for ; Mon, 21 Feb 2000 18:36:27 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 38517 invoked by uid 1001); 22 Feb 2000 02:33:35 -0000 Date: 21 Feb 2000 18:33:35 -0800 Date: Mon, 21 Feb 2000 18:33:35 -0800 From: Bill Swingle To: Thomas Dean Cc: current@FreeBSD.ORG Subject: Re: breakage in make release Message-ID: <20000221183335.B38475@dub.net> References: <20000221175714.A37786@dub.net> <200002220221.SAA25142@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002220221.SAA25142@ix.netcom.com>; from tomdean@ix.netcom.com on Mon, Feb 21, 2000 at 06:21:48PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 06:21:48PM -0800, Thomas Dean wrote: > There were some posts on -current in the past few days about binutils. > I believe they were related. > > Look at the archive on FreeBSD, search current for binutils. Hehe, funny that you would suggest that I should look in the archives since I'm still trying to get them back up again. :) Thanks for the pointer anyway :) -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 19: 9:44 2000 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 B051537B568; Mon, 21 Feb 2000 19:09:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA32354; Mon, 21 Feb 2000 19:05:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: jdp@freebsd.org Cc: peter@freebsd.org, current@freebsd.org Subject: "Interesting" failure mode for static linking with shared libs. Date: Mon, 21 Feb 2000 19:05:47 -0800 Message-ID: <32351.951188747@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG root@zippy-> cc -fPIC -c stub.c root@zippy-> ld -shared -o stub.so stub.o root@zippy-> cc -static test.c -o test stub.so root@zippy-> ./test ELF interpreter /usr/lib/libc.so.1 not found Abort trap root@zippy-> cc -static test.c -o test stub.o root@zippy-> ./test Now in the client, calling doit() You have reached the stub. Please leave a message. As you can see from the first case, linking against the shared library succeeds but generates an executable with rather sub-optimal behavior and a bogus diagnostic to boot (I tried grabbing an old libc.so.1 from the compat dists and installing it in /usr/lib just to see what it would do, it had no effect). I ran across this as part of my continuing efforts to make the openssl library pull in the rsaref code at runtime, something which now works just peachy in the dynamic linking case but does not work in the static linking case. That is to say that if I want to link ssh static, for whatever reason, and I compile it up in the following ways (the names used for the libs aren't exactly correct, I'm just illustrating a point): 1. cc -static ${SSHOBJS} -o ssh -lrsaref -lrsaglue -lssl 2. cc -static ${SSHOBJS} -o ssh -lrsaglue -lssl Then in case #2 the expected happens, e.g. ssh bitches about needing the rsa code and aborts since dlopen() is not available to the rsaglue stub functions I wrote and I'd consider that correct. However, case #1 also causes the very same behavior, and that just mystifies me since I'd have expected the "strong" symbols in librsaref to have been bound to in preference to the weak ones in librsaglue. I've also tried referencing the .a file directly in the link line (cc -static ${SSHOBJS} -o ssh /usr/local/lib/librsaref.a -lrsaglue -lssl) in hopes that this would somehow get it preferred just on that basis alone, but no deal. Urk! Any ideas? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 19:26:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id A5ECD37B5ED for ; Mon, 21 Feb 2000 19:26:50 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id VAA00607; Mon, 21 Feb 2000 21:59:57 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38B1FBAD.448DEE9F@acm.org> Date: Mon, 21 Feb 2000 21:59:57 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Swingle Cc: Thomas Dean , current@FreeBSD.ORG Subject: Re: breakage in make release References: <20000221175714.A37786@dub.net> <200002220221.SAA25142@ix.netcom.com> <20000221183335.B38475@dub.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien committed some changes a few hours ago adding the gasp infodocs into the build. He might have introduced a bug here. Here is the commit message. Jim Bloom bloom@acm.org > obrien 2000/02/21 12:33:32 PST > > Modified files: > gnu/usr.bin/binutils/doc Makefile > gnu/usr.bin/binutils/gasp Makefile > Removed files: > gnu/usr.bin/binutils/gasp/doc Makefile > Log: > Build and install gasp's infodocs along side the other binutil docs rather > than seperately. > > Pointed out by: bde > > Revision Changes Path > 1.4 +3 -2 src/gnu/usr.bin/binutils/doc/Makefile > 1.6 +1 -3 src/gnu/usr.bin/binutils/gasp/Makefile Bill Swingle wrote: > > On Mon, Feb 21, 2000 at 06:21:48PM -0800, Thomas Dean wrote: > > There were some posts on -current in the past few days about binutils. > > I believe they were related. > > > > Look at the archive on FreeBSD, search current for binutils. > > Hehe, funny that you would suggest that I should look in the archives > since I'm still trying to get them back up again. :) > > Thanks for the pointer anyway :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 20: 5:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fb00.eng00.mindspring.net (fb00.eng00.mindspring.net [207.69.200.31]) by hub.freebsd.org (Postfix) with ESMTP id 6350037B52B for ; Mon, 21 Feb 2000 20:05:34 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa16-40.ix.netcom.com [207.93.148.168]) by fb00.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA25833; Mon, 21 Feb 2000 21:22:02 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id SAA25142; Mon, 21 Feb 2000 18:21:48 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Mon, 21 Feb 2000 18:21:48 -0800 (PST) Message-Id: <200002220221.SAA25142@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: unfurl@dub.net Cc: current@FreeBSD.ORG In-reply-to: <20000221175714.A37786@dub.net> (message from Bill Swingle on 21 Feb 2000 17:57:14 -0800) Subject: Re: breakage in make release References: <20000221175714.A37786@dub.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There were some posts on -current in the past few days about binutils. I believe they were related. Look at the archive on FreeBSD, search current for binutils. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 20:12:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F3CED37B583 for ; Mon, 21 Feb 2000 20:12:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA73756; Mon, 21 Feb 2000 20:12:56 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA45107; Mon, 21 Feb 2000 20:13:03 -0800 (PST) (envelope-from obrien) Date: Mon, 21 Feb 2000 20:13:02 -0800 From: "David O'Brien" To: Bill Swingle Cc: current@freebsd.org Subject: Re: breakage in make release Message-ID: <20000221201302.A45085@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000221175714.A37786@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000221175714.A37786@dub.net>; from unfurl@dub.net on Mon, Feb 21, 2000 at 05:57:14PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 05:57:14PM -0800, Bill Swingle wrote: > ===> gnu/usr.bin/binutils/doc ... > install-info --quiet --defsection="Programming & development tools." --defentry="* Gasp: (gasp). The GNU Assembler Macro Preprocessor." gasp.info /local0/ftp/pub/FreeBSD/snapshots/4.0-20000221-SNAP/usr/share/info/dir > install-info: No such file or directory for gasp.info > *** Error code 1 Is this during `make buildworld' or `make installworld'? Are you using -DNOCLEAN by chance? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 20:22:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 2ECE137B67F; Mon, 21 Feb 2000 20:22:44 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id NAA25932; Tue, 22 Feb 2000 13:22:39 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id NAA25301; Tue, 22 Feb 2000 13:22:37 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id NAA23872; Tue, 22 Feb 2000 13:22:36 +0900 (JST) To: asmodai@bart.nl Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000221144858.O84100@lucifer.bart.nl> References: <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> <20000221144858.O84100@lucifer.bart.nl> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000222132327B.shin@nd.net.fujitsu.co.jp> Date: Tue, 22 Feb 2000 13:23:27 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 82 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Woops sorry I was worng. > >tp->tt_rexmt->c_flags is actually causing the panic, and the > >necessary data is the contents of the tp->tt_rexmt->c_flags. > > (kgdb) print tp->tt_rexmt->c_flags > $1 = 6 > > (kgdb) print tp->tt_rexmt > $2 = (struct callout *) 0xd5ce6c2c > > (kgdb) print (*tp->tt_rexmt) > $3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c, > tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60, > c_func = 0xc018bcdc , c_flags = 6} Wmm, the contents of tp->tt_rexmt not seems to be broken. As the result of more review, I found one part which might cause the problem in very delicate timing, tcp_output.c around line 776. if (!callout_active(tp->tt_rexmt) && tp->snd_nxt != tp->snd_una) { callout_reset(tp->tt_rexmt, tp->t_rxtcur, tcp_timer_rexmt, tp); if (callout_active(tp->tt_persist)) { callout_stop(tp->tt_persist); tp->t_rxtshift = 0; } } If persist timer is working, and if it happen to timeout between callout_reset(tp->tt_rexmt, tp->t_rxtcur, tcp_timer_rexmt, tp); and callout_stop(tp->tt_persist); then the panic might happen at tcp_setpersist(). This is same as Jan 5 version, but in more previous version, the code was like below, if (tp->t_timer[TCPT_REXMT] == 0 && tp->snd_nxt != tp->snd_una) { tp->t_timer[TCPT_REXMT] = tp->t_rxtcur; if (tp->t_timer[TCPT_PERSIST]) { tp->t_timer[TCPT_PERSIST] = 0; tp->t_rxtshift = 0; } } Same problem might also happen in this case but the running step were more fewer than now, so it was more difficult to happen. I think applying following patch will be safer. Please review this patch. (Same kind of patch might better to be applied into stable also.) Thanks, Yoshinobu Inoue Index: tcp_output.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_output.c,v retrieving revision 1.39 diff -u -r1.39 tcp_output.c --- tcp_output.c 2000/02/09 00:34:40 1.39 +++ tcp_output.c 2000/02/22 04:13:32 @@ -775,12 +775,12 @@ */ if (!callout_active(tp->tt_rexmt) && tp->snd_nxt != tp->snd_una) { - callout_reset(tp->tt_rexmt, tp->t_rxtcur, - tcp_timer_rexmt, tp); if (callout_active(tp->tt_persist)) { callout_stop(tp->tt_persist); tp->t_rxtshift = 0; } + callout_reset(tp->tt_rexmt, tp->t_rxtcur, + tcp_timer_rexmt, tp); } } else if (SEQ_GT(tp->snd_nxt + len, tp->snd_max)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 20:39:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 4AF4937B569 for ; Mon, 21 Feb 2000 20:39:43 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA18029; Mon, 21 Feb 2000 20:39:40 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B2127B.9754138D@gorean.org> Date: Mon, 21 Feb 2000 20:37:15 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jeffrey J. Mountin" Cc: current@FreeBSD.org Subject: Re: minor nit with 4.0-RC2 References: <3.0.3.32.20000221181800.00a2d660@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" wrote: > > Nothing major.... > > Finished a build, installed, and mergemaster points out that the $FreeBSD > line is missing from the /etc/group binary install. Hrrmm... so you did a clean install from floppies, etc. and the installed version of /etc/group didn't have a $FreeBSD tag? I'm a little confused by your account. > Only a touch > irritating. 'Twas the case with RC1 as well, but when I merged the temp > and original version it lumped the ID with a comment and the wheel group > line and thus removing my account, which I then promptly forgot to fix. Did you try to merge the two group files? If so, did you use the '%eb' option to edit both files together? That would have allowed you to combine the bits from both files that you wanted to keep into the merged version of the file. The man page for sdiff has more details. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 20:42:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3F25637B61B for ; Mon, 21 Feb 2000 20:42:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA17982 for ; Mon, 21 Feb 2000 20:42:19 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA35349; Mon, 21 Feb 2000 20:42:19 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 21 Feb 2000 20:42:19 -0800 (PST) Message-Id: <200002220442.UAA35349@vashon.polstra.com> To: current@freebsd.org Subject: Re: "Interesting" failure mode for static linking with shared libs. In-Reply-To: <32351.951188747@zippy.cdrom.com> References: <32351.951188747@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <32351.951188747@zippy.cdrom.com>, Jordan K. Hubbard wrote: > > I ran across this as part of my continuing efforts to make the openssl > library pull in the rsaref code at runtime, something which now works > just peachy in the dynamic linking case but does not work in the > static linking case. That is to say that if I want to link ssh > static, for whatever reason, and I compile it up in the following ways > (the names used for the libs aren't exactly correct, I'm just > illustrating a point): > > 1. cc -static ${SSHOBJS} -o ssh -lrsaref -lrsaglue -lssl > > 2. cc -static ${SSHOBJS} -o ssh -lrsaglue -lssl > > Then in case #2 the expected happens, e.g. ssh bitches about needing > the rsa code and aborts since dlopen() is not available to the rsaglue > stub functions I wrote and I'd consider that correct. > > However, case #1 also causes the very same behavior, and that just > mystifies me since I'd have expected the "strong" symbols in librsaref > to have been bound to in preference to the weak ones in librsaglue. > I've also tried referencing the .a file directly in the link line > (cc -static ${SSHOBJS} -o ssh /usr/local/lib/librsaref.a -lrsaglue -lssl) > in hopes that this would somehow get it preferred just on that > basis alone, but no deal. Urk! Any ideas? A simple test case that I built does the right thing. I'll look into your specific example and figure out why it's not working. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 21:15: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id A543837B57B for ; Mon, 21 Feb 2000 21:15:00 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id XAA04916; Mon, 21 Feb 2000 23:14:57 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-87.max1.wa.cyberlynk.net(207.227.118.87) by peak.mountin.net via smap (V1.3) id sma004914; Mon Feb 21 23:14:42 2000 Message-Id: <3.0.3.32.20000221231422.00870370@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 21 Feb 2000 23:14:22 -0600 To: Doug Barton From: "Jeffrey J. Mountin" Subject: Re: minor nit with 4.0-RC2 Cc: current@FreeBSD.ORG In-Reply-To: <38B2127B.9754138D@gorean.org> References: <3.0.3.32.20000221181800.00a2d660@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:37 PM 2/21/00 -0800, Doug Barton wrote: > Hrrmm... so you did a clean install from floppies, etc. and the installed >version of /etc/group didn't have a $FreeBSD tag? I'm a little confused by >your account. Yes, a clean install. No, the sysinstall version of /etc/group did not have the tag. This may affect binary installs of 3.4R as well, but I didn't pay too much attention and also CVSup'd it to -stable right after install. Not to mention this was about a month back. FYI - I start with a fresh binary install after releases and CVSup to -stable (or -current lately ;). > Did you try to merge the two group files? If so, did you use the '%eb' >option to edit both files together? That would have allowed you to combine >the bits from both files that you wanted to keep into the merged version of >the file. The man page for sdiff has more details. Yes, I did merge them. Thanks for the tip on sdiff. Usually "save it for later" and merge manually. Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Mon Feb 21 21:24:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from code.cs.unm.edu (code.cs.unm.edu [198.83.92.110]) by hub.freebsd.org (Postfix) with ESMTP id 9B94C37B5D2 for ; Mon, 21 Feb 2000 21:24:30 -0800 (PST) (envelope-from spcoltri@code.cs.unm.edu) Received: from code.cs.unm.edu (localhost.cs.unm.edu [127.0.0.1]) by code.cs.unm.edu (8.9.3/8.9.3) with ESMTP id WAA06010 for ; Mon, 21 Feb 2000 22:24:29 -0700 (MST) (envelope-from spcoltri@code.cs.unm.edu) Message-Id: <200002220524.WAA06010@code.cs.unm.edu> To: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-reply-to: Your message of "Mon, 21 Feb 2000 18:56:41 EST." Date: Mon, 21 Feb 2000 22:24:29 -0700 From: Steve Coltrin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bryan Liesner writes: >Netscape would always crash on me when loading a java applet - I found >that if you define both the scaled and unscaled fonts in XF86Config as >below that all the java related crashes go away. >Section "Files" > RgbPath "/usr/X11R6/lib/X11/rgb" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/misc" > FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" > ModulePath "/usr/X11R6/lib/modules" >EndSection >Hope this helps. I tried this and Netscape ran Java for me for the first time _ever_, but other X programs started using scaled versions of bitmapped fonts - bleaurgh. Thinking about fonts inspired me, though; I copied the fonts.properties that the Linux JDK ports at http://www.jmcm.org/tech/ports/linux_jdk.html installed, and that works too. (This is with the Linux Netscape version; I haven't tried with the FreeBSD native version.) -spc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 21:51:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id DEB9C37B5EA; Mon, 21 Feb 2000 21:51:31 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA18269; Mon, 21 Feb 2000 21:51:29 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B22348.FFB655EB@gorean.org> Date: Mon, 21 Feb 2000 21:48:56 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jeffrey J. Mountin" Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: minor nit with 4.0-RC2 References: <3.0.3.32.20000221181800.00a2d660@207.227.119.2> <3.0.3.32.20000221231422.00870370@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" wrote: > > At 08:37 PM 2/21/00 -0800, Doug Barton wrote: > > Hrrmm... so you did a clean install from floppies, etc. and the installed > >version of /etc/group didn't have a $FreeBSD tag? I'm a little confused by > >your account. > > Yes, a clean install. > No, the sysinstall version of /etc/group did not have the tag. Ok, that's bad. I'm cc'ing Jordan so he can look into it. Thanks for the report. These are the little things that really need to be tested. > Thanks for the tip on sdiff. My pleasure. > Usually "save it for later" and merge manually. Yeah, I do the same thing, depending on the file. sdiff is really a powerful tool, maybe I should include some tips for its use in mm's man page... Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 22:15:37 2000 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 C65B737B569; Mon, 21 Feb 2000 22:15:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA33145; Mon, 21 Feb 2000 22:15:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Doug Barton Cc: "Jeffrey J. Mountin" , current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: minor nit with 4.0-RC2 In-reply-to: Your message of "Mon, 21 Feb 2000 21:48:56 PST." <38B22348.FFB655EB@gorean.org> Date: Mon, 21 Feb 2000 22:15:12 -0800 Message-ID: <33142.951200112@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, a clean install. > > No, the sysinstall version of /etc/group did not have the tag. > > Ok, that's bad. I'm cc'ing Jordan so he can look into it. Thanks for th e > report. These are the little things that really need to be tested. I'm not sure I understand this - sysinstall doesn't install an /etc/group file so there's really no "sysinstall version" which is distinct from that installed as part of the bindist, at least to my knowledge. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 22:20:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id AE8FE37B513 for ; Mon, 21 Feb 2000 22:20:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00686; Mon, 21 Feb 2000 22:32:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220632.WAA00686@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Donn Miller Cc: Vladimir Kushnir , freebsd-current@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Sun, 20 Feb 2000 19:59:15 EST." <38B08DE3.7080906@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Mon, 21 Feb 2000 22:32:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Vladimir Kushnir wrote: > > = > > Hello, > > I dont't know if this is some HW problem, but after the last update s= ystem > > became unbootable if I load modules by /boot/loader rather them kldlo= ad. = > That seems to be a bug -- I'd just load the modules via /etc/rc.conf fo= r = > now.=A0 Other people have reported problems when loading modules via th= e = > boot loader.=A0 My advice would be to just load them via /etc/rc.conf This is entirely incorrect, and if you're having trouble loading modules = with the loader there's something wrong that needs to be fixed. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Feb 21 23:12:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 8435D37B590 for ; Mon, 21 Feb 2000 23:12:34 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA10826; Tue, 22 Feb 2000 02:11:59 -0500 Date: Tue, 22 Feb 2000 02:11:59 -0500 (EST) From: Mike Nowlin To: Kenneth Wayne Culver Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You may want to try upgrading your linux libraries... they may be old... I > don't have these problems though... Netscape rarely crashes for me. Me and one of my friends got really sick of this problem one weekend a few months ago (under Linux), and decided to figure out what was blowing up... After trying LOTS (about 40) of different library versions in even more (several hundred) combinations, we finally found a few combinations that worked (basically) every time... NS would still blow up when heavily strained, but 99.9% of the time it worked fine... This was on Slackware and Redhat Linux, dunno which versions.... (It really doesn't make any difference.) The general rule that we found is to take the NS version you're running, do an "ldd" on it to get the required libs, and go find what was at the time of that NS version release the most recent version of each library. Upgrading to a newer version almost always made NS die horribly, usually in Java... Sometimes you had to go back to the previous library version on one or two of them. After some more experimentation, I found very similar results under both AIX and Digital UNIX. Something tells me that they're doing something funny with memory pointers..... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 23:18:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 8204537B5EE; Mon, 21 Feb 2000 23:18:48 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id BAA05558; Tue, 22 Feb 2000 01:18:45 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-100.max1.wa.cyberlynk.net(207.227.118.100) by peak.mountin.net via smap (V1.3) id sma005556; Tue Feb 22 01:18:26 2000 Message-Id: <3.0.3.32.20000222011805.00844100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 22 Feb 2000 01:18:05 -0600 To: "Jordan K. Hubbard" From: "Jeffrey J. Mountin" Subject: Re: minor nit with 4.0-RC2 Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <33142.951200112@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:15 PM 2/21/00 -0800, Jordan K. Hubbard wrote: >> > Yes, a clean install. >> > No, the sysinstall version of /etc/group did not have the tag. >> >> Ok, that's bad. I'm cc'ing Jordan so he can look into it. Thanks for th >e >> report. These are the little things that really need to be tested. > >I'm not sure I understand this - sysinstall doesn't install an >/etc/group file so there's really no "sysinstall version" which is >distinct from that installed as part of the bindist, at least to my >knowledge. Nevermind. Manually extracted etc/group and it has the tag line. Must/might be losing it, but then I don't strip the tag lines when I edit files. 8-/ Then again maybe adduser does this. Could start fresh again I suppose and see what went wrong or if I lose my pilots license. Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Mon Feb 21 23:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id F3B6837B649 for ; Mon, 21 Feb 2000 23:44:17 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 12055019 invoked from network); 22 Feb 2000 07:44:16 -0000 Received: from d122.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.122]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 22 Feb 2000 07:44:16 -0000 Message-ID: <38B23D6A.9F73BD55@cybercable.fr> Date: Tue, 22 Feb 2000 08:40:26 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Donn Miller , Vladimir Kushnir , freebsd-current@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002220632.WAA00686@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've yesterday sent a post on this list (from my work email) about the impossibility of loading the if_xl and miibus modules with the loader (it works well with kldload, afterwards) This is with 4.0 - RC1. TfH (The loader loops trying to load the miibus module) Mike Smith wrote: > > > Vladimir Kushnir wrote: > > > > > > Hello, > > > I dont't know if this is some HW problem, but after the last update system > > > became unbootable if I load modules by /boot/loader rather them kldload. > > That seems to be a bug -- I'd just load the modules via /etc/rc.conf for > > now. Other people have reported problems when loading modules via the > > boot loader. My advice would be to just load them via /etc/rc.conf > > This is entirely incorrect, and if you're having trouble loading modules > with the loader there's something wrong that needs to be fixed. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 21 23:48:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id 5F47D37B5F8; Mon, 21 Feb 2000 23:48:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA44693; Tue, 22 Feb 2000 00:01:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220801.AAA44693@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thierry Herbelot Cc: Mike Smith , Donn Miller , Vladimir Kushnir , freebsd-current@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Tue, 22 Feb 2000 08:40:26 +0100." <38B23D6A.9F73BD55@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 00:01:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I've yesterday sent a post on this list (from my work email) about the > impossibility of loading the if_xl and miibus modules with the loader > (it works well with kldload, afterwards) This is a known problem with modules that have dependancies; if you load the miibus module first it shouldn't happen (I haven't tested this). We tried to get some code to fix this into 4.x, but were thwarted by the freeze. Other modules should, however, work fine. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Feb 21 23:53:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id B992437B63D for ; Mon, 21 Feb 2000 23:53:32 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 139747 invoked from network); 22 Feb 2000 07:53:30 -0000 Received: from d122.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.122]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 22 Feb 2000 07:53:30 -0000 Message-ID: <38B23F95.E079BD5B@cybercable.fr> Date: Tue, 22 Feb 2000 08:49:41 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Donn Miller , Vladimir Kushnir , freebsd-current@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002220801.AAA44693@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Hello, > > > > I've yesterday sent a post on this list (from my work email) about the > > impossibility of loading the if_xl and miibus modules with the loader > > (it works well with kldload, afterwards) > > This is a known problem with modules that have dependancies; if you load > the miibus module first it shouldn't happen (I haven't tested this). it does : I've tried loading miibus alone : works fine loading miibus, then if_xl : loops in loading miibus Strange ! TfH > > We tried to get some code to fix this into 4.x, but were thwarted by the > freeze. Other modules should, however, work fine. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ 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 Feb 21 23:56:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id 8BC3137B616 for ; Mon, 21 Feb 2000 23:56:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA59841; Tue, 22 Feb 2000 00:08:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220808.AAA59841@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thierry Herbelot Cc: Donn Miller , Vladimir Kushnir , freebsd-current@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Tue, 22 Feb 2000 08:49:41 +0100." <38B23F95.E079BD5B@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 00:08:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I've yesterday sent a post on this list (from my work email) about the > > > impossibility of loading the if_xl and miibus modules with the loader > > > (it works well with kldload, afterwards) > > > > This is a known problem with modules that have dependancies; if you load > > the miibus module first it shouldn't happen (I haven't tested this). > > it does : I've tried > loading miibus alone : works fine > loading miibus, then if_xl : loops in loading miibus Ok. We know that hurts, don't do that. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 9E6F037B63F for ; Tue, 22 Feb 2000 00:01:15 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 9379705 invoked from network); 22 Feb 2000 08:01:13 -0000 Received: from d122.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.122]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 22 Feb 2000 08:01:13 -0000 Message-ID: <38B24163.C1A6C33B@cybercable.fr> Date: Tue, 22 Feb 2000 08:57:23 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Donn Miller , Vladimir Kushnir , freebsd-current@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002220808.AAA59841@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > I've yesterday sent a post on this list (from my work email) about the > > > > impossibility of loading the if_xl and miibus modules with the loader > > > > (it works well with kldload, afterwards) > > > > > > This is a known problem with modules that have dependancies; if you load > > > the miibus module first it shouldn't happen (I haven't tested this). > > > > it does : I've tried > > loading miibus alone : works fine > > loading miibus, then if_xl : loops in loading miibus > > Ok. We know that hurts, don't do that. 8) fine, could there be a note in /boot/loader.conf, so that l^Husers don't get burn trying to load things which won't work (no code change : just a word of caution) TfH > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0: 2:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id 1052137B5EE; Tue, 22 Feb 2000 00:02:22 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id JAA29309; Tue, 22 Feb 2000 09:01:43 +0100 (MET) Date: Tue, 22 Feb 2000 09:01:42 +0100 From: Martin Cracauer To: "Jordan K. Hubbard" Cc: jdp@FreeBSD.ORG, peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: "Interesting" failure mode for static linking with shared libs. Message-ID: <20000222090142.A29249@cons.org> References: <32351.951188747@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <32351.951188747@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Mon, Feb 21, 2000 at 07:05:47PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <32351.951188747@zippy.cdrom.com>, Jordan K. Hubbard wrote: > root@zippy-> cc -fPIC -c stub.c > root@zippy-> ld -shared -o stub.so stub.o > root@zippy-> cc -static test.c -o test stub.so > root@zippy-> ./test > ELF interpreter /usr/lib/libc.so.1 not found > Abort trap > root@zippy-> cc -static test.c -o test stub.o > root@zippy-> ./test > Now in the client, calling doit() > You have reached the stub. Please leave a message. As a workaround for a static binary, you should be able to use -Xlinker -Bstatic instead of -static -static links the libs statically and also leaves out the dynamic loading code from the binary. The former leaves the dynamic loading code in the binary, but links the libs statically. You have a slightly bigger binary, but you don't need the libs at runtime and you are resistent against changed/faked libs, which might do the job you want static linking for. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0: 8:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id DB76337B5EE; Tue, 22 Feb 2000 00:08:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA86719; Tue, 22 Feb 2000 00:20:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220820.AAA86719@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thierry Herbelot Cc: Mike Smith , Donn Miller , Vladimir Kushnir , freebsd-current@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Tue, 22 Feb 2000 08:57:23 +0100." <38B24163.C1A6C33B@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 00:20:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > I've yesterday sent a post on this list (from my work email) about the > > > > > impossibility of loading the if_xl and miibus modules with the loader > > > > > (it works well with kldload, afterwards) > > > > > > > > This is a known problem with modules that have dependancies; if you load > > > > the miibus module first it shouldn't happen (I haven't tested this). > > > > > > it does : I've tried > > > loading miibus alone : works fine > > > loading miibus, then if_xl : loops in loading miibus > > > > Ok. We know that hurts, don't do that. 8) > > fine, could there be a note in /boot/loader.conf, so that l^Husers don't > get burn trying to load things which won't work (no code change : just a > word of caution) Actually, I think that turning off dependancy handling in the loader is the right way to do it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0:10:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id EF80137B5F0 for ; Tue, 22 Feb 2000 00:10:47 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id JAA29574; Tue, 22 Feb 2000 09:09:24 +0100 (MET) Date: Tue, 22 Feb 2000 09:09:24 +0100 From: Martin Cracauer To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000222090924.B29249@cons.org> References: <20000221195137.D50580@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000221195137.D50580@funk.org>; from alexlh@funk.org on Mon, Feb 21, 2000 at 07:51:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000221195137.D50580@funk.org>, Alex Le Heux wrote: > Hi, > > Am I the only one who's experiencing an amzing amount of crashes on > Netscape? This made a real difference in stability for me: Before installing a new Netscape, rm -rf /usr/local/lib/netscape rm -rf /home/*/.netscape Seriously, when I had old config stuff lying around, Netscape's crash frequency was about 10 times as much as it is now that I clean up before upgrading. Turning off Javascript also helps, but may be contraproductive. Also, consider Netscape 3.04 for stability. BTW, does anyone know if its possible to write a plugin for the BSDI version of Navigator 3.04 so that it display *.png files as it displays *.gif files now? As I understand, a plugin doesn't have fine enough access to the display code to do this, right? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0:16:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 9EC4E37B64E for ; Tue, 22 Feb 2000 00:16:34 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 13124 invoked from network); 22 Feb 2000 08:16:33 -0000 Received: from lcm208.cvzoom.net (HELO cvzoom.net) (208.230.69.208) by ns.cvzoom.net with SMTP; 22 Feb 2000 08:16:33 -0000 Message-ID: <38B245C0.F0ABAC48@cvzoom.net> Date: Tue, 22 Feb 2000 03:16:00 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Martin Cracauer Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? References: <20000221195137.D50580@funk.org> <20000222090924.B29249@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > BTW, does anyone know if its possible to write a plugin for the BSDI > version of Navigator 3.04 so that it display *.png files as it > displays *.gif files now? > > As I understand, a plugin doesn't have fine enough access to the > display code to do this, right? You could try Mozilla. I usually check out the SeaMonkeyAll code via cvs. So far, it's built fairly well. Mozilla is still a bit sluggish now, though. (I guess the optimization for speed will come later.) I can give you the .mozconfig file I used to successfully build Mozilla on -current. Also, xemacs has a `w3' package that does web pages, possibly png. (Some pages don't look very well, however.) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0:26: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 2BC0237B5D1 for ; Tue, 22 Feb 2000 00:25:59 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.70]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1906; Tue, 22 Feb 2000 09:25:55 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA98425; Tue, 22 Feb 2000 08:37:08 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 08:37:08 +0100 From: Jeroen Ruigrok/Asmodai To: Luigi Rizzo Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000222083708.K79013@daemon.ninth-circle.org> References: <20000221110752.A83583@lucifer.bart.nl> <200002211022.LAA92236@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002211022.LAA92236@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Mon, Feb 21, 2000 at 11:22:28AM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 12:01], Luigi Rizzo (luigi@info.iet.unipi.it) wrote: >> this is fun... >> >> Just caught panic #3 on my Diablo newstransit box running 4.0 from the >> 7th of February. >> >> This box pushes around 360-380 GB in a weekend on network IO. > >this is the right kind of app for -current isn't it :) Hey you guys claim everything was limited and fixed and more stable and errr... Wait a sec, I'm part of this development. Mmm. =) Well, it's definately a good torture box for CURRENT. I was already able to get the amr driver to wedge once after which I changed something in the driver after speaking with Mike. Now to get the last few panics looked at. OBTW, is it possible to gdb -k kernel.0 vmcore.0 the files on another box, or not? -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Religion... Is the opium of the people... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 0:32:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C53A737B64E for ; Tue, 22 Feb 2000 00:32:45 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA00330; Tue, 22 Feb 2000 09:32:43 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002220832.JAA00330@freebsd.dk> Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus In-Reply-To: <20000221235518.A998@titan.klemm.gtn.com> from Andreas Klemm at "Feb 21, 2000 11:55:18 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 22 Feb 2000 09:32:43 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Andreas Klemm wrote: > Hi ! > > I have hangs and timeouts using the EIDE disk in my computer. > The controller is a Abit Hot Rod 66 and Maxtor Diamond Max 54098U8. > I use the 80 pin cable from the Abit EIDE controller special for UDMA. > > Messages are: > ad4: READ command timeout - resetting > ata2: resetting devices > > ad4: WRITE command timeout - resetting > ata2: resetting devices .. done You have a config problem.... > atapci0: at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 > ata0: probe allocation failed > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0001 > ata1: probe allocation failed > atapci1: port 0xa400-0xa4ff,0xa000-0xa003,0x9c00-0x9c07 irq 15 at device 14.0 on pci0 > ata2: iobase=0x9c00 altiobase=0xa000 bmaddr=0xa400 > ata2: at 0x9c00 on atapci1 > atapci2: port 0xb000-0xb0ff,0xac00-0xac03,0xa800-0xa807 irq 15 at device 14.1 on pci0 > ata3: iobase=0xa800 altiobase=0xac00 bmaddr=0xb000 > ata3: probe allocation failed Now where did this come form: > ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 > ata4: mask=00 status0=ff status1=ff > ata4: probe allocation failed > ata2-master: success setting up UDMA4 mode on HPT366 chip > ad4: ATA-5 disk at ata2 as master > ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S > ad4: 16 secs/int, 1 depth queue, UDMA66 > ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 > # ATA and ATAPI devices > device ata0 at isa? port IO_WD1 irq 14 > #device ata1 at isa? port IO_WD2 irq 15 > device ata > device atadisk # ATA disk drives > #device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices make that: device ata device atadisk options ATA_STATIC_ID -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 Feb 22 1: 0:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 5FF8D37B663; Tue, 22 Feb 2000 01:00:09 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id KAA13794; Tue, 22 Feb 2000 10:00:07 +0100 (CET) Date: Tue, 22 Feb 2000 10:00:06 +0100 From: Martin Cracauer To: jdp@freebsd.org Cc: jkh@freebsd.org, current@freebsd.org, dillon@apollo.backplane.com Subject: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000222100006.A13742@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to hunt the strptime(..., "%+", ...) bug down. It looks like a showstopper dynamic linker bug in 4.0 now. I suspect that extern variables located in shared variables are broken, either by a ld.so or a mmap bug. In a dynamically linked program, it looks like the address of the symbol "extern char *tzname[];" changes at runtime. You can write to it as much as you like, but if you read it, the address points to the void and the program dumps core. gdb displays very odd stuff, probably reflecting a change in the underlying memory mapping. When you link the program statically, it runs fine. Try this program: #include #include int main(void) { fprintf(stderr, "Address of tzname: %p\n", tzname); tzname[0] = "ERA"; fprintf(stderr, "Address of tzname: %p\n", tzname); tzname[1] = "ERA"; fprintf(stderr, "Address of tzname: %p\n", tzname); tzset(); fprintf(stderr, "Address of tzname: %p\n", tzname); fprintf(stderr, "Values: '%s', '%s'\n", tzname[0], tzname[1]); return 0; } Run it in gdb, using this .gdbinit: file test2 b main r display tzname n n Breakpoint 1, 0x80484ab in main () at test2.c:7 7 fprintf(stderr, "Address of tzname: %p\n", tzname); Address of tzname: 0x8049638 9 tzname[0] = "ERA"; 1: {} (void *) 0x8049638 = 671997369 10 fprintf(stderr, "Address of tzname: %p\n", tzname); 1: {} (void *) 0x8049638 = 134514018 Now, look at the addresses printed by gdb: The hex addresses are the same, but the decimal ones are not. Also, the type of variable tzname is defined in scope, gdb should be able to gather it. Further down, when accessing tzname[0] or tzname[1] for reading, the program dumps core, both when running in gdb and running standalone. As I said, everything works fine when linking statically. In 3.4-stable, all is well for static and dynamic linking. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 1: 5: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id B270A37B63F; Tue, 22 Feb 2000 01:04:53 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id JAA26808; Tue, 22 Feb 2000 09:04:50 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id XAA00450; Mon, 21 Feb 2000 23:31:57 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 21 Feb 2000 23:31:56 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Hellmuth Michaelis Cc: Andrew Gordon , dfr@nlsystems.com, current@freebsd.org, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems In-Reply-To: <20000220191947.A58381F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe this is a silly suggestion, but could someone with a card like that boot it in a Windows environment and tell us what that hardware manager tells us about hardware requirements the card would have if it is configured for the '0x160' address (whatever that configuration is on the card I don't know)? Nick > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > > that the fifo appears at an address 3 bytes after the last register (0x3e > > with the current scheme - see tels0163_read_fifo()). > > Oh yes, you are right! I was (and am still a bit) confused. > > So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX > and at least three bytes at its base address, right ? > > This makes sense. Now the real question left is are this the only locations > where the card is driving the bus ? > > hellmuth > -- > Hellmuth Michaelis hm@kts.org Hamburg, Europe > We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 1: 5:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 91D4937B930 for ; Tue, 22 Feb 2000 01:05:13 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id JAA26800; Tue, 22 Feb 2000 09:04:47 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id XAA00795; Mon, 21 Feb 2000 23:50:17 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 21 Feb 2000 23:50:17 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Bryan Liesner Cc: Kenneth Wayne Culver , freebsd-current@freebsd.org, USB BSD list Subject: Re: ATA errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I cvsupped this morning and I just had a chance to build a new kernel, and > >now I get a "cannot mount root" and it drops into some kind of commandline > >where I can enter a root for it to mount. This is the error it gives me > >now: > > > >ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY > >ata0-slave: ata_command: timeout waiting for intr > >ata0-slave: identify failed > > I went through this this morning. If you are loading modules from the > boot loader, load them later, like from rc.conf. I'm not sure what > broke there, but it's a good workaround. Well, the same seems to apply to some OHCI host controllers. They fail to work as well if preloaded or postloaded, but do work if they are compiled into the kernel. I haven't tried yet whether the compiled USB support fails if a module is preloaded though. My gut feeling is that this must be related. I think, and this is just a bad guess, that this broke around 2 weeks ago. I'll see if I can run a few test kernels this evening. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 1:11: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 9C33737B71A for ; Tue, 22 Feb 2000 01:11:00 -0800 (PST) (envelope-from alexlh@xs4all.nl) Received: from xs3.xs4all.nl (alexlh@xs3.xs4all.nl [194.109.6.44]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id KAA25855; Tue, 22 Feb 2000 10:10:58 +0100 (CET) Received: (from alexlh@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) id KAA06924; Tue, 22 Feb 2000 10:10:58 +0100 (CET) Date: Tue, 22 Feb 2000 10:10:58 +0100 From: Alex To: Bryan Liesner Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000222101058.A6900@xs4all.nl> References: <20000221195137.D50580@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bleez@netaxs.com on Mon, Feb 21, 2000 at 06:56:41PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will try this and see if it helps. Cheers, Alex On Mon, Feb 21, 2000 at 06:56:41PM -0500, Bryan Liesner wrote: > On Mon, 21 Feb 2000, Alex Le Heux wrote: > > >Hi, > > > >Am I the only one who's experiencing an amzing amount of crashes on > >Netscape? > > > >It's been going on for quite some time now (months), upgrading Netscape or > >switching from the Linux to the FreeBSD to the BSDI version doesn't help. > >The most stable version seems to be the Linux version, but that even > >crashes 5-10 times per day. It will *always* crash when a page uses java, > >but I've not been able to find a non-java page that will always crash it. > > Netscape would always crash on me when loading a java applet - I found > that if you define both the scaled and unscaled fonts in XF86Config as > below that all the java related crashes go away. > > It still crashes occasionally on complex pages that load up a million > different frames, though. > > Section "Files" > RgbPath "/usr/X11R6/lib/X11/rgb" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/misc" > FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" > ModulePath "/usr/X11R6/lib/modules" > EndSection > > Hope this helps. > > -Bryan > > -- --- I dabble in techno-house and sometimes, I do that badass hip-hop thang... But the F U N K gets me every time! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 1:12:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id C36F337B6EE; Tue, 22 Feb 2000 01:12:15 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id KAA05740; Tue, 22 Feb 2000 10:12:06 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 10:12:06 +0100 From: Jeroen Ruigrok van der Werven To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000222101206.B5555@lucifer.bart.nl> References: <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> <20000221144858.O84100@lucifer.bart.nl> <20000222132327B.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000222132327B.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Tue, Feb 22, 2000 at 01:23:27PM +0900 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks fine to me. Perhaps Garrett has something to say about it? -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 1:24:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1D3CF37B5E3 for ; Tue, 22 Feb 2000 01:24:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA00487; Tue, 22 Feb 2000 10:24:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002220924.KAA00487@freebsd.dk> Subject: Re: 0208-CURRENT and CD-Changer In-Reply-To: <00f201bf7c83$4ea290e0$16280c0a@sos> from Morten Seeberg at "Feb 21, 2000 04:49:58 pm" To: ml@seeberg.dk (Morten Seeberg) Date: Tue, 22 Feb 2000 10:24:18 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Morten Seeberg wrote: > I have a Teac 6 CD changer (acd0: CDROM with 6 CD changer at > ata1-master using PIO4), which works just fine in 3.x except for the usual > error message when the CD-ROM drive is empty and I start up > /stand/sysinstall), but in subj. when starting /stand/sysinstall (this also > happens when installing), it takes a LOOOONG time to start, and these are > some of the errors that appear: I've just yesterday committed some updates to the changercode, that might solve your problem... -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 Feb 22 1:41:32 2000 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 518E437B5F0; Tue, 22 Feb 2000 01:41:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA33904; Tue, 22 Feb 2000 01:41:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Martin Cracauer Cc: jdp@FreeBSD.ORG, peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: "Interesting" failure mode for static linking with shared libs. In-reply-to: Your message of "Tue, 22 Feb 2000 09:01:42 +0100." <20000222090142.A29249@cons.org> Date: Tue, 22 Feb 2000 01:41:05 -0800 Message-ID: <33901.951212465@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As a workaround for a static binary, you should be able to use > -Xlinker -Bstatic > instead of > -static Actually, it appears that just -Xlinker is necessary; it works fine in conjunction with -static. Thanks for this most helpful tip! I can see a *lot* of scenarios where I'll be using -Xlinker in the future. I didn't even know about that flag. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 2:31:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 1063137B625 for ; Tue, 22 Feb 2000 02:31:58 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id CAA01453 for freebsd-current@freebsd.org; Tue, 22 Feb 2000 02:31:57 -0800 Date: Tue, 22 Feb 2000 02:31:57 -0800 From: Arun Sharma To: freebsd-current@freebsd.org Subject: ABIT BP6, UDMA-66 and wdc AC310200 Message-ID: <20000222023156.A1426@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the above hardware combination and here's the dmesg from 4.0-current: atapci0: port 0xf000-0xf00f at device 7.1 on pci0 atapci1: port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 ata2: at 0xac00 on atapci1 atapci2: port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 ad4: 9787MB [19885/16/63] at ata2-master using UDMA33 How do I get my disk to work in UDMA66 mode ? Is it supported with for my disk ? http://www.westerndigital.com/service/FAQ/dtr.html lists my disk as ATA-66. What am I doing wrong ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 2:45:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (dhcp52.iafrica.com [196.31.1.52]) by hub.freebsd.org (Postfix) with ESMTP id 106DF37B66C; Tue, 22 Feb 2000 02:45:24 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id MAA89379; Tue, 22 Feb 2000 12:47:27 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002221047.MAA89379@grimreaper.grondar.za> To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Cc: current@FreeBSD.org, committers@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: In-Reply-To: ; from Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) "21 Feb 2000 13:20:52 +0100." Date: Tue, 22 Feb 2000 12:47:27 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Paul Richards writes: > > > The daemon approach actually has benfits that I'm keen on that aren't > > related to security. A single point of access to the data means that the > > backend can be changed so that passwords can be in a different file or a > > database, without having to worry about rebuilding all the binaries. You > > could even split users across different back end systems. > > This sounds like PAM, doesn't it? One of the prime uses for the tool will be PAM. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 2:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 17AA337B58C for ; Tue, 22 Feb 2000 02:54:50 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA09790; Tue, 22 Feb 2000 11:54:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002221054.LAA09790@freebsd.dk> Subject: Re: ABIT BP6, UDMA-66 and wdc AC310200 In-Reply-To: <20000222023156.A1426@sharmas.dhs.org> from Arun Sharma at "Feb 22, 2000 02:31:57 am" To: adsharma@sharmas.dhs.org (Arun Sharma) Date: Tue, 22 Feb 2000 11:54:40 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Arun Sharma wrote: > I have the above hardware combination and here's the dmesg from > 4.0-current: > > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > atapci1: port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 > ata2: at 0xac00 on atapci1 > atapci2: port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 > ad4: 9787MB [19885/16/63] at ata2-master using UDMA33 > > How do I get my disk to work in UDMA66 mode ? Is it supported with for > my disk ? Do you have the prober 80pin cable ?? if so please provide a verbose boot... -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 Feb 22 2:56:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B645037B6EE for ; Tue, 22 Feb 2000 02:56:32 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id QAA00764; Tue, 22 Feb 2000 16:56:29 +0600 (NOVT) (envelope-from nnd) Date: Tue, 22 Feb 2000 16:56:29 +0600 (NOVT) Message-Id: <200002221056.QAA00764@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Cc: Arun Sharma Subject: Re: ABIT BP6, UDMA-66 and wdc AC310200 X-Newsgroups: itfs.freebsd.current In-Reply-To: <20000222023156.A1426@sharmas.dhs.org> User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000222023156.A1426@sharmas.dhs.org> Arun Sharma wrote: What kind of cable do yuo use ? Is it 80-wire one ? N.Dudorov > I have the above hardware combination and here's the dmesg from > 4.0-current: > > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > atapci1: port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 > ata2: at 0xac00 on atapci1 > atapci2: port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 > ad4: 9787MB [19885/16/63] at ata2-master using UDMA33 > > How do I get my disk to work in UDMA66 mode ? Is it supported with for > my disk ? > > http://www.westerndigital.com/service/FAQ/dtr.html lists my disk as > ATA-66. > > What am I doing wrong ? > > -Arun > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 3:16:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id DB1C737B65C for ; Tue, 22 Feb 2000 03:16:46 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id MAA19282; Tue, 22 Feb 2000 12:16:31 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id MAA07579; Tue, 22 Feb 2000 12:07:29 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 12:07:29 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222120729.A5646@titan.klemm.gtn.com> References: <20000221235518.A998@titan.klemm.gtn.com> <200002220832.JAA00330@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002220832.JAA00330@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 09:32:43AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 09:32:43AM +0100, Soren Schmidt wrote: > You have a config problem.... Oh ... > Now where did this come form: > > ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 > > ata4: mask=00 status0=ff status1=ff > > ata4: probe allocation failed > > > ata2-master: success setting up UDMA4 mode on HPT366 chip > > ad4: ATA-5 disk at ata2 as master > > ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S > > ad4: 16 secs/int, 1 depth queue, UDMA66 > > ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 Hmmm... > > # ATA and ATAPI devices > > device ata0 at isa? port IO_WD1 irq 14 Thought, this would be necessary. > > #device ata1 at isa? port IO_WD2 irq 15 > > device ata > > device atadisk # ATA disk drives > > #device atapicd # ATAPI CDROM drives > > #device atapifd # ATAPI floppy drives > > #device atapist # ATAPI tape drives > > options ATA_STATIC_ID #Static device numbering > > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > make that: > > device ata > device atadisk > options ATA_STATIC_ID Will try that. BTW, I tried this night (til 5am *sigh*) to make the device run under the Boards IDE controller. To make that happen I did the (probably mistake), to set a cylinder limitation jumper and install a special BIOS on the disk using the MaxBlast software from Maxtors ftp site. Since then the disk only had 4111cyl/255heads/64sectors =66043215 sectors. Now the drive ran fine under Windows and FreeBSD, but when I removed the jumper on the disk and tried again the abit EIDE controller, the disk wasn't recognized anymore. O.k. at 5am I was f***ing tired... Did I do something wrong to my disk using this maxtor utility ? Does somebody know, if there is a magic trick, to remove the BIOS ? I'll now try, what FreeBSD says to the drive, when I install the new kernel and if I remove the jumpers... Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 3:30:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id AC46037B600 for ; Tue, 22 Feb 2000 03:30:51 -0800 (PST) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (root@guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id WAA20742 for ; Tue, 22 Feb 2000 22:00:48 +1030 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id WAA12473 for freebsd-current@freebsd.org; Tue, 22 Feb 2000 22:00:47 +1030 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 22 Feb 2000 22:00:47 +1030 (CST) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Subject: kdelibs port broken? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to build the kdelibs port on a -current that is 2 days old.. It fails like so... gmake[2]: Entering directory `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' /usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" gmake[2]: *** [kconfig.moc] Error 1 gmake[2]: Leaving directory `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' Now, I'd look this up in the mailing lists, but the search is still down :( I do remember something about C++ stuff needing to be recompiled (which is why I'm rebuilding kdelibs in the first place).. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 4:23:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2055737B5BE for ; Tue, 22 Feb 2000 04:23:36 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA08848; Tue, 22 Feb 2000 13:23:27 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 13:23:27 +0100 From: Jeroen Ruigrok van der Werven To: Lyndon Nerenberg Cc: current@FreeBSD.ORG Subject: Re: status of 'device awe' ? Message-ID: <20000222132327.O5555@lucifer.bart.nl> References: <200002212001.e1LK1a915911@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002212001.e1LK1a915911@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Mon, Feb 21, 2000 at 01:01:36PM -0700 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000221 21:15], Lyndon Nerenberg (lyndon@orthanc.ab.ca) wrote: >LINT has an entry for an 'awe' device, however there doesn't appear >to be any corresponding source code in the tree. Is this device dead? >If so, the entry should be removed from LINT, or an appropriate >comment added. device pcm device sbc Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 4:30:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 6D7B637B55A for ; Tue, 22 Feb 2000 04:30:20 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id NAA24083; Tue, 22 Feb 2000 13:30:08 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id NAA01214; Tue, 22 Feb 2000 13:14:29 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 13:14:29 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222131429.A870@titan.klemm.gtn.com> References: <20000221235518.A998@titan.klemm.gtn.com> <200002220832.JAA00330@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002220832.JAA00330@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 09:32:43AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Soren, > make that: > device ata > device atadisk > options ATA_STATIC_ID did that: after kernel re-compilation I created a new disklabel on the device I used the whole disk /dev/ad4c /data ufs rw 1 2 just for testing purposes. Newfs'ing and mounting the filesystem went fine. I enabled softupdates prior mounting. But when I tried fire up bonnie -s 100 I soon get after nearly writing the 100 MB characterwise... ad4: READ command timeout - resetting ata2: resetting devices And the whole system hangs -> reset Behind dmesg of a verbose boot my new kernel config as reference Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Feb 22 12:11:23 CET 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN Calibrating clock(s) ... TSC clock: 199426380 Hz, i8254 clock: 1193149 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 159383552 (155648K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00345000 - 0x097f5fff, 155914240 bytes (38065 pages) avail memory = 150921216 (147384K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 15 IOAPIC #0 intpin 17 -> irq 11 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 19 -> irq 14 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00fac30 bios32: Entry = 0xfb0b0 (c00fb0b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb0e0 pnpbios: Found PnP BIOS data at 0xc00fbc30 pnpbios: Entry = f0000:bc58 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0329000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base e0000000, size 14 map[14]: type 1, range 32, base e1000000, size 23 found-> vendor=0x10b7, dev=0x9001, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base 00009400, size 6 found-> vendor=0x1102, dev=0x0002, revid=0x04 class=04-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00009800, size 5 found-> vendor=0x1102, dev=0x7002, revid=0x01 class=09-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 00009c00, size 3 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000a000, size 8 map[14]: type 1, range 32, base e2000000, size 12 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 0000a400, size 3 map[14]: type 1, range 32, base 0000a800, size 2 map[20]: type 1, range 32, base 0000ac00, size 8 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 0000b000, size 3 map[14]: type 1, range 32, base 0000b400, size 2 map[20]: type 1, range 32, base 0000b800, size 8 pci0: on pcib0 isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: IRQ15, B: IRQ11, C: IRQ10, D: IRQ14 MB0: , MB1: isa0: on isab0 atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata0: mask=00 status0=ff status1=ff ata0: probe allocation failed ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0001 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: Matrox MGA Millennium 2064W graphics accelerator (vendor=0x102b, dev=0x0519) at 10.0 irq 15 xl0: <3Com 3c900-COMBO Etherlink XL> port 0x9400-0x943f irq 14 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: media options word: e138 xl0: found 10baseT xl0: found AUI xl0: found BNC xl0: selecting 10baseT transceiver, half duplex bpf: xl0 attached pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 10 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 ahc0: port 0xa000-0xa0ff mem 0xe2000000-0xe2000fff irq 11 at device 13.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable not present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: Low byte termination Enabled ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 413 instructions downloaded atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 ata2: iobase=0xa400 altiobase=0xa800 bmaddr=0xac00 ata2: mask=03 status0=50 status1=00 ata2: mask=03 status0=50 status1=00 ata2: devices = 0x1 ata2: at 0xa400 on atapci1 atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 ata3: iobase=0xb000 altiobase=0xb400 bmaddr=0xb800 ata3: mask=03 status0=20 status1=30 ata3: mask=03 status0=20 status1=30 ata3: devices = 0x0 ata3: probe allocation failed Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff fb: new array size 4 sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 5 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) bpf: ed0 attached isa_probe_children: probing PnP devices SMP: enabled INTs: 1, 3, 4, 5, 6, 7, 11, 12, 14, 15, apic_imen: 0x00ff2705 BIOS Geometries: 0:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 1:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 2:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 3:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors 4:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default DUMMYNET initialized (000106) bpf: lo0 attached Linux-ELF exec handler installed SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ata2-master: success setting up UDMA4 mode on HPT366 chip ad4: ATA-5 disk at ata2 as master ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad4 Creating DISK wd4 Waiting 8 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: target 6 synchronous at 10.0MHz, offset = 0xf ahc0: target 2 synchronous at 10.0MHz, offset = 0xf ahc0: target 0 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 synchronous at 10.0MHz, offset = 0xf ahc0: target 3 synchronous at 10.0MHz, offset = 0xf Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 Creating DISK cd0 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 5U6G6557 pass0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number 5U2N3906 pass1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 5U312691 pass2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled pass3 at ahc0 bus 0 target 3 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number 5U323663 pass3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled pass4 at ahc0 bus 0 target 6 lun 0 pass4: Removable CD-ROM SCSI-2 device pass4: Serial Number 8704381B pass4: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s2a (cd0:ahc0:0:6:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:6:0): NOT READY asc:3a,0 (cd0:ahc0:0:6:0): Medium not present cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: Serial Number 8704381B cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number 5U2N3906 da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number 5U323663 da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 5U6G6557 da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number 5U312691 da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0s1: type 0xb, start 63, end = 1638629, size 1638567 : OK da0s2: type 0xa5, start 1638630, end = 4225094, size 2586465 : OK start_init: trying /sbin/init da1s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK da2s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK da3s1: type 0xa5, start 32, end = 4225023, size 4224992 : OK WARNING: R/W mount of /obj denied. Filesystem is not clean - run fsck WARNING: R/W mount of /news denied. Filesystem is not clean - run fsck WARNING: R/W mount of /proxy denied. Filesystem is not clean - run fsck WARNING: R/W mount of /home denied. Filesystem is not clean - run fsck splash: image decoder found: daemon_saver xl0: promiscuous mode enabled xl0: promiscuous mode disabled (da0:ahc0:0:0:0): tagged openings now 32 (da1:ahc0:0:1:0): tagged openings now 32 (da3:ahc0:0:3:0): tagged openings now 32 (da2:ahc0:0:2:0): tagged openings now 32 machine i386 cpu I686_CPU ident TITAN maxusers 100 options INCLUDE_CONFIG_FILE #Include this file in kernel options INET #Internet communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES #Softupdates options MD5 options NSWAPDEV=4 options COMPAT_LINUX options SHOW_BUSYBUFS options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options USER_LDT options MSGBUF_SIZE=40960 options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options PQ_HUGECACHE # color for 1024k/16k cache device isa0 device pci0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ahc0 # AHA2940 and onboard AIC7xxx devices options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options AHC_ALLOW_MEMIO device scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? irq 7 device ppbus0 # Parallel port bus (required) device lpt0 at ppbus? # Printer device plip0 at ppbus? # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPDIVERT #divert sockets options ICMP_BANDLIM options DUMMYNET device miibus0 # MII bus support device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 pseudo-device loop # Network loopback pseudo-device ether # Ethernet support options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver device smbus0 device iicbus0 device iicbb0 device intpm0 device smb0 at smbus? device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 4:39:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BFE1037B64E for ; Tue, 22 Feb 2000 04:39:50 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA34644; Tue, 22 Feb 2000 13:39:46 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002221239.NAA34644@freebsd.dk> Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus In-Reply-To: <20000222131429.A870@titan.klemm.gtn.com> from Andreas Klemm at "Feb 22, 2000 01:14:29 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 22 Feb 2000 13:39:46 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Andreas Klemm wrote: > Newfs'ing and mounting the filesystem went fine. > I enabled softupdates prior mounting. > > But when I tried fire up bonnie -s 100 > I soon get after nearly writing the 100 MB characterwise... > > ad4: READ command timeout - resetting > ata2: resetting devices > > And the whole system hangs -> reset Hmm, this looks very wierd, how is your BIOS setup wrt to onboard ATA channels ?? Try to use a "normal" ie 40pin cable, that will limit the disk to UDMA33 mode, if that works, well... -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 Feb 22 5:19:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 5100F37B685 for ; Tue, 22 Feb 2000 05:19:41 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 12152 invoked from network); 22 Feb 2000 13:19:38 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Feb 2000 13:19:38 -0000 Date: Wed, 23 Feb 2000 00:19:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Jordan K. Hubbard" Cc: Martin Cracauer , jdp@FreeBSD.ORG, peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: "Interesting" failure mode for static linking with shared libs. In-Reply-To: <33901.951212465@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, Jordan K. Hubbard wrote: > > As a workaround for a static binary, you should be able to use > > -Xlinker -Bstatic > > instead of > > -static > > Actually, it appears that just -Xlinker is necessary; it works > fine in conjunction with -static. Thanks for this most helpful > tip! I can see a *lot* of scenarios where I'll be using > -Xlinker in the future. I didn't even know about that flag. :) This is because `-Xlinker -static' is equivalent to `-Xlinker -Bstatic' in the elf case. Passing -static to the linker used to be a common error. The aout linker doesn't understand -static; it has sloppy args checking and misinterprets -static as -s (strip). -Xlinker alone is bogus. -Xlinker is not an option; it modifies the next option by causing it to be passed to the linker instead of interpreted by the compiler. I didn't know about -Xlinker either :-). It is normally spelled `-Wl,'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7: 5:27 2000 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 70B3837B697; Tue, 22 Feb 2000 07:05:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA07676; Tue, 22 Feb 2000 10:05:16 -0500 (EST) (envelope-from wollman) Date: Tue, 22 Feb 2000 10:05:16 -0500 (EST) From: Garrett Wollman Message-Id: <200002221505.KAA07676@khavrinen.lcs.mit.edu> To: Yoshinobu Inoue Cc: asmodai@bart.nl, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000222132327B.shin@nd.net.fujitsu.co.jp> References: <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> <20000221144858.O84100@lucifer.bart.nl> <20000222132327B.shin@nd.net.fujitsu.co.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > If persist timer is working, and if it happen to timeout between > callout_reset(tp->tt_rexmt, tp->t_rxtcur, > tcp_timer_rexmt, tp); > and > callout_stop(tp->tt_persist); > then the panic might happen at tcp_setpersist(). This should never happen, since this code is supposed to be running at splnet(), which is supposed to block timeouts. Rather than papering over the problem, I'd like to understand how it's possible. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7:15:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id E241837B68C for ; Tue, 22 Feb 2000 07:15:24 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id QAA05711; Tue, 22 Feb 2000 16:15:13 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id QAA03433; Tue, 22 Feb 2000 16:04:56 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 16:04:56 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222160456.A3127@titan.klemm.gtn.com> References: <20000222131429.A870@titan.klemm.gtn.com> <200002221239.NAA34644@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002221239.NAA34644@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 01:39:46PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote: > Hmm, this looks very wierd, Oh yes ;-) BTW no problem with win98 or Win2000 installation. > how is your BIOS setup wrt to onboard ATA channels ?? > Try to use a "normal" ie 40pin cable, that will limit the disk to > UDMA33 mode, if that works, well... Will have to buy that. When I ran with the on board IDE chip I had a drive mode (something like) mdma2. That worked even with FreeBSD. I now tried BIOS setup values. First entered BIOS default values, which are turning off most features, then I enabled SETUP defaults and then changed no performance boosting things. RAM Timing I changed to automatic 70ns, although I have 60 ns RAM. On chip PCI IDE is completely disabled. Then I changed as a last resort method the mode to hw.atamodes: ---,---,---,---,pio,---,---,---, Even with PIO the drive has problems, but is then able to recover: ata2-master: success setting up PIO4 mode on HPT366 chip ad4: invalid primary partition table: no magic this is. because I newfs'd ad4c on the whole ... quick and dirty for testing... now bonnie -s 100 ad4: WRITE command timeout - resetting ata2: resetting devices .. ata2: mask=01 status0=50 status1=00 ata2-master: success setting up PIO4 mode on HPT366 chip done ad4: timeout waiting for DRQ How can I force the driver with kernel modifications to use mdma2 mode or something like this ??? BTW, I have a 5 Slot PCI machine ... in the first slot there is the abit controller in the last the Matrox Millenium card. They share the same IRQ 15... Is this sane ? Or might my problem be SMP related ??? Well, have to go to the supermarket now ... I'll remove one card later, to free one IRQ and will try to use a single cpu kernel... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7:33:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 8728037B68C; Tue, 22 Feb 2000 07:33:09 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id AAA23320; Wed, 23 Feb 2000 00:32:01 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id AAA10819; Wed, 23 Feb 2000 00:32:01 +0900 (JST) Received: from localhost ([192.168.245.60]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id AAA01669; Wed, 23 Feb 2000 00:31:59 +0900 (JST) To: wollman@khavrinen.lcs.mit.edu Cc: asmodai@bart.nl, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <200002221505.KAA07676@khavrinen.lcs.mit.edu> References: <20000221144858.O84100@lucifer.bart.nl> <20000222132327B.shin@nd.net.fujitsu.co.jp> <200002221505.KAA07676@khavrinen.lcs.mit.edu> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000223003250I.shin@nd.net.fujitsu.co.jp> Date: Wed, 23 Feb 2000 00:32:50 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If persist timer is working, and if it happen to timeout between > > callout_reset(tp->tt_rexmt, tp->t_rxtcur, > > tcp_timer_rexmt, tp); > > and > > callout_stop(tp->tt_persist); > > then the panic might happen at tcp_setpersist(). > > This should never happen, since this code is supposed to be running at > splnet(), which is supposed to block timeouts. Rather than papering > over the problem, I'd like to understand how it's possible. I also later thought so, but again I suspect that the part is also one of the cause of the problem. Because as the value of tp->t_rexmt at panic, retransmit timer also seemed to be running at the time, and I can't find any other place which might cause this situation. Also I think anyway the patch is better to be applied. My assumption might be wrong but I am now trying if I can create some patch that make the problem very likely to happen. Thanks, Yoshinobu Inoue > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7:38:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id AE13F37B69E for ; Tue, 22 Feb 2000 07:38:33 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-49.iptelecom.net.ua [212.9.227.113]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA09641; Tue, 22 Feb 2000 17:39:47 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id RAA21201; Tue, 22 Feb 2000 17:36:21 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38B2ACF3.F92BDB1@altavista.net> Date: Tue, 22 Feb 2000 17:36:19 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: kdelibs port broken? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > I am trying to build the kdelibs port on a -current that is 2 days old.. > It fails like so... > > gmake[2]: Entering directory > `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' > /usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol > "_vt$9exception" > gmake[2]: *** [kconfig.moc] Error 1 > gmake[2]: Leaving directory > `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' > > Now, I'd look this up in the mailing lists, but the search is still down :( > > I do remember something about C++ stuff needing to be recompiled (which is > why I'm rebuilding kdelibs in the first place).. You have to rebuild qt2 first to be able to run moc. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7:44:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 1FCDF37B6E5 for ; Tue, 22 Feb 2000 07:44:07 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 26165 invoked by alias); 22 Feb 2000 15:43:58 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 26137 invoked by uid 0); 22 Feb 2000 15:43:57 -0000 Received: from usr1-37.cybcon.com (HELO laptop.cybcon.com) (205.147.75.38) by ptldpop2.ptld.uswest.net with SMTP; 22 Feb 2000 15:43:57 -0000 Content-Length: 1199 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38B2ACF3.F92BDB1@altavista.net> Date: Tue, 22 Feb 2000 07:40:55 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Maxim Sobolev Subject: Re: kdelibs port broken? Cc: freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ON that subject, has anyone tried compiling the KDE port with the new QT145 port? On 22-Feb-00 Maxim Sobolev wrote: > Daniel O'Connor wrote: > >> I am trying to build the kdelibs port on a -current that is 2 days old.. >> It fails like so... >> >> gmake[2]: Entering directory >> `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' >> /usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc >> /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol >> "_vt$9exception" >> gmake[2]: *** [kconfig.moc] Error 1 >> gmake[2]: Leaving directory >> `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore' >> >> Now, I'd look this up in the mailing lists, but the search is still down :( >> >> I do remember something about C++ stuff needing to be recompiled (which is >> why I'm rebuilding kdelibs in the first place).. > > You have to rebuild qt2 first to be able to run moc. > > -Maxim > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 07:39:55l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 7:58:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by hub.freebsd.org (Postfix) with ESMTP id BEB7A37B6A8 for ; Tue, 22 Feb 2000 07:58:12 -0800 (PST) (envelope-from ilmar@ints.ru) Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id SAA58210; Tue, 22 Feb 2000 18:58:24 +0300 (MSK) Date: Tue, 22 Feb 2000 18:58:24 +0300 (MSK) From: "Ilmar S. Habibulin" To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: kdelibs port broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, Daniel O'Connor wrote: > I am trying to build the kdelibs port on a -current that is 2 days old.. > It fails like so... [...] > Now, I'd look this up in the mailing lists, but the search is still down :( > > I do remember something about C++ stuff needing to be recompiled (which is > why I'm rebuilding kdelibs in the first place).. I tryed to recompile them and failed. Qt builds fine, and kdelibs libs compiled fine. The error occured at the linkage stage. :( So i switched to kde-2.0(current). There i have another problems. libkhtml has undefined simbol. But it compiles and works. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9: 8: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 4BC7137B6EE for ; Tue, 22 Feb 2000 09:08:00 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc062023.tokyo.jcom.ne.jp [210.155.62.23]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id CAA03797 for ; Wed, 23 Feb 2000 02:07:58 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id CAA34086; Wed, 23 Feb 2000 02:07:27 +0900 (JST) Date: Wed, 23 Feb 2000 02:07:59 +0900 Message-ID: <86hff1go7k.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: freebsd-current@freebsd.org Subject: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.11 (Euglena viridis) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Associated I. Daemons MIME-Version: 1.0 (generated by EMIKO 1.13.11 - "Euglena viridis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running recent 4.0-CURRENT and my Seagate Barracuda ST320430A 20GB hard drive connected with Promise Ultra66 card isn't recognized as an Ultra ATA/66 drive but only /33. I'm sure I'm using a correct cable for the /66 drive and I confirmed it works successfully in /66 on WinNT 4.0. Am I missing something or doing wrong? Any suggestions are welcome. -- kernel config file -- machine i386 cpu I686_CPU ident ARCHON maxusers 32 options INET options FFS options FFS_ROOT options SOFTUPDATES options MFS options NFS options MSDOSFS options NTFS options EXT2FS options CD9660 options PROCFS options NULLFS options UNION options PORTAL options COMPAT_43 options SCSI_DELAY=3000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options ICMP_BANDLIM options DDB options SMP options APIC_IO device isa device eisa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata device atadisk options ATA_STATIC_ID device ahc device scbus device da device sa device cd device pass device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x20 device pcm0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? irq 7 device ppbus device lpt device plip device ppi device fxp pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun pseudo-device pty 16 pseudo-device md pseudo-device vn pseudo-device bpf 4 options SHMMAXPGS=2049 options COMPAT_LINUX -- dmesg output -- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #29: Sat Feb 19 02:21:47 JST 2000 root@archon.local.idaemons.org:/usr/src/sys/compile/ARCHON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 256925696 (250904K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0361000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0xe1000000-0xe17fffff,0xe0000000-0xe0003fff,0xe4000000-0xe4ffffff at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA not enabled pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x5000-0x500f at device 7.3 on pci0 ahc0: port 0xa400-0xa4ff mem 0xe8920000-0xe8920fff irq 17 at device 8.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: port 0xa800-0xa81f mem 0xe8800000-0xe88fffff,0xe8921000-0xe8921fff irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:14:cf:35 pcm0: port 0xac00-0xac3f irq 18 at device 10.0 on pci0 ata-pci1: port 0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 0xe8900000-0xe891ffff irq 16 at device 12.0 on pci0 ata2 at 0xb000 irq -1 on ata-pci1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 3 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! ad4: 19569MB [39761/16/63] at ata2-master using UDMA33 Mounting root from ufs:/dev/da1s1a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-438 $ /dev/vmmon: Module vmmon: initialized Thanks in advance. -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:14:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8D83937B71E for ; Tue, 22 Feb 2000 09:14:43 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA78664; Tue, 22 Feb 2000 18:14:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002221714.SAA78664@freebsd.dk> Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( In-Reply-To: <86hff1go7k.wl@archon.local.idaemons.org> from Akinori -Aki- MUSHA at "Feb 23, 2000 02:07:59 am" To: knu@idaemons.org (Akinori -Aki- MUSHA) Date: Tue, 22 Feb 2000 18:14:23 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Akinori -Aki- MUSHA wrote: > Hi, > > I'm running recent 4.0-CURRENT and my Seagate Barracuda ST320430A > 20GB hard drive connected with Promise Ultra66 card isn't recognized > as an Ultra ATA/66 drive but only /33. Could I have a verbote boot log please, that would give some hints... > ata-pci1: port 0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 0xe8900000-0xe891ffff irq 16 at device 12.0 on pci0 > ata2 at 0xb000 irq -1 on ata-pci1 > ad4: 19569MB [39761/16/63] at ata2-master using UDMA33 This probe suggests that you are not up to date on -current, that would maybe also help... -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 Feb 22 9:15:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id BCC0C37B724 for ; Tue, 22 Feb 2000 09:15:13 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id JAA02243; Tue, 22 Feb 2000 09:15:10 -0800 Date: Tue, 22 Feb 2000 09:15:10 -0800 From: Arun Sharma To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ABIT BP6, UDMA-66 and wdc AC310200 Message-ID: <20000222091510.A2230@sharmas.dhs.org> References: <20000222023156.A1426@sharmas.dhs.org> <200002221054.LAA09790@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200002221054.LAA09790@freebsd.dk>; from Soren Schmidt on Tue, Feb 22, 2000 at 11:54:40AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 11:54:40AM +0100, Soren Schmidt wrote: > It seems Arun Sharma wrote: > > I have the above hardware combination and here's the dmesg from > > 4.0-current: > > > > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > > atapci1: port 0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0 > > ata2: at 0xac00 on atapci1 > > atapci2: port 0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0 > > ad4: 9787MB [19885/16/63] at ata2-master using UDMA33 > > > > How do I get my disk to work in UDMA66 mode ? Is it supported with for > > my disk ? > > > Do you have the prober 80pin cable ?? if so please provide a verbose boot... Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very unscientific benchmark that I ran didn't seem to produce much of a difference between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s. # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10 10+0 records in 10+0 records out 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec) Can anyone point me to some benchmarks and comment about the improvement ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:30:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6CC3E37B72C for ; Tue, 22 Feb 2000 09:30:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA78748; Tue, 22 Feb 2000 18:30:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002221730.SAA78748@freebsd.dk> Subject: Re: ABIT BP6, UDMA-66 and wdc AC310200 In-Reply-To: <20000222091510.A2230@sharmas.dhs.org> from Arun Sharma at "Feb 22, 2000 09:15:10 am" To: adsharma@sharmas.dhs.org (Arun Sharma) Date: Tue, 22 Feb 2000 18:30:21 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Arun Sharma wrote: > > Do you have the prober 80pin cable ?? if so please provide a verbose boot... > > Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very > unscientific benchmark that I ran didn't seem to produce much of a difference > between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s. There are almost no mesureable difference between UDMA33 and UDMA66, all mesurements I've done (and have read about) sees little if no difference, in fact some drives can be faster under UDMA33 even if they support the higher rate too. > # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10 > 10+0 records in > 10+0 records out > 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec) Thats probably close to what your drive can pull of the platters... I get 22-23MB/sec off an IBM DPTA drive here with < 1% cpu usage, so the driver is not the problem.. I have a config with 7 disks online, giving me a raw throughput of ~100MB/s sustained, that is about the limit of what can be done over the PCI bus... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:34:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from outpost.hstn.tensor.pgs.com (outpost.hstn.tensor.pgs.com [157.147.25.67]) by hub.freebsd.org (Postfix) with ESMTP id ABD8437B72C for ; Tue, 22 Feb 2000 09:34:26 -0800 (PST) (envelope-from shocking@prg01.hstn.tensor.pgs.com) Received: from hap.hstn.tensor.pgs.com (hap.hstn.tensor.pgs.com [157.147.128.1]) by outpost.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id LAA18334 for ; Tue, 22 Feb 2000 11:33:53 -0600 (CST) Received: from prg01.hstn.tensor.pgs.com (prg01.hstn.tensor.pgs.com [157.147.132.150]) by hap.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id LAA23240 for ; Tue, 22 Feb 2000 11:33:52 -0600 (CST) Received: from prg01.hstn.tensor.pgs.com (localhost [127.0.0.1]) by prg01.hstn.tensor.pgs.com (8.8.8+Sun/8.8.8) with ESMTP id LAA27559 for ; Tue, 22 Feb 2000 11:33:50 -0600 (CST) Message-Id: <200002221733.LAA27559@prg01.hstn.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Re: Crashing netscape? In-Reply-To: Your message of "Tue, 22 Feb 2000 01:05:36 PST." Reply-To: shocking@prth.pgs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 11:33:46 -0600 From: Steve Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was some discussion of this over on the XFree mailing lists, and it transpired that netscape was using a pointer to some memory that had been freed some time back. This showed up in cases where you open up a stack of windows and then close them at random. There was a patch to work around this for libXt (I think). Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:51:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 0716437B6F0 for ; Tue, 22 Feb 2000 09:51:28 -0800 (PST) (envelope-from jpt@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id LAA81519; Tue, 22 Feb 2000 11:51:25 -0600 (CST) (envelope-from jpt@us.networkcs.com) Received: (from jpt@localhost) by us.networkcs.com (8.9.2/8.9.2) id LAA70135; Tue, 22 Feb 2000 11:51:25 -0600 (CST) (envelope-from jpt) From: Joseph Thomas Message-Id: <200002221751.LAA70135@us.networkcs.com> Subject: Re: ABIT BP6, UDMA-66 and wdc AC310200 To: sos@freebsd.dk (Soren Schmidt) Date: Tue, 22 Feb 2000 11:51:25 -0600 (CST) Cc: adsharma@sharmas.dhs.org (Arun Sharma), freebsd-current@FreeBSD.ORG In-Reply-To: <200002221730.SAA78748@freebsd.dk> from "Soren Schmidt" at Feb 22, 2000 06:30:21 PM X-Mailer: ELM [version 2.5 PL2] 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 Arun Sharma wrote: > > > Do you have the prober 80pin cable ?? if so please provide a verbose boot... > > > > Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very > > unscientific benchmark that I ran didn't seem to produce much of a difference > > between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s. > > There are almost no mesureable difference between UDMA33 and UDMA66, all > mesurements I've done (and have read about) sees little if no difference, > in fact some drives can be faster under UDMA33 even if they support the > higher rate too. > > > # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10 > > 10+0 records in > > 10+0 records out > > 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec) > > Thats probably close to what your drive can pull of the platters... > I get 22-23MB/sec off an IBM DPTA drive here with < 1% cpu usage, > so the driver is not the problem.. Look at your drive specs. I have one drive (Maxtor) with specs that say ~34MB to/from media and 66MB to/from interface (bus). Another piece of the puzzle is the amount of drive cache buffer. Again, I've seen between 512KB and 2MB. Mileage will vary... [It's the old 'burst rate of X' where the following 378 conditions must be met to reach the burst level...] > I have a config with 7 disks online, giving me a raw throughput > of ~100MB/s sustained, that is about the limit of what can be done > over the PCI bus... > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Joseph Thomas E/Mail: jpt@networkcs.com Network Computing Services, Inc. jpt@magic.net 1200 Washington Ave So. Tel: +1 612 337 3558 Minneapolis, MN 55415-1227 FAX: +1 612 337 3400 An elephant is a mouse with an operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:55:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 43CBA37B769 for ; Tue, 22 Feb 2000 09:55:29 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id MAA00415 for current@freebsd.org; Tue, 22 Feb 2000 12:55:27 -0500 (EST) (envelope-from mwlucas) Message-Id: <200002221755.MAA00415@blackhelicopters.org> Subject: Hardware for 4.0 To: current@freebsd.org Date: Tue, 22 Feb 2000 12:55:27 -0500 (EST) From: mwlucas@gltg.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm purchasing a server to run 4.0 on. It won't be in production immediately, but I need to get a quote ASAP. What SCSI card would people recommend? It doesn't need RAID. Any particular SCSI tape drive? I'll probably buy a midrange Asus motherboard and a nice Intel fxp NIC to go on it. Any other recommendations? Thanks, ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 9:56:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 8AA5B37B745 for ; Tue, 22 Feb 2000 09:56:34 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc062023.tokyo.jcom.ne.jp [210.155.62.23]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id CAA08307; Wed, 23 Feb 2000 02:55:26 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id CAA34503; Wed, 23 Feb 2000 02:54:54 +0900 (JST) Date: Wed, 23 Feb 2000 02:55:27 +0900 Message-ID: <86g0ulgm0g.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( In-Reply-To: In your message of "Tue, 22 Feb 2000 18:14:23 +0100 (CET)" <200002221714.SAA78664@freebsd.dk> References: <86hff1go7k.wl@archon.local.idaemons.org> <200002221714.SAA78664@freebsd.dk> User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.11 (Euglena viridis) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Associated I. Daemons MIME-Version: 1.0 (generated by EMIKO 1.13.11 - "Euglena viridis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 22 Feb 2000 18:14:23 +0100 (CET), Soren Schmidt wrote: > Could I have a verbote boot log please, that would give some hints... Sorry but could you tell me how to increase verbosity? > > ata-pci1: port 0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 0xe8900000-0xe891ffff irq 16 at device 12.0 on pci0 > > ata2 at 0xb000 irq -1 on ata-pci1 > > ad4: 19569MB [39761/16/63] at ata2-master using UDMA33 > > This probe suggests that you are not up to date on -current, that would > maybe also help... Okay, I'll update the kernel, but I built it last Saturday from the then up-to-date source tree. Not recent enough? -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 10: 0:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 723C837B72C for ; Tue, 22 Feb 2000 10:00:31 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id TAA17136; Tue, 22 Feb 2000 19:00:20 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id SAA03229; Tue, 22 Feb 2000 18:49:29 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 18:49:29 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222184929.A2934@titan.klemm.gtn.com> References: <20000222131429.A870@titan.klemm.gtn.com> <200002221239.NAA34644@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002221239.NAA34644@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 01:39:46PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote: > Try to use a "normal" ie 40pin cable, that will limit the disk to > UDMA33 mode, if that works, well... Hurray, using a normal cable works. I got 2 cables for $0 from a friend in a computershop ;-) A freebsd user, which I gave a promotion CD last year ;-) dmesg | grep ata: atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 ata2: at 0xa400 on atapci1 atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 Do you think there is a chance to get UDMA66 running, although for one disk UDMA/33 should be satisfactory ? BTW, what mode is MA DMA or something like this ? The abit supports two modes I never heard of before. PIO is known UDMA is known, but something like M DMA or MA DMA ??? Then an idea. What about something like atacontrol, to overwrite the speed settings, if you have to like in this case ? Would it be much work for you or worth the effort ? Would be fine to use the better cable with low speed... Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 10:30:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id DEAED37B742 for ; Tue, 22 Feb 2000 10:30:39 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id TAA19016; Tue, 22 Feb 2000 19:30:09 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id TAA04286; Tue, 22 Feb 2000 19:13:00 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 19:13:00 +0100 From: Andreas Klemm To: Akinori -Aki- MUSHA Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( Message-ID: <20000222191300.A4266@titan.klemm.gtn.com> References: <86hff1go7k.wl@archon.local.idaemons.org> <200002221714.SAA78664@freebsd.dk> <86g0ulgm0g.wl@archon.local.idaemons.org> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <86g0ulgm0g.wl@archon.local.idaemons.org>; from knu@idaemons.org on Wed, Feb 23, 2000 at 02:55:27AM +0900 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:55:27AM +0900, Akinori -Aki- MUSHA wrote: > At Tue, 22 Feb 2000 18:14:23 +0100 (CET), > Soren Schmidt wrote: > > Could I have a verbote boot log please, that would give some hints... > > Sorry but could you tell me how to increase verbosity? set boot_verbose=1 in the boot loader -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 10:34:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id C992237B754 for ; Tue, 22 Feb 2000 10:34:32 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id NAA00625; Tue, 22 Feb 2000 13:35:01 -0500 (EST) Date: Tue, 22 Feb 2000 13:35:01 -0500 From: Dan Moschuk To: mwlucas@gltg.com Cc: current@freebsd.org Subject: Re: Hardware for 4.0 Message-ID: <20000222133501.C503@spirit.jaded.net> References: <200002221755.MAA00415@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002221755.MAA00415@blackhelicopters.org>; from mwlucas@gltg.com on Tue, Feb 22, 2000 at 12:55:27PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | What SCSI card would people recommend? It doesn't need RAID. | Any particular SCSI tape drive? I like the Adapdec 2940 cards for low-medium end servers. | I'll probably buy a midrange Asus motherboard and a nice Intel fxp | NIC to go on it. Any other recommendations? The fxp cards are good, but I usually use the 3Com 905[BC] cards. -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 11: 6:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 6289A37B739 for ; Tue, 22 Feb 2000 11:06:12 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA62279; Tue, 22 Feb 2000 11:06:08 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002221906.LAA62279@gndrsh.dnsmgr.net> Subject: Re: Hardware for 4.0 In-Reply-To: <200002221755.MAA00415@blackhelicopters.org> from "mwlucas@gltg.com" at "Feb 22, 2000 12:55:27 pm" To: mwlucas@gltg.com Date: Tue, 22 Feb 2000 11:06:07 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I'm purchasing a server to run 4.0 on. It won't be in production > immediately, but I need to get a quote ASAP. > > What SCSI card would people recommend? It doesn't need RAID. > Any particular SCSI tape drive? We are partial to the TekRAM 390-F symbios 53C875 based controller. > I'll probably buy a midrange Asus motherboard and a nice Intel fxp > NIC to go on it. Any other recommendations? IBM Hard drives... And if you get the ASUS P3B board don't let it run in jumper free mode, nail the settings down with the jumpers as we have seen one too many times that this board likes to _think_ the CPU has changed and fails during a remote reboot. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 11: 8:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from defiant.quansoo.com (defiant.quansoo.com [63.66.225.90]) by hub.freebsd.org (Postfix) with ESMTP id DE03A37B742 for ; Tue, 22 Feb 2000 11:08:45 -0800 (PST) (envelope-from cgriffiths@quansoo.com) Received: from localhost (cgriffiths@localhost) by defiant.quansoo.com (8.9.3/8.9.3) with ESMTP id OAA00802 for ; Tue, 22 Feb 2000 14:08:43 -0500 (EST) (envelope-from cgriffiths@quansoo.com) X-Authentication-Warning: defiant.quansoo.com: cgriffiths owned process doing -bs Date: Tue, 22 Feb 2000 14:08:43 -0500 (EST) From: "Christopher T. Griffiths" To: freebsd-current@freebsd.org Subject: Upgrade to 4.0 current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was trying to upgrade from 3.4 -stable to 4.0 Current to test it out for the coming release of 4.0. I cvsup'd as of this morning at 10:00am and did a make buildworld. Then followed by a shutdown now then make installworld. I then got the following error: ===> lib/csu/i386-elf install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o install -c -o root -g wheel -m 444 crtbegin.So /usr/lib/crtbeginS.o install -c -o root -g wheel -m 444 crtend.So /usr/lib/crtendS.o ===> lib/libcom_err cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib ln -sf libcom_err.so.2 /usr/lib/libcom_err.so install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 ===> lib/libcom_err/doc install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Stop. *** Error code 1 Stop. If anyone can give me any pointers as to how to fix this that would be great. Thanks Chris --- Christopher T. Griffiths Engineering Department Quansoo Group Inc. cgriffiths@quansoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 11:13:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 4DEB737B794 for ; Tue, 22 Feb 2000 11:13:34 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc062023.tokyo.jcom.ne.jp [210.155.62.23]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id EAA13594; Wed, 23 Feb 2000 04:13:27 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id EAA35164; Wed, 23 Feb 2000 04:12:56 +0900 (JST) Date: Wed, 23 Feb 2000 04:13:30 +0900 Message-ID: <86ln4dkq3p.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( In-Reply-To: In your message of "Wed, 23 Feb 2000 02:55:27 +0900" <86g0ulgm0g.wl@archon.local.idaemons.org> References: <86hff1go7k.wl@archon.local.idaemons.org> <200002221714.SAA78664@freebsd.dk> <86g0ulgm0g.wl@archon.local.idaemons.org> User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.11 (Euglena viridis) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Associated I. Daemons MIME-Version: 1.0 (generated by EMIKO 1.13.11 - "Euglena viridis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I booted the system with boot_verbose=1, and the dmesg output was as follows. I wish this would help your investigation. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #30: Wed Feb 23 03:50:42 JST 2000 root@archon.local.idaemons.org:/usr/src/sys/compile/ARCHON Calibrating clock(s) ... TSC clock: 451010773 Hz, i8254 clock: 1193150 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0037e000 - 0x0fff7fff, 264740864 bytes (64634 pages) fb: new array size 4 avail memory = 256921600 (250900K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00faf10 bios32: Entry = 0xfb390 (c00fb390) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb3c0 pnpbios: Found PnP BIOS data at 0xc00fbff0 pnpbios: Entry = f0000:c018 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0362000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e8000000, size 23 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=19 map[20]: type 1, range 32, base 0000a000, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00005000, size 4 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x9005, dev=0x0010, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[10]: type 1, range 32, base 0000a400, size 8 map[14]: type 1, range 64, base e8920000, size 12 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[10]: type 1, range 32, base e8921000, size 12 map[14]: type 1, range 32, base 0000a800, size 5 map[18]: type 1, range 32, base e8800000, size 20 Freeing (NOT implemented) redirected PCI irq 5. found-> vendor=0x1274, dev=0x5000, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[10]: type 1, range 32, base 0000ac00, size 6 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x105a, dev=0x4d38, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base 0000b000, size 3 map[14]: type 1, range 32, base 0000b400, size 2 map[18]: type 1, range 32, base 0000b800, size 3 map[1c]: type 1, range 32, base 0000bc00, size 2 map[20]: type 1, range 32, base 0000c000, size 6 map[24]: type 1, range 32, base e8900000, size 17 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x102b, dev=0x0521, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base e4000000, size 24 map[14]: type 1, range 32, base e0000000, size 14 map[18]: type 1, range 32, base e1000000, size 23 pci1: on pcib1 pci1: Matrox MGA G200 AGP graphics accelerator (vendor=0x102b, dev=0x0521) at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: at device 7.1 on pci0 atapci0: Busmastering DMA not enabled ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata0: mask=00 status0=ff status1=ff ata0: probe allocation failed ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0001 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x5000-0x500f at device 7.3 on pci0 ahc0: port 0xa400-0xa4ff mem 0xe8920000-0xe8920fff irq 17 at device 8.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 403 instructions downloaded fxp0: port 0xa800-0xa81f mem 0xe8800000-0xe88fffff,0xe8921000-0xe8921fff irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:14:cf:35 bpf: fxp0 attached pcm0: port 0xac00-0xac3f irq 18 at device 10.0 on pci0 pcm: setmap 7000, 10000; 0xcb377000 -> 7000 pcm: setmap 17000, 10000; 0xcb387000 -> 17000 atapci1: port 0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 0xe8900000-0xe891ffff irq 16 at device 12.0 on pci0 ata2: iobase=0xb000 altiobase=0xb400 bmaddr=0xc000 ata2: mask=03 status0=50 status1=00 ata2: mask=03 status0=50 status1=00 ata2: devices = 0x1 ata2: at 0xb000 on atapci1 ata3: iobase=0xb800 altiobase=0xbc00 bmaddr=0xc008 ata3: mask=03 status0=00 status1=00 ata3: mask=03 status0=00 status1=00 ata3: devices = 0x0 ata3: probe allocation failed Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 1a 03 3c psm: status 1a 03 3c psm: status 1a 03 3c psm: status 10 00 64 psm: data c8 c6 51 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0-51, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached isa_probe_children: probing PnP devices SMP: enabled INTs: 1, 3, 4, 6, 7, 12, 16, 17, 18, 19, apic_imen: 0x00f0ef25 BIOS Geometries: 0:022afe3f 0..554=555 cylinders, 0..254=255 heads, 1..63=63 sectors 1:022afe3f 0..554=555 cylinders, 0..254=255 heads, 1..63=63 sectors 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 bpf: sl0 attached bpf: ppp0 attached new masks: bio 48010040, tty 4304109a, net 470c109a bpf: lo0 attached Linux-ELF exec handler installed SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ata2-master: success setting up UDMA2 mode on Promise chip ad4: ATA-4 disk at ata2 as master ad4: 19569MB (40079088 sectors), 39761 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA33 ad4: piomode=4 dmamode=2 udmamode=2 cblid=1 Creating DISK ad4 Creating DISK wd4 Waiting 3 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0 (probe2:ahc0:0:2:0): Invalid field in CDB ahc0: target 2 synchronous at 16.0MHz, offset = 0x10 ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 40.0MHz, offset = 0xf ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 40.0MHz, offset = 0xf Creating DISK da0 Creating DISK da1 Creating DISK cd0 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number RD3M0557 pass0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number RD2M2470 pass1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 19.230MB/s transfers (19.230MHz, offset 16) Mounting root from ufs:/dev/da1s1a (cd0:ahc0:0:2:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:2:0): NOT READY asc:3a,0 (cd0:ahc0:0:2:0): Medium not present cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number RD3M0557 da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number RD2M2470 da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1s1: type 0xa5, start 63, end = 2361554, size 2361492 : OK da1s2: type 0xa5, start 2361555, end = 8916074, size 6554520 : OK start_init: trying /sbin/init da0s1: type 0x6, start 63, end = 192779, size 192717 : OK da0s2: type 0xa5, start 192780, end = 771119, size 578340 : OK da0s3: type 0xa5, start 6522390, end = 8916074, size 2393685 : OK da0s4: type 0x5, start 771120, end = 6522389, size 5751270 : OK ad4s1: type 0xa5, start 63, end = 8177084, size 8177022 : OK ad4s2: type 0xa5, start 8177085, end = 16354169, size 8177085 : OK ad4s3: type 0xa5, start 16354170, end = 24531254, size 8177085 : OK ad4s4: type 0xf, start 24531255, end = 40066109, size 15534855 : OK da0s5: type 0x7, start 771183, end = 6522389, size 5751207 : OK ad4s5: type 0x7, start 24531318, end = 28627829, size 4096512 ad4s5: C/H/S start 1023/1/1 (16434558) != start 24531318: invalid ad4s1: type 0xa5, start 63, end = 8177084, size 8177022 : OK ad4s2: type 0xa5, start 8177085, end = 16354169, size 8177085 : OK ad4s3: type 0xa5, start 16354170, end = 24531254, size 8177085 : OK ad4s4: type 0xf, start 24531255, end = 40066109, size 15534855 : OK ad4s5: type 0x7, start 24531318, end = 28627829, size 4096512 ad4s5: C/H/S start 1023/1/1 (16434558) != start 24531318: invalid splash: image decoder found: logo_saver /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-438 $ /dev/vmmon: Module vmmon: initialized bpf: vmnet1 attached -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 11:26: 2 2000 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 8EB5037B751 for ; Tue, 22 Feb 2000 11:25:58 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA08637; Tue, 22 Feb 2000 14:25:45 -0500 (EST) (envelope-from wollman) Date: Tue, 22 Feb 2000 14:25:45 -0500 (EST) From: Garrett Wollman Message-Id: <200002221925.OAA08637@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: mwlucas@gltg.com, current@FreeBSD.ORG Subject: Re: Hardware for 4.0 In-Reply-To: <200002221906.LAA62279@gndrsh.dnsmgr.net> References: <200002221755.MAA00415@blackhelicopters.org> <200002221906.LAA62279@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > IBM Hard drives... If you can actually get them.... Last time I bought a drive we weren't able to get IBM in any reasonable timeframe and ended up with a Seagate instead. (And that Cheetah 18LP's not a bad drive, either.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 11:46: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 9678B37B754 for ; Tue, 22 Feb 2000 11:45:51 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id VAA85124; Tue, 22 Feb 2000 21:45:08 +0200 (EET) (envelope-from ru) Date: Tue, 22 Feb 2000 21:45:08 +0200 From: Ruslan Ermilov To: "Christopher T. Griffiths" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade to 4.0 current Message-ID: <20000222214508.B81744@relay.ucb.crimea.ua> Mail-Followup-To: "Christopher T. Griffiths" , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Christopher T. Griffiths on Tue, Feb 22, 2000 at 02:08:43PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! The set of correct instructions is provided in the latest src/UPDATING. There is a bootstrapping problem with texinfo, and you should use -DNOINFO on the first installworld for it to complete. Anyway, just follow the instructions from the src/UPDATING and you should be OK. On Tue, Feb 22, 2000 at 02:08:43PM -0500, Christopher T. Griffiths wrote: > Hello, > > I was trying to upgrade from 3.4 -stable to 4.0 Current to test it out for > the coming release of 4.0. > > > I cvsup'd as of this morning at 10:00am and did a make buildworld. Then > followed by a shutdown now then make installworld. > > > I then got the following error: > > ===> lib/csu/i386-elf > install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o > install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o > install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o > install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o > install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o > install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o > install -c -o root -g wheel -m 444 crtbegin.So /usr/lib/crtbeginS.o > install -c -o root -g wheel -m 444 crtend.So /usr/lib/crtendS.o > ===> lib/libcom_err > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 > /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 > /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include > install -c -o root -g wheel -m 444 libcom_err.a /usr/lib > install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib > install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib > ln -sf libcom_err.so.2 /usr/lib/libcom_err.so > install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." > --defentry="* libcom_err: (com_err). A Common Error Description > Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development > tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > If anyone can give me any pointers as to how to fix this that would be > great. > > Thanks > > Chris > > > --- > Christopher T. Griffiths > Engineering Department > Quansoo Group Inc. > cgriffiths@quansoo.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 12:10:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 363B537B59D for ; Tue, 22 Feb 2000 12:10:27 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA62402; Tue, 22 Feb 2000 12:10:13 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002222010.MAA62402@gndrsh.dnsmgr.net> Subject: Re: Hardware for 4.0 In-Reply-To: <200002221925.OAA08637@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 22, 2000 02:25:45 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 22 Feb 2000 12:10:12 -0800 (PST) Cc: mwlucas@gltg.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > IBM Hard drives... > > If you can actually get them.... Last time I bought a drive we > weren't able to get IBM in any reasonable timeframe and ended up with > a Seagate instead. (And that Cheetah 18LP's not a bad drive, either.) Should you run into that problem again give me a call. We deal directly with one of the larger official distributors of IBM hard drives. Last inventory check showed about 4,000+ IBM 25L1900/25L1910's on the shelf. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 12:29:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8FE8837B705 for ; Tue, 22 Feb 2000 12:29:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA79290; Tue, 22 Feb 2000 21:29:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002222029.VAA79290@freebsd.dk> Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( In-Reply-To: <86ln4dkq3p.wl@archon.local.idaemons.org> from Akinori -Aki- MUSHA at "Feb 23, 2000 04:13:30 am" To: knu@idaemons.org (Akinori -Aki- MUSHA) Date: Tue, 22 Feb 2000 21:29:30 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Akinori -Aki- MUSHA wrote: > Alright, I booted the system with boot_verbose=1, and the dmesg > output was as follows. I wish this would help your investigation. It does: > ata2-master: success setting up UDMA2 mode on Promise chip > ad4: ATA-4 disk at ata2 as master > ad4: 19569MB (40079088 sectors), 39761 cyls, 16 heads, 63 S/T, 512 B/S > ad4: 16 secs/int, 1 depth queue, UDMA33 > ad4: piomode=4 dmamode=2 udmamode=2 cblid=1 ^^^^^^^^^^^^^^^^^^ The disk reports it can do at max UDMA2 mode (ATA33), so thats why the ata driver dont put it at UDMA4 (ATA66)... -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 Feb 22 12:42: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 5C8D437B705; Tue, 22 Feb 2000 12:41:58 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id VAA13235; Tue, 22 Feb 2000 21:41:56 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 21:41:56 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Cc: freebsd-fs@freebsd.org Subject: Panic (ffs) #2 Message-ID: <20000222214156.A13189@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And here we are again. This time on another disk: dev = #amrd/0x20004, block = 2048, fs = /news/spool panic: ffs_blkfree: freeing free block Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.372 db> trace Debugger(c01e7ee3) at Debugger+0x35 panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70 ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd ffs_indirtrunc(c1db6d00,fffffff4,10bab0,ffffffff,0,d98cfd84) at ffs_indirtrunc+0x219 ffs_truncate(d8c79da0,0,0,0,c1d4d700) at ffs_truncate+0x6fd ufs_setattr(d98cfec8,d98cff3c,c0171857,d98cfec8,d98b52a0) at ufs_setattr+0x1ce ufs_vnoperate(d98cfec8,d98b52a0,c0206bac,d98cff80,d8c79da0) at ufs_vnoperate+0x15 ftruncate(d98b52a0,d98cff80,8098900,bfbff608,bfbf741f) at ftruncate+0x113 syscall(2f,280a002f,bfbf002f,bfbf741f,bfbff608) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 Dumping the 512 MB to disk now. See my previous Panic (ffs) mail on CURRENT for a almost exact problem. No soft-updates. Two different disks on two different controllers now. Current from 21 Feb. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 12:48:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3C57C37B75B for ; Tue, 22 Feb 2000 12:48:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA21516; Tue, 22 Feb 2000 13:47:45 -0700 (MST) (envelope-from ken) Date: Tue, 22 Feb 2000 13:47:45 -0700 From: "Kenneth D. Merry" To: Garrett Wollman Cc: "Rodney W. Grimes" , mwlucas@gltg.com, current@FreeBSD.ORG Subject: Re: Hardware for 4.0 Message-ID: <20000222134744.A21348@panzer.kdm.org> References: <200002221755.MAA00415@blackhelicopters.org> <200002221906.LAA62279@gndrsh.dnsmgr.net> <200002221925.OAA08637@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002221925.OAA08637@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Tue, Feb 22, 2000 at 02:25:45PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 14:25:45 -0500, Garrett Wollman wrote: > < said: > > > IBM Hard drives... > > If you can actually get them.... Last time I bought a drive we > weren't able to get IBM in any reasonable timeframe and ended up with > a Seagate instead. (And that Cheetah 18LP's not a bad drive, either.) Yeah, the Seagates are good too. I wish they'd come up with temperature sensors like IBM, though. :) But I'm surprised you had trouble getting IBM drives. NECX (www.necx.com) at least, usually has most IBM SCSI disks in stock. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 12:54:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id C472037B78B; Tue, 22 Feb 2000 12:54:28 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id PAA21722; Tue, 22 Feb 2000 15:54:23 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id PAA08695; Tue, 22 Feb 2000 15:54:21 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id PAA87131; Tue, 22 Feb 2000 15:54:21 -0500 (EST) Date: Tue, 22 Feb 2000 15:54:21 -0500 (EST) From: Thomas David Rivers Message-Id: <200002222054.PAA87131@lakes.dignus.com> To: asmodai@bart.nl, freebsd-current@FreeBSD.ORG Subject: Re: Panic (ffs) #2 Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <20000222214156.A13189@lucifer.bart.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And here we are again. > > This time on another disk: > > dev = #amrd/0x20004, block = 2048, fs = /news/spool > panic: ffs_blkfree: freeing free block > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.372 > db> trace > Debugger(c01e7ee3) at Debugger+0x35 > panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70 > ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd Aha! The Dave Rivers' memorial panic rears its ugly head! This is exactly the panic's I reported years ago; but we've never been able to track down... [Even the same block number I believe] You may want to scan the archives to read more about my investigations; which never went anywhere... (sigh) I describe a way to reproduce it on some versions of FreeBSD, you might want to see if you can get a reliable reproduction, etc... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 12:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 8F2BF37B5B6 for ; Tue, 22 Feb 2000 12:57:20 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id MAA30629; Tue, 22 Feb 2000 12:56:09 -0800 (PST) From: Archie Cobbs Message-Id: <200002222056.MAA30629@bubba.whistle.com> Subject: Re: IP tunnel In-Reply-To: <87og9eg413.fsf@rock.gnt.kiev.ua> from Cob at "Feb 18, 2000 01:10:16 pm" To: cob@gnt.kiev.ua Date: Tue, 22 Feb 2000 12:56:09 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cob writes: > What about ${subj} in current? > Or maybe someone know how to make > ip tunnel on current using patches, tools, etc.? One way is exhibited in /usr/share/examples/netgraph/udp.tunnel. -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 Feb 22 13: 4:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id EEF0337B6D1; Tue, 22 Feb 2000 13:04:36 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id NAA30708; Tue, 22 Feb 2000 13:04:34 -0800 (PST) From: Archie Cobbs Message-Id: <200002222104.NAA30708@bubba.whistle.com> Subject: Re: NETGRAPH patches (proposal) In-Reply-To: <20000221143707.21862.qmail@web119.yahoomail.com> from Maksim Yevmenkin at "Feb 21, 2000 06:37:07 am" To: m_evmenkin@yahoo.com (Maksim Yevmenkin) Date: Tue, 22 Feb 2000 13:04:34 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maksim Yevmenkin writes: > Here are some small patches for NETGRAPH. > These are against -current cvsup'ed yesterday around 8:30pm EST. > > http://home.earthlink.net/~evmax/ng.tar.gz > > It also includes small test program (based on nghook). > Compile and run it like: > > # ./a.out -a iface_name: divert > > NETGRAPH option in kernel config file is required. > > Here is the description. ng_ether node has two hooks ``divert'' and > ``orphan''. > It is possible to connect to the one of the hooks and intercept row Ethernet > frames. But there is no clean way to intercept frame, do something and > return it back to kernel. > > This patch provides additional hook ``divertin'' (mmm... name is not good, > i think) for each ng_ether node. > > Implementation issues > > This will not work for ``orphan'' frames. Since kernel drops it anyway, i > decided to leave it as it is. But is is possible to intercept ``orphan'' > packets, change it, and write back to ``divertin''. The "divertin" hook is a useful idea.. after 4.0-REL we can check something in based on your patches... 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 Feb 22 13:16: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 643D437B6CF for ; Tue, 22 Feb 2000 13:16:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA79494; Tue, 22 Feb 2000 22:15:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002222115.WAA79494@freebsd.dk> Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus In-Reply-To: <20000222184929.A2934@titan.klemm.gtn.com> from Andreas Klemm at "Feb 22, 2000 06:49:29 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 22 Feb 2000 22:15:42 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Andreas Klemm wrote: > On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote: > > Try to use a "normal" ie 40pin cable, that will limit the disk to > > UDMA33 mode, if that works, well... > > Hurray, using a normal cable works. I got 2 cables for $0 > from a friend in a computershop ;-) A freebsd user, which > I gave a promotion CD last year ;-) > > dmesg | grep ata: > > atapci0: at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled > atapci1: port 0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0 > ata2: at 0xa400 on atapci1 > atapci2: port 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0 > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 > > Do you think there is a chance to get UDMA66 running, although > for one disk UDMA/33 should be satisfactory ? There are two posibilities, either the cable is bad or the disk is bad. Since you could talk to it, and you didn't get ICRC errors, my bet is that the particular Maxtor model is just as broken as most of its other family memebers :( However there is no mesurable difference between running ATA66 and ATA33 as long as you have only one disk pr channel, and if you have more than one, the difference is still not worth mentioning... > BTW, what mode is MA DMA or something like this ? The abit supports > two modes I never heard of before. PIO is known UDMA is known, but > something like M DMA or MA DMA ??? That has to me MWDMA that the old 16MB/s mode, ata knows this mode too, but only uses it if no UDMA mdoes are possible... > Then an idea. What about something like atacontrol, to overwrite > the speed settings, if you have to like in this case ? Would it > be much work for you or worth the effort ? Well, there are some pretty tricky things with that, some of the controllers dont like you to step back in mode without serious handholding and special code.... > Would be fine to use the better cable with low speed... As long as you dont get any ICRC errors due to bad cableing there is no difference whatsoever... -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 Feb 22 13:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id E5A2837B6A5 for ; Tue, 22 Feb 2000 13:26:21 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id NAA08563 for ; Tue, 22 Feb 2000 13:30:45 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id NAA66956; Tue, 22 Feb 2000 13:27:59 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: <19347.951098777@zippy.cdrom.com> From: Joel Ray Holveck Date: 20 Feb 2000 20:49:32 -0800 In-Reply-To: "Jordan K. Hubbard"'s message of "Sun, 20 Feb 2000 18:06:17 -0800" Message-ID: <86d7prqhwj.fsf@detlev.UUCP> Lines: 30 X-Mailer: Gnus v5.7/Emacs 20.5 MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would obviously not be hard to write a set of stubs for these > things, getting those stubs called selectively in the "no real RSA" > case also not being very difficult. One way would be to put them in a > lower version-numbered shared lib, like OpenBSD did it, so that the > application would fall through to link against the stub version if > librsaref.so.2 was not found. Another, better way, would be to use > weak symbols and a dlopen(), e.g.: [snip] > That way it's not an error to link against the openssl library without > librsa, though if you do link with -lrsa and -lssl then you can also > skip the stubs entirely and not encur the dlopen() overhead, something > which makes the -static (or stand-alone) linkers happy. I'm not familiar with OpenSSL's link lines, but here's a question. Are linking with -lrsa and -lssl normally necessary, or is it normally just -lssl? If it't the latter, then programs that expect to link against OpenSSL will succeed to build and link, but fail to run properly. I realize that every OS has its quirks for building packages, but I find this sort of change vulgar. Naturally, if OpenSSL-based programs *expect* to build against -lrsa and -lssl, then I have no objections. joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 13:27:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id 7B07137B7E8; Tue, 22 Feb 2000 13:27:04 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id NAA08567; Tue, 22 Feb 2000 13:31:28 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id NAA66959; Tue, 22 Feb 2000 13:28:45 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: "'Kris Kennaway'" , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current References: <1D45ABC754FB1E4888E508992CE97E4F059CE8@teknos.teknos.com> From: Joel Ray Holveck Date: 20 Feb 2000 17:23:48 -0800 In-Reply-To: "Victor A. Salaman"'s message of "Sun, 20 Feb 2000 03:12:26 -0400" Message-ID: <86k8jzqrfe.fsf@detlev.UUCP> Lines: 80 X-Mailer: Gnus v5.7/Emacs 20.5 MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just read several documents from www.eff.org, www.rsa.com, and > www.openssl.org and have failed to find anything in there, that forbids us > from not using openssl's RSA version. RSA has a patent for the algorithm, > and they have provided a reference implementation to help the adoption of > the algorithm. In their license (RSAREF) it says you can't export the code > outside USA, but the US ITAR laws don't say anything about importing. So in > theory, if the CD was made outside the USA, then it could be imported > without a single problem. I'm not a lawyer. Here's my take. Let's consider that we are in Switzerland making the One Great CD that I may legally use inside of the US. (We may assume that I also may use it outside of the US, but that's irrelevant to this discussion.) While I use this CD, I'm using the RSA algorithm. This is covered by US patent 4,405,829, meaning that I have to have RSA Labs' permission to use it. I am now obligated to obtain their permission. I have their permission to use it, so long as I'm using RSAREF, and I'm using it for non-commercial purposes. So, we now have to use RSAREF. However, since we're making this in Switzerland, and RSAREF originated in the US, we (or somebody else) must have exported it from the US. We could put a non-RSAREF algorithm on it, but then I do not have RSA's permission to use it in the US. This is entirely disregarding the expense of setting up a Walnut Creek CD-ROM plant in Switzerland, or flying Jordan out of the country every time he wants to build a new release. > The whole RSA scheme is bogus, because anyone in the world can get an > implementation of RSA, so its widely accesible, so why all this > RSAREF/non-RSAREF mumbo-jumbo? The whole RSA scheme is not entirely bogus, at least not from a commercial point of view. The RSAREF/non-RSAREF scheme is the implementation of RSA's goals within our current legal framework. Anybody who is inside the US and using RSA for commercial purposes must pay RSA Labs. That is the purpose of RSA's patent. Encouraging R&D using RSA is the purpose of RSAREF. Then, people outside of the US want a way to use RSA. Because of ITAR, they can't get at RSAREF. So, that is the purpose of non-RSAREF. No doubt RSA Labs would love to be able to patent their algorithm outside of the US and export their software, but ITAR forbds it. > Perhaps we should send e-mail to RSA to clarify this, and in light > of this, ask for permission to distribute RSA with the base OS. Gee, > we can get RSA anyway, so what's the point on making harder? RSA is not likely to be helpful. They cannot allow non-US users to use RSAREF, so the best they could do would be to allow a non-RSAREF implementation to be used in the US. That may open them up to certain legal problems, and doesn't gain them anything, so they are very likely to say "go away". > Does anyone have ANY document saying that if you are in the US you are > obligued to use RSAREF? Patent #4,405,829, issued 20Sep1983, availible online from the horse's mouth at http://164.195.100.11/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1='4,405,829'.WKU.&OS=PN/4,405,829&RS=PN/4,405,829 This means that if I'm in the US, I must have permission from RSA Labs to use the RSA algorithm. Now, there are two main ways to get permission. Either set up an agreement with RSA (and probably give them money as part of the agreement), or use RSAREF. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped --BAC18391.951126129/detlev.piqnet.org-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 13:29:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id 0D28537B798 for ; Tue, 22 Feb 2000 13:29:06 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id NAA08571 for ; Tue, 22 Feb 2000 13:33:29 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id NAA67108; Tue, 22 Feb 2000 13:30:45 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.UUCP: joelh set sender to joelh@gnu.org using -f To: "'FreeBSD Current list'" Subject: Re: Rc2 install References: From: Joel Ray Holveck Date: 19 Feb 2000 15:05:01 -0800 In-Reply-To: Marc Schneiders's message of "Sat, 19 Feb 2000 01:10:43 +0100 (CET)" Message-ID: <86og9cbxpe.fsf@detlev.UUCP> Lines: 24 X-Mailer: Gnus v5.7/Emacs 20.5 MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've come to the conclusion that the -current stuff really doesn't install >> on an 8 Meg machine anymore. I have an old 486/66 machine I'm using >> to play with the current-RC's, and it consistantly dies loading the 'bin' >> stuff. Perhaps I'll make a MINIGENERIC kernel without some extraneous items like NFS, etc. I can attest that 3.3 can be made to install with 8MB, albeit with some work. I've got a machine with only 8MB that can't be upgraded or replaced. It took some work to get it 3.3 to install (I think I ended up using a different installation method than I originally planned, but I forgot to document it). Anyway, I'll probably bring it to 4.0 after its release, and I'll try to document whatever I do to make it happen. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped --BAE18391.951126130/detlev.piqnet.org-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 13:38:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 2F4E937B705; Tue, 22 Feb 2000 13:38:51 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (a-211.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id NAA39735; Tue, 22 Feb 2000 13:38:47 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id NAA00790; Tue, 22 Feb 2000 13:38:47 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <38B301E6.23151221@sftw.com> Date: Tue, 22 Feb 2000 21:38:46 +0000 From: Nick Sayer Reply-To: nsayer@FreeBSD.ORG X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-current@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG Subject: Re: Weird AMD panics caused by VMware?! References: <20000217221219.A448@jupiter.delta.ny.us> <38B2F3E8.C8FF1F21@sftw.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To followup to myself, I think I have this pinned down... In line 403 of /sys/kern/vfs_cache.c, ncpp is somehow becoming 0. I believe that the trap is in ncp = LIST_FIRST(ncpp); -- LIST_FIRST(x) expands to ((x)->lh_first). That ends up being a dereference of NULL, which causes the trap and panic. As to how ncpp ends up being null, that's a good question, given it's the variable in the for loop at line 402. cache_zap() can't really have a side effect, since ncpp is a stack variable. I am going to try rewriting the outer for() loop as for(i=nchash ; i>=0 ; i--) and the initialization of the inner loop as ncp = LIST_FIRST(&(nchashtbl[i])) just in case cache_zap() causes the value of nchashtbl to change (just how the hell THAT would happen is way beyond me). Nick Sayer wrote: > (crossposting to -current in case it's not VMware related) > > I have a serial console running on the machine, so now I can tell the > difference between > a panic and a hang. :-) > > With that said, I now have a complete dump from one of these trap panics. > Here is a > stack trace: > > #0 0xc0152d28 in boot () > #1 0xc01530ac in poweroff_wait () > #2 0xc02571f9 in trap_fatal () > #3 0xc0256ed7 in trap_pfault () > #4 0xc0256a9a in trap () > #5 0xc0177da0 in cache_purgevfs () > #6 0xc017e6f1 in dounmount () > #7 0xc017e681 in unmount () > #8 0xc0257437 in syscall () > #9 0xc024b946 in Xint0x80_syscall () > #10 0x8057585 in ?? () > [etc] > > The machine is running amd, and my home directory is amd mounted. That is > the only > conceivable reason I can think why an 'unmount' would be in progress. > > Sure enough, ps aux on the core shows: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 841 97.7 0.0 1100 0 ?? R 31Dec69 0:00.00 (amd) > nsayer 699 8.5 0.0 59480 0 #C1 R 31Dec69 4:46.96 (vmware) > root 2 0.0 0.0 0 0 ?? RL 31Dec69 0:03.56 > (pagedaemon) > root 3 0.0 0.0 0 0 ?? DL 31Dec69 0:00.42 (vmdaemon) > root 4 0.0 0.0 0 0 ?? RL 31Dec69 0:00.00 (bufdaemon) > > root 5 0.0 0.0 0 0 ?? RL 31Dec69 0:02.17 (syncer) > [...] > > Does anyone recognize this? What other information can I get that would be > of use? > > "Vladimir N. Silyaev" wrote: > > > > My machine here at the office gets these a _lot_ whenever I'm running > > > vmware: > > [skipped] > > > > >This machine also seems to hang a lot, but it could be that the hangs > > >are just these happening behind X so I can't see them. > > As you wrote below, you are have another box. So just try to use > > serial console (that will be provide a possibility to always > > see a panic message), also will be a right thing to compile kernel > > with DDB, that will provide some more information. > > > > > They always happen with amd as the current process. They frequently > > > happen when > > >vmware is running. They never happen at other times. > > The FreeBSD vmmon has a 'historical' bug - it's clear 'GS' register. > > But I was never encounter problem with them. And more I was > > so impressed by the fact that I was never encountered any vmware(vmmon) > > related problem. > > > > -- > > Vladimir Silyaev > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-emulation" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" 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 Feb 22 13:56:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id 7321537B6FF; Tue, 22 Feb 2000 13:56:00 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from mo3980r1.ems.att.com ([135.38.12.14]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id QAA02931; Tue, 22 Feb 2000 16:55:29 -0500 (EST) Received: from njb140bh1.ems.att.com by mo3980r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id QAA24003; Tue, 22 Feb 2000 16:51:08 -0500 (EST) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2650.21) id ; Tue, 22 Feb 2000 16:55:28 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Archie Cobbs'" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: RE: NETGRAPH patches (proposal) Date: Tue, 22 Feb 2000 16:55:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here is the description. ng_ether node has two hooks ``divert'' and > > ``orphan''. > > It is possible to connect to the one of the hooks and > intercept row Ethernet > > frames. But there is no clean way to intercept frame, do > something and > > return it back to kernel. > > > > This patch provides additional hook ``divertin'' (mmm... > name is not good, > > i think) for each ng_ether node. > > > > Implementation issues > > > > This will not work for ``orphan'' frames. Since kernel > drops it anyway, i > > decided to leave it as it is. But is is possible to > intercept ``orphan'' > > packets, change it, and write back to ``divertin''. > > The "divertin" hook is a useful idea.. after 4.0-REL we can check > something in based on your patches... > ok. i just have a dumb question. what is the big deal with updating ether_shost in ethernet header in ngether_rcvdata. since we are passing raw ethernet frame, why should we update ether_shost? wouldn't it be nice to make it optional? just another control message? Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 13:56:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id D14B237B747; Tue, 22 Feb 2000 13:55:51 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id WAA13862; Tue, 22 Feb 2000 22:55:43 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 22:55:43 +0100 From: Jeroen Ruigrok van der Werven To: Thomas David Rivers Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Panic (ffs) #2 Message-ID: <20000222225542.A13664@lucifer.bart.nl> References: <20000222214156.A13189@lucifer.bart.nl> <200002222054.PAA87131@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002222054.PAA87131@lakes.dignus.com>; from rivers@dignus.com on Tue, Feb 22, 2000 at 03:54:21PM -0500 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000222 21:55], Thomas David Rivers (rivers@dignus.com) wrote: >> >> And here we are again. >> >> This time on another disk: >> >> dev = #amrd/0x20004, block = 2048, fs = /news/spool >> panic: ffs_blkfree: freeing free block >> Debugger("panic") >> Stopped at Debugger+0x35: movb $0,in_Debugger.372 >> db> trace >> Debugger(c01e7ee3) at Debugger+0x35 >> panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70 >> ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd > > Aha! The Dave Rivers' memorial panic rears its ugly head! > > This is exactly the panic's I reported years ago; but we've never > been able to track down... [Even the same block number I believe] Well, at this rate I can drop debugs on the lists at a rate of one per day. > You may want to scan the archives to read more about my investigations; If they were up. Thank god I have some personal archives... Hope I'll get some info from them. > which never went anywhere... (sigh) I describe a way to reproduce > it on some versions of FreeBSD, you might want to see if you can > get a reliable reproduction, etc... Hah, reliable reproduction, try to let the box stay up for a day or two, bang. So far in this existance of the box, I have had 4 ffs panics and 1 tcp... If this were a debug box I'd say ok, well cool... But this is in fact a machine so close to the RC of 4.0 that I am not sure I want to run production servers on it. Add to that mix that I am a b-rated coder, just learning about gdb, and on filesystem level and even dumber than (insert locally dumb idiot here). Then the logical step might be to say, well, then the hardware must be faulty... No way Jose... I have tested this box in every way possible, even detected incorrect CAS/RAS latency settings on the box in the BIOS for the memory. Anyways: [root@tyr] (4) # gdb -k /kernel.debug vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2625536 initial pcb at 21c9e0 panicstr: from debugger panic messages: --- panic: ffs_blkfree: freeing free block panic: from debugger Uptime: 39m4s amrd0: still open, can't shutdown dumping to dev #da/0x20001, offset 524312 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 ! 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc01244e1 in db_panic (addr=-1071886047, have_addr=0, count=-1, modif=0xd8b7fb88 "") at ../../ddb/db_command.c:433 #3 0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c, aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333 #4 0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc012665f in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc01c4ec5 in kdb_trap (type=3, code=0, regs=0xd8b7fc90) at ../../i386/i386/db_interface.c:158 #7 0xc01d05f4 in trap (frame={tf_fs = -1072431088, tf_es = -701956080, tf_ds = -701956080, tf_edi = -838037504, tf_esi = 256, tf_ebp = -659030824, tf_isp = -659030852, tf_ebx = -1071700000, tf_edx = 0, tf_ecx = 1021, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071886047, tf_cs = 8, tf_eflags = 582, tf_esp = -1071668385, tf_ss = -1071743261}) at ../../i386/i386/trap.c:549 #8 0xc01c5121 in Debugger (msg=0xc01e7ee3 "panic") at machine/cpufunc.h:64 #9 0xc0143d58 in panic (fmt=0xc01f27e0 "ffs_blkfree: freeing free block") at ../../kern/kern_shutdown.c:552 #10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192) at ../../ufs/ffs/ffs_alloc.c:1337 #11 0xc0197be1 in ffs_truncate (vp=0xd8d11fe0, length=0, flags=0, cred=0x0, p=0xd8b320c0) at ../../ufs/ffs/ffs_inode.c:337 #12 0xc019c8e6 in ufs_inactive (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_inode.c:84 #13 0xc01a1985 in ufs_vnoperate (ap=0xd8b7feb8) at ../../ufs/ufs/ufs_vnops.c:2283 #14 0xc016d0ae in vput (vp=0xd8d11fe0) at vnode_if.h:794 #15 0xc01703b9 in unlink (p=0xd8b320c0, uap=0xd8b7ff80) at ../../kern/vfs_syscalls.c:1421 #16 0xc01d0e96 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 1, tf_esi = 134721536, tf_ebp = -1077945076, tf_isp = -659030060, tf_ebx = 134750720, tf_edx = 134750812, tf_ecx = 0, tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 134533504, tf_cs = 31, tf_eflags = 647, tf_esp = -1077945120, tf_ss = 47}) at ../../i386/i386/trap.c:1073 #17 0xc01c57c6 in Xint0x80_syscall () #18 0x80482c3 in ?? () #19 0x80480f9 in ?? () (kgdb) up 10 #10 0xc0195c61 in ffs_blkfree (ip=0xc1d92200, bno=6560, size=8192) at ../../ufs/ffs/ffs_alloc.c:1337 1337 panic("ffs_blkfree: freeing free block"); More info will be coming shortly... As usual, advice, hints, tips (on how to maintain my sanity for example) are highly appreciated. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands el: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14: 3:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 1F6C837B754 for ; Tue, 22 Feb 2000 14:03:32 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc062023.tokyo.jcom.ne.jp [210.155.62.23]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id HAA22968; Wed, 23 Feb 2000 07:03:25 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id HAA36539; Wed, 23 Feb 2000 07:02:53 +0900 (JST) Date: Wed, 23 Feb 2000 07:03:27 +0900 Message-ID: <8666vgao9c.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise Ultra66 + Seagate ATA/66 => Ultra ATA/33 :( In-Reply-To: In your message of "Tue, 22 Feb 2000 21:29:30 +0100 (CET)" <200002222029.VAA79290@freebsd.dk> References: <86ln4dkq3p.wl@archon.local.idaemons.org> <200002222029.VAA79290@freebsd.dk> User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.11 (Euglena viridis) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Associated I. Daemons MIME-Version: 1.0 (generated by EMIKO 1.13.11 - "Euglena viridis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 22 Feb 2000 21:29:30 +0100 (CET), Soren Schmidt wrote: > > ad4: piomode=4 dmamode=2 udmamode=2 cblid=1 > ^^^^^^^^^^^^^^^^^^ > > The disk reports it can do at max UDMA2 mode (ATA33), so thats why > the ata driver dont put it at UDMA4 (ATA66)... Ah! I tried resetting the /66 activation flag by Seagate's utility, and now it's successfully proved at /66 mode! :) I still wonder why it was ok on WinNT 4.0, but anyway I'm now happy on FreeBSD with your ata driver. Thanks! -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14:20:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id DDEAD37B7AB for ; Tue, 22 Feb 2000 14:20:07 -0800 (PST) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (root@guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id IAA23668; Wed, 23 Feb 2000 08:49:46 +1030 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id IAA24210; Wed, 23 Feb 2000 08:49:43 +1030 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222132327.O5555@lucifer.bart.nl> Date: Wed, 23 Feb 2000 08:49:42 +1030 (CST) From: "Daniel O'Connor" To: Jeroen Ruigrok van der Werven Subject: Re: status of 'device awe' ? Cc: current@FreeBSD.ORG, Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: > Should be used instead. > I am so in favor of just declaring voxware dead... But the armchair > generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14:21:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from Stalker.Alfacom.net (SAT.Alfacom.net [207.241.164.112]) by hub.freebsd.org (Postfix) with ESMTP id 45DA637B7AB for ; Tue, 22 Feb 2000 14:20:42 -0800 (PST) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (dup-50.alfacom.net [62.244.36.50]) by Stalker.Alfacom.net (8.9.0/8.9.0) with ESMTP id AAA24825 for ; Wed, 23 Feb 2000 00:20:30 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.9.3/8.9.3) with ESMTP id AAA08327 for ; Wed, 23 Feb 2000 00:20:22 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Wed, 23 Feb 2000 00:20:21 +0200 (EET) From: Vladimir Kushnir To: current@FreeBSD.ORG Subject: Re: "Interesting" failure mode for static linking with shared libs. In-Reply-To: <20000222090142.A29249@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, this is a (minor) bug in binutils (see patch below): ELF interpreteu is defined as /usr/lib/libc.so.1 rather than (here) /usr/libexec/ld-elf.so.1 On Tue, 22 Feb 2000, Martin Cracauer wrote: > In <32351.951188747@zippy.cdrom.com>, Jordan K. Hubbard wrote: > > root@zippy-> cc -fPIC -c stub.c > > root@zippy-> ld -shared -o stub.so stub.o > > root@zippy-> cc -static test.c -o test stub.so > > root@zippy-> ./test > > ELF interpreter /usr/lib/libc.so.1 not found > > Abort trap > > root@zippy-> cc -static test.c -o test stub.o > > root@zippy-> ./test > > Now in the client, calling doit() > > You have reached the stub. Please leave a message. > > As a workaround for a static binary, you should be able to use > -Xlinker -Bstatic > instead of > -static > > -static links the libs statically and also leaves out the dynamic > loading code from the binary. > > The former leaves the dynamic loading code in the binary, but links > the libs statically. You have a slightly bigger binary, but you don't > need the libs at runtime and you are resistent against changed/faked > libs, which might do the job you want static linking for. > > Martin > Regards, Vladimir --- /usr/src/contrib/binutils/bfd/elf32-i386.c.orig Tue Feb 9 21:57:33 1999 +++ /usr/src/contrib/binutils/bfd/elf32-i386.c Tue Feb 9 21:55:53 1999 @@ -249,7 +249,7 @@ /* The name of the dynamic interpreter. This is put in the .interp section. */ -#define ELF_DYNAMIC_INTERPRETER "/usr/lib/libc.so.1" +#define ELF_DYNAMIC_INTERPRETER "/usr/libexec/ld-elf.so.1" /* The size in bytes of an entry in the procedure linkage table. */ --- /usr/src/contrib/binutils/bfd/elf64-alpha.c.orig Wed Feb 10 00:39:39 1999 +++ /usr/src/contrib/binutils/bfd/elf64-alpha.c Wed Feb 10 00:40:05 1999 @@ -1018,7 +1018,7 @@ #define MAX_GOT_ENTRIES (64*1024 / 8) -#define ELF_DYNAMIC_INTERPRETER "/usr/lib/ld.so" +#define ELF_DYNAMIC_INTERPRETER "/usr/libexec/ld-elf.so.1" /* Handle an Alpha specific section when reading an object file. This is called when elfcode.h finds a section with an unknown type. -- ===========================|======================= Vladimir Kushnir | vkushnir@Alfacom.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 Tue Feb 22 14:26: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 569FA37B816; Tue, 22 Feb 2000 14:25:58 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id OAA42237; Tue, 22 Feb 2000 14:25:56 -0800 (PST) From: Archie Cobbs Message-Id: <200002222225.OAA42237@bubba.whistle.com> Subject: Re: NETGRAPH patches (proposal) In-Reply-To: from "Yevmenkin, Maksim N, CSCIO" at "Feb 22, 2000 04:55:21 pm" To: myevmenkin@att.com (Yevmenkin Maksim N CSCIO) Date: Tue, 22 Feb 2000 14:25:55 -0800 (PST) Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yevmenkin, Maksim N, CSCIO writes: > > > Here is the description. ng_ether node has two hooks ``divert'' and > > > ``orphan''. > > > It is possible to connect to the one of the hooks and > > intercept row Ethernet > > > frames. But there is no clean way to intercept frame, do > > something and > > > return it back to kernel. > > > > > > This patch provides additional hook ``divertin'' (mmm... > > name is not good, > > > i think) for each ng_ether node. > > > > > > Implementation issues > > > > > > This will not work for ``orphan'' frames. Since kernel > > drops it anyway, i > > > decided to leave it as it is. But is is possible to > > intercept ``orphan'' > > > packets, change it, and write back to ``divertin''. > > > > The "divertin" hook is a useful idea.. after 4.0-REL we can check > > something in based on your patches... > > > > ok. i just have a dumb question. what is the big deal with updating > ether_shost > in ethernet header in ngether_rcvdata. since we are passing raw ethernet > frame, > why should we update ether_shost? wouldn't it be nice to make it optional? > just another control message? I agree.. you should have to set the host address manually. -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 Feb 22 14:33:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id AC36737B796 for ; Tue, 22 Feb 2000 14:33:48 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id XAA14110; Tue, 22 Feb 2000 23:33:26 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 23:33:26 +0100 From: Jeroen Ruigrok van der Werven To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, Lyndon Nerenberg Subject: Re: status of 'device awe' ? Message-ID: <20000222233325.A14094@lucifer.bart.nl> References: <20000222132327.O5555@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from doconnor@gsoft.com.au on Wed, Feb 23, 2000 at 08:49:42AM +1030 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000222 23:25], Daniel O'Connor (doconnor@gsoft.com.au) wrote: > >On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: >> Should be used instead. >> I am so in favor of just declaring voxware dead... But the armchair >> generals wouldn't like that. > >The awe device controls the AWE's wavetable.. newpcm doesn't talk to this >(yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14:45: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 6F7AA37B777 for ; Tue, 22 Feb 2000 14:44:55 -0800 (PST) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (root@guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id JAA23774; Wed, 23 Feb 2000 09:14:52 +1030 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id JAA47897; Wed, 23 Feb 2000 09:14:52 +1030 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222233325.A14094@lucifer.bart.nl> Date: Wed, 23 Feb 2000 09:14:51 +1030 (CST) From: "Daniel O'Connor" To: Jeroen Ruigrok van der Werven Subject: Re: status of 'device awe' ? Cc: Lyndon Nerenberg , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: > That's why I wanted to kill voxware in 4.0, would allow pcm to be used > from default... Now we're stuck to the voxware crap for another release > cycle until 5.0 hits the public. You don't _have_ to use it :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14:46:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B546337B7AF for ; Tue, 22 Feb 2000 14:46:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA22857; Tue, 22 Feb 2000 15:46:04 -0700 (MST) (envelope-from ken) Date: Tue, 22 Feb 2000 15:46:04 -0700 From: "Kenneth D. Merry" To: Jeroen Ruigrok van der Werven Cc: "Daniel O'Connor" , current@FreeBSD.ORG, Lyndon Nerenberg Subject: Re: status of 'device awe' ? Message-ID: <20000222154604.A22803@panzer.kdm.org> References: <20000222132327.O5555@lucifer.bart.nl> <20000222233325.A14094@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000222233325.A14094@lucifer.bart.nl>; from asmodai@bart.nl on Tue, Feb 22, 2000 at 11:33:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote: > -On [20000222 23:25], Daniel O'Connor (doconnor@gsoft.com.au) wrote: > > > >On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: > >> Should be used instead. > >> I am so in favor of just declaring voxware dead... But the armchair > >> generals wouldn't like that. > > > >The awe device controls the AWE's wavetable.. newpcm doesn't talk to this > >(yet - no idea if there are any plans) > > newmidi is underway... > > That's why I wanted to kill voxware in 4.0, would allow pcm to be used > from default... Now we're stuck to the voxware crap for another release > cycle until 5.0 hits the public. Voxware may be "crap", but newpcm doesn't work right for my GUS PnP. (And yep, I sent mail to the multimedia list, which got some response, and I sent mail to Cameron, which got no response.) Voxware used to work fine, way back when. Luigi's pcm code worked fine as well with my GUS PnP. Maybe it's time for me to switch back to voxware from newpcm. I'm tired of getting static every once in a while when playing sound files. I don't see any reason to get rid of voxware before newpcm is fully functional. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 14:55: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id EA8C437B574; Tue, 22 Feb 2000 14:54:57 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id XAA14248; Tue, 22 Feb 2000 23:54:53 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 23:54:53 +0100 From: Jeroen Ruigrok van der Werven To: Thomas David Rivers Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Panic (ffs) #2 Message-ID: <20000222235453.A14224@lucifer.bart.nl> References: <20000222214156.A13189@lucifer.bart.nl> <200002222054.PAA87131@lakes.dignus.com> <20000222225542.A13664@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000222225542.A13664@lucifer.bart.nl>; from asmodai@bart.nl on Tue, Feb 22, 2000 at 10:55:43PM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *sigh* ignore the gdb output of this one... it was the old one. =( /var/crash was too full. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 15:35:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6743637B690 for ; Tue, 22 Feb 2000 15:35:20 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA27676; Wed, 23 Feb 2000 10:05:10 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38B2ACF3.F92BDB1@altavista.net> Date: Wed, 23 Feb 2000 10:05:10 +1030 (CST) From: "Daniel O'Connor" To: Maxim Sobolev Subject: Re: kdelibs port broken? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Feb-00 Maxim Sobolev wrote: > > Now, I'd look this up in the mailing lists, but the search is still down > > I do remember something about C++ stuff needing to be recompiled (which > > is > > why I'm rebuilding kdelibs in the first place).. > You have to rebuild qt2 first to be able to run moc. Ahh yes, that fixed it.. I rebuild qt142.. KDE libs works fine now, thanks :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 15:48: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id D395137B761 for ; Tue, 22 Feb 2000 15:48:00 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@17-034.008.popsite.net [209.69.196.34] (may be forged)) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id PAA08856; Tue, 22 Feb 2000 15:47:48 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id D4EAE1933; Tue, 22 Feb 2000 18:47:46 -0500 (EST) Date: Tue, 22 Feb 2000 18:47:46 -0500 From: Will Andrews To: Maxim Sobolev Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: kdelibs port broken? Message-ID: <20000222184746.B14314@shadow.blackdawn.com> References: <38B2ACF3.F92BDB1@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B2ACF3.F92BDB1@altavista.net>; from sobomax@altavista.net on Tue, Feb 22, 2000 at 05:36:19PM +0200 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 05:36:19PM +0200, Maxim Sobolev wrote: > You have to rebuild qt2 first to be able to run moc. ITYM Qt 1.45, not Qt2. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 15:48:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 269D437B7C3 for ; Tue, 22 Feb 2000 15:48:39 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@17-034.008.popsite.net [209.69.196.34] (may be forged)) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id PAA08875; Tue, 22 Feb 2000 15:48:32 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id D88DF1933; Tue, 22 Feb 2000 18:48:30 -0500 (EST) Date: Tue, 22 Feb 2000 18:48:30 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: Maxim Sobolev , freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: kdelibs port broken? Message-ID: <20000222184830.C14314@shadow.blackdawn.com> References: <38B2ACF3.F92BDB1@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 07:40:55AM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote: > ON that subject, has anyone tried compiling the KDE port with the new QT145 > port? In my original tests, Qt 1.45 works fine with the KDE ports. Do you have any problems with it? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 16:10:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from BSDpc.geek4food.org (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id 0C11D37B823 for ; Tue, 22 Feb 2000 16:10:04 -0800 (PST) (envelope-from andy@geek4food.org) Received: from mega.geek4food.org (mega.geek4food.org [192.168.1.57]) by BSDpc.geek4food.org (Postfix) with ESMTP id 3D439119C0; Tue, 22 Feb 2000 16:10:03 -0800 (PST) Received: (from andy@localhost) by mega.geek4food.org (8.9.3/8.9.3) id QAA84101; Tue, 22 Feb 2000 16:10:03 -0800 (PST) (envelope-from andy@geek4food.org) Date: Tue, 22 Feb 2000 16:10:02 -0800 From: Andy Sparrow To: "Kenneth D. Merry" Cc: Jeroen Ruigrok van der Werven , "Daniel O'Connor" , current@FreeBSD.ORG, Lyndon Nerenberg Subject: Re: status of 'device awe' ? Message-ID: <20000222161002.A83593@mega.geek4food.org> References: <20000222132327.O5555@lucifer.bart.nl> <20000222233325.A14094@lucifer.bart.nl> <20000222154604.A22803@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000222154604.A22803@panzer.kdm.org>; from ken@kdm.org on Tue, Feb 22, 2000 at 03:46:04PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 03:46:04PM -0700, Kenneth D. Merry wrote: > On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote: > > -On [20000222 23:25], Daniel O'Connor (doconnor@gsoft.com.au) wrote: > > > > > >On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: > > >> Should be used instead. > > >> I am so in favor of just declaring voxware dead... But the armchair > > >> generals wouldn't like that. > > > > > >The awe device controls the AWE's wavetable.. newpcm doesn't talk to this > > >(yet - no idea if there are any plans) > > > > newmidi is underway... > > > > That's why I wanted to kill voxware in 4.0, would allow pcm to be used > > from default... Now we're stuck to the voxware crap for another release > > cycle until 5.0 hits the public. > > Voxware may be "crap", but newpcm doesn't work right for my GUS PnP. (And > yep, I sent mail to the multimedia list, which got some response, and I > sent mail to Cameron, which got no response.) > > Voxware used to work fine, way back when. Luigi's pcm code worked fine as > well with my GUS PnP. Maybe it's time for me to switch back to voxware > from newpcm. I'm tired of getting static every once in a while when > playing sound files. > > I don't see any reason to get rid of voxware before newpcm is fully > functional. Unfortunately for those of us who used to use 'pnp' commands in userconfig to probe/init the AWE registers, the AWE wavetable is already useless in -current. AFAIK, the AWE cannot work without this, and the cards PnPinfo seems to not include the other two registers - and if you don't probe them, then the 'awe' driver check doesn't see the EMU8000... Is there even a single person out there able to use the AWE device under Voxware in -current? My understanding is that this is no longer possible, following the removal of the 'pnp' interface in userconfig.. So, people with the AWE32, AWE daughter card or the AWE64 might as well have an original SoundBlaster 16, for all the good the EMU8000 wavetable/synth chip does them. If that is really so, then I would suggest that either: a) the 'awe' driver is now just so much cruft and should be removed. or b) FreeBSD has lost significant functionality (namely, AWE wavetable support) with the removal of the older 'pnp' interface, and this should be put back. I guess that your perspective on this really depends on whether you actually have the hardware and want to use it... For me, with an integrated Vibra 16 on the mobo, Voxware is now unusable for sound as the SoundBlaster portion is not recognised. (Again, only in -current, it all works perfectly in -stable). I /have/ to use pcm in -current, simply to play CDs (which, incidentally, works well for me)... Of course, for the time being, I have the option of using this hardware under -stable, but eventually the changes will filter through to there as well. Of more importance (to me, right now), is that -stable is not getting the benefit of the other improvements that are going on in -current. (e.g. Linux threads, SMP, NFS etc.) Cheers, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 17: 0:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D25F37B81C; Tue, 22 Feb 2000 17:00:12 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id TAA26497; Tue, 22 Feb 2000 19:59:56 -0500 (EST) Date: Tue, 22 Feb 2000 19:59:55 -0500 (EST) From: Bosko Milekic To: =?iso-8859-1?Q?Jos=E9=20Lu=EDs?= Faria Cc: freebsd-config@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Kernel In-Reply-To: <38B127F0.48C04CB0@di.uminho.pt> 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 =09Try looking at the sysctl(3) interface. Issue `sysctl -A' and note one of the exported variable names. Then, search the code to see how it's setup. This is most probably what you're looking for. On Mon, 21 Feb 2000, [iso-8859-1] Jos=E9 Lu=EDs Faria wrote: >Hello=20 > >I'm creating a litle update to a freebsd 3.4 kernel. >My program is for account some data: number of >packets by class, number of packets dropped by class, etc. >Now I need to pass this values to another program wich in X-Window >display this values on-line. After, I want to save this values >in a file. > >I need some docs about how I can do this. >Which are the primitives in the kernel to do this. >I use the printf to put this data in /var/log/messages. >This inappropriate, I dont want this. This is only for testing now. > >Can you help me ? > >Thank you very much. > > >P.S. I'm sorry my english. > > >--=20 > > :) cumprimentos >-------------------------------- > Jose Luis Faria > Administrador de Sistemas > Universidade do Minho - Departamento de Inform=E1tica > Campus de Gualtar > 4710-057 Braga > Portugal > tel.: +351 253604440 Fax:+351 253604471 > http://admin.di.uminho.pt/~jose > <--------------------------------------------------------------------------= > Bosko Milekic * bmilekic@dsuper.net * http://pages.infinit.net/bmilekic/ <--------------------------------------------------------------------------= > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 17:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 3EBF637B858 for ; Tue, 22 Feb 2000 17:35:41 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id KAA36091; Wed, 23 Feb 2000 10:35:32 +0900 (JST) Date: Wed, 23 Feb 2000 10:35:31 +0900 Message-ID: <14515.14691.973264.61791G@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: andy@geek4food.org Cc: ken@kdm.org, asmodai@bart.nl, doconnor@gsoft.com.au, current@FreeBSD.ORG, lyndon@orthanc.ab.ca Subject: Re: status of 'device awe' ? In-Reply-To: In your message of "Tue, 22 Feb 2000 16:10:02 -0800" <20000222161002.A83593@mega.geek4food.org> References: <20000222132327.O5555@lucifer.bart.nl> <20000222233325.A14094@lucifer.bart.nl> <20000222154604.A22803@panzer.kdm.org> <20000222161002.A83593@mega.geek4food.org> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000 16:10:02 -0800, Andy Sparrow said: Andy> Unfortunately for those of us who used to use 'pnp' commands in Andy> userconfig to probe/init the AWE registers, the AWE wavetable is Andy> already useless in -current. Andy> AFAIK, the AWE cannot work without this, and the cards PnPinfo Andy> seems to not include the other two registers - and if you don't Andy> probe them, then the 'awe' driver check doesn't see the EMU8000... My newmidi patch includes a quirk to add the extra IO ports missing in the pnp information provided by EMU8000. That part of the patch is extracted into: http://people.FreeBSD.org/~tanimura/patches/awequirk.diff although not sure if the old-fashioned awe driver makes use of it... -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 18:54:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from filk.iinet.net.au (filk.iinet.net.au [203.59.24.235]) by hub.freebsd.org (Postfix) with ESMTP id F3BBA37B882; Tue, 22 Feb 2000 18:54:24 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-20-179.nv.iinet.net.au [203.59.85.179]) by filk.iinet.net.au (8.8.4/8.8.5) with SMTP id KAA28134; Wed, 23 Feb 2000 10:54:06 +0800 Message-ID: <38B34BBA.41C67EA6@elischer.org> Date: Tue, 22 Feb 2000 18:53:46 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Archie Cobbs Cc: Yevmenkin Maksim N CSCIO , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NETGRAPH patches (proposal) References: <200002222225.OAA42237@bubba.whistle.com> 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: > > Yevmenkin, Maksim N, CSCIO writes: > > > > Here is the description. ng_ether node has two hooks ``divert'' and > > > > ``orphan''. > > > > It is possible to connect to the one of the hooks and > > > intercept row Ethernet > > > > frames. But there is no clean way to intercept frame, do > > > something and > > > > return it back to kernel. > > > > > > > > This patch provides additional hook ``divertin'' (mmm... > > > name is not good, > > > > i think) for each ng_ether node. > > > > > > > > Implementation issues > > > > > > > > This will not work for ``orphan'' frames. Since kernel > > > drops it anyway, i > > > > decided to leave it as it is. But is is possible to > > > intercept ``orphan'' > > > > packets, change it, and write back to ``divertin''. > > > > > > The "divertin" hook is a useful idea.. after 4.0-REL we can check > > > something in based on your patches... > > > > > > > ok. i just have a dumb question. what is the big deal with updating > > ether_shost > > in ethernet header in ngether_rcvdata. since we are passing raw ethernet > > frame, > > why should we update ether_shost? wouldn't it be nice to make it optional? > > just another control message? > > I agree.. you should have to set the host address manually. > > -Archie It's because all packets sent by this node should have the node's address. If you don't have it then PPPoE cannot send a packet "FROM" thia node, as it has no idea of what this node's address is. > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 18:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 90D1B37B88C for ; Tue, 22 Feb 2000 18:56:38 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 2093 invoked by alias); 23 Feb 2000 02:56:31 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 2058 invoked by uid 0); 23 Feb 2000 02:56:29 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 02:56:29 -0000 Content-Length: 830 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222184830.C14314@shadow.blackdawn.com> Date: Tue, 22 Feb 2000 18:53:29 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Will Andrews Subject: Re: kdelibs port broken? Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, Maxim Sobolev , bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yea, after I compiled QT145, I couldent compile KDE. I am not sure of the exact error, it was a few days ago and I went back to 142, but It wouldent comile. On 22-Feb-00 Will Andrews wrote: > On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote: >> ON that subject, has anyone tried compiling the KDE port with the new QT145 >> port? > > In my original tests, Qt 1.45 works fine with the KDE ports. Do you have > any problems with it? > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 16:27:23l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 19: 4: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id D408837B830 for ; Tue, 22 Feb 2000 19:03:59 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 1FD759B17; Tue, 22 Feb 2000 22:03:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id E199FBA1D; Tue, 22 Feb 2000 22:03:55 -0500 (EST) Date: Tue, 22 Feb 2000 22:03:55 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: bwoods2@uswest.net Cc: Will Andrews , Daniel O'Connor , freebsd-current@FreeBSD.ORG, Maxim Sobolev Subject: Re: kdelibs port broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, William Woods wrote: > On 22-Feb-00 Will Andrews wrote: > > On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote: > >> ON that subject, has anyone tried compiling the KDE port with the new QT145 > >> port? > > > > In my original tests, Qt 1.45 works fine with the KDE ports. Do you have > > any problems with it? > Yea, after I compiled QT145, I couldent compile KDE. I am not sure of the exact > error, it was a few days ago and I went back to 142, but It wouldent comile. > Did you change the depends under USE_QT in bsd.port.mk to use qt.3 (provided by qt145) instead of qt.2 (provided by qt142)? I'm using qt145/kde under -CURRENT and -STABLE (under OLDGCC *and* NEWGCC) without problems. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:11: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from heidegger.uol.com.br (heidegger.uol.com.br [200.230.198.88]) by hub.freebsd.org (Postfix) with ESMTP id 28C4037B8FB for ; Tue, 22 Feb 2000 20:10:55 -0800 (PST) (envelope-from lioux-alias-ppp-freebsd-current=freebsd.org@uol.com.br) Received: from 200.197.112.65 (bsa-1-as01-7-a04.gd.uol.com.br [200.197.118.4]) by heidegger.uol.com.br (8.9.1/8.9.1) with ESMTP id CAA18467 for ; Wed, 23 Feb 2000 02:07:44 -0200 (BRST) Received: (qmail 74898 invoked by uid 1001); 23 Feb 2000 05:10:00 -0000 From: lioux@uol.com.br Date: Wed, 23 Feb 2000 02:10:00 -0300 To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org, lioux@linf.unb.br Subject: XFree 3.3.6 authentication failed? Message-ID: <20000223021000.A74659@Fedaykin.here> Reply-To: lioux@linf.unb.br Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear guys, I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and KDE 1.1.2. All from monday's ports tree. Well, I think I can't say I am running this system, for I am getting the following message whenever I try startx: Authentication failed - cannot start X server. Perhaps you do not have console ownership? _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. Damn, I know this must be my mistake. However, I can't seem to get X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup works smooth. Before you mention it: yeah, yeah, I tried startx as root against my best judgement; and no, it did not work. :) UCONSOLE is enabled. My .xinitrc follows at the end of this file. What am I missing? A new authentication system? My guess. I went through the FAQ and most of the simple docs; I must be overlooking something. Any and all help appreciated. Please CC: to lioux@linf.unb.br, for I am subscribed to neither freebsd-questions nor freebsd-current. I apologize in advance for the CC: accross mailing lists. Regards, Mario Ferreira ps: Please, don't flame me. /dev/null appreciates it. Thanks again. -- #!/bin/sh # $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $ userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11R6/lib/X11/xinit/.Xresources sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap # merge in defaults and keymaps if [ -f $sysresources ]; then xrdb -merge $sysresources fi if [ -f $sysmodmap ]; then xmodmap $sysmodmap fi if [ -f $userresources ]; then xrdb -merge $userresources fi if [ -f $usermodmap ]; then xmodmap $usermodmap fi # start some nice programs kde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:20:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 96A6437B5E0; Tue, 22 Feb 2000 20:20:21 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.196.34]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id UAA12517; Tue, 22 Feb 2000 20:19:26 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 3FE981954; Tue, 22 Feb 2000 23:18:26 -0500 (EST) Date: Tue, 22 Feb 2000 23:18:26 -0500 From: Will Andrews To: lioux@linf.unb.br Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: XFree 3.3.6 authentication failed? Message-ID: <20000222231826.J14314@shadow.blackdawn.com> References: <20000223021000.A74659@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223021000.A74659@Fedaykin.here>; from lioux@uol.com.br on Wed, Feb 23, 2000 at 02:10:00AM -0300 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:10:00AM -0300, lioux@uol.com.br wrote: > Dear guys, > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. > > Damn, I know this must be my mistake. However, I can't seem to get > X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup > works smooth. Before you mention it: yeah, yeah, I tried startx as root > against my best judgement; and no, it did not work. :) > UCONSOLE is enabled. > My .xinitrc follows at the end of this file. > What am I missing? A new authentication system? My guess. I went > through the FAQ and most of the simple docs; I must be overlooking something. > Any and all help appreciated. Please CC: to lioux@linf.unb.br, for I > am subscribed to neither freebsd-questions nor freebsd-current. > I apologize in advance for the CC: accross mailing lists. > > Regards, > Mario Ferreira > > ps: Please, don't flame me. /dev/null appreciates it. Thanks again. 1) Do you have "XSERVER" option in kernel? I'm not sure if it's required, but it might be. 2) You should start KDE with "startkde" not "kde". -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:24:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 467A837B8A3; Tue, 22 Feb 2000 20:24:23 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id XAA10068; Tue, 22 Feb 2000 23:29:25 -0500 (EST) (envelope-from cjc) Date: Tue, 22 Feb 2000 23:29:25 -0500 From: "Crist J. Clark" To: lioux@linf.unb.br Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: XFree 3.3.6 authentication failed? Message-ID: <20000222232925.C9788@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: <20000223021000.A74659@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223021000.A74659@Fedaykin.here>; from lioux@uol.com.br on Wed, Feb 23, 2000 at 02:10:00AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:10:00AM -0300, lioux@uol.com.br wrote: > Dear guys, > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? [snip] You built X with PAM enabled. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:48:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 1F84937B5E0 for ; Tue, 22 Feb 2000 20:48:31 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 16552 invoked by alias); 23 Feb 2000 04:48:28 -0000 Delivered-To: fixup-freebsd-current@freebsd.org@fixme Received: (qmail 16542 invoked by uid 0); 23 Feb 2000 04:48:28 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 04:48:28 -0000 Content-Length: 830 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 22 Feb 2000 20:45:28 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-current@freebsd.org Subject: Upgrade from 3.4 to 4.0... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I have been following the disscussions here for a while, just trying to get a feel of what the transition from 3.4-stable 4.0-release will be like. I am running -current on my alpha, but that was a fresh install. I am debating trying -current on my laptop, but before we go there, I would like to inquire as to what shape the transition is in. Are there steps posted somewhere that work? Also, what condition (I know, I am asking you to read the future) do you expect the transition to be like at the end of the month when 4.0 -release comes out. Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, where would I find the nessary instructions? ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 20:40:26l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:54:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 11A8F37B8C3; Tue, 22 Feb 2000 20:54:10 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id XAA83424; Tue, 22 Feb 2000 23:54:00 -0500 Date: Tue, 22 Feb 2000 23:54:00 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Will Andrews Cc: lioux@linf.unb.br, freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: XFree 3.3.6 authentication failed? In-Reply-To: <20000222231826.J14314@shadow.blackdawn.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 Actually I think this is a pam.conf issue. You probably built 3.3.6 with PAM support? This happened to me as soon as 3.3.6 came out. try copying pam.conf from whereveryoubuildworld/etc to /etc and see if that fixes it. I think mergemaster would take care of this too, I dunno last time I used it it did more harm than good. -Will On Tue, 22 Feb 2000, Will Andrews wrote: > On Wed, Feb 23, 2000 at 02:10:00AM -0300, lioux@uol.com.br wrote: > > Dear guys, > > > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > > KDE 1.1.2. All from monday's ports tree. > > Well, I think I can't say I am running this system, for I am getting > > the following message whenever I try startx: > > > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > giving up. > > xinit: No such file or directory (errno 2): unable to connect to X server > > xinit: No such process (errno 3): Server error. > > > > Damn, I know this must be my mistake. However, I can't seem to get > > X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup > > works smooth. Before you mention it: yeah, yeah, I tried startx as root > > against my best judgement; and no, it did not work. :) > > UCONSOLE is enabled. > > My .xinitrc follows at the end of this file. > > What am I missing? A new authentication system? My guess. I went > > through the FAQ and most of the simple docs; I must be overlooking something. > > Any and all help appreciated. Please CC: to lioux@linf.unb.br, for I > > am subscribed to neither freebsd-questions nor freebsd-current. > > I apologize in advance for the CC: accross mailing lists. > > > > Regards, > > Mario Ferreira > > > > ps: Please, don't flame me. /dev/null appreciates it. Thanks again. > > 1) Do you have "XSERVER" option in kernel? I'm not sure if it's > required, but it might be. > > 2) You should start KDE with "startkde" not "kde". > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? > > > 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 Feb 22 20:54:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 885B737B836 for ; Tue, 22 Feb 2000 20:54:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id VAA03383; Tue, 22 Feb 2000 21:23:08 -0800 (PST) Date: Tue, 22 Feb 2000 21:23:08 -0800 From: Alfred Perlstein To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000222212308.O21720@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 08:45:28PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * William Woods [000222 21:19] wrote: > Hey, > > I have been following the disscussions here for a while, just trying to get a > feel of what the transition from 3.4-stable 4.0-release will be like. I am > running -current on my alpha, but that was a fresh install. I am debating > trying -current on my laptop, but before we go there, I would like to inquire > as to what shape the transition is in. Are there steps posted somewhere that > work? > > Also, what condition (I know, I am asking you to read the future) do you expect > the transition to be like at the end of the month when 4.0 -release comes out. > > Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, where > would I find the nessary instructions? Please see src/UPDATING thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:57:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 447A537B594 for ; Tue, 22 Feb 2000 20:57:18 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 22235 invoked by alias); 23 Feb 2000 04:57:14 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 22218 invoked by uid 0); 23 Feb 2000 04:57:14 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 04:57:14 -0000 Content-Length: 1195 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222212308.O21720@fw.wintelcom.net> Date: Tue, 22 Feb 2000 20:54:14 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Alfred Perlstein Subject: Re: Upgrade from 3.4 to 4.0... Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did read that document, and honestly, it dident make a lot of sence and it seemed to have some conflicting instructions.....which is why I am asking here. On 23-Feb-00 Alfred Perlstein wrote: > * William Woods [000222 21:19] wrote: >> Hey, >> >> I have been following the disscussions here for a while, just trying to get >> a >> feel of what the transition from 3.4-stable 4.0-release will be like. I am >> running -current on my alpha, but that was a fresh install. I am debating >> trying -current on my laptop, but before we go there, I would like to >> inquire >> as to what shape the transition is in. Are there steps posted somewhere that >> work? >> >> Also, what condition (I know, I am asking you to read the future) do you >> expect >> the transition to be like at the end of the month when 4.0 -release comes >> out. >> >> Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, >> where >> would I find the nessary instructions? > > Please see src/UPDATING > > thanks, > -Alfred ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 20:53:10l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 20:58:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 1D21F37B87E for ; Tue, 22 Feb 2000 20:58:13 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.196.34]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id UAA13014; Tue, 22 Feb 2000 20:57:39 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id DE5761954; Tue, 22 Feb 2000 23:57:20 -0500 (EST) Date: Tue, 22 Feb 2000 23:57:20 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000222235720.K14314@shadow.blackdawn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 08:45:28PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 08:45:28PM -0800, William Woods wrote: > I have been following the disscussions here for a while, just trying to get a > feel of what the transition from 3.4-stable 4.0-release will be like. I am > running -current on my alpha, but that was a fresh install. I am debating > trying -current on my laptop, but before we go there, I would like to inquire > as to what shape the transition is in. Are there steps posted somewhere that > work? See src/UPDATING. I made the transition on my laptop from 3.3-RELEASE to 4.0-CURRENT about six months ago, so my experience wouldn't help you much, unfortunately. However, I would just like to say that I'm very happy with my 4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-) > Also, what condition (I know, I am asking you to read the future) do you expect > the transition to be like at the end of the month when 4.0 -release comes out. Should be fairly easy, if you do it the cvsup/make world way.. there's a lot of different thorns here and there so I'm not real sure what it would be like once 4.0-RELEASE goes out. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 0:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 65A9237B90A for ; Tue, 22 Feb 2000 21:00:40 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 24515 invoked by alias); 23 Feb 2000 05:00:35 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 24494 invoked by uid 0); 23 Feb 2000 05:00:34 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 05:00:34 -0000 Content-Length: 598 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222235720.K14314@shadow.blackdawn.com> Date: Tue, 22 Feb 2000 20:57:35 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Will Andrews Subject: Re: Upgrade from 3.4 to 4.0... Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-00 Will Andrews wrote: > See src/UPDATING. I read that...I must say it is a bit confusing and in some places contradictory > I made the transition on my laptop from 3.3-RELEASE to 4.0-CURRENT about > six months ago, so my experience wouldn't help you much, unfortunately. > > However, I would just like to say that I'm very happy with my > 4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-) I have that same card.... ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 20:55:56l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 1:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 28D0737B8B6; Tue, 22 Feb 2000 21:01:19 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id AAA85299; Wed, 23 Feb 2000 00:01:16 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id AAA01580; Wed, 23 Feb 2000 00:01:15 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: msmith@FreeBSD.ORG (Mike Smith) Cc: current@FreeBSD.ORG Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Date: Wed, 23 Feb 2000 04:59:17 GMT Message-ID: <38b368b7.105281807@mail.sentex.net> References: <3.0.5.32.20000217103709.01c2f7b0@marble.sentex.ca> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Feb 2000 17:39:19 -0500, in sentex.lists.freebsd.current you wrote: > >Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware >up within a few minutes. The Dell 3.00 firmware remains stable under the >same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a >firmware lockup - the SCSI bus is hung and usually the PCI bus as well. I am going to test the card in another older MB to see if its some strange interaction. What MB chipset are you using to test with ? ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 3:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 0DC8C37B8DE; Tue, 22 Feb 2000 21:03:20 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id VAA84742; Tue, 22 Feb 2000 21:02:44 -0800 (PST) From: Archie Cobbs Message-Id: <200002230502.VAA84742@bubba.whistle.com> Subject: Re: NETGRAPH patches (proposal) In-Reply-To: <38B34BBA.41C67EA6@elischer.org> from Julian Elischer at "Feb 22, 2000 06:53:46 pm" To: julian@elischer.org (Julian Elischer) Date: Tue, 22 Feb 2000 21:02:43 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), myevmenkin@att.com (Yevmenkin Maksim N CSCIO), freebsd-current@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > > ok. i just have a dumb question. what is the big deal with updating > > > ether_shost > > > in ethernet header in ngether_rcvdata. since we are passing raw ethernet > > > frame, > > > why should we update ether_shost? wouldn't it be nice to make it optional? > > > just another control message? > > > > I agree.. you should have to set the host address manually. > > It's because all packets sent by this node should have the node's > address. If you don't have it then PPPoE cannot send a packet "FROM" > thia node, as it has no idea of what this node's address is. So.. we can have two hooks, one that sets the host address and one that doesn't.. :-) -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 Feb 22 21: 3:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 5DDA437B8DE for ; Tue, 22 Feb 2000 21:03:35 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.196.34]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id VAA13090; Tue, 22 Feb 2000 21:02:51 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id D33551954; Wed, 23 Feb 2000 00:02:33 -0500 (EST) Date: Wed, 23 Feb 2000 00:02:33 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000223000233.M14314@shadow.blackdawn.com> References: <20000222212308.O21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 08:54:14PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 08:54:14PM -0800, William Woods wrote: > I did read that document, and honestly, it dident make a lot of sence and it > seemed to have some conflicting instructions.....which is why I am asking here. Specifics, specifics... and are you sure you're looking at an _UP_TO_DATE_ copy of src/UPDATING ? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 6:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 48BB537B8B7 for ; Tue, 22 Feb 2000 21:06:08 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 28572 invoked by alias); 23 Feb 2000 05:06:05 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 28552 invoked by uid 0); 23 Feb 2000 05:06:04 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 05:06:04 -0000 Content-Length: 785 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000223000233.M14314@shadow.blackdawn.com> Date: Tue, 22 Feb 2000 21:03:04 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Will Andrews Subject: Re: Upgrade from 3.4 to 4.0... Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein , bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsupped a few hours ago...... On 23-Feb-00 Will Andrews wrote: > On Tue, Feb 22, 2000 at 08:54:14PM -0800, William Woods wrote: >> I did read that document, and honestly, it dident make a lot of sence and it >> seemed to have some conflicting instructions.....which is why I am asking >> here. > > Specifics, specifics... and are you sure you're looking at an > _UP_TO_DATE_ copy of src/UPDATING ? > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 21:02:44l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 7: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles517.castles.com [208.214.165.81]) by hub.freebsd.org (Postfix) with ESMTP id 23D5B37B8FC for ; Tue, 22 Feb 2000 21:07:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00682; Tue, 22 Feb 2000 21:19:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002230519.VAA00682@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mike@sentex.net (Mike Tancsa) Cc: current@FreeBSD.ORG Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) In-reply-to: Your message of "Wed, 23 Feb 2000 04:59:17 GMT." <38b368b7.105281807@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 21:19:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 18 Feb 2000 17:39:19 -0500, in sentex.lists.freebsd.current you wrote: > > > >Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware > >up within a few minutes. The Dell 3.00 firmware remains stable under the > >same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a > >firmware lockup - the SCSI bus is hung and usually the PCI bus as well. > > I am going to test the card in another older MB to see if its some strange > interaction. What MB chipset are you using to test with ? I've been testing most recently with the Intel 450NX and AMD 751. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 8:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8F69237B8B6 for ; Tue, 22 Feb 2000 21:08:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id VAA03788; Tue, 22 Feb 2000 21:35:57 -0800 (PST) Date: Tue, 22 Feb 2000 21:35:57 -0800 From: Alfred Perlstein To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000222213557.P21720@fw.wintelcom.net> References: <20000222212308.O21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 08:54:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * William Woods [000222 21:27] wrote: > I did read that document, and honestly, it dident make a lot of sence and it > seemed to have some conflicting instructions.....which is why I am asking here. It looks pretty concise to me, perhaps you can explain the confusion so that we may fix it so as to help other users? -Alfred > > On 23-Feb-00 Alfred Perlstein wrote: > > * William Woods [000222 21:19] wrote: > >> Hey, > >> > >> I have been following the disscussions here for a while, just trying to get > >> a > >> feel of what the transition from 3.4-stable 4.0-release will be like. I am > >> running -current on my alpha, but that was a fresh install. I am debating > >> trying -current on my laptop, but before we go there, I would like to > >> inquire > >> as to what shape the transition is in. Are there steps posted somewhere that > >> work? > >> > >> Also, what condition (I know, I am asking you to read the future) do you > >> expect > >> the transition to be like at the end of the month when 4.0 -release comes > >> out. > >> > >> Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, > >> where > >> would I find the nessary instructions? > > > > Please see src/UPDATING To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21: 8:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 79F6E37B8B2 for ; Tue, 22 Feb 2000 21:08:33 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.196.34]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id VAA13154; Tue, 22 Feb 2000 21:08:21 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 7B0DB1954; Wed, 23 Feb 2000 00:08:01 -0500 (EST) Date: Wed, 23 Feb 2000 00:08:01 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: Will Andrews , freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000223000801.N14314@shadow.blackdawn.com> References: <20000222235720.K14314@shadow.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 08:57:35PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 08:57:35PM -0800, William Woods wrote: > > 4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-) > > I have that same card.... Works great on 4.0-CURRENT, which I'm sure you'll be glad to know. If you have any trouble getting it to work, just drop me a line and I'll help you debug it. :-) I've been able to get 1.2MB/sec on half-duplex 100BaseTX. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21:12: 4 2000 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 0EAC937BA6E for ; Tue, 22 Feb 2000 21:11:56 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA00651; Tue, 22 Feb 2000 22:11:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA33033; Tue, 22 Feb 2000 22:11:44 -0700 (MST) Message-Id: <200002230511.WAA33033@harmony.village.org> To: bwoods2@uswest.net Subject: Re: Upgrade from 3.4 to 4.0... Cc: Will Andrews , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Feb 2000 20:57:35 PST." References: Date: Tue, 22 Feb 2000 22:11:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : I read that...I must say it is a bit confusing and in some places contradictory I'm not surprising that it is confusing. It is hard to hit a moving target like current. And things have often are contradictory... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21:12:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 1DCC937BA6E for ; Tue, 22 Feb 2000 21:12:22 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 2593 invoked by alias); 23 Feb 2000 05:12:17 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 2573 invoked by uid 0); 23 Feb 2000 05:12:17 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 05:12:17 -0000 Content-Length: 2071 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000222213557.P21720@fw.wintelcom.net> Date: Tue, 22 Feb 2000 21:09:17 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Alfred Perlstein Subject: Re: Upgrade from 3.4 to 4.0... Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I guess what confused me is the order.... I would assume that the last entry, being the newest, would have all the steps listed that are currently needed. Maby its just me and, I am really not tyring to cause a hassle, maby I am reading it wrong. It seems to me that you need to piece together what you need be applying past steps and seeing what has changed. I guess what I am looking for is a : 1) xxxxxx 2) xxxxxx 3) xxxxxx type of thing. Again, thats what confused me. Maby others can see it fine, but it lost me. Thanks On 23-Feb-00 Alfred Perlstein wrote: > * William Woods [000222 21:27] wrote: >> I did read that document, and honestly, it dident make a lot of sence and it >> seemed to have some conflicting instructions.....which is why I am asking >> here. > > It looks pretty concise to me, perhaps you can explain the confusion > so that we may fix it so as to help other users? > > -Alfred > >> >> On 23-Feb-00 Alfred Perlstein wrote: >> > * William Woods [000222 21:19] wrote: >> >> Hey, >> >> >> >> I have been following the disscussions here for a while, just trying to >> >> get >> >> a >> >> feel of what the transition from 3.4-stable 4.0-release will be like. I >> >> am >> >> running -current on my alpha, but that was a fresh install. I am debating >> >> trying -current on my laptop, but before we go there, I would like to >> >> inquire >> >> as to what shape the transition is in. Are there steps posted somewhere >> >> that >> >> work? >> >> >> >> Also, what condition (I know, I am asking you to read the future) do you >> >> expect >> >> the transition to be like at the end of the month when 4.0 -release comes >> >> out. >> >> >> >> Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, >> >> where >> >> would I find the nessary instructions? >> > >> > Please see src/UPDATING ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 21:05:59l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21:16:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 29A6537B89C for ; Tue, 22 Feb 2000 21:16:25 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.196.34]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id VAA13225; Tue, 22 Feb 2000 21:15:59 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 31F6C1B57; Wed, 23 Feb 2000 00:15:49 -0500 (EST) Date: Wed, 23 Feb 2000 00:15:49 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: Will Andrews , freebsd-current@FreeBSD.ORG, Alfred Perlstein Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000223001549.P14314@shadow.blackdawn.com> References: <20000223000233.M14314@shadow.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Tue, Feb 22, 2000 at 09:03:04PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 09:03:04PM -0800, William Woods wrote: > cvsupped a few hours ago...... > > Specifics, specifics... and are you sure you're looking at an Specifics please. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 21:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 4BBB737B948; Tue, 22 Feb 2000 21:27:32 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id LAA41089; Wed, 23 Feb 2000 11:16:05 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 23 Feb 2000 11:16:04 +0600 (NS) From: Max Khon To: lioux@linf.unb.br Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: XFree 3.3.6 authentication failed? In-Reply-To: <20000223021000.A74659@Fedaykin.here> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 23 Feb 2000 lioux@uol.com.br wrote: > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. seems that you have built XFree with PAM support. Just rebuild without PAM -- it's broken. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 22:17:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id CAEB737B771 for ; Tue, 22 Feb 2000 22:17:24 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip209.r4.d.bel.nwlink.com (ip209.r4.d.bel.nwlink.com [207.202.172.209]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id WAA07227; Tue, 22 Feb 2000 22:17:21 -0800 (PST) Date: Tue, 22 Feb 2000 22:12:20 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Alfred Perlstein Cc: bwoods2@uswest.net, freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... In-Reply-To: <20000222213557.P21720@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, Alfred Perlstein wrote: > * William Woods [000222 21:27] wrote: > > I did read that document, and honestly, it dident make a lot of sence and it > > seemed to have some conflicting instructions.....which is why I am asking here. > > It looks pretty concise to me, perhaps you can explain the confusion > so that we may fix it so as to help other users? It seems like it contains good information for those who have been on the track for awhile, while being a bit cryptic for people new to the process. Since this is a development version, I suppose that's to be expected. I followed the instructions that someone else posted on -questions: make buildworld make buildkernel &&make installkernel Then reboot in single user mode make -DNOINFO installworld make buildkernel &&make installkernel (again) make installworld This worked for me perfectly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 22:22:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 9D03637B850 for ; Tue, 22 Feb 2000 22:22:18 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 16992 invoked by alias); 23 Feb 2000 06:22:13 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 16967 invoked by uid 0); 23 Feb 2000 06:22:12 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 06:22:12 -0000 Content-Length: 516 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 22 Feb 2000 22:19:13 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: R Joseph Wright Subject: Re: Upgrade from 3.4 to 4.0... Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net, Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-00 R Joseph Wright wrote: > > make buildworld > make buildkernel &&make installkernel > Then reboot in single user mode > make -DNOINFO installworld > make buildkernel &&make installkernel (again) > make installworld > > This worked for me perfectly. Hmmm.....the only question I have regarding this is does it handle the new devices corectly? ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 22:18:06l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 22:34:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from stargate.iss.com.tw (stargate.iss.com.tw [210.68.99.1]) by hub.freebsd.org (Postfix) with ESMTP id BC4DF37B7B3 for ; Tue, 22 Feb 2000 22:34:28 -0800 (PST) (envelope-from urania@iss.com.tw) Received: from stargate.iss.com.tw (root@localhost) by stargate.iss.com.tw with ESMTP id OAA19347 for ; Wed, 23 Feb 2000 14:40:50 +0800 (CST) Received: from iss.com.tw (mail.iss.com.tw [172.16.6.97]) by stargate.iss.com.tw with SMTP id OAA19343 for ; Wed, 23 Feb 2000 14:40:49 +0800 (CST) Received: (qmail 16267 invoked by uid 1001); 23 Feb 2000 06:27:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Feb 2000 06:27:31 -0000 Date: Wed, 23 Feb 2000 14:27:31 +0800 (CST) From: User URANIA To: freebsd-current@freebsd.org Subject: Problem with IBM Netfinity 5000 Server Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've a Netfinity 5000 Server, internal 5 PCI slot onborad. If i put one Intel 82558 NIC at 5th PCI Slot, everythings goes fine. Every times i put the same Intel NIC to any other PCI slots ( 1th ~ 4th ), after system login prompt , i also login as root, then system direct reboot .... ><# Here is boot -v message as I put The NIC at 4th PCI Slot: Feb 23 14:02:59 www /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Feb 23 14:02:59 www /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 23 14:02:59 www /kernel: The Regents of the University of California. All rights reserved. Feb 23 14:02:59 www /kernel: FreeBSD 4.0-CURRENT #0: Wed Feb 23 13:56:44 CST 2000 Feb 23 14:02:59 www /kernel: root@www.securenet.com.tw:/usr/src/sys/compile/www Feb 23 14:02:59 www /kernel: Calibrating clock(s) ... TSC clock: 498595828 Hz, i8254 clock: 1193010 Hz Feb 23 14:02:59 www /kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Feb 23 14:02:59 www /kernel: Timecounter "i8254" frequency 1193182 Hz Feb 23 14:02:59 www /kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Feb 23 14:02:59 www /kernel: Timecounter "TSC" frequency 498670821 Hz Feb 23 14:02:59 www /kernel: CPU: Pentium III/Pentium III Xeon (498.67-MHz 686-class CPU) Feb 23 14:02:59 www /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Feb 23 14:02:59 www /kernel: Features=0x383fbff Feb 23 14:02:59 www /kernel: real memory = 536854528 (524272K bytes) Feb 23 14:02:59 www /kernel: Physical memory chunk(s): Feb 23 14:02:59 www /kernel: 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) Feb 23 14:02:59 www /kernel: 0x0031c000 - 0x1fff3fff, 533561344 bytes (130264 pages) Feb 23 14:02:59 www /kernel: avail memory = 517894144 (505756K bytes) Feb 23 14:02:59 www /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd5d0 Feb 23 14:02:59 www /kernel: bios32: Entry = 0xfd5e1 (c00fd5e1) Rev = 0 Len = 1 Feb 23 14:02:59 www /kernel: pcibios: PCI BIOS entry at 0xd61c Feb 23 14:02:59 www /kernel: pnpbios: Found PnP BIOS data at 0xc00fde90 Feb 23 14:02:59 www /kernel: pnpbios: Entry = f0000:497d Rev = 1.0 Feb 23 14:02:59 www /kernel: Other BIOS signatures found: Feb 23 14:02:59 www /kernel: ACPI: 000fdec0 Feb 23 14:02:59 www /kernel: Preloaded elf kernel "kernel" at 0xc0303000. Feb 23 14:02:59 www /kernel: Pentium Pro MTRR support enabled Feb 23 14:02:59 www /kernel: Math emulator present Feb 23 14:02:59 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000070 Feb 23 14:02:59 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:02:59 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:02:59 www /kernel: npx0: on motherboard Feb 23 14:02:59 www /kernel: npx0: INT 16 interface Feb 23 14:02:59 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 Feb 23 14:02:59 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:02:59 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:02:59 www /kernel: pcib0: on motherboard Feb 23 14:02:59 www /kernel: found-> vendor=0x1166, dev=0x0007, revid=0x04 Feb 23 14:02:59 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:02:59 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:02:59 www /kernel: map[10]: type 1, range 32, base 00000000, size 0 Feb 23 14:02:59 www /kernel: found-> vendor=0x1166, dev=0x0005, revid=0x02 Feb 23 14:02:59 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:02:59 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:02:59 www /kernel: found-> vendor=0x9004, dev=0x7895, revid=0x04 Feb 23 14:02:59 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:02:59 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:02:59 www /kernel: intpin=a, irq=11 Feb 23 14:02:59 www /kernel: map[10]: type 1, range 32, base 00002000, size 8 Feb 23 14:02:59 www /kernel: map[14]: type 1, range 32, base febff000, size 12 Feb 23 14:02:59 www /kernel: found-> vendor=0x9004, dev=0x7895, revid=0x04 Feb 23 14:02:59 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:02:59 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=b, irq=15 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base 00002200, size 8 Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base febfe000, size 12 Feb 23 14:03:00 www /kernel: found-> vendor=0x1022, dev=0x2000, revid=0x36 Feb 23 14:03:00 www /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=a, irq=10 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base 00002180, size 5 Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base febfdc00, size 5 Feb 23 14:03:00 www /kernel: found-> vendor=0x5333, dev=0x8901, revid=0x16 Feb 23 14:03:00 www /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=a, irq=9 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base f8000000, size 26 Feb 23 14:03:00 www /kernel: found-> vendor=0x1166, dev=0x0200, revid=0x4d Feb 23 14:03:00 www /kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: found-> vendor=0x1166, dev=0x0210, revid=0x4a Feb 23 14:03:00 www /kernel: class=01-01-ea, hdrtype=0x00, mfdev=1 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=a, irq=14 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base 000001f0, size 3 Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base 000003f4, size 2 Feb 23 14:03:00 www /kernel: map[18]: type 1, range 32, base 00000010, size 3 Feb 23 14:03:00 www /kernel: map[1c]: type 1, range 32, base 00000000, size 2 Feb 23 14:03:00 www /kernel: map[20]: type 1, range 32, base 0000ffa0, size 4 Feb 23 14:03:00 www /kernel: found-> vendor=0x1166, dev=0x0220, revid=0x04 Feb 23 14:03:00 www /kernel: class=0c-03-10, hdrtype=0x00, mfdev=0 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=a, irq=10 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base ff700000, size 12 Feb 23 14:03:00 www /kernel: pci0: on pcib0 Feb 23 14:03:00 www /kernel: ahc0: port 0x2000-0x20ff mem 0xfebff000-0xfebfffff irq 11 at device 6.0 on pci0 Feb 23 14:03:00 www /kernel: ahc0: Reading SEEPROM...done. Feb 23 14:03:00 www /kernel: ahc0: Low byte termination Enabled Feb 23 14:03:00 www /kernel: ahc0: High byte termination Enabled Feb 23 14:03:00 www /kernel: ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs Feb 23 14:03:00 www /kernel: ahc0: Downloading Sequencer Program... 389 instructions downloaded Feb 23 14:03:00 www /kernel: ahc1: port 0x2200-0x22ff mem 0xfebfe000-0xfebfefff irq 15 at device 6.1 on pci0 Feb 23 14:03:00 www /kernel: ahc1: Reading SEEPROM...done. Feb 23 14:03:00 www /kernel: ahc1: Low byte termination Enabled Feb 23 14:03:00 www /kernel: ahc1: High byte termination Enabled Feb 23 14:03:00 www /kernel: ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Feb 23 14:03:00 www /kernel: ahc1: Downloading Sequencer Program... 389 instructions downloaded Feb 23 14:03:00 www /kernel: lnc0: port 0x2180-0x219f mem 0xfebfdc00-0xfebfdc1f irq 10 at device 9.0 on pci0 Feb 23 14:03:00 www /kernel: lnc0: PCnet-FAST+ address 00:06:29:39:16:e0 Feb 23 14:03:00 www /kernel: bpf: lnc0 attached Feb 23 14:03:00 www /kernel: lnc0: driver is using old-style compatability shims Feb 23 14:03:00 www /kernel: pci0: (vendor=0x5333, dev=0x8901) at 10.0 irq 9 Feb 23 14:03:00 www /kernel: isab0: at device 15.0 on pci0 Feb 23 14:03:00 www /kernel: isa0: on isab0 Feb 23 14:03:00 www /kernel: atapci0: port 0xffa0-0xffaf,0-0x3,0x10-0x17,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at device 15.1 on pci0 Feb 23 14:03:00 www /kernel: ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 Feb 23 14:03:00 www /kernel: ata0: mask=03 status0=50 status1=00 Feb 23 14:03:00 www /kernel: ata0: mask=03 status0=00 status1=00 Feb 23 14:03:00 www /kernel: ata0: devices = 0x4 Feb 23 14:03:00 www /kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 23 14:03:00 www /kernel: ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 Feb 23 14:03:00 www /kernel: ata1: mask=00 status0=ff status1=ff Feb 23 14:03:00 www /kernel: ata1: probe allocation failed Feb 23 14:03:00 www /kernel: pci0: (vendor=0x1166, dev=0x0220) at 15.2 irq 10 Feb 23 14:03:00 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 Feb 23 14:03:00 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:03:00 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:03:00 www /kernel: pcib1: on motherboard Feb 23 14:03:00 www /kernel: found-> vendor=0x8086, dev=0x1229, revid=0x05 Feb 23 14:03:00 www /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:03:00 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:03:00 www /kernel: intpin=a, irq=11 Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base c0fdf000, size 12 Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base 00004b00, size 5 Feb 23 14:03:01 www /kernel: map[18]: type 1, range 32, base c0e00000, size 20 Feb 23 14:03:01 www /kernel: pci1: on pcib1 Feb 23 14:03:01 www /kernel: fxp0: port 0x4b00-0x4b1f mem 0xc0e00000-0xc0efffff,0xc0fdf000-0xc0fdffff irq 11 at device 2.0 on pci1 Feb 23 14:03:01 www /kernel: using shared irq11. Feb 23 14:03:01 www /kernel: fxp0: Ethernet address 00:04:ac:45:75:fc Feb 23 14:03:01 www /kernel: bpf: fxp0 attached Feb 23 14:03:01 www /kernel: Trying Read_Port at 203 Feb 23 14:03:01 www /kernel: Trying Read_Port at 243 Feb 23 14:03:01 www /kernel: Trying Read_Port at 283 Feb 23 14:03:01 www /kernel: Trying Read_Port at 2c3 Feb 23 14:03:01 www /kernel: Trying Read_Port at 303 Feb 23 14:03:01 www /kernel: Trying Read_Port at 343 Feb 23 14:03:01 www /kernel: Trying Read_Port at 383 Feb 23 14:03:01 www /kernel: Trying Read_Port at 3c3 Feb 23 14:03:01 www /kernel: devclass_alloc_unit: lnc0 already exists, using next available unit number Feb 23 14:03:01 www /kernel: isa_probe_children: disabling PnP devices Feb 23 14:03:01 www /kernel: isa_probe_children: probing non-PnP devices Feb 23 14:03:01 www /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Feb 23 14:03:01 www /kernel: fdc0: FIFO enabled, 8 bytes threshold Feb 23 14:03:01 www /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Feb 23 14:03:01 www /kernel: atkbdc0: at port 0x60-0x6f on isa0 Feb 23 14:03:01 www /kernel: atkbd0: irq 1 on atkbdc0 Feb 23 14:03:01 www /kernel: atkbd: the current kbd controller command byte 0045 Feb 23 14:03:01 www /kernel: atkbd: keyboard ID 0x41ab (2) Feb 23 14:03:01 www /kernel: kbdc: RESET_KBD return code:00fa Feb 23 14:03:01 www /kernel: kbdc: RESET_KBD status:00aa Feb 23 14:03:01 www /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Feb 23 14:03:01 www /kernel: psm0: current command byte:0045 Feb 23 14:03:01 www /kernel: kbdc: TEST_AUX_PORT status:0000 Feb 23 14:03:01 www /kernel: kbdc: RESET_AUX return code:00fa Feb 23 14:03:01 www /kernel: kbdc: RESET_AUX status:00aa Feb 23 14:03:01 www /kernel: kbdc: RESET_AUX ID:0000 Feb 23 14:03:01 www /kernel: psm: status 00 02 64 Feb 23 14:03:01 www /kernel: psm: status 00 00 64 Feb 23 14:03:01 www /kernel: psm: status 00 03 64 Feb 23 14:03:01 www /kernel: psm: status 00 03 64 Feb 23 14:03:01 www /kernel: psm: status 00 00 64 Feb 23 14:03:01 www /kernel: psm: data ffffffff 00 64 Feb 23 14:03:01 www /kernel: psm: status 00 02 64 Feb 23 14:03:01 www /kernel: psm: data ffffffff 02 64 Feb 23 14:03:01 www /kernel: psm0: failed to get data. Feb 23 14:03:01 www /kernel: psm: status 00 02 64 Feb 23 14:03:01 www /kernel: psm0: irq 12 on atkbdc0 Feb 23 14:03:01 www /kernel: psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons Feb 23 14:03:01 www /kernel: psm0: config:00000000, flags:00000000, packet size:3 Feb 23 14:03:01 www /kernel: psm0: syncmask:00, syncbits:00 Feb 23 14:03:01 www /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Feb 23 14:03:01 www /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Feb 23 14:03:01 www /kernel: fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 Feb 23 14:03:01 www /kernel: fb0: init mode:24, bios mode:3, current mode:24 Feb 23 14:03:01 www /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k Feb 23 14:03:01 www /kernel: VGA parameters upon power-up Feb 23 14:03:01 www /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:03:01 www /kernel: bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 Feb 23 14:03:01 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:03:01 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:03:01 www /kernel: VGA parameters in BIOS for mode 24 Feb 23 14:03:01 www /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:03:01 www /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Feb 23 14:03:01 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:03:02 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:03:02 www /kernel: EGA/VGA parameters to be used for mode 24 Feb 23 14:03:02 www /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:03:02 www /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Feb 23 14:03:02 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:03:02 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:03:02 www /kernel: sc0: on isa0 Feb 23 14:03:02 www /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Feb 23 14:03:02 www /kernel: sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) Feb 23 14:03:02 www /kernel: sio0: irq maps: 0x41 0x51 0x41 0x41 Feb 23 14:03:02 www /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Feb 23 14:03:02 www /kernel: sio0: type 16550A Feb 23 14:03:02 www /kernel: sio1: irq maps: 0x41 0x49 0x41 0x41 Feb 23 14:03:02 www /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Feb 23 14:03:02 www /kernel: sio1: type 16550A Feb 23 14:03:02 www /kernel: ppc0: parallel port found at 0x378 Feb 23 14:03:02 www /kernel: ppc0: SPP Feb 23 14:03:02 www /kernel: ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 Feb 23 14:03:02 www /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Feb 23 14:03:02 www /kernel: ppi0: on ppbus0 Feb 23 14:03:02 www /kernel: lpt0: on ppbus0 Feb 23 14:03:02 www /kernel: lpt0: Interrupt-driven port Feb 23 14:03:02 www /kernel: isa_probe_children: probing PnP devices Feb 23 14:03:02 www /kernel: BIOS Geometries: Feb 23 14:03:02 www /kernel: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:03:02 www /kernel: 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:03:02 www /kernel: 2:0223fe3f 0..547=548 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:03:02 www /kernel: 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:03:02 www /kernel: 0 accounted for Feb 23 14:03:02 www /kernel: Device configuration finished. Feb 23 14:03:02 www /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 16 packets/entry by default Feb 23 14:03:02 www /kernel: bpf: lo0 attached Feb 23 14:03:02 www /kernel: ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 Feb 23 14:03:02 www /kernel: ata0-master: success setting up PIO4 mode on generic chip Feb 23 14:03:02 www /kernel: acd0: MODE_SENSE_BIG command timeout - resetting Feb 23 14:03:02 www /kernel: ata0: resetting devices .. ata0: mask=01 status0=00 status1=00 Feb 23 14:03:02 www /kernel: done Feb 23 14:03:02 www /kernel: acd0: read data overrun 28/2 Feb 23 14:03:02 www /kernel: acd0: CDROM drive at ata0 as master Feb 23 14:03:02 www /kernel: acd0: read 500KB/s (10517KB/s), 1792KB buffer, PIO4 Feb 23 14:03:02 www /kernel: acd0: Reads: CD-RW Feb 23 14:03:02 www /kernel: acd0: Mechanism: caddy Feb 23 14:03:02 www /kernel: acd0: Medium: CD-ROM 120mm audio disc loaded Feb 23 14:03:02 www /kernel: (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Feb 23 14:03:02 www /kernel: (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Feb 23 14:03:02 www /kernel: ahc1: target 4 using 16bit transfers Feb 23 14:03:02 www /kernel: ahc1: target 4 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:03:02 www /kernel: ahc1: target 1 using 16bit transfers Feb 23 14:03:02 www /kernel: ahc1: target 1 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:03:02 www /kernel: ahc1: target 0 using 16bit transfers Feb 23 14:03:02 www /kernel: ahc1: target 0 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:03:02 www /kernel: ahc0: target 5 using 16bit transfers Feb 23 14:03:02 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:02 www /kernel: Creating DISK da3 Feb 23 14:03:02 www /kernel: Creating DISK da0 Feb 23 14:03:02 www /kernel: Creating DISK da1 Feb 23 14:03:02 www /kernel: Creating DISK da2 Feb 23 14:03:02 www /kernel: pass0 at ahc0 bus 0 target 5 lun 0 Feb 23 14:03:02 www /kernel: pass0: Fixed Direct Access SCSI-2 device Feb 23 14:03:02 www /kernel: pass0: Serial Number  Feb 23 14:03:02 www /kernel: pass0: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: pass1 at ahc1 bus 0 target 0 lun 0 Feb 23 14:03:02 www /kernel: pass1: Fixed Direct Access SCSI-3 device Feb 23 14:03:02 www /kernel: pass1: Serial Number AJ1EP186 Feb 23 14:03:02 www /kernel: pass1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: pass2 at ahc1 bus 0 target 1 lun 0 Feb 23 14:03:02 www /kernel: pass2: Fixed Direct Access SCSI-3 device Feb 23 14:03:02 www /kernel: pass2: Serial Number AJ1J7486 Feb 23 14:03:02 www /kernel: pass2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: pass3 at ahc1 bus 0 target 4 lun 0 Feb 23 14:03:02 www /kernel: pass3: Fixed Direct Access SCSI-2 device Feb 23 14:03:02 www /kernel: pass3: Serial Number RD4C8750 Feb 23 14:03:02 www /kernel: pass3: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: pass4 at ahc1 bus 0 target 14 lun 0 Feb 23 14:03:02 www /kernel: pass4: Fixed Processor SCSI-2 device Feb 23 14:03:02 www /kernel: pass4: Serial Number 1 Feb 23 14:03:02 www /kernel: pass4: 3.300MB/s transfers Feb 23 14:03:02 www /kernel: pass4 at ahc1 bus 0 target 14 lun 0 Feb 23 14:03:02 www /kernel: pass4: Fixed Processor SCSI-2 device Feb 23 14:03:02 www /kernel: pass4: Serial Number 1 Feb 23 14:03:02 www /kernel: pass4: 3.300MB/s transfers Feb 23 14:03:02 www /kernel: da3 at ahc0 bus 0 target 5 lun 0 Feb 23 14:03:02 www /kernel: da3: Fixed Direct Access SCSI-2 device Feb 23 14:03:02 www /kernel: da3: Serial Number  Feb 23 14:03:02 www /kernel: da3: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: da3: 61208MB (125353984 512 byte sectors: 255H 63S/T 7802C) Feb 23 14:03:02 www /kernel: Mounting root from ufs:/dev/da0s1a Feb 23 14:03:02 www /kernel: da0 at ahc1 bus 0 target 0 lun 0 Feb 23 14:03:02 www /kernel: da0: Fixed Direct Access SCSI-3 device Feb 23 14:03:02 www /kernel: da0: Serial Number AJ1EP186 Feb 23 14:03:02 www /kernel: da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) Feb 23 14:03:02 www /kernel: da1 at ahc1 bus 0 target 1 lun 0 Feb 23 14:03:02 www /kernel: da1: Fixed Direct Access SCSI-3 device Feb 23 14:03:02 www /kernel: da1: Serial Number AJ1J7486 Feb 23 14:03:02 www /kernel: da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: da1: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) Feb 23 14:03:02 www /kernel: da0s1: type 0xa5, start 63, end = 401624, size 401562 : OK Feb 23 14:03:02 www /kernel: da0s2: type 0xa5, start 401625, end = 2490074, size 2088450 : OK Feb 23 14:03:02 www /kernel: da0s3: type 0xa5, start 2490075, end = 17767889, size 15277815 : OK Feb 23 14:03:02 www /kernel: da2 at ahc1 bus 0 target 4 lun 0 Feb 23 14:03:02 www /kernel: da2: Fixed Direct Access SCSI-2 device Feb 23 14:03:02 www /kernel: da2: Serial Number RD4C8750 Feb 23 14:03:02 www /kernel: da2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:03:02 www /kernel: da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) Feb 23 14:03:03 www /kernel: start_init: trying /sbin/init Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK Feb 23 14:03:03 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:03:03 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:03:03 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:03:03 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:03:03 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:03:03 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:03:03 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:03:03 www /kernel: da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK Feb 23 14:03:03 www /kernel: lnc0: Device timeout -- Resetting Feb 23 14:03:03 www named[136]: starting. named 8.2.2-P5-NOESW Wed Feb 23 12:42:20 CST 2000 root@www.securenet.com.tw:/usr/obj/usr/src/usr.sbin/named Feb 23 14:03:03 www named[136]: limit files set to fdlimit (1024) Feb 23 14:03:03 www named[137]: Ready to answer queries. Feb 23 14:03:05 www /kernel: Linux-ELF exec handler installed Feb 23 14:03:06 www /kernel: splash: image decoder found: blank_saver Feb 23 14:03:09 www sshd[261]: Listener created on port 22. Feb 23 14:03:09 www sshd[262]: Daemon is running. Feb 23 14:03:10 www /kernel: pid 256 (snpserv), uid 0: exited on signal 11 (core dumped) Feb 23 14:03:18 www /kernel: (da0:ahc1:0:0:0): tagged openings now 64 no console login messages record .... ><# I login as root, and fire up apache with SSL, then system direct reboot. I also send message as I put the NIC at 5th PCI slot .... Feb 23 14:09:05 www /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Feb 23 14:09:05 www /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 23 14:09:05 www /kernel: The Regents of the University of California. All rights reserved. Feb 23 14:09:05 www /kernel: FreeBSD 4.0-CURRENT #0: Wed Feb 23 13:56:44 CST 2000 Feb 23 14:09:05 www /kernel: root@www.securenet.com.tw:/usr/src/sys/compile/www Feb 23 14:09:05 www /kernel: Calibrating clock(s) ... TSC clock: 498602083 Hz, i8254 clock: 1193024 Hz Feb 23 14:09:05 www /kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Feb 23 14:09:05 www /kernel: Timecounter "i8254" frequency 1193182 Hz Feb 23 14:09:05 www /kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Feb 23 14:09:05 www /kernel: Timecounter "TSC" frequency 498670656 Hz Feb 23 14:09:05 www /kernel: CPU: Pentium III/Pentium III Xeon (498.67-MHz 686-class CPU) Feb 23 14:09:05 www /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Feb 23 14:09:05 www /kernel: Features=0x383fbff Feb 23 14:09:05 www /kernel: real memory = 536854528 (524272K bytes) Feb 23 14:09:05 www /kernel: Physical memory chunk(s): Feb 23 14:09:05 www /kernel: 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) Feb 23 14:09:05 www /kernel: 0x0031c000 - 0x1fff3fff, 533561344 bytes (130264 pages) Feb 23 14:09:05 www /kernel: avail memory = 517894144 (505756K bytes) Feb 23 14:09:05 www /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd5d0 Feb 23 14:09:05 www /kernel: bios32: Entry = 0xfd5e1 (c00fd5e1) Rev = 0 Len = 1 Feb 23 14:09:05 www /kernel: pcibios: PCI BIOS entry at 0xd61c Feb 23 14:09:05 www /kernel: pnpbios: Found PnP BIOS data at 0xc00fde90 Feb 23 14:09:05 www /kernel: pnpbios: Entry = f0000:497d Rev = 1.0 Feb 23 14:09:05 www /kernel: Other BIOS signatures found: Feb 23 14:09:05 www /kernel: ACPI: 000fdec0 Feb 23 14:09:05 www /kernel: Preloaded elf kernel "kernel" at 0xc0303000. Feb 23 14:09:05 www /kernel: Pentium Pro MTRR support enabled Feb 23 14:09:05 www /kernel: Math emulator present Feb 23 14:09:05 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000070 Feb 23 14:09:05 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:09:05 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:09:05 www /kernel: npx0: on motherboard Feb 23 14:09:05 www /kernel: npx0: INT 16 interface Feb 23 14:09:05 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 Feb 23 14:09:05 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:09:05 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:09:05 www /kernel: pcib0: on motherboard Feb 23 14:09:05 www /kernel: found-> vendor=0x1166, dev=0x0007, revid=0x04 Feb 23 14:09:05 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: map[10]: type 1, range 32, base 00000000, size 0 Feb 23 14:09:05 www /kernel: found-> vendor=0x1166, dev=0x0005, revid=0x02 Feb 23 14:09:05 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: found-> vendor=0x8086, dev=0x1229, revid=0x05 Feb 23 14:09:05 www /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: intpin=a, irq=11 Feb 23 14:09:05 www /kernel: map[10]: type 1, range 32, base febff000, size 12 Feb 23 14:09:05 www /kernel: map[14]: type 1, range 32, base 00002000, size 5 Feb 23 14:09:05 www /kernel: map[18]: type 1, range 32, base fea00000, size 20 Feb 23 14:09:05 www /kernel: found-> vendor=0x9004, dev=0x7895, revid=0x04 Feb 23 14:09:05 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: intpin=a, irq=15 Feb 23 14:09:05 www /kernel: map[10]: type 1, range 32, base 00002200, size 8 Feb 23 14:09:05 www /kernel: map[14]: type 1, range 32, base febfe000, size 12 Feb 23 14:09:05 www /kernel: found-> vendor=0x9004, dev=0x7895, revid=0x04 Feb 23 14:09:05 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: intpin=b, irq=10 Feb 23 14:09:05 www /kernel: map[10]: type 1, range 32, base 00002300, size 8 Feb 23 14:09:05 www /kernel: map[14]: type 1, range 32, base febfd000, size 12 Feb 23 14:09:05 www /kernel: found-> vendor=0x1022, dev=0x2000, revid=0x36 Feb 23 14:09:05 www /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: intpin=a, irq=11 Feb 23 14:09:05 www /kernel: map[10]: type 1, range 32, base 00002020, size 5 Feb 23 14:09:05 www /kernel: map[14]: type 1, range 32, base febfcc00, size 5 Feb 23 14:09:05 www /kernel: found-> vendor=0x5333, dev=0x8901, revid=0x16 Feb 23 14:09:05 www /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Feb 23 14:09:05 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:05 www /kernel: intpin=a, irq=9 Feb 23 14:09:06 www /kernel: map[10]: type 1, range 32, base f8000000, size 26 Feb 23 14:09:06 www /kernel: found-> vendor=0x1166, dev=0x0200, revid=0x4d Feb 23 14:09:06 www /kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Feb 23 14:09:06 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:06 www /kernel: found-> vendor=0x1166, dev=0x0210, revid=0x4a Feb 23 14:09:06 www /kernel: class=01-01-ea, hdrtype=0x00, mfdev=1 Feb 23 14:09:06 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:06 www /kernel: intpin=a, irq=14 Feb 23 14:09:06 www /kernel: map[10]: type 1, range 32, base 000001f0, size 3 Feb 23 14:09:06 www /kernel: map[14]: type 1, range 32, base 000003f4, size 2 Feb 23 14:09:06 www /kernel: map[18]: type 1, range 32, base 00000010, size 3 Feb 23 14:09:06 www /kernel: map[1c]: type 1, range 32, base 00000000, size 2 Feb 23 14:09:06 www /kernel: map[20]: type 1, range 32, base 0000ffa0, size 4 Feb 23 14:09:06 www /kernel: found-> vendor=0x1166, dev=0x0220, revid=0x04 Feb 23 14:09:06 www /kernel: class=0c-03-10, hdrtype=0x00, mfdev=0 Feb 23 14:09:06 www /kernel: subordinatebus=0 secondarybus=0 Feb 23 14:09:06 www /kernel: intpin=a, irq=10 Feb 23 14:09:06 www /kernel: map[10]: type 1, range 32, base ff700000, size 12 Feb 23 14:09:06 www /kernel: pci0: on pcib0 Feb 23 14:09:06 www /kernel: fxp0: port 0x2000-0x201f mem 0xfea00000-0xfeafffff,0xfebff000-0xfebfffff irq 11 at device 1.0 on pci0 Feb 23 14:09:06 www /kernel: fxp0: Ethernet address 00:04:ac:45:75:fc Feb 23 14:09:06 www /kernel: bpf: fxp0 attached Feb 23 14:09:06 www /kernel: ahc0: port 0x2200-0x22ff mem 0xfebfe000-0xfebfefff irq 15 at device 6.0 on pci0 Feb 23 14:09:06 www /kernel: ahc0: Reading SEEPROM...done. Feb 23 14:09:06 www /kernel: ahc0: Low byte termination Enabled Feb 23 14:09:06 www /kernel: ahc0: High byte termination Enabled Feb 23 14:09:06 www /kernel: ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs Feb 23 14:09:06 www /kernel: ahc0: Downloading Sequencer Program... 389 instructions downloaded Feb 23 14:09:06 www /kernel: ahc1: port 0x2300-0x23ff mem 0xfebfd000-0xfebfdfff irq 10 at device 6.1 on pci0 Feb 23 14:09:06 www /kernel: ahc1: Reading SEEPROM...done. Feb 23 14:09:06 www /kernel: ahc1: Low byte termination Enabled Feb 23 14:09:06 www /kernel: ahc1: High byte termination Enabled Feb 23 14:09:06 www /kernel: ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Feb 23 14:09:06 www /kernel: ahc1: Downloading Sequencer Program... 389 instructions downloaded Feb 23 14:09:06 www /kernel: lnc0: port 0x2020-0x203f mem 0xfebfcc00-0xfebfcc1f irq 11 at device 9.0 on pci0 Feb 23 14:09:06 www /kernel: lnc0: PCnet-FAST+ address 00:06:29:39:16:e0 Feb 23 14:09:06 www /kernel: bpf: lnc0 attached Feb 23 14:09:06 www /kernel: using shared irq11. Feb 23 14:09:06 www /kernel: lnc0: driver is using old-style compatability shims Feb 23 14:09:06 www /kernel: pci0: (vendor=0x5333, dev=0x8901) at 10.0 irq 9 Feb 23 14:09:06 www /kernel: isab0: at device 15.0 on pci0 Feb 23 14:09:06 www /kernel: isa0: on isab0 Feb 23 14:09:06 www /kernel: atapci0: port 0xffa0-0xffaf,0-0x3,0x10-0x17,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at device 15.1 on pci0 Feb 23 14:09:06 www /kernel: ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 Feb 23 14:09:06 www /kernel: ata0: mask=03 status0=50 status1=00 Feb 23 14:09:06 www /kernel: ata0: mask=03 status0=00 status1=00 Feb 23 14:09:06 www /kernel: ata0: devices = 0x4 Feb 23 14:09:06 www /kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 23 14:09:06 www /kernel: ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 Feb 23 14:09:06 www /kernel: ata1: mask=00 status0=ff status1=ff Feb 23 14:09:06 www /kernel: ata1: probe allocation failed Feb 23 14:09:06 www /kernel: pci0: (vendor=0x1166, dev=0x0220) at 15.2 irq 10 Feb 23 14:09:06 www /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 Feb 23 14:09:06 www /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Feb 23 14:09:06 www /kernel: pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) Feb 23 14:09:06 www /kernel: pcib1: on motherboard Feb 23 14:09:06 www /kernel: pci1: on pcib1 Feb 23 14:09:06 www /kernel: Trying Read_Port at 203 Feb 23 14:09:06 www /kernel: Trying Read_Port at 243 Feb 23 14:09:06 www /kernel: Trying Read_Port at 283 Feb 23 14:09:06 www /kernel: Trying Read_Port at 2c3 Feb 23 14:09:06 www /kernel: Trying Read_Port at 303 Feb 23 14:09:06 www /kernel: Trying Read_Port at 343 Feb 23 14:09:06 www /kernel: Trying Read_Port at 383 Feb 23 14:09:06 www /kernel: Trying Read_Port at 3c3 Feb 23 14:09:06 www /kernel: devclass_alloc_unit: lnc0 already exists, using next available unit number Feb 23 14:09:06 www /kernel: isa_probe_children: disabling PnP devices Feb 23 14:09:06 www /kernel: isa_probe_children: probing non-PnP devices Feb 23 14:09:06 www /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Feb 23 14:09:06 www /kernel: fdc0: FIFO enabled, 8 bytes threshold Feb 23 14:09:06 www /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Feb 23 14:09:06 www /kernel: atkbdc0: at port 0x60-0x6f on isa0 Feb 23 14:09:06 www /kernel: atkbd0: irq 1 on atkbdc0 Feb 23 14:09:06 www /kernel: atkbd: the current kbd controller command byte 0045 Feb 23 14:09:06 www /kernel: atkbd: keyboard ID 0x41ab (2) Feb 23 14:09:06 www /kernel: kbdc: RESET_KBD return code:00fa Feb 23 14:09:06 www /kernel: kbdc: RESET_KBD status:00aa Feb 23 14:09:06 www /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Feb 23 14:09:06 www /kernel: psm0: current command byte:0045 Feb 23 14:09:06 www /kernel: kbdc: TEST_AUX_PORT status:0000 Feb 23 14:09:06 www /kernel: kbdc: RESET_AUX return code:00fa Feb 23 14:09:06 www /kernel: kbdc: RESET_AUX status:00aa Feb 23 14:09:06 www /kernel: kbdc: RESET_AUX ID:0000 Feb 23 14:09:06 www /kernel: psm: status 00 02 64 Feb 23 14:09:06 www /kernel: psm: status 00 00 64 Feb 23 14:09:06 www /kernel: psm: status 00 03 64 Feb 23 14:09:06 www /kernel: psm: status 00 03 64 Feb 23 14:09:06 www /kernel: psm: status 00 00 64 Feb 23 14:09:06 www /kernel: psm: data ffffffff 00 64 Feb 23 14:09:06 www /kernel: psm: status 00 02 64 Feb 23 14:09:06 www /kernel: psm: data ffffffff 02 64 Feb 23 14:09:06 www /kernel: psm0: failed to get data. Feb 23 14:09:06 www /kernel: psm: status 00 02 64 Feb 23 14:09:06 www /kernel: psm0: irq 12 on atkbdc0 Feb 23 14:09:06 www /kernel: psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons Feb 23 14:09:06 www /kernel: psm0: config:00000000, flags:00000000, packet size:3 Feb 23 14:09:06 www /kernel: psm0: syncmask:00, syncbits:00 Feb 23 14:09:06 www /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Feb 23 14:09:06 www /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Feb 23 14:09:06 www /kernel: fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 Feb 23 14:09:06 www /kernel: fb0: init mode:24, bios mode:3, current mode:24 Feb 23 14:09:06 www /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k Feb 23 14:09:06 www /kernel: VGA parameters upon power-up Feb 23 14:09:06 www /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:09:06 www /kernel: bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 Feb 23 14:09:06 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:09:06 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:09:06 www /kernel: VGA parameters in BIOS for mode 24 Feb 23 14:09:06 www /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:09:06 www /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Feb 23 14:09:06 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:09:06 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:09:06 www /kernel: EGA/VGA parameters to be used for mode 24 Feb 23 14:09:07 www /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Feb 23 14:09:07 www /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Feb 23 14:09:07 www /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Feb 23 14:09:07 www /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Feb 23 14:09:07 www /kernel: sc0: on isa0 Feb 23 14:09:07 www /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Feb 23 14:09:07 www /kernel: sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) Feb 23 14:09:07 www /kernel: sio0: irq maps: 0x41 0x51 0x41 0x41 Feb 23 14:09:07 www /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Feb 23 14:09:07 www /kernel: sio0: type 16550A Feb 23 14:09:07 www /kernel: sio1: irq maps: 0x41 0x49 0x41 0x41 Feb 23 14:09:07 www /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Feb 23 14:09:07 www /kernel: sio1: type 16550A Feb 23 14:09:07 www /kernel: ppc0: parallel port found at 0x378 Feb 23 14:09:07 www /kernel: ppc0: SPP Feb 23 14:09:07 www /kernel: ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 Feb 23 14:09:07 www /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Feb 23 14:09:07 www /kernel: ppi0: on ppbus0 Feb 23 14:09:07 www /kernel: lpt0: on ppbus0 Feb 23 14:09:07 www /kernel: lpt0: Interrupt-driven port Feb 23 14:09:07 www /kernel: isa_probe_children: probing PnP devices Feb 23 14:09:07 www /kernel: BIOS Geometries: Feb 23 14:09:07 www /kernel: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:09:07 www /kernel: 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:09:07 www /kernel: 2:0223fe3f 0..547=548 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:09:07 www /kernel: 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors Feb 23 14:09:07 www /kernel: 0 accounted for Feb 23 14:09:07 www /kernel: Device configuration finished. Feb 23 14:09:07 www /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 16 packets/entry by default Feb 23 14:09:07 www /kernel: bpf: lo0 attached Feb 23 14:09:07 www /kernel: ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 Feb 23 14:09:07 www /kernel: ata0-master: success setting up PIO4 mode on generic chip Feb 23 14:09:07 www /kernel: acd0: MODE_SENSE_BIG command timeout - resetting Feb 23 14:09:07 www /kernel: ata0: resetting devices .. ata0: mask=01 status0=00 status1=00 Feb 23 14:09:07 www /kernel: done Feb 23 14:09:07 www /kernel: acd0: read data overrun 28/2 Feb 23 14:09:07 www /kernel: acd0: CDROM drive at ata0 as master Feb 23 14:09:07 www /kernel: acd0: read 500KB/s (10517KB/s), 1792KB buffer, PIO4 Feb 23 14:09:07 www /kernel: acd0: Reads: CD-RW Feb 23 14:09:07 www /kernel: acd0: Mechanism: caddy Feb 23 14:09:07 www /kernel: acd0: Medium: CD-ROM 120mm audio disc loaded Feb 23 14:09:07 www /kernel: (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Feb 23 14:09:07 www /kernel: (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Feb 23 14:09:07 www /kernel: ahc1: target 4 using 16bit transfers Feb 23 14:09:07 www /kernel: ahc1: target 4 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:09:07 www /kernel: ahc1: target 0 using 16bit transfers Feb 23 14:09:07 www /kernel: ahc1: target 0 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:09:07 www /kernel: ahc1: target 1 using 16bit transfers Feb 23 14:09:07 www /kernel: ahc1: target 1 synchronous at 5.7MHz, offset = 0x8 Feb 23 14:09:07 www /kernel: ahc0: target 5 using 16bit transfers Feb 23 14:09:07 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:07 www /kernel: Creating DISK da3 Feb 23 14:09:07 www /kernel: Creating DISK da0 Feb 23 14:09:07 www /kernel: Creating DISK da1 Feb 23 14:09:07 www /kernel: Creating DISK da2 Feb 23 14:09:07 www /kernel: pass0 at ahc0 bus 0 target 5 lun 0 Feb 23 14:09:07 www /kernel: pass0: Fixed Direct Access SCSI-2 device Feb 23 14:09:07 www /kernel: pass0: Serial Number  Feb 23 14:09:07 www /kernel: pass0: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:07 www /kernel: pass1 at ahc1 bus 0 target 0 lun 0 Feb 23 14:09:07 www /kernel: pass1: Fixed Direct Access SCSI-3 device Feb 23 14:09:07 www /kernel: pass1: Serial Number AJ1EP186 Feb 23 14:09:07 www /kernel: pass1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:07 www /kernel: pass2 at ahc1 bus 0 target 1 lun 0 Feb 23 14:09:07 www /kernel: pass2: Fixed Direct Access SCSI-3 device Feb 23 14:09:07 www /kernel: pass2: Serial Number AJ1J7486 Feb 23 14:09:07 www /kernel: pass2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:07 www /kernel: pass3 at ahc1 bus 0 target 4 lun 0 Feb 23 14:09:08 www /kernel: pass3: Fixed Direct Access SCSI-2 device Feb 23 14:09:08 www /kernel: pass3: Serial Number RD4C8750 Feb 23 14:09:08 www /kernel: pass3: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:08 www /kernel: pass4 at ahc1 bus 0 target 14 lun 0 Feb 23 14:09:08 www /kernel: pass4: Fixed Processor SCSI-2 device Feb 23 14:09:08 www /kernel: pass4: Serial Number 1 Feb 23 14:09:08 www /kernel: pass4: 3.300MB/s transfers Feb 23 14:09:08 www /kernel: pass4 at ahc1 bus 0 target 14 lun 0 Feb 23 14:09:08 www /kernel: pass4: Fixed Processor SCSI-2 device Feb 23 14:09:08 www /kernel: pass4: Serial Number 1 Feb 23 14:09:08 www /kernel: pass4: 3.300MB/s transfers Feb 23 14:09:08 www /kernel: da3 at ahc0 bus 0 target 5 lun 0 Feb 23 14:09:08 www /kernel: da3: Fixed Direct Access SCSI-2 device Feb 23 14:09:08 www /kernel: da3: Serial Number  Feb 23 14:09:08 www /kernel: da3: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:08 www /kernel: da3: 61208MB (125353984 512 byte sectors: 255H 63S/T 7802C) Feb 23 14:09:08 www /kernel: Mounting root from ufs:/dev/da0s1a Feb 23 14:09:08 www /kernel: da1 at ahc1 bus 0 target 1 lun 0 Feb 23 14:09:08 www /kernel: da1: Fixed Direct Access SCSI-3 device Feb 23 14:09:08 www /kernel: da1: Serial Number AJ1J7486 Feb 23 14:09:08 www /kernel: da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:08 www /kernel: da1: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) Feb 23 14:09:08 www /kernel: da0 at ahc1 bus 0 target 0 lun 0 Feb 23 14:09:08 www /kernel: da0: Fixed Direct Access SCSI-3 device Feb 23 14:09:08 www /kernel: da0: Serial Number AJ1EP186 Feb 23 14:09:08 www /kernel: da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:08 www /kernel: da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) Feb 23 14:09:08 www /kernel: da0s1: type 0xa5, start 63, end = 401624, size 401562 : OK Feb 23 14:09:08 www /kernel: da0s2: type 0xa5, start 401625, end = 2490074, size 2088450 : OK Feb 23 14:09:08 www /kernel: da0s3: type 0xa5, start 2490075, end = 17767889, size 15277815 : OK Feb 23 14:09:08 www /kernel: da2 at ahc1 bus 0 target 4 lun 0 Feb 23 14:09:08 www /kernel: da2: Fixed Direct Access SCSI-2 device Feb 23 14:09:08 www /kernel: da2: Serial Number RD4C8750 Feb 23 14:09:08 www /kernel: da2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 23 14:09:08 www /kernel: da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) Feb 23 14:09:08 www /kernel: WARNING: / was not properly dismounted Feb 23 14:09:08 www /kernel: start_init: trying /sbin/init Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK Feb 23 14:09:08 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:09:08 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:09:08 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:09:08 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:09:08 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: ahc0: target 5 using asynchronous transfers Feb 23 14:09:08 www /kernel: ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Feb 23 14:09:08 www /kernel: da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK Feb 23 14:09:08 www /kernel: da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK Feb 23 14:09:08 www /kernel: lnc0: Device timeout -- Resetting Feb 23 14:09:09 www named[136]: starting. named 8.2.2-P5-NOESW Wed Feb 23 12:42:20 CST 2000 root@www.securenet.com.tw:/usr/obj/usr/src/usr.sbin/named Feb 23 14:09:09 www named[136]: limit files set to fdlimit (1024) Feb 23 14:09:09 www named[137]: Ready to answer queries. Feb 23 14:09:11 www /kernel: Linux-ELF exec handler installed Feb 23 14:09:12 www /kernel: splash: image decoder found: blank_saver Feb 23 14:09:15 www sshd[259]: Listener created on port 22. Feb 23 14:09:15 www sshd[260]: Daemon is running. Feb 23 14:09:15 www /kernel: pid 254 (snpserv), uid 0: exited on signal 11 (core dumped) Feb 23 14:09:24 www /kernel: (da0:ahc1:0:0:0): tagged openings now 64 Feb 23 14:09:27 www login: ROOT LOGIN (root) ON ttyv0 Ok, Now The IBM Server can do everythings right .... Here comes my kernel config file machine i386 cpu I686_CPU options NO_F00F_HACK ident www maxusers 32 options NMBCLUSTERS=2048 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options QUOTA #enable disk quotas #options NSWAPDEV=20 # Allow this many swap-devices. options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa0 #device pnp0 # PnP support for ISA device pci0 # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives #options ATA_ENABLE_ATAPI_DMA #controller wdc0 at isa? port IO_WD1 irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 # SCSI Controllers #device ahc device ahc0 # AHA2940 and onboard AIC7xxx devices device ahc1 # Netfinity 5000 support two channels # SCSI peripherals # because Netfinity 5000 ahc0 attaches to external usage, and ahc1 attaches # to internal usage, we cannot change it .... ><# device scbus0 at ahc0 bus0 device scbus1 at ahc1 bus0 device da0 at scbus1 target 0 unit 0 device da1 at scbus1 target 1 unit 0 device da2 at scbus1 target 4 unit 0 # Next device entry is for external RAID usage, you must modify it to # match realy world configure. device da3 at scbus0 target 5 unit 0 device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x31 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 device ppbus0 # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel device ppi # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) # ISA Ethernet NICs. device lnc0 at isa? port 0x280 irq 10 drq 0 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse options SOFTUPDATES options MD5 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #pseudo-device vinum #Vinum concat/mirror/raid driver options SC_DISABLE_REBOOT # disable reboot key sequence options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=16 # end of WWW Server config file I also set these flags at my /etc/make.conf # CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations # # To avoid building various parts of the base system: NO_SENDMAIL= true #NO_CVS= true # # To compile just the kernel with special optimisations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway): # COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 22:59:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 2940337B858 for ; Tue, 22 Feb 2000 22:59:28 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip209.r4.d.bel.nwlink.com (ip209.r4.d.bel.nwlink.com [207.202.172.209]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id WAA11188; Tue, 22 Feb 2000 22:58:52 -0800 (PST) Date: Tue, 22 Feb 2000 22:53:52 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein Subject: Re: Upgrade from 3.4 to 4.0... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, William Woods wrote: > > On 23-Feb-00 R Joseph Wright wrote: > > > > make buildworld > > make buildkernel &&make installkernel > > Then reboot in single user mode > > make -DNOINFO installworld > > make buildkernel &&make installkernel (again) > > make installworld > > > > This worked for me perfectly. > > Hmmm.....the only question I have regarding this is does it handle the new > devices corectly? It did, although I did eventually remake them. I did: mv /dev /dev.old mkdir /dev cp /usr/src/etc/MAKE* /dev sh MAKEDEV all I also had to make the partition entries for my IDE drive: sh MAKEDEV ad0s4a Then I edited /etc/fstab to reflect the new devices --Very Important! Of course I also ran mergemaster to update the /etc directory. That's it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 23:12: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id B40F837B8BC for ; Tue, 22 Feb 2000 23:12:01 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 15825 invoked by alias); 23 Feb 2000 07:11:59 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 15750 invoked by uid 0); 23 Feb 2000 07:11:56 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 23 Feb 2000 07:11:56 -0000 Content-Length: 725 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 22 Feb 2000 23:08:54 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: R Joseph Wright Subject: Re: Upgrade from 3.4 to 4.0... Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It did, although I did eventually remake them. > > I did: > mv /dev /dev.old > mkdir /dev > cp /usr/src/etc/MAKE* /dev > sh MAKEDEV all This makes sence.... > I also had to make the partition entries for my IDE drive: > > sh MAKEDEV ad0s4a Ahh....ok. So if my partitions are thus: /dev/wd0s1a 9229851 2248506 6242957 26% / procfs 4 4 0 100% /proc I would do?? > Then I edited /etc/fstab to reflect the new devices --Very Important! > > Of course I also ran mergemaster to update the /etc directory. > That's it. ---------------------------------- E-Mail: William Woods Date: 22-Feb-00 Time: 23:04:46l FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 23:45: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.nwnexus.com (smtp10.nwnexus.com [206.63.63.53]) by hub.freebsd.org (Postfix) with ESMTP id 58B3E37BBF7 for ; Tue, 22 Feb 2000 23:44:59 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip29.nwnexus.net [204.57.235.29]) by smtp10.nwnexus.com (8.8.8/8.8.8) with ESMTP id XAA08261; Tue, 22 Feb 2000 23:44:56 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.3/8.9.3) id XAA00919; Tue, 22 Feb 2000 23:42:56 -0800 (PST) (envelope-from wrsomsky) Date: Tue, 22 Feb 2000 23:42:56 -0800 From: "William R. Somsky" To: "Kenneth D. Merry" Cc: Matthew Jacob , Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000222234256.B893@gramarye.halcyon.com> References: <20000221130916.A11980@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000221130916.A11980@panzer.kdm.org>; from ken@kdm.org on Mon, Feb 21, 2000 at 01:09:16PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 21, 2000 at 01:09:16PM -0700, Kenneth D. Merry wrote: > On Mon, Feb 21, 2000 at 11:50:46 -0800, Matthew Jacob wrote: > > > > It crashes for me a lot. There's some deal about fonts, oddly enough, which > > causes it to crash right away- see the installation instructions that come out > > when you install communicator-47- it said something about mkfontdir. > > > > It still crashes or wedges for me a lot, though. I tried mozilla, and that was > > worse. > > For me at least, slashdot seems to make netscape crash eventually. Same here, except "eventually" is sometimes "immediately"... :-( ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 22 23:56:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 06EB037B85B for ; Tue, 22 Feb 2000 23:56:49 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA27621; Wed, 23 Feb 2000 00:56:37 -0700 (MST) (envelope-from ken) Date: Wed, 23 Feb 2000 00:56:37 -0700 From: "Kenneth D. Merry" To: "William R. Somsky" Cc: Matthew Jacob , Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000223005637.A27599@panzer.kdm.org> References: <20000221130916.A11980@panzer.kdm.org> <20000222234256.B893@gramarye.halcyon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000222234256.B893@gramarye.halcyon.com>; from wrsomsky@halcyon.com on Tue, Feb 22, 2000 at 11:42:56PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 23:42:56 -0800, William R. Somsky wrote: > On Mon, Feb 21, 2000 at 01:09:16PM -0700, Kenneth D. Merry wrote: > > On Mon, Feb 21, 2000 at 11:50:46 -0800, Matthew Jacob wrote: > > > > > > It crashes for me a lot. There's some deal about fonts, oddly enough, which > > > causes it to crash right away- see the installation instructions that come out > > > when you install communicator-47- it said something about mkfontdir. > > > > > > It still crashes or wedges for me a lot, though. I tried mozilla, and that was > > > worse. > > > > For me at least, slashdot seems to make netscape crash eventually. > > Same here, except "eventually" is sometimes "immediately"... :-( Well, Alexander Leidinger's suggestion of disabling Javascript seems to help. I disabled both JavaScript and Style Sheets (in the "advanced" preferences menu) and in relatively limited testing, Slashdot didn't crash Netscape for me. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 0: 4: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C469E37B7A3 for ; Wed, 23 Feb 2000 00:03:56 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA11852; Wed, 23 Feb 2000 18:33:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000223005637.A27599@panzer.kdm.org> Date: Wed, 23 Feb 2000 18:33:26 +1030 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: Crashing netscape? Cc: freebsd-current@FreeBSD.ORG, Alex Le Heux , Matthew Jacob , "William R. Somsky" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-00 Kenneth D. Merry wrote: > Well, Alexander Leidinger's suggestion of disabling Javascript seems to > help. I disabled both JavaScript and Style Sheets (in the "advanced" > preferences menu) and in relatively limited testing, Slashdot didn't crash > Netscape for me. If you login to /. you can change your preferences to be 'simple HTML' which makes it not crash netscape and load faster too.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 0:15:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id B8B0937B755 for ; Wed, 23 Feb 2000 00:15:43 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA34351; Wed, 23 Feb 2000 10:15:05 +0200 (EET) (envelope-from ru) Date: Wed, 23 Feb 2000 10:15:05 +0200 From: Ruslan Ermilov To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade from 3.4 to 4.0... Message-ID: <20000223101505.A32663@relay.ucb.crimea.ua> Mail-Followup-To: bwoods2@uswest.net, freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from William Woods on Tue, Feb 22, 2000 at 11:08:54PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 11:08:54PM -0800, William Woods wrote: > > It did, although I did eventually remake them. > > > > I did: > > mv /dev /dev.old > > mkdir /dev > > cp /usr/src/etc/MAKE* /dev > > sh MAKEDEV all > > This makes sence.... > > > I also had to make the partition entries for my IDE drive: > > > > sh MAKEDEV ad0s4a > > Ahh....ok. So if my partitions are thus: > > /dev/wd0s1a 9229851 2248506 6242957 26% / > procfs 4 4 0 100% /proc > > I would do?? > Do nothing, except upgrade your /dev and /etc, just like you did it when you were tracking -stable. The new ata(4) driver supports old wd(4) names, i.e. it will accept both new adX and old wdX names. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 0:37:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (nebula.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 0C59937B8A5; Wed, 23 Feb 2000 00:37:13 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA04852; Wed, 23 Feb 2000 09:35:48 +0100 (CET) Date: Wed, 23 Feb 2000 09:35:47 +0100 From: Martin Cracauer To: jdp@FreeBSD.ORG Cc: jkh@FreeBSD.ORG, current@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000223093546.B4666@cons.org> References: <20000222100006.A13742@cons.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="LZvS9be/3tNcYl/X" X-Mailer: Mutt 1.0i In-Reply-To: <20000222100006.A13742@cons.org>; from cracauer@cons.org on Tue, Feb 22, 2000 at 10:00:06AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Updates on the "moving" symbols problem: The problem with gdb not finding out the type of tzname[] is caused by the shared libs not being built with -g. It probably doesn't have to do with the problem. I appended a tarfile with some test cases. Case 1-3 show different occasions of the error, all dump core when linked dynamically and work fine with -static. 'shlib3.gdb' fed into gdb will show that the symbol address is a moving target. Case 4 is an attempt to reproduce the error I get with tzname[] from libc.so with a newly constructed shared library and a similar symbol. However, this case works fine and I don't understand the difference so far. Set LD_LIBRARY_PATH=`pwd` to run this test case. I have updated two machines to -current from yesterday, no change in the problem. As I suspect the MMU hardwware may influence the problem, here are the CPU ids from the machine I can reproduce the error on (that doesn't mean I have -current machines where the error does not show up): CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff CPU: Pentium/P54C (99.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf Let me repeat that this looks like a serious memory mapping bug and that we must not ship 4.0 until we gain more knowledge about it. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 --LZvS9be/3tNcYl/X Content-Type: application/x-tar-gz Content-Disposition: attachment; filename="shlib.tar.gz" Content-Transfer-Encoding: base64 H4sIABeYszgAA+w9XYwbSVrO7pE9mzu0u4fEC9LVejMZe+IZd/tnvPEkYT2ensSHZzzYnvxc Nvja3eVxJ3a36W7PxHsXDpR7WS177AMvSEi88sATPMIDYqWFQyfBAw888gJa6ZAOpAMBWil8 X1X1j3/mJ8l6EvamMrarqr+/+n6qvqp2OyvpyNwLyUmFfJ5ECCFyQWafJJPjn7xIhBSkfK4g 5yRJBigpI+ciJD9/0SKRoeOqNiERzVY1dUjtw+AArNM5DYFOt5RvNubuAU9h/2yhkEX757Py mf1Po6D965blzpOHLEmrudwR9s9lhf0leM8AlJzLZCJEmqdQXvk5tz8Oe99Z0SzTWbHsvWK6 a/Vp2lNGGtwj9qJFPCtzLCz+6cByDNeyR/PhcWz8y6sT8Z9Zza+exf9plI5NadvR0y51XOcs 1H/uCsa/Yrq2QZ258Tgu/ldzqxP5X0bOS2fxfxol7XR7RtuRV7S0vCKnb1GdbNI2yWSJVChm 5SJUMpIkpdMxAZmZDZkpZjITkNnZkPC3OgW5p7dnwV4uyiFYx7UHrtGnh0mQzU/Qzc2AfKco w6hyPiROfAA7E1K6XMxNQ3ZnQ8qyD7mlPqAdo0cBMDfJvFDMBYB1pbSxpcySsVDM+CPfmOO8 7Jt/fiyOjf9swdv/SatZGeNfXs3nzuL/NMrbhqn1hjolVxxXN6yV7rVY0MWCDXpihunG+qph JvYtQ0/GvhsjBIJxqLnE7cPfGrSNDkl4AZqIb1km92aZYLhJGPNbSpN5dDxF4guX4P2i20+S q1fJ9m61miRIlJCBDbw6ifiOajuGuUc6KsSR/p4ZT66x6/Sh4SZk1ngUiwXwTWBLDlSHLC44 iwCeIqqjMVmQC8ADrE3doW0SaS326CzTEcWbqubJ47j4L+SD85/VXJ7Fv5w9i//TKOXNaul6 4ypZvqX2emR5jyxX0kPHTju2loaVAV9aGqYGDCVyIbFVqystjpOM8c+Mj3w4Zqy6wflEl6sr sVipWr0aFSsPEWmF+MwSeMeVdsWxRFcuFgPyReAOeMlYTCAUPcwVAPRTAysWvZAol5MALcQk yxa58C65ANOYt4JbReIv+36tO4mZAdSNnUqZLHcGhkaWNUHJR43FAlkDilMSIB2nq9qwwAei iKF5g8jBIAJi02O4kBAa9IYToC33ECsW03pUNYux6LLdJ0vQv7SiWTb1tHaY/f1EaY4+dkz8 w+WcH//wzuK/cHb+dyrFX+zjfhzEY7EZWcGsHKAjVl8AorYNy3pJ123qOER1SZvuGaYJS3jx PXdhwFbkjmWxhXsKrWyZLjVdhrcwKLI1PBWs5IDH3u5K9/infI/TYV3kKom3VVuKe12y1yXH Z3Lzhey41CYHtuHOVUrDhIxlNsVxSRBwXmJ4mRIX5SwXOiui+Jv6OfI4Lv/LFfL+/i8nrbL5 f/Xs/PdUysn2fxqkL2Qp5qdZCbxf5BLe3R52UiTc0em7qdD+cAk2YGsn30OebSJPs/ir/hx5 HHv/p5Dx8r/Maq6A8V84O/89nUIfQupheoEL6cI98HKMUJ63sFhd4x1eAiH6XrTkZ+WLKKFD 9bnxODr+M4Xsamj9z7D7P7nMWfyfSkkvxcgS2bEOqK1be6Ri6qAQvBtIHhim3hvBevdbQ7w3 TDqU6m1Ve0A6ttUnqjmyTEr6lm50RrDGIhW3awDY0IQl0zKL0IOdG6pLi6TZHaaIlCffGppE vny5QDJZvMchF8iylJMkQhB0EwgXya/TfcMk9aGuj8iVB9hYsbHx7kAIuaJZ/WsI37SK5Ftq H2TdNNz3rxvtNiQMV+5jz7smrPHOikldBtkYtu9TzS2SOsiy61BidcjIGtrETzaySUhhIOdJ dA4gOQEUxqBLYfyqA2Q7lg3jg22yaeGg40TrqUOHZwuOBZdgN8aUYWgqDt8hB9awpyMVEJcS pjnV1MkBhQ64AvOrS/ds0A7S7bNrNjUcZ0h9gio5MGDXx2RRh7pBTc3DRt6GSxKAa9P2iDgD EFTHZAelPKBqz+0mVwgMAWzSBSG5ivuqzvAGluMY7R7wtsgedX09YPvAsh8QGHIfbEysAQUZ ka4zclzad1aQTGWxT0wL0IY2MOuOmLiLDokPepDhkaGpahoduCpwiCNJlGnTpnS9sUFcqvZX PA2XzNGBOkqhMYimsnXI3GMSAlb8wHC7BBSPn9ZwXMFxyM2QAmI6lJKO4cJwFfO+NVohJy6e HCGnOyQeUlDXUO50jMdM2RqMbGOvC0bQkujUuVloIEup1yMM0AEDO9Tep/qKCI461Q2Eaw9x SMwHmGFNcIGhDcbGnrZhqvYIPbAPUkzohBk1pBZIWcEkYLS+4boUF21rH3xI5w6FduhYvZ51 gBaFnF03mLMyBwO8PnUxbom8MiGagxEjZGJx0ofxYS6M5kaqatvax0tCJ0gECviIodEUnxl6 QA/JBGzZ8MZlAqYQWeCJNvORzLQgwDCkEU8QGKc+1OicZBEkxFh1Sxv2qemqntHSYA8LIxFi BtIpQ+05geKZweCioBEeDBtidoV5iKrvU9s12H4loIJsAJBtYqgKOw+Y7IDZkE9hOBRB1rE6 7gEzIeoDmEAkjibGA1OQaR3ATmiPIt2iQBWTBNegS8TuzwlI6nSf9mAiAFcczfRxJJRbYdOl CbMvijZrRemDRDhrtCkOQMcQp6Zu2TgYT8UgRd+COVFI4wBz24CI4asOs50vlzctOAOqYQBg huoTwnM9l5o8FGCy49pms/qNSoM0apvNW6W6QqC+U6/drGwoG2T9Dtmp3VLqG7XrpLK9sdto 1itKg3znO6UGwC0uktL2BrzuIBXl9k5daTRIrU4qWzvVCqADvXppuwkoMFlsl6u7G5Xt6ymy vtsk27UmqVa2Kk0Aa9ZSIIPC5tEpTFLbhD1uvXwDmqX1SrXSvMO4blaa28huE/iVyE6p3qyU d6ulOputdus7tYZCcDgblUa5WqpsKRsw81S2gTFRbirbTdK4UapWke/MIa4zcaqV0npV4Ty2 7wCtulJu4liCWhkUBZJVU6Sxo5QrWFFuKzCMUv1OCpTBZsbadkP5jV2Ag+tko7RVug4sEseo BKxQ3q0rWyhsbZOt2rvrjWaludtUyPVabYPpuqHUb1bKSmONVGsNpq3dhpICJs0SskcqoCq4 zEVZ321UmN4q202lXt/daVZq20lyA1RwU6mTcgmwN5iCa9tszKCgWv0O0kVlMP2nkNCtGwpc qqNKYXjNegnVgcorN0OQKEGzVm+GBku2levVynVlu8xUDAA1JHSr0lCSYLFKA2EqnPmtEnDe xeEzQ4FsvBryVyYMWpRUNklp42YF5Rfw4ASNivAZ6Grslm8I7fN1K/a20dFpB+RdL7fq5UbM wSlMC5/d2Jpj6HfvkasxQuIXxJJdJLPu6aWDnUNqH1YMyOVgEbycljNpWSKyVMxnivkccbq0 p1tmlygPB+RCfC32NsS80WHCmChNDw+GvMZ2rbLhi4UC+bM4Eyr+buLt5POtvCBBmL6jeSMm jHgwqKi0IpOERzhJLufSUjadKfhDIOkl8hYIbZgwPaHgqOPgEs50ODah+ckztaBHc0eDiS4c gbnH+9Bk0VbzBn5XqNUobSohuIHbxbRvDDkuOlswG+7DQoI3dITOQzd7QIqepak9drsnrJAl 0pp5yjd+xDd2vocHY2PnCO77uAywo4RZ8gt2goInbn/o0ofR1p7l7vVd3tLBKjsCcwumgdut RrMEE1+rsl3BuaXybaXum3OMTsuNRsOUYEG4Si6OE/ddURBAWwFA6/pWEwXnloUs03ifWp2E mowmeJVAnaSJ14DWXeleMjmhxthsNZ7ksDT23VgUL0a1NaiEYAeuDT0gZ9RIxaLRHjV5kyiQ 7oP6gf0+ZDi1UAtGEgU0GD0wAuiDrgFZfwJJkbeuEgmPTKNRPHhF0fAgVUpCR7QNunyAyFEN cBH80iXWRFANURcXFjky64IldqBqNJEYmo6xhxGBIie1JKPms0UeyJZcvEgOQUEYgRWFKrKF Gu1hXuzxXmIXOFBwIAsN0BZsVoYUG49Q3LBmYCAMqjbV11PbtFecGGw06kCGoXXZLIMD1VSQ QSp6NVBA0Rs+F8hTy7RcIXUy1Esclak8FHDMO6oYl3T5mg7B22LuwQ7QBacxKx3NpBzI95bh 6Mae4R6h7IAUNmECu337Ns8MDwyYRxlxtg3OLjNSRIMccshnWpjioswfYTQZJgsCJgymXYL9 YO8J4x8uzxrh5uXeFTXI0lVYT9ZE4xI3P1kmi9Ii7wQGy8us+sj3R3IFVoZZI3P7y9fcfmtE VYwKA3c7kgTU5MvSbDVqJ7CV9lyG2jiCQ3yhn17Q0wuj+DOTVwI/GAuH731vbKrglARydDx0 RBTC9GgRFiwh8rVnI187IfnNxSDiOiGPVo6gPVOTMHWAwoBGkvyabzilg5YjxaBj87lMWT/S lDeKC1vPbkf7SNoVoF1caJCFwbNzaB4rPXB4dvK3TxBJt59L/Q9PwOHhc3G4/xyTKp8gsy/P BIkxapBrJLu6etRUqcPGHadKmCRn6mQrFKKN8UWRqZWxOXa1D6g+j3Zf8PLjSc/nmq1FnwpT +TWSF2vSuJN5mu4bOASD0yIs5xlHX5WOQneoFqDHxsxw8qRrMkNErLcOQwMgL1fzs6Yp97gR co9KqP4gVO9xt0kv4Tvuk/F0C/ZsKbLQA6HZSZZl9kbeYQ+1CX046Bma4fZGAsc7lwPpVEec NOG51/vUtpYHqq7D9o+QG7Cj26d2SiCxA3TkYFoEhtTHQz7VOzHzMXE3xhEEGk+OKEoXSIQH XHtWG8/V8eaIa1nsEN0TDz3OwSSWnX7BXsyybaqB/IJ0+v+36495/o1FDHpefzAVBZnsLDcW Hu8ByZkj5qQu3r1hvv7SuPlgwoX9/Bn+2tbekJl+oNpo/Dbt4JdzcRTLNu1Bpq8LLN+bnLBX cAPDegaVhLeQqaEVDC6ZKIbWH4yvdmo/hW6Q5OtbyA5hRQbKnphYJgGBiA85bgmBgEYAP+Fb 02g4J3sUO3Qgg5MMZPCFDuStQwZyCftPNpQxv+QuUArNaCp3h3A44prrnSd4wzqg9AGsrxB6 Rijw/Dgq+bEzW3UC/a5xj6twthL5lWh0Gsu/FKhW9ATDHV+KDpHjGYR4GgkmchcAO0yRR0wa ByKR8fcIIfNORvNuyJS3jots/KIYu7OrmmzdUR0HViK8SU721Z7hxbZh4i0rfttogCeSpuvd U3L74hAI76iyO3WGI7AGFh7xwM4IxqkNca4gKt6W7iHtIayQjkXuD9khEdUesFtNHNFm91LR AU3r4Eu1xrBMKjtLypdiJTh4jj0CanVCA37ydyLXfmm0oIciiE5EEEudaCh1gkgK8rnpTE6g TeVz4EvukSmct6oOtS45OpGjZ4ncdJBl5SN8rv/y+dx6yOfaoXr3ZItx3zLd7vRSPHaM5S2D wRq9HqzRhyRqPbfFSIdWyCOXyOgszODq1EoZXiq5ASfW7KcQ9tkEfWohx8Q7VJJnkePpVXV8 csEd46hYsMyTZhb95z5Belnmh9AJ0pGbNaEcfn700swVd0Lzw+gFn1qJ4LzDzqZzpPiSmNiX SmAtXw1ukwTXR4tMFnCH1cvJgL4cAsSLU6erIQ/x7sa8RO7xbe4STHvhm7DagN9pZI33IT1w 8K6sby1tAOMAudYQkss+HAyoPSWENgATXboEH+S76SXaH7ijpXSg+QGYBocnzCcYAW3MbDTV ByCXiCymSDY5DkYJAZsi/GazR2ktTOiu143ffFh8z/MBceeeP1Wp1EvxsW55qtuh7IFCb3qW 0B+AOk7PvhTx61vNeNIbCH43S9xlB2Ly2AbzUBK+WGNkhO9AEIBx/BOIE9KSj6Q1LlcANn6o wJcPMd17Cg0i6FHIrVgL/gSBBHefJIN/FPsCnrDyvjRAloDFIV+8iI5/RwL86EHiYvg7Ecng 6znRwEg4WiA6fUcldB8F1Y0w4PACkWsXgVsgJCBjda+f4PCoTPYFFAZgJy4Gd2TGGT860VCG 5tGDEWpnqvlSPLf1RRX/xwzmyOPY5z/zWf/5r4Is8ee/8mfPf5xGOfnz/8EjYhlcBvBJyzg+ I2aoPSmeCrVkaD0ST5HFgqfI+C8G+I/sQ23ykX2o4SP7jwTq2PNmR//eAPtysAHrq07n9QT9 l3TW8H+qbY48jv39v6z/+18F/C4O+/2vs+e/TqU88+9/HRqL+FwCS7GKRAQib/LHp2ckmM9G i5AZSelziCUy2WcnMYV2E0/nnanpxddAOBV9YY+Wh36AcW48jn3+Oy/78Z/J5c5+//MUC/72 m/fTW7E2wSCP2TH/+SHmoDET/r1oQc/KXIqX9TnW/HhA/B/1/z8UCsHv/8LCz57/zpw9/306 5ftKdfPcuXMR8ahP5FX4dw76P4O3HHz+SZTD5SIEriQivxL5ZXY9XP70Ff76BWy8HmHXWd+b /PUQ2r8Dr/PiOlyK/Bjefvwmf92O8Bde/wq8XoXXL8Lrq/DCeeeVEC8hDuP1moA959EW+JMF ryMfLG9E/uMJ0vzLUJvA5z+LQb0JlC/C5x+94rVfi6TgU4d2nrXPR2T4vPANLt8bkV9i/R48 0rsirnvt8kS7Bp+pUDvS2rizXdqqlCOt69Xaeqnaqm1uNpRmq4mP47UiLdxERVod+IiwKmxK Ii3q0ofQS3XVVSOtVttxWujK2GXqkb+F8Z0HpXyGCvokEtn94F8e/9vrNxufIdO7v/vJ34Ad Pvrznz158uTxX+B7xH3j48effuXxtcjwv39y/oP/+vD8k394/OnnHz3+d7h4+dODn979zR99 8tH+FJ3vMzqfMzqfMzpf/5jjMlo/QzTA8eFrAP/h469B46MP//WnT5588HcfvO61f+K1733+ o08+/vjjz34fCH6CG0UcsRx5gvSheJ+eTb3yNWHHrwt7oC/8gfCVH5zjPvKPwqeawsdeZzaI RP7pHNqW2/Qb4nO8fDPyZ69yXF34QyRUX4XPKwJSiXB/x+KG6j8M1f86VP/fUL1wLqg/DtX/ PlT/z1D9m68EdSVUvx+q/yBU/+NQ/a9C9f8J1X/11aD+bqh+P1T/bahfAM3i2D+E+gaPflE/ z/TK66/BzOHVvxqRZuBeiPDY+j2oEzG7YD/q9g9fCZ9RTfzvJPhLBWlt31lmlbH/yiAd2dO0 TEuz+gP87acVCBy36CaklJy8arOPNUnCH5ISBVpywS9rETztYPAZDp8B+DU5A1d6lrlHPGrZ k1Hzj/49vFwITxrDy4bxGK8p5PxTII9JuxogytKssiYVZpUwrSlpCodJIx9Cy+latuujv8PR 30muLWczhdV31vDdh5ridpmDX0ZzrObz2fz/tXftPE4DQXhzueIuB+J9QoJikRA6EGcl5hWS BgHiGoQojmeB5Fx8iUViI9tBHFCARIFooYQGKCkQSnk/gILyCsor+RnM7OzaG+PjISEkpPmk vcnsjmfHu2vPjOPbgGT+rQrNcF1bVAedDbdJ0zbx7QvJmaWAprfdU6BqdRB5epm42WmdhFbR jUadgU9N+aQ3sUkNi92eT27DRQFchAP/QXYODZjApIlvcLWU2HFYR247GHo9zZ9wsSI/0DLL TOFpbZcRsfs3M3JGG2hkfjBUjz1QbSmm99QE40xEeZzWJc3gjbi1hNcDDLJn5r3daGMVjOcx dakIsXThQksuLF25dlS6ztlTjqv+N7hRh7BvIfYHvpf4f1fK3K/x7lFvOHX00b9bJ5xkbZh6 HaBpTLRvPvW9pC+c7loIIkTTWDjQrdOLUuEod+woT+wo/+zEkXLIDv1dSaM4AYaIOgR0eMNg RTjgsbFH6tfrKMUwVfjeE/VAbWGU/sHu3AcE+Tt0T690OSfyGGpal0OC/B/Wb+jyUeTxFMrg PfyorkM59KFYlq3+TCyI4zir5dCXYpnR/DatD/mWyOM19NWblTx2M/YJbbORw1gUy7hE7pIl hz4fS5m+y1oO7Xk7RcXOac15LOvPeM4qfrWDT0vf7RK5mRI5z5Ibg9x4C7m+JYex6foUjb8t h2WozxXlVPw8RbFz1ZJD/fc1xXqMPQ9Xy/t9ZJ07AuWeVPK+UQ7n76nVB+I9NHyyKoyOFwV9 16FTO6cybS9FHstjjHQOgrYFQfOzwzqPN4LifMRrKJ9n8jjL1rerYN80KH9XImfWgEEf+pVQ MQ+f94t83c8W9D0Ho+6U6Nur7ZSaHoSGClyANzV9XCmLJQmvNK1qbRsZTxY+qxieLPma8TR7 mxlPsde3jKcrwOQkVT2CbzOeLPqw2/CzBZ6ujHHGzym6nvHbFP2S8dsVNTlOFXIiG1U1oza/ s8DvUjTNeFL8OuP3FOT3Fvh9BX5+Yg1OQ441JyZzQNRg52x437RzQLw/2jnfETGZw7liMkds ismcsCwHtHPOW6KQA+ZBbp4N6hRPORnKAe00T/kbSgUpByxPHjEb3Br0CzQ/EfgL+OX3v41G /vsPrtr/F5w7P//5FzjvRx1vpZ+Owp4ftmqL8mocQXw4lCnun4QvXEu1rUWygpvUDYLwrh/K MIAjpDdardUueonsdTsyP3AYpLILFDf+C9O1exI3HguDB1kD7mgH0VQnGvjy4UhC107thh+G shv4MlIb9eFTabXTl5LFp9O6T9SxiDuXYVoX+JAhJEHYPU7W1rpgDFjlqN9iuBdHvdgbDun4 k3Lg+aNVsLoDKj18HbzrQZ8xqg16Dj/fZjAYDAaDwWAwGAwGg8FgMBgMBoPBYDAYDAaDwWAw GAzG/4TvYTBAPACgAAA= --LZvS9be/3tNcYl/X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 1: 7:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C25A237B815; Wed, 23 Feb 2000 01:07:30 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Feb 2000 08:57:51 +0000 (GMT) Date: Wed, 23 Feb 2000 08:57:50 +0000 From: David Malone To: Archie Cobbs Cc: julian@elischer.org, myevmenkin@att.com, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NETGRAPH patches (proposal) Message-ID: <20000223085750.A29008@walton.maths.tcd.ie> References: <38B34BBA.41C67EA6@elischer.org> <200002230502.VAA84742@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002230502.VAA84742@bubba.whistle.com>; from archie@whistle.com on Tue, Feb 22, 2000 at 09:02:43PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 09:02:43PM -0800, Archie Cobbs wrote: > > It's because all packets sent by this node should have the node's > > address. If you don't have it then PPPoE cannot send a packet "FROM" > > thia node, as it has no idea of what this node's address is. > > So.. we can have two hooks, one that sets the host address and > one that doesn't.. :-) In that case can we have one that also sets the destination address via arp? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 1:34: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D86A937B897 for ; Wed, 23 Feb 2000 01:34:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA81418; Wed, 23 Feb 2000 01:23:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA26390; Wed, 23 Feb 2000 01:23:19 -0800 (PST) (envelope-from obrien) Date: Wed, 23 Feb 2000 01:23:19 -0800 From: "David O'Brien" To: Donn Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? Message-ID: <20000223012319.A26357@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000221195137.D50580@funk.org> <20000222090924.B29249@cons.org> <38B245C0.F0ABAC48@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B245C0.F0ABAC48@cvzoom.net>; from dmmiller@cvzoom.net on Tue, Feb 22, 2000 at 03:16:00AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 03:16:00AM -0500, Donn Miller wrote: > I can give you the .mozconfig file I used to successfully build Mozilla > on -current. Patches to make the port compile on Current? :-) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 1:36:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (nebula.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 9768737B64D; Wed, 23 Feb 2000 01:36:09 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id KAA04922; Wed, 23 Feb 2000 10:00:36 +0100 (CET) Date: Wed, 23 Feb 2000 10:00:36 +0100 From: Martin Cracauer To: jdp@FreeBSD.ORG Cc: jkh@FreeBSD.ORG, current@FreeBSD.ORG, dillon@apollo.backplane.com, obrien@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000223100036.A4872@cons.org> References: <20000222100006.A13742@cons.org> <20000223093546.B4666@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223093546.B4666@cons.org>; from cracauer@cons.org on Wed, Feb 23, 2000 at 09:35:47AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [CC'ed David, since the new compiler seems to cause the problems] Sorry for the update bombing, but I found that the file where the tzname symbol is being defined in triggers this error mesage in a `make world`: cc -fpic -DPIC -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/stdtime/localtime.c -o localtime.So {standard input}: Assembler messages: {standard input}:87: Warning: warning: unrecognized characters `@GOTOFF' in expression {standard input}:114: Warning: warning: unrecognized characters `@GOTOFF' in expression The assembler code looks like this (not that it is surrounding the symbol we have problems with): .L18: leal (%edi,%edi,4),%edx leal 1868+lclmem@GOTOFF(%ebx),%eax <<< [1] leal (%eax,%edx,4),%edx movl tzname@GOT(%ebx),%esi movl 4(%edx),%ecx sall $2,%ecx movl %ebx,%eax addl 8(%edx),%eax addl $6988+lclmem@GOTOFF,%eax <<< [2] movl %eax,(%ecx,%esi) incl %edi movl -4(%ebp),%eax cmpl 8(%eax),%edi jl .L18 Note that 'as' complains about [2], [1] is fine. I'm not that familar with gas syntax, but it seems to be that this is a syntax error generated by the new gcc, that @GOTOFF must be passed one argument. /usr/src/contrib/gcc/config/i386/i386.c:2988 seems to be the line that writes the GOTOFF without an argument. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 1:57:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 929AF37B5DA for ; Wed, 23 Feb 2000 01:57:19 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 29346 invoked from network); 23 Feb 2000 09:51:44 -0000 Received: from lcm208.cvzoom.net (208.230.69.208) by ns.cvzoom.net with SMTP; 23 Feb 2000 09:51:44 -0000 Date: Wed, 23 Feb 2000 04:51:20 -0500 (EST) From: Donn Miller To: David O'Brien Cc: freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <20000223012319.A26357@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, David O'Brien wrote: > On Tue, Feb 22, 2000 at 03:16:00AM -0500, Donn Miller wrote: > > I can give you the .mozconfig file I used to successfully build Mozilla > > on -current. > > Patches to make the port compile on Current? :-) Well, I've been checking out the source code to Mozilla about 2X a week (via cvs -z3 co SeaMonkeyAll), and building it on my own... I see they've fixed some stuff since M13. But, putting the right stuff in .mozconfig can be tricky. If you put certain things in there, the build will bomb out. BTW, I noticed there's certain bugs with gcc's optimization code. For example, I used '-mpentium -O3 -pipe' as the optimization flags in building the latest Qt snapshot. If I used those CFLAGS I described, the build bombs out with "Internal compiler error". When I reverted back to the stock CFLAGS for the Qt build (-O2 -pipe), the errors went away. I guess I really don't have to build _everything_ on the planet with -mpentium -O3 -pipe. I noticed that most gcc "Internal compiler errors" are caused by using high optimization levels. I really didn't notice that big an increase in performance, anyways. The performance increase was about on par with changing the air filter in your car. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 1:59:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from stargate.iss.com.tw (stargate.iss.com.tw [210.68.99.1]) by hub.freebsd.org (Postfix) with ESMTP id AEECC37B906 for ; Wed, 23 Feb 2000 01:59:19 -0800 (PST) (envelope-from urania@iss.com.tw) Received: from stargate.iss.com.tw (root@localhost) by stargate.iss.com.tw with ESMTP id RAA20560 for ; Wed, 23 Feb 2000 17:29:23 +0800 (CST) Received: from iss.com.tw (mail.iss.com.tw [172.16.6.97]) by stargate.iss.com.tw with SMTP id RAA20556 for ; Wed, 23 Feb 2000 17:29:23 +0800 (CST) Received: (qmail 27917 invoked by uid 1001); 23 Feb 2000 09:16:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Feb 2000 09:16:06 -0000 Date: Wed, 23 Feb 2000 17:16:06 +0800 (CST) From: User URANIA To: freebsd-current@freebsd.org Cc: laa@zgia.zp.ua Subject: Re: Problem with IBM Netfinity 5000 Server Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for sending you all the messages from /var/log/messages, here is dmesg as the NIC at 5th PCI slot, Sorry for I cannot got dmesg as the NIC at 4th PCI slot, server reboot and I lost every things .... Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Feb 23 13:56:44 CST 2000 root@www.securenet.com.tw:/usr/src/sys/compile/www Calibrating clock(s) ... TSC clock: 498602083 Hz, i8254 clock: 1193024 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 498670656 Hz CPU: Pentium III/Pentium III Xeon (498.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536854528 (524272K bytes) Physical memory chunk(s): 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) 0x0031c000 - 0x1fff3fff, 533561344 bytes (130264 pages) avail memory = 517894144 (505756K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd5d0 bios32: Entry = 0xfd5e1 (c00fd5e1) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xd61c pnpbios: Found PnP BIOS data at 0xc00fde90 pnpbios: Entry = f0000:497d Rev = 1.0 Other BIOS signatures found: ACPI: 000fdec0 Preloaded elf kernel "kernel" at 0xc0303000. Pentium Pro MTRR support enabled Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x00000070 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) pcib0: on motherboard found-> vendor=0x1166, dev=0x0007, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 00000000, size 0 found-> vendor=0x1166, dev=0x0005, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base febff000, size 12 map[14]: type 1, range 32, base 00002000, size 5 map[18]: type 1, range 32, base fea00000, size 20 found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00002200, size 8 map[14]: type 1, range 32, base febfe000, size 12 found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=10 map[10]: type 1, range 32, base 00002300, size 8 map[14]: type 1, range 32, base febfd000, size 12 found-> vendor=0x1022, dev=0x2000, revid=0x36 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 00002020, size 5 map[14]: type 1, range 32, base febfcc00, size 5 found-> vendor=0x5333, dev=0x8901, revid=0x16 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x1166, dev=0x0200, revid=0x4d class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0210, revid=0x4a class=01-01-ea, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 map[18]: type 1, range 32, base 00000010, size 3 map[1c]: type 1, range 32, base 00000000, size 2 map[20]: type 1, range 32, base 0000ffa0, size 4 found-> vendor=0x1166, dev=0x0220, revid=0x04 class=0c-03-10, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base ff700000, size 12 pci0: on pcib0 fxp0: port 0x2000-0x201f mem 0xfea00000-0xfeafffff,0xfebff000-0xfebfffff irq 11 at device 1.0 on pci0 fxp0: Ethernet address 00:04:ac:45:75:fc bpf: fxp0 attached ahc0: port 0x2200-0x22ff mem 0xfebfe000-0xfebfefff irq 15 at device 6.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 389 instructions downloaded ahc1: port 0x2300-0x23ff mem 0xfebfd000-0xfebfdfff irq 10 at device 6.1 on pci0 ahc1: Reading SEEPROM...done. ahc1: Low byte termination Enabled ahc1: High byte termination Enabled ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Downloading Sequencer Program... 389 instructions downloaded lnc0: port 0x2020-0x203f mem 0xfebfcc00-0xfebfcc1f irq 11 at device 9.0 on pci0 lnc0: PCnet-FAST+ address 00:06:29:39:16:e0 bpf: lnc0 attached using shared irq11. lnc0: driver is using old-style compatability shims pci0: (vendor=0x5333, dev=0x8901) at 10.0 irq 9 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0-0x3,0x10-0x17,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at device 15.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: (vendor=0x1166, dev=0x0220) at 15.2 irq 10 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) pcib1: on motherboard pci1: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 devclass_alloc_unit: lnc0 already exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0045 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 00 00 64 psm: data ffffffff 00 64 psm: status 00 02 64 psm: data ffffffff 02 64 psm0: failed to get data. psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:00, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: SPP ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 2:0223fe3f 0..547=548 cylinders, 0..254=255 heads, 1..63=63 sectors 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 16 packets/entry by default bpf: lo0 attached ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata0-master: success setting up PIO4 mode on generic chip acd0: MODE_SENSE_BIG command timeout - resetting ata0: resetting devices .. ata0: mask=01 status0=00 status1=00 done acd0: read data overrun 28/2 acd0: CDROM drive at ata0 as master acd0: read 500KB/s (10517KB/s), 1792KB buffer, PIO4 acd0: Reads: CD-RW acd0: Mechanism: caddy acd0: Medium: CD-ROM 120mm audio disc loaded (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc1: target 4 using 16bit transfers ahc1: target 4 synchronous at 5.7MHz, offset = 0x8 ahc1: target 0 using 16bit transfers ahc1: target 0 synchronous at 5.7MHz, offset = 0x8 ahc1: target 1 using 16bit transfers ahc1: target 1 synchronous at 5.7MHz, offset = 0x8 ahc0: target 5 using 16bit transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Creating DISK da3 Creating DISK da0 Creating DISK da1 Creating DISK da2 pass0 at ahc0 bus 0 target 5 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number \^_ pass0: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass1 at ahc1 bus 0 target 0 lun 0 pass1: Fixed Direct Access SCSI-3 device pass1: Serial Number AJ1EP186 pass1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass2 at ahc1 bus 0 target 1 lun 0 pass2: Fixed Direct Access SCSI-3 device pass2: Serial Number AJ1J7486 pass2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass3 at ahc1 bus 0 target 4 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number RD4C8750 pass3: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass4 at ahc1 bus 0 target 14 lun 0 pass4: Fixed Processor SCSI-2 device pass4: Serial Number 1 pass4: 3.300MB/s transfers pass4 at ahc1 bus 0 target 14 lun 0 pass4: Fixed Processor SCSI-2 device pass4: Serial Number 1 pass4: 3.300MB/s transfers da3 at ahc0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number \^_ da3: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 61208MB (125353984 512 byte sectors: 255H 63S/T 7802C) Mounting root from ufs:/dev/da0s1a da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Serial Number AJ1J7486 da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number AJ1EP186 da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da0s1: type 0xa5, start 63, end = 401624, size 401562 : OK da0s2: type 0xa5, start 401625, end = 2490074, size 2088450 : OK da0s3: type 0xa5, start 2490075, end = 17767889, size 15277815 : OK da2 at ahc1 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number RD4C8750 da2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) WARNING: / was not properly dismounted start_init: trying /sbin/init da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK lnc0: Device timeout -- Resetting Linux-ELF exec handler installed splash: image decoder found: blank_saver pid 254 (snpserv), uid 0: exited on signal 11 (core dumped) (da0:ahc1:0:0:0): tagged openings now 64 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 2: 0: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 1B9B737B9AA; Wed, 23 Feb 2000 01:59:55 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id KAA17199; Wed, 23 Feb 2000 10:01:01 +0100 (CET) (envelope-from asmodai) Date: Wed, 23 Feb 2000 10:01:01 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Cc: dillon@freebsd.org Subject: Panic (pmap) Message-ID: <20000223100101.B17129@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And I may welcome panic #6 here. db> trace pmap_remove_all(5a3e000,c061ab70,0,c0230ac0,d62a2f8c) at pmap_remove_all+0x40 pmap_page_protect(5a3e000,0) at pmap_page_protect+0xde vm_pageout_page_stats(0) at vm_pageout_page_stats+0x15e vm_pageout(0) at vm_pageout+0x1fb fork_trampoline() at fork_trampoline+0x8 Dumping system to disk, and will put out the gdb bt when it's done doing that. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 2: 6:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id E16D937B850; Wed, 23 Feb 2000 02:06:33 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id LAA17795; Wed, 23 Feb 2000 11:01:39 +0100 (CET) (envelope-from asmodai) Date: Wed, 23 Feb 2000 11:01:39 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Cc: dillon@freebsd.org, diablo-list@list.bart.nl Subject: Re: Panic (pmap) Message-ID: <20000223110139.D17129@lucifer.bart.nl> Reply-To: freebsd-current@freebsd.org References: <20000223100101.B17129@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223100101.B17129@lucifer.bart.nl>; from asmodai@bart.nl on Wed, Feb 23, 2000 at 10:01:01AM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000223 10:01], Jeroen Ruigrok van der Werven (asmodai@bart.nl) wrote: >And I may welcome panic #6 here. > >db> trace >pmap_remove_all(5a3e000,c061ab70,0,c0230ac0,d62a2f8c) at >pmap_remove_all+0x40 >pmap_page_protect(5a3e000,0) at pmap_page_protect+0xde >vm_pageout_page_stats(0) at vm_pageout_page_stats+0x15e >vm_pageout(0) at vm_pageout+0x1fb >fork_trampoline() at fork_trampoline+0x8 [root@tyr] (1) # cd /var/crash/ /var/crash [root@tyr] (2) # gdb -k /kernel.debug vmcore.2 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2625536 initial pcb at 21c9e0 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01cdefc stack pointer = 0x10:0xd62a2f44 frame pointer = 0x10:0xd62a2f50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (pagedaemon) interrupt mask = net bio cam panic: from debugger panic: from debugger Uptime: 11h59m1s amrd0: still open, can't shutdown dumping to dev #da/0x20001, offset 524312 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 ! 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc01244e1 in db_panic (addr=-1071849732, have_addr=0, count=-1, modif=0xd62a2db0 "") at ../../ddb/db_command.c:433 #3 0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c, aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333 #4 0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc012665f in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xc01c4ec5 in kdb_trap (type=12, code=0, regs=0xd62a2f04) at ../../i386/i386/db_interface.c:158 #7 0xc01d0c38 in trap_fatal (frame=0xd62a2f04, eva=0) at ../../i386/i386/trap.c:919 #8 0xc01d0911 in trap_pfault (frame=0xd62a2f04, usermode=0, eva=0) at ../../i386/i386/trap.c:817 #9 0xc01d04c3 in trap (frame={tf_fs = -701890544, tf_es = -1071906800, tf_ds = 16, tf_edi = 0, tf_esi = -1061788720, tf_ebp = -701878448, tf_isp = -701878480, tf_ebx = -1059687328, tf_edx = 0, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1071849732, tf_cs = 8, tf_eflags = 66118, tf_esp = 94625792, tf_ss = 0}) at ../../i386/i386/trap.c:423 #10 0xc01cdefc in pmap_remove_all (pa=94625792) at machine/cpufunc.h:304 #11 0xc01cf146 in pmap_page_protect (phys=94625792, prot=0) at ../../i386/i386/pmap.c:3141 #12 0xc01ad952 in vm_pageout_page_stats () at ../../vm/vm_page.h:451 #13 0xc01adc77 in vm_pageout () at ../../vm/vm_pageout.c:1341 #14 0xc01c57e0 in fork_trampoline () Cannot access memory at address 0x8000. Of course, hints and tips are welcome. Current score: 1 tcp panic 1 pmap panic 4 ffs panics 4.0-CURRENT-27-Feb Diablo 1.27 amr array at /news/spool rest is da disks on a 2940U2W onboard controller -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 2: 8: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from stargate.iss.com.tw (stargate.iss.com.tw [210.68.99.1]) by hub.freebsd.org (Postfix) with ESMTP id CF2E137B921 for ; Wed, 23 Feb 2000 02:07:43 -0800 (PST) (envelope-from urania@iss.com.tw) Received: from stargate.iss.com.tw (root@localhost) by stargate.iss.com.tw with ESMTP id SAA21015 for ; Wed, 23 Feb 2000 18:09:54 +0800 (CST) Received: from iss.com.tw (mail.iss.com.tw [172.16.6.97]) by stargate.iss.com.tw with SMTP id SAA21011 for ; Wed, 23 Feb 2000 18:09:54 +0800 (CST) Received: (qmail 28351 invoked by uid 1001); 23 Feb 2000 09:56:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Feb 2000 09:56:39 -0000 Date: Wed, 23 Feb 2000 17:56:39 +0800 (CST) From: User URANIA To: freebsd-current@freebsd.org Subject: Problem with IBM Netfinity 5000 Server (with dmesg) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for sending you all the messages from /var/log/messages, here is dmesg as the NIC at 5th PCI slot, Sorry for I cannot got dmesg as the NIC at 4th PCI slot, server reboot and I lost every things .... Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Feb 23 13:56:44 CST 2000 root@www.securenet.com.tw:/usr/src/sys/compile/www Calibrating clock(s) ... TSC clock: 498602083 Hz, i8254 clock: 1193024 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 498670656 Hz CPU: Pentium III/Pentium III Xeon (498.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536854528 (524272K bytes) Physical memory chunk(s): 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) 0x0031c000 - 0x1fff3fff, 533561344 bytes (130264 pages) avail memory = 517894144 (505756K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd5d0 bios32: Entry = 0xfd5e1 (c00fd5e1) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xd61c pnpbios: Found PnP BIOS data at 0xc00fde90 pnpbios: Entry = f0000:497d Rev = 1.0 Other BIOS signatures found: ACPI: 000fdec0 Preloaded elf kernel "kernel" at 0xc0303000. Pentium Pro MTRR support enabled Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x00000070 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) pcib0: on motherboard found-> vendor=0x1166, dev=0x0007, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 00000000, size 0 found-> vendor=0x1166, dev=0x0005, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base febff000, size 12 map[14]: type 1, range 32, base 00002000, size 5 map[18]: type 1, range 32, base fea00000, size 20 found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00002200, size 8 map[14]: type 1, range 32, base febfe000, size 12 found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=10 map[10]: type 1, range 32, base 00002300, size 8 map[14]: type 1, range 32, base febfd000, size 12 found-> vendor=0x1022, dev=0x2000, revid=0x36 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 00002020, size 5 map[14]: type 1, range 32, base febfcc00, size 5 found-> vendor=0x5333, dev=0x8901, revid=0x16 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x1166, dev=0x0200, revid=0x4d class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0210, revid=0x4a class=01-01-ea, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 map[18]: type 1, range 32, base 00000010, size 3 map[1c]: type 1, range 32, base 00000000, size 2 map[20]: type 1, range 32, base 0000ffa0, size 4 found-> vendor=0x1166, dev=0x0220, revid=0x04 class=0c-03-10, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base ff700000, size 12 pci0: on pcib0 fxp0: port 0x2000-0x201f mem 0xfea00000-0xfeafffff,0xfebff000-0xfebfffff irq 11 at device 1.0 on pci0 fxp0: Ethernet address 00:04:ac:45:75:fc bpf: fxp0 attached ahc0: port 0x2200-0x22ff mem 0xfebfe000-0xfebfefff irq 15 at device 6.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 389 instructions downloaded ahc1: port 0x2300-0x23ff mem 0xfebfd000-0xfebfdfff irq 10 at device 6.1 on pci0 ahc1: Reading SEEPROM...done. ahc1: Low byte termination Enabled ahc1: High byte termination Enabled ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Downloading Sequencer Program... 389 instructions downloaded lnc0: port 0x2020-0x203f mem 0xfebfcc00-0xfebfcc1f irq 11 at device 9.0 on pci0 lnc0: PCnet-FAST+ address 00:06:29:39:16:e0 bpf: lnc0 attached using shared irq11. lnc0: driver is using old-style compatability shims pci0: (vendor=0x5333, dev=0x8901) at 10.0 irq 9 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0-0x3,0x10-0x17,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at device 15.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: (vendor=0x1166, dev=0x0220) at 15.2 irq 10 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) pcib1: on motherboard pci1: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 devclass_alloc_unit: lnc0 already exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0045 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 00 00 64 psm: data ffffffff 00 64 psm: status 00 02 64 psm: data ffffffff 02 64 psm0: failed to get data. psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:00, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: SPP ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 2:0223fe3f 0..547=548 cylinders, 0..254=255 heads, 1..63=63 sectors 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 16 packets/entry by default bpf: lo0 attached ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata0-master: success setting up PIO4 mode on generic chip acd0: MODE_SENSE_BIG command timeout - resetting ata0: resetting devices .. ata0: mask=01 status0=00 status1=00 done acd0: read data overrun 28/2 acd0: CDROM drive at ata0 as master acd0: read 500KB/s (10517KB/s), 1792KB buffer, PIO4 acd0: Reads: CD-RW acd0: Mechanism: caddy acd0: Medium: CD-ROM 120mm audio disc loaded (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc1: target 4 using 16bit transfers ahc1: target 4 synchronous at 5.7MHz, offset = 0x8 ahc1: target 0 using 16bit transfers ahc1: target 0 synchronous at 5.7MHz, offset = 0x8 ahc1: target 1 using 16bit transfers ahc1: target 1 synchronous at 5.7MHz, offset = 0x8 ahc0: target 5 using 16bit transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 Creating DISK da3 Creating DISK da0 Creating DISK da1 Creating DISK da2 pass0 at ahc0 bus 0 target 5 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number \^_ pass0: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass1 at ahc1 bus 0 target 0 lun 0 pass1: Fixed Direct Access SCSI-3 device pass1: Serial Number AJ1EP186 pass1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass2 at ahc1 bus 0 target 1 lun 0 pass2: Fixed Direct Access SCSI-3 device pass2: Serial Number AJ1J7486 pass2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass3 at ahc1 bus 0 target 4 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number RD4C8750 pass3: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled pass4 at ahc1 bus 0 target 14 lun 0 pass4: Fixed Processor SCSI-2 device pass4: Serial Number 1 pass4: 3.300MB/s transfers pass4 at ahc1 bus 0 target 14 lun 0 pass4: Fixed Processor SCSI-2 device pass4: Serial Number 1 pass4: 3.300MB/s transfers da3 at ahc0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number \^_ da3: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 61208MB (125353984 512 byte sectors: 255H 63S/T 7802C) Mounting root from ufs:/dev/da0s1a da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Serial Number AJ1J7486 da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number AJ1EP186 da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da0s1: type 0xa5, start 63, end = 401624, size 401562 : OK da0s2: type 0xa5, start 401625, end = 2490074, size 2088450 : OK da0s3: type 0xa5, start 2490075, end = 17767889, size 15277815 : OK da2 at ahc1 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number RD4C8750 da2: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) WARNING: / was not properly dismounted start_init: trying /sbin/init da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK ahc0: target 5 using asynchronous transfers ahc0: target 5 synchronous at 5.0MHz, offset = 0x8 da3s1: type 0xa5, start 63, end = 125339129, size 125339067 : OK da2s1: type 0xa5, start 63, end = 8803619, size 8803557 : OK lnc0: Device timeout -- Resetting Linux-ELF exec handler installed splash: image decoder found: blank_saver pid 254 (snpserv), uid 0: exited on signal 11 (core dumped) (da0:ahc1:0:0:0): tagged openings now 64 Here comes my kernel config file machine i386 cpu I686_CPU options NO_F00F_HACK ident www maxusers 32 options NMBCLUSTERS=2048 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options QUOTA #enable disk quotas #options NSWAPDEV=20 # Allow this many swap-devices. options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa0 #device pnp0 # PnP support for ISA device pci0 # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives #options ATA_ENABLE_ATAPI_DMA #controller wdc0 at isa? port IO_WD1 irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 # SCSI Controllers #device ahc device ahc0 # AHA2940 and onboard AIC7xxx devices device ahc1 # Netfinity 5000 support two channels # SCSI peripherals # because Netfinity 5000 ahc0 attaches to external usage, and ahc1 attaches # to internal usage, we cannot change it .... ><# device scbus0 at ahc0 bus0 device scbus1 at ahc1 bus0 device da0 at scbus1 target 0 unit 0 device da1 at scbus1 target 1 unit 0 device da2 at scbus1 target 4 unit 0 # Next device entry is for external RAID usage, you must modify it to # match realy world configure. device da3 at scbus0 target 5 unit 0 device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x31 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 device ppbus0 # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel device ppi # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) # ISA Ethernet NICs. device lnc0 at isa? port 0x280 irq 10 drq 0 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse options SOFTUPDATES options MD5 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #pseudo-device vinum #Vinum concat/mirror/raid driver options SC_DISABLE_REBOOT # disable reboot key sequence options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=16 # end of WWW Server config file I also set these flags at my /etc/make.conf # CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations # # To avoid building various parts of the base system: NO_SENDMAIL= true #NO_CVS= true # # To compile just the kernel with special optimisations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway): # COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 3:37:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E02537B7F0 for ; Wed, 23 Feb 2000 03:37:28 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id MAA16364; Wed, 23 Feb 2000 12:00:24 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id WAA02295; Tue, 22 Feb 2000 22:31:49 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 22:31:49 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: thanks for your nice help ! (was Re: timeout problems ....) Message-ID: <20000222223149.A2237@titan.klemm.gtn.com> References: <20000222184929.A2934@titan.klemm.gtn.com> <200002222115.WAA79494@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002222115.WAA79494@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 10:15:42PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 10:15:42PM +0100, Soren Schmidt wrote: > There are two posibilities, either the cable is bad or the disk is bad. > Since you could talk to it, and you didn't get ICRC errors, my bet is > that the particular Maxtor model is just as broken as most of its > other family memebers :( Hmm, too bad. But o.k. actually it's working now and a big thanks for your kind support !!! -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 3:44:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 129AD37B6F7; Wed, 23 Feb 2000 03:44:17 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Feb 2000 11:20:07 +0000 (GMT) Date: Wed, 23 Feb 2000 11:20:07 +0000 From: David Malone To: freebsd-current@freebsd.org Cc: dillon@freebsd.org, diablo-list@list.bart.nl Subject: Re: Panic (pmap) Message-ID: <20000223112007.A35612@walton.maths.tcd.ie> References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223110139.D17129@lucifer.bart.nl>; from asmodai@bart.nl on Wed, Feb 23, 2000 at 11:01:39AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 11:01:39AM +0100, Jeroen Ruigrok van der Werven wrote: > Current score: > > 1 tcp panic > 1 pmap panic > 4 ffs panics Such a mix might suggests bad hardware? (Mind you, we're seeing "freeing free block" panics on a NFS server with full disks on 3.4). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 3:48:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 4FAD237B7DF for ; Wed, 23 Feb 2000 03:48:15 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id MAA19744 for current@FreeBSD.ORG; Wed, 23 Feb 2000 12:45:24 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id MAA06249 for current@FreeBSD.ORG; Wed, 23 Feb 2000 12:19:29 +0100 (CET) (envelope-from andreas) Date: Wed, 23 Feb 2000 12:19:29 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: disklabels partition sizes differ from FreeBSDs syslog messages on mounting Message-ID: <20000223121928.A803@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I'm worried about this message and don't know if I may forget about it or not. I see a discrepany of disklabel partition sizes and those syslog messages I get, when I mount something from my 40GB EIDE disk. I did a normal FreeBSD 4.0 SNAP installation on a new 40 GB disk. On the largest filesystem I wanted to backup my old system. So I mounted now the ata disk under my SCSI environment, to do a backup. Please note: I did no manual fiddeling with disklabel or such on the EIDE disk, it was a normal installation from self burned CD and doing a custom installation. When I try to mount the largest filesystem from the EIDE disk I get these syslog messages and this worries me: ad4s1d: start 24322111, end 80035829, size 55713719 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1f: start 5447743, end 13836350, size 8388608 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1g: start 13836351, end 15933502, size 2097152 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1h: start 15933503, end 24322110, size 8388608 Look at the different partition sizes, I made a tabular, some values are equal, some greater, some less, no clear picture to me: ad4s1d: start 24322111, end 80035829, size 55713719 disklabel -r at4 value: 37075257 < ad4s1f: start 5447743, end 13836350, size 8388608 disklabel -r at4 value: 8388608 = ad4s1g: start 13836351, end 15933502, size 2097152 disklabel -r at4 value: 4194304 > ad4s1h: start 15933503, end 24322110, size 8388608 disklabel -r at4 value: 8388608 = kernel in core disklabel and on the disk are the same: This is thew exact output: disklabel -r ad4 # /dev/rad4c: type: ESDI disk: ad4s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 4217 sectors/unit: 67746105 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 262144 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 16*) b: 1048576 262144 swap # (Cyl. 16*- 81*) c: 67746105 0 unused 0 0 # (Cyl. 0 - 4216) d: 37075257 30670848 4.2BSD 1024 8192 16 # (Cyl. 1909*- 4216*) e: 8388608 1310720 4.2BSD 1024 8192 16 # (Cyl. 81*- 603*) f: 8388608 9699328 4.2BSD 1024 8192 16 # (Cyl. 603*- 1125*) g: 4194304 18087936 4.2BSD 1024 8192 16 # (Cyl. 1125*- 1387*) h: 8388608 22282240 4.2BSD 1024 8192 16 # (Cyl. 1387*- 1909*) And here for reference the output of /stand/sysinstall: Disk name: ad4 FDISK Partition Editor DISK Geometry: 4982 cyls/255 heads/63 sectors = 80035830 sectors Offset Size End Name PType Desc Subtype Flags 0 63 62 - 6 unused 0 63 12289662 12289724 ad4s1 2 fat 11 12289725 67746105 80035829 ad4s2 3 freebsd 165 C> 80035830 5418 80041247 - 6 unused 0 > And here what the kernel says: ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 Any thoughts ... should I simply install or better wait ??? ;-) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 3:58:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id E017937B64D for ; Wed, 23 Feb 2000 03:58:41 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.6] (helo=mx0.freenet.de) by mout0.freenet.de with esmtp (Exim 3.13 #1) id 12NZZT-0007Dt-00; Wed, 23 Feb 2000 12:03:07 +0100 Received: from [213.6.57.184] (helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.13 #3) id 12NZZT-0000R3-00; Wed, 23 Feb 2000 12:03:07 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id VAA11669; Tue, 22 Feb 2000 21:27:51 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200002222027.VAA11669@Magelan.Leidinger.net> Date: Tue, 22 Feb 2000 21:27:50 +0100 (CET) From: Alexander Leidinger Subject: Re: Crashing netscape? To: shocking@prth.pgs.com Cc: current@FreeBSD.ORG In-Reply-To: <200002221733.LAA27559@prg01.hstn.tensor.pgs.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Feb, Steve Hocking wrote: > There was some discussion of this over on the XFree mailing lists, and it > transpired that netscape was using a pointer to some memory that had been > freed some time back. This showed up in cases where you open up a stack of > windows and then close them at random. There was a patch to work around this > for libXt (I think). But this didn't solve the crash at exit. But... rm -rf /usr/lib/compat/* cd /usr/src/lib/compat/compat22/ make all install clean cd ../compat3x.i386/ make all install clean solved this for me (YMMV). Together with disabling Java* and using those ---snip--- Netscape*dragInitiatorProtocolStyle: XmDRAG_NONE Netscape*dragReceiverProtocolStyle: XmDRAG_NONE ---snip--- Xresources I have a more stable Netscape. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 3:59:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B8C4A37B722 for ; Wed, 23 Feb 2000 03:59:29 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12NZg2-0000Kw-00; Wed, 23 Feb 2000 13:09:54 +0200 From: Sheldon Hearn To: Thierry.Herbelot@alcatel.fr Cc: current@FreeBSD.ORG Subject: Re: can't load if_xl module at startup In-reply-to: Your message of "Mon, 21 Feb 2000 18:47:48 +0100." Date: Wed, 23 Feb 2000 13:09:53 +0200 Message-ID: <1297.951304193@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Feb 2000 18:47:48 +0100, Thierry.Herbelot@alcatel.fr wrote: > When I load the if_xl module "by hand", all is well : the miibus is > also loaded and everything's fine (xl0 appears in ifconfig -a ...) > > When I try to load the if_xl and miibus modules via the loader, the > loader spins in : I'm answering because you don't seem to have gotten any other (public) answers, not because I'm sure of my facts. Quite a few people have reported problems loading modules from the loader (different modules, mind you). I'm pretty sure that I saw a clueful person suggest loading them out of /etc/rc.local for now. I can't check the archives to validate this, so you might want to think about it more than I have. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 4: 4:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E7F637B7DF for ; Wed, 23 Feb 2000 04:04:55 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id NAA20757 for current@FreeBSD.ORG; Wed, 23 Feb 2000 13:00:21 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id MAA08125 for current@FreeBSD.ORG; Wed, 23 Feb 2000 12:58:04 +0100 (CET) (envelope-from andreas) Date: Wed, 23 Feb 2000 12:58:04 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: ad4s1: raw partition size != slice size (was Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting) Message-ID: <20000223125804.A8099@titan.klemm.gtn.com> References: <20000223121928.A803@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <20000223121928.A803@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Wed, Feb 23, 2000 at 12:19:29PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 12:19:29PM +0100, Andreas Klemm wrote: > ad4s1d: start 24322111, end 80035829, size 55713719 > ad4s1: rejecting partition in BSD label: it isn't entirely within the slice > ad4s1f: start 5447743, end 13836350, size 8388608 > ad4s1: rejecting partition in BSD label: it isn't entirely within the slice > ad4s1g: start 13836351, end 15933502, size 2097152 > ad4s1: rejecting partition in BSD label: it isn't entirely within the slice > ad4s1h: start 15933503, end 24322110, size 8388608 After mounting every new filesystem I even get these messages: (after adding fstab and mount -at ufs): ad4s1: raw partition size != slice size ad4s1: start 63, end 12289724, size 12289662 ad4s1c: start 63, end 80035829, size 80035767 ad4s1: truncating raw partition ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1: start 63, end 12289724, size 12289662 ad4s1d: start 24322111, end 80035829, size 55713719 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1f: start 5447743, end 13836350, size 8388608 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1g: start 13836351, end 15933502, size 2097152 ad4s1: rejecting partition in BSD label: it isn't entirely within the slice ad4s1h: start 15933503, end 24322110, size 8388608 # Device Mountpoint FStype Options Dump Pass# /dev/ad4s2a /new ufs rw 1 2 /dev/ad4s2e /new/var ufs rw 1 2 /dev/ad4s2f /new/usr ufs rw 1 2 /dev/ad4s2g /new/internet ufs rw 1 2 /dev/ad4s2h /new/home ufs rw 1 2 /dev/ad4s2d /new/data ufs rw 1 2 # /dev/rad4c: type: ESDI disk: ad4s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 4217 sectors/unit: 67746105 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 262144 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 16*) b: 1048576 262144 swap # (Cyl. 16*- 81*) c: 67746105 0 unused 0 0 # (Cyl. 0 - 4216) d: 37075257 30670848 4.2BSD 1024 8192 16 # (Cyl. 1909*- 4216*) e: 8388608 1310720 4.2BSD 1024 8192 16 # (Cyl. 81*- 603*) f: 8388608 9699328 4.2BSD 1024 8192 16 # (Cyl. 603*- 1125*) g: 4194304 18087936 4.2BSD 1024 8192 16 # (Cyl. 1125*- 1387*) h: 8388608 22282240 4.2BSD 1024 8192 16 # (Cyl. 1387*- 1909*) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 4:30: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 6A31D37B780 for ; Wed, 23 Feb 2000 04:29:52 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 18529 invoked from network); 23 Feb 2000 12:29:49 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 23 Feb 2000 12:29:49 -0000 Date: Wed, 23 Feb 2000 23:29:44 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Martin Cracauer Cc: jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG, dillon@apollo.backplane.com, obrien@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) In-Reply-To: <20000223100036.A4872@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, Martin Cracauer wrote: > cc -fpic -DPIC -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/stdtime/localtime.c -o localtime.So > {standard input}: Assembler messages: > {standard input}:87: Warning: warning: unrecognized characters > `@GOTOFF' in expression > {standard input}:114: Warning: warning: unrecognized characters > `@GOTOFF' in expression > I'm not that familar with gas syntax, but it seems to be that this is > a syntax error generated by the new gcc, that @GOTOFF must be passed > one argument. The syntax seems reasonable, but our version of gas doesn't support it, and it is the result of a pessimisation. I tweaked the source code to avoid the bad code: diff -c2 localtime.c~ localtime.c *** localtime.c~ Fri Jan 28 17:29:18 2000 --- localtime.c Wed Feb 23 22:51:34 2000 *************** *** 220,224 **** settzname P((void)) { ! register struct state * const sp = lclptr; register int i; --- 220,224 ---- settzname P((void)) { ! register struct state * sp = lclptr; register int i; This seems to fix some of your prooblems. It works as follows: when sp is declared as const, gcc decides not to keep in a register in the default !ALL_STATE case (lclptr is &lclmem in this case), since it can "easily" be recovered by computing the address constant &lclmem. However, computing the constant turns out to be not so easy in the -fpic case -- it takes an extra 8 instructions, including a pessimization which gives the bug. (The natural and efficient way to reload lclptr (plus an offset) is: leal offset+lclmem@GOTOFF(%ebx),%reg but for some reason this sometimes gets pessimized to essentially: movl %ebx,%reg addl offset+lclmem@GOTOFF,%reg The last instruction is a syntax error with the current gas.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 4:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B3D5F37B863 for ; Wed, 23 Feb 2000 04:43:47 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA08755; Wed, 23 Feb 2000 23:47:48 +1100 Date: Wed, 23 Feb 2000 23:43:32 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting In-Reply-To: <20000223121928.A803@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, Andreas Klemm wrote: > I'm worried about this message and don't know if I may forget about > it or not. I see a discrepany of disklabel partition sizes and those > syslog messages I get, when I mount something from my 40GB EIDE disk. Old systems don't support 40GB disks (except in LBA mode, which is broken in other ways). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 4:44:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id BD53537B845 for ; Wed, 23 Feb 2000 04:44:55 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id B6FAF12328 for ; Wed, 23 Feb 2000 13:44:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Wed, 23 Feb 2000 13:44:09 +0100 To: freebsd-current@freebsd.org From: Brad Knowles Subject: Union semun defined in /usr/include/sys/sem.h? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I've run into a problem compiling bonnie++ 0.99f and 3.4-STABLE. Normally, I would ask a question about this on the -stable list, but from discussions with the author, it's my understanding that this will probably be fixed in the next revision of the code. However, this has brought up an interesting question. It is my understanding that X/Open requires that this union be defined within the client source code (which is why Russell is going to fix his code), and not within standard system headers. However, looking in this file under 3.2-RELEASE and 3.4-STABLE, I find that FreeBSD does go ahead and define this object. Is this changed in -CURRENT? If not, are there any plans to change it in -CURRENT? Or has the X/Open standard changed, and FreeBSD is following the new standard in this area? My understanding is that the other BSDs follow the X/Open standard, as does Linux. I'm trying to understand why FreeBSD is different in this regard. I'm also curious to know why there is a difference in how this object is defined under Linux and FreeBSD. Linux apparently defines it like so: union semun { int val; /* value for SETVAL */ struct semid_ds *buf; /* buffer for IPC_STAT, IPC_SET */ unsigned short int *array; /* array for GETALL, SETALL */ struct seminfo *__buf; /* buffer for IPC_INFO */ }; #endif Whereas looking in /usr/include/sys/sem.h, FreeBSD defines it like so: union semun { int val; /* value for SETVAL */ struct semid_ds *buf; /* buffer for IPC_STAT & IPC_SET */ u_short *array; /* array for GETALL & SETALL */ }; At the end of the day, I'm just trying to get a working bonnie++. However, I'm also interested as to who is "right" on this issue, and more importantly, why they are "right". Thanks! -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 5: 6:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 6DBAC37B880 for ; Wed, 23 Feb 2000 05:06:32 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id NAA19352; Wed, 23 Feb 2000 13:58:43 +0100 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id OAA29051; Wed, 23 Feb 2000 14:00:31 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C125688E.0047FBB8 ; Wed, 23 Feb 2000 14:06:14 +0100 X-Lotus-FromDomain: ALCATEL To: Sheldon Hearn Cc: current@FreeBSD.ORG Message-ID: Date: Wed, 23 Feb 2000 14:01:48 +0100 Subject: Re: can't load if_xl module at startup Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Well, this is exactly what I've conluded : don't use the loader for now (I've recompiled my kernel). I had a mail exchange with Mike Smith (on -Current) and I told him I would very much like to have a committer add a comment in /boot/loader.conf telling newbies about with little problem (don't know if I was heard) TfH Sheldon Hearn on 23/02/2000 12:09:53 To: Thierry HERBELOT/FR/ALCATEL@ALCATEL cc: current@FreeBSD.ORG Subject: Re: can't load if_xl module at startup On Mon, 21 Feb 2000 18:47:48 +0100, Thierry.Herbelot@alcatel.fr wrote: > When I load the if_xl module "by hand", all is well : the miibus is > also loaded and everything's fine (xl0 appears in ifconfig -a ...) > > When I try to load the if_xl and miibus modules via the loader, the > loader spins in : I'm answering because you don't seem to have gotten any other (public) answers, not because I'm sure of my facts. Quite a few people have reported problems loading modules from the loader (different modules, mind you). I'm pretty sure that I saw a clueful person suggest loading them out of /etc/rc.local for now. I can't check the archives to validate this, so you might want to think about it more than I have. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 5:31:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (nebula.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 81B2E37B6F7; Wed, 23 Feb 2000 05:31:11 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id OAA06063; Wed, 23 Feb 2000 14:31:01 +0100 (CET) Date: Wed, 23 Feb 2000 14:31:01 +0100 From: Martin Cracauer To: Bruce Evans Cc: Martin Cracauer , jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000223143101.A5971@cons.org> References: <20000223100036.A4872@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Wed, Feb 23, 2000 at 11:29:44PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Bruce Evans wrote: > diff -c2 localtime.c~ localtime.c > *** localtime.c~ Fri Jan 28 17:29:18 2000 > --- localtime.c Wed Feb 23 22:51:34 2000 > *************** > *** 220,224 **** > settzname P((void)) > { > ! register struct state * const sp = lclptr; > register int i; > > --- 220,224 ---- > settzname P((void)) > { > ! register struct state * sp = lclptr; > register int i; > > This seems to fix some of your prooblems. > > It works as follows: when sp is declared as const, gcc decides not to > keep in a register in the default !ALL_STATE case (lclptr is &lclmem in > this case), since it can "easily" be recovered by computing the address > constant &lclmem. However, computing the constant turns out to be not > so easy in the -fpic case -- it takes an extra 8 instructions, including > a pessimization which gives the bug. My initial next question would be how this bad code in localtime.c can affect straight references from the calling program to the symbol tzname[] without calling code in localtime. And why write accesses succeed and read accesses fail. Looking on the assembler code, I guess that the wrong code in localtime.c leave a wrong value in %ecx, why is used as a base address by rtld. Once the wrong code is called, the symbol table is messed up. However, some calls such as the write test in my shlibs3 example still succeed because the compiler saved/cached the address from a previous call (which he is allowed to since the address is constant). Once the code goes through normal rtld lookup again, it bombs. Right? I am not sure how harmless this bug is. `make world` output shows that the as warning message only occurs in localtime.c. I think a workaround might be to fix as you suggest and turn the assembler warning into an error, although in that case users might not be able to compile valid code into shared libraries. Where's the bug, anyway? Do we need to fix the compiler or would it be better to get a newer assembler? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 5:37:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AC4CB37B85A for ; Wed, 23 Feb 2000 05:37:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA82728; Wed, 23 Feb 2000 14:37:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002231337.OAA82728@freebsd.dk> Subject: Re: thanks for your nice help ! (was Re: timeout problems ....) In-Reply-To: <20000222223149.A2237@titan.klemm.gtn.com> from Andreas Klemm at "Feb 22, 2000 10:31:49 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Wed, 23 Feb 2000 14:37:23 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Andreas Klemm wrote: > On Tue, Feb 22, 2000 at 10:15:42PM +0100, Soren Schmidt wrote: > > There are two posibilities, either the cable is bad or the disk is bad. > > Since you could talk to it, and you didn't get ICRC errors, my bet is > > that the particular Maxtor model is just as broken as most of its > > other family memebers :( > > Hmm, too bad. But o.k. actually it's working now and a big > thanks for your kind support !!! You're welcome :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 5:58:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id A445C37B6F7; Wed, 23 Feb 2000 05:58:21 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id IAA25553; Wed, 23 Feb 2000 08:58:17 -0500 (EST) Received: from njb140bh2.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id IAA11040; Wed, 23 Feb 2000 08:57:38 -0500 (EST) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Feb 2000 08:58:17 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'David Malone'" , Archie Cobbs Cc: julian@elischer.org, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: NETGRAPH patches (proposal) CONT. Date: Wed, 23 Feb 2000 08:58:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Feb 22, 2000 at 09:02:43PM -0800, Archie Cobbs wrote: > > > > It's because all packets sent by this node should have the node's > > > address. If you don't have it then PPPoE cannot send a > packet "FROM" > > > thia node, as it has no idea of what this node's address is. > > > > So.. we can have two hooks, one that sets the host address and > > one that doesn't.. :-) > > In that case can we have one that also sets the destination address > via arp? > i added new control message for ``ngether_node''. i called it NGEF_RAW_MODE. now you can set it to on/off by using NgSendMsg. ``ngether_rcvdata'' will not update ``ether_shost'' if it set to on. otherwise it will. patches available at http://home.earthlink.net/~evmax/ng.tar.gz these are against -current cvsup'ed this sunday around 8:30pm EST. it also includes small test program based ion ``nghook''. Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 6: 7: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 81A2937B8CE for ; Wed, 23 Feb 2000 06:06:58 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 07FB6137FBA for ; Wed, 23 Feb 2000 09:06:57 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id JAA25312; Wed, 23 Feb 2000 09:07:15 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14515.59795.632514.748870@trooper.velocet.net> Date: Wed, 23 Feb 2000 09:07:15 -0500 (EST) To: freebsd-current@freebsd.org Subject: Re: Wierd AMD panics caused by VMWare? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had reported this earlier, but the similarities are striking: I too have seen strange AMD panics where stack variables inexplicably go to zero. My systems are K6/2-400's, and I have often witnessed the following fault (only happens on a *really* busy web server) #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc014aad1 in panic (fmt=0xc023878a "page fault") at ../../kern/kern_shutdown.c:446 #2 0xc02098ce in trap_fatal (frame=0xcc74eecc, eva=134812896) at ../../i386/i386/trap.c:942 #3 0xc0209587 in trap_pfault (frame=0xcc74eecc, usermode=0, eva=134812896) at ../../i386/i386/trap.c:835 #4 0xc02091ba in trap (frame={tf_es = -887750640, tf_ds = -1036058608, tf_edi = -1050208512, tf_esi = -1043943040, tf_ebp = -864751828, tf_isp = -864751884, tf_ebx = 2287, tf_edx = -1036043576, tf_ecx = 0, tf_eax = 134812884, tf_trapno = 12, tf_err = 2, tf_eip = -1072417321, tf_cs = 8, tf_eflags = 66054, tf_esp = -1041509376, tf_ss = -1036024832}) at ../../i386/i386/trap.c:437 #5 0xc01435d7 in fdcopy (p=0xcc5796e0) at ../../kern/kern_descrip.c:954 #6 0xc014587b in fork1 (p1=0xcc5796e0, flags=-2147483596) at ../../kern/kern_fork.c:379 #7 0xc014533b in vfork (p=0xcc5796e0, uap=0xcc74ef94) at ../../kern/kern_fork.c:109 #8 0xc0209b17 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 236237520, tf_esi = 236231856, tf_ebp = -1077952324, tf_isp = -864751644, tf_ebx = 673171048, tf_edx = 163766316, tf_ecx = 672877149, tf_eax = 66, tf_trapno = 7, tf_err = 2, tf_eip = 672936705, tf_cs = 31, tf_eflags = 514, tf_esp = -1077952368, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #9 0xc01feedc in Xint0x80_syscall () Now the interesting code here is at stack from #5: (kgdb) list 948 fpp = newfdp->fd_ofiles; 949 for (i = newfdp->fd_lastfile; i-- >= 0; fpp++) 950 if (*fpp != NULL) 951 (*fpp)->f_count++; (kgdb) p newfdp->fd_ofiles $1 = (struct file **) 0xc23f2000 (kgdb) p fpp $2 = (struct file **) 0x0 Now... the only operation on fpp is fpp++. It should take a _long_ time for fpp to get around to 0 and you'd thing that *fpp would be zero long before that (or cause a page fault at some other non-existant location). So... the similarity here is that deep in the kernel, we have a automatic (possibly register) local variable that's getting zero'd. I have half-a-dozen crash dumps of this nature. For me, it always happens in fdcopy(). This may be due to the fact that the machine is running a large apache config --- so fork() is something it's doing often. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 6:15:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from Kirk.NetUnlimited.net (Kirk.netunlimited.net [208.128.132.1]) by hub.freebsd.org (Postfix) with ESMTP id E602137B8EA for ; Wed, 23 Feb 2000 06:15:45 -0800 (PST) (envelope-from arc@twinds.com) Received: from seahawk.twinds.com (seahawk.twinds.com [208.165.2.226]) by Kirk.NetUnlimited.net (8.9.3/8.9.3) with ESMTP id JAA06129 for ; Wed, 23 Feb 2000 09:19:16 -0500 (EST) Date: Wed, 23 Feb 2000 09:13:47 -0500 (EST) From: Arley Carter To: FreeBSD-current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 6:30:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 1CD2437B722 for ; Wed, 23 Feb 2000 06:30:32 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id PAA00822; Wed, 23 Feb 2000 15:30:11 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id PAA03509; Wed, 23 Feb 2000 15:21:30 +0100 (CET) (envelope-from andreas) Date: Wed, 23 Feb 2000 15:21:30 +0100 From: Andreas Klemm To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting Message-ID: <20000223152130.A1583@titan.klemm.gtn.com> References: <20000223121928.A803@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Wed, Feb 23, 2000 at 11:43:32PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 11:43:32PM +1100, Bruce Evans wrote: > On Wed, 23 Feb 2000, Andreas Klemm wrote: > > I'm worried about this message and don't know if I may forget about > > it or not. I see a discrepany of disklabel partition sizes and those > > syslog messages I get, when I mount something from my 40GB EIDE disk. > > Old systems don't support 40GB disks (except in LBA mode, which is > broken in other ways). Hi Bruce, what do you mean exactly with "old systems" ? Correct me if I'm wrong, but I don't "old hardware", since I have a *brand new* EIDE controller (Abit) which _is_ capable of recognizing the 40 GB harddisk. Please look here: FreeBSD is able to detect the drive in it's full size, kernel message: ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 79406*16*63= 80041248 sectors FreeBSD offers during installation to use a more clever partitioning scheme (sector translation). The values seem reasonable for me: Systinstall displays in the first line: 4982 cyls/255 heads/63 sectors = 80035830 sectors 4982*255*63= 80035830 which is smaller than the total sector size of the drive (80041248) Disklabel also has reasonable entries: sectors/track: 63 tracks/cylinder: 255 cylinders: 4217 sectors/unit: 67746105 255*63*4217= 67746105 which should be the size of my FreeBSD slice Could you please be more verbose on what's going wrong in your opineon ? I assume you might have missed the point, that I use a brand new EIDE controller and turned off on board IDE ... Anyway, thanks for your answer Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 6:36:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 011C437B8C5; Wed, 23 Feb 2000 06:36:31 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id PAA21449; Wed, 23 Feb 2000 15:36:29 +0100 (CET) (envelope-from asmodai) Date: Wed, 23 Feb 2000 15:36:29 +0100 From: Jeroen Ruigrok van der Werven To: freebsd-current@freebsd.org Cc: freebsd-fs@freebsd.org, mckusick@freebsd.org Subject: Panic #3 (ffs) Message-ID: <20000223153629.H18964@lucifer.bart.nl> Reply-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *sigh* I think I am going to give up my job and become a buddhist monk... start = 0, len = 2646, fs = /news panic: ffs_alloccg: map corrupted Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.372 db> trace Debugger(c01e7ee3) at Debugger+0x35 panic(c01f28bf,c01f28a0,0,a56,c1d0d8d4) at panic+0x70 ffs_mapsearch(c1d0d800,ccd49000,5d2a8,1,b) at ffs_mapsearch+0x143 ffs_alloccg(c1da7700,b,5d2a8,400) at ffs_alloccg+0x21a ffs_hashalloc(c1da7700,b,5d2a8,400,c0194cb8) at ffs_hashalloc+0x23 ffs_alloc(c1da7700,b,5d2a8,400,c1d38280) at ffs_alloc+0xad ffs_balloc(d8a1ce68,d8a4c200,c1d6a180,3,d8b74ba0) at ffs_balloc+0x456 ffs_write(d8a1cea0,d6299a80,4c,c1d6a180,c0201d00) at ffs_write+0x319 vn_write(c1d6a180,d8a1ceec,c1d38280,0,d6299a80) at vn_write+0xda dofilewrite(d6299a80,c1d6a180,18,280c4000,4c) at dofilewrite+0x91 write(d6299a80,d8a1cf80,280ad140,280ad140,280c404d) at write+0x33 syscall(280c002f,280a002f,bfbf002f,280c404d,280ad140) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 7:16: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by hub.freebsd.org (Postfix) with ESMTP id 94E6D37B89E; Wed, 23 Feb 2000 07:15:52 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-20-228.nv.iinet.net.au [203.59.85.228]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id XAA21454; Wed, 23 Feb 2000 23:14:17 +0800 Message-ID: <38B3F8FC.2781E494@elischer.org> Date: Wed, 23 Feb 2000 07:13:00 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: David Malone Cc: Archie Cobbs , myevmenkin@att.com, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NETGRAPH patches (proposal) References: <38B34BBA.41C67EA6@elischer.org> <200002230502.VAA84742@bubba.whistle.com> <20000223085750.A29008@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > > On Tue, Feb 22, 2000 at 09:02:43PM -0800, Archie Cobbs wrote: > > > > It's because all packets sent by this node should have the node's > > > address. If you don't have it then PPPoE cannot send a packet "FROM" > > > thia node, as it has no idea of what this node's address is. > > > > So.. we can have two hooks, one that sets the host address and > > one that doesn't.. :-) > > In that case can we have one that also sets the destination address > via arp? Now I think you are talking a separate node that implements such a protocol. > > David. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 7:53:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 5E04037B857 for ; Wed, 23 Feb 2000 07:53:43 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id HAA16102; Wed, 23 Feb 2000 07:53:37 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id HAA03693; Wed, 23 Feb 2000 07:53:06 -0800 (PST) Message-ID: <38B40262.FC4EEDD0@quack.kfu.com> Date: Wed, 23 Feb 2000 15:53:06 +0000 From: Nick Sayer X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: David Gilbert , freebsd-current@freebsd.org Subject: Re: Wierd AMD panics caused by VMWare? References: <14515.59795.632514.748870@trooper.velocet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only thing I would add is that by AMD I didn't mean Advanced Micro Devices. I meant /usr/sbin/amd. In my case this behavior has been observed on a Pentium III and on a K7, so it's CPU independent. David Gilbert wrote: > > I had reported this earlier, but the similarities are striking: > > I too have seen strange AMD panics where stack variables inexplicably > go to zero. My systems are K6/2-400's, and I have often witnessed the > following fault (only happens on a *really* busy web server) The common denominator seems to be that the machine has to be very active. VMware stresses the vm system quite a bit (64M of shared memory with multiple processes digging around, etc). A very busy web server is going to do a lot of context switching (I think?). In that situation, it appears that the stack is being smashed. I tried insulating the code where my machines go nuts inside of splhigh() / splx(), but it didn't help. Is your machine running the automounter? > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 > #1 0xc014aad1 in panic (fmt=0xc023878a "page fault") > at ../../kern/kern_shutdown.c:446 > #2 0xc02098ce in trap_fatal (frame=0xcc74eecc, eva=134812896) > at ../../i386/i386/trap.c:942 > #3 0xc0209587 in trap_pfault (frame=0xcc74eecc, usermode=0, eva=134812896) > at ../../i386/i386/trap.c:835 > #4 0xc02091ba in trap (frame={tf_es = -887750640, tf_ds = -1036058608, > tf_edi = -1050208512, tf_esi = -1043943040, tf_ebp = -864751828, > tf_isp = -864751884, tf_ebx = 2287, tf_edx = -1036043576, tf_ecx = 0, > tf_eax = 134812884, tf_trapno = 12, tf_err = 2, tf_eip = -1072417321, > tf_cs = 8, tf_eflags = 66054, tf_esp = -1041509376, tf_ss = -1036024832}) > at ../../i386/i386/trap.c:437 > #5 0xc01435d7 in fdcopy (p=0xcc5796e0) at ../../kern/kern_descrip.c:954 > #6 0xc014587b in fork1 (p1=0xcc5796e0, flags=-2147483596) > at ../../kern/kern_fork.c:379 > #7 0xc014533b in vfork (p=0xcc5796e0, uap=0xcc74ef94) > at ../../kern/kern_fork.c:109 > #8 0xc0209b17 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 236237520, > tf_esi = 236231856, tf_ebp = -1077952324, tf_isp = -864751644, > tf_ebx = 673171048, tf_edx = 163766316, tf_ecx = 672877149, tf_eax = 66, > tf_trapno = 7, tf_err = 2, tf_eip = 672936705, tf_cs = 31, > tf_eflags = 514, tf_esp = -1077952368, tf_ss = 39}) > at ../../i386/i386/trap.c:1100 > #9 0xc01feedc in Xint0x80_syscall () > > Now the interesting code here is at stack from #5: > > (kgdb) list > 948 fpp = newfdp->fd_ofiles; > 949 for (i = newfdp->fd_lastfile; i-- >= 0; fpp++) > 950 if (*fpp != NULL) > 951 (*fpp)->f_count++; > > (kgdb) p newfdp->fd_ofiles > $1 = (struct file **) 0xc23f2000 > (kgdb) p fpp > $2 = (struct file **) 0x0 > > Now... the only operation on fpp is fpp++. It should take a _long_ > time for fpp to get around to 0 and you'd thing that *fpp would be > zero long before that (or cause a page fault at some other > non-existant location). > > So... the similarity here is that deep in the kernel, we have a > automatic (possibly register) local variable that's getting zero'd. > > I have half-a-dozen crash dumps of this nature. For me, it always > happens in fdcopy(). This may be due to the fact that the machine is > running a large apache config --- so fork() is something it's doing > often. > > 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 Feb 23 8: 6:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id BA9AD37B79D for ; Wed, 23 Feb 2000 08:06:41 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 48B87137FC9; Wed, 23 Feb 2000 11:06:37 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id LAA36095; Wed, 23 Feb 2000 11:06:56 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14516.1439.654452.424962@trooper.velocet.net> Date: Wed, 23 Feb 2000 11:06:55 -0500 (EST) To: Nick Sayer Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: Wierd AMD panics caused by VMWare? In-Reply-To: <38B40262.FC4EEDD0@quack.kfu.com> References: <14515.59795.632514.748870@trooper.velocet.net> <38B40262.FC4EEDD0@quack.kfu.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Nick" == Nick Sayer writes: Nick> The only thing I would add is that by AMD I didn't mean Advanced Nick> Micro Devices. I meant /usr/sbin/amd. In my case this behavior Nick> has been observed on a Pentium III and on a K7, so it's CPU Nick> independent. Nick> The common denominator seems to be that the machine has to be Nick> very active. VMware stresses the vm system quite a bit (64M of Nick> shared memory with multiple processes digging around, etc). A Nick> very busy web server is going to do a lot of context switching Nick> (I think?). In that situation, it appears that the stack is Nick> being smashed. Nick> I tried insulating the code where my machines go nuts inside of Nick> splhigh() / splx(), but it didn't help. Nick> Is your machine running the automounter? No... but someone sent me some patches that deal with file descriptor coruption that may (or may not) solve my problem. It at least sounds plausable. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 8:19: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 33B0737B8F6 for ; Wed, 23 Feb 2000 08:19:02 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from sos (userhost.cma.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id RAA16941 for ; Wed, 23 Feb 2000 17:28:58 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <026a01bf7e19$eeacd6d0$16280c0a@sos> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: Things to consider in CURRENT Date: Wed, 23 Feb 2000 17:20:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did this via /stand/sysinstall - Configure packages from the RELENG-4 server, on a brand new installed 4.0-20000208-CURRENT > ----- Original Message ----- > From: "Garance A Drosihn" > To: "Morten Seeberg" ; > Sent: Monday, February 21, 2000 7:20 PM > Subject: Re: Things to consider in CURRENT > > > > At 4:47 PM +0100 2/21/00, Morten Seeberg wrote: > > >Hi, I just installed: FreeBSD fw.home 4.0-20000208-CURRENT and have a few > > >comments: > > > > > >It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this > out > > >for it self? One day when installing BSD without X (which automatically > > >installs Combat 3.x) I couldnt start it without. > > > > How did you do the install? Did you do an "install from scratch", or > > did you build over a system you already had running a previous release > > of freebsd? > > > > > > --- > > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > > Senior Systems Programmer or drosih@rpi.edu > > Rensselaer Polytechnic Institute > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 8:52:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2453B37B908 for ; Wed, 23 Feb 2000 08:52:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA30224; Wed, 23 Feb 2000 08:52:35 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 08:52:35 -0800 (PST) From: Matthew Dillon Message-Id: <200002231652.IAA30224@apollo.backplane.com> To: David Malone Cc: freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: Panic (pmap) References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> <20000223112007.A35612@walton.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, Feb 23, 2000 at 11:01:39AM +0100, Jeroen Ruigrok van der Werven wrote: : :> Current score: :> :> 1 tcp panic :> 1 pmap panic :> 4 ffs panics : :Such a mix might suggests bad hardware? : :(Mind you, we're seeing "freeing free block" panics on a NFS server :with full disks on 3.4). : : David. With softupdates turned on? Softupdates has known problems when a disk runs out of space. -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 Feb 23 9: 9:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by hub.freebsd.org (Postfix) with ESMTP id 6ED1737B957 for ; Wed, 23 Feb 2000 09:09:31 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-20-228.nv.iinet.net.au [203.59.85.228]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id BAA24656; Thu, 24 Feb 2000 01:09:02 +0800 Message-ID: <38B413E1.446B9B3D@elischer.org> Date: Wed, 23 Feb 2000 09:07:45 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Matthew Dillon Cc: David Malone , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: Panic (pmap) References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> <20000223112007.A35612@walton.maths.tcd.ie> <200002231652.IAA30224@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :On Wed, Feb 23, 2000 at 11:01:39AM +0100, Jeroen Ruigrok van der Werven wrote: > : > :> Current score: > :> > :> 1 tcp panic > :> 1 pmap panic > :> 4 ffs panics > : > :Such a mix might suggests bad hardware? > : > :(Mind you, we're seeing "freeing free block" panics on a NFS server > :with full disks on 3.4). > : > : David. > > With softupdates turned on? Softupdates has known problems when a > disk runs out of space. didn't kirk just fix that? > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 9:25:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C182037B908 for ; Wed, 23 Feb 2000 09:25:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA30519; Wed, 23 Feb 2000 09:25:12 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 09:25:12 -0800 (PST) From: Matthew Dillon Message-Id: <200002231725.JAA30519@apollo.backplane.com> To: Julian Elischer Cc: David Malone , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: Panic (pmap) References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> <20000223112007.A35612@walton.maths.tcd.ie> <200002231652.IAA30224@apollo.backplane.com> <38B413E1.446B9B3D@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : David. :> :> With softupdates turned on? Softupdates has known problems when a :> disk runs out of space. : :didn't kirk just fix that? : : __--_|\ Julian Elischer I don't recall it being fixed. The pmap panics are more telling. Softupdates has no known bugs that cause a pmap panic, but nothing else in the system is currently known to cause a pmap panic either except bad hardware. But the fact that the bug is occuring in the same place -- during the vm_pageout_page_stats() call, could indicate a bug rather then hardware. The vm_pageout_page_stats() procedure is really scary -- it's doing a bunch of things outside of splvm() that probably should be inside splvm(), like checking to see if a page is deactivateable and then only entering splvm() to deactivate it (but what if the page changed state after the check but before entering splvm()?). There are a couple of places in the kernel where the VM system tries to 'optimize' scans by dealing with side effects instead of splvm()ing, and this is one of them. I think it may be worth having David do a quick patch to see if it helps. David, try the following brute-force patch and see if it helps. Also, is this an SMP box or not? -Matt Matthew Dillon Index: vm_pageout.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_pageout.c,v retrieving revision 1.151 diff -u -r1.151 vm_pageout.c --- vm_pageout.c 1999/12/11 16:13:02 1.151 +++ vm_pageout.c 2000/02/23 17:23:23 @@ -1151,6 +1151,7 @@ int pcount,tpcount; /* Number of pages to check */ static int fullintervalcount = 0; int page_shortage; + int s0; page_shortage = (cnt.v_inactive_target + cnt.v_cache_max + cnt.v_free_min) - @@ -1159,6 +1160,8 @@ if (page_shortage <= 0) return; + s0 = splvm(); + pcount = cnt.v_active_count; fullintervalcount += vm_pageout_stats_interval; if (fullintervalcount < vm_pageout_full_stats_interval) { @@ -1227,6 +1230,7 @@ m = next; } + splx(s0); } static int To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 10:15:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id DD87A37B950; Wed, 23 Feb 2000 10:15:45 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id KAA87838; Wed, 23 Feb 2000 10:15:01 -0800 (PST) From: Archie Cobbs Message-Id: <200002231815.KAA87838@bubba.whistle.com> Subject: Re: NETGRAPH patches (proposal) In-Reply-To: <38B3F8FC.2781E494@elischer.org> from Julian Elischer at "Feb 23, 2000 07:13:00 am" To: julian@elischer.org (Julian Elischer) Date: Wed, 23 Feb 2000 10:15:01 -0800 (PST) Cc: dwmalone@maths.tcd.ie, myevmenkin@att.com, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > > > It's because all packets sent by this node should have the node's > > > > address. If you don't have it then PPPoE cannot send a packet "FROM" > > > > thia node, as it has no idea of what this node's address is. > > > > > > So.. we can have two hooks, one that sets the host address and > > > one that doesn't.. :-) > > > > In that case can we have one that also sets the destination address > > via arp? > > Now I think you are talking a separate node that implements > such a protocol. Right.. ARP is an IP-specific protocol. Ethernet nodes should have no specific knowledge of ARP. But it would be easy to create an ARP node that sat between the IP stack and an Ethernet node... it would maintain an ARP cache, and when it saw an outgoing dest IP address that was unmapped would issue an ARP request, etc. It would listen to the incoming Ethertypes for IP and ARP coming up from the Ethernet node. This brings up another point.. to really do this correctly we would also need a 802.3/802.2 node type that decoded Ethertypes and SNAP headers. It would have a "downstream" hook that connected to the Ethernet node and also hooks for "ip", "arp", "appletalk", "aarp" (AppleTalk's ARP), "ipx", "ipv6", etc. Also, it could suport generic Ethertype hooks having names of the form "0xNNNN". Probably the raw Ethernet node type should not even know about 802.3 (the standard 14 byte Ethernet header and the 60 byte minimum packet length).. -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 Wed Feb 23 10:17:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1C86637BA23 for ; Wed, 23 Feb 2000 10:17:17 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id KAA21717; Wed, 23 Feb 2000 10:46:15 -0800 (PST) Date: Wed, 23 Feb 2000 10:46:14 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Julian Elischer , David Malone , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: softdep out of space should be fixed Re: Panic (pmap) Message-ID: <20000223104614.U21720@fw.wintelcom.net> References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> <20000223112007.A35612@walton.maths.tcd.ie> <200002231652.IAA30224@apollo.backplane.com> <38B413E1.446B9B3D@elischer.org> <200002231725.JAA30519@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002231725.JAA30519@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 23, 2000 at 09:25:12AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000223 09:55] wrote: > > :> : David. > :> > :> With softupdates turned on? Softupdates has known problems when a > :> disk runs out of space. > : > :didn't kirk just fix that? > : > : __--_|\ Julian Elischer > > I don't recall it being fixed. It _should_ be fixed in both 4.0 (rev 1.25) and 3.4 (rev 1.21.2.2+1.21.2.3) of src/sys/ufs/ffs/ffs_balloc.c -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 10:31: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0D59A37B98C for ; Wed, 23 Feb 2000 10:30:58 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Feb 2000 18:30:51 +0000 (GMT) To: Matthew Dillon Cc: David Malone , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: ffs_blkfree: freeing free block (was Re: Panic (pmap)) In-reply-to: Your message of "Wed, 23 Feb 2000 08:52:35 PST." <200002231652.IAA30224@apollo.backplane.com> Date: Wed, 23 Feb 2000 18:30:51 +0000 From: Ian Dowse Message-ID: <200002231830.aa95387@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002231652.IAA30224@apollo.backplane.com>, Matthew Dillon writes: >:(Mind you, we're seeing "freeing free block" panics on a NFS server >:with full disks on 3.4). >: >: David. > > With softupdates turned on? Softupdates has known problems when a > disk runs out of space. No, softupdates is not enabled on this filesystem. Other filesystems on the same machine that are used lightly and are not full do have softupdates enabled though. (we have v1.21.2.3 of ffs_balloc.c anyway) The panics have been occurring every few days recently, and their timing always corresponds within a few minutes to the filesystem becoming full (/var/log/messages will have a flurry of 'file system full' messages just before the reboot). An example trace is below. Let me know if any further information would be useful. Ian #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc0148311 in panic (fmt=0xc0234c11 "ffs_blkfree: freeing free block") at ../../kern/kern_shutdown.c:446 #2 0xc01ca29f in ffs_blkfree (ip=0xc2303000, bno=18512, size=8192) at ../../ufs/ffs/ffs_alloc.c:1328 #3 0xc01ccab2 in ffs_indirtrunc (ip=0xc2303000, lbn=-2061, dbn=15492288, lastbn=-1, level=1, countp=0xcb2aab2c) at ../../ufs/ffs/ffs_inode.c:498 #4 0xc01cc528 in ffs_truncate (vp=0xcb3f1cc0, length=0, flags=0, cred=0xc21a8f84, p=0xcb254700) at ../../ufs/ffs/ffs_inode.c:315 #5 0xc01d8ca9 in ufs_setattr (ap=0xcb2aac98) at ../../ufs/ufs/ufs_vnops.c:493 #6 0xc01db11d in ufs_vnoperate (ap=0xcb2aac98) at ../../ufs/ufs/ufs_vnops.c:2300 #7 0xc01956f8 in nfsrv_setattr (nfsd=0xc21a8f00, slp=0xc20c4d00, procp=0xcb254700, mrq=0xcb2aae34) at vnode_if.h:275 #8 0xc01aec96 in nfssvc_nfsd (nsd=0xcb2aae94, argp=0x8072b64 "", p=0xcb254700) at ../../nfs/nfs_syscalls.c:652 #9 0xc01ae5e1 in nfssvc (p=0xcb254700, uap=0xcb2aaf94) at ../../nfs/nfs_syscalls.c:342 #10 0xc0204be3 in syscall (frame={tf_es = 39, tf_ds = -1078001625, tf_edi = 16, tf_esi = 4, tf_ebp = -1077944908, tf_isp = -886394908, tf_ebx = 0, tf_edx = 3, tf_ecx = 3, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134519880, tf_cs = 31, tf_eflags = 662, tf_esp = -1077945308, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #11 0xc01fa16c in Xint0x80_syscall () #12 0x80480e9 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 10:33:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AABD737B974 for ; Wed, 23 Feb 2000 10:33:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA22281; Thu, 24 Feb 2000 05:37:54 +1100 Date: Thu, 24 Feb 2000 05:33:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? In-Reply-To: <14515.59795.632514.748870@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, David Gilbert wrote: >... > I have half-a-dozen crash dumps of this nature. For me, it always > happens in fdcopy(). This may be due to the fact that the machine is > running a large apache config --- so fork() is something it's doing > often. See PR 16568. pmap_remove_all() doesn't flush the TLB properly in FreeBSD-3.x on i386's. Somehow this doesn't cause many problems, but it fairly reliably breaks the free() in fdfree() when there was a file descriptor larger than about 1000 (this gives a free() of more than MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 10:43:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 52F5237B96D for ; Wed, 23 Feb 2000 10:43:20 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA22656; Thu, 24 Feb 2000 05:47:22 +1100 Date: Thu, 24 Feb 2000 05:43:04 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting In-Reply-To: <20000223152130.A1583@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, Andreas Klemm wrote: > On Wed, Feb 23, 2000 at 11:43:32PM +1100, Bruce Evans wrote: > > Old systems don't support 40GB disks (except in LBA mode, which is > > broken in other ways). > what do you mean exactly with "old systems" ? FreeBSD-3.x, or FreeBSD--current with the wd driver. > Please look here: > FreeBSD is able to detect the drive in it's full size, kernel message: > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 > 79406*16*63= 80041248 sectors Old systems only support 65536 cylinders. (All FreeBSD drivers only support 65556 sectors in CHS mode.) > Disklabel also has reasonable entries: > sectors/track: 63 > tracks/cylinder: 255 > cylinders: 4217 > sectors/unit: 67746105 > 255*63*4217= 67746105 > which should be the size of my FreeBSD slice This is reasonable if the slice isn't [nearly] the whole disk. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 10:43:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id 8E9F537B9D4; Wed, 23 Feb 2000 10:43:37 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id NAA23162; Wed, 23 Feb 2000 13:43:34 -0500 (EST) Received: from njb140bh2.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id NAA11284; Wed, 23 Feb 2000 13:42:53 -0500 (EST) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Feb 2000 13:43:32 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Archie Cobbs'" , julian@elischer.org Cc: dwmalone@maths.tcd.ie, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: RE: NETGRAPH patches (proposal) Date: Wed, 23 Feb 2000 13:43:17 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Archie Cobbs [mailto:archie@whistle.com] > Julian Elischer writes: > > > > > It's because all packets sent by this node should > have the node's > > > > > address. If you don't have it then PPPoE cannot send > a packet "FROM" > > > > > thia node, as it has no idea of what this node's address is. > > > > > > > > So.. we can have two hooks, one that sets the host address and > > > > one that doesn't.. :-) > > > > > > In that case can we have one that also sets the > destination address > > > via arp? > > > > Now I think you are talking a separate node that implements > > such a protocol. > > Right.. ARP is an IP-specific protocol. Ethernet nodes should have > no specific knowledge of ARP. > [...] > This brings up another point.. to really do this correctly we would > also need a 802.3/802.2 node type that decoded Ethertypes and SNAP > headers. It would have a "downstream" hook that connected to the > Ethernet node and also hooks for "ip", "arp", "appletalk", "aarp" > (AppleTalk's ARP), "ipx", "ipv6", etc. Also, it could suport > generic Ethertype hooks having names of the form "0xNNNN". > > Probably the raw Ethernet node type should not even know about 802.3 > (the standard 14 byte Ethernet header and the 60 byte minimum packet > length).. i think that ethernet driver should be just raw ethernet node. it should not have any specific knowledge about upper levels. these raw nodes connected to another node that will perform the same functionality as ``ether_input'' does. i.e. it will decode type and send data to the appropriate hook. if the hook is connected - fine, we got data and put it to the protocol stack. if not - just drop. so we are really control the system. if we need specific protocol in the stack just load specific node and connect it to the hook. we can use simple name convention for the hooks (like "ether_0xNNN" where NNN is type) and in this case we do not have to change ``ether_input'' node. this looks more and more like STREAMS :). but NETGRAPH do not put data in the ``envelope'' like STREAMS does. the only thing that bothers me... how we can marry existing functionality and NETGRAPH? i vote for NETGRAPH :) it is c00l :) i just like the idea of connecting raw ethernet device driver with tty level :) thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 11:15:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from ring.vpop.net (ring.vpop.net [206.117.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 980CF37B99B; Wed, 23 Feb 2000 11:15:15 -0800 (PST) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by ring.vpop.net (8.9.3/8.9.3) with ESMTP id LAA91697; Wed, 23 Feb 2000 11:15:13 -0800 (PST) (envelope-from mreimer@vpop.net) Message-ID: <38B431C3.32FD2C13@vpop.net> Date: Wed, 23 Feb 2000 11:15:15 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-multimedia@freebsd.org Cc: freebsd-current@freebsd.org Subject: PATCH: partial fix for PR 16587 can't record with CS423x Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Partial fix: the following patch correctly configures the card for dual channel DMA. The problem was that the SDC bit (0x04) can only be set in the MCE state. So now recording doesn't hang, and data is returned, but the recorded sound doesn't sound right when played back. Anybody have an idea why? --- mss.c.orig Wed Feb 23 11:04:23 2000 +++ mss.c Fri Jan 28 16:18:28 2000 @@ -92,8 +92,6 @@ static int ad_read(struct mss_info *mss, int reg); static void ad_write(struct mss_info *mss, int reg, u_char data); static void ad_write_cnt(struct mss_info *mss, int reg, u_short data -static void ad_enter_MCE(struct mss_info *mss); -static void ad_leave_MCE(struct mss_info *mss); /* io primitives */ static void conf_wr(struct mss_info *mss, u_char reg, u_char data); @@ -467,9 +465,7 @@ } if (FULL_DUPLEX(mss) && mss->bd_id != MD_OPTI931) ad_write(mss, 12, ad_read(mss, 12) | 0x40); /* mode 2 */ - ad_enter_MCE(mss); ad_write(mss, 9, FULL_DUPLEX(mss)? 0 : 4); - ad_leave_MCE(mss); ad_write(mss, 10, 2); /* int enable */ io_wr(mss, MSS_STATUS, 0); /* Clear interrupt status */ /* the following seem required on the CS4232 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 11:17:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ring.vpop.net (ring.vpop.net [206.117.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 4DE6837B950; Wed, 23 Feb 2000 11:17:21 -0800 (PST) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by ring.vpop.net (8.9.3/8.9.3) with ESMTP id LAA92241; Wed, 23 Feb 2000 11:17:19 -0800 (PST) (envelope-from mreimer@vpop.net) Message-ID: <38B43241.6451BA50@vpop.net> Date: Wed, 23 Feb 2000 11:17:21 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-multimedia@freebsd.org, freebsd-current@freebsd.org Subject: Re: PATCH: partial fix for PR 16587 can't record with CS423x References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doh! Sorry, I reversed the patch. Matt Matthew Reimer wrote: > > Partial fix: the following patch correctly configures the card for dual > channel DMA. The problem was that the SDC bit (0x04) can only be set in > the MCE state. > > So now recording doesn't hang, and data is returned, but the recorded > sound doesn't sound right when played back. Anybody have an idea why? > > --- mss.c.orig Wed Feb 23 11:04:23 2000 > +++ mss.c Fri Jan 28 16:18:28 2000 > @@ -92,8 +92,6 @@ > static int ad_read(struct mss_info *mss, int reg); > static void ad_write(struct mss_info *mss, int reg, u_char > data); > static void ad_write_cnt(struct mss_info *mss, int reg, > u_short data > -static void ad_enter_MCE(struct mss_info *mss); > -static void ad_leave_MCE(struct mss_info *mss); > > /* io primitives */ > static void conf_wr(struct mss_info *mss, u_char reg, u_char > data); > @@ -467,9 +465,7 @@ > } > if (FULL_DUPLEX(mss) && mss->bd_id != MD_OPTI931) > ad_write(mss, 12, ad_read(mss, 12) | 0x40); /* mode 2 */ > - ad_enter_MCE(mss); > ad_write(mss, 9, FULL_DUPLEX(mss)? 0 : 4); > - ad_leave_MCE(mss); > ad_write(mss, 10, 2); /* int enable */ > io_wr(mss, MSS_STATUS, 0); /* Clear interrupt status */ > /* the following seem required on the CS4232 */ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" 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 Feb 23 11:30:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id AAA5537B9D4 for ; Wed, 23 Feb 2000 11:30:39 -0800 (PST) (envelope-from karsten@rohrbach.de) Received: (qmail 2451 invoked by uid 1000); 23 Feb 2000 19:30:37 -0000 Date: Wed, 23 Feb 2000 20:30:37 +0100 From: "Karsten W. Rohrbach" To: freebsd-current@FreeBSD.ORG, asmodai@bart.nl Cc: freebsd-fs@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: Panic #3 (ffs) Message-ID: <20000223203037.A2298@rohrbach.de> Reply-To: karsten@rohrbach.de References: <20000223153629.H18964@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223153629.H18964@lucifer.bart.nl>; from asmodai@bart.nl on Wed, Feb 23, 2000 at 03:36:29PM +0100 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG which megaraid adapter do you use in this box (hw, fw ver, bios ver, cntl-m ver)... i've seen those panics on our old news box when there where errors on the scsi busses which did not get detected properly. mainly termination issues *sigh* /k Jeroen Ruigrok van der Werven(asmodai@bart.nl)@Wed, Feb 23, 2000 at 03:36:29PM +0100: > *sigh* > > I think I am going to give up my job and become a buddhist monk... > > start = 0, len = 2646, fs = /news > panic: ffs_alloccg: map corrupted > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.372 > db> trace > Debugger(c01e7ee3) at Debugger+0x35 > panic(c01f28bf,c01f28a0,0,a56,c1d0d8d4) at panic+0x70 > ffs_mapsearch(c1d0d800,ccd49000,5d2a8,1,b) at ffs_mapsearch+0x143 > ffs_alloccg(c1da7700,b,5d2a8,400) at ffs_alloccg+0x21a > ffs_hashalloc(c1da7700,b,5d2a8,400,c0194cb8) at ffs_hashalloc+0x23 > ffs_alloc(c1da7700,b,5d2a8,400,c1d38280) at ffs_alloc+0xad > ffs_balloc(d8a1ce68,d8a4c200,c1d6a180,3,d8b74ba0) at ffs_balloc+0x456 > ffs_write(d8a1cea0,d6299a80,4c,c1d6a180,c0201d00) at ffs_write+0x319 > vn_write(c1d6a180,d8a1ceec,c1d38280,0,d6299a80) at vn_write+0xda > dofilewrite(d6299a80,c1d6a180,18,280c4000,4c) at dofilewrite+0x91 > write(d6299a80,d8a1cf80,280ad140,280ad140,280c404d) at write+0x33 > syscall(280c002f,280a002f,bfbf002f,280c404d,280ad140) at syscall+0x176 > Xint0x80_syscall() at Xint0x80_syscall+0x26 > > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > bART Internet Services / > BSD: Technical excellence at its best VIA NET.WORKS Netherlands > Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message -- > Hugh Hefner is a virgin. http://www.webmonster.de http://www.apache.de http://www.splatterworld.de (NIC-HDL KR433/KR11-RIPE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 11:38: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id CAD7237B908; Wed, 23 Feb 2000 11:38:01 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id UAA24256; Wed, 23 Feb 2000 20:37:55 +0100 (CET) (envelope-from asmodai) Date: Wed, 23 Feb 2000 20:37:55 +0100 From: Jeroen Ruigrok van der Werven To: "Karsten W. Rohrbach" Cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: Panic #3 (ffs) Message-ID: <20000223203755.A24240@lucifer.bart.nl> References: <20000223153629.H18964@lucifer.bart.nl> <20000223203037.A2298@rohrbach.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223203037.A2298@rohrbach.de>; from karsten@rohrbach.de on Wed, Feb 23, 2000 at 08:30:37PM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000223 20:35], Karsten W. Rohrbach (karsten@rohrbach.de) wrote: >which megaraid adapter do you use in this box (hw, fw ver, bios ver, >cntl-m ver)... > >i've seen those panics on our old news box when there where errors on >the scsi busses which did not get detected properly. mainly termination >issues *sigh* amr0: mem 0xe3000000-0xe300ffff irq 10 at device 10.1 on pci0 amr0: firmware EH61 bios 1.31 16MB memory amrd0: on amr0 amrd0: 35040MB (71761920 sectors) RAID 0 (optimal) And I receive the panics on BOTH the array and the normal da disks. I know the termination is correct. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 11:40:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 4FEF637B92B for ; Wed, 23 Feb 2000 11:40:45 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id OAA76986; Wed, 23 Feb 2000 14:40:33 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000223143725.01c6ecb0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 23 Feb 2000 14:37:25 -0500 To: karsten@rohrbach.de, freebsd-current@FreeBSD.ORG From: Mike Tancsa Subject: Re: Panic #3 (ffs) (MegaRAID) In-Reply-To: <20000223203037.A2298@rohrbach.de> References: <20000223153629.H18964@lucifer.bart.nl> <20000223153629.H18964@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:30 PM 2/23/00 +0100, Karsten W. Rohrbach wrote: >which megaraid adapter do you use in this box (hw, fw ver, bios ver, >cntl-m ver)... > >i've seen those panics on our old news box when there where errors on >the scsi busses which did not get detected properly. mainly termination >issues *sigh* I dont think its necessarily a termination issue. I have swapped the exact same chain onto a Mylex DAC960 and can pound the box without issue. I have a nasty feeling my 466 might not like my MB chipset. I am using a 466 PERC2/SC on BX chipset ECS MB and its throwing all sorts of fits. When I used a 428 on another box (a plain old Pentium), I didnt have nearly this many problems. Soon as my co-worker is finished with the older Pentium, I can test this theory to see if this is the case. Looking at the release notes for the BIOS revs at AMI, it seems older BIOS revs might have problems with newer MBs From ftp://ftp.megatrends.com/MegaRAID/drivers/466/readme-gh6d.txt >Changes in this release: >----------------------- >1. CTRL-M is not invoked until after the system BIOS is completed > on newer systems that support PMM (POST Memory Management). > The system would hang at different places in CTRL-M on these > systems prior to these changes. Until I flashed it to this new rev, I was seeing this behaviour. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 11:47:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 7CE7137B99A for ; Wed, 23 Feb 2000 11:47:52 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA28981; Wed, 23 Feb 2000 14:47:08 -0500 (EST) Message-ID: <20000223144707.A27132@netmonger.net> Date: Wed, 23 Feb 2000 14:47:07 -0500 From: Christopher Masto To: Andy Sparrow , "Kenneth D. Merry" Cc: Jeroen Ruigrok van der Werven , "Daniel O'Connor" , current@FreeBSD.ORG, Lyndon Nerenberg Subject: Re: status of 'device awe' ? References: <20000222132327.O5555@lucifer.bart.nl> <20000222233325.A14094@lucifer.bart.nl> <20000222154604.A22803@panzer.kdm.org> <20000222161002.A83593@mega.geek4food.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <20000222161002.A83593@mega.geek4food.org>; from Andy Sparrow on Tue, Feb 22, 2000 at 04:10:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 04:10:02PM -0800, Andy Sparrow wrote: > AFAIK, the AWE cannot work without this, and the cards PnPinfo > seems to not include the other two registers - and if you don't > probe them, then the 'awe' driver check doesn't see the EMU8000... > > Is there even a single person out there able to use the AWE device > under Voxware in -current? No, but that's sort of moot as far as I'm concerned, since I also can't record sound (see " recording does not work" on freebsd-current). It comes out as static regardless of the input source. There are just so many things broken right now, I haven't got time to worry about not having sound recording, but it'll be sad if 4.0 is released in this state. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:10:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (Postfix) with ESMTP id D024D37B9C7 for ; Wed, 23 Feb 2000 12:10:22 -0800 (PST) (envelope-from yds@dppl.com) Received: from dppl.com (avs.medianow.com [216.182.7.89]) by paris.dppl.com (Postfix) with ESMTP id 48648963B for ; Wed, 23 Feb 2000 15:10:21 -0500 (EST) Message-ID: <38B43EAC.75158BE0@dppl.com> Date: Wed, 23 Feb 2000 15:10:20 -0500 From: Yarema X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en, uk, ru, ja MIME-Version: 1.0 To: FreeBSD Current Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002220808.AAA59841@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa0400000) Mounting root from ufs:/dev/ad0s3a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 If at the boot prompt I: unload load kernel boot there's no problem. Also there's no problem if loading modules from /boot/loader.conf with a kernel suped and built on Feb. 17th with today's buildworld. Mike Smith wrote: > > > > it does : I've tried > > loading miibus alone : works fine > > loading miibus, then if_xl : loops in loading miibus > > Ok. We know that hurts, don't do that. 8) > From the above remark should I conclude that it's a known problem and we should refrain from loading modules from the boot loader until it works? Or would it help send boot_verbose output from my kernel as well? -- Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:10:26 2000 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 AF8DB37B9C8 for ; Wed, 23 Feb 2000 12:10:23 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA03320 for ; Wed, 23 Feb 2000 13:10:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA37081 for ; Wed, 23 Feb 2000 13:10:12 -0700 (MST) Message-Id: <200002232010.NAA37081@harmony.village.org> To: freebsd-current@freebsd.org Subject: routed dumping core? Date: Wed, 23 Feb 2000 13:10:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I go off and sink a huge amount of time into this, I was wondering if anybody else was noticing that routed in 4.0-rc2 was dumping core within a minute of the system starting. We have 4 different machines that this is hitting right now, but have not had the time to track it down any further than this. If this isn't a known problem, I'll dig further and put the time in to find/kill the bug, but I hadn't seen anything here so I thought I'd ask. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:20:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 3CFC337B9E1 for ; Wed, 23 Feb 2000 12:20:42 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip67.r2.d.bel.nwlink.com (ip67.r2.d.bel.nwlink.com [207.202.172.67]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id MAA10628 for ; Wed, 23 Feb 2000 12:20:40 -0800 (PST) Date: Wed, 23 Feb 2000 12:15:39 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: current@FreeBSD.org Subject: pcm and /dev/dsp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 4.0, the pcm sound driver works with my es1371 chipset soundcard for playing cds. But I cannot play mp3s. When I use mpg123, I get the error message "can't open /dev/dsp!" This is an improvement over 3.4, however, where I could not get pcm to work at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:25:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id ECCB937B992 for ; Wed, 23 Feb 2000 12:25:42 -0800 (PST) (envelope-from forrie@forrie.net) Received: (from forrie@localhost) by forrie.net with id e1NKPgU52981 for freebsd-current@freebsd.org; Wed, 23 Feb 2000 15:25:42 -0500 (EST) Date: Wed, 23 Feb 2000 15:25:42 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: USA_RESIDENT= in latest current Message-ID: <20000223152542.A52969@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Even though I have USA_RESIDENT="YES" in /etc/make.conf (this is how it was installed), I get: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >>> You must define the value of USA_RESIDENT as 'YES' or >>> 'NO' as appropriate, in the environment or /etc/make.conf >>> before building can proceed. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:26:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 650A937B9A6 for ; Wed, 23 Feb 2000 12:26:30 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA06927; Wed, 23 Feb 2000 12:26:24 -0800 (PST) Date: Wed, 23 Feb 2000 12:26:24 -0800 From: Brooks Davis To: R Joseph Wright Cc: current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp Message-ID: <20000223122624.A5227@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from rjoseph@nwlink.com on Wed, Feb 23, 2000 at 12:15:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote: > In 4.0, the pcm sound driver works with my es1371 chipset soundcard for > playing cds. But I cannot play mp3s. When I use mpg123, I get the error > message "can't open /dev/dsp!" > This is an improvement over 3.4, however, where I could not get pcm to > work at all. The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a "MAKEDEV snd0" after upgrading. My es1371 is working great streaming mp3s off of my.mp3.com using xmms. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:32:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 59B7D37BA02 for ; Wed, 23 Feb 2000 12:32:56 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip67.r2.d.bel.nwlink.com (ip67.r2.d.bel.nwlink.com [207.202.172.67]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id MAA13204; Wed, 23 Feb 2000 12:32:49 -0800 (PST) Date: Wed, 23 Feb 2000 12:27:49 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Brooks Davis Cc: current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp In-Reply-To: <20000223122624.A5227@orion.ac.hmc.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, 23 Feb 2000, Brooks Davis wrote: > On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote: > > In 4.0, the pcm sound driver works with my es1371 chipset soundcard for > > playing cds. But I cannot play mp3s. When I use mpg123, I get the error > > message "can't open /dev/dsp!" > > This is an improvement over 3.4, however, where I could not get pcm to > > work at all. > > The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a > "MAKEDEV snd0" after upgrading. My es1371 is working great streaming > mp3s off of my.mp3.com using xmms. > Beautiful. Thank you :) What about for isa cards? Which one is used for them now? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:36: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from math.udel.edu (math.udel.edu [128.175.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 1CB9E37B999 for ; Wed, 23 Feb 2000 12:36:03 -0800 (PST) (envelope-from schwenk@math.udel.edu) Received: from math.udel.edu (sisyphus.math.udel.edu [128.175.16.167]) by math.udel.edu (8.9.3+Sun/8.9.1) with ESMTP id PAA23353; Wed, 23 Feb 2000 15:35:52 -0500 (EST) Message-ID: <38B444A8.AD0CE3BB@math.udel.edu> Date: Wed, 23 Feb 2000 15:35:52 -0500 From: Peter Schwenk Organization: University of Delaware X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en, fr, de, ko MIME-Version: 1.0 To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: USA_RESIDENT= in latest current References: <20000223152542.A52969@forrie.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My make.conf is in /usr/defaults. I'm running 4.0-RC2 on a laptop. I set USA_RESIDENT="YES" there, and it seemed to work fine. Forrest Aldrich wrote: > Even though I have USA_RESIDENT="YES" in /etc/make.conf (this is how > it was installed), I get: > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >>> You must define the value of USA_RESIDENT as 'YES' or > >>> 'NO' as appropriate, in the environment or /etc/make.conf > >>> before building can proceed. > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- PETER SCHWENK | UNIX System Administrator Department of Mathematical Sciences | University of Delaware schwenk@math.udel.edu | (302)831-0437 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:40: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id A6D4D37B9C6 for ; Wed, 23 Feb 2000 12:40:05 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id D4DD41726; Wed, 23 Feb 2000 12:40:03 -0800 (PST) Date: Wed, 23 Feb 2000 12:40:03 -0800 From: Chris Piazza To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: USA_RESIDENT= in latest current Message-ID: <20000223124003.A4847@norn.ca.eu.org> References: <20000223152542.A52969@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223152542.A52969@forrie.net>; from forrie@forrie.net on Wed, Feb 23, 2000 at 03:25:42PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 03:25:42PM -0500, Forrest Aldrich wrote: > Even though I have USA_RESIDENT="YES" in /etc/make.conf (this is how > it was installed), I get: > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >>> You must define the value of USA_RESIDENT as 'YES' or > >>> 'NO' as appropriate, in the environment or /etc/make.conf > >>> before building can proceed. > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The proper format is USA_RESIDENT= YES in make.conf. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:43:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 581CE37B9A6 for ; Wed, 23 Feb 2000 12:43:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31642; Wed, 23 Feb 2000 12:43:20 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 12:43:20 -0800 (PST) From: Matthew Dillon Message-Id: <200002232043.MAA31642@apollo.backplane.com> To: Bruce Evans Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, 23 Feb 2000, David Gilbert wrote: : :>... : :> I have half-a-dozen crash dumps of this nature. For me, it always :> happens in fdcopy(). This may be due to the fact that the machine is :> running a large apache config --- so fork() is something it's doing :> often. : :See PR 16568. pmap_remove_all() doesn't flush the TLB properly in :FreeBSD-3.x on i386's. Somehow this doesn't cause many problems, but :it fairly reliably breaks the free() in fdfree() when there was a file :descriptor larger than about 1000 (this gives a free() of more than :MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. : :Bruce Ahh. I presume you will commit this patch now that Bjoern has confirmed that it works? I don't know why an unconditional invltlb() didn't work either, it should have. Maybe the __asm macro is being optimized out. -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 Feb 23 12:45:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from teknos.teknos.com (teknos-gw.nappr.org [216.0.190.254]) by hub.freebsd.org (Postfix) with ESMTP id E6B9237B9AB; Wed, 23 Feb 2000 12:45:30 -0800 (PST) (envelope-from salaman@teknos.com) Received: by teknos.teknos.com with Internet Mail Service (5.5.2650.21) id <19NW71WW>; Wed, 23 Feb 2000 16:40:45 -0400 Message-ID: <1D45ABC754FB1E4888E508992CE97E4F059CFF@teknos.teknos.com> From: "Victor A. Salaman" To: "'freebsd-current@freebsd.org'" , "'freebsd-emulation@freebsd.org'" Subject: Linux Emulation patches Date: Wed, 23 Feb 2000 16:40:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF7E3E.414733B0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF7E3E.414733B0 Content-Type: text/plain; charset="iso-8859-1" Hi: I was wondering who mantains the Linux Emulation? I have some patches that were sent to me for FreeBSD-3.4, I have converted them to FreeBSD 4.0-Current for Linux emulation problems. Specifically anyone trying to use any program that opens a server socket will get bitten by the emulation unless these patches are applied ( JServ, Resin, Tomcat are some Java programs affected by this... and since Sun hasn't release a JDK 1.2 for FreeBSD, well, the only way to run some server programs is with Blackdown, but without these patches they are useless ). Anyways, after sending email to marcel and peter with the patches, I haven't even received a reply. So therefore, I'm posting them here, in case anyone wants to commit them at all. I feel 4.0 shouldn't go out with a known broken linux emulation. --- /usr/src/sys/i386/linux/linux_file.c Wed Feb 23 16:11:50 2000 +++ /usr/src/sys/i386/linux/linux_file.orig Wed Feb 23 16:11:37 2000 @@ -199,6 +199,12 @@ } */ fcntl_args; struct linux_flock linux_flock; struct flock *bsd_flock; + struct filedesc *fdp; + struct file *fp; + struct vnode *vp; + long pgid; + struct pgrp *pgrp; + struct tty *tp; caddr_t sg; dev_t dev; @@ -283,9 +289,47 @@ case LINUX_F_SETOWN: case LINUX_F_GETOWN: - fcntl_args.cmd = args->cmd == LINUX_F_SETOWN ? F_SETOWN : F_GETOWN; - fcntl_args.arg = args->arg; - return fcntl(p, &fcntl_args); + /* + * We need to route around the normal fcntl() for these calls, + * since it uses TIOC{G,S}PGRP, which is too restrictive for + * Linux F_{G,S}ETOWN semantics. For sockets, this problem + * does not exist. + */ + fdp = p->p_fd; + if ((u_int)args->fd >= fdp->fd_nfiles || + (fp = fdp->fd_ofiles[args->fd]) == NULL) + return EBADF; + if (fp->f_type == DTYPE_SOCKET) { + fcntl_args.cmd = args->cmd == LINUX_F_SETOWN ? F_SETOWN : F_GETOWN; + fcntl_args.arg = args->arg; + return fcntl(p, &fcntl_args); + } + vp = (struct vnode *)fp->f_data; + dev = vn_todev(vp); + if (dev == NODEV) + return EINVAL; + if (!(devsw(dev)->d_flags & D_TTY)) + return EINVAL; + tp = dev->si_tty; + if (!tp) + return EINVAL; + if (args->cmd == LINUX_F_GETOWN) { + p->p_retval[0] = tp->t_pgrp ? tp->t_pgrp->pg_id : NO_PID; + return 0; + } + if ((long)args->arg <= 0) { + pgid = -(long)args->arg; + } else { + struct proc *p1 = pfind((long)args->arg); + if (p1 == 0) + return (ESRCH); + pgid = (long)p1->p_pgrp->pg_id; + } + pgrp = pgfind(pgid); + if (pgrp == NULL || pgrp->pg_session != p->p_session) + return EPERM; + tp->t_pgrp = pgrp; + return 0; } return EINVAL; } --- /usr/src/sys/i386/linux/linux_socket.c Wed Feb 23 16:11:50 2000 +++ /usr/src/sys/i386/linux/linux_socket.orig Wed Feb 23 16:11:48 2000 @@ -441,11 +441,6 @@ caddr_t name; int *anamelen; } */ bsd_args; - struct fcntl_args /* { - int fd; - int cmd; - long arg; - } */ f_args; int error; if ((error=copyin((caddr_t)args, (caddr_t)&linux_args, sizeof(linux_args)))) @@ -453,24 +448,7 @@ bsd_args.s = linux_args.s; bsd_args.name = (caddr_t)linux_args.addr; bsd_args.anamelen = linux_args.namelen; - - if (error = oaccept(p, &bsd_args)) - return error; - /* - * linux appears not to copy flags from the parent socket to the - * accepted one, so we must clear the flags in the new descriptor. - */ - f_args.fd = p->p_retval[0]; - f_args.cmd = F_SETFL; - f_args.arg = 0; - /* - * we ignore errors here since otherwise we would have an open file - * descriptor that wasn't returned to the user. - */ - (void) fcntl(p, &f_args); - /* put the file descriptor back as the return value */ - p->p_retval[0] = f_args.fd; - return 0; + return oaccept(p, &bsd_args); } struct linux_getsockname_args { ------_=_NextPart_001_01BF7E3E.414733B0 Content-Type: text/html; charset="iso-8859-1"
Hi:
 
I was wondering who mantains the Linux Emulation? I have some patches that were sent to me for FreeBSD-3.4, I have converted them to FreeBSD 4.0-Current for Linux emulation problems. Specifically anyone trying to use any program that opens a server socket will get bitten by the emulation unless these patches are applied ( JServ, Resin, Tomcat are some Java programs affected by this... and since Sun hasn't release a JDK 1.2 for FreeBSD, well, the only way to run some server programs is with Blackdown, but without these patches they are useless ).
 
Anyways, after sending email to marcel and peter with the patches, I haven't even received a reply. So therefore, I'm posting them here, in case anyone wants to commit them at all. I feel 4.0 shouldn't go out with a known broken linux emulation.
 
--- /usr/src/sys/i386/linux/linux_file.c Wed Feb 23 16:11:50 2000
+++ /usr/src/sys/i386/linux/linux_file.orig Wed Feb 23 16:11:37 2000
@@ -199,6 +199,12 @@
     } */ fcntl_args;
     struct linux_flock linux_flock;
     struct flock *bsd_flock;
+    struct filedesc *fdp;
+    struct file *fp;
+    struct vnode *vp;
+    long pgid;
+    struct pgrp *pgrp;
+    struct tty *tp;
     caddr_t sg;
     dev_t dev;
 
@@ -283,9 +289,47 @@
 
     case LINUX_F_SETOWN:
     case LINUX_F_GETOWN:
- fcntl_args.cmd = args->cmd == LINUX_F_SETOWN ? F_SETOWN : F_GETOWN;
- fcntl_args.arg = args->arg;
- return fcntl(p, &fcntl_args);
+ /*
+  * We need to route around the normal fcntl() for these calls,
+  * since it uses TIOC{G,S}PGRP, which is too restrictive for
+  * Linux F_{G,S}ETOWN semantics. For sockets, this problem
+  * does not exist.
+  */
+ fdp = p->p_fd;
+ if ((u_int)args->fd >= fdp->fd_nfiles ||
+  (fp = fdp->fd_ofiles[args->fd]) == NULL)
+     return EBADF;
+ if (fp->f_type == DTYPE_SOCKET) {
+     fcntl_args.cmd = args->cmd == LINUX_F_SETOWN ? F_SETOWN : F_GETOWN;
+         fcntl_args.arg = args->arg;
+     return fcntl(p, &fcntl_args);
+ }
+ vp = (struct vnode *)fp->f_data;
+ dev = vn_todev(vp);
+ if (dev == NODEV)
+     return EINVAL;
+ if (!(devsw(dev)->d_flags & D_TTY))
+     return EINVAL;
+ tp = dev->si_tty;
+ if (!tp)
+     return EINVAL;
+ if (args->cmd == LINUX_F_GETOWN) {
+     p->p_retval[0] = tp->t_pgrp ? tp->t_pgrp->pg_id : NO_PID;
+     return 0;
+ }
+ if ((long)args->arg <= 0) {
+     pgid = -(long)args->arg;
+ } else {
+     struct proc *p1 = pfind((long)args->arg);
+     if (p1 == 0)
+  return (ESRCH);
+     pgid = (long)p1->p_pgrp->pg_id;
+ }
+ pgrp = pgfind(pgid);
+ if (pgrp == NULL || pgrp->pg_session != p->p_session)
+     return EPERM;
+ tp->t_pgrp = pgrp;
+ return 0;
     }
     return EINVAL;
 }
--- /usr/src/sys/i386/linux/linux_socket.c Wed Feb 23 16:11:50 2000
+++ /usr/src/sys/i386/linux/linux_socket.orig Wed Feb 23 16:11:48 2000
@@ -441,11 +441,6 @@
  caddr_t name;
  int *anamelen;
     } */ bsd_args;
-    struct fcntl_args /* {
-    int fd;
-    int cmd;
-    long arg;
-    } */ f_args;
     int error;
 
     if ((error=copyin((caddr_t)args, (caddr_t)&linux_args, sizeof(linux_args))))
@@ -453,24 +448,7 @@
     bsd_args.s = linux_args.s;
     bsd_args.name = (caddr_t)linux_args.addr;
     bsd_args.anamelen = linux_args.namelen;
-
-    if (error = oaccept(p, &bsd_args))
- return error;
-    /*
-     * linux appears not to copy flags from the parent socket to the
-     * accepted one, so we must clear the flags in the new descriptor.
-     */
-    f_args.fd = p->p_retval[0];
-    f_args.cmd = F_SETFL;
-    f_args.arg = 0;
-   /*
-     * we ignore errors here since otherwise we would have an open file
-     * descriptor that wasn't returned to the user.
-     */
-    (void) fcntl(p, &f_args);
-    /* put the file descriptor back as the return value */
-    p->p_retval[0] = f_args.fd;
-    return 0;
+    return oaccept(p, &bsd_args);
 }
 
 struct linux_getsockname_args {
------_=_NextPart_001_01BF7E3E.414733B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:53:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 046FE37B9ED for ; Wed, 23 Feb 2000 12:53:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31746; Wed, 23 Feb 2000 12:53:11 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 12:53:11 -0800 (PST) From: Matthew Dillon Message-Id: <200002232053.MAA31746@apollo.backplane.com> To: Ian Dowse Cc: David Malone , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) References: <200002231830.aa95387@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> With softupdates turned on? Softupdates has known problems when a :> disk runs out of space. : :No, softupdates is not enabled on this filesystem. Other filesystems :on the same machine that are used lightly and are not full do have :softupdates enabled though. (we have v1.21.2.3 of ffs_balloc.c anyway) : :The panics have been occurring every few days recently, and their timing :always corresponds within a few minutes to the filesystem becoming full :(/var/log/messages will have a flurry of 'file system full' messages :just before the reboot). : :An example trace is below. Let me know if any further information would :be useful. : :Ian There must still be a bug in there somewhere, unrelated to softupdates. Try turning off the vfs.ffs.doreallocblks via sysctl and see if that stops the crashes, that will help narrow down where to search for the problem. -Matt :#0 boot (howto=256) at ../../kern/kern_shutdown.c:285 :#1 0xc0148311 in panic (fmt=0xc0234c11 "ffs_blkfree: freeing free block") : at ../../kern/kern_shutdown.c:446 :#2 0xc01ca29f in ffs_blkfree (ip=0xc2303000, bno=18512, size=8192) : at ../../ufs/ffs/ffs_alloc.c:1328 :#3 0xc01ccab2 in ffs_indirtrunc (ip=0xc2303000, lbn=-2061, dbn=15492288, : lastbn=-1, level=1, countp=0xcb2aab2c) at ../../ufs/ffs/ffs_inode.c:498 :#4 0xc01cc528 in ffs_truncate (vp=0xcb3f1cc0, length=0, flags=0, : cred=0xc21a8f84, p=0xcb254700) at ../../ufs/ffs/ffs_inode.c:315 :#5 0xc01d8ca9 in ufs_setattr (ap=0xcb2aac98) at ../../ufs/ufs/ufs_vnops.c:493 :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 12:57:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 903D837B9E0 for ; Wed, 23 Feb 2000 12:57:24 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115201>; Thu, 24 Feb 2000 07:58:04 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: Union semun defined in /usr/include/sys/sem.h? In-reply-to: ; from blk@skynet.be on Wed, Feb 23, 2000 at 11:46:35PM +1100 To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Feb24.075804est.115201@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: Date: Thu, 24 Feb 2000 07:58:03 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Feb-23 23:46:35 +1100, Brad Knowles wrote: > However, this has brought up an interesting question. It is my >understanding that X/Open requires that this union be defined within >the client source code Both Solaris and the Single UNIX Specification, Version 2 explicitly state this. > Is this changed in -CURRENT? Not at present. > If not, are there any plans to >change it in -CURRENT? Or has the X/Open standard changed, and >FreeBSD is following the new standard in this area? I can't comment on this. There doesn't seem to be a high level of interest in the SysV semaphore handling. > I'm also curious to know why there is a difference in how this >object is defined under Linux and FreeBSD. There are two differences: - The type of "array": SUSv2 and Linux specify "unsigned short int *", Solaris uses "ushort *" and FreeBSD uses "u_short *". The underlying type should be the same. (Though it does bring up another `bug' in our implementation - SUSv2 states should be idempotent, but we require to be explicitly included first). - Linux includes an "__buf" field. This field (and the associated IPC_INFO) don't appear in either SUSv2 or Solaris - I suspect it is a Linux extension to make ipcs(1) cleaner. >However, I'm also interested as to who is "right" on this issue, and >more importantly, why they are "right". It looks very much like FreeBSD is in the wrong here. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13: 5:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id CCCEC37C14E; Wed, 23 Feb 2000 13:05:03 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id QAA91326; Wed, 23 Feb 2000 16:05:00 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000223160154.00f44ad0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 23 Feb 2000 16:01:54 -0500 To: current@freebsd.org From: Mike Tancsa Subject: more PERC2/SC testing (MegaRAID 466) Cc: msmith@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 OK, I popped the 466 card in an older Celeron MB to see if I could get it to work. Same problems as on the PIII. 4+ bonnies in the background leads the SCSI chain to jam. I tried lowering the amount of queue tags, and then disabling them all together with no effect. I am going to try and downgrade the BIOS back to the official Dell BIOS which would not work with my PIII and see how that effects it. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13:10:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 00AF637B9C6 for ; Wed, 23 Feb 2000 13:09:30 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id VAA63412; Wed, 23 Feb 2000 21:08:58 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id VAA01106; Wed, 23 Feb 2000 21:07:07 GMT (envelope-from n_hibma@calcaphon.com) Date: Wed, 23 Feb 2000 21:07:07 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: R Joseph Wright Cc: Brooks Davis , current@freebsd.org Subject: Re: pcm and /dev/dsp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a > > "MAKEDEV snd0" after upgrading. My es1371 is working great streaming > > mp3s off of my.mp3.com using xmms. > > > Beautiful. Thank you :) > What about for isa cards? Which one is used for them now? See the output of dmesgt for the pcm[0-9] device that attaches to it. Then check what the /dev/ entries say. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13:23:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id A3BAC37B9D4 for ; Wed, 23 Feb 2000 13:23:45 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id NAA01237; Wed, 23 Feb 2000 13:23:42 -0800 (PST) Date: Wed, 23 Feb 2000 13:23:22 -0800 From: Brooks Davis To: R Joseph Wright Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp Message-ID: <20000223132322.A29598@orion.ac.hmc.edu> References: <20000223122624.A5227@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from rjoseph@nwlink.com on Wed, Feb 23, 2000 at 12:27:49PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: > Beautiful. Thank you :) > What about for isa cards? Which one is used for them now? I gave my only ISA sound card to Camran so I can't say for sure, but if you hardware the probe address the card ends up at that number and I think PnP cards would end up at pcm0 by default. However, Nick gave the more correct answer in that you should check dmesg and /dev/sndstat. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13:24:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 5786237B9B9 for ; Wed, 23 Feb 2000 13:24:10 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from vmware (a-211.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with SMTP id NAA50341 for ; Wed, 23 Feb 2000 13:24:09 -0800 (PST) (envelope-from nsayer@quack.kfu.com) From: "Nick Sayer" To: Subject: RE: Wierd AMD panics caused by VMWare? Date: Wed, 23 Feb 2000 13:23:17 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: <200002232043.MAA31642@apollo.backplane.com> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have gathered a bit more information. The problem I'm having always ends up in the same place - line 403 of vfs_cache.c. No matter how I try and test the value of ncpp before starting the inner for() (which bombs dereferencing NULL in the init part), I end up getting traps with ncpp being NULL, which is one of those can't-possibly-happen things. 1. I have found that putting an if (panicstr) return ; at the top of this routine necessary. When the trap happens, usually it ends up causing a circular panic. 2. I went through this routine's parent (in the panic), dounmount(). One of the things I discovered is that the clearing of the name cache (what cache_purgevfs() does, I guess) happens very early in an unmount. This means that I can put "unmount /usr" in a loop, and even though the unmount will always fail, it will end up making the namei cache useless. Now, It'd be sort of dopey to do this, I'll admit, but aparently it's the sort of thing amd does fairly routinely (it must blindly attempt to unmount every partition and the ones that don't go away must be in use). This probably has an impact on the namei cache efficiency of amd mounted disks. :-) 3. unmount /usr is sufficient to cause the panic, but not all of the time. Something has to happen to set up a situation where the unmount attempt will cause the trap. 4. My latest attempt has been to change ncpp from a stack variable to a global (staticly declared in vfs_cache.c). This _appears_ to be working longer than previous attempts, but just about every time I say that it seems it croaks almost immediately. :-) It's a bit of a gross workaround for an aparent register corruption (ddb shows that the instruction that fails is a movl 0(%eax),%eamumble). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13:30:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 83F7C37BA46 for ; Wed, 23 Feb 2000 13:30:48 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id NAA04218; Wed, 23 Feb 2000 13:30:42 -0800 (PST) Date: Wed, 23 Feb 2000 13:30:36 -0800 From: Brooks Davis To: Brooks Davis Cc: R Joseph Wright , current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp Message-ID: <20000223133036.A2970@orion.ac.hmc.edu> References: <20000223122624.A5227@orion.ac.hmc.edu> <20000223132322.A29598@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000223132322.A29598@orion.ac.hmc.edu>; from brooks@one-eyed-alien.net on Wed, Feb 23, 2000 at 01:23:22PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 01:23:22PM -0800, Brooks Davis wrote: > On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: > > Beautiful. Thank you :) > > What about for isa cards? Which one is used for them now? > > I gave my only ISA sound card to Camran so I can't say for sure, but if ^^^^^^ That's Cameron. My apologies. I can't spell and I even pulled up a window to check and then forgot. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 13:57:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from drama.navinet.net (drama.navinet.net [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 5810F37B9B2 for ; Wed, 23 Feb 2000 13:57:25 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net with id e1NLvLA06909; Wed, 23 Feb 2000 16:57:21 -0500 (EST) Date: Wed, 23 Feb 2000 16:57:21 -0500 From: Forrest Aldrich To: Chris Piazza Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: USA_RESIDENT= in latest current Message-ID: <20000223165721.B6809@drama.navinet.net> References: <20000223152542.A52969@forrie.net> <20000223124003.A4847@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000223124003.A4847@norn.ca.eu.org>; from cpiazza@jaxon.net on Wed, Feb 23, 2000 at 12:40:03PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps, but take a look at the installation... it sets it to USA_RESIDENT="YES" (note WITH quotes). _F > > The proper format is USA_RESIDENT= YES in make.conf. > > -Chris > -- > cpiazza@jaxon.net cpiazza@FreeBSD.org > Abbotsford, BC, Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 14: 6:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.viper.net.au (gatekeeper.viper.net.au [203.31.238.1]) by hub.freebsd.org (Postfix) with ESMTP id D672F37B9C8 for ; Wed, 23 Feb 2000 14:06:32 -0800 (PST) (envelope-from mark@viper.net.au) Received: from localhost (mark@localhost) by gatekeeper.viper.net.au (8.9.3/8.9.3) with ESMTP id JAA61733; Thu, 24 Feb 2000 09:06:03 +1100 (EST) (envelope-from mark@viper.net.au) Date: Thu, 24 Feb 2000 09:06:03 +1100 (EST) From: Mark Russell To: Doug Barton Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: 4.0 buildworld breaking In-Reply-To: <38B39548.5EEB3C94@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, Doug Barton wrote: > Mark Russell wrote: > > > > Hi > > For the last few days I've been trying to buildworld on my > > -CURRENT box and it barfs at libperl. > > > > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl > > -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 > > -I/usr/obj/usr/src/i386/usr/include -c > > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c -o > > toke.o > > mkdir: build: File exists > > *** Error code 1 > > You should discuss -current problems on freebsd-current. This looks like a Wrist slap taken. > classic "stale dependencies" problem. Try deleting /usr/obj/* and > /usr/src/*, download new sources and try again. > OK Now I'm even more baffled, I hosed /usr/obj and /usr/src and it broke in exactly the same place. Just wondering if you anyone else had any more idea's? Thanx +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Mark Russell mark@viper.net.au ph 61 + 2 + 9699 3837 viper.net.au http://www.viper.net.au fax 61 + 2 + 9699 3841 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Would you let this organisation make judgements about you http://www.tio.sux.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 14:35:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D950D37B9AF for ; Wed, 23 Feb 2000 14:35:30 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from maccullagh.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Feb 2000 22:35:29 +0000 (GMT) To: Matthew Dillon Cc: nops@maths.tcd.ie, freebsd-current@freebsd.org, diablo-list@list.bart.nl Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) In-reply-to: Your message of "Wed, 23 Feb 2000 12:53:11 PST." <200002232053.MAA31746@apollo.backplane.com> Date: Wed, 23 Feb 2000 22:35:29 +0000 From: Ian Dowse Message-ID: <200002232235.aa22335@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002232053.MAA31746@apollo.backplane.com>, Matthew Dillon writes: > There must still be a bug in there somewhere, unrelated to softupdates. > > Try turning off the vfs.ffs.doreallocblks via sysctl and see if that > stops the crashes, that will help narrow down where to search for the > problem. I think I've found it. Here's an easy way to repeat the problem to start with: mount_mfs -T fd1440 none /mnt cd /mnt dd if=/dev/zero bs=4k of=test seek=1036 count=1 dd if=/dev/zero bs=4k of=test1 count=1 dd if=/dev/zero bs=4k of=test2 rm test1 dd if=/dev/zero bs=4k of=test seek=8000 count=1 echo > test It looks as if the problem is in ffs_balloc(), and occurs as follows: - ffs_balloc() is asked to allocate a doubly indirect block. - The first-level indirection block already exists - The second-level indirection block does not exist, but is successfully allocated. - This block is linked into the first-level indirection block by the line: bap[indirs[i - 1].in_off] = nb; - Allocation of the data block fails. - All allocated blocks are then released, but there is still a link in the first-level indirection block to what is now a free block. The fix should be relatively straightforward - either the code should avoid linking new indirection blocks until all allocations succeed, or it should back out the changes on failure. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:14:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 44CC937BA1E for ; Wed, 23 Feb 2000 15:14:30 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (a-211.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id PAA51416 for ; Wed, 23 Feb 2000 15:14:29 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id PAA00700 for ; Wed, 23 Feb 2000 15:14:28 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <38B469D3.A7FA57FF@sftw.com> Date: Wed, 23 Feb 2000 23:14:27 +0000 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: sync hang Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm full of all sorts of good news today. :-( The machine I'm having such problems with just hung. Fortunately, I was able to get at it with ddb and force it to dump. The resulting core gives me this stack trace: #8 0xc026bde7 in siointr (arg=0xc0afe000) at ../../isa/sio.c:1679 #9 0xc0250b37 in Xfastintr4 () #10 0xc017d3e1 in vop_defaultop (ap=0xc84c5f20) at ../../kern/vfs_default.c:138 #11 0xc01d1023 in nfs_sync (mp=0xc0bc7200, waitfor=3, cred=0xc073b780, p=0xc84b7780) at vnode_if.h:27 #12 0xc0181571 in sync_fsync (ap=0xc84c5f7c) at ../../kern/vfs_subr.c:2827 #13 0xc017faf7 in sched_sync () at vnode_if.h:537 From 9 on up it is undoubtedly the result of the drop into DDB and the subsequent dump and boot. A ps on the core shows that indeed, the syncer is the running "process". vop_default() is very short, but there's no stack entry from VOCALL(). Perhaps it "wandered off..."? vmware was booting NT4 at the time. I'm begining to think that vmware isn't ready for prime time, but I can't quite come up with a mechanism in my head for how it's causing this and that I am somehow the only person in the world seeing it. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:21:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6D70937BAA2 for ; Wed, 23 Feb 2000 15:21:44 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Feb 2000 23:21:43 +0000 (GMT) Date: Wed, 23 Feb 2000 23:21:42 +0000 From: David Malone To: Matthew Dillon Cc: Julian Elischer , freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: Panic (pmap) Message-ID: <20000223232142.A78191@walton.maths.tcd.ie> References: <20000223100101.B17129@lucifer.bart.nl> <20000223110139.D17129@lucifer.bart.nl> <20000223112007.A35612@walton.maths.tcd.ie> <200002231652.IAA30224@apollo.backplane.com> <38B413E1.446B9B3D@elischer.org> <200002231725.JAA30519@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002231725.JAA30519@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 23, 2000 at 09:25:12AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 09:25:12AM -0800, Matthew Dillon wrote: Looks like Ian has tracked down our problem, but that's unlikely to be the problem Jurgen is seeing. > I think it may be worth having David do a quick patch to see if it > helps. David, try the following brute-force patch and see if it helps. Is this likely to help him? > Also, is this an SMP box or not? Just for reference, it wasn't. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:31:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 7494837BA4F for ; Wed, 23 Feb 2000 15:31:15 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip152.r7.d.bel.nwlink.com (ip152.r7.d.bel.nwlink.com [207.202.173.152]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id PAA14357; Wed, 23 Feb 2000 15:31:11 -0800 (PST) Date: Wed, 23 Feb 2000 15:26:07 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Brooks Davis Cc: current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp In-Reply-To: <20000223132322.A29598@orion.ac.hmc.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, 23 Feb 2000, Brooks Davis wrote: > On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: > > Beautiful. Thank you :) > > What about for isa cards? Which one is used for them now? > > I gave my only ISA sound card to Camran so I can't say for sure, but if > you hardware the probe address the card ends up at that number and I > think PnP cards would end up at pcm0 by default. However, Nick gave the > more correct answer in that you should check dmesg and /dev/sndstat. > I actually do not have an isa sound card, I was merely curious because in 3.x, pcm0 was reserved for isa cards and pcm1 was used for pci. Is it now set up so that it doesn't matter whether the card is isa or pci, you just use pcm0? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:34:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 1405037BA10 for ; Wed, 23 Feb 2000 15:34:02 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (a-211.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id PAA51581 for ; Wed, 23 Feb 2000 15:34:01 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id PAA00731 for ; Wed, 23 Feb 2000 15:34:01 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <38B46E69.1A711A21@sftw.com> Date: Wed, 23 Feb 2000 23:34:01 +0000 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: [Fwd: sync hang] Content-Type: multipart/mixed; boundary="------------352EFC8A1EECAD238528CA6A" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------352EFC8A1EECAD238528CA6A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Oh... one more thing on the hang... (kgdb) #10 0xc017d3e1 in vop_defaultop (ap=0xc84c5f20) at ../../kern/vfs_default.c:138 138 return (VOCALL(default_vnodeop_p, ap->a_desc->vdesc_offset, ap)); (kgdb) print ap $3 = (struct vop_generic_args *) 0x0 if ap is NULL, then ap->a_desc->vdesc_offset is probably a bad idea. :-( Looking at the actual disassembly, it looks like another case of a register getting a 0 stuffed into it at the oddest of times. --------------352EFC8A1EECAD238528CA6A Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <38B469D3.A7FA57FF@sftw.com> Date: Wed, 23 Feb 2000 23:14:27 +0000 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: sync hang Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm full of all sorts of good news today. :-( The machine I'm having such problems with just hung. Fortunately, I was able to get at it with ddb and force it to dump. The resulting core gives me this stack trace: #8 0xc026bde7 in siointr (arg=0xc0afe000) at ../../isa/sio.c:1679 #9 0xc0250b37 in Xfastintr4 () #10 0xc017d3e1 in vop_defaultop (ap=0xc84c5f20) at ../../kern/vfs_default.c:138 #11 0xc01d1023 in nfs_sync (mp=0xc0bc7200, waitfor=3, cred=0xc073b780, p=0xc84b7780) at vnode_if.h:27 #12 0xc0181571 in sync_fsync (ap=0xc84c5f7c) at ../../kern/vfs_subr.c:2827 #13 0xc017faf7 in sched_sync () at vnode_if.h:537 From 9 on up it is undoubtedly the result of the drop into DDB and the subsequent dump and boot. A ps on the core shows that indeed, the syncer is the running "process". vop_default() is very short, but there's no stack entry from VOCALL(). Perhaps it "wandered off..."? vmware was booting NT4 at the time. I'm begining to think that vmware isn't ready for prime time, but I can't quite come up with a mechanism in my head for how it's causing this and that I am somehow the only person in the world seeing it. :-) --------------352EFC8A1EECAD238528CA6A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:38: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 1060037BA1C; Wed, 23 Feb 2000 15:37:55 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from [128.130.111.2] (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.9.3/8.9.3) with ESMTP id AAA18446; Thu, 24 Feb 2000 00:37:48 +0100 (MET) Date: Thu, 24 Feb 2000 00:37:46 +0100 (CET) From: Gerald Pfeifer To: "Victor A. Salaman" Cc: freebsd-current@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: Linux Emulation patches In-Reply-To: <1D45ABC754FB1E4888E508992CE97E4F059CFF@teknos.teknos.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, 23 Feb 2000, Victor A. Salaman wrote: > Anyways, after sending email to marcel and peter with the patches, I haven't > even received a reply. :-( > > So therefore, I'm posting them here, in case anyone wants to commit > them at all. I feel 4.0 shouldn't go out with a known broken linux > emulation. One way to make sure your patch does not get lost is to create a GNATS report with the patch and priority=high by means of send-pr or the web form at http://www.freebsd.org/support.html#gnats. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 15:43: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 421AA37B8E6 for ; Wed, 23 Feb 2000 15:43:01 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id PAA27116; Wed, 23 Feb 2000 15:42:55 -0800 (PST) Date: Wed, 23 Feb 2000 15:42:55 -0800 From: Brooks Davis To: R Joseph Wright Cc: Brooks Davis , current@FreeBSD.ORG Subject: Re: pcm and /dev/dsp Message-ID: <20000223154255.A23994@orion.ac.hmc.edu> References: <20000223132322.A29598@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from rjoseph@nwlink.com on Wed, Feb 23, 2000 at 03:26:07PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 03:26:07PM -0800, R Joseph Wright wrote: > On Wed, 23 Feb 2000, Brooks Davis wrote: > > On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: > > > Beautiful. Thank you :) > > > What about for isa cards? Which one is used for them now? > > > > I gave my only ISA sound card to Camran so I can't say for sure, but if > > you hardware the probe address the card ends up at that number and I > > think PnP cards would end up at pcm0 by default. However, Nick gave the > > more correct answer in that you should check dmesg and /dev/sndstat. > > > I actually do not have an isa sound card, I was merely curious because in > 3.x, pcm0 was reserved for isa cards and pcm1 was used for pci. Is it now > set up so that it doesn't matter whether the card is isa or pci, you just > use pcm0? Basicaly, yes. The current system avoids skipping numbers where the old one would skip entries where you had provided isa probe hints, but there wasn't a card there. I believe there was some talk about changing things so device hints mean something like, "if there is a device matching these parameters use this entry, otherwise, don't." This would allow things like wiring devices to slots on PCI. It is possiably I misunderstood the proposal and it certaintly won't make it into 4.0. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 16:13: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 468DB37B926; Wed, 23 Feb 2000 16:12:56 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id TAA18140; Wed, 23 Feb 2000 19:12:50 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id TAA06540; Wed, 23 Feb 2000 19:12:48 -0500 (EST) Message-Id: <4.2.2.20000223190830.03b74b88@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 23 Feb 2000 19:10:42 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002230519.VAA00682@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:19 PM 2/22/2000 -0800, Mike Smith wrote: > > On 18 Feb 2000 17:39:19 -0500, in sentex.lists.freebsd.current you wrote: > > > > > >Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware > > >up within a few minutes. The Dell 3.00 firmware remains stable under the > > >same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a > > >firmware lockup - the SCSI bus is hung and usually the PCI bus as well. > > > > I am going to test the card in another older MB to see if its some strange > > interaction. What MB chipset are you using to test with ? > >I've been testing most recently with the Intel 450NX and AMD 751. OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but it crashes hard when you write to the partition. I am going to try and reflash the card to the latest AMI BIOS and see what happens. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 17:29:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A108637BA60 for ; Wed, 23 Feb 2000 17:29:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA33080; Wed, 23 Feb 2000 17:29:26 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 17:29:26 -0800 (PST) From: Matthew Dillon Message-Id: <200002240129.RAA33080@apollo.backplane.com> To: Nick Sayer Cc: freebsd-current@FreeBSD.ORG Subject: Re: sync hang References: <38B469D3.A7FA57FF@sftw.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm full of all sorts of good news today. :-( : :The machine I'm having such problems with just hung. Fortunately, I was :able to get at it with :ddb and force it to dump. The resulting core gives me this stack trace: What kind of machine is this? 3.x or 4.x? This could be another pmap issue but I doubt it. I think it's time for me to install VMWare :-) The process may not be 'stuck' in vop_defaultop ... it may be in an infinite loop at a higher level instead (e.g. in sync_fsync() or nfs_sync()). -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 Feb 23 17:33:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 787C637B786 for ; Wed, 23 Feb 2000 17:33:09 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 19735 invoked from network); 24 Feb 2000 01:33:08 -0000 Received: from lcm208.cvzoom.net (208.230.69.208) by ns.cvzoom.net with SMTP; 24 Feb 2000 01:33:08 -0000 Date: Wed, 23 Feb 2000 20:32:42 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: XFree86 3.9.18 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've built this thing on -current recently, and I'l getting the weirdest errors when I try to start X: (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 3 Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 9 Elf_RelocateEntry() Unsupported relocation type 9 Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 4 Elf_RelocateEntry() Unsupported relocation type 9 Elf_RelocateEntry() Unsupported relocation type 9 Elf_RelocateEntry() Unsupported relocation type 9 - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 17:48:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D13AA37BA89 for ; Wed, 23 Feb 2000 17:48:15 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Feb 2000 01:48:14 +0000 (GMT) To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) In-reply-to: Your message of "Wed, 23 Feb 2000 22:35:29 GMT." <200002232235.aa22335@salmon.maths.tcd.ie> Date: Thu, 24 Feb 2000 01:48:14 +0000 From: Ian Dowse Message-ID: <200002240148.aa34053@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002232235.aa22335@salmon.maths.tcd.ie>, Ian Dowse writes: > >The fix should be relatively straightforward - either the code should >avoid linking new indirection blocks until all allocations succeed, >or it should back out the changes on failure. Here's one patch that seems to fix the problem. It may not be the best approach though? Ian --- ffs_balloc.c.orig Thu Feb 24 00:44:32 2000 +++ ffs_balloc.c Thu Feb 24 01:45:46 2000 @@ -71,7 +71,7 @@ int flags; struct fs *fs; ufs_daddr_t nb; - struct buf *bp, *nbp; + struct buf *bp, *nbp, *allocbp; struct vnode *vp; struct indir indirs[NIADDR + 2]; ufs_daddr_t newb, *bap, pref; @@ -197,6 +197,7 @@ --num; nb = ip->i_ib[indirs[0].in_off]; allocib = NULL; + allocbp = NULL; allocblk = allociblk; if (nb == 0) { pref = ffs_blkpref(ip, lbn, 0, (ufs_daddr_t *)0); @@ -272,6 +273,17 @@ } } bap[indirs[i - 1].in_off] = nb; + if (allocib == NULL) { + /* + * Writing bp would link in the newly allocated + * blocks; hold off in case of allocation failure + * later. + */ + allocib = &bap[indirs[i - 1].in_off]; + allocbp = bp; + continue; + } + /* * If required, write synchronously, otherwise use * delayed write. @@ -316,8 +328,7 @@ bp->b_flags |= B_CLUSTEROK; bdwrite(bp); } - *ap->a_bpp = nbp; - return (0); + goto success; } brelse(bp); if (flags & B_CLRBUF) { @@ -330,6 +341,22 @@ nbp = getblk(vp, lbn, fs->fs_bsize, 0, 0); nbp->b_blkno = fsbtodb(fs, nb); } +success: + if (allocbp != NULL) { + /* + * It is safe to write allocbp now. + * + * If required, write synchronously, otherwise use + * delayed write. + */ + if (flags & B_SYNC) { + bwrite(allocbp); + } else { + if (allocbp->b_bufsize == fs->fs_bsize) + allocbp->b_flags |= B_CLUSTEROK; + bdwrite(allocbp); + } + } *ap->a_bpp = nbp; return (0); fail: @@ -349,8 +376,11 @@ ffs_blkfree(ip, *blkp, fs->fs_bsize); deallocated += fs->fs_bsize; } - if (allocib != NULL) + if (allocib != NULL) { *allocib = 0; + if (allocbp != NULL) + brelse(allocbp); + } if (deallocated) { #ifdef QUOTA /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 18:27:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3CE9137BABB for ; Wed, 23 Feb 2000 18:27:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA33299; Wed, 23 Feb 2000 18:27:06 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 18:27:06 -0800 (PST) From: Matthew Dillon Message-Id: <200002240227.SAA33299@apollo.backplane.com> To: Ian Dowse Cc: nops@maths.tcd.ie, freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) References: <200002232235.aa22335@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think I've found it. Here's an easy way to repeat the problem to :start with: : : mount_mfs -T fd1440 none /mnt : cd /mnt : dd if=/dev/zero bs=4k of=test seek=1036 count=1 : dd if=/dev/zero bs=4k of=test1 count=1 : dd if=/dev/zero bs=4k of=test2 : rm test1 : dd if=/dev/zero bs=4k of=test seek=8000 count=1 : echo > test : :It looks as if the problem is in ffs_balloc(), and occurs as follows: : - ffs_balloc() is asked to allocate a doubly indirect block. : - The first-level indirection block already exists : - The second-level indirection block does not exist, but is : successfully allocated. : - This block is linked into the first-level indirection block by : the line: : : bap[indirs[i - 1].in_off] = nb; : : - Allocation of the data block fails. : - All allocated blocks are then released, but there is still : a link in the first-level indirection block to what is : now a free block. : :The fix should be relatively straightforward - either the code should :avoid linking new indirection blocks until all allocations succeed, :or it should back out the changes on failure. : :Ian Great detective work! The 'allocib' variable is used to unwind the 'first' new indirect block allocation, but it is *only* initialized for the Level 0 block. So the unwinding only works when the Level 0 indirect block had to be allocated. When the Level 0 indirect block is valid and a deeper level indirect block had to be allocated, allocib is not initialized and the association is not unwound even though the deeper indirect block is freed when the data block allocation fails. Unfortunately, we can't simply initialize 'allocib' here, because it would point into the middle of a buffer. The fix is thus not entirely trivial. This is what I think we need to do, but THIS PATCH IS NOT TESTED AND COULD BE COMPLETELY WRONG. Any filesystem gurus out there who can look at this and tell me if it's correct? -Matt Matthew Dillon Index: ffs_balloc.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_balloc.c,v retrieving revision 1.25 diff -u -r1.25 ffs_balloc.c --- ffs_balloc.c 2000/01/11 08:27:00 1.25 +++ ffs_balloc.c 2000/02/24 02:25:53 @@ -77,6 +77,7 @@ ufs_daddr_t newb, *bap, pref; int deallocated, osize, nsize, num, i, error; ufs_daddr_t *allocib, *blkp, *allocblk, allociblk[NIADDR + 1]; + int unwindidx = -1; struct proc *p = curproc; /* XXX */ vp = ap->a_vp; @@ -272,6 +273,8 @@ } } bap[indirs[i - 1].in_off] = nb; + if (allocib == NULL && unwindidx < 0) + unwindidx = i - 1; /* * If required, write synchronously, otherwise use * delayed write. @@ -349,8 +352,26 @@ ffs_blkfree(ip, *blkp, fs->fs_bsize); deallocated += fs->fs_bsize; } - if (allocib != NULL) + if (allocib != NULL) { *allocib = 0; + } else if (unwindidx >= 0) { + error = bread(vp, + indirs[unwindidx].in_lbn, (int)fs->fs_bsize, NOCRED, &bp); + if (error) { + panic("Could not unwind indirect block, error %d", error); + brelse(bp); + } else { + bap = (ufs_daddr_t *)bp->b_data; + bap[indirs[unwindidx].in_off] = 0; + if (flags & B_SYNC) { + bwrite(bp); + } else { + if (bp->b_bufsize == fs->fs_bsize) + bp->b_flags |= B_CLUSTEROK; + bdwrite(bp); + } + } + } if (deallocated) { #ifdef QUOTA /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 18:29: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 90D0A37BA6C for ; Wed, 23 Feb 2000 18:28:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA33327; Wed, 23 Feb 2000 18:28:55 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 18:28:55 -0800 (PST) From: Matthew Dillon Message-Id: <200002240228.SAA33327@apollo.backplane.com> To: Ian Dowse Cc: freebsd-current@freebsd.org Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) References: <200002240148.aa34053@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <200002232235.aa22335@salmon.maths.tcd.ie>, Ian Dowse writes: :> :>The fix should be relatively straightforward - either the code should :>avoid linking new indirection blocks until all allocations succeed, :>or it should back out the changes on failure. : :Here's one patch that seems to fix the problem. It may not be the best :approach though? : :Ian I thought of this but I was worried that the softupdates blackmagic would get broken by it, so my approach is to actually unwind it which, between inbetween to FSYNC's, should be softupdates-safe. -Matt : bap[indirs[i - 1].in_off] = nb; :+ if (allocib == NULL) { :+ /* :+ * Writing bp would link in the newly allocated :+ * blocks; hold off in case of allocation failure :+ * later. :+ */ :+ allocib = &bap[indirs[i - 1].in_off]; :+ allocbp = bp; :+ continue; :+ } :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 19:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id E5C5237BA9A for ; Wed, 23 Feb 2000 19:18:43 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 9046 invoked from network); 24 Feb 2000 03:18:42 -0000 Received: from lcm208.cvzoom.net (208.230.69.208) by ns.cvzoom.net with SMTP; 24 Feb 2000 03:18:42 -0000 Date: Wed, 23 Feb 2000 22:18:16 -0500 (EST) From: Donn Miller To: Kenneth Wayne Culver Cc: current@FreeBSD.ORG Subject: Re: XFree86 3.9.18 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-656450158-951362296=:95548" 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-656450158-951362296=:95548 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 23 Feb 2000, Kenneth Wayne Culver wrote: > That's odd... I just built it tonight, and I havn't had anything but this: > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > Which doesn't cause the server to crash, in fact, it seems pretty stable. What did you put in your host.def? Here's my host.def (see attachment). - Donn --0-656450158-951362296=:95548 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="host.def" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="host.def" WENPTU0gJFhGcmVlODY6IHhjL2NvbmZpZy9jZi94Zjg2c2l0ZS5kZWYsdiAz LjE1MyAxOTk5LzEyLzAzIDE5OjE3OjE3IGVpY2ggRXhwICQNCi8qKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKiovDQovKg0KICogVGhpcyBmaWxl IGlzIHRvIHByb3ZpZGUgYSBxdWljayBtZXRob2QgZm9yIG1vc3QgcGVvcGxl IHRvIGNoYW5nZSB0aGUNCiAqIGJlaGF2aW91ciBvZiB0aGVpciBYRnJlZTg2 IGluc3RhbGxhdGlvbiB3aXRob3V0IGhhdmluZyB0byBmdWxseQ0KICogdW5k ZXJzdGFuZCB0aGUgd29ya2luZ3Mgb2Ygc2l0ZS5kZWYgYW5kIGFsbCB0aGUg dmFyaW91cyAnLmNmJyBmaWxlcy4NCiAqDQogKiBUaGVzZSBhcmUgdGhlIG1v c3QgY29tbW9uIHNldHRpbmdzIHlvdSB3b3VsZCBjaG9vc2UgZm9yIGNvbXBp bGluZyBhbmQNCiAqIGluc3RhbGxpbmcgWEZyZWU4NiBvbiB0aGUgc3lzdGVt cyBzdXBwb3J0ZWQgYnkgaXQuDQogKg0KICogQSBnb29kIHdheSB0byB1c2Ug dGhpcyBmaWxlIGlzIHRvIGNvcHkgaXQgdG8gaG9zdC5kZWYsIGFuZCBtYWtl IHRoZQ0KICogY2hhbmdlcyB0aGVyZS4gIFRoYXQgd2F5LCBmdXR1cmUgcGF0 Y2hlcyB0byB0aGlzIGZpbGUgd29uJ3QgZmFpbC4NCiAqIFRoZSBob3N0LmRl ZiBmaWxlIHdpbGwgbmV2ZXIgYmUgcGF0Y2hlZC4NCiAqDQogKiBUaGUgZGlz dHJpYnV0ZWQgdmVyc2lvbiBvZiB0aGlzIGZpbGUgc2hvdWxkIGNvbnRhaW4g bm8gdW5jb21tZW50ZWQNCiAqIGRlZmluaXRpb25zLiAgU3VjaCBkZWZhdWx0 IGRlZmluaXRpb25zIGJlbG9uZyBpbiB4ZnJlZTg2LmNmLg0KICovDQovKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqLw0KDQovKg0KICogSWYg eW91IGhhdmUgYnVpbGQtc3BlY2lmaWMgbW9kaWZpY2F0aW9ucyBpbiB5b3Vy IGhvc3QuZGVmIGZpbGUsIGJ1dA0KICogd2FudCBhbiBlbXB0eSBob3N0LmRl ZiBmaWxlIGluc3RhbGxlZCB3aGVuIGRvaW5nICdtYWtlIGluc3RhbGwnLA0K ICogdW5jb21tZW50IHRoZSBmb2xsb3dpbmcNCiAqDQojZGVmaW5lIEluc3Rh bGxFbXB0eUhvc3REZWYNCiAqLw0KDQovKg0KICogSWYgdXNpbmcgR0NDIDIu eCBvbiBhIHN5c3RlbSB3aGVyZSBpdCBpc24ndCB0aGUgZGVmYXVsdCwgdW5j b21tZW50DQogKiB0aGUgZm9sbG93aW5nDQogKg0KI2RlZmluZSBIYXNHY2My CQlZRVMNCiNkZWZpbmUgSGFzR2NjCQlZRVMNCiAqLw0KDQovKg0KICogSWYg dXNpbmcgR0NDIDIueCB3aXRoIEMrKyBvbiBhIHN5c3RlbSB3aGVyZSBpdCBp c24ndCB0aGUgZGVmYXVsdCwgdW5jb21tZW50DQogKiB0aGUgZm9sbG93aW5n Lg0KICoNCiNkZWZpbmUgSGFzR2NjMkZvckNwbHVzcGx1cwlZRVMNCiAqLw0K DQovKg0KICogVGhlIGRlZmF1bHQgb3B0aW1pc2F0aW9uIGZsYWdzIGZvciBH Q0MgMi54LiAgLWZuby1zdHJlbmd0aC1yZWR1Y2UgaXMNCiAqIGhlcmUgdG8g d29yayBhcm91bmQgYSBidWcgaW4gLU8yIGZvciBHQ0MgMi54IG9uIGkzODYg cGxhdGZvcm1zLg0KICogSWYgeW91IGFyZSB1c2luZyBhIHZlcnNpb24gdGhh dCBkb2Vzbid0IGhhdmUgdGhpcyBidWcsIHlvdSBjYW4NCiAqIHVuY29tbWVu dCB0aGUgZm9sbG93aW5nIGxpbmUsIGFuZCByZW1vdmUgJy1mbm8tc3RyZW5n dGgtcmVkdWNlJw0KICogSWYgeW91IGFyZSBidWlsZGluZyBiaW5hcmllcyBm b3IgYSA0ODYsIGl0IG1heSBiZSBiZW5lZmljaWFsIHRvIGFkZA0KICogLW00 ODYNCiAqDQogKi8NCiNkZWZpbmUgRGVmYXVsdEdjYzJpMzg2T3B0CS1tcGVu dGl1bSAtTzMgLXBpcGUNCg0KLyoNCiAqIFRoaXMgYWxsb3dzIHRoZSBHQ0Mg d2FybmluZyBmbGFncyB0byBiZSBzZXQuICBUaGUgZGVmYXVsdCBpcyBzaG93 biBoZXJlLg0KICoNCiAqLw0KI2RlZmluZSBHY2NXYXJuaW5nT3B0aW9ucyAt V2FsbA0KDQovKiANCiAqIFN1biBDb21waWxlciBzdHVmZi4uIA0KICoNCiNk ZWZpbmUgSGFzU3VuQyAgICAgICAgICAgICAgICAgICAgICAgICBZRVMNCiNk ZWZpbmUgSGFzU3VuQ3BsdXNwbHVzICAgICAgICAgICAgICAgICBZRVMNCiNk ZWZpbmUgQ3BsdXNwbHVzQ29tcGlsZXJNYWpvclZlcnNpb24gICA1DQojZGVm aW5lIENwbHVzcGx1c0NvbXBpbGVyTWlub3JWZXJzaW9uICAgMA0KI2RlZmlu ZSBDQ29tcGlsZXJNYWpvclZlcnNpb24gICAgICAgICAgIDUNCiNkZWZpbmUg Q0NvbXBpbGVyTWlub3JWZXJzaW9uICAgICAgICAgICAwDQogKi8NCg0KLyoN CiAqIE9wdGltaXplZCBTdW4gQ29tcGlsZXIgQnVpbGQuDQogKg0KI2RlZmlu ZSBEZWZhdWx0Q0RlYnVnRmxhZ3MgICAgICAgICAgICAgIC14TzQgLXh0YXJn ZXQ9cGVudGl1bV9wcm8NCiNkZWZpbmUgT3B0aW1pemVkQ0RlYnVnRmxhZ3Mg ICAgICAgICAgICAteE80IC14dGFyZ2V0PXBlbnRpdW1fcHJvDQogKi8NCg0K LyogDQogKiBEZWJ1Z2dhYmxlIFN1biBDb21waWxlciBCdWlsZC4gDQogKiBO b3RlOiBUaGlzIGJ1aWxkcyBfRVZFUllUSElOR18gYXMgZGVidWdnYWJsZQ0K ICoNCiNkZWZpbmUgRGVmYXVsdENEZWJ1Z0ZsYWdzICAgICAgICAgICAgICAt ZyAteHMNCiNkZWZpbmUgT3B0aW1pemVkQ0RlYnVnRmxhZ3MgICAgICAgICAg ICAtZyAteHMNCiAqLw0KDQovKg0KICogRm9yIExpbnV4LCB0aGlzIHNob3Vs ZCBtYXRjaCB0aGUgQmludXRpbHMgdmVyc2lvbiB5b3UgaGF2ZS4gIFRoaXMg ZXhhbXBsZQ0KICogaXMgZm9yIDIuNi4wLjcuICBTZWUgbGludXguY2YgZm9y IHRoZSBkZWZhdWx0IHNldHRpbmcuDQogKg0KICogVGhpcyBzaG91bGQgYXV0 b21hdGljYWxseSBnZXQgc2V0IGNvcnJlY3RseSBieSBpbWFrZS4NCiAqDQoj ZGVmaW5lIExpbnV4QmluVXRpbHNNYWpvclZlcnNpb24JMjYNCiAqLw0KDQov Kg0KICogRm9yIExpbnV4LCB0aGVzZSBzaG91bGQgbWF0Y2ggdGhlIGxpYmMg dmVyc2lvbiB5b3UgaGF2ZS4gIFRoaXMgZXhhbXBsZQ0KICogaXMgZm9yIGxp YmMuNS40LnguICBTZWUgbGludXguY2YgZm9yIHRoZSBkZWZhdWx0IHNldHRp bmcuDQogKg0KICogVGhpcyBzaG91bGQgYXV0b21hdGljYWxseSBnZXQgc2V0 IGNvcnJlY3RseSBieSBpbWFrZS4NCiAqDQojZGVmaW5lIExpbnV4Q0xpYk1h am9yVmVyc2lvbgk1DQojZGVmaW5lIExpbnV4Q2xpYk1pbm9yVmVyc2lvbgk0 DQogKi8NCg0KLyoNCiAqIElmIHlvdSB3YW50IHRvIHVzZSB0aGUgR05VIG1h bGxvYyBsaWJyYXJ5LCB1bmNvbW1lbnQgdGhpcw0KICoNCiNkZWZpbmUgVXNl R251TWFsbG9jCQlZRVMNCiAqLw0KDQovKg0KICogU2V0IHRoaXMgdG8gd2hh dGV2ZXIgaXMgcmVxdWlyZWQgdG8gYWNjZXNzIHRoZSBHTlUgbWFsbG9jIGxp YnJhcnkuDQogKiBUaGUgZGVmYXVsdCBpcyAnLWxnbWFsbG9jJyB1bmxlc3Mg aXMgc3BlY2lmaWVkIGluIHRoZSBPUydzIC5jZiBmaWxlLg0KICoNCiNkZWZp bmUgR251TWFsbG9jTGlicmFyeQktTC91c3IvbG9jYWwvbGliIC1sZ21hbGxv Yw0KICovDQoNCi8qDQogKiBUbyBkaXNhYmxlIHRoZSBpbnRlcm5hbCBYc2Vy dmVyIG1hbGxvYywgc2V0IHRoaXMgdG8gTk8NCiAqDQojZGVmaW5lIFVzZUlu dGVybmFsTWFsbG9jCVlFUw0KICovDQoNCi8qDQogKiBTb21lIExpbnV4IHJl bGVhc2VzIGRvbid0IGhhdmUgYSBsaWJ0ZXJtY2FwLiAgSW4gdGhpcyBjYXNl IHlvdSBtYXkgbmVlZA0KICogdG8gdW5jb21tZW50IHRoZSBmb2xsb3dpbmcN CiAqDQojZGVmaW5lIFRlcm1jYXBMaWJyYXJ5CQktbG5jdXJzZXMNCiAqLw0K DQovKg0KICogSWYgeW91IGhhdmUgVGsgKHdoaWNoIGlzIHJlcXVpcmVkIHRv IGJ1aWxkIFhGODZTZXR1cCksIHVuY29tbWVudCB0aGlzDQogKiBOb3RlOiB2 ZXJzaW9uIDQuMCBvciA0LjEgaXMgcmVxdWlyZWQsIGFuZCBYRjg2U2V0dXAg bGlua3MgaXQgc3RhdGljYWxseSBieQ0KICogZGVmYXVsdC4NCiAqDQojZGVm aW5lIEhhc1RrCQkJWUVTDQogKi8NCg0KLyoNCiAqIFNldCB0aGUgcGF0aHMg YW5kIG5hbWVzIGZvciB5b3VyIFRrIGxpYnJhcnkgaWYgdGhleSBkb24ndCBt YXRjaCB0aGUNCiAqIGRlZmF1bHRzIChjaGVjayB5b3VyIE9TIC5jZiBmaWxl IG9yIEltYWtlLnRtcGwgZm9yIHRoZSBkZWZhdWx0cykuDQogKg0KICogQ29t bW9uIHZhbHVlcyBmb3IgVGtMaWJOYW1lIGFyZSB0azQuMCwgdGs0LjEsIGV0 Yy4NCiAqDQogKiBTb21lIExpbnV4IHJlbGVhc2VzIG5lZWQgVGtJbmNEaXIg c2V0IHRvIC91c3IvaW5jbHVkZS90Y2wsIGFuZCBzb21lDQogKiBuZWVkIGl0 IHNldCB0byAvdXNyL1gxMVI2L2luY2x1ZGUuDQogKg0KICogU29tZSBMaW51 eCByZWxlYXNlcyBuZWVkIFRrTGliRGlyIHNldCB0byAvdXNyL1gxMVI2L2xp Yg0KICoNCiNkZWZpbmUgVGtMaWJEaXIJCS91c3IvbG9jYWwvbGliDQojZGVm aW5lIFRrSW5jRGlyCQkvdXNyL2xvY2FsL2luY2x1ZGUNCiNkZWZpbmUgVGtM aWJOYW1lCQl0aw0KICovDQoNCi8qDQogKiBCeSBkZWZhdWx0LCBYRjg2U2V0 dXAgaXMgbGlua2VkIHdpdGggYSBzdGF0aWMgVGsgbGlicmFyeS4gIFRvIGNo YW5nZQ0KICogdGhhdCwgdW5jb21tZW50IHRoZSBmb2xsb3dpbmcgbGluZS4N CiAqDQojZGVmaW5lIFhGODZTZXR1cFVzZXNTdGF0aWNUawlOTw0KICovDQoN Ci8qDQogKiBJZiB5b3UgaGF2ZSBUY2wgKHdoaWNoIGlzIHJlcXVpcmVkIHRv IGJ1aWxkIFhGODZTZXR1cCksIHVuY29tbWVudCB0aGlzDQogKiBOb3RlOiB2 ZXJzaW9uIDcuNCBvciA3LjUgaXMgcmVxdWlyZWQsIGFuZCBYRjg2U2V0dXAg bGlua3MgaXQgc3RhdGljYWxseSBieQ0KICogZGVmYXVsdC4NCiAqDQojZGVm aW5lIEhhc1RjbAkJCVlFUw0KICovDQoNCi8qDQogKiBTZXQgdGhlIHBhdGhz IGFuZCBuYW1lcyBmb3IgeW91ciBUY2wgbGlicmFyeSBpZiB0aGV5IGRvbid0 IG1hdGNoIHRoZQ0KICogZGVmYXVsdHMgKGNoZWNrIHlvdXIgT1MgLmNmIGZp bGUgb3IgSW1ha2UudG1wbCBmb3IgdGhlIGRlZmF1bHRzKS4NCiAqDQogKiBD b21tb24gdmFsdWVzIGZvciBUY2xMaWJOYW1lIGFyZSB0Y2w3LjQsIHRjbDcu NSwgZXRjLg0KICoNCiAqIFNvbWUgTGludXggcmVsZWFzZXMgbmVlZCBUY2xJ bmNEaXIgc2V0IHRvIC91c3IvaW5jbHVkZS90Y2wuDQogKg0KI2RlZmluZSBU Y2xMaWJEaXIJCS91c3IvbG9jYWwvbGliDQojZGVmaW5lIFRjbEluY0RpcgkJ L3Vzci9sb2NhbC9pbmNsdWRlDQojZGVmaW5lIFRjbExpYk5hbWUJCXRjbA0K ICovDQoNCi8qDQogKiBCeSBkZWZhdWx0LCBYRjg2U2V0dXAgaXMgbGlua2Vk IHdpdGggYSBzdGF0aWMgVGNsIGxpYnJhcnkuICBUbyBjaGFuZ2UNCiAqIHRo YXQsIHVuY29tbWVudCB0aGUgZm9sbG93aW5nIGxpbmUuDQogKg0KI2RlZmlu ZSBYRjg2U2V0dXBVc2VzU3RhdGljVGNsCU5PDQogKi8NCg0KLyoNCiAqIEJ1 aWxkIGEgc2VydmVyIHRoYXQgZHluYW1pY2FsbHkgbG9hZHMgdGhlIG1vZHVs ZXMgYnkgc2V0dGluZw0KICogdGhpcyB0byBZRVMuICBUaGlzIGRlZmF1bHRz IHRvIFlFUyBvbiBtb3N0IHBsYXRmb3Jtcy4gIEEgc3RhdGljIHNlcnZlcg0K ICogY2FuIGJlIGJ1aWx0IGJ5IHNldHRpbmcgdGhpcyB0byBOTy4NCiAqDQoj ZGVmaW5lIERvTG9hZGFibGVTZXJ2ZXIJTk8NCiAqLw0KDQovKg0KICogQnVp bGQgZGxvcGVuKCkgc3R5bGUgbW9kdWxlcyBpbnN0ZWFkIG9mIHRoZSBzdGFu ZGFyZCBsb2FkZXIgbW9kdWxlcy4NCiAqDQogKi8NCiNkZWZpbmUgTWFrZURs bE1vZHVsZXMJCVlFUw0KDQovKg0KICogV2hpY2ggc2VydmVycyB0byBidWls ZC4gIFRoZXJlIGlzIG5vdyBvbmx5IG9uZSBYRnJlZTg2IHNlcnZlci4NCiAq IEl0IGNhbiBiZSBkaXNhYmxlZCBieSB0aGUgZm9sbG93aW5nLg0KICoNCiNk ZWZpbmUgWEY4NlNlcnZlcgkJTk8NCiAqLw0KDQovKg0KICogVG8gZGlzYWJs ZSBidWlsZGluZyB0aGUgWG5lc3Qgc2VydmVyLCB1bmNvbW1lbnQgdGhpcy4N CiAqDQojZGVmaW5lIFhuZXN0U2VydmVyCQlOTw0KICovDQoNCi8qDQogKiBU byBkaXNhYmxlIGJ1aWxkaW5nIFh2ZmIsIHVuY29tbWVudCB0aGlzLg0KICoN CiNkZWZpbmUgWFZpcnR1YWxGcmFtZWJ1ZmZlclNlcnZlcglOTw0KICovDQoN Ci8qDQogKiBUbyBkaXNhYmxlIGJ1aWxkaW5nIFhwcnQsIHVuY29tbWVudCB0 aGlzLg0KICoNCiNkZWZpbmUgWHBydFNlcnZlciBOTw0KICovDQoNCi8qDQog KiBTZXQgdGhlIGRlZmF1bHQgc2VydmVyIChpZSB0aGUgb25lIHRoYXQgZ2V0 cyB0aGUgc3ltLWxpbmsgdG8gIlgiKQ0KICoNCiNkZWZpbmUgU2VydmVyVG9J bnN0YWxsCQlYRnJlZTg2DQogKi8NCg0KDQovKg0KICogU2VydmVyIGNvbmZp Z3VyYXRpb24gcGFyYW1ldGVycy4gIFRoZSBkZWZhdWx0cyBhcmUgc2hvd24g aGVyZToNCiAqLw0KDQovKg0KICogV2hpY2ggZHJpdmVycyB0byBidWlsZC4g IFdoZW4gYnVpbGRpbmcgYSBzdGF0aWMgc2VydmVyLCBlYWNoIG9mIHRoZXNl DQogKiB3aWxsIGJlIGluY2x1ZGVkIGluIGl0LiAgV2hlbiBidWlsZGluZyB0 aGUgbG9hZGFibGUgc2VydmVyIGVhY2ggb2YgdGhlc2UNCiAqIG1vZHVsZXMg d2lsbCBiZSBidWlsdC4NCiAqDQojZGVmaW5lIFhGODZDYXJkRHJpdmVycwkJ bWdhIGdsaW50IG52IHRnYSBzM3ZpcmdlIHNpcyByZW5kaXRpb24gXA0KCQkJ CW5lb21hZ2ljIGk3NDAgdGRmeCBcDQoJCQkJY2lycnVzIHRzZW5nIHRyaWRl bnQgY2hpcHMgYXBtIFwNCgkJCQlHbGlkZURyaXZlciBmYmRldiBcDQoJCQkJ YXRpIHIxMjggdmdhIFhGODZFeHRyYUNhcmREcml2ZXJzDQogKi8NCg0KLyoN CiAqIEJ1aWxkIFhBQS4gIFRoaXMgY2FuIGJlIGRpc2FibGVkIHdpdGg6DQog Kg0KI2RlZmluZSBYRjg2WEFBCQkJTk8NCiAqLw0KDQovKg0KICogQnVpbGQg dmdhaHcuICBUaGlzIGNhbiBiZSBkaXNhYmxlZCB3aXRoOg0KICoNCiNkZWZp bmUgWEY4NlZnYUh3CQlOTw0KICovDQoNCi8qDQogKiBCdWlsZCB4ZjFicHAu ICBUaGlzIGNhbiBiZSBkaXNhYmxlZCB3aXRoOg0KICoNCiNkZWZpbmUgWEYx QnBwCQkJTk8NCiAqLw0KDQovKg0KICogQnVpbGQgeGY0YnBwLiAgVGhpcyBj YW4gYmUgZGlzYWJsZWQgd2l0aDoNCiAqDQojZGVmaW5lIFhGNEJwcAkJCU5P DQogKi8NCg0KDQovKg0KICogQlNEIENvbnNvbGUgZHJpdmVyIHN1cHBvcnQg KGZvciBGcmVlQlNEIGFuZCBOZXRCU0QpLg0KICoNCiAqIEJ5IGRlZmF1bHQs IHN1cHBvcnQgaXMgaW5jbHVkZWQgZm9yIHBjY29ucyBhbmQgcGN2dCBmb3Ig TmV0QlNELCBhbmQNCiAqIHBjY29ucywgc3lzY29ucyBhbmQgcGN2dCBmb3Ig RnJlZUJTRC4NCiAqDQogKiBUbyBjaGFuZ2UgdGhlIGxpc3Qgb2Ygc3VwcG9y dGVkIGRyaXZlcnMsIHNldCB0aGUgZm9sbG93aW5nIHBhcmFtZXRlci4NCiAq IFBvc3NpYmxlIHZhbHVlcyBhcmUgLURQQ0NPTlNfU1VQUE9SVCwgLURTWVND T05TX1NVUFBPUlQsIC1EUENWVF9TVVBQT1JULg0KICogVGhlIGZvbGxvd2lu ZyBleGFtcGxlIGluY2x1ZGVzIHN1cHBvcnQgZm9yIHN5c2NvbnMgYW5kIHBj dnQgb25seS4NCiAqDQojZGVmaW5lIFhGcmVlODZDb25zb2xlRGVmaW5lcwkt RFNZU0NPTlNfU1VQUE9SVCAtRFBDVlRfU1VQUE9SVA0KICovDQoNCi8qDQog KiBJZiB5b3Ugb25seSBydW4gdGhlIFggc2VydmVyIHVuZGVyIHhkbSB0aGUg WCBzZXJ2ZXJzIGRvbid0IG5lZWQgdG8gYmUNCiAqIGluc3RhbGxlZCBTZXRV SUQsIGFuZCB5b3UgbWF5IGNvbW1lbnQgb3V0IHRoZSBsaW5lcyBiZWxvdy4g IElmIHlvdSBydW4NCiAqIHRoZSBzZXJ2ZXJzIGJ5IGhhbmQgKHdpdGggeGlu aXQgb3Igc3RhcnR4KSwgdGhlbiB0aGV5IGRvIG5lZWQgdG8gYmUNCiAqIGlu c3RhbGxlZCBTZXRVSUQgb24gbW9zdCBPU3MuDQogKiBDb25zdWx0IHlvdXIg c3lzdGVtIGFkbWluaXN0cmF0b3IgYmVmb3JlIG1ha2luZyB0aGUgWCBzZXJ2 ZXIgc2V0dWlkLg0KICoNCiNkZWZpbmUgSW5zdGFsbFhzZXJ2ZXJTZXRVSUQJ Tk8NCiAqLw0KDQovKg0KICogVG8gZGlzYWJsZSBidWlsZGluZyB0aGUgZm9u dCBzZXJ2ZXIsIHVuY29tbWVudCB0aGlzLg0KICoNCiNkZWZpbmUgQnVpbGRG b250U2VydmVyCQlOTw0KICovDQoNCi8qDQogKiBUbyBkaXNhYmxlIHN1cHBv cnQgZm9yIFNwZWVkbyBmb250cywgdW5jb21tZW50IHRoaXMuDQogKg0KI2Rl ZmluZSBCdWlsZFNwZWVkbwkJTk8NCiAqLw0KDQovKg0KICogVG8gZGlzYWJs ZSBzdXBwb3J0IGZvciBUeXBlMSBmb250cywgdW5jb21tZW50IHRoaXMuDQog Kg0KI2RlZmluZSBCdWlsZFR5cGUxCQlOTw0KICovDQoNCi8qDQogKiBUbyBk aXNhYmxlIHN1cHBvcnQgZm9yIENJRCBmb250cywgdW5jb21tZW50IHRoaXMu DQogKg0KI2RlZmluZSBCdWlsZENJRAkJTk8NCiAqLw0KDQovKg0KICogVG8g ZGlzYWJsZSBzdXBwb3J0IGZvciBUcnVlVHlwZSBmb250cywgdW5jb21tZW50 IHRoZXNlLg0KICoNCiNkZWZpbmUgQnVpbGRGcmVlVHlwZQkJTk8NCiNkZWZp bmUgQnVpbGRYVFQJCU5PDQogKi8NCg0KLyoNCiAqIERvIHlvdSB3YW50IHRv IEJ1aWxkIEZvbnRzIChVc3VhbGx5IHlvdSBvbmx5IHdhbnQgdG8gYnVpbGQg YW5kIGluc3RhbGwNCiAqIGZvbnRzIG9uY2UsIGlmIHRoaXMgaXMgYSBmaXJz dCB0aW1lIGluc3RhbGwgeW91IHdpbGwgd2FudCB0byBidWlsZCB0aGUNCiAq IGZvbnRzKQ0KICoNCiNkZWZpbmUgQnVpbGRGb250cwkJTk8NCiAqLw0KDQov Kg0KICogVG8gbm90IGJ1aWxkL2luc3RhbGwgdGhlIDc1ZHBpIGZvbnRzLCB1 bmNvbW1lbnQgdGhlIGZvbGxvd2luZw0KICoNCiNkZWZpbmUgQnVpbGQ3NURw aUZvbnRzCQlOTw0KICovDQoNCi8qDQogKiBUbyBub3QgYnVpbGQvaW5zdGFs bCB0aGUgMTAwZHBpIGZvbnRzLCB1bmNvbW1lbnQgdGhlIGZvbGxvd2luZw0K ICoNCiNkZWZpbmUgQnVpbGQxMDBEcGlGb250cwlOTw0KICovDQoNCi8qDQog KiBUbyBub3QgYnVpbGQvaW5zdGFsbCB0aGUgU3BlZWRvIGZvbnRzLCB1bmNv bW1lbnQgdGhlIGZvbGxvd2luZw0KICoNCiNkZWZpbmUgQnVpbGRTcGVlZG9G b250cwlOTw0KICovDQoNCi8qDQogKiBUbyBub3QgYnVpbGQvaW5zdGFsbCB0 aGUgVHlwZTEgZm9udHMsIHVuY29tbWVudCB0aGUgZm9sbG93aW5nDQogKg0K I2RlZmluZSBCdWlsZFR5cGUxRm9udHMJCU5PDQogKi8NCg0KLyoNCiAqIFRv IG5vdCBidWlsZC9pbnN0YWxsIHRoZSBDSUQgZm9udHMsIHVuY29tbWVudCB0 aGUgZm9sbG93aW5nDQogKg0KI2RlZmluZSBCdWlsZENJREZvbnRzCQlOTw0K ICovDQoNCi8qDQogKiBUbyBub3QgYnVpbGQvaW5zdGFsbCB0aGUgQ3lyaWxs aWMgZm9udHMsIHVuY29tbWVudCB0aGUgZm9sbG93aW5nDQogKg0KI2RlZmlu ZSBCdWlsZEN5cmlsbGljRm9udHMJTk8NCiAqLw0KDQovKg0KICogVG8gbm90 IGJ1aWxkL2luc3RhbGwgdGhlIExhdGluMiBmb250cywgdW5jb21tZW50IHRo ZSBmb2xsb3dpbmcNCiAqDQojZGVmaW5lIEJ1aWxkTGF0aW4yRm9udHMJTk8N CiAqLw0KDQovKg0KICogVG8gbm90IGluc3RhbGwgdGhlIGxvY2FsIGZvbnQg ZGlyZWN0b3J5LCB1bmNvbW1lbnQgdGhlIGZvbGxvd2luZw0KICoNCiNkZWZp bmUgTWFrZUxvY2FsRm9udERpcglOTw0KICovDQoNCi8qDQogKiBUbyBidWls ZCBvbmx5IHRoZSBzZXJ2ZXJzIHdpdGggYSBjdXQtZG93biBzb3VyY2UgdHJl ZSwgdW5jb21tZW50DQogKiB0aGlzLg0KICoNCiNkZWZpbmUgQnVpbGRTZXJ2 ZXJzT25seQlZRVMNCiAqLw0KDQovKg0KICogVG8gZGlzYWJsZSBidWlsZGlu ZyBYSW5wdXQgc3VwcG9ydCwgdW5jb21tZW50IHRoaXMNCiAqDQojZGVmaW5l IEJ1aWxkWElucHV0RXh0CQlOTw0KICovDQoNCi8qDQogKiBTZWxlY3QgdGhl IFhJbnB1dCBkZXZpY2VzIHlvdSB3YW50IGJ5IHVuY29tbWVudGluZyB0aGlz Lg0KICoNCiNkZWZpbmUgWElucHV0RHJpdmVycyBkeW5hcHJvIGVsbzIzMDAg ZWxvZ3JhcGhpY3MgbWFnZWxsYW4gbWljcm90b3VjaCBcDQoJbXV0b3VjaCBz cGFjZW9yYiB3YWNvbQ0KICovDQoNCi8qDQogKiBVbmNvbW1lbnQgdGhpcyBm b3Igam95c3RpY2sgc3VwcG9ydC4NCiAqDQogKiBOb3RlOiBKb3lzdGljayBz dXBwb3J0IGlzIG9ubHkgaW5jbHVkZWQgZm9yIExpbnV4IGFuZCBGcmVlQlNE IGF0IHRoZQ0KICogbW9tZW50LiAgRm9yIExpbnV4IGl0IHJlcXVpcmVzIHRo ZSBKb3lzdGljayBtb2R1bGUgdG8gYmUgaW5zdGFsbGVkIChpdA0KICogaXNu J3QgcGFydCBvZiB0aGUgc3RhbmRhcmQga2VybmVsIGRpc3RyaWJ1dGlvbiku ICBGb3IgRnJlZUJTRCwgYSBrZXJuZWwNCiAqIHdpbGwgbmVlZCB0byBiZSBi dWlsdCB3aXRoIHRoZSBKb3lzdGljayBkcml2ZXIgaW4gb3JkZXIgdG8gYmUg YWJsZSB0bw0KICogdXNlIHRoaXMuDQogKg0KI2RlZmluZSBKb3lzdGlja1N1 cHBvcnQgWUVTDQogKi8NCg0KLyoNCiAqIFRvIGRpc2FibGUgdGhlIFNjcmVl blNhdmVyIEV4dGVuc2lvbiwgdW5jb21tZW50IHRoaXMgbGluZS4NCiAqDQoj ZGVmaW5lIEJ1aWxkU2NyZWVuU2F2ZXJFeHQJTk8NCiAqLw0KDQovKg0KICog SWYgeW91IGRvbid0IHdhbnQgdG8gYnVpbGQgUEVYLCB1bmNvbW1lbnQgdGhp cy4NCiAqDQojZGVmaW5lIEJ1aWxkUGV4RXh0CQlOTw0KICovDQoNCi8qIA0K ICogSWYgeW91IGRvbid0IHdhbnQgdG8gYnVpbGQgWGluZXJhbWEgc3VwcG9y dCwgdW5jb21tZW50IHRoaXMuDQogKg0KI2RlZmluZSBCdWlsZFhpbmVyYW1h CQlOTw0KICovDQoNCi8qDQogKiBJZiB5b3UgZG9uJ3Qgd2FudCB0byBidWls ZCBzdXBwb3J0IGZvciBhbiBleHRlcm5hbCBHTFggc2VydmVyIG1vZHVsZSBv cg0KICogbGlicmFyeSwgdW5jb21tZW50IHRoaXMuDQogKg0KI2RlZmluZSBC dWlsZEdseEV4dCAgICAgICAgICAgICBOTw0KICovDQoNCi8qDQogKiBJZiB5 b3Ugd2FudCB0byBidWlsZCBzdXBwb3J0IGZvciB0aGUgb2xkIGRsb3BlbiBz dHlsZSBleHRlcm5hbCBHTFgNCiAqIHNlcnZlciBtb2R1bGUgb3IgbGlicmFy eSwgdW5jb21tZW50IHRoaXMuDQogKg0KICovDQojZGVmaW5lIEdseFN0dWJM aWIgICAgICAgICAgICAgIFlFUw0KDQovKg0KICogSWYgeW91IGFyZW4ndCBi dWlsZGluZyB3aXRoIHN1cHBvcnQgZm9yIGxvYWRhYmxlIG1vZHVsZXMgYW5k IHdpc2gNCiAqIHRvIHN0YXRpY2FsbHkgbGluayBleHRlcm5hbCBHTFggc2Vy dmVyIGxpYnMgaW5zdGVhZCBvZiB0aGUgZGVmYXVsdA0KICogbm9uLWZ1bmN0 aW9uYWwgc3R1YiBsaWJyYXJ5LCB1bmNvbW1lbnQgdGhlIGZvbGxvd2luZyBk ZWZpbmUgYW5kDQogKiBzcGVjaWZ5IHRoZSBzcGFjZS1zZXBlcmF0ZWQgcGF0 aG5hbWVzIG9mIHRob3NlIGxpYnJhcmllcyBoZXJlLg0KICoNCiNkZWZpbmUg R2x4U3RhdGljU2VydmVyTGliCS9mdWxsL3BhdGgvbmFtZS90by9nbHgvc2Vy dkdML2xpYlNlcnZlckdseC5hIFwNCgkJCQkvZnVsbC9wYXRoL25hbWUvdG8v Z2x4L3NlcnZHTC9saWJNZXNhR2x4LmENCiAqLw0KDQovKg0KICogSWYgeW91 IGRvbid0IHdhbnQgdG8gYnVpbGQgWElFLCB1bmNvbW1lbnQgdGhpcy4NCiAq DQojZGVmaW5lIEJ1aWxkWElFCQlOTw0KICovDQoNCi8qDQogKiBJZiB5b3Ug d2FudCB0byBidWlsZCBvbmx5IHRoZSBESVMgKERvY3VtZW50IEltYWdpbmcg U3Vic2V0IG9mIFhJRSkNCiAqIHVuY29tbWVudCB0aGlzIGxpbmUuICBUaGlz IG9wdGlvbiBpcyBvbmx5IHJlbGV2YW50IHdoZW4gWElFIGlzIGJ1aWx0Lg0K ICoNCiNkZWZpbmUgQnVpbGRESVMJCVlFUw0KICovDQoNCi8qDQogKiBJZiB5 b3UgZG9uJ3Qgd2FudCB0byBidWlsZCB0aGUgeGY4NnJ1c2ggZXh0ZW5zaW9u LCB1bmNvbW1lbnQgdGhpcyBsaW5lLg0KICoNCiNkZWZpbmUgQnVpbGRYRjg2 UnVzaEV4dAlOTw0KICovDQoNCi8qDQogKiBJZiB5b3UgZG9uJ3Qgd2FudCB0 byBidWlsZCB0aGUgY2xpZW50IGxpYnJhcnkgZm9yIHRoZSB4Zjg2cnVzaCBl eHRlbnNpb24sDQogKiB1bmNvbW1lbnQgdGhpcyBsaW5lLg0KICoNCiNkZWZp bmUgQnVpbGRYRjg2UnVzaExpYnJhcnkJTk8NCiAqLw0KDQovKg0KICogQnkg ZGVmYXVsdCwgdGhlIHNhbXBsZSBjb25maWcgZmlsZXMgZm9yIHhpbml0LCB4 ZG0gYW5kIHhmcyBhcmUgaW5zdGFsbGVkDQogKiBvbmx5IHdoZW4gdGhlcmUg aXMgbm8gcHJlLWV4aXN0aW5nIHZlcnNpb24gaW5zdGFsbGVkLiAgVW5jb21t ZW50aW5nIHRoZQ0KICogZm9sbG93aW5nIGxpbmVzIHdpbGwgZm9yY2UgdGhl IHNhbXBsZSB2ZXJzaW9ucyB0byBiZSBpbnN0YWxsZWQgZXZlbiBpZg0KICog aXQgbWVhbnMgb3Zlci13cml0aW5nIGV4aXN0aW5nIHZlcnNpb25zLg0KICoN CiNkZWZpbmUgSW5zdGFsbFhpbml0Q29uZmlnCVlFUw0KI2RlZmluZSBJbnN0 YWxsWGRtQ29uZmlnCVlFUw0KI2RlZmluZSBJbnN0YWxsRlNDb25maWcJCVlF Uw0KICovDQoNCi8qDQogKiBCeSBkZWZhdWx0IHRoZSBhcHBsaWNhdGlvbiBk ZWZhdWx0cyBmaWxlcyBhcmUgYWx3YXlzIGluc3RhbGxlZC4NCiAqIFVuY29t bWVudGluZyB0aGUgdGhlIGZvbGxvd2luZyB3aWxsIHByZXZlbnQgZXhpc2lu ZyBhcHBsaWNhdGlvbg0KICogZGVmYXVsdHMgZmlsZXMgZnJvbSBiZWluZyBv dmVyLXdyaXR0ZW4uDQogKg0KI2RlZmluZSBJbnN0YWxsQXBwRGVmRmlsZXMJ Tk8NCiAqLw0KDQovKg0KICogSWYgeW91IGFyZSBydW5uaW5nIE5ldEJTRCAw LjlDIG9yIGxhdGVyLCBhbmQgaGF2ZSB0aGUgYXBlcnR1cmUgZHJpdmVyDQog KiBpbnN0YWxsZWQsIHVuY29tbWVudCB0aGlzLg0KICoNCiNkZWZpbmUgSGFz TmV0QlNEQXBlcnR1cmVEcml2ZXIJWUVTDQogKi8NCg0KLyoNCiAqIElmIHlv dSBhcmUgcnVubmluZyBTVlIzIGFuZCBoYXZlIHRoZSBtbWFwIGRyaXZlciBp bnN0YWxsZWQgKGZvciBsaW5lYXINCiAqIGZyYW1lYnVmZmVyIGFjY2Vzcykg dW5jb21tZW50IHRoaXMuDQogKg0KI2RlZmluZSBIYXNTVlIzbW1hcERydglZ RVMNCiAqLw0KDQovKg0KICogSWYgeW91IGFyZSB1c2luZyBhbiBTVlIzIChs aWtlIElTQyA0LngpIHdoaWNoIHN1cHBvcnRzIGxvbmcgZmlsZSBuYW1lcywN CiAqIHlvdSBjYW4gKiB1bmNvbW1lbnQgdGhpcyB0byBoYXZlIG1hbnVhbCBw YWdlcyBpbnN0YWxsZWQgdW5kZXIgdGhlaXINCiAqIGZ1bGwgbmFtZXMNCiAq DQogKi8NCiNkZWZpbmUgRXhwYW5kTWFuTmFtZXMJCVlFUw0KDQovKg0KICog Rm9yIGEgUE9TSVhpemVkIGJ1aWxkIG9uIEludGVyYWN0aXZlIHVuY29tbWVu dCB0aGlzDQogKiBDb3VsZCBiZSB1c2VkIHdpdGggZ2NjICd0aWxsIFZlcnNp b24gMi42LjMNCiAqIFNob3VsZCBiZSB1c2VkIHdpdGggZ2NjIDIuNy4yLiAN CiAqDQojZGVmaW5lIFVzZVBvc2l4CQlZRVMNCiAqLw0KDQovKg0KICogSWYg eW91IHdhbnQgWERNQVVUSCBzdXBwb3J0IChpZiB5b3UgaGF2ZSBXcmFwaGVs cC5jKSwgdW5jb21tZW50IHRoaXMuDQogKg0KI2RlZmluZSBIYXNYZG1BdXRo CQlZRVMNCiAqLw0KDQovKg0KICogSWYgeW91IGhhdmUgTGludXggREVDbmV0 IHN1cHBvcnQsIGFuZCB3YW50IHRvIGJ1aWxkIFhGcmVlODYgd2l0aCBzdXBw b3J0DQogKiBmb3IgY29ubmVjdGlvbnMgb3ZlciBERUNuZXQsIHVuY29tbWVu dCB0aGlzLg0KICoNCiNkZWZpbmUgSGFzREVDbmV0CQlZRVMNCiAqLw0KDQov Kg0KICogVG8gYnVpbGQgc3RhdGljIGFuZCBzaGFyZWQgbGlicmFyaWVzIHdp dGggZGVidWdnaW5nIGluZm9ybWF0aW9uLCB1bmNvbW1lbnQNCiAqIHRoaXMu IEFzc3VtZXMgeW91IGhhdmUgR2NjMi4NCiAqIChJZiB5b3UgZG9uJ3QgaGF2 ZSBHY2MyLCB5b3UgY2FuIHVzZSB0aGUgRGVidWdMaWJ7WDExLFh0LFhhdywu Li59IHZhcmlhYmxlcw0KICogdG8gYnVpbGQgZGVidWdnaW5nIHZlcnNpb25z IG9mIHRoZSBsaWJyYXJpZXMgc2VwYXJhdGVseS4pDQogKg0KI2RlZmluZSBE ZWJ1Z2dhYmxlTGlicmFyaWVzCVlFUw0KKi8NCg0KLyoNCiAqIFRvIGZvcmNl YWJseSBidWlsZCBzdGF0aWMgbGlicmFyaWVzIGluIGFkZGl0aW9uIHRvIHNo YXJlZCBsaWJyYXJpZXMsDQogKiB1bmNvbW1lbnQgdGhpcy4NCiAqDQogKi8N CiNkZWZpbmUgRm9yY2VOb3JtYWxMaWIJCVlFUw0KDQovKg0KICogVW5jb21t ZW50IHRoaXMgaWYgeW91ciBkZWZhdWx0IHRvb2xzIChlZywgZ2NjLCBsZCwg YXMsIGV0YykgYXJlDQogKiBub3QgdGhlIExpbnV4IEVMRiB2ZXJzaW9ucy4N CiAqDQojZGVmaW5lIExpbnV4RWxmRGVmYXVsdAkJTk8NCiAqLw0KDQovKg0K ICogVG8gdXNlIEVMRiBmb3JtYXQgc2hhcmVkIGxpYnJhcmllcyBmb3Igc3Vw cG9ydGVkIE9TcywgdW5jb21tZW50IHRoaXMuDQogKg0KICogRm9yIExpbnV4 IHRoZSBkZWZhdWx0IHNldHRpbmcgb2YgdGhpcyBpcyB0aGUgc2FtZSBhcyB0 aGUgc2V0dGluZyBvZg0KICogTGludXhFbGZEZWZhdWx0Lg0KICoNCiAqIEZv ciBGcmVlQlNEIHRoaXMgc2hvdWxkIGF1dG9tYXRpY2FsbHkgYmUgc2V0IGNv cnJlY3RseSBieSBpbWFrZS4gIE9ubHkNCiAqIGNoYW5nZSBpdCBoZXJlIGlm IHlvdSBuZWVkIHRvIG92ZXJyaWRlIHRoZSBhdXRvbWF0aWMgc2V0dGluZy4N CiAqDQojZGVmaW5lIFVzZUVsZkZvcm1hdAkJWUVTDQogKi8NCg0KLyoNCiAq IEZvciBGcmVlQlNEL0VMRiAoRnJlZUJTRCAzLjApIGl0IGlzIHBvc3NpYmxl IHRvIGFsc28gYnVpbGQgYW5kIGluc3RhbGwNCiAqIGEub3V0IGNvbXBhdGli aWxpdHkgbGlicmFyaWVzLiAgVG8gZW5hYmxlIHRoYXQsIHVuY29tbWVudCB0 aGlzLg0KICoNCiAqLw0KI2RlZmluZSBCdWlsZEFvdXRMaWJyYXJpZXMJWUVT DQoNCi8qDQogKiBJZiB5b3UgaGF2ZSB0cm91YmxlIHdpdGggbWFrZSBib21i aW5nIG91dCBpbiBYbGliLCB0cnkgdW5jb21tZW50aW5nIHRoaXMuDQogKiBZ b3Ugd2lsbCBub3QgZ2V0IGRlcGVuZGVuY2llcyBhcyBhIHJlc3VsdCwgYnV0 IGJldHRlciB0aGFuIG5vdGhpbmcuDQogKg0KI2RlZmluZSBNYWtlSGFzaFRh YmxlQnVnICAgICAgICBZRVMNCiAqLw0KDQovKg0KICogSWYgeW91IGRvIG5v dCB3YW50IHlvdXIgbWFuIHBhZ2VzIGNvbXByZXNzIHVuZGVyIFNWUjMgc3lz dGVtcyB0aGF0DQogKiBzdXBwb3J0IGl0LCB1bmNvbW1lbnQgdGhpcy4NCiAq DQojZGVmaW5lIENvbXByZXNzTWFuUGFnZXMgICAgICAgIE5PDQogKi8NCg0K LyoNCiAqIElmIHlvdSBoYXZlIHNnbWxmbXQgKHRoZSBYRnJlZTg2IGRvY3Rv b2xzIHBhY2thZ2UpIGFuZCB3YW50IHRvIGJ1aWxkDQogKiBmb3JtYXR0ZWQg ZG9jcyBmcm9tIHRoZSBTR01MIHNvdXJjZSwgdW5jb21tZW50IHRoaXMuDQog Kg0KI2RlZmluZSBIYXNTZ21sRm10CQlZRVMNCiAqLw0KDQovKg0KICogVG8g ZGlzYWJsZSBidWlsZGluZyBzb21lIGRvY3VtZW50IGZvcm1hdHMsIHVuY29t bWVudCBzb21lIG9mIHRoZXNlLg0KICoNCiNkZWZpbmUgQnVpbGRMaW51eERv Y1RleHQJTk8NCiNkZWZpbmUgQnVpbGRMaW51eERvY0h0bWwJTk8NCiNkZWZp bmUgQnVpbGRMaW51eERvY1BTCQlOTw0KICovDQoNCi8qDQogKiBUbyBpbnN0 YWxsIEphcGFuZXNlIHZlcnNpb25zIG9mIHRoZSBkb2N1bWVudGF0aW9uIHVu Y29tbWVudCB0aGlzLg0KICogTm90ZTogVGhlIEphcGFuZXNlIGRvY3VtZW50 YXRpb24gY29uc2lzdHMgb2YgYSBzdWJzZXQgb2YgdGhlDQogKiBYRnJlZTg2 IDMuMSBkb2NzLg0KICoNCiNkZWZpbmUgSW5zdGFsbEphcGFuZXNlRG9jcwlZ RVMNCiAqLw0KDQovKg0KICogQnkgZGVmYXVsdCwgWEY4NkNvbnRyaWIgaXMg ZGVmaW5lZCBzbyBidWlsZCBvbmx5IHRob3NlIHBhcnRzIG9mDQogKiBvZiB0 aGUgY29udHJpYiBkaXN0cmlidXRpb24gc3VwcG9ydGVkIGJ5IFhGcmVlODYu ICBUbyBwcmV2ZW50IHRoaXMNCiAqIGZyb20gYmVpbmcgZGVmaW5lZCwgdW5j b21tZW50IHRoZSBmb2xsb3dpbmcuDQogKg0KI2RlZmluZSBEb250RGVmaW5l WEY4NkNvbnRyaWINCiAqLw0KDQovKiANCiAqIFRvIGVuYWJsZSBidWlsZGlu ZyB0aGUgZ2xpZGUgZHJpdmVyLCB5b3UgbmVlZCB0byBkZWZpbmUgDQogKiBI YXNHbGlkZSB0byBZRVMgYW5kIHNldCB0aGUgR2xpZGVJbmNEaXIgdmFyaWFi bGUuIA0KICogSGFzR2xpZGUgaXMgcGVyIGRlZmF1bHQgTk8uDQogKg0KI2Rl ZmluZSBIYXNHbGlkZSBZRVMNCiAqLw0KDQovKg0KICogU2V0IHRoZSBwYXRo IHRvIHlvdXIgR2xpZGUgaW5jbHVkZSBmaWxlcy4NCiAqDQojZGVmaW5lIEds aWRlSW5jRGlyIC91c3IvaW5jbHVkZS9nbGlkZQ0KICovDQoNCi8qDQogKiBJ ZiB5b3VyIHN5c3RlbSBkb2Vzbid0IHN1cHBvcnQgdm04NigpIG1vZGUgYW5k IHlvdSBoYXZlDQogKiBsaWJ4ODZlbXUgc2V0IGxpYnJhcnkgcGF0aCBoZXJl DQogKg0KI2RlZmluZSBYODZFTVVfTElCUEFUSCAvdXNyL2xvY2FsL2xpYg0K ICovIA0K --0-656450158-951362296=:95548-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 19:39:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id D3F2C37BA9E for ; Wed, 23 Feb 2000 19:39:09 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id WAA13814; Wed, 23 Feb 2000 22:06:56 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA10606; Wed, 23 Feb 2000 22:06:59 -0500 (EST) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA10602; Wed, 23 Feb 2000 22:06:59 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Wed, 23 Feb 2000 22:06:59 -0500 (EST) From: Kenneth Wayne Culver To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: XFree86 3.9.18 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's odd... I just built it tonight, and I havn't had anything but this: XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 Which doesn't cause the server to crash, in fact, it seems pretty stable. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 23 Feb 2000, Donn Miller wrote: > I've built this thing on -current recently, and I'l getting the weirdest > errors when I try to start X: > > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > Elf_RelocateEntry() Unsupported relocation type 4 > Elf_RelocateEntry() Unsupported relocation type 3 > Elf_RelocateEntry() Unsupported relocation type 4 > Elf_RelocateEntry() Unsupported relocation type 9 > Elf_RelocateEntry() Unsupported relocation type 9 > Elf_RelocateEntry() Unsupported relocation type 4 > Elf_RelocateEntry() Unsupported relocation type 4 > Elf_RelocateEntry() Unsupported relocation type 4 > Elf_RelocateEntry() Unsupported relocation type 9 > Elf_RelocateEntry() Unsupported relocation type 9 > Elf_RelocateEntry() Unsupported relocation type 9 > > > - Donn > > > > 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 Feb 23 20:33:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 4D39F37BC23 for ; Wed, 23 Feb 2000 20:33:40 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id WAA36776; Wed, 23 Feb 2000 22:32:08 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200002240432.WAA36776@celery.dragondata.com> Subject: Re: XFree86 3.9.18 To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Wed, 23 Feb 2000 22:32:08 -0600 (CST) Cc: dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG In-Reply-To: from "Kenneth Wayne Culver" at Feb 23, 2000 10:06:59 PM X-Mailer: ELM [version 2.5 PL1] 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 > > That's odd... I just built it tonight, and I havn't had anything but this: > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > Which doesn't cause the server to crash, in fact, it seems pretty stable. > 24 EMFILE Too many open files. Getdtablesize(2) will obtain the current limit. You can probably bump up your ulimit, and make this go away, too. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 21:56:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 15FD537BAEB for ; Wed, 23 Feb 2000 21:56:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA34592; Wed, 23 Feb 2000 21:56:35 -0800 (PST) (envelope-from dillon) Date: Wed, 23 Feb 2000 21:56:35 -0800 (PST) From: Matthew Dillon Message-Id: <200002240556.VAA34592@apollo.backplane.com> To: Matthew Dillon Cc: Ian Dowse , nops@maths.tcd.ie, freebsd-current@FreeBSD.ORG, diablo-list@list.bart.nl Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) References: <200002232235.aa22335@salmon.maths.tcd.ie> <200002240227.SAA33299@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Ian's test script >>> mount_mfs -T fd1440 none /mnt cd /mnt dd if=/dev/zero bs=4k of=test seek=1036 count=1 dd if=/dev/zero bs=4k of=test1 count=1 dd if=/dev/zero bs=4k of=test2 rm test1 dd if=/dev/zero bs=4k of=test seek=8000 count=1 echo > test <<<<<<<<<<<<<<<<<<<<<<<<< Oops, here's a new version of my patch. This one survives Ian's test script. I was improperly blowing away an 'error' field. -Matt Index: ffs_balloc.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_balloc.c,v retrieving revision 1.25 diff -u -r1.25 ffs_balloc.c --- ffs_balloc.c 2000/01/11 08:27:00 1.25 +++ ffs_balloc.c 2000/02/24 05:44:59 @@ -77,6 +77,7 @@ ufs_daddr_t newb, *bap, pref; int deallocated, osize, nsize, num, i, error; ufs_daddr_t *allocib, *blkp, *allocblk, allociblk[NIADDR + 1]; + int unwindidx = -1; struct proc *p = curproc; /* XXX */ vp = ap->a_vp; @@ -272,6 +273,8 @@ } } bap[indirs[i - 1].in_off] = nb; + if (allocib == NULL && unwindidx < 0) + unwindidx = i - 1; /* * If required, write synchronously, otherwise use * delayed write. @@ -349,8 +352,28 @@ ffs_blkfree(ip, *blkp, fs->fs_bsize); deallocated += fs->fs_bsize; } - if (allocib != NULL) + if (allocib != NULL) { *allocib = 0; + } else if (unwindidx >= 0) { + int r; + + r = bread(vp, indirs[unwindidx].in_lbn, + (int)fs->fs_bsize, NOCRED, &bp); + if (r) { + panic("Could not unwind indirect block, error %d", error); + brelse(bp); + } else { + bap = (ufs_daddr_t *)bp->b_data; + bap[indirs[unwindidx].in_off] = 0; + if (flags & B_SYNC) { + bwrite(bp); + } else { + if (bp->b_bufsize == fs->fs_bsize) + bp->b_flags |= B_CLUSTEROK; + bdwrite(bp); + } + } + } if (deallocated) { #ifdef QUOTA /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 22:25:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4212937BB0C; Wed, 23 Feb 2000 22:25:50 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id WAA09550; Wed, 23 Feb 2000 22:55:06 -0800 (PST) Date: Wed, 23 Feb 2000 22:55:06 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Ian Dowse , mckusick@freebsd.org, current@freebsd.org Subject: Re: ffs_blkfree: freeing free block (was Re: Panic (pmap)) Message-ID: <20000223225505.A21720@fw.wintelcom.net> References: <200002232235.aa22335@salmon.maths.tcd.ie> <200002240227.SAA33299@apollo.backplane.com> <200002240556.VAA34592@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002240556.VAA34592@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 23, 2000 at 09:56:35PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Er, shouldn't you guys let Kirk know, not only is he "MAINTAINER", but pretty much mostly "CREATOR" :) Kirk, another issue with running out of space in FFS seems to have come up: * Matthew Dillon [000223 18:57] wrote: > :Ian Dowse wrote: > :I think I've found it. Here's an easy way to repeat the problem to > :start with: > : > : mount_mfs -T fd1440 none /mnt > : cd /mnt > : dd if=/dev/zero bs=4k of=test seek=1036 count=1 > : dd if=/dev/zero bs=4k of=test1 count=1 > : dd if=/dev/zero bs=4k of=test2 > : rm test1 > : dd if=/dev/zero bs=4k of=test seek=8000 count=1 > : echo > test > : > :It looks as if the problem is in ffs_balloc(), and occurs as follows: > : - ffs_balloc() is asked to allocate a doubly indirect block. > : - The first-level indirection block already exists > : - The second-level indirection block does not exist, but is > : successfully allocated. > : - This block is linked into the first-level indirection block by > : the line: > : > : bap[indirs[i - 1].in_off] = nb; > : > : - Allocation of the data block fails. > : - All allocated blocks are then released, but there is still > : a link in the first-level indirection block to what is > : now a free block. > : > :The fix should be relatively straightforward - either the code should > :avoid linking new indirection blocks until all allocations succeed, > :or it should back out the changes on failure. > : > :Ian > > Great detective work! The 'allocib' variable is used to unwind the > 'first' new indirect block allocation, but it is *only* initialized > for the Level 0 block. So the unwinding only works when the Level 0 > indirect block had to be allocated. When the Level 0 indirect block > is valid and a deeper level indirect block had to be allocated, > allocib is not initialized and the association is not unwound even > though the deeper indirect block is freed when the data block allocation > fails. > > Unfortunately, we can't simply initialize 'allocib' here, because it > would point into the middle of a buffer. The fix is thus not entirely > trivial. > > This is what I think we need to do, but THIS PATCH IS NOT TESTED AND > COULD BE COMPLETELY WRONG. Any filesystem gurus out there who can look > at this and tell me if it's correct? [patch snipped, Matt just re-issued a fixed version] * Matthew Dillon [000223 22:26] wrote: > > Oops, here's a new version of my patch. This one survives Ian's test > script. I was improperly blowing away an 'error' field. > > -Matt > > Index: ffs_balloc.c > =================================================================== > RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_balloc.c,v > retrieving revision 1.25 > diff -u -r1.25 ffs_balloc.c > --- ffs_balloc.c 2000/01/11 08:27:00 1.25 > +++ ffs_balloc.c 2000/02/24 05:44:59 > @@ -77,6 +77,7 @@ > ufs_daddr_t newb, *bap, pref; > int deallocated, osize, nsize, num, i, error; > ufs_daddr_t *allocib, *blkp, *allocblk, allociblk[NIADDR + 1]; > + int unwindidx = -1; > struct proc *p = curproc; /* XXX */ > > vp = ap->a_vp; > @@ -272,6 +273,8 @@ > } > } > bap[indirs[i - 1].in_off] = nb; > + if (allocib == NULL && unwindidx < 0) > + unwindidx = i - 1; > /* > * If required, write synchronously, otherwise use > * delayed write. > @@ -349,8 +352,28 @@ > ffs_blkfree(ip, *blkp, fs->fs_bsize); > deallocated += fs->fs_bsize; > } > - if (allocib != NULL) > + if (allocib != NULL) { > *allocib = 0; > + } else if (unwindidx >= 0) { > + int r; > + > + r = bread(vp, indirs[unwindidx].in_lbn, > + (int)fs->fs_bsize, NOCRED, &bp); > + if (r) { > + panic("Could not unwind indirect block, error %d", error); > + brelse(bp); > + } else { > + bap = (ufs_daddr_t *)bp->b_data; > + bap[indirs[unwindidx].in_off] = 0; > + if (flags & B_SYNC) { > + bwrite(bp); > + } else { > + if (bp->b_bufsize == fs->fs_bsize) > + bp->b_flags |= B_CLUSTEROK; > + bdwrite(bp); > + } > + } > + } > if (deallocated) { > #ifdef QUOTA > /* > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 22:40:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id F335637BB33 for ; Wed, 23 Feb 2000 22:40:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00785; Wed, 23 Feb 2000 22:53:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002240653.WAA00785@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: karsten@rohrbach.de, freebsd-current@FreeBSD.ORG Subject: Re: Panic #3 (ffs) (MegaRAID) In-reply-to: Your message of "Wed, 23 Feb 2000 14:37:25 EST." <3.0.5.32.20000223143725.01c6ecb0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Feb 2000 22:53:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 08:30 PM 2/23/00 +0100, Karsten W. Rohrbach wrote: > >which megaraid adapter do you use in this box (hw, fw ver, bios ver, > >cntl-m ver)... > > > >i've seen those panics on our old news box when there where errors on > >the scsi busses which did not get detected properly. mainly termination > >issues *sigh* > > I dont think its necessarily a termination issue. I have swapped the exact > same chain onto a Mylex DAC960 and can pound the box without issue. I have > a nasty feeling my 466 might not like my MB chipset. I am using a 466 > PERC2/SC on BX chipset ECS MB and its throwing all sorts of fits. When I > used a 428 on another box (a plain old Pentium), I didnt have nearly this > many problems. Soon as my co-worker is finished with the older Pentium, I > can test this theory to see if this is the case. Looking at the release > notes for the BIOS revs at AMI, it seems older BIOS revs might have > problems with newer MBs > > >From ftp://ftp.megatrends.com/MegaRAID/drivers/466/readme-gh6d.txt > >Changes in this release: > >----------------------- > >1. CTRL-M is not invoked until after the system BIOS is completed > > on newer systems that support PMM (POST Memory Management). > > The system would hang at different places in CTRL-M on these > > systems prior to these changes. > > Until I flashed it to this new rev, I was seeing this behaviour. Just to reiterate; I can reliably hang the 466 running with this firmware within a few minutes under the 'amr' driver, while the Dell 3.00 firmware doesn't demonstrate the config-time hangs on any system I've run it on and is also not susceptible to the hang problems. I've been a little distracted with various Mylex-related issues for a little bit now, and am still waiting for some response from AMI before returning to work on these problems. I'm also in need of a more or less permanent loan of a 434 or 438 (preferably) controller as all I have right now are 418/428/466 and Karsten's been reporting issues with all of the 438's firmware. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 23 23:37:54 2000 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 B461737BB60 for ; Wed, 23 Feb 2000 23:37:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA94541 for ; Wed, 23 Feb 2000 23:37:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Heads up! OpenSSH is about to enter the tree. Date: Wed, 23 Feb 2000 23:37:55 -0800 Message-ID: <94538.951377875@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since it came down to making openssl actually useful for something or taking it out of the tree, we accelerated progress somewhat on the openssh integration work. This is using the rsarefglue stubs I've been talking about for the last couple of days to "abstract" rsaref away so we don't have any RSA bundling issues. Users can load the appropriate rsaref package (or install the port) and openssl-using packages like openssh will then "just work." This work will take place in 3 stages: 1. Mark Murray will bring his openssh work into -current. 2. A lot of fur will fly around while a few things are tweaked. 3. John Polstra and others will work on integrating changes for the static compilation case. Dynamic linking of rsaref works fine, dealing with static linking requires a bit more finesse and we've already worked out what we need to do for this step. I will also be delaying -current's release date until March 10th in order to give this more proper testing. Yes, I know this is a rather stunning development for a code base supposedly in code freeze, but special situations sometimes merit special dispensation and this is one such situation. I think the merits of having ssh in the base system far outweigh the risks of bringing it in right now and I'll be fully supporting this work in a number of ways intended to minimize those risks even further. It's my neck and I'm sticking it out. :) Watch this 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 Feb 24 0: 4:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 8146737BB51; Thu, 24 Feb 2000 00:04:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA00465; Thu, 24 Feb 2000 00:17:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002240817.AAA00465@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Yarema Cc: FreeBSD Current , sos@FreeBSD.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Wed, 23 Feb 2000 15:10:20 EST." <38B43EAC.75158BE0@dppl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 00:17:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Forgive me if I'm beating a dead horse... I'm still having the following > problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. Soren - this is somewhat of a showstopper. Can you reproduce it there? > ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR > ata0-slave: ata_command: timeout waiting for intr > ata0-slave: identify failed > no devsw (majdev=0 bootdev=0xa0400000) > Mounting root from ufs:/dev/ad0s3a > no such device 'ad' > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > > If at the boot prompt I: > > unload > load kernel > boot > > there's no problem. Also there's no problem if loading modules from > /boot/loader.conf with a kernel suped and built on Feb. 17th with > today's buildworld. > > Mike Smith wrote: > > > > > > it does : I've tried > > > loading miibus alone : works fine > > > loading miibus, then if_xl : loops in loading miibus > > > > Ok. We know that hurts, don't do that. 8) > > > > >From the above remark should I conclude that it's a known problem and we > should refrain from loading modules from the boot loader until it works? > Or would it help send boot_verbose output from my kernel as well? > > -- > Yarema > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 0: 5:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B28537BB75 for ; Thu, 24 Feb 2000 00:05:33 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-8.iptelecom.net.ua [212.9.227.72]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA10313 for ; Thu, 24 Feb 2000 10:06:45 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA29492 for ; Thu, 24 Feb 2000 10:04:30 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38B4E609.9AB33280@altavista.net> Date: Thu, 24 Feb 2000 10:04:25 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: /usr/share/examples/kld/cdev broken Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems that /usr/share/examples/kld/cdev example is broken for a long time, which obviously not we want for 4.0-RELEASE. Could someone review my docs/16173 PR and commit it with corrections if it will be necessary (I'm really not very prominent as a kld hacker)? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 0:15:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id F3CA537BB5F; Thu, 24 Feb 2000 00:15:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA00518; Thu, 24 Feb 2000 00:26:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002240826.AAA00518@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) In-reply-to: Your message of "Wed, 23 Feb 2000 19:10:42 EST." <4.2.2.20000223190830.03b74b88@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 00:26:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware > > > >up within a few minutes. The Dell 3.00 firmware remains stable under the > > > >same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a > > > >firmware lockup - the SCSI bus is hung and usually the PCI bus as well. > > > > > > I am going to test the card in another older MB to see if its some strange > > > interaction. What MB chipset are you using to test with ? > > > >I've been testing most recently with the Intel 450NX and AMD 751. > > OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes > with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but > it crashes hard when you write to the partition. I am going to try and > reflash the card to the latest AMI BIOS and see what happens. How about with FreeBSD and the Dell firmware? Let's keep the number of variables down. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 0:45:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 89D6937BB20; Thu, 24 Feb 2000 00:45:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA86244; Thu, 24 Feb 2000 09:45:04 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002240845.JAA86244@freebsd.dk> Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002240817.AAA00465@mass.cdrom.com> from Mike Smith at "Feb 24, 2000 00:17:40 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 24 Feb 2000 09:45:04 +0100 (CET) Cc: yds@dppl.com (Yarema), FreeBSD-Current@FreeBSD.ORG (FreeBSD Current), sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Mike Smith wrote: > > Forgive me if I'm beating a dead horse... I'm still having the following > > problem if I load any modules from /boot/loader.conf: > > I've reproduced this here, and narrowed it down to Soren's ATA megacommit > on the 18th. Unfortunately, the newbus patches (tested) and the other > gunk (untested) ended up lumped in together, and I'm not having a lot of > luck working out what exactly might be causing this. That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. > Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? We've seen this before, but back then no solution was found either, it dissaperead all by itself... > > ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR > > ata0-slave: ata_command: timeout waiting for intr > > ata0-slave: identify failed -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 0:52:15 2000 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 8B33F37BB45 for ; Thu, 24 Feb 2000 00:52:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA94850; Thu, 24 Feb 2000 00:51:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Forrest Aldrich Cc: Chris Piazza , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: USA_RESIDENT= in latest current In-reply-to: Your message of "Wed, 23 Feb 2000 16:57:21 EST." <20000223165721.B6809@drama.navinet.net> Date: Thu, 24 Feb 2000 00:51:11 -0800 Message-ID: <94847.951382271@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps, but take a look at the installation... it sets it > to USA_RESIDENT="YES" (note WITH quotes). Fixed, whoops! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 1: 0:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 89BD837BB45 for ; Thu, 24 Feb 2000 01:00:40 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id KAA05875; Thu, 24 Feb 2000 10:00:17 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id JAA74003; Thu, 24 Feb 2000 09:50:50 +0100 (CET) (envelope-from andreas) Date: Thu, 24 Feb 2000 09:50:50 +0100 From: Andreas Klemm To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting Message-ID: <20000224095049.A73506@titan.klemm.gtn.com> References: <20000223152130.A1583@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Thu, Feb 24, 2000 at 05:43:04AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 05:43:04AM +1100, Bruce Evans wrote: > > what do you mean exactly with "old systems" ? > FreeBSD-3.x, or FreeBSD--current with the wd driver. Oh, that you mean ... Well but I'm running a very up to date -current. FreeBSD titan.klemm.gtn.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Feb 22 12:11:23 CET 2000 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN i386 I even updated the boot loader by cd /usr/src/sys/boot make clean all install -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 1: 1:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 5FEFA37BAED; Thu, 24 Feb 2000 01:01:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12Nu8o-000Mhw-0X; Thu, 24 Feb 2000 09:00:59 +0000 Received: from tecra.nlsystems.com (tecra [10.0.0.5]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94982; Thu, 24 Feb 2000 09:04:02 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 24 Feb 2000 09:03:55 +0000 (GMT) From: Doug Rabson To: Soren Schmidt Cc: Mike Smith , Yarema , FreeBSD Current , sos@freebsd.org Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002240845.JAA86244@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Feb 2000, Soren Schmidt wrote: > It seems Mike Smith wrote: > > > Forgive me if I'm beating a dead horse... I'm still having the following > > > problem if I load any modules from /boot/loader.conf: > > > > I've reproduced this here, and narrowed it down to Soren's ATA megacommit > > on the 18th. Unfortunately, the newbus patches (tested) and the other > > gunk (untested) ended up lumped in together, and I'm not having a lot of > > luck working out what exactly might be causing this. > > That megapatch was only newbus patches and cosmetics around that, one > new item was cmd646 support but that is hardly the problem here. > > > Soren - this is somewhat of a showstopper. Can you reproduce it there? > > Nope, I've tried several machines here, no problems, even with tons > of modules.. > > The only thing I can come up with is that _something_ makes the > delayed probe be called _before_ interrupts are up and running. > That will make it fail like this. Quuestion is is something > else messing with those hooks ? > We've seen this before, but back then no solution was found either, > it dissaperead all by itself... Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. Nick spent a couple of hours looking at it without much success. I'll try some things today to see if the probe is being called with interrupts disabled. -- 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 Feb 24 1:18:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 19C7F37BB81; Thu, 24 Feb 2000 01:18:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA86366; Thu, 24 Feb 2000 10:18:28 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002240918.KAA86366@freebsd.dk> Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: from Doug Rabson at "Feb 24, 2000 09:03:55 am" To: dfr@nlsystems.com (Doug Rabson) Date: Thu, 24 Feb 2000 10:18:28 +0100 (CET) Cc: msmith@freebsd.org (Mike Smith), yds@dppl.com (Yarema), FreeBSD-Current@freebsd.org (FreeBSD Current), sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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: > > > > That megapatch was only newbus patches and cosmetics around that, one > > new item was cmd646 support but that is hardly the problem here. > > > > > Soren - this is somewhat of a showstopper. Can you reproduce it there? > > > > Nope, I've tried several machines here, no problems, even with tons > > of modules.. > > > > The only thing I can come up with is that _something_ makes the > > delayed probe be called _before_ interrupts are up and running. > > That will make it fail like this. Quuestion is is something > > else messing with those hooks ? > > We've seen this before, but back then no solution was found either, > > it dissaperead all by itself... > > Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. > Nick spent a couple of hours looking at it without much success. I'll try > some things today to see if the probe is being called with interrupts > disabled. My main dev box is an Athlon too, so that is not the problem. I still suspect missing interrupts... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 1:19:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 1FF0A37BEE6 for ; Thu, 24 Feb 2000 01:19:12 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12NuQK-000LPq-0U; Thu, 24 Feb 2000 09:19:04 +0000 Received: from tecra.nlsystems.com (tecra [10.0.0.5]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA16468; Thu, 24 Feb 2000 09:21:22 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 24 Feb 2000 09:21:14 +0000 (GMT) From: Doug Rabson To: Kevin Day Cc: Kenneth Wayne Culver , Donn Miller , current@freebsd.org Subject: Re: XFree86 3.9.18 In-Reply-To: <200002240432.WAA36776@celery.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, Kevin Day wrote: > > > > That's odd... I just built it tonight, and I havn't had anything but this: > > > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 > > > > Which doesn't cause the server to crash, in fact, it seems pretty stable. > > > > 24 EMFILE Too many open files. open files per process is 64.> Getdtablesize(2) will obtain the > current limit. > > > > You can probably bump up your ulimit, and make this go away, too. I'm pretty sure this error is generated when the server tries to use too many shared memory segments. -- 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 Feb 24 1:37:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 914EA37BB91 for ; Thu, 24 Feb 2000 01:37:55 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 48CEE2CE5F; Thu, 24 Feb 2000 11:37:51 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 0D7443D7; Thu, 24 Feb 2000 11:37:39 +0200 (EET) Date: Thu, 24 Feb 2000 11:37:38 +0200 From: Vallo Kallaste To: User URANIA Cc: freebsd-current@freebsd.org Subject: Re: Problem with IBM Netfinity 5000 Server Message-ID: <20000224113738.A59264@myhakas.matti.ee> Reply-To: vallo@matti.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from User URANIA on Wed, Feb 23, 2000 at 02:27:31PM +0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: > I've a Netfinity 5000 Server, internal 5 PCI slot onborad. > If i put one Intel 82558 NIC at 5th PCI Slot, everythings goes > fine. Every times i put the same Intel NIC to any other PCI > slots ( 1th ~ 4th ), after system login prompt , i also login > as root, then system direct reboot .... ><# > > I also set these flags at my /etc/make.conf > > # > CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations > # > # To avoid building various parts of the base system: > NO_SENDMAIL= true > #NO_CVS= true > # > # To compile just the kernel with special optimisations, you should use > # this instead of CFLAGS (which is not applicable to kernel builds anyway): > # > COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops Please forget the "special" optimization parameters and compile world and kernel with standard -O -pipe. Make sure you don't have any unusual tweaks anywhere. Then compile GENERIC kernel and try it out. I don't think the optimizing compiler is bad idea but I haven't seen any significant gains versus dying kernels and weird acting standard system binaries. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 2:38: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail1.geocities.com [209.1.224.29]) by hub.freebsd.org (Postfix) with ESMTP id E089C37BB5F for ; Thu, 24 Feb 2000 02:37:57 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg131-061.ricochet.net [204.179.131.61]) by geocities.com (8.9.3/8.9.3) with ESMTP id CAA21670 for ; Thu, 24 Feb 2000 02:37:59 -0800 (PST) Message-ID: <38B50B92.2D399CA3@geocities.com> Date: Thu, 24 Feb 2000 02:44:34 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: natd, firewall, and RFC1918...? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been wondering what the right answer to this scenario is. Here is the scenario: machine A -- outside ip (internet) machine B -- router, natd, registered ip and set to stop RFC1918 on the public interface machine C -- inside LAN, unregisterd ip 192.168.0.0/16 When I connect to machine A from machine C, machine B (natd) seems to translate the addresses correctly like this: Out [TCP] "machine C's ip" --> "machine A's ip" aliased to [TCP] "machine B's ip" --> "machine A's ip" but when the packet comes back in, I get this: In [TCP] "machine A's ip" --> "machine B's ip" aliased to [TCP] "machine A's ip" --> "machine C's ip" ^ ^ ^ ^ ^ ^ ^ ^ and this brakes my ipfw rule of: "deny ip from any to 192.168.0.0/16 via outside_interface" ... which is part of the example from rc.firewall "stopping RFC1918 on the public interface." So, I always just delete this rule to get the packet inside the LAN. questions are: 1. Is this right? Is natd behaving correctly when the packet comes back in for unregistered ips? I would think that it would be aliased to like this, "machine B's ip" --> machine C's ip".... like a proxy? But this would still break the rule "... from any ...". 2. If so, is it correct to not include the ipfw rule above when stopping RFC1918? Better yet, what is the correct way of writing the rule? correct me if my assumptions are wrong. using 4.0current-2000.02.14 --- arnee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 3: 4:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id A1B8F37BBBA for ; Thu, 24 Feb 2000 03:04:39 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 486131FD8; Thu, 24 Feb 2000 12:04:38 +0100 (CET) Date: Thu, 24 Feb 2000 12:04:38 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: dc0 wierdness with Compex Freedomline Message-ID: <20000224120438.A24299@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am experiencing some weird problems with the dc-driver for a specific ethernet-card ... the Compex Freedomline (10/100 Mbps). The card perfectly seems to autodetect the mode it should operate on and seems to indeed be working just fine just after the system has booted up. --[dmesg]------- dc0: port 0xb400-0xb47f mem 0xdd000000-0xdd00007f irq 11 at device 12.0 on pci0 dc0: Ethernet address: 00:80:48:e7:1a:8e miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto --[ifconfig]------ sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 dc0: flags=8843 mtu 1500 inet 130.89.226.126 netmask 0xffff0000 broadcast 130.89.255.255 ether 00:80:48:e7:1a:8e media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX none Downloading an 128 MB-file from the network to /dev/null results in speeds like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) After a (little) while though network performance almost comes to a halt somewhere around 6 to 32 kB/s ... and never seems to "recover" again. --[uname]------ FreeBSD cam043216.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Feb 19 10:29:30 CET 2000 dingo@cam043216.student.utwente.nl:/usr/src/sys/compile/DINGO i386 Anybody that could help me out trying to figure out why the card seems to break down like this ? -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 4: 7: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id 0EA3F37BBB2 for ; Thu, 24 Feb 2000 04:06:58 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg131-061.ricochet.net [204.179.131.61]) by geocities.com (8.9.3/8.9.3) with ESMTP id EAA00347 for ; Thu, 24 Feb 2000 04:07:00 -0800 (PST) Message-ID: <38B5206E.E84E7AC3@geocities.com> Date: Thu, 24 Feb 2000 04:13:34 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: natd, firewall, and RFC1918...? apologies! References: <38B50B92.2D399CA3@geocities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sorry, i'm suppose to post this under freebsd-questions. this should teach me posting early in the morning :-) To continue the questions... if the sample ipfw rule "deny all from any to 192.168.0.0/16 via outside_interfaces" doesn't always work. Should it be included in the rc.firewall example? arnee wrote: > I have been wondering what the right answer to this scenario is. Here is > the scenario: > > machine A -- outside ip (internet) > machine B -- router, natd, registered ip and set to stop RFC1918 on the > public interface > machine C -- inside LAN, unregisterd ip 192.168.0.0/16 > > When I connect to machine A from machine C, machine B (natd) seems to > translate the addresses correctly like this: > > Out [TCP] "machine C's ip" --> "machine A's ip" aliased to > [TCP] "machine B's ip" --> "machine A's ip" > > but when the packet comes back in, I get this: > > In [TCP] "machine A's ip" --> "machine B's ip" aliased to > [TCP] "machine A's ip" --> "machine C's ip" > ^ ^ ^ ^ ^ ^ ^ ^ > > and this brakes my ipfw rule of: > > "deny ip from any to 192.168.0.0/16 via outside_interface" ... which is > part of the example from rc.firewall "stopping RFC1918 on the public > interface." So, I always just delete this rule to get the packet inside > the LAN. > > questions are: > > 1. Is this right? Is natd behaving correctly when the packet comes back > in for unregistered ips? I would think that it would be aliased to like > this, "machine B's ip" --> machine C's ip".... like a proxy? But this > would still break the rule "... from any ...". > 2. If so, is it correct to not include the ipfw rule above when stopping > RFC1918? Better yet, what is the correct way of writing the rule? > > correct me if my assumptions are wrong. > > using 4.0current-2000.02.14 > --- > arnee > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 4: 9:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id AD5A137BBC5 for ; Thu, 24 Feb 2000 04:09:44 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id NAA28969 for ; Thu, 24 Feb 2000 13:10:01 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Thu, 24 Feb 2000 13:10:01 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: strange things ... Message-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 cvsup'd this morning the sources, the original installed system was 4.0-20000214. Built a new kernel, installed it, rebooted - locked out? Huh ... root's password won't run anymore and I have no glue why ... Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 4:21:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from teknos.teknos.com (teknos-gw.nappr.org [216.0.190.254]) by hub.freebsd.org (Postfix) with ESMTP id F2A2C37B905; Thu, 24 Feb 2000 04:21:38 -0800 (PST) (envelope-from salaman@teknos.com) Received: by teknos.teknos.com with Internet Mail Service (5.5.2650.21) id <19NW7153>; Thu, 24 Feb 2000 08:17:01 -0400 Message-ID: <1D45ABC754FB1E4888E508992CE97E4F059D04@teknos.teknos.com> From: "Victor A. Salaman" To: "'FreeBSD-current@freebsd.org'" Cc: "'sos@freebsd.dk'" , "'dfr@nlsystems.com'" , "'msmith@freebsd.org'" Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. Date: Thu, 24 Feb 2000 08:16:59 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF7EC1.0CE21540" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF7EC1.0CE21540 Content-Type: text/plain; charset="iso-8859-1" I'm also experiencing this under current since the Mega Patch, I'm running on Celeron 500. Asus P99B Board (2 IDE, 128MB Ram, 4.3 GB Hard Disk). But if I don't load any modules, it works fine. ------_=_NextPart_001_01BF7EC1.0CE21540 Content-Type: text/html; charset="iso-8859-1"
I'm also experiencing this under current since the Mega Patch, I'm running on Celeron 500. Asus P99B Board (2 IDE, 128MB Ram, 4.3 GB Hard Disk). But if I don't load any modules, it works fine.
------_=_NextPart_001_01BF7EC1.0CE21540-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 4:53:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id CC20937BCF0; Thu, 24 Feb 2000 04:53:32 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id HAA78568; Thu, 24 Feb 2000 07:53:30 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id HAA15919; Thu, 24 Feb 2000 07:53:29 -0500 (EST) Message-Id: <4.2.2.20000224074639.03308aa8@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 24 Feb 2000 07:51:25 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002240826.AAA00518@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:26 AM 2/24/2000 -0800, Mike Smith wrote: > > OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes > > with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but > > it crashes hard when you write to the partition. I am going to try and > > reflash the card to the latest AMI BIOS and see what happens. > >How about with FreeBSD and the Dell firmware? Let's keep the number of >variables down. 8) I cant disklabel the drive when using the 3.00 firmware from dell. newmail# disklabel -Brw amrd0 auto newmail# disklabel -e amrd0 disklabel: ioctl DIOCGDINFO: Invalid argument Its entirely possible the card is cooked. I am going to test the latest firmware with LINUX when I get back to the office today. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 4:58:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 42E3237BBDB for ; Thu, 24 Feb 2000 04:58:00 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id OAA17950; Thu, 24 Feb 2000 14:55:46 +0200 (EET) (envelope-from ru) Date: Thu, 24 Feb 2000 14:55:46 +0200 From: Ruslan Ermilov To: arnee Cc: freebsd-current@FreeBSD.ORG Subject: Re: natd, firewall, and RFC1918...? apologies! Message-ID: <20000224145546.A4465@relay.ucb.crimea.ua> Mail-Followup-To: arnee , freebsd-current@FreeBSD.ORG References: <38B50B92.2D399CA3@geocities.com> <38B5206E.E84E7AC3@geocities.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <38B5206E.E84E7AC3@geocities.com>; from arnee on Thu, Feb 24, 2000 at 04:13:34AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 04:13:34AM -0800, arnee wrote: > sorry, i'm suppose to post this under freebsd-questions. this should teach > me posting early in the morning :-) > > To continue the questions... if the sample ipfw rule "deny all from any to > 192.168.0.0/16 via outside_interfaces" doesn't always work. Should it be > included in the rc.firewall example? > Please see PR conf/13769 for the same problem and a possible workaround. Note, that: : After translation by natd, packets re-enter the firewall at the rule : number following the rule number that caused the diversion (not the : next rule if there are several at the same number). Depending on the actual config, there could be a clean solution for this problem. For example, I use dedicated IP number for NATD, and my NATD rules look very close to the following: # Outside interface ruleset ${IPFW} add 50000 skipto 60000 ip from any to ${ALIAS_IP} in ... # Stop RFC1918 nets usage on the outside interface ${IPFW} add reject log ip from ${RFC1918_A} to any ${IPFW} add reject log ip from ${RFC1918_B} to any ${IPFW} add reject log ip from ${RFC1918_C} to any ${IPFW} add deny log ip from any to ${RFC1918_A} ${IPFW} add deny log ip from any to ${RFC1918_B} ${IPFW} add deny log ip from any to ${RFC1918_C} ... # IP de-aliasing ${IPFW} add 60000 divert natd ip from any to ${ALIAS_IP} in # Deny & log everything that isn't de-aliased ${IPFW} add deny log ip from any to ${ALIAS_IP} in # Pass all that is de-aliased ${IPFW} add allow ip from any to any in Also, the description of how packets re-enter firewall filter provided in etc/rc.firewall is obsoleted and should be replaced to match the reality. I will fix that. If you have something to say further, please followup on PR 13769. > arnee wrote: > > > I have been wondering what the right answer to this scenario is. Here is > > the scenario: > > > > machine A -- outside ip (internet) > > machine B -- router, natd, registered ip and set to stop RFC1918 on the > > public interface > > machine C -- inside LAN, unregisterd ip 192.168.0.0/16 > > > > When I connect to machine A from machine C, machine B (natd) seems to > > translate the addresses correctly like this: > > > > Out [TCP] "machine C's ip" --> "machine A's ip" aliased to > > [TCP] "machine B's ip" --> "machine A's ip" > > > > but when the packet comes back in, I get this: > > > > In [TCP] "machine A's ip" --> "machine B's ip" aliased to > > [TCP] "machine A's ip" --> "machine C's ip" > > ^ ^ ^ ^ ^ ^ ^ ^ > > > > and this brakes my ipfw rule of: > > > > "deny ip from any to 192.168.0.0/16 via outside_interface" ... which is > > part of the example from rc.firewall "stopping RFC1918 on the public > > interface." So, I always just delete this rule to get the packet inside > > the LAN. > > > > questions are: > > > > 1. Is this right? Is natd behaving correctly when the packet comes back > > in for unregistered ips? I would think that it would be aliased to like > > this, "machine B's ip" --> machine C's ip".... like a proxy? But this > > would still break the rule "... from any ...". > > 2. If so, is it correct to not include the ipfw rule above when stopping > > RFC1918? Better yet, what is the correct way of writing the rule? > > > > correct me if my assumptions are wrong. > > > > using 4.0current-2000.02.14 > > --- > > arnee -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 7: 6:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 652AC37BD2D; Thu, 24 Feb 2000 07:06:50 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA98434; Thu, 24 Feb 2000 10:06:49 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000224100338.028e5590@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 24 Feb 2000 10:03:38 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002240826.AAA00518@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:26 AM 2/24/00 -0800, Mike Smith wrote: >> OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes >> with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but >> it crashes hard when you write to the partition. I am going to try and >> reflash the card to the latest AMI BIOS and see what happens. > >How about with FreeBSD and the Dell firmware? Let's keep the number of >variables down. 8) OK, I have flashed the BIOS of the card to the latest version from AMI, and booted it up with RedHAT (latest kernel compiled) with various patches, and the driver compiled directly into the kernel, not as a module. Note, these are the drivers that come with RedHAT. I havent tried the RPMs directly from AMI/Dell megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] [3.0 GB] Then tried /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & Its slow, but the server does not crash..... However, if Queing enabled, it does crash. However, this could be due to the old Segates ( ST31055W ) that I am using to test with. I did try the same on FreeBSD, but it did not have any positive effect. So it seems the card does work... ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 8:10: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay1.freightliner.com (relay1.freightliner.com [208.26.204.160]) by hub.freebsd.org (Postfix) with SMTP id B3DFE37BBC4 for ; Thu, 24 Feb 2000 08:10:02 -0800 (PST) (envelope-from BillWoods@Freightliner.com) Received: from 170.2.32.100 by relay1.freightliner.com with ESMTP ( relay1.freightliner.com(WSS) v4.0.2); Thu, 24 Feb 00 08:03:12 -0800 X-Server-Uuid: 3c925716-650e-11d2-99ea-002035296a3f Received: by corpowa1.freightliner.com with Internet Mail Service ( 5.5.2650.21) id <1TYB6J5M>; Thu, 24 Feb 2000 08:10:19 -0800 Message-ID: From: "Bill Woods" To: "'freebsd-current@freebsd.org'" Subject: http download of iso ?? Date: Thu, 24 Feb 2000 08:10:19 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-WSS-ID: 14AB89CA116413-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it possible to get the RC2 iso via http?? The reason I ask is that the > firewall here blocks ftp. > > PS...Please email directly as this address is not on the mailing list > > Thank you, > > William To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 8:43:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D3D6737BF1D; Thu, 24 Feb 2000 08:43:27 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id IAA06190; Thu, 24 Feb 2000 08:43:27 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 24 Feb 2000 08:43:26 -0800 (PST) From: Kris Kennaway To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: strange things ... 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, 24 Feb 2000, O. Hartmann wrote: > I cvsup'd this morning the sources, the original installed > system was 4.0-20000214. Built a new kernel, installed it, rebooted - > locked out? Huh ... root's password won't run anymore and I have no > glue why ... You were using DES crypt libraries but didn't install them in the upgrade. Add the "DES" distribution in sysinstall, or the crypto/ and secure/ source directories and rebuild. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 8:48:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (Postfix) with ESMTP id B568C37BC75; Thu, 24 Feb 2000 08:48:32 -0800 (PST) (envelope-from yds@dppl.com) Received: from dppl.com (avs.medianow.com [216.182.7.89]) by paris.dppl.com (Postfix) with ESMTP id 6A1629670; Thu, 24 Feb 2000 11:48:30 -0500 (EST) Message-ID: <38B560DD.2B002A4A@dppl.com> Date: Thu, 24 Feb 2000 11:48:30 -0500 From: Yarema X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en, uk, ru, ja MIME-Version: 1.0 To: Soren Schmidt Cc: Mike Smith , FreeBSD Current , sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. References: <200002240845.JAA86244@freebsd.dk> Content-Type: multipart/mixed; boundary="------------A8DC670B316E17F9EF5EF379" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------A8DC670B316E17F9EF5EF379 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Soren Schmidt wrote: > > It seems Mike Smith wrote: > > > Forgive me if I'm beating a dead horse... I'm still having the following > > > problem if I load any modules from /boot/loader.conf: > > > > I've reproduced this here, and narrowed it down to Soren's ATA megacommit > > on the 18th. Unfortunately, the newbus patches (tested) and the other > > gunk (untested) ended up lumped in together, and I'm not having a lot of > > luck working out what exactly might be causing this. > > That megapatch was only newbus patches and cosmetics around that, one > new item was cmd646 support but that is hardly the problem here. > > > Soren - this is somewhat of a showstopper. Can you reproduce it there? > > Nope, I've tried several machines here, no problems, even with tons > of modules.. > > The only thing I can come up with is that _something_ makes the > delayed probe be called _before_ interrupts are up and running. > That will make it fail like this. Quuestion is is something > else messing with those hooks ? > We've seen this before, but back then no solution was found either, > it dissaperead all by itself... > > -Søren Perhaps this will help. Attached is a copy of a boot_verbose dmesg when my box DOES boot. When it does NOT boot the screen shows something like this: ... Device configuration finished. bpf: lo0 attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default Linux-ELF exec handler installed IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/ad0s1a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 ... Seems like it craps out right after the linux module kicks in at 'Linux-ELF exec handler installed'. The platform in this case is a Celleron 466/ASUS MES-N/SiS® 620 AGPset. http://www.asus.com.tw/products/motherboard/pentiumpro/mes-n/index.html http://www.sis.com.tw/products/pentium2/620.htm Hope this helps. Incidentally ata(4) states: The currently supported controllers with their maximum speed include: ... SiS 5591 Ultra DMA 33 (UDMA2), 33 MB/sec ... yet the above URL claims: The IDE controller is ATA-3 compliant, supporting PIO mode 0/1/2/3/4, DMA multiword 0/1/2 and Ultra DMA 33/66 operations. The two IDE channels are fully independent with dedicated 16 double-word FIFO built-in. I understand there's little (if any) perfrmance difference between UDMA33 and UDMA66. Just wondering why UDMA66 was not supported for this controller. -- Yarema --------------A8DC670B316E17F9EF5EF379 Content-Type: text/plain; charset=us-ascii; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Wed Feb 23 11:03:02 EST 2000 root@reims.medianow.com:/usr/src/sys/compile/ASUSMESN Calibrating clock(s) ... TSC clock: 466827092 Hz, i8254 clock: 1193128 Hz Timecounter "i8254" frequency 1193128 Hz Timecounter "TSC" frequency 466827092 Hz CPU: Pentium II/Pentium II Xeon/Celeron (466.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 266326016 (260084K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00369000 - 0x0fdf4fff, 262717440 bytes (64140 pages) avail memory = 254541824 (248576K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f99d0 bios32: Entry = 0xf04c0 (c00f04c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x4f0 pnpbios: Found PnP BIOS data at 0xc00fca10 pnpbios: Entry = f0000:ca40 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f54a0 Preloaded elf kernel "kernel" at 0xc0350000. VESA: information block 56 45 53 41 00 02 00 01 00 01 04 00 00 00 22 00 00 01 20 00 00 01 14 01 00 01 36 01 00 01 40 01 00 01 00 01 01 01 03 01 05 01 07 01 21 01 80 01 81 01 82 01 89 01 8d 01 0d 01 10 01 13 01 16 01 VESA: 35 mode(s) found VESA: v2.0, 2048k memory, flags:0x4, mode table:0xc02f0ea2 (1000022) VESA: SiS VESA: Silicon Integrated Systems Corp. 6306 0A Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80010010 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=06201039) devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=06201039) pcib0: on motherboard found-> vendor=0x1039, dev=0x0620, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e6800000, size 22 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[10]: type 1, range 32, base 0000e400, size 3 map[14]: type 1, range 32, base 0000e000, size 2 map[18]: type 1, range 32, base 0000d800, size 3 map[1c]: type 1, range 32, base 0000d400, size 2 map[20]: type 1, range 32, base 0000d000, size 4 found-> vendor=0x1039, dev=0x0008, revid=0xb3 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x0009, revid=0x00 class=ff-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x7001, revid=0x11 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base e6000000, size 12 found-> vendor=0x1039, dev=0x0001, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base e5000000, size 12 map[14]: type 1, range 32, base 0000a800, size 6 map[18]: type 1, range 32, base e4800000, size 20 found-> vendor=0x1073, dev=0x000d, revid=0x03 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base e4000000, size 15 pci0: on pcib0 atapci0: port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 14 at device 0.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed isab0: at device 1.0 on pci0 isa0: on isab0 pci0: (vendor=0x1039, dev=0x0009) at 1.1 ohci0: mem 0xe6000000-0xe6000fff irq 15 at device 1.2 on pci0 ohci0: (New OHCI DeviceId=0x70011039) usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib2: at device 2.0 on pci0 found-> vendor=0x1039, dev=0x6306, revid=0x2a class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e7800000, size 23 map[14]: type 1, range 32, base e5800000, size 16 map[18]: type 1, range 32, base 0000b800, size 7 pci1: on pcib2 pci1: (vendor=0x1039, dev=0x6306) at 0.0 fxp0: port 0xa800-0xa83f mem 0xe4800000-0xe48fffff,0xe5000000-0xe5000fff irq 10 at device 3.0 on pci0 fxp0: Ethernet address 00:e0:18:e0:12:e1 bpf: fxp0 attached pci0: (vendor=0x1073, dev=0x000d) at 6.0 irq 12 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=06201039) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0001 psm0: strange result for test aux port (1). kbdc: RESET_AUX return code:ffffffff kbdc: RESET_AUX return code:ffffffff kbdc: RESET_AUX return code:ffffffff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 53 9f bf 1f 00 4f 0d 0e 00 00 07 80 9b 8d 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 53 9f bf 1f 00 4f 0d 0e 00 00 00 00 9b 8d 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 53 9f bf 1f 00 4f 0d 0e 00 00 00 00 9b 8d 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 sio0: irq maps: 0xc9 0xd9 0xc9 0xc9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0xc1 0xc9 0xc1 0xc1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default bpf: lo0 attached IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 ata0-master: success setting up UDMA2 mode on SiS chip ad0: ATA-5 disk at ata0 as master ad0: 26059MB (53369568 sectors), 52946 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 0, end = 53369567, size 53369568 : OK start_init: trying /sbin/init --------------A8DC670B316E17F9EF5EF379-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 9:20:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id 83CB037BCA1 for ; Thu, 24 Feb 2000 09:20:41 -0800 (PST) (envelope-from flatline@area51.v-wave.com) Received: (qmail 1850 invoked by uid 1001); 24 Feb 2000 17:21:31 -0000 Date: Thu, 24 Feb 2000 10:21:31 -0700 From: Chris Wasser To: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline Message-ID: <20000224102131.A1796@area51.v-wave.com> References: <20000224120438.A24299@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000224120438.A24299@shadowmere.student.utwente.nl>; from daeron@wit401305.student.utwente.nl on Thu, Feb 24, 2000 at 12:04:38PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 12:04:38PM +0100, Pascal Hofstee wrote: > media: autoselect (100baseTX ) > > Downloading an 128 MB-file from the network to /dev/null results in speeds > like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps->MB/s you divide by 8] I realize my punctuation may be off, but there you are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 9:29:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from math.udel.edu (math.udel.edu [128.175.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 9939137BC02 for ; Thu, 24 Feb 2000 09:29:51 -0800 (PST) (envelope-from schwenk@math.udel.edu) Received: from math.udel.edu (sisyphus.math.udel.edu [128.175.16.167]) by math.udel.edu (8.9.3+Sun/8.9.1) with ESMTP id MAA11090; Thu, 24 Feb 2000 12:29:46 -0500 (EST) Message-ID: <38B56A8A.6D8C53A2@math.udel.edu> Date: Thu, 24 Feb 2000 12:29:46 -0500 From: Peter Schwenk Organization: University of Delaware X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en, fr, de, ko MIME-Version: 1.0 To: Chris Wasser Cc: freebsd-current@freebsd.org Subject: Re: dc0 wierdness with Compex Freedomline References: <20000224120438.A24299@shadowmere.student.utwente.nl> <20000224102131.A1796@area51.v-wave.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't forget protocol overhead. Chris Wasser wrote: > On Thu, Feb 24, 2000 at 12:04:38PM +0100, Pascal Hofstee wrote: > > media: autoselect (100baseTX ) > > > > Downloading an 128 MB-file from the network to /dev/null results in speeds > > like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) > > The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s > (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps->MB/s you divide > by 8] I realize my punctuation may be off, but there you are. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- PETER SCHWENK | UNIX System Administrator Department of Mathematical Sciences | University of Delaware schwenk@math.udel.edu | (302)831-0437 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 9:55:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles503.castles.com [208.214.165.67]) by hub.freebsd.org (Postfix) with ESMTP id C332737BC78; Thu, 24 Feb 2000 09:55:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00424; Thu, 24 Feb 2000 10:07:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002241807.KAA00424@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: msmith@FreeBSD.ORG (Mike Smith), yds@dppl.com (Yarema), FreeBSD-Current@FreeBSD.ORG (FreeBSD Current), sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Thu, 24 Feb 2000 09:45:04 +0100." <200002240845.JAA86244@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 24 Feb 2000 10:07:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Mike Smith wrote: > > > Forgive me if I'm beating a dead horse... I'm still having the foll= owing > > > problem if I load any modules from /boot/loader.conf: > > = > > I've reproduced this here, and narrowed it down to Soren's ATA megaco= mmit = > > on the 18th. Unfortunately, the newbus patches (tested) and the othe= r = > > gunk (untested) ended up lumped in together, and I'm not having a lot= of = > > luck working out what exactly might be causing this. > = > That megapatch was only newbus patches and cosmetics around that, one > new item was cmd646 support but that is hardly the problem here. You didn't mention the 0xa5 test, and I forgot to tell you that I backed = it out as well (no change). > > Soren - this is somewhat of a showstopper. Can you reproduce it ther= e? > = > Nope, I've tried several machines here, no problems, even with tons > of modules.. Try a network interface module, if you haven't already. I was loading = if_wi. > The only thing I can come up with is that _something_ makes the > delayed probe be called _before_ interrupts are up and running. > That will make it fail like this. Quuestion is is something > else messing with those hooks ? That's possible; it may be that the kernel linker is calling something = before you expect it to be called. Also, I note that you've only partially newbussed the code; I don't see = any busspace/busdma stuff in there. Is there another megapatch coming? -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 10:22:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from snapple.webct.com (snapple.webct.com [209.87.17.45]) by hub.freebsd.org (Postfix) with ESMTP id 6D8FF37B8F2 for ; Thu, 24 Feb 2000 10:22:14 -0800 (PST) (envelope-from varju@snapple.webct.com) Received: (from varju@localhost) by snapple.webct.com (8.9.3/8.9.3) id KAA58605; Thu, 24 Feb 2000 10:17:54 -0800 (PST) (envelope-from varju) Date: Thu, 24 Feb 2000 10:17:54 -0800 (PST) From: Alex Varju To: current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: <200002222027.VAA11669@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 22 Feb 2000, Alexander Leidinger wrote: > But this didn't solve the crash at exit. But... > rm -rf /usr/lib/compat/* > cd /usr/src/lib/compat/compat22/ > make all install clean > cd ../compat3x.i386/ > make all install clean > solved this for me (YMMV). After doing this, I noticed some crud lying around on my machine that might have been contributing to problems for me. I noticed that the aout version of libc was coming from /usr/lib/aout, which I guess is an old place that libraries were kept. This is probably one more thing people can look for to ensure that they are using the newest versions of the compatibility libraries. Alex. -- alex varju just a guy webct canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 10:31:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3673337BDCB for ; Thu, 24 Feb 2000 10:31:50 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA417544; Thu, 24 Feb 2000 13:31:41 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <94538.951377875@zippy.cdrom.com> References: <94538.951377875@zippy.cdrom.com> Date: Thu, 24 Feb 2000 13:32:00 -0500 To: "Jordan K. Hubbard" , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Heads up! OpenSSH is about to enter the tree. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:37 PM -0800 2/23/00, Jordan K. Hubbard wrote: >Since it came down to making openssl actually useful for something or >taking it out of the tree, we accelerated progress somewhat on the >openssh integration work. Sounds like a good idea. >I will also be delaying -current's release date until March 10th in >order to give this more proper testing. I think it's worth the wait to have openssh included. One minor thought. In OpenBSD there is still a port for ssh1, and they have it so the port for ssh1 starts that up on port 2022. We (at RPI) have found a few ssh clients that do not work well with openssh, and I think it would be a good idea to do something similar to what openbsd did with the port for ssh1. (maybe not exactly the same -- maybe have it just some messages that the ssh1-build process will print out so people are aware of that option. 4.0-release wouldn't have to wait for those adjustments to the ssh1 port, of course) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 10:48:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id DA03837BCEF for ; Thu, 24 Feb 2000 10:48:38 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from xterminator.studfb.unibw-muenchen.de (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id TAA24144; Thu, 24 Feb 2000 19:48:36 +0100 (MET) Received: from didi (wintermute.STUDFB.UniBw-Muenchen.de [137.193.211.253]) by xterminator.studfb.unibw-muenchen.de (8.9.3/8.8.6) with SMTP id TAA09736; Thu, 24 Feb 2000 19:48:32 +0100 From: Dieter Rothacker To: Chris Wasser Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline Date: Thu, 24 Feb 2000 19:48:35 +0100 Organization: Organized ? No way... Message-ID: References: <20000224120438.A24299@shadowmere.student.utwente.nl> <20000224102131.A1796@area51.v-wave.com> In-Reply-To: <20000224102131.A1796@area51.v-wave.com> X-Mailer: Forte Agent 1.6/32.661 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser wrote: >> Downloading an 128 MB-file from the network to /dev/null results in speeds >> like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) > >The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s >(megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps->MB/s you divide >by 8] I realize my punctuation may be off, but there you are. No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX cables are used simultaneous. Due to the small ethernet frame size, it is next to impossible to get the full speed for data transmission. -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 11: 2:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 24A6037C2F5; Thu, 24 Feb 2000 11:02:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA05235; Thu, 24 Feb 2000 11:02:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA89500; Thu, 24 Feb 2000 11:02:45 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Feb 2000 11:02:44 -0800 From: "David O'Brien" To: Martin Cracauer Cc: Bruce Evans , jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000224110244.A89479@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000223100036.A4872@cons.org> <20000223143101.A5971@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000223143101.A5971@cons.org>; from cracauer@cons.org on Wed, Feb 23, 2000 at 02:31:01PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:31:01PM +0100, Martin Cracauer wrote: > Where's the bug, anyway? Do we need to fix the compiler or would it be > better to get a newer assembler? A new assembler (whole binutils) is on the way, probably around the end of March. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 11: 7:49 2000 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 61A7037C183 for ; Thu, 24 Feb 2000 11:07:44 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA27437; Thu, 24 Feb 2000 14:07:40 -0500 (EST) (envelope-from wollman) Date: Thu, 24 Feb 2000 14:07:40 -0500 (EST) From: Garrett Wollman Message-Id: <200002241907.OAA27437@khavrinen.lcs.mit.edu> To: Chris Wasser Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <20000224102131.A1796@area51.v-wave.com> References: <20000224120438.A24299@shadowmere.student.utwente.nl> <20000224102131.A1796@area51.v-wave.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s > (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps->MB/s you divide > by 8] I realize my punctuation may be off, but there you are. Assuming you mean ``100BASE-T (half duplex)'' here... This is not quite right. In a CSMA/CD medium access protocol, like that used by Ethernet, the actual capacity of the link is always(*) somewhat less than 100%; the exact value depends on the precise parameters of the transmissions at both ends.(**) -GAWollman (*)In non-trivial conditions; i.e., when actual work is being done. (**)I've heard numbers between 70% and 95%. -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 11:15:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id CE5F337BF1D for ; Thu, 24 Feb 2000 11:15:20 -0800 (PST) (envelope-from flatline@area51.v-wave.com) Received: (qmail 2437 invoked by uid 1001); 24 Feb 2000 19:16:11 -0000 Date: Thu, 24 Feb 2000 12:16:11 -0700 From: Chris Wasser To: Dieter Rothacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline Message-ID: <20000224121611.A2411@area51.v-wave.com> References: <20000224120438.A24299@shadowmere.student.utwente.nl> <20000224102131.A1796@area51.v-wave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from didi@Xterminator.STUDFB.UniBw-Muenchen.de on Thu, Feb 24, 2000 at 07:48:35PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 07:48:35PM +0100, Dieter Rothacker wrote: > No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get > 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX > cables are used simultaneous. Due to the small ethernet frame size, it is > next to impossible to get the full speed for data transmission. You're right, I stand corrected. FDX is 100Mbps wide, but bi-directional, so it's only 12MB/s maximum theoretical speed (not including protocol overhead and what-not) .. I was basing the original opinion posted on assumed total bandwidth (100Mbps both ways) which is incorrect. I apologize for my ignorance :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 11:20:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6344037BCD1; Thu, 24 Feb 2000 11:19:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA24133; Thu, 24 Feb 2000 20:19:55 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002241919.UAA24133@freebsd.dk> Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002241807.KAA00424@mass.cdrom.com> from Mike Smith at "Feb 24, 2000 10:07:16 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 24 Feb 2000 20:19:55 +0100 (CET) Cc: yds@dppl.com (Yarema), FreeBSD-Current@FreeBSD.ORG (FreeBSD Current), sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Mike Smith wrote: > > > > That megapatch was only newbus patches and cosmetics around that, one > > new item was cmd646 support but that is hardly the problem here. > > You didn't mention the 0xa5 test, and I forgot to tell you that I backed > it out as well (no change). yeah, cosmetics :) > > > Soren - this is somewhat of a showstopper. Can you reproduce it there? > > > > Nope, I've tried several machines here, no problems, even with tons > > of modules.. > > Try a network interface module, if you haven't already. I was loading > if_wi. Still no problems... > > The only thing I can come up with is that _something_ makes the > > delayed probe be called _before_ interrupts are up and running. > > That will make it fail like this. Quuestion is is something > > else messing with those hooks ? > > That's possible; it may be that the kernel linker is calling something > before you expect it to be called. Well, its rather that the delayed probe rutine I register with config_intrhook_establish() is called before interrupts are actually working, that would explain why it times out on the probe... This didn't happen before, so thats probably why it breaks... It should break SCSI systems too, ass they do the same... > Also, I note that you've only partially newbussed the code; I don't see > any busspace/busdma stuff in there. Is there another megapatch coming? Busspace is a joke, I'm perfectly fine with calling those macros in[bwl]/out[bwl] like they should be :) Busdma, hmm, well I dont see that helping here either.... And no, no more mega patches before 4.0, this should probably have waited too, but there has been pushed very stronly for this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 12:51:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 7EF0B37B891 for ; Thu, 24 Feb 2000 12:51:06 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 9529 invoked from network); 24 Feb 2000 20:50:53 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 24 Feb 2000 20:50:53 -0000 Date: Fri, 25 Feb 2000 07:50:49 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Dillon Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? In-Reply-To: <200002232043.MAA31642@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, 23 Feb 2000, Matthew Dillon wrote: [I wrote] > :See PR 16568. pmap_remove_all() doesn't flush the TLB properly in > :FreeBSD-3.x on i386's. Somehow this doesn't cause many problems, but > :it fairly reliably breaks the free() in fdfree() when there was a file > :descriptor larger than about 1000 (this gives a free() of more than > :MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. > Ahh. I presume you will commit this patch now that Bjoern has > confirmed that it works? Not until the reason that it works is understood. > I don't know why an unconditional invltlb() didn't work either, > it should have. Maybe the __asm macro is being optimized out. I verified that the unconditional invtlb() doesn't work. Better yet, replacing the invltlb_1pg() in the loop doesn't work. I think this means that we've changed the page tables too early for a page elsewhere. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 13: 6: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D023C37B9C0 for ; Thu, 24 Feb 2000 13:06:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA42378; Thu, 24 Feb 2000 13:05:58 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Feb 2000 13:05:58 -0800 (PST) From: Matthew Dillon Message-Id: <200002242105.NAA42378@apollo.backplane.com> To: Bruce Evans Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. : :> Ahh. I presume you will commit this patch now that Bjoern has :> confirmed that it works? : :Not until the reason that it works is understood. : :> I don't know why an unconditional invltlb() didn't work either, :> it should have. Maybe the __asm macro is being optimized out. : :I verified that the unconditional invtlb() doesn't work. Better yet, :replacing the invltlb_1pg() in the loop doesn't work. I think this :means that we've changed the page tables too early for a page elsewhere. : :Bruce Ok, lets narrow it down - if we can panic the kernel with a dup2() then the problem should reside in the fdalloc() chain somewhere. fdalloc() uses MALLOC(), bcopy, and bzero to reallocate the chain. Due to the way fdalloc() works, we are multiplying nfiles by 2 and reallocating the array in a loop until we reach the file descriptor number we want. (BTW, this will seriously fragment the MALLOC pool!). We also are MALLOC()ing space that is oddly sized, due to OFILESDIZE being (sizeof(struct file *) + sizeof(char)). Well, this tells me there is a fairly good chance that we are hitting a bug in the kernel MALLOC somewhere related to the kernel pmap, or a bug in fdalloc(). I'll take a close look at both. That is where I recommend we start. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 13:14:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 1FA5F37B9C0 for ; Thu, 24 Feb 2000 13:14:46 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id KAA01431 for ; Fri, 25 Feb 2000 10:14:34 +1300 (NZDT) Message-Id: <200002242114.KAA01431@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: freebsd-current@freebsd.org Date: Fri, 25 Feb 2000 10:14:32 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: yes, current is broke... Reply-To: dan@freebsddiary.org X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm guessing this is related to jkh's mention of OpenSSH coming into the tree, but I'm posting it anyway. Just in case it helps. my cvsup is less then 4 hours old. ===> libssl rm -f .depend mkdep -f .depend -a -DTERMIOS -DANSI_SOURCE -DNO_IDEA - I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto - I/usr/obj/usr/src/secure/lib/libssl -DL_ENDIAN - DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/i386/usr/include /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/bio_ssl.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_both.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_algs.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_asn1.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_cert.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_ciph.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_err.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_err2.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_rsa.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_sess.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_stat.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_txt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_srvr.c cd /usr/src/secure/lib/libssl; make _EXTRADEPEND echo libssl.so.1: /usr/obj/usr/src/secure/lib/libssl/openssl/opensslconf.h >> .depend ===> libssh make: don't know how to make strlcat.c. Stop *** Error code 2 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 13:29:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id E300537BBFF; Thu, 24 Feb 2000 13:29:08 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id QAA06191; Thu, 24 Feb 2000 16:28:12 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38B5A26C.79DF6111@acm.org> Date: Thu, 24 Feb 2000 16:28:12 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: dan@freebsddiary.org Cc: freebsd-current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: yes, current is broke... References: <200002242114.KAA01431@ducky.nz.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes it is. strlcat and strlcpy are not needed in libssh since they are in the libc already. They existed in the port because earlier version of 3.x did not have them. Mark is in the middle of committing all of the changes. It might be a little while until everything is clean again. Jim Bloom bloom@acm.org Dan Langille wrote: > > I'm guessing this is related to jkh's mention of OpenSSH coming into > the tree, but I'm posting it anyway. Just in case it helps. my cvsup is > less then 4 hours old. > > ===> libssl > cd /usr/src/secure/lib/libssl; make _EXTRADEPEND > echo libssl.so.1: /usr/obj/usr/src/secure/lib/libssl/openssl/opensslconf.h >> .depend > ===> libssh > make: don't know how to make strlcat.c. Stop > *** Error code 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 13:30:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1A12637BD14 for ; Thu, 24 Feb 2000 13:30:36 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id NAA02952; Thu, 24 Feb 2000 13:59:45 -0800 (PST) Date: Thu, 24 Feb 2000 13:59:45 -0800 From: Alfred Perlstein To: Dan Langille Cc: freebsd-current@FreeBSD.ORG Subject: Re: yes, current is broke... Message-ID: <20000224135945.S21720@fw.wintelcom.net> References: <200002242114.KAA01431@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002242114.KAA01431@ducky.nz.freebsd.org>; from dan@freebsddiary.org on Fri, Feb 25, 2000 at 10:14:32AM +1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dan Langille [000224 13:45] wrote: > I'm guessing this is related to jkh's mention of OpenSSH coming into > the tree, but I'm posting it anyway. Just in case it helps. my cvsup is > less then 4 hours old. > > ===> libssl > rm -f .depend > mkdep -f .depend -a -DTERMIOS -DANSI_SOURCE -DNO_IDEA - > I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto - > I/usr/obj/usr/src/secure/lib/libssl -DL_ENDIAN - > DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/i386/usr/include Yes, Mark is currently ripping into libcryto and friends pretty roughly, this is sorta expected. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id EB59037B95B for ; Thu, 24 Feb 2000 14:18:46 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 7407C1F92; Thu, 24 Feb 2000 23:18:42 +0100 (CET) Date: Thu, 24 Feb 2000 23:18:42 +0100 From: Pascal Hofstee To: Garrett Wollman Cc: Chris Wasser , freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline Message-ID: <20000224231842.B74208@shadowmere.student.utwente.nl> References: <20000224120438.A24299@shadowmere.student.utwente.nl> <20000224102131.A1796@area51.v-wave.com> <200002241907.OAA27437@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002241907.OAA27437@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Feb 24, 2000 at 02:07:40PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 02:07:40PM -0500, Garrett Wollman wrote: > < said: > Assuming you mean ``100BASE-T (half duplex)'' here... This is not > quite right. In a CSMA/CD medium access protocol, like that used by > Ethernet, the actual capacity of the link is always(*) somewhat less than > 100%; the exact value depends on the precise parameters of the > transmissions at both ends.(**) Ok ... we all know what exactly should be theoretical maximum and all ... but that wasn't exactly my question ... I have having weird problems with the network performance permanently dropping to below 100 kB/s (while still in 100 Mbps/FDX). Is there anybody that could give a plausible explanation for this break-down ? -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:33: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 31E9C37BA49 for ; Thu, 24 Feb 2000 14:33:05 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA23734; Thu, 24 Feb 2000 16:33:02 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-102.max1.wa.cyberlynk.net(207.227.118.102) by peak.mountin.net via smap (V1.3) id sma023728; Thu Feb 24 16:32:53 2000 Message-Id: <3.0.3.32.20000224162916.007f1100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 24 Feb 2000 16:29:16 -0600 To: Alfred Perlstein From: "Jeffrey J. Mountin" Subject: Re: yes, current is broke... Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20000224135945.S21720@fw.wintelcom.net> References: <200002242114.KAA01431@ducky.nz.freebsd.org> <200002242114.KAA01431@ducky.nz.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 At 01:59 PM 2/24/00 -0800, Alfred Perlstein wrote: >* Dan Langille [000224 13:45] wrote: >> I'm guessing this is related to jkh's mention of OpenSSH coming into >> the tree, but I'm posting it anyway. Just in case it helps. my cvsup is >> less then 4 hours old. >> >> ===> libssl >> rm -f .depend >> mkdep -f .depend -a -DTERMIOS -DANSI_SOURCE -DNO_IDEA - >> I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto - >> I/usr/obj/usr/src/secure/lib/libssl -DL_ENDIAN - >> DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/i386/usr/include > >Yes, Mark is currently ripping into libcryto and friends pretty >roughly, this is sorta expected. :) With 48 commits (so far) to -current (only 1 to -stable) he's on a rampage! CVSup'd in the middle and of course building is broken. Check commits, check mail, check more commits, Need to wait for him to either run out of code to commit or steam or Dew or smokes or whatever's keeping him going. Then we can all resume building. Meantime I'll just sit back and cheer. ;) Go Mark, Go Mark.... Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Thu Feb 24 14:45:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 286BD37BBA0 for ; Thu, 24 Feb 2000 14:45:38 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id XAA01223; Thu, 24 Feb 2000 23:45:14 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id WAA76494; Thu, 24 Feb 2000 22:19:39 +0100 (CET) (envelope-from andreas) Date: Thu, 24 Feb 2000 22:19:38 +0100 From: Andreas Klemm To: Bruce Evans Cc: current@FreeBSD.ORG Subject: solved (was Re: disklabels partition sizes differ ...) Message-ID: <20000224221938.A71796@titan.klemm.gtn.com> References: <20000223152130.A1583@titan.klemm.gtn.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Thu, Feb 24, 2000 at 05:43:04AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bruce, it's running now. I removed every slice and started over. I randomly choosed another size for the WIn98 slice (~6GB) installed after that FreeBSD and now I don't get that messages anymore. Maybe fdisk was the culprit ... have no other explanation. Thanks for your help and patience Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:47:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id 236AD37BBA0 for ; Thu, 24 Feb 2000 14:47:18 -0800 (PST) (envelope-from ue@nathan.ruhr.de) Received: (qmail 84055 invoked by alias); 24 Feb 2000 22:47:16 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id XAA05210; Thu, 24 Feb 2000 23:50:43 +0100 (CET) (envelope-from ue) Date: Thu, 24 Feb 2000 23:50:42 +0100 From: Udo Erdelhoff To: freebsd-current@freebsd.org Cc: Mark Murray Subject: Re: cvs commit: src/crypto/libdes [...] Message-ID: <20000224235042.C4862@nathan.ruhr.de> References: <200002241934.VAA03512@internat.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="M9NhX3UHpAaciwkO" X-Mailer: Mutt 1.0.1i In-Reply-To: <200002241934.VAA03512@internat.freebsd.org>; from markm@FreeBSD.ORG on Thu, Feb 24, 2000 at 09:34:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii On Thu, Feb 24, 2000 at 09:34:36PM +0200, Mark Murray wrote: > markm 2000/02/24 21:34:35 SAST > IP libdes. All hail libcrypto! With -current (cvsuped from cvsup.freebsd.org/cvsup.internat.freebsd.org) as of right now (23:40 +0100): >>> stage 4: populating /usr/obj/usr/src/i386/usr/include [...] cd /usr/src/secure/lib/libcrypto; make beforeinstall [...] cd /usr/src/secure/lib/libdes; make beforeinstall cd: can't cd to /usr/src/secure/lib/libdes *** Error code 2 Patch for Makefile.inc1 1.138 included. /s/Udo -- Booze is the answer. I don't remember the question. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch --- Makefile.inc1.orig Thu Feb 24 23:24:49 2000 +++ Makefile.inc1 Thu Feb 24 23:36:15 2000 @@ -585,7 +585,6 @@ .if exists(${.CURDIR}/secure/lib/libcrypto) cd ${.CURDIR}/secure/lib/libcrypto; ${MAKE} beforeinstall .endif - cd ${.CURDIR}/secure/lib/libdes; ${MAKE} beforeinstall .if exists(${.CURDIR}/secure/lib/libssl) cd ${.CURDIR}/secure/lib/libssl; ${MAKE} beforeinstall .endif --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:51:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 34A9437B8A6 for ; Thu, 24 Feb 2000 14:51:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA06680; Thu, 24 Feb 2000 14:51:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA90390; Thu, 24 Feb 2000 14:51:21 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Feb 2000 14:51:21 -0800 From: "David O'Brien" To: User URANIA Cc: freebsd-current@freebsd.org Subject: Re: Problem with IBM Netfinity 5000 Server Message-ID: <20000224145121.C90075@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from urania@iss.com.tw on Wed, Feb 23, 2000 at 02:27:31PM +0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: > I also set these flags at my /etc/make.conf > CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations > COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -O6 (any -O above 3) is nonsense with the base GCC compiler. I really have to wonder what people think they are getting by using such hight -O values. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:54:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9EABB37BC05 for ; Thu, 24 Feb 2000 14:54:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA42874; Thu, 24 Feb 2000 14:54:08 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Feb 2000 14:54:08 -0800 (PST) From: Matthew Dillon Message-Id: <200002242254.OAA42874@apollo.backplane.com> To: Matthew Dillon Cc: Bruce Evans , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? References: <200002242105.NAA42378@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's something fishy going on here. I have a feeling that the issue may be related to the reallocation fragmentation -- we might be running the system out of KVM and there are *NO* NULL checks in the file descriptor allocation code. I'm trying to instrument the code and duplicate the problem now, and will go from there. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (nld-dial-196-7-200-29.mweb.co.za [196.7.200.29]) by hub.freebsd.org (Postfix) with ESMTP id C5CE937BBFA for ; Thu, 24 Feb 2000 14:56:39 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id AAA17041; Fri, 25 Feb 2000 00:58:44 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002242258.AAA17041@grimreaper.grondar.za> To: Udo Erdelhoff Cc: freebsd-current@freebsd.org Subject: Re: cvs commit: src/crypto/libdes [...] References: <20000224235042.C4862@nathan.ruhr.de> In-Reply-To: <20000224235042.C4862@nathan.ruhr.de> ; from Udo Erdelhoff "Thu, 24 Feb 2000 23:50:42 +0100." Date: Fri, 25 Feb 2000 00:58:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gimme a break, I'm getting there! :-) M > > --M9NhX3UHpAaciwkO > Content-Type: text/plain; charset=us-ascii > > On Thu, Feb 24, 2000 at 09:34:36PM +0200, Mark Murray wrote: > > markm 2000/02/24 21:34:35 SAST > > IP libdes. All hail libcrypto! > > With -current (cvsuped from cvsup.freebsd.org/cvsup.internat.freebsd.org) as > of right now (23:40 +0100): > >>> stage 4: populating /usr/obj/usr/src/i386/usr/include > [...] > cd /usr/src/secure/lib/libcrypto; make beforeinstall > [...] > cd /usr/src/secure/lib/libdes; make beforeinstall > cd: can't cd to /usr/src/secure/lib/libdes > *** Error code 2 > > Patch for Makefile.inc1 1.138 included. > > /s/Udo > -- > Booze is the answer. I don't remember the question. > > --M9NhX3UHpAaciwkO > Content-Type: text/plain; charset=us-ascii > Content-Disposition: attachment; filename=patch > > --- Makefile.inc1.orig Thu Feb 24 23:24:49 2000 > +++ Makefile.inc1 Thu Feb 24 23:36:15 2000 > @@ -585,7 +585,6 @@ > .if exists(${.CURDIR}/secure/lib/libcrypto) > cd ${.CURDIR}/secure/lib/libcrypto; ${MAKE} beforeinstall > .endif > - cd ${.CURDIR}/secure/lib/libdes; ${MAKE} beforeinstall > .if exists(${.CURDIR}/secure/lib/libssl) > cd ${.CURDIR}/secure/lib/libssl; ${MAKE} beforeinstall > .endif > > --M9NhX3UHpAaciwkO-- > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 14:57:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from hiro.netizen.com.au (hiro.netizen.com.au [203.30.75.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D62E37BBA0; Thu, 24 Feb 2000 14:57:46 -0800 (PST) (envelope-from benno@hiro.netizen.com.au) Received: (from benno@localhost) by hiro.netizen.com.au (8.9.3/8.9.3/Debian/GNU) id JAA10703; Fri, 25 Feb 2000 09:56:35 +1100 Date: Fri, 25 Feb 2000 09:56:35 +1100 From: Benno Rice To: Doug Rabson Cc: Soren Schmidt , Mike Smith , Yarema , FreeBSD Current , sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. Message-ID: <20000225095635.B10185@netizen.com.au> References: <200002240845.JAA86244@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Doug Rabson on Thu, Feb 24, 2000 at 09:03:55AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 09:03:55AM +0000, Doug Rabson wrote: [snip] > Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. > Nick spent a couple of hours looking at it without much success. I'll try > some things today to see if the probe is being called with interrupts > disabled. I'm getting this as well on my Twinhead Slimnote VX laptop. I'm loading vesa, linux, if_tun, usb and ums as modules. I can provide a successful boot dmesg and suchlike if you're interested. It's a PIIX4 controller and a mobile Pentium II 333. -- Benno Rice "No, no. We're *sweet* and XNFP Aries Dark Subculture- *innocent* evil bastards." friendly Internet Geek benno@netizen.com.au "Defend your joy" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 15: 1:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E877C37BBA0; Thu, 24 Feb 2000 15:01:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA00848; Thu, 24 Feb 2000 15:00:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002242300.PAA00848@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: msmith@FreeBSD.ORG (Mike Smith), yds@dppl.com (Yarema), FreeBSD-Current@FreeBSD.ORG (FreeBSD Current), sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Thu, 24 Feb 2000 20:19:55 +0100." <200002241919.UAA24133@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 24 Feb 2000 15:00:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Mike Smith wrote: > > That's possible; it may be that the kernel linker is calling somethin= g = > > before you expect it to be called. > = > Well, its rather that the delayed probe rutine I register with = > config_intrhook_establish() is called before interrupts are actually > working, that would explain why it times out on the probe... > This didn't happen before, so thats probably why it breaks... > It should break SCSI systems too, ass they do the same... Hmm. You're assuming that interrupts are working when the hooks are run,= = rather than assuming that it's safe to do things which will subsequently = cause interrupts which ought to be correctly handled. I'd hazard a guess that the presence of modules is causing the kernel = linker to run and pull all the sysctl hooks for modules it's finding. = I'm probably wrong, just a guess. > > Also, I note that you've only partially newbussed the code; I don't s= ee = > > any busspace/busdma stuff in there. Is there another megapatch comin= g? > = > Busspace is a joke, I'm perfectly fine with calling those macros > in[bwl]/out[bwl] like they should be :) > > Busdma, hmm, well I dont see that helping here either.... That's such a hopelessly naive attitude that I really hope it's a joke. = Both are necessary items. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 15:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7475E37BC9B; Thu, 24 Feb 2000 15:22:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01090; Thu, 24 Feb 2000 15:22:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002242322.PAA01090@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) In-reply-to: Your message of "Thu, 24 Feb 2000 10:03:38 EST." <3.0.5.32.20000224100338.028e5590@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 15:22:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > megaraid: v107 (December 22, 1999) > megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 > scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 > megaraid: [GH6D:1.43] detected 1 logical drives > scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 > > scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns > SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] [3.0 GB] > > Then tried > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > > Its slow, but the server does not crash..... However, if Queing enabled, it > does crash. ie. the card is still unstable. That more or less confirms what I thought. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 15:29:44 2000 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 8D08C37BCAC for ; Thu, 24 Feb 2000 15:29:38 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 33498 invoked by uid 1001); 24 Feb 2000 23:29:35 +0000 (GMT) To: daeron@shadowmere.student.utwente.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 24 Feb 2000 23:18:42 +0100" References: <20000224231842.B74208@shadowmere.student.utwente.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 25 Feb 2000 00:29:35 +0100 Message-ID: <33496.951434975@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok ... we all know what exactly should be theoretical maximum and all ... > but that wasn't exactly my question ... I have having weird problems with > the network performance permanently dropping to below 100 kB/s (while still > in 100 Mbps/FDX). Is there anybody that could give a plausible explanation > for this break-down ? Most likely you have a duplex mismatch, ie. one end full duplex, the other half duplex. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 15:31:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 53FE237BC82; Thu, 24 Feb 2000 15:31:13 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA24140; Thu, 24 Feb 2000 17:31:12 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma024136; Thu Feb 24 17:31:04 2000 Message-Id: <3.0.3.32.20000224173000.00868970@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 24 Feb 2000 17:30:00 -0600 To: obrien@FreeBSD.ORG, User URANIA From: "Jeffrey J. Mountin" Subject: Re: Problem with IBM Netfinity 5000 Server Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20000224145121.C90075@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:51 PM 2/24/00 -0800, David O'Brien wrote: >On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: >> I also set these flags at my /etc/make.conf >> CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations >> COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops > >-O6 (any -O above 3) is nonsense with the base GCC compiler. >I really have to wonder what people think they are getting by using such >hight -O values. Maybe due to things like the Apache ports' Makefile: # # Set APACHE_PERF_TUNING env. variable to YES to get maximum performance # .if defined(APACHE_PERF_TUNING) && ${APACHE_PERF_TUNING} == YES OPTIM+= -DBUFFERED_LOGS CFLAGS+= -O6 -fomit-frame-pointer .endif ... and not reading the man page or looking at the source. Hey does this, looks good, and so.... Also, the various optimization levels (et all) choice keeps coming up, but -O6 is not mentioned in the man pages. Must be magic then. ;) Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Thu Feb 24 15:32:48 2000 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 9348837BCA9 for ; Thu, 24 Feb 2000 15:32:37 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 33610 invoked by uid 1001); 24 Feb 2000 23:32:35 +0000 (GMT) To: didi@Xterminator.STUDFB.UniBw-Muenchen.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 24 Feb 2000 19:48:35 +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: Fri, 25 Feb 2000 00:32:35 +0100 Message-ID: <33608.951435155@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get > 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX > cables are used simultaneous. Due to the small ethernet frame size, it is > next to impossible to get the full speed for data transmission. FreeBSD has been able to do that (full speed) for several years now. I measured this myself way back in June 1997, between a P-133 and a PPro-200. You can do much better with current hardware. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 15:39:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C397737BCE9 for ; Thu, 24 Feb 2000 15:39:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA43271; Thu, 24 Feb 2000 15:39:07 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Feb 2000 15:39:07 -0800 (PST) From: Matthew Dillon Message-Id: <200002242339.PAA43271@apollo.backplane.com> To: Bruce Evans , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? References: <200002242105.NAA42378@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've reproduced the crash. It isn't running out of KVM. I suspect there is a bug in kmem_malloc() or kmem_free(), or possibly kmem_malloc() of a previously freed space. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 16: 3:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.kscable.com (fe2.rdc-kc.rr.com [24.94.163.49]) by hub.freebsd.org (Postfix) with ESMTP id 0CF6237BCCB for ; Thu, 24 Feb 2000 16:03:24 -0800 (PST) (envelope-from bvance@kscable.com) Received: from scott.kscable.com ([24.92.128.198]) by mail2.kscable.com with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 24 Feb 2000 18:03:18 -0600 Message-ID: <002201bf7f24$3d150080$c6805c18@kscable.com> From: "Brian Vance" To: Subject: Problem with a Compaq Prosigna 300m P75 Date: Thu, 24 Feb 2000 18:07:00 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01BF7EF1.F226A420" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001F_01BF7EF1.F226A420 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Does anyone know how to allow 3.4 or 4.0 to read the memory on the riser = board. The Compaq smart start reads it and it shows up when the system = boots. It knows the riser board is there, because the CPU is on it Scott ------=_NextPart_000_001F_01BF7EF1.F226A420 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Does anyone know how to allow 3.4 or = 4.0 to read=20 the memory on the riser board.  The Compaq smart start reads it and = it=20 shows up when the system boots.  It knows the riser board is there, = because=20 the CPU is on it
 
Scott
------=_NextPart_000_001F_01BF7EF1.F226A420-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 16:25: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 38F4D37BCF3 for ; Thu, 24 Feb 2000 16:24:57 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA24531; Thu, 24 Feb 2000 18:24:49 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-98.max1.wa.cyberlynk.net(207.227.118.98) by peak.mountin.net via smap (V1.3) id sma024527; Thu Feb 24 18:24:38 2000 Message-Id: <3.0.3.32.20000224182319.007ece90@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 24 Feb 2000 18:23:19 -0600 To: Mark Murray From: "Jeffrey J. Mountin" Subject: Marathon Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200002242258.AAA17041@grimreaper.grondar.za> References: <20000224235042.C4862@nathan.ruhr.de> <20000224235042.C4862@nathan.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:58 AM 2/25/00 +0200, Mark Murray wrote: >Gimme a break, I'm getting there! :-) So when is this event scheduled to end, so we can go for a test drive? 57^H^H61 commits to -current and counting... Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Thu Feb 24 16:33:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EBB5C37BD44; Thu, 24 Feb 2000 16:33:27 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA21691; Thu, 24 Feb 2000 16:33:27 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 24 Feb 2000 16:33:26 -0800 (PST) From: Kris Kennaway To: "Jeffrey J. Mountin" Cc: Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: Marathon In-Reply-To: <3.0.3.32.20000224182319.007ece90@207.227.119.2> Message-ID: 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, 24 Feb 2000, Jeffrey J. Mountin wrote: > So when is this event scheduled to end, so we can go for a test drive? > > 57^H^H61 commits to -current and counting... The last message to show up in the series said Mark was finished and about to collapse unconscious, so I guess that means "let the bug reports begin"! Please check that your bug hasn't already been reported before mailing, though, eh? Making Mark pass out again in fright due to 3000 new messages in -current when he wakes up won't help anyone, least of all him :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 16:33:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B2D1C37BCF4 for ; Thu, 24 Feb 2000 16:33:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA43662; Thu, 24 Feb 2000 16:33:44 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Feb 2000 16:33:44 -0800 (PST) From: Matthew Dillon Message-Id: <200002250033.QAA43662@apollo.backplane.com> To: Bruce Evans , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Patch to try (was Re: Wierd AMD panics caused by VMWare?) References: <200002242105.NAA42378@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please try the following patch and tell me if the crashes still occur. If this fixes the problem then I'm homing in on the bug. I am beginning to suspect that there is a case where a pmap can get cleared without the tlb being flushed, causing origpte to be 0 when the new pte is later created again at the same spot. When the new page is allocated and added to the pmap later on, it fails to flush the tlb entry in pmap_enter() because it believes it does not have to. This would explain why messing with the pmap_remove_all() case does not do what we expect -- I suspect that routine is not being called at all in certain cases. I have not found the case where the pmap gets cleared without being flushed yet but when I force the flush in pmap_enter(), it seems to stop the crashes (but I can't be 100% sure because I had to mess around with that file descriptor program to get it to crash the first time). (This patch is relative to 3.x) -Matt Matthew Dillon Index: pmap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v retrieving revision 1.219.2.6 diff -u -r1.219.2.6 pmap.c --- pmap.c 1999/09/02 23:56:47 1.219.2.6 +++ pmap.c 2000/02/25 00:06:50 @@ -2204,7 +2204,7 @@ */ if ((origpte & ~(PG_M|PG_A)) != newpte) { *pte = newpte | PG_A; - if (origpte) + /*if (origpte)*/ invltlb_1pg(va); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 16:51:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BFD637BE4F for ; Thu, 24 Feb 2000 16:51:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA43750; Thu, 24 Feb 2000 16:51:25 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Feb 2000 16:51:25 -0800 (PST) From: Matthew Dillon Message-Id: <200002250051.QAA43750@apollo.backplane.com> To: Bruce Evans , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Patch to try (was Re: Wierd AMD panics caused by VMWare?) References: <200002242105.NAA42378@apollo.backplane.com> <200002250033.QAA43662@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : This would explain why messing with the pmap_remove_all() case does : not do what we expect -- I suspect that routine is not being called : at all in certain cases. : : I have not found the case where the pmap gets cleared without being : flushed yet but when I force the flush in pmap_enter(), it seems to : stop the crashes (but I can't be 100% sure because I had to mess : around with that file descriptor program to get it to crash the first : time). Is it possible that a speculative read by the cpu is causing the TLB to load the invalid pte entry after we have cleared it but before we have created a new entry? This would not cause a fault, but it would load the TLB and cause a problem when we later initialize the pte but fail to invalpg1 the VA. A sequence like this: pmap_remove_all() called on pa tlb at VA flushed (something happens to cause the cpu to load the tlb at VA without faulting). pmap_enter() called with new pte (kernel memory is freed and then later allocated again). Old contents was 0 so pmap_enter() does not flush the tlb at VA. TLB still contains the invalid pte. System resumes operation, but invalid tlb entry for VA is still in the tlb. Bewm. Personally speaking I think we should simply invalidate the tlb at VA whenever we modify a pte, no matter what the original contents of that pte was. For both 3.x and 4.x. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 17:17:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id A612C37BC74; Thu, 24 Feb 2000 17:17:36 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA55749; Thu, 24 Feb 2000 17:17:32 -0800 (PST) (envelope-from Doug@gorean.org) Date: Thu, 24 Feb 2000 17:17:31 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Soren Schmidt Cc: Mike Smith , FreeBSD Current , sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002241919.UAA24133@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can reliably reproduce this problem with the following lines in /boot/loader.conf.local splash_bmp_load="YES" bitmap_name="/boot/earth.bmp" bitmap_load="YES" I have the same VESA and splash screen options in my kernel now (sources cvsup'ed yesterday) that I did on the system previously (sources from 9/22/99). Those are the only lines in the file. If I comment them out, it boots normally. dmesg, etc. available on request. I'm also willing to try patches, etc. This is an all-IDE system. I can try enabling a splash screen on my SCSI + IDE CD system at home if you want and see if that breaks too... Let me know, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 17:23:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 1502F37BD2F; Thu, 24 Feb 2000 17:23:51 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id UAA94593; Thu, 24 Feb 2000 20:23:49 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id UAA02277; Thu, 24 Feb 2000 20:23:48 -0500 (EST) Message-Id: <4.2.2.20000224201748.03ca6988@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 24 Feb 2000 20:21:46 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002242322.PAA01090@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:22 PM 2/24/2000 -0800, Mike Smith wrote: > > megaraid: v107 (December 22, 1999) > > megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 > > scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 > > megaraid: [GH6D:1.43] detected 1 logical drives > > scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 > > > > scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns > > SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] > [3.0 GB] > > > > Then tried > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > /usr/local/bin/bonnie -s 100 -d /mnt & > > > > Its slow, but the server does not crash..... However, if Queing enabled, it > > does crash. > >ie. the card is still unstable. That more or less confirms what I >thought. It would seem that way. Although I would have thought it would have crashed a little more consistently on LINUX. I suppose it is possible its an issue of drive compatibility and turning off the tagging avoided the issue. In that mode, the card was quite stable and performed as expected, but not quite as fast as on FreeBSD. I think I will stick to the Mylex cards for now. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 17:39:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 3395737BAA3 for ; Thu, 24 Feb 2000 17:39:37 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 86164137FC5; Thu, 24 Feb 2000 20:39:26 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id UAA35457; Thu, 24 Feb 2000 20:39:47 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14517.56675.102218.408699@trooper.velocet.net> Date: Thu, 24 Feb 2000 20:39:47 -0500 (EST) To: Matthew Dillon Cc: Bruce Evans , David Gilbert , freebsd-current@FreeBSD.ORG Subject: Patch to try (was Re: Wierd AMD panics caused by VMWare?) In-Reply-To: <200002250033.QAA43662@apollo.backplane.com> References: <200002242105.NAA42378@apollo.backplane.com> <200002250033.QAA43662@apollo.backplane.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Matthew" == Matthew Dillon writes: Matthew> Please try the following patch and tell me if the crashes Matthew> still occur. If this fixes the problem then I'm homing in on Matthew> the bug. Matthew> I am beginning to suspect that there is a case where a Matthew> pmap can get cleared without the tlb being flushed, causing Matthew> origpte to be 0 when the new pte is later created again at Matthew> the same spot. When the new page is allocated and added to Matthew> the pmap later on, it fails to flush the tlb entry in Matthew> pmap_enter() because it believes it does not have to. Matthew> This would explain why messing with the pmap_remove_all() Matthew> case does not do what we expect -- I suspect that routine is Matthew> not being called at all in certain cases. Matthew> I have not found the case where the pmap gets cleared Matthew> without being flushed yet but when I force the flush in Matthew> pmap_enter(), it seems to stop the crashes (but I can't be Matthew> 100% sure because I had to mess around with that file Matthew> descriptor program to get it to crash the first time). So... to get this straight, you'd like us to back out that other patch and apply this one? I have to be honest that the machine that we have is only doing this once a month because we kept adding RAM to it until it stopped exhibiting the symptoms often. If it helps, it appears to us that 3.0 didn't have the problem and 3.2 did. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 17:59:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 8953137BD4E for ; Thu, 24 Feb 2000 17:59:19 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id UAA98429 for ; Thu, 24 Feb 2000 20:59:13 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id UAA11068 for ; Thu, 24 Feb 2000 20:59:13 -0500 (EST) Message-Id: <4.2.2.20000224205401.03c6c600@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 24 Feb 2000 20:57:11 -0500 To: current@freebsd.org From: Mike Tancsa Subject: anon FTP setup on Feb 23 SNAP Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The first time I thought I made a typo, but the second time through it happened again. It seems that even if you choose NO to setup anon FTP, it still gets setup. Anyone else notice this ? This was through the standard installation. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 18:28:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id B6DBF37BD23; Thu, 24 Feb 2000 18:28:26 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from 2Cust106.tnt3.waldorf.md.da.uu.net (localhost [127.0.0.1]) by builder.freebsd.org (Postfix) with ESMTP id CDF2C132DD; Thu, 24 Feb 2000 18:26:31 -0800 (PST) Date: Thu, 24 Feb 2000 21:28:18 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mike Smith Cc: Soren Schmidt , Yarema , FreeBSD Current , sos@FreeBSD.ORG Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002242300.PAA00848@mass.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 Thu, 24 Feb 2000, Mike Smith wrote: > > It seems Mike Smith wrote: > > > That's possible; it may be that the kernel linker is calling something > > > before you expect it to be called. > > > > Well, its rather that the delayed probe rutine I register with > > config_intrhook_establish() is called before interrupts are actually > > working, that would explain why it times out on the probe... > > This didn't happen before, so thats probably why it breaks... > > It should break SCSI systems too, ass they do the same... > > Hmm. You're assuming that interrupts are working when the hooks are run, > rather than assuming that it's safe to do things which will subsequently > cause interrupts which ought to be correctly handled. > > I'd hazard a guess that the presence of modules is causing the kernel > linker to run and pull all the sysctl hooks for modules it's finding. > I'm probably wrong, just a guess. It certainly seems like the intrhooks are called really early. I did a little bit of experimenting with this problem last night, and that's the most I found: intrhooks really seem to be called to early. I guess I'll go look up cold usage, and see if it necessarily has to be done that early. I'll also investigate that sysctl possibility. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Feb 24 18:30:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id C715137BD87 for ; Thu, 24 Feb 2000 18:30:35 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20993 invoked from network); 25 Feb 2000 02:30:31 -0000 Received: from lcm208.cvzoom.net (208.230.69.208) by ns.cvzoom.net with SMTP; 25 Feb 2000 02:30:31 -0000 Date: Thu, 24 Feb 2000 21:30:05 -0500 (EST) From: Donn Miller To: David O'Brien Cc: User URANIA , freebsd-current@freebsd.org Subject: Re: Problem with IBM Netfinity 5000 Server In-Reply-To: <20000224145121.C90075@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Feb 2000, David O'Brien wrote: > On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: > > I also set these flags at my /etc/make.conf > > CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations > > COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops > > -O6 (any -O above 3) is nonsense with the base GCC compiler. > I really have to wonder what people think they are getting by using such > hight -O values. I looked at the code for gcc a while back, and it looks like optimization levels of 3 and above are considered 3. So, -O6 is the same as -O3. I think gcc a long time ago had flags that went this high. I think pgcc uses -O6, though. Sometimes when using flags -mpentium -O3 -pipe, I'll get an "internal compiler error" unless I bump down the opt to -O2 or lower. This is good -- you want to have a compiler error saying the compiler can't do it, rather than having it creating the code anyway with bugs. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 18:42:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 011A637BE00; Thu, 24 Feb 2000 18:42:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA00981; Thu, 24 Feb 2000 18:42:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002250242.SAA00981@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Fundakowski Feldman Cc: Soren Schmidt , Yarema , FreeBSD Current Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-reply-to: Your message of "Thu, 24 Feb 2000 21:28:18 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 18:42:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'd hazard a guess that the presence of modules is causing the kernel > > linker to run and pull all the sysctl hooks for modules it's finding. > > I'm probably wrong, just a guess. ... > I'll go look up cold usage, and see if it necessarily has to be done that > early. I'll also investigate that sysctl possibility. Oops. I meant sysinit, not sysctl. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 18:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 64FBA37BC1A; Thu, 24 Feb 2000 18:57:21 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from 1Cust232.tnt4.waldorf.md.da.uu.net (localhost [127.0.0.1]) by builder.freebsd.org (Postfix) with ESMTP id 9EAD2132DD; Thu, 24 Feb 2000 18:55:28 -0800 (PST) Date: Thu, 24 Feb 2000 21:57:16 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mike Smith Cc: Soren Schmidt , Yarema , FreeBSD Current Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. In-Reply-To: <200002250242.SAA00981@mass.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 Thu, 24 Feb 2000, Mike Smith wrote: > > > I'd hazard a guess that the presence of modules is causing the kernel > > > linker to run and pull all the sysctl hooks for modules it's finding. > > > I'm probably wrong, just a guess. > ... > > I'll go look up cold usage, and see if it necessarily has to be done that > > early. I'll also investigate that sysctl possibility. > > Oops. I meant sysinit, not sysctl. Well, I don't think that's it. I've tried moving it around a bit. None of the code is called until the intrhook handler is called back, so I don't see how it can be the sysinit itself causing the failure. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Feb 24 19: 1:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from stargate.iss.com.tw (stargate.iss.com.tw [210.68.99.1]) by hub.freebsd.org (Postfix) with ESMTP id AD4FD37BCFE for ; Thu, 24 Feb 2000 19:01:16 -0800 (PST) (envelope-from urania@iss.com.tw) Received: from stargate.iss.com.tw (root@localhost) by stargate.iss.com.tw with ESMTP id LAA11076 for ; Fri, 25 Feb 2000 11:07:36 +0800 (CST) Received: from iss.com.tw (mail.iss.com.tw [172.16.6.97]) by stargate.iss.com.tw with SMTP id LAA11072 for ; Fri, 25 Feb 2000 11:07:36 +0800 (CST) Received: (qmail 51285 invoked from network); 25 Feb 2000 02:54:29 -0000 Received: from unknown (HELO iss.com.tw) (172.16.6.98) by 172.16.6.97 with SMTP; 25 Feb 2000 02:54:29 -0000 Message-ID: <38B5F15E.82197160@iss.com.tw> Date: Fri, 25 Feb 2000 11:05:02 +0800 From: urania X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, laa@zgia.zp.ua Subject: Re: Problem with IBM Netfinity 5000 Server References: Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Donn Miller wrote: > I looked at the code for gcc a while back, and it looks like optimization > levels of 3 and above are considered 3. So, -O6 is the same as -O3. I > think gcc a long time ago had flags that went this high. I think pgcc > uses -O6, though. > > Sometimes when using flags -mpentium -O3 -pipe, I'll get an "internal > compiler error" unless I bump down the opt to -O2 or lower. This is good > -- you want to have a compiler error saying the compiler can't do it, > rather than having it creating the code anyway with bugs. > > - Donn Thanks you all, I do know gcc do nothing more as optimization levels large than 3. 3 Month ago I try install RedHat 6.1 to this IBM 5000 server, eepro100 module could only found by install and never success load this module. This Month I try install RedHat 6.2, it can found eepro100, and most important is everythings work fine !! So I think maybe FreeBSD problem only ? 3 Month ago 4.0-Current cannot see anything as I plug any PCI interface at 1th-4th slot, only can found device at 5th PCI slot. This Month 4.0-Current RC is out, I'm happy to re-build all things from cvsup source, update everything as /usr/src/UPDATE says, after reboot, I see the missing device I plug at 4th PCI slot, but after few seconds I login at console, this IBM Server direct reboot. Nothing Panic, just like M$ Windows crash => Server Reset ? After a longtime disk check, I login again, Server Reset again .... Don't things realy strage ? Everything wroks fine if 1th-4th PCI slot is empty, no device attached. Same kernel, Same Applications its running .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 19:24:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from netfinity.nxos.com (firewall.nxos.com [209.166.45.226]) by hub.freebsd.org (Postfix) with ESMTP id 080F637BD7E for ; Thu, 24 Feb 2000 19:24:27 -0800 (PST) (envelope-from jja@nxos.com) Received: from 0001 ([209.166.45.232]) by netfinity.nxos.com (8.9.3+Sun/8.9.1) with SMTP id DAA19102; Fri, 25 Feb 2000 03:23:50 GMT Message-ID: <00a201bf7f40$505bef20$e82da6d1@nxos.com> From: "Jason Allum" To: "urania" , References: <38B5F15E.82197160@iss.com.tw> Subject: Re: Problem with IBM Netfinity 5000 Server Date: Thu, 24 Feb 2000 22:27:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "urania" To: ; Sent: Thursday, February 24, 2000 10:05 PM Subject: Re: Problem with IBM Netfinity 5000 Server > Thanks you all, > I do know gcc do nothing more as optimization levels large than 3. > 3 Month ago I try install RedHat 6.1 to this IBM 5000 server, > eepro100 module could only found by install and never success load this > module. > This Month I try install RedHat 6.2, it can found eepro100, and most > important is everythings work fine !! > So I think maybe FreeBSD problem only ? > > 3 Month ago 4.0-Current cannot see anything as I plug any PCI > interface at 1th-4th slot, only can found device at 5th PCI slot. > This Month 4.0-Current RC is out, I'm happy to re-build all things > from cvsup > source, update everything as /usr/src/UPDATE says, after reboot, I see > the missing > device I plug at 4th PCI slot, but after few seconds I login at console, > this IBM > Server direct reboot. > Nothing Panic, just like M$ Windows crash => Server Reset ? > > After a longtime disk check, I login again, Server Reset again .... > > Don't things realy strage ? > Everything wroks fine if 1th-4th PCI slot is empty, no device > attached. > Same kernel, Same Applications its running .... aren't pci slots 1 through 4 "hot-pluggable" on the '5000? - jason allum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 19:51:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 2783037BDA2 for ; Thu, 24 Feb 2000 19:51:05 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 33604 invoked by uid 1001); 25 Feb 2000 03:51:03 -0000 Date: 24 Feb 2000 19:51:03 -0800 Date: Thu, 24 Feb 2000 19:51:03 -0800 From: Bill Swingle To: Mike Tancsa Cc: current@freebsd.org, Jordan Hubbard Subject: Re: anon FTP setup on Feb 23 SNAP Message-ID: <20000224195103.A31954@dub.net> References: <4.2.2.20000224205401.03c6c600@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.2.2.20000224205401.03c6c600@mail.sentex.net>; from mike@sentex.net on Thu, Feb 24, 2000 at 08:57:11PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did an install of the Feb 22 snap. The new wording for the anon ftp section is really screwy. It's been turned around. The old straight forward "Do you want to enable anon ftp?" was fine. Hrmm. -Bill On Thu, Feb 24, 2000 at 08:57:11PM -0500, Mike Tancsa wrote: > > The first time I thought I made a typo, but the second time through it > happened again. It seems that even if you choose NO to setup anon FTP, it > still gets setup. Anyone else notice this ? This was through the standard > installation. > > ---Mike > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 20:29:14 2000 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 A319837BD27; Thu, 24 Feb 2000 20:29:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA23042; Thu, 24 Feb 2000 20:29:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Swingle Cc: Mike Tancsa , current@freebsd.org, Jordan Hubbard Subject: Re: anon FTP setup on Feb 23 SNAP In-reply-to: Your message of "Thu, 24 Feb 2000 19:51:03 PST." <20000224195103.A31954@dub.net> Date: Thu, 24 Feb 2000 20:29:01 -0800 Message-ID: <23039.951452941@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just did an install of the Feb 22 snap. The new wording for the anon > ftp section is really screwy. It's been turned around. The old straight > forward "Do you want to enable anon ftp?" was fine. It's been turned around because people usually just hit return without reading the dialogs and I didn't think defaulting to anonymous ftp access was an especially good idea. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 20:31:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id C4F8D37BDFF for ; Thu, 24 Feb 2000 20:31:34 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id UAA37145 for current@FreeBSD.org; Thu, 24 Feb 2000 20:31:31 -0800 (PST) (envelope-from ulf) Date: Thu, 24 Feb 2000 20:31:30 -0800 From: Ulf Zimmermann To: current@FreeBSD.org Subject: Problems with -current snapshot of 02242000 Message-ID: <20000224203130.B467@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tried to install the snapshot, but it hangs at Probing devices. ALT-F2 shows as last entry: DEBUG: Found a disk device named mlxd0 Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL will ask if you really want to stop the install. System is an AMD K7-750, 256MB memory, some Matrox Millinium PCI card, Intel fxp, Mylex AcceleRaid 250 controller. Any ideas ? Mike ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 20:44:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 22C3937BDE9 for ; Thu, 24 Feb 2000 20:44:37 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id XAA16543; Thu, 24 Feb 2000 23:44:36 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id XAA18235; Thu, 24 Feb 2000 23:44:35 -0500 (EST) Message-Id: <4.2.2.20000224233028.03c603d8@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 24 Feb 2000 23:42:34 -0500 To: Bill Swingle From: Mike Tancsa Subject: Re: anon FTP setup on Feb 23 SNAP Cc: current@freebsd.org In-Reply-To: <20000224195103.A31954@dub.net> References: <4.2.2.20000224205401.03c6c600@mail.sentex.net> <4.2.2.20000224205401.03c6c600@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:51 PM 2/24/2000 -0800, Bill Swingle wrote: >I just did an install of the Feb 22 snap. The new wording for the anon >ftp section is really screwy. It's been turned around. The old straight >forward "Do you want to enable anon ftp?" was fine. > >Hrmm. OK, I am embarrassed now :-) I cant believe I didnt read the damn prompt. Its a good thing I didnt have a dialog box ask me today, "Destory the Hard drive ? Yes/No" ;-) One of those days... ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 20:55: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 06E0C37BD79 for ; Thu, 24 Feb 2000 20:54:51 -0800 (PST) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id NAA24234; Fri, 25 Feb 2000 13:54:44 +0900 (JST) Received: from unknown(133.253.31.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma023934; Fri, 25 Feb 00 13:54:04 +0900 Received: (from uucp@localhost) by lemond.gkn.kubota.co.jp (8.9.3+3.2W/3.7W00013112) with UUCP id NAA08403 for freebsd-current@freebsd.org; Fri, 25 Feb 2000 13:54:02 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.ttr.kubota.co.jp (8.9.3/3.7W-uucp) with ESMTP id NAA02132 for ; Fri, 25 Feb 2000 13:52:18 +0900 (JST) To: freebsd-current@freebsd.org Subject: mergemaster fail with crypto changes X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000225135218A.haro@tk.kubota.co.jp> Date: Fri, 25 Feb 2000 13:52:18 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 40 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I don't have crypto in my source tree, because I'm in Japan, I get following error using mergemaster. ----------8<---------8<---------Cut here---------8<---------8<--------- # mergemaster .... .... install: /usr/src/etc/../crypto/openssh/ssh_config: No such file or directory *** Error code 71 Stop in /usr/src/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment ----------8<---------8<---------Cut here---------8<---------8<--------- In /usr/src/etc/Makefile (rev 1.214), it should check for existance of crypto directory. --- Makefile.ctm Fri Feb 25 11:53:34 2000 +++ Makefile Fri Feb 25 13:47:10 2000 @@ -20,7 +20,7 @@ ${.CURDIR}/../usr.bin/mail/misc/mail.rc \ ${.CURDIR}/../usr.bin/locate/locate/locate.rc -.if !defined(NO_OPENSSH) +.if exists(${.CURDIR}../crypto) && !defined(NO_OPENSSH) BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \ ${.CURDIR}/../crypto/openssh/sshd_config .endif =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Development, Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 Email: haro@tk.kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 21: 1: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 3EDB137BD53 for ; Thu, 24 Feb 2000 21:00:57 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 35049 invoked by uid 1001); 25 Feb 2000 05:00:51 -0000 Date: 24 Feb 2000 21:00:51 -0800 Date: Thu, 24 Feb 2000 21:00:51 -0800 From: Bill Swingle To: "Jordan K. Hubbard" Cc: Mike Tancsa , current@freebsd.org Subject: Re: anon FTP setup on Feb 23 SNAP Message-ID: <20000224210050.C34888@dub.net> References: <20000224195103.A31954@dub.net> <23039.951452941@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <23039.951452941@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Feb 24, 2000 at 08:29:01PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 08:29:01PM -0800, Jordan K. Hubbard wrote: > > I just did an install of the Feb 22 snap. The new wording for the anon > > ftp section is really screwy. It's been turned around. The old straight > > forward "Do you want to enable anon ftp?" was fine. > > It's been turned around because people usually just hit return without > reading the dialogs and I didn't think defaulting to anonymous ftp > access was an especially good idea. :) I agree but the wording is a bit weird. Maybe it should read: "Do you want to enable anon ftp?" but if they just hit return it defaults to no. -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 21:16:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 499D537BE11 for ; Thu, 24 Feb 2000 21:15:50 -0800 (PST) (envelope-from bloom@acm.org) Received: from reyim.ne.mediaone.net ([24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id AAA23900 for ; Fri, 25 Feb 2000 00:15:47 -0500 (EST) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id XAA50502; Thu, 24 Feb 2000 23:04:03 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38B5FF33.DE8D6C6A@acm.org> Date: Thu, 24 Feb 2000 23:04:03 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Munehiro Matsuda Cc: freebsd-current@FreeBSD.ORG Subject: Re: mergemaster fail with crypto changes References: <20000225135218A.haro@tk.kubota.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While I was working on this project before I found out that Mark was 95% done already, I made those tests be: .in !defined(NO_OPENSSH) && !defined(NOCRYPT) NOCRYPT has been the standard way of indicating that the cryptograph package has not been installed. Jim Bloom bloom@acm.org Munehiro Matsuda wrote: > > Hi all, > > I don't have crypto in my source tree, because I'm in Japan, > I get following error using mergemaster. > > ----------8<---------8<---------Cut here---------8<---------8<--------- > # mergemaster > .... > .... > install: /usr/src/etc/../crypto/openssh/ssh_config: No such file or directory > *** Error code 71 > > Stop in /usr/src/etc. > > *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the > temproot environment > ----------8<---------8<---------Cut here---------8<---------8<--------- > > In /usr/src/etc/Makefile (rev 1.214), it should check for existance of > crypto directory. > > --- Makefile.ctm Fri Feb 25 11:53:34 2000 > +++ Makefile Fri Feb 25 13:47:10 2000 > @@ -20,7 +20,7 @@ > ${.CURDIR}/../usr.bin/mail/misc/mail.rc \ > ${.CURDIR}/../usr.bin/locate/locate/locate.rc > > -.if !defined(NO_OPENSSH) > +.if exists(${.CURDIR}../crypto) && !defined(NO_OPENSSH) > BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \ > ${.CURDIR}/../crypto/openssh/sshd_config > .endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 21:22: 7 2000 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 BB09A37C0D3 for ; Thu, 24 Feb 2000 21:21:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA02114; Thu, 24 Feb 2000 21:21:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Swingle Cc: Mike Tancsa , current@freebsd.org Subject: Re: anon FTP setup on Feb 23 SNAP In-reply-to: Your message of "Thu, 24 Feb 2000 21:00:51 PST." <20000224210050.C34888@dub.net> Date: Thu, 24 Feb 2000 21:21:11 -0800 Message-ID: <2111.951456071@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree but the wording is a bit weird. Maybe it should read: > "Do you want to enable anon ftp?" but if they just hit return it > defaults to no. There's no way to make a libdialog yes/no requestor "default to no" or I'd have done exactly that. C'mon, give me at least minimum credit for having thought this out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 21:25:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhop1.nyroc.rr.com (mailhop1-0.nyroc.rr.com [24.92.226.120]) by hub.freebsd.org (Postfix) with ESMTP id F1A5A37BC50 for ; Thu, 24 Feb 2000 21:25:11 -0800 (PST) (envelope-from bokonon@rochester.rr.com) Received: from mailout1.nyroc.rr.com ([24.92.226.146]) by mailhop1.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with ESMTP id com for ; Fri, 25 Feb 2000 00:22:19 -0500 Received: from helga ([24.161.80.54]) by mailout1.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com for ; Fri, 25 Feb 2000 00:22:57 -0500 From: "Caleb Land" To: Subject: Date: Fri, 25 Feb 2000 00:30:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth ceff744c subscribe freebsd-current bokonon@rochester.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 21:47:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id BD73E37BE48 for ; Thu, 24 Feb 2000 21:45:53 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id LAA32061; Fri, 25 Feb 2000 11:45:08 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 25 Feb 2000 11:45:07 +0600 (NS) From: Max Khon To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) In-Reply-To: <20000224110244.A89479@dragon.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 hi, there! On Thu, 24 Feb 2000, David O'Brien wrote: > On Wed, Feb 23, 2000 at 02:31:01PM +0100, Martin Cracauer wrote: > > Where's the bug, anyway? Do we need to fix the compiler or would it be > > better to get a newer assembler? > > A new assembler (whole binutils) is on the way, probably around the end > of March. great. will we have collect2 then? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 22:10:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id D553B37BE10 for ; Thu, 24 Feb 2000 22:10:27 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id WAA63554; Thu, 24 Feb 2000 22:10:23 -0800 (PST) (envelope-from ulf) Date: Thu, 24 Feb 2000 22:10:22 -0800 From: Ulf Zimmermann To: Ulf Zimmermann Cc: current@FreeBSD.ORG Subject: Re: Problems with -current snapshot of 02242000 Message-ID: <20000224221022.C467@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000224203130.B467@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000224203130.B467@PacHell.TelcoSucks.org>; from ulf@Alameda.net on Thu, Feb 24, 2000 at 08:31:30PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 08:31:30PM -0800, Ulf Zimmermann wrote: > Tried to install the snapshot, but it hangs at Probing devices. > ALT-F2 shows as last entry: > > DEBUG: Found a disk device named mlxd0 > > Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL > will ask if you really want to stop the install. > > System is an AMD K7-750, 256MB memory, some Matrox Millinium PCI card, > Intel fxp, Mylex AcceleRaid 250 controller. Any ideas ? Mike ? Tried the snap 02202000 and that one zipped just throw probing in less then 1 second. > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 22:38:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id D365437BE2F for ; Thu, 24 Feb 2000 22:38:17 -0800 (PST) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id PAA11436; Fri, 25 Feb 2000 15:38:11 +0900 (JST) Received: from unknown(133.253.31.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma011209; Fri, 25 Feb 00 15:37:30 +0900 Received: (from uucp@localhost) by lemond.gkn.kubota.co.jp (8.9.3+3.2W/3.7W00013112) with UUCP id PAA09799; Fri, 25 Feb 2000 15:37:30 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.ttr.kubota.co.jp (8.9.3/3.7W-uucp) with ESMTP id PAA02379; Fri, 25 Feb 2000 15:35:46 +0900 (JST) To: bloom@acm.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: mergemaster fail with crypto changes In-Reply-To: <38B5FF33.DE8D6C6A@acm.org> References: <20000225135218A.haro@tk.kubota.co.jp> <38B5FF33.DE8D6C6A@acm.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000225153546A.haro@tk.kubota.co.jp> Date: Fri, 25 Feb 2000 15:35:46 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 56 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well that does't seem to work for me. Becase mergemaster doesn't use NOCRYPT stuff and /usr/src/crypto doesn't exist by default, if you just cvsup (or use CTM for my case). I think checking for crypto is just simple. Munehiro (Haro) Matsuda From: Jim Bloom Date: Thu, 24 Feb 2000 23:04:03 -0500 ::While I was working on this project before I found out that Mark was 95% ::done already, I made those tests be: :: :: .in !defined(NO_OPENSSH) && !defined(NOCRYPT) :: ::NOCRYPT has been the standard way of indicating that the cryptograph ::package has not been installed. :: ::Jim Bloom ::bloom@acm.org :: ::Munehiro Matsuda wrote: ::> ::> Hi all, ::> ::> I don't have crypto in my source tree, because I'm in Japan, ::> I get following error using mergemaster. ::> ::> ----------8<---------8<---------Cut here---------8<---------8<--------- ::> # mergemaster ::> .... ::> .... ::> install: /usr/src/etc/../crypto/openssh/ssh_config: No such file or directory ::> *** Error code 71 ::> ::> Stop in /usr/src/etc. ::> ::> *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the ::> temproot environment ::> ----------8<---------8<---------Cut here---------8<---------8<--------- ::> ::> In /usr/src/etc/Makefile (rev 1.214), it should check for existance of ::> crypto directory. ::> ::> --- Makefile.ctm Fri Feb 25 11:53:34 2000 ::> +++ Makefile Fri Feb 25 13:47:10 2000 ::> @@ -20,7 +20,7 @@ ::> ${.CURDIR}/../usr.bin/mail/misc/mail.rc \ ::> ${.CURDIR}/../usr.bin/locate/locate/locate.rc ::> ::> -.if !defined(NO_OPENSSH) ::> +.if exists(${.CURDIR}../crypto) && !defined(NO_OPENSSH) ::> BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \ ::> ${.CURDIR}/../crypto/openssh/sshd_config ::> .endif :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 22:41:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 4627237BE10; Thu, 24 Feb 2000 22:41:27 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA26245; Fri, 25 Feb 2000 00:41:26 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-105.max1.wa.cyberlynk.net(207.227.118.105) by peak.mountin.net via smap (V1.3) id sma026241; Fri Feb 25 00:41:16 2000 Message-Id: <3.0.3.32.20000225004006.00a0a100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 25 Feb 2000 00:40:06 -0600 To: Kris Kennaway From: "Jeffrey J. Mountin" Subject: Re: Marathon Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.20000224182319.007ece90@207.227.119.2> 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:33 PM 2/24/00 -0800, Kris Kennaway wrote: >On Thu, 24 Feb 2000, Jeffrey J. Mountin wrote: > >> So when is this event scheduled to end, so we can go for a test drive? >> >> 57^H^H61 commits to -current and counting... > >The last message to show up in the series said Mark was finished and about >to collapse unconscious, so I guess that means "let the bug reports >begin"! Please check that your bug hasn't already been reported before >mailing, though, eh? Making Mark pass out again in fright due to 3000 new >messages in -current when he wakes up won't help anyone, least of all him >:-) Looks like 61 messages for 209 deltas is the final total, but may have missed a few messages, since I didn't find the "done" part. No to mention my CVSup output shows DG following right behind him. 'Cept it looks like Brian F impersonating him. No matter, build in progress. Dependant ports to follow. Hmmm... maybe should have toasted the RSAref port, then build, then install and see if the "just works" part mentioned does work.... Why not.... in progress... kudos/complaints to follow. ;) As for checking first. Usually wait a day before even building, but tend to get a bit more adventuresome around release time. Otherwise my build dies and it's usually fixed or at least spoken for. 8-/ Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Thu Feb 24 22:49:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id 62AC237BEF9 for ; Thu, 24 Feb 2000 22:49:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00448; Thu, 24 Feb 2000 22:49:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002250649.WAA00448@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: ulf@Alameda.net Cc: current@FreeBSD.org Subject: Re: Problems with -current snapshot of 02242000 In-reply-to: Your message of "Thu, 24 Feb 2000 20:31:30 PST." <20000224203130.B467@PacHell.TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 22:49:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tried to install the snapshot, but it hangs at Probing devices. > ALT-F2 shows as last entry: > > DEBUG: Found a disk device named mlxd0 > > Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL > will ask if you really want to stop the install. > > System is an AMD K7-750, 256MB memory, some Matrox Millinium PCI card, > Intel fxp, Mylex AcceleRaid 250 controller. Any ideas ? Mike ? This is a weird one; I've seen it a couple of times now. Try hitting Esc or Enter _once_ on the vty with the "probing devices" message. It almost looks like something's losing the display update... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 22:53:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 9578937BE10 for ; Thu, 24 Feb 2000 22:53:40 -0800 (PST) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.9.3/8.9.3) id BAA15415 for freebsd-current@freebsd.org; Fri, 25 Feb 2000 01:53:55 -0500 (EST) Date: Fri, 25 Feb 2000 01:53:55 -0500 (EST) From: Kent Hauser Message-Id: <200002250653.BAA15415@rtp.tfd.com> To: freebsd-current@freebsd.org Subject: IPSec/VPN Config Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Is there a howto/example guide for configuring IPSec for -current. Needless to say I've spent fruitless hours trying to convince "setkey" to sent an IPSec packet to my network's internet gateway w/o success. My setup is typical: mobile/dynamic-assigned-ip-address freebsd box trying to contact fixed address/private address network/(net 10)/ network via an Ascend router with IPSec support. But according to "tcpdump" my IPSec packets never leave. Help would be appreciated. Thanks a bunch. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 23: 0:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id E912A37BE44 for ; Thu, 24 Feb 2000 23:00:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA00544 for ; Thu, 24 Feb 2000 23:00:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002250700.XAA00544@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: cvs commit: src/sys/boot/common load_elf.c module.c (fwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 23:00:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For all of you seeing problems with eg. the if_xl module's dependancies on the miibus module, this should be the cure. ------- Forwarded Message Return-Path: msmith Delivered-To: msmith@freebsd.org Return-Path: owner-cvs-committers@FreeBSD.org Received: from hub.freebsd.org by localhost with POP3 (fetchmail-5.1.2) for msmith@localhost (single-drop); Thu, 24 Feb 2000 22:46:09 -0800 (PST) Received: by hub.freebsd.org (Postfix, from userid 538) id A3E2637BE11; Thu, 24 Feb 2000 21:10:48 -0800 (PST) Delivered-To: cvs-committers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DD14D37BE06; Thu, 24 Feb 2000 21:10:46 -0800 (PST) (envelope-from bp@FreeBSD.org) Received: (from bp@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA99104; Thu, 24 Feb 2000 21:10:46 -0800 (PST) (envelope-from bp@FreeBSD.org) Message-Id: <200002250510.VAA99104@freefall.freebsd.org> From: Boris Popov Date: Thu, 24 Feb 2000 21:10:46 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/boot/common load_elf.c module.c Sender: owner-cvs-committers@FreeBSD.org Precedence: bulk X-UIDL: 655f06170f338e0f7535db07e4c59457 bp 2000/02/24 21:10:45 PST Modified files: sys/boot/common load_elf.c module.c Log: Fix the loader to handle module dependencies properly. More fixes will be provided after modmetadata appears in the kernel. Reviewed by: msmith Approved by: jkh Revision Changes Path 1.13 +9 -40 src/sys/boot/common/load_elf.c 1.13 +75 -71 src/sys/boot/common/module.c ------- End of Forwarded Message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 24 23:25:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id C98B637BE44 for ; Thu, 24 Feb 2000 23:25:48 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id QAA07644; Fri, 25 Feb 2000 16:25:33 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id QAA06496; Fri, 25 Feb 2000 16:25:32 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id QAA28786; Fri, 25 Feb 2000 16:25:31 +0900 (JST) In-Reply-To: <200002250653.BAA15415@rtp.tfd.com> References: <200002250653.BAA15415@rtp.tfd.com> X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Subject: Re: IPSec/VPN Config To: kent@tfd.com Cc: freebsd-current@FreeBSD.ORG X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000225162622L.shin@nd.net.fujitsu.co.jp> Date: Fri, 25 Feb 2000 16:26:22 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 128 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > > Is there a howto/example guide for configuring IPSec for -current. Hi, I prepared one and sent the patches to freebsd-doc yesterday. I'll attach IPsec part from the document to end of this mail. Also, http://www.kame.net/newsletter/19991007/ might have better description about IPsec tunnel setup. Thanks, Yoshinobu Inoue > Needless to say I've spent fruitless hours trying to convince "setkey" > to sent an IPSec packet to my network's internet gateway w/o success. > My setup is typical: mobile/dynamic-assigned-ip-address freebsd box > trying to contact fixed address/private address network/(net 10)/ network > via an Ascend router with IPSec support. But according to "tcpdump" my > IPSec packets never leave. Help would be appreciated. > > Thanks a bunch. > > Kent ------------------------------------------------------------------- +<<>> + +The current KAME supports both transport mode and tunnel mode. +However, tunnel mode comes with some restrictions. + +IPsec requires fairly complex configuration, so here we show transport +mode only. http://www.kame.net/newsletter/ has more comprehensive +examples. + +Let's setup security association to deploy a secure channel between +HOST A (10.2.3.4) and HOST B (10.6.7.8). Here we show a little +complicated example. From HOST A to HOST B, only old AH is used. +From HOST B to HOST A, new AH and new ESP are combined. + +Now we should choose algorithm to be used corresponding to "AH"/"new +AH"/"ESP"/"new ESP". Please refer to the "setkey" man page to know +algorithm names. Our choice is MD5 for AH, new-HMAC-SHA1 for new AH, +and new-DES-expIV with 8 byte IV for new ESP. + +Key length highly depends on each algorithm. For example, key +length must be equal to 16 bytes for MD5, 20 for new-HMAC-SHA1, +and 8 for new-DES-expIV. Now we choose "MYSECRETMYSECRET", +"KAMEKAMEKAMEKAMEKAME", "PASSWORD", respectively. + +OK, let's assign SPI (Security Parameter Index) for each protocol. +Please note that we need 3 SPIs for this secure channel since three +security headers are produced (one for from HOST A to HOST B, two for +from HOST B to HOST A). Please also note that SPI MUST be greater +than or equal to 256. We choose, 1000, 2000, and 3000, respectively. + + + (1) + HOST A ------> HOST B + + (1)PROTO=AH + ALG=MD5(RFC1826) + KEY=MYSECRETMYSECRET + SPI=1000 + + (2.1) + HOST A <------ HOST B + <------ + (2.2) + + (2.1) + PROTO=AH + ALG=new-HMAC-SHA1(new AH) + KEY=KAMEKAMEKAMEKAMEKAME + SPI=2000 + + (2.2) + PROTO=ESP + ALG=new-DES-expIV(new ESP) + IV length = 8 + KEY=PASSWORD + SPI=3000 + +Now, let's setup security association. Execute "setkey" on both HOST +A and B: + +# setkey -c +add 10.2.3.4 10.6.7.8 ah 1000 -m transport -A keyed-md5 "MYSECRETMYSECRET" ; +add 10.6.7.8 10.2.3.4 ah 2000 -m transport -A hmac-sha1 "KAMEKAMEKAMEKAMEKAME" ; +add 10.6.7.8 10.2.3.4 esp 3000 -m transport -E des-cbc "PASSWORD" ; +^D + +Actually, IPsec communication doesn't process until security policy +entries will be defined. In this case, you must setup each host. + +At A: +# setkey -c +spdadd 10.2.3.4 10.6.7.8 any -P out ipsec + ah/transport/10.2.3.4-10.6.7.8/require ; +^D + +At B: +spdadd 10.6.7.8 10.2.3.4 any -P out ipsec + esp/transport/10.6.7.8-10.2.3.4/require ; +spdadd 10.6.7.8 10.2.3.4 any -P out ipsec + ah/transport/10.6.7.8-10.2.3.4/require ; +^D + +To utilize the security associations installed into the kernel, you +must set the socket security level by using setsockopt(). +This is per-application (or per-socket) security. For example, +the "ping" command has the -P option with parameter to enable AH and/or ESP. + +For example: +% ping -P "out ipsec \ + ah/transport/10.0.1.1-10.0.2.2/use \ + esp/tunnel/10.0.1.1-10.0.1.2/require" 10.0.2.2 + +If there are proper SAs, this policy specification causes ICMP packet +to be AH transport mode inner ESP tunnel mode like below. + + HOST C -----------> GATEWAY D ----------> HOST E + 10.0.1.1 10.0.1.2 10.0.2.1 10.0.2.2 + | | | | + | ======= ESP ======= | + ==================== AH ================== + + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 1:14: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9259537BEBF for ; Fri, 25 Feb 2000 01:14:03 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA69782; Fri, 25 Feb 2000 01:13:52 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002250913.BAA69782@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002241907.OAA27437@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 24, 2000 02:07:40 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 25 Feb 2000 01:13:51 -0800 (PST) Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > > The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s > > (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps->MB/s you divide > > by 8] I realize my punctuation may be off, but there you are. > > Assuming you mean ``100BASE-T (half duplex)'' here... This is not Just to put a final nit pick on this... 100BASE-T is not defined by the standards. 100baseTX, 100baseFX, and 100baseT4 are. > quite right. In a CSMA/CD medium access protocol, like that used by > Ethernet, the actual capacity of the link is always(*) somewhat less than > 100%; the exact value depends on the precise parameters of the > transmissions at both ends.(**) > > -GAWollman > > (*)In non-trivial conditions; i.e., when actual work is being done. > > (**)I've heard numbers between 70% and 95%. And the major set of parameters that effect the higher side of this number are MTU(Maximum Transmission Unit) and IFG (Interframe Gap) and the protocol overhead of what ever proto you are using. For those really interested in the nuts and bolts of the calculations for this I refer you to ``Switched, Fast and Gigabit Ethernet Third Edition'' Robert Bryer & Sean Riley, ISBN 1-57870-073-6 chapter 7, ''Bandwidth: How Much Is Enough?''. Also chapter 2 in the same book for some of the data used below and for a more indepth explination of what all these things are, for that matter, 802.* :-) Some interesting numbers: (In a format that might help some people understand where the magic numbers 1500, 1518 and 1538 come from in ethernet documentation (though few folks but ethernet framer geeks would ever deal with the 1538 number :-)). Layer 2 maximal data rate: (ie, raw ethenet packets, no protocol) data / ( IFG + ( Preamble + SFD ) + DA + SA + type + data + CRC ) = 1500 / ( 12 + ( 7 + 1 ) + 6 + 6 + 2 + 1500 + 4 ) = 97.53% 1500 / ( 12 + ( 8 ) + 1518 ) = 97.53% 1500 / ( 1538 ) = 97.53% So infact the Layer 2 maximal data rate of 100BaseTX is 97.5929Mb/s or 12.1912MB/s. I'll leave the Layer 3 to 7 calculation up to the reader, as I am a hardware geek and I showed you how to do the calculations at the hardwire layer, you software geeks can go figure out the overhead for the software layers :-). Please note that ``maximal'' is a key word in the above discussion, so please don't tell me that not all frames are 1500 bytes of data, because if they are not 1500 bytes of data you didn't solve the problem for the maximal. The first hardware that I know of that was ever capable of doing the 95.53% at the link layer was the i82586 by Intel on 10base, and you had to lock the sucker up in continues ring search mode with a good shared memory access mechanism to make it hit that. You needed very large chunks of shared memory (MB's) to sustain a very long burst of traffic at wire speed. You can not use ethernet in a shared mode and achive these numbers (point to point or effectivly point to point via switching only). Anyone quoteing ethernet or any other MAC layer data rates without atleast as much detail as above is practicing abuse of statistics and not presenting hard factual data which should be treated as such. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 1:26:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id ECE7137C245 for ; Fri, 25 Feb 2000 01:26:19 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA69805; Fri, 25 Feb 2000 01:25:59 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002250925.BAA69805@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <20000224231842.B74208@shadowmere.student.utwente.nl> from Pascal Hofstee at "Feb 24, 2000 11:18:42 pm" To: daeron@wit401305.student.utwente.nl (Pascal Hofstee) Date: Fri, 25 Feb 2000 01:25:59 -0800 (PST) Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Feb 24, 2000 at 02:07:40PM -0500, Garrett Wollman wrote: > > < said: > > Assuming you mean ``100BASE-T (half duplex)'' here... This is not > > quite right. In a CSMA/CD medium access protocol, like that used by > > Ethernet, the actual capacity of the link is always(*) somewhat less than > > 100%; the exact value depends on the precise parameters of the > > transmissions at both ends.(**) > > Ok ... we all know what exactly should be theoretical maximum and all ... > but that wasn't exactly my question ... I have having weird problems with > the network performance permanently dropping to below 100 kB/s (while still > in 100 Mbps/FDX). Is there anybody that could give a plausible explanation > for this break-down ? There was a patch of DC21143 chips it seems that has a very strange thermal problem. Can you tell me what your hub link lite is doing when you see this major slow down? If you abort all traffic does the link light keep blinking wildly? If you power the machine down for an hour or so and let everything cool down nice and cool does it seem to work for a longer period of time before the speed drops? If you see any of these symptoms call Kingston tech support, describe the problem to them, ask them for an RMA number :-) What is the date code on your DC21143 chip (I think I am recalling that you said you had a KNE100TX, and I am assuming you do, and that it is of new enough vintage to be the 21143 chip, and that it might be in this same range of chips we had problems with (33% of 4 lots of 20 cards would go to la la land within 1 to 2 hours of being placed into burn in). The problem seems to have started shortly after Intel took over production of the chips from DEC. I have not seen the problem in the last 6 lots of product. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 1:46:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id C041437B591 for ; Fri, 25 Feb 2000 01:46:08 -0800 (PST) (envelope-from khetan@freebsd.os.org.za) Received: by kg.ops.uunet.co.za (Postfix, from userid 1000) id 3B91B16E91; Fri, 25 Feb 2000 11:46:01 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by kg.ops.uunet.co.za (Postfix) with ESMTP id BF0C6112F0; Fri, 25 Feb 2000 11:46:01 +0200 (SAST) Date: Fri, 25 Feb 2000 11:46:01 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@kg.ops.uunet.co.za To: "Jeffrey J. Mountin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: yes, current is broke... In-Reply-To: <3.0.3.32.20000224162916.007f1100@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around Yesterday, "Jeffrey J. Mountin" wrote : >Need to wait for him to either run out of code to commit or steam or Dew or >smokes or whatever's keeping him going. Then we can all resume building. 1. There no end of code to commit 2. His car uses 97 Octane 3. He doesn't drink Mountain Dew (at least, not a significant enough amount that I'd notice) 4. He doesn't smoke I think it's driven by a desire to see ssh in the tree ;-) Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * kg+details@os.org.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 1:51:46 2000 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 99C1F37BED1 for ; Fri, 25 Feb 2000 01:51:41 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id KAA51364 for current@freebsd.org; Fri, 25 Feb 2000 10:51:39 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id KAA06033 for ; Fri, 25 Feb 2000 10:48:48 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Fri, 25 Feb 2000 10:48:47 +0100 (CET) From: Michael Reifenberger To: FreeBSD-Current Subject: "env MAKE_KERBEROS5=YES make includes" fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, the above statement leads to: ... cd /usr/src/kerberos5/lib/libkrb5; make beforeinstall install -C -o root -g wheel -m 444 krb5.h /usr/include/krb5.h install: krb5.h: No such file or directory *** Error code 71 ... Something missing? 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 Feb 25 2: 3:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 1582337BE80 for ; Fri, 25 Feb 2000 02:03:53 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 0751B1FDE; Fri, 25 Feb 2000 11:03:51 +0100 (CET) Date: Fri, 25 Feb 2000 11:03:51 +0100 From: Pascal Hofstee To: "Rodney W. Grimes" Cc: Pascal Hofstee , Garrett Wollman , Chris Wasser , freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline Message-ID: <20000225110351.A3811@shadowmere.student.utwente.nl> References: <20000224231842.B74208@shadowmere.student.utwente.nl> <200002250925.BAA69805@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002250925.BAA69805@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Fri, Feb 25, 2000 at 01:25:59AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 25, 2000 at 01:25:59AM -0800, Rodney W. Grimes wrote: > > There was a patch of DC21143 chips it seems that has a very strange > thermal problem. Can you tell me what your hub link lite is doing > when you see this major slow down? Nope ... as this machine is connected directly to the UTP-socket in the wall .. which is connected to an HP-switch which is hidden in a locked 19" rackmount (without a looking glass). > If you abort all traffic does the link light keep blinking wildly? > > If you power the machine down for an hour or so and let everything cool > down nice and cool does it seem to work for a longer period of time before > the speed drops? As far as i can remember leaving the system powered down for a longer period of time indeed seems to make the connection work properly again for a (little) while ... at least a short power-down to give everything a chance to reinitialize hardly ever seems to be working. > If you see any of these symptoms call Kingston tech support, describe > the problem to them, ask them for an RMA number :-) > > What is the date code on your DC21143 chip (I think I am recalling that > you said you had a KNE100TX, and I am assuming you do, and that it is > of new enough vintage to be the 21143 chip, and that it might be in this > same range of chips we had problems with (33% of 4 lots of 20 cards would > go to la la land within 1 to 2 hours of being placed into burn in). Well .. it's not my own system which is having these problems but of a friend of mine ... I'll check this information with him today and have a talk with the place that sold us this card. Thank you very much for providing this insight ... -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 2: 8:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 12F0737C1B4 for ; Fri, 25 Feb 2000 02:08:28 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA65259; Fri, 25 Feb 2000 02:08:18 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B65491.5BB196CC@gorean.org> Date: Fri, 25 Feb 2000 02:08:17 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Munehiro Matsuda Cc: bloom@acm.org, freebsd-current@FreeBSD.ORG Subject: Re: mergemaster fail with crypto changes References: <20000225135218A.haro@tk.kubota.co.jp> <38B5FF33.DE8D6C6A@acm.org> <20000225153546A.haro@tk.kubota.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Munehiro Matsuda wrote: > > Well that does't seem to work for me. Becase mergemaster doesn't use > NOCRYPT stuff and /usr/src/crypto doesn't exist by default, if you > just cvsup (or use CTM for my case). > > I think checking for crypto is just simple. It probably will be, but we all need time to adjust to these massive changes. Please give me a little time to get my source tree, etc. up to date. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 2:24:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id DDBA337BB58; Fri, 25 Feb 2000 02:24:36 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA96596; Fri, 25 Feb 2000 12:24:22 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200002251024.MAA96596@zibbi.mikom.csir.co.za> Subject: etc/Makefile patch To: peter@freebsd.org, current@freebsd.org Date: Fri, 25 Feb 2000 12:24:22 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a missing / in the .if that protects the addition of the ssh config files. The result is that they will never be installed. With this patch mergemaster was able to install them. John -- John Hay -- John.Hay@mikom.csir.co.za Index: etc/Makefile =================================================================== RCS file: /home/ncvs/src/etc/Makefile,v retrieving revision 1.215 diff -u -r1.215 Makefile --- etc/Makefile 2000/02/25 05:16:44 1.215 +++ etc/Makefile 2000/02/25 09:08:51 @@ -20,7 +20,7 @@ ${.CURDIR}/../usr.bin/mail/misc/mail.rc \ ${.CURDIR}/../usr.bin/locate/locate/locate.rc -.if exists(${.CURDIR}../crypto) && !defined(NO_OPENSSH) +.if exists(${.CURDIR}/../crypto) && !defined(NO_OPENSSH) BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \ ${.CURDIR}/../crypto/openssh/sshd_config .endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:17:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 0CCC937BCB3; Fri, 25 Feb 2000 04:17:44 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id DB246CC29; Fri, 25 Feb 2000 13:17:28 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <23039.951452941@zippy.cdrom.com> References: <23039.951452941@zippy.cdrom.com> Date: Fri, 25 Feb 2000 12:09:31 +0100 To: "Jordan K. Hubbard" , Bill Swingle From: Brad Knowles Subject: Re: anon FTP setup on Feb 23 SNAP Cc: Mike Tancsa , current@FreeBSD.ORG, Jordan Hubbard Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:29 PM -0800 2000/2/24, Jordan K. Hubbard wrote: > It's been turned around because people usually just hit return without > reading the dialogs and I didn't think defaulting to anonymous ftp > access was an especially good idea. :) Thank you! -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:17:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id B7BA837BCB3 for ; Fri, 25 Feb 2000 04:17:50 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 294EDCB62; Fri, 25 Feb 2000 13:17:39 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200002250913.BAA69782@gndrsh.dnsmgr.net> References: <200002250913.BAA69782@gndrsh.dnsmgr.net> Date: Fri, 25 Feb 2000 12:14:17 +0100 To: "Rodney W. Grimes" , wollman@khavrinen.lcs.mit.edu (Garrett Wollman) From: Brad Knowles Subject: Re: dc0 wierdness with Compex Freedomline Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:13 AM -0800 2000/2/25, Rodney W. Grimes wrote: > So infact the Layer 2 maximal data rate of 100BaseTX is 97.5929Mb/s or > 12.1912MB/s. I'll leave the Layer 3 to 7 calculation up to the reader, > as I am a hardware geek and I showed you how to do the calculations > at the hardwire layer, you software geeks can go figure out the > overhead for the software layers :-). I always enjoy seeing detailed discussions of things like this. I may not ever need this information, and I probably won't remember it if I do, but I will probably remember that I read something about it before and can go back and re-read what you just posted. Thanks! -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:48:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 0B84E37BD22; Fri, 25 Feb 2000 04:48:20 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id NAA17251; Fri, 25 Feb 2000 13:47:09 +0100 (CET) Date: Fri, 25 Feb 2000 13:47:08 +0100 From: Martin Cracauer To: "David O'Brien" Cc: Martin Cracauer , Bruce Evans , jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) Message-ID: <20000225134708.B16847@cons.org> References: <20000223100036.A4872@cons.org> <20000223143101.A5971@cons.org> <20000224110244.A89479@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000224110244.A89479@dragon.nuxi.com>; from obrien@NUXI.com on Thu, Feb 24, 2000 at 11:02:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000224110244.A89479@dragon.nuxi.com>, David O'Brien wrote: > On Wed, Feb 23, 2000 at 02:31:01PM +0100, Martin Cracauer wrote: > > Where's the bug, anyway? Do we need to fix the compiler or would it be > > better to get a newer assembler? > > A new assembler (whole binutils) is on the way, probably around the end > of March. In my opinion, we need a fix before 4.0. At the very least the assembler warning must be turned into an error. It is also not clear to me that the new assembler really fixes the bug. While I cannot judge over the correctness of the syntax, I think it is possible that the new assembler still works on the same syntax, not recognizing the parameterless GOTOFF our gcc generates. It is possible that we indroduced the bug by our profiling changes? The line in i386.c that generates the code in question is from revision 1.5, which is the profiling delta from the original gcc. In that case we can't count on a new gas fixing it for us. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:51:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id F1EF437BE66; Fri, 25 Feb 2000 04:51:44 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.5.62]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 2FCB95932; Fri, 25 Feb 2000 13:51:41 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id DA57C4E3F; Fri, 25 Feb 2000 13:51:40 +0100 (CET) Date: Fri, 25 Feb 2000 13:51:40 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Cc: markm@freebsd.org Subject: openssh uses /etc (bad) Message-ID: <20000225135140.A476@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just saw that openssh (thanks Mark!) is using /etc/ for its configuration file. As the author of the "--with-etcdir" option of SSH (back in '96) and for the sake of consistency, I'd like to create a /etc/ssh directory and move everything there. We have /etc/ssl, /etc/mail, /etc/ppp, /etc/uucp and the ssh2 port uses /etc/ssh2 so it is only natural to use /etc/ssh. BTW manual build in /usr/src/crypto/openssh (i.e. outside buildworld) is rather broken but I'm sure Mark will look at that. Index: ssh.h =================================================================== RCS file: /home/ncvs/src/crypto/openssh/ssh.h,v retrieving revision 1.3 diff -u -2 -u -r1.3 ssh.h --- ssh.h 2000/02/24 23:54:44 1.3 +++ ssh.h 2000/02/25 12:28:59 @@ -63,5 +63,5 @@ #define SSH_SERVICE_NAME "ssh" -#define ETCDIR "/etc" +#define ETCDIR "/etc/ssh" #define PIDDIR "/var/run" Index: sshd/Makefile =================================================================== RCS file: /home/ncvs/src/crypto/openssh/sshd/Makefile,v retrieving revision 1.1.1.1 diff -u -2 -u -r1.1.1.1 Makefile --- sshd/Makefile 2000/02/24 14:29:17 1.1.1.1 +++ sshd/Makefile 2000/02/25 12:35:03 @@ -30,5 +30,5 @@ .include -LDADD+= -lcrypto -lutil -lz +LDADD+= -lcrypto -lutil -lz -lcrypt DPADD+= ${LIBCRYPTO} ${LIBUTIL} ${LIBZ} -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:55:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3A59537BC4F; Fri, 25 Feb 2000 04:55:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id NAA03820; Fri, 25 Feb 2000 13:55:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ollivier Robert Cc: "FreeBSD Current Users' list" , markm@FreeBSD.ORG Subject: Re: openssh uses /etc (bad) In-reply-to: Your message of "Fri, 25 Feb 2000 13:51:40 +0100." <20000225135140.A476@caerdonn.eurocontrol.fr> Date: Fri, 25 Feb 2000 13:55:37 +0100 Message-ID: <3818.951483337@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000225135140.A476@caerdonn.eurocontrol.fr>, Ollivier Robert write s: >I just saw that openssh (thanks Mark!) is using /etc/ for its configuration >file. As the author of the "--with-etcdir" option of SSH (back in '96) and >for the sake of consistency, I'd like to create a /etc/ssh directory and >move everything there. yes -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 4:58:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.a-net.ne.jp (ns.a-net.ne.jp [210.161.126.226]) by hub.freebsd.org (Postfix) with SMTP id 2E4AF37BD23; Fri, 25 Feb 2000 04:58:11 -0800 (PST) (envelope-from ganba@a-net.ne.jp) Received: from mail.a-net.ne.jp (unverified [210.161.126.7]) by ns.a-net.ne.jp (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 25 Feb 2000 21:55:52 +0900 Message-ID: <200002252157.529@ganba.a-net.ne.jp> Date: Fri, 25 Feb 2000 21:57:17 +0900 From: =?ISO-2022-JP?B?GyRCJCIkZiRfGyhC?= To: ganba@a-net.ne.jp Subject: =?ISO-2022-JP?B?GyRCJGgkJiQzJD0hIiQiJGYkXyROJVshPCVgJVohPCU4GyhC?= =?ISO-2022-JP?B?GyRCJFgbKEI=?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Mailer: Gen Mail 0.9b X-Antirelay: Good relay from local net2 210.161.126.0/24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B$O$8$a$^$7$F!"$"$f$_(B $B$H8@$$$^$9!#(B $BFMA3$N%a!<%k$G!"$4$a$s$J$5$$!#(B $B$3$s$J;d$,%[!<%`%Z!<%8$r:n$C$A$c$$$^$7$?!#(B $B$^$@!"2?$bL5$$$s$@$1$I!&!&!&!#(B $B$G$b!"$3$s$J;d$G$b(B"$B%j!{%k!<%He$KBg$-$/$H$j$"$2$F$b$i$($F$H$C$F$b%O%C%T!<$G$9!#(B http://www1.sphere.ne.jp/cube/idol/ $B$I$)! Date: Fri, 25 Feb 2000 09:03:43 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: "FreeBSD Current Users' list" , markm@FreeBSD.ORG Subject: Re: openssh uses /etc (bad) References: <20000225135140.A476@caerdonn.eurocontrol.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not suprised to here this. The Makefiles in that directory are from OpenBSD's version of openssh. If you want to build ssh manually, you will need to build parts of /usr/src/secure/{lib,user.sbin,usr.bin} and /usr/src/lib/libpam. The makefiles are for reference only. Jim Bloom bloom@acm.org Ollivier Robert wrote: > > BTW manual build in /usr/src/crypto/openssh (i.e. outside buildworld) is > rather broken but I'm sure Mark will look at that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 6:10:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 0AD2537BA81 for ; Fri, 25 Feb 2000 06:10:38 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28583 invoked from network); 25 Feb 2000 14:10:31 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 25 Feb 2000 14:10:31 -0000 Date: Sat, 26 Feb 2000 01:10:26 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Martin Cracauer Cc: David O'Brien , jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) In-Reply-To: <20000225134708.B16847@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Feb 2000, Martin Cracauer wrote: > It is also not clear to me that the new assembler really fixes the > bug. While I cannot judge over the correctness of the syntax, I think > it is possible that the new assembler still works on the same syntax, > not recognizing the parameterless GOTOFF our gcc generates. I happen to have a Linux gas built from a relatively recent version of binutils. It still has the problem. Surprisingly, both assemblers handle: leal foo@GOTOFF,%eax but neither handles the equivalent: movl $foo@GOTOFF,%eax > It is possible that we indroduced the bug by our profiling changes? > The line in i386.c that generates the code in question is from > revision 1.5, which is the profiling delta from the original gcc. In > that case we can't count on a new gas fixing it for us. Reverting to the FSF version of i386.c didn't fix the problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 7:25:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id C796537BDF5 for ; Fri, 25 Feb 2000 07:25:54 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.147.129.124]) by forrie.net with id e1PFPnj71718 for ; Fri, 25 Feb 2000 10:25:50 -0500 (EST) Message-Id: <4.2.2.20000225102306.00c59600@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 25 Feb 2000 10:23:37 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Streamlining FreeBSD installations across many machines Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps this would be of interest in CURRENT issues: We have several servers that we plan on deploying across the US. Their purpose in life is network status and monitoring. The hardware profiles are exactly the same... Currently, we're using DD to mirror a disk image onto a new installation, and them nanually tweaking all the necessary configurations. It's tedious, and is going to get hellish with the amount we plan on deploying. I'm wondering if there might not be a way to streamline this install process, such that a boot floopy and script could be created to take a minimum amount of information, and then "do the right thing" as for the install. Things like putting in the packet filters, the kernel, IP config, etc. Surely someone has done this before...? Any pointers would be greatly appreciated. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 7:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8852237BDF5 for ; Fri, 25 Feb 2000 07:29:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA04557; Fri, 25 Feb 2000 16:29:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Streamlining FreeBSD installations across many machines In-reply-to: Your message of "Fri, 25 Feb 2000 10:23:37 EST." <4.2.2.20000225102306.00c59600@216.67.12.69> Date: Fri, 25 Feb 2000 16:29:54 +0100 Message-ID: <4555.951492594@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.2.20000225102306.00c59600@216.67.12.69>, Forrest Aldrich writes : >Perhaps this would be of interest in CURRENT issues: > > >We have several servers that we plan on deploying across the US. Their >purpose in life is network status and monitoring. The hardware profiles >are exactly the same... > >Currently, we're using DD to mirror a disk image onto a new installation, >and them nanually tweaking all the necessary configurations. It's >tedious, and is going to get hellish with the amount we plan on deploying. There was actually a good deal of interest in this at FreeBSDcon'99, and I belive we managed to bully^H^H^H^H^H^Hpersuade Wes Peters to take an active role in coordinating efforts in this area ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 7:39:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 42A1D37BD1C for ; Fri, 25 Feb 2000 07:39:30 -0800 (PST) (envelope-from ivt@logger.gamma.ru) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id SAA86928; Fri, 25 Feb 2000 18:39:26 +0300 (MSK) From: Igor Timkin Message-Id: <200002251539.SAA86928@logger.gamma.ru> Subject: Re: dump of vinum disks In-Reply-To: <200002171009.NAA75066@logger.gamma.ru> from Igor Timkin at "Feb 17, 2000 01:09:52 pm" To: Igor Timkin Date: Fri, 25 Feb 2000 18:39:26 +0300 (MSK) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 Who will correct dump (dump use /dev/rXXX instead of /dev/XXX) ? I wrote: > Yesterday current: > ivt@newsfeed:/news/etc:2:770>uname -a > FreeBSD newsfeed.gamma.ru 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Feb 16 03:00:26 MSK 2000 ivt@newsfeed.gamma.ru:/usr/src/sys/compile/NEWSFEED i386 > ivt@newsfeed:/news/etc:2:771>dump 0f /dev/null /news > DUMP: Date of this level 0 dump: Thu Feb 17 12:24:34 2000 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/vinum/rraid0 (/news) to /dev/null > DUMP: Cannot open /dev/vinum/rraid0 > vt@newsfeed:/news/etc:2:772>dump 0f /dev/null /dev/vinum/raid0 > DUMP: Date of this level 0 dump: Thu Feb 17 12:25:10 2000 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/vinum/rraid0 (/news) to /dev/null > DUMP: Cannot open /dev/vinum/rraid0 > vt@newsfeed:/news/etc:2:773>ls -ltr /dev/vinum > total 4 > drwxr-xr-x 2 root wheel 512 Feb 16 06:13 drive > drwxr-xr-x 2 root wheel 512 Feb 16 06:13 plex > drwxr-xr-x 2 root wheel 512 Feb 16 06:13 sd > drwxr-xr-x 3 root wheel 512 Feb 16 06:13 vol > crw------- 1 root wheel 91, 0x40000001 Feb 16 06:13 Control > crw------- 1 root wheel 91, 0x40000002 Feb 16 06:13 control > crw------- 1 root wheel 91, 0x40000000 Feb 16 06:13 controld > crw-r----- 1 root operator 91, 0 Feb 16 06:14 raid0 > (vinum create vinum's disks with ``wheel'' group, so i made > chgrp operator raid0). > > Just moment solution is (cd /dev/vinum; ln raid0 rraid0). > > > 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 Feb 25 7:45:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [207.249.162.252]) by hub.freebsd.org (Postfix) with ESMTP id DE01337BCFD for ; Fri, 25 Feb 2000 07:45:48 -0800 (PST) (envelope-from ales@megared.net.mx) Received: from ales (ales2.megared.net.mx [207.249.163.241]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id JAA26057; Fri, 25 Feb 2000 09:45:47 -0600 (CST) (envelope-from ales@megared.net.mx) Message-ID: <007301bf7fa7$564b3aa0$020a0a0a@megared.net.mx> From: "Alejandro Ramirez" To: "urania" , References: <38B5F15E.82197160@iss.com.tw> Subject: RE: Problem with IBM Netfinity 5000 Server Date: Fri, 25 Feb 2000 09:45:26 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Don't things realy strage ? > Everything wroks fine if 1th-4th PCI slot is empty, no device > attached. > Same kernel, Same Applications its running .... I have had problems with the 1st PCI slot in the IBM Netfinity 5000, it reboots my system constantly, I dont know why, but now Im not using this slot any more, and everything runs great. Greetings Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 8: 3:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 7421537C361; Fri, 25 Feb 2000 08:03:28 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA154846; Fri, 25 Feb 2000 11:03:18 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000225135140.A476@caerdonn.eurocontrol.fr> References: <20000225135140.A476@caerdonn.eurocontrol.fr> Date: Fri, 25 Feb 2000 11:03:37 -0500 To: Ollivier Robert , "FreeBSD Current Users' list" From: Garance A Drosihn Subject: Re: openssh uses /etc (bad) Cc: markm@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:51 PM +0100 2/25/00, Ollivier Robert wrote: >I just saw that openssh (thanks Mark!) is using /etc/ for its configuration >file. As the author of the "--with-etcdir" option of SSH (back in '96) and >for the sake of consistency, I'd like to create a /etc/ssh directory and >move everything there. I have always installed ssh that way too (so thanks for the option! :-). When I am rebuilding a system, ssh is about the first thing I bring up, and I want to make sure I do that with all the right settings and hostkey. Having all those files inside one directory makes that easy. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 8: 8: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 77EB937B884; Fri, 25 Feb 2000 08:07:56 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id TAA59409; Fri, 25 Feb 2000 19:07:55 +0300 (MSK) (envelope-from ache) Date: Fri, 25 Feb 2000 19:07:54 +0300 From: "Andrey A. Chernov" To: markm@freebsd.org Cc: current@freebsd.org Subject: OpenSSH bugs with login.conf Message-ID: <20000225190754.A59343@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How to reproduce bug: with default /etc/login.conf try to log in using standard login (1) and "ssh localhost" (2). Then "echo $FTP_PASSIVE_MODE". You'll have "YES" in case (1) and "Undefined variable." in case (2). User's ~/.login_conf not handled too. Please use corresponding security/ssh/patches/patch-af to fix the problem Searching for HAVE_LOGIN_CAP_H in whole sources (not in patches only) will help (sshd.c and userfile.c are affected). Patched standard ssh1 from ports deal with login.conf in correct way. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 8:26:24 2000 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 B2B3337BEC6 for ; Fri, 25 Feb 2000 08:26:15 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA30533; Fri, 25 Feb 2000 11:25:59 -0500 (EST) (envelope-from wollman) Date: Fri, 25 Feb 2000 11:25:59 -0500 (EST) From: Garrett Wollman Message-Id: <200002251625.LAA30533@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002250913.BAA69782@gndrsh.dnsmgr.net> References: <200002241907.OAA27437@khavrinen.lcs.mit.edu> <200002250913.BAA69782@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> [I wrote:] >> quite right. In a CSMA/CD medium access protocol, like that used by >> Ethernet, the actual capacity of the link is always(*) somewhat less than >> 100%; the exact value depends on the precise parameters of the >> transmissions at both ends.(**) >> (*)In non-trivial conditions; i.e., when actual work is being done. >> (**)I've heard numbers between 70% and 95%. > And the major set of parameters that effect the higher side of this > number are MTU(Maximum Transmission Unit) and IFG (Interframe Gap) > and the protocol overhead of what ever proto you are using. Nope. Those two values are defined by the protocol, and are not parameters at all. (It's only a parameter if it could conceivably be varied in an experiment.) The relevant parameters are the transmission schedules of the end stations, which are of course dynamic in most real-world applications, but not necessarily so. These can be boiled down into a single number P(coll), which is the probability that two stations will cause a collision by transmitting at precisely the same time. Although this seems unlikely, certain kinds of network protocols can unintentionally synchronize end-stations to the extent of causing pessimal behavior. Back in the mists of ancient time, this was considered one of the major arguments against CSMA/CD protocols and for token-passing protocols, and many academic papers were written about it. How horrifying, that your dearly-bought 10-Mbit/s (or even 3-Mbit/s) Ethernet channel could be wasting 30% of its capacity on collisions! Nowadays, we recognize that the sort of protocols which show pathological behavior are a bad idea for lots of reasons, and the normal operation of TCP and IP over an Ethernet channel results in significantly better than worst-case behavior. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 8:45:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 196B237BB4F for ; Fri, 25 Feb 2000 08:45:44 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 12ONs7-000KMS-00 for freebsd-current@freebsd.org; Fri, 25 Feb 2000 08:45:43 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: install-info problem? Message-Id: Date: Fri, 25 Feb 2000 08:45:43 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> lib/libcom_err/doc install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 9:19:22 2000 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 9C36D37BD54 for ; Fri, 25 Feb 2000 09:19:20 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA81439; Fri, 25 Feb 2000 09:21:13 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200002251721.JAA81439@troutmask.apl.washington.edu> Subject: Re: install-info problem? In-Reply-To: from Randy Bush at "Feb 25, 2000 08:45:43 am" To: Randy Bush Date: Fri, 25 Feb 2000 09:21:13 -0800 (PST) Cc: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL61 (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 Randy Bush wrote: > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > See end of /usr/src/UPDATING. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 9:25:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 0A4A637BEBF for ; Fri, 25 Feb 2000 09:25:28 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA70872; Fri, 25 Feb 2000 09:24:58 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251724.JAA70872@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <20000225110351.A3811@shadowmere.student.utwente.nl> from Pascal Hofstee at "Feb 25, 2000 11:03:51 am" To: daeron@wit401305.student.utwente.nl (Pascal Hofstee) Date: Fri, 25 Feb 2000 09:24:58 -0800 (PST) Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Feb 25, 2000 at 01:25:59AM -0800, Rodney W. Grimes wrote: > > > > There was a patch of DC21143 chips it seems that has a very strange > > thermal problem. Can you tell me what your hub link lite is doing > > when you see this major slow down? > > Nope ... as this machine is connected directly to the UTP-socket in the > wall .. which is connected to an HP-switch which is hidden in a locked 19" > rackmount (without a looking glass). :-(. Then do the next best thing, look at the lights on the back of the card (another reason I like the KNE100TX, it has them, not all DC21x4x cards do.) > > If you abort all traffic does the link light keep blinking wildly? > > > > If you power the machine down for an hour or so and let everything cool > > down nice and cool does it seem to work for a longer period of time before > > the speed drops? > > As far as i can remember leaving the system powered down for a longer > period of time indeed seems to make the connection work properly again for > a (little) while ... at least a short power-down to give everything a > chance to reinitialize hardly ever seems to be working. Sounds like we might be on the right track. > > If you see any of these symptoms call Kingston tech support, describe > > the problem to them, ask them for an RMA number :-) > > > > What is the date code on your DC21143 chip (I think I am recalling that > > you said you had a KNE100TX, and I am assuming you do, and that it is > > of new enough vintage to be the 21143 chip, and that it might be in this > > same range of chips we had problems with (33% of 4 lots of 20 cards would > > go to la la land within 1 to 2 hours of being placed into burn in). > > Well .. it's not my own system which is having these problems but of a > friend of mine ... I'll check this information with him today and have a > talk with the place that sold us this card. > > Thank you very much for providing this insight ... Your welcome. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 9:37:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 20D3237B920 for ; Fri, 25 Feb 2000 09:37:21 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA70913; Fri, 25 Feb 2000 09:37:02 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251737.JAA70913@gndrsh.dnsmgr.net> Subject: Re: Streamlining FreeBSD installations across many machines In-Reply-To: <4.2.2.20000225102306.00c59600@216.67.12.69> from Forrest Aldrich at "Feb 25, 2000 10:23:37 am" To: forrie@forrie.com (Forrest Aldrich) Date: Fri, 25 Feb 2000 09:37:02 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps this would be of interest in CURRENT issues: > > > We have several servers that we plan on deploying across the US. Their > purpose in life is network status and monitoring. The hardware profiles > are exactly the same... > > Currently, we're using DD to mirror a disk image onto a new installation, > and them nanually tweaking all the necessary configurations. It's > tedious, and is going to get hellish with the amount we plan on deploying. A much faster way to do this is to just dd the first few megabytes of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use dump | restore to populate the disk. (We actually have 3.x and 4.x recent build filesystems that are built weekly on a master loading machine just for this purpose.) We mass produce system disk this way and it is much faster than a whole disk image operation especially when dealing with drives much larger than 2G bytes. > I'm wondering if there might not be a way to streamline this install > process, such that a boot floopy and script could be created to take a > minimum amount of information, and then "do the right thing" as for the > install. Things like putting in the packet filters, the kernel, IP > config, etc. > > Surely someone has done this before...? We do it on a weekly basis, 4 to 32 disks at a time... > Any pointers would be greatly appreciated. Hope this gives you some ideas... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 9:53:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BDFE537B8CD for ; Fri, 25 Feb 2000 09:53:45 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA70936; Fri, 25 Feb 2000 09:53:37 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251753.JAA70936@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251625.LAA30533@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 25, 2000 11:25:59 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 25 Feb 2000 09:53:37 -0800 (PST) Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> [I wrote:] > >> quite right. In a CSMA/CD medium access protocol, like that used by > >> Ethernet, the actual capacity of the link is always(*) somewhat less than > >> 100%; the exact value depends on the precise parameters of the > >> transmissions at both ends.(**) > > >> (*)In non-trivial conditions; i.e., when actual work is being done. > >> (**)I've heard numbers between 70% and 95%. > > > And the major set of parameters that effect the higher side of this > > number are MTU(Maximum Transmission Unit) and IFG (Interframe Gap) > > and the protocol overhead of what ever proto you are using. > > Nope. Those two values are defined by the protocol, and are not > parameters at all. (It's only a parameter if it could conceivably be > varied in an experiment.) Don't tell the guys at PARC, Intel, DEC or TRW these are not parameters, the MTU as defined by the ethernet specification has a minimal and maximal value. That pretty much makes it a parameter. Also the 1518 bytes is the in-spec maximal but many chips, even the old 82586, could be programmed to do 4K or larger frames. (TRW takes advantage of the 82586's ability to do 16KByte frames for pumping huge images around very effecently on ethernet. Given that I have worked on real world systems that modify the MTU to reach a desired goal I can state without a doubt that MTU is a paramter, as I have changed not just in experiments or on paper, but in the real world with 1000's of systems deployed using the tweaked value, including having to hack out the jabber circuits in hubs to deal with the frame size.) > The relevant parameters are the > transmission schedules of the end stations, which are of course > dynamic in most real-world applications, but not necessarily so. Those parameters mean nothing when caclulating the Data Link layer maximal transmission rate possible. If they use them then you are calculation something else, like the application maximal transmission rate. > These can be boiled down into a single number P(coll), which is the > probability that two stations will cause a collision by transmitting > at precisely the same time. Although this seems unlikely, certain > kinds of network protocols can unintentionally synchronize > end-stations to the extent of causing pessimal behavior. I specifically excluded P(coll) by stating point to point or effectively point to point via switching. P(coll) is 0 in this situation, again going to my note of keyword ``maximal''. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 9:54: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from michael.ithinc.net (michael.ithinc.net [207.70.152.4]) by hub.freebsd.org (Postfix) with SMTP id 1915D37B8CD for ; Fri, 25 Feb 2000 09:53:53 -0800 (PST) (envelope-from jgordon@lhtech-inc.com) Received: (qmail 22341 invoked from network); 25 Feb 2000 17:58:10 -0000 Received: from dominic.ithinc.net (HELO jgordon) (207.70.152.2) by michael.ithinc.net with SMTP; 25 Feb 2000 17:58:10 -0000 Message-ID: <007601bf7fba$40d3cc10$6800300a@lhtechinc.com> From: "Jeffrey D. Gordon" To: Subject: Missing in RC2 Date: Fri, 25 Feb 2000 12:00:51 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the RC2 .iso there is not tools/ directory containing fdimage, rawrite, etc! Plus the CD doesn't boot with keyboard support suprisingly on our PS2 based testserver (already running 3.4 quite happily) Thanks! Jeff -- Jeffrey D. Gordon jgordon@lhtech-inc.com Network Administrator/Development Programmer Lighthouse Technologies http://www.lhtech-inc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 10: 8: 9 2000 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 A1F3E37BBBE for ; Fri, 25 Feb 2000 10:08:06 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA30934; Fri, 25 Feb 2000 13:08:01 -0500 (EST) (envelope-from wollman) Date: Fri, 25 Feb 2000 13:08:01 -0500 (EST) From: Garrett Wollman Message-Id: <200002251808.NAA30934@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251753.JAA70936@gndrsh.dnsmgr.net> References: <200002251625.LAA30533@khavrinen.lcs.mit.edu> <200002251753.JAA70936@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I specifically excluded P(coll) by stating point to point or effectively > point to point via switching. Rod, please bother to READ what people write before spewing nonsense. The original question asked SPECIFICALLY about half-duplex. I answered SPECIFICALLY about half-duplex. End Of Story. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 10:17:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id DF32237BCAE for ; Fri, 25 Feb 2000 10:17:06 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id KAA05438 for ; Fri, 25 Feb 2000 10:17:12 -0800 Received: by shell1.aracnet.com (8.9.3) id KAA03152; Fri, 25 Feb 2000 10:18:09 -0800 Date: Fri, 25 Feb 2000 10:18:09 -0800 (PST) From: Brian Beattie To: freebsd-current@freebsd.org Subject: Serial console on sio3 Message-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 would like to use sio3 as my serial console and automatically using the serial console. I changed BOOT_COMCONSOLE to the right value did a make clean, make, make install in /sys/boot/i386, reconfig'd and built the kernel, set /boot.config to contain -h. It mostly works. What happens is that after selecting the partition(slice), it prints the "-h" and opens sio0!, since I have a mouse on that port, the boot hangs. If I disconnect the mouse before booting, the boot succeeds. the system is 4.0 current from this week. any hints? Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 10:28:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id C2ADF37BC6F for ; Fri, 25 Feb 2000 10:28:39 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA71012; Fri, 25 Feb 2000 10:28:15 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251828.KAA71012@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251808.NAA30934@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 25, 2000 01:08:01 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 25 Feb 2000 10:28:15 -0800 (PST) Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > I specifically excluded P(coll) by stating point to point or effectively > > point to point via switching. > > Rod, please bother to READ what people write before spewing nonsense. I did read it, and did not spew nonsense. P(coll) is non-sense when talking about maximal. > The original question asked SPECIFICALLY about half-duplex. It also asked about ``maximal'', I solved the equations for maximal, to achive maximal P(coll)=0. > I answered SPECIFICALLY about half-duplex. The duplex does not in any way effect the maximal link layer transmission data rate. You seem to keep forgetting the maximal part... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 10:33:33 2000 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 1D0DA37BD6D for ; Fri, 25 Feb 2000 10:33:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA31071; Fri, 25 Feb 2000 13:33:16 -0500 (EST) (envelope-from wollman) Date: Fri, 25 Feb 2000 13:33:16 -0500 (EST) From: Garrett Wollman Message-Id: <200002251833.NAA31071@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251828.KAA71012@gndrsh.dnsmgr.net> References: <200002251808.NAA30934@khavrinen.lcs.mit.edu> <200002251828.KAA71012@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> I answered SPECIFICALLY about half-duplex. > The duplex does not in any way effect the maximal link layer transmission > data rate. You seem to keep forgetting the maximal part... The maximum for full-duplex is utterly irrelevant, since the bounds on performance for half-duplex Ethernet networks come from CSMA/CD. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 10:45:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AEA9537BBE8; Fri, 25 Feb 2000 10:45:34 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA15018; Fri, 25 Feb 2000 10:45:34 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Feb 2000 10:45:34 -0800 (PST) From: Kris Kennaway To: Ollivier Robert Cc: "FreeBSD Current Users' list" , markm@freebsd.org Subject: Re: openssh uses /etc (bad) In-Reply-To: <20000225135140.A476@caerdonn.eurocontrol.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Feb 2000, Ollivier Robert wrote: > I just saw that openssh (thanks Mark!) is using /etc/ for its configuration > file. As the author of the "--with-etcdir" option of SSH (back in '96) and > for the sake of consistency, I'd like to create a /etc/ssh directory and > move everything there. In case you hadn't already found out, Peter fixed this. > We have /etc/ssl, /etc/mail, /etc/ppp, /etc/uucp and the ssh2 port uses > /etc/ssh2 so it is only natural to use /etc/ssh. > > BTW manual build in /usr/src/crypto/openssh (i.e. outside buildworld) is > rather broken but I'm sure Mark will look at that. crypto/ is the analogue of contrib/ for crypto code. You're not supposed to build there..look under secure/. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 11: 8:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 8A06437BA9B for ; Fri, 25 Feb 2000 11:08:34 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA71093; Fri, 25 Feb 2000 11:08:24 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002251908.LAA71093@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251833.NAA31071@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 25, 2000 01:33:16 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 25 Feb 2000 11:08:24 -0800 (PST) Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> I answered SPECIFICALLY about half-duplex. > > > The duplex does not in any way effect the maximal link layer transmission > > data rate. You seem to keep forgetting the maximal part... > > The maximum for full-duplex is utterly irrelevant, since the bounds on > performance for half-duplex Ethernet networks come from CSMA/CD. I will say it one last time, duplex falls out of the equations when you solve for ``maximal''. It has 0 meaning in the numbers used. Go read my analysis and tell me why I can't pump 12MB/sec on 100BaseTX, tell me that my 15 years of doing 97.5% of data clock on ethernet just doesn't happen. Then tell me why it can't happen, show me numbers and equations and I'll show you how you forget the keyword maximal and keep jumping over to something less than maximal as your not narrowing the scope of what it is your measureing/calculating. You keep throwing P(coll) in, P(coll) only occurs if your upper layer is causing P(coll) by doing things like ack packets. CSMA/CD does not define this. It defines the exact things I have used in the calculations to derive the number. There is no other number and no other formula to apply when solving for maximal. I can back up my numbers with lab data, 15 years of lab data. The only thing that effects maximal data transfer on a CSMA/CD network is IFG, MTU (not the upper layer MTU the layer 2 frame MTU) and layer 2 overhead bytes as clearly formulated in my post (preamble, Start of Frame, Source Address, Destination Address, type and CRC). The IFG is the multi-access window, if no one else accesses the media during the IFG (technically a violation of spec) one is free to start your next frame of transmission. If 2 nodes attempt to access the media at end of IFG you have P(coll), solving for maximal says that this never occurs to get maximal. THAT IS THE END OF THE STORY AS IT WORKS IN THE REAL WORLD DAY AFTER DAY IN 4 DESIGNS I HAVE DONE FOR PEOPLE. The only bloody ack that can cause a collission in our l3 design occurs after the whole of the data transfer, thus they don't effect our 1 way data transfer rate except by 64 bytes in Megabytes of data which shows up out in the 4th or 5th digit and is _NOT_ the maximal link layer data rate (the link layer is till doing 97.5% of data clock, the data is just going the other way :-)). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 11:21:25 2000 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 726C037BA4D for ; Fri, 25 Feb 2000 11:21:20 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA31520; Fri, 25 Feb 2000 14:21:15 -0500 (EST) (envelope-from wollman) Date: Fri, 25 Feb 2000 14:21:15 -0500 (EST) From: Garrett Wollman Message-Id: <200002251921.OAA31520@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251908.LAA71093@gndrsh.dnsmgr.net> References: <200002251833.NAA31071@khavrinen.lcs.mit.edu> <200002251908.LAA71093@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> The maximum for full-duplex is utterly irrelevant, since the bounds on >> performance for half-duplex Ethernet networks come from CSMA/CD. > I will say it one last time, duplex falls out of the equations when you > solve for ``maximal''. Nonsense. > It has 0 meaning in the numbers used. Go read > my analysis and tell me why I can't pump 12MB/sec on 100BaseTX, By no means -- you certainly can do that, if you have only one station sending at a time. Of course, a monologue is by definition not useful communication. > You keep throwing P(coll) in, P(coll) only occurs if your upper layer is > causing P(coll) by doing things like ack packets. I'd certainly like to see a demonstration of your network using ESP for reliability. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 12: 7:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 623DC37BB09; Fri, 25 Feb 2000 12:07:20 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA12839; Fri, 25 Feb 2000 15:07:19 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200002252007.PAA12839@blackhelicopters.org> Subject: HP servers and FreeBSD? To: questions@freebsd.org Date: Fri, 25 Feb 2000 15:07:18 -0500 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've been offered a deal on a couple of HP servers. Does anyone have any experience with the HP Netserver LC3 7/550? How about the HP Surestore DAT 12/24? These machines will be dedicated to testing 4.0 for the next six months or so, so I'm copying -current. (Sorry, I'll shut up now.) Thanks, ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13: 1:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from ixori.demon.nl (ixori.demon.nl [195.11.248.5]) by hub.freebsd.org (Postfix) with ESMTP id 6E18A37BBA3 for ; Fri, 25 Feb 2000 13:00:53 -0800 (PST) (envelope-from bart@ixori.demon.nl) Received: from smtp-relay by ixori.demon.nl (8.9.3/8.9.2) with ESMTP id VAA17497 for ; Fri, 25 Feb 2000 21:58:52 +0100 (CET) (envelope-from bart@ixori.demon.nl) Received: from network (intranet) by smtp-relay (Bart's intranet smtp server) Message-ID: <38B70928.D20A72F1@ixori.demon.nl> Date: Fri, 25 Feb 2000 21:58:48 -0100 From: Bart van Leeuwen X-Mailer: Mozilla 4.61 [en] (X11; I; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: RC2, some problems. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, After getting me an iso image of RC2 and trying to install it I encountered 2 small problems. Both are easy to solve for the more expereinced user, but are annoying nonetheless. Both have to do with the packages collection on the cd. 1. Netscape Communicator 4.7 for FreeBSD. as most people prolly know, this program requires aout libs, and not just the stuff from compatxx, but also the aout libs for X11. The two ways a user has to fix this are either grabbing a copy of the aout libs somewhere or recompiling xfree with aout libs. Both are not too hard to do as long as your system is connected to the internet, but if not then you are bound to have a harder time getting this to work. Adding the XFree86 aout libs either as an option to the X distribution or as a seperate package would be a good solution. Also, quite a few people who tried RC2 here found it rather strange to find a package on the CD (netscape) that requires something to be able to run that is not installed as a dependency and worse, that they cannot find back on the distribution at all. Its silly that netscape doesnt use the ELF libraries, but its also very silly to include software on a distribution while knowing that it requires something thats not included (or at least hard to find) I'm aware this is older then 4.0 (actually I think it dates back to 3.0) but imho its a problem because it makes the distribution look incomplete and badly tested (X + netscape is one of the first things a new user will try to install and run nowadays) One could also install the linux version, but heh, being able to run a linux version but not the native version doesn't look very good either. (not to say its even more silly) 2. linux_base When installing fbsd, a directory /usr/compat is created and it is linked to /compat When trying to install the linux_base package, it fails with a message that it can't cwd to /compat It seems to expect a directory while it finds a link. Removing the link and creating a /compat dir makes that it installs perfectly well. Of course this is not hard to circumvent, but still, its annoying. As I said, relatively small problems, but imho fixing them is quite a good idea. If anyone thinks I should fix them instead of complain... well... point me where to start and I'll try ;-) For the rest, keep up the good work, 4.0-current has been running here for a long time now, and if the release is just as stable as most of the current builts that I ran so far, then things look very bright to me ;-) regards, Bart van Leeuwen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13: 2:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 513B137BBA3 for ; Fri, 25 Feb 2000 13:02:53 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id WAA01037 for ; Fri, 25 Feb 2000 22:03:11 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 25 Feb 2000 22:03:11 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: BUILDWORLD Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of our two servers will not perform "buildworld"! Well, kernel stuff should be on the newest track, I cvsup-dated them both today. After a short while making dependencies it stops with the following error: /usr/vol1/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509v3/v3err.c /usr/vol1/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/err/err_all.c:68: openssl/rsaref.h: No such file or directory /usr/vol1/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/../rsaref/rsar_err.c:62: openssl/rsaref.h: No such file or directory /usr/vol1/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/../rsaref/rsaref.c:64: openssl/rsaref.h: No such file or directory mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error I deleted /usr/src/crypto and ./secure tree and made an other cvsupdate, but with no success. Compiled a new kernel, installed it ... no success. Why? The other machine has the same stuff, I cvsupdated the same way and today, but it performs the make world task without any problems. I can not understand this behaviour ... Please help. Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13: 6:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id CA97837BBA3; Fri, 25 Feb 2000 13:06:26 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA18416; Fri, 25 Feb 2000 15:06:08 -0600 (CST) Date: Fri, 25 Feb 2000 15:06:08 -0600 From: "Matthew D. Fuller" To: "Andrey A. Chernov" Cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OpenSSH bugs with login.conf Message-ID: <20000225150607.A28385@futuresouth.com> References: <20000225190754.A59343@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000225190754.A59343@nagual.pp.ru> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 25, 2000 at 07:07:54PM +0300, a little birdie told me that Andrey A. Chernov remarked > How to reproduce bug: > with default /etc/login.conf try to log in using standard login (1) and > "ssh localhost" (2). Then "echo $FTP_PASSIVE_MODE". You'll have "YES" in > case (1) and "Undefined variable." in case (2). User's ~/.login_conf not > handled too. As long as this type of issue is coming up, I'd like to mention another related thing that's been brought up relating to the various ssh ports from time to time; namely, login.access. If we have OpenSSH in the base system, it'd be REALLY nice if it could somehow be thwacked into following the same pattern of access control/etc that every other login method uses. I haven't actually looked through ssh in general to see what sort of login process it uses, but is there any inherent reason why it can't just use login(1) like everything else, and avoid special patching and duplicated code to read the files? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13: 9: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 8E5DE37B939 for ; Fri, 25 Feb 2000 13:08:51 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id KAA09955; Sat, 26 Feb 2000 10:07:15 +1300 (NZDT) Message-Id: <200002252107.KAA09955@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: "O. Hartmann" Date: Sat, 26 Feb 2000 10:07:04 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: BUILDWORLD Problems Reply-To: dan@freebsddiary.org Cc: freebsd-current@freebsd.org In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Feb 00, at 22:03, O. Hartmann wrote: > One of our two servers will not perform "buildworld"! Well, kernel stuff > should be on the newest track, I cvsup-dated them both today. > > After a short while making dependencies it stops with the following error: [snip] > I deleted /usr/src/crypto and ./secure tree and made an other cvsupdate, > but with no success. Compiled a new kernel, installed it ... no success. > Why? The other machine has the same stuff, I cvsupdated the same way and > today, but it performs the make world task without any problems. I can not > understand this behaviour ... Please help. libcrypto is being updated. You (and the rest of us) will just have to wait until it's finished. See also the thead titled "Re: yes, current is broke...". -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13:15:58 2000 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 01E3537BBF7 for ; Fri, 25 Feb 2000 13:15:50 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA04241 for freebsd-current@FreeBSD.ORG; Fri, 25 Feb 2000 22:15:29 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6B56D87AE; Fri, 25 Feb 2000 20:04:28 +0100 (CET) Date: Fri, 25 Feb 2000 20:04:27 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: openssh uses /etc (bad) Message-ID: <20000225200427.A95939@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list References: <20000225135140.A476@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Fri, Feb 25, 2000 at 11:03:37AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Garance A Drosihn: > hostkey. Having all those files inside one directory makes that easy. Peter has committed the diff, thanks Peter! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13:40:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4F4F437BCF0 for ; Fri, 25 Feb 2000 13:40:49 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id NAA71447; Fri, 25 Feb 2000 13:40:09 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002252140.NAA71447@gndrsh.dnsmgr.net> Subject: Re: dc0 wierdness with Compex Freedomline In-Reply-To: <200002251921.OAA31520@khavrinen.lcs.mit.edu> from Garrett Wollman at "Feb 25, 2000 02:21:15 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 25 Feb 2000 13:40:09 -0800 (PST) Cc: cwasser@v-wave.com (Chris Wasser), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> The maximum for full-duplex is utterly irrelevant, since the bounds on > >> performance for half-duplex Ethernet networks come from CSMA/CD. > > > I will say it one last time, duplex falls out of the equations when you > > solve for ``maximal''. > > Nonsense. Either stop saying that or put up the formula's like I did that show that duplex enters into the L2 maximal data rate. > > It has 0 meaning in the numbers used. Go read > > my analysis and tell me why I can't pump 12MB/sec on 100BaseTX, > > By no means -- you certainly can do that, if you have only one station > sending at a time. Of course, a monologue is by definition not useful > communication. You have a very twisted definition of communication. > > You keep throwing P(coll) in, P(coll) only occurs if your upper layer is > > causing P(coll) by doing things like ack packets. > > I'd certainly like to see a demonstration of your network using ESP > for reliability. Have you ever calculated the BER of a controlled CSMA/CD network? It is something like 10^-9. I could show you 4 working implementations of this, but I would have to call the boys in grey coats afterwards. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 13:41: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 160B937BCFA for ; Fri, 25 Feb 2000 13:40:51 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 9623 invoked from network); 25 Feb 2000 21:40:46 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 25 Feb 2000 21:40:46 -0000 Date: Sat, 26 Feb 2000 08:40:41 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Dillon Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Patch to try (was Re: Wierd AMD panics caused by VMWare?) In-Reply-To: <200002250033.QAA43662@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 Thu, 24 Feb 2000, Matthew Dillon wrote: > Please try the following patch and tell me if the crashes still occur. > If this fixes the problem then I'm homing in on the bug. It seems to work here. > I am beginning to suspect that there is a case where a pmap can get > cleared without the tlb being flushed, causing origpte to be 0 when the > new pte is later created again at the same spot. When the new I think I found the real bug: invltlb() doesn't work on global pages. invlpg() is supposed to have no effect on global pages, and the point is that it apparently decides globalness based on cached copies of the PTE's. It has to invalidate all TLB entries, and it would be stupid for it to read all the corresponding PTE's just in case a PTE has been changed without doing an invlpg(). Removing the global bit from pgeflag seems to fix the bug (I just used ddb to clear pgeflag; this keeps PG_G out of future mappings). Some code in pmap.c seems to be vaguely aware of the need to use invlpg() instead of invltlb(). pmap_new_proc() always uses invlpg() for pages with the global bit set, but its test for the global bit is a no-op since the global bit can only be set if (cpu_class > CPUCLASS_386). Similarly in pmap_dispose_proc(). pmap_remove_pte() always uses invlpg() for pages with the global bit set and apparently depends on its caller to call at least invltlb() for other pages. More code in pmap.c is probably broken if this is the problem. Everything that uses invltlb() is suspect. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 14: 7:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (Postfix) with ESMTP id E0AB537BCF0 for ; Fri, 25 Feb 2000 14:07:14 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.3/8.9.1) with ESMTP id OAA33186 for ; Fri, 25 Feb 2000 14:07:13 -0800 (PST) Date: Fri, 25 Feb 2000 14:07:13 -0800 (PST) From: Chris Timmons To: freebsd-current@freebsd.org Subject: openssh: fatal: rsa_private_decrypt() failed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I find that if I start /usr/sbin/sshd manually everything works as expected. When I allow it to start via the rc scripts, I get upon connecting from my 1.2.27 ssh client sshd[190]: fatal: rsa_private_decrypt() failed There is a good chance that I have cruftlets from a prior sshd port installation but I am momentarily dazed and confused as to how that would affect the environment at rc.network time :| -c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 14:26:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id B2AFE37BE86 for ; Fri, 25 Feb 2000 14:26:35 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id QAA00368; Fri, 25 Feb 2000 16:24:42 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-76.max1.wa.cyberlynk.net(207.227.118.76) by peak.mountin.net via smap (V1.3) id sma000366; Fri Feb 25 16:24:18 2000 Message-Id: <3.0.3.32.20000225162240.009e3100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 25 Feb 2000 16:22:40 -0600 To: dan@freebsddiary.org, "O. Hartmann" From: "Jeffrey J. Mountin" Subject: Re: BUILDWORLD Problems Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200002252107.KAA09955@ducky.nz.freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:07 AM 2/26/00 +1300, Dan Langille wrote: >On 25 Feb 00, at 22:03, O. Hartmann wrote: > >> One of our two servers will not perform "buildworld"! Well, kernel stuff >> should be on the newest track, I cvsup-dated them both today. >> >> After a short while making dependencies it stops with the following error: > >[snip] Noticed a similar error and found some later commits got past that. >> I deleted /usr/src/crypto and ./secure tree and made an other cvsupdate, >> but with no success. Compiled a new kernel, installed it ... no success. >> Why? The other machine has the same stuff, I cvsupdated the same way and >> today, but it performs the make world task without any problems. I can not >> understand this behaviour ... Please help. > >libcrypto is being updated. You (and the rest of us) will just have to wait >until it's finished. AFAIK, the last commit was over 4 hours ago. I'd say try again. Should find out myself in the next half-hour or so. Jeff Mountin - jeff@mountin.net Systems/Network Administrator 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 Feb 25 14:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (Postfix) with ESMTP id D2F0337BE81 for ; Fri, 25 Feb 2000 14:28:39 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.3/8.9.1) with ESMTP id OAA33434 for ; Fri, 25 Feb 2000 14:28:39 -0800 (PST) Date: Fri, 25 Feb 2000 14:28:38 -0800 (PST) From: Chris Timmons To: freebsd-current@FreeBSD.ORG Subject: Re: openssh: fatal: rsa_private_decrypt() failed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks as though sshd is started prematurely (before ldconfig runs) in /etc/rc. I made the problem disappear on my system by starting sshd around the time inetd is started. -c On Fri, 25 Feb 2000, Chris Timmons wrote: > I find that if I start /usr/sbin/sshd manually everything works as > expected. When I allow it to start via the rc scripts, I get upon > connecting from my 1.2.27 ssh client > > sshd[190]: fatal: rsa_private_decrypt() failed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 14:32: 5 2000 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 669C837BD92 for ; Fri, 25 Feb 2000 14:31:48 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA07981 for freebsd-current@FreeBSD.ORG; Fri, 25 Feb 2000 23:31:42 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D597687AE; Fri, 25 Feb 2000 22:24:41 +0100 (CET) Date: Fri, 25 Feb 2000 22:24:41 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: openssh uses /etc (bad) Message-ID: <20000225222441.A97997@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list References: <20000225135140.A476@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Fri, Feb 25, 2000 at 10:45:34AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kris Kennaway: > crypto/ is the analogue of contrib/ for crypto code. You're not supposed > to build there..look under secure/. I was confused :) "buildworld" is now running on the two machines here... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 15: 2: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id 701AB37BDE7 for ; Fri, 25 Feb 2000 15:01:57 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id PAA12412; Fri, 25 Feb 2000 15:05:48 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id PAA81835; Fri, 25 Feb 2000 15:03:01 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: bwoods2@uswest.net Cc: Maxim Sobolev , freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: kdelibs port broken? References: From: Joel Ray Holveck Date: 25 Feb 2000 15:02:58 -0800 In-Reply-To: William Woods's message of "Tue, 22 Feb 2000 07:40:55 -0800 (PST)" Message-ID: <86k8jssx5o.fsf@detlev.piqnet.org> Lines: 17 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ON that subject, has anyone tried compiling the KDE port with the > new QT145 port? Not with the port. I was installing Qt to /usr/local/qt, and the port was putting the libs in a non-standard place where KDE couldn't find them. :-C I built Qt 1.45 by hand, installed it, set QTDIR, and everything compiled fine. I haven't done much testing on it yet (only ran kdehelp a couple of times), but nothing obvious. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 15: 6: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id 202DD37BEBC; Fri, 25 Feb 2000 15:05:56 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id PAA12419; Fri, 25 Feb 2000 15:09:44 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id PAA81841; Fri, 25 Feb 2000 15:06:56 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: Max Khon Cc: lioux@linf.unb.br, freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: XFree 3.3.6 authentication failed? References: From: Joel Ray Holveck Reply-To: freebsd-current@FreeBSD.ORG Date: 25 Feb 2000 15:06:55 -0800 In-Reply-To: Max Khon's message of "Wed, 23 Feb 2000 11:16:04 +0600 (NS)" Message-ID: <86hfewswz4.fsf@detlev.piqnet.org> Lines: 22 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Followups to -current] >> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and >> KDE 1.1.2. All from monday's ports tree. >> Well, I think I can't say I am running this system, for I am getting >> the following message whenever I try startx: > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > seems that you have built XFree with PAM support. > Just rebuild without PAM -- it's broken. Could you give me a few more details about the brokenness? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 15:10: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5F9E337BDDA for ; Fri, 25 Feb 2000 15:10:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA08673; Fri, 25 Feb 2000 15:10:00 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA42555; Fri, 25 Feb 2000 15:09:59 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 25 Feb 2000 15:09:59 -0800 (PST) Message-Id: <200002252309.PAA42555@vashon.polstra.com> To: freebsd@gndrsh.dnsmgr.net Subject: Re: Streamlining FreeBSD installations across many machines In-Reply-To: <200002251737.JAA70913@gndrsh.dnsmgr.net> References: <200002251737.JAA70913@gndrsh.dnsmgr.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200002251737.JAA70913@gndrsh.dnsmgr.net>, Rodney W. Grimes wrote: > A much faster way to do this is to just dd the first few megabytes > of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use > dump | restore to populate the disk. Do you run newfs on the receiving disk before the dump|restore? It seems like if you didn't then the free block bitmaps in the cylinder groups would contain garbage. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:13:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id D5E3537BE90 for ; Fri, 25 Feb 2000 16:13:52 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id TAA99269; Fri, 25 Feb 2000 19:13:10 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38B71A96.6A7CF46E@acm.org> Date: Fri, 25 Feb 2000 19:13:10 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: openssh uses /etc (bad) References: <20000225135140.A476@caerdonn.eurocontrol.fr> <20000225222441.A97997@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crypto/ is just a storage location for the for files. They are committed there just like files are in contrib. Buildworld never explicitly goes into either of these directories; the files stored there are referenced by makefiles in other parts of the tree. For example, look at the directory src/secure/usr.bin/ssh. The only file there is Makefile. Reading the Makefile, you will see that it needs several files. These are found through the .PATH derective which references crypto/openssh. Jim Bloom bloom@acm.org Ollivier Robert wrote: > > According to Kris Kennaway: > > crypto/ is the analogue of contrib/ for crypto code. You're not supposed > > to build there..look under secure/. > > I was confused :) > > "buildworld" is now running on the two machines here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:17:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 19E7237BEC4 for ; Fri, 25 Feb 2000 16:17:18 -0800 (PST) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id TAA04105 for freebsd-current@freebsd.org; Fri, 25 Feb 2000 19:17:07 -0500 (EST) (envelope-from ray) Date: Fri, 25 Feb 2000 19:17:07 -0500 From: Ray Kohler To: freebsd-current@freebsd.org Subject: Is openssl/openssh working right yet for others? Message-ID: <20000225191707.A4091@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that openssl and openssh were under heavy construction (yesterday?), but since the commits have stopped (for now), I was wondering is anyone else is able to build it. Going to /usr/src/secure and running make produces a problem due to a missing buildinf.h, which should be automatically generated (in crypto/openssl/crypto), and doing make -k produces loads of syntax errors and such. Since I hadn't seen any complaints about this here (not even from random people who don't know what's going on), I just wondered whether it was just my problem, or if it's not compilable yet. Will produce make (-k) output on request. -- Ray Kohler A closed mouth gathers no foot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:21:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6CEC537BEC4 for ; Fri, 25 Feb 2000 16:21:10 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id QAA21479; Fri, 25 Feb 2000 16:50:42 -0800 (PST) Date: Fri, 25 Feb 2000 16:50:42 -0800 From: Alfred Perlstein To: rjk191@psu.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is openssl/openssh working right yet for others? Message-ID: <20000225165041.M21720@fw.wintelcom.net> References: <20000225191707.A4091@rjk191.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000225191707.A4091@rjk191.rh.psu.edu>; from ray@rjk191.rh.psu.edu on Fri, Feb 25, 2000 at 07:17:07PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Ray Kohler [000225 16:47] wrote: > I know that openssl and openssh were under heavy construction > (yesterday?), but since the commits have stopped (for now), I was > wondering is anyone else is able to build it. Going to > /usr/src/secure and running make produces a problem due to a missing > buildinf.h, which should be automatically generated (in > crypto/openssl/crypto), and doing make -k produces loads of syntax > errors and such. Since I hadn't seen any complaints about this here > (not even from random people who don't know what's going on), I just > wondered whether it was just my problem, or if it's not compilable > yet. Will produce make (-k) output on request. It compiles ok during buildworld, but doing it seperately bombs out as discussed in previous mail. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:22:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (Postfix) with ESMTP id 6A91837BEFC for ; Fri, 25 Feb 2000 16:22:15 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.3/8.9.1) with ESMTP id QAA35349; Fri, 25 Feb 2000 16:22:12 -0800 (PST) Date: Fri, 25 Feb 2000 16:22:11 -0800 (PST) From: Chris Timmons To: rjk191@psu.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is openssl/openssh working right yet for others? In-Reply-To: <20000225191707.A4091@rjk191.rh.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a buildworld/installworld this afternoon and it works fine if I start /usr/bin/sshd from the command line as root. The way it starts from rc.network caused a problem for me which is described in another thread on this list. If you are still having trouble building, make sure you are getting an appropriate crypto distribution for your part of the world into your source tree. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:30:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from web110.yahoomail.com (web110.yahoomail.com [205.180.60.80]) by hub.freebsd.org (Postfix) with SMTP id 7CDF037BE90 for ; Fri, 25 Feb 2000 16:30:15 -0800 (PST) (envelope-from ixkatl@yahoo.com) Received: (qmail 8767 invoked by uid 60001); 26 Feb 2000 00:33:24 -0000 Message-ID: <20000226003324.8766.qmail@web110.yahoomail.com> Received: from [207.172.145.168] by web110.yahoomail.com; Fri, 25 Feb 2000 16:33:24 PST Date: Fri, 25 Feb 2000 16:33:24 -0800 (PST) From: Andrew Sherrod Subject: Re: Is openssl/openssh working right yet for others? To: rjk191@psu.edu, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had similar problems with mod_ssl (for apache). And once I completed that, getting it to install, and for apache to recognize it... Well, actually still working on it. Apache tells me to configure ssl, I do, ssl tells me to run "make certificate" on apache, and I do, apache crashes then tells me to configure ssl... and so on, ad infinitum. Any ideas? AGS --- Ray Kohler wrote: > I know that openssl and openssh were under heavy > construction > (yesterday?), but since the commits have stopped > (for now), I was > wondering is anyone else is able to build it. Going > to > /usr/src/secure and running make produces a problem > due to a missing > buildinf.h, which should be automatically generated > (in > crypto/openssl/crypto), and doing make -k produces > loads of syntax > errors and such. Since I hadn't seen any complaints > about this here > (not even from random people who don't know what's > going on), I just > wondered whether it was just my problem, or if it's > not compilable > yet. Will produce make (-k) output on request. > > -- > Ray Kohler > A closed mouth gathers no foot. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > ===== 'During my service in the United States Congress, I took the initiative in creating the Internet.' - Al Gore, March 9, 1999: On CNN's Late Edition __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.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 Feb 25 16:30:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 0284537BEE5 for ; Fri, 25 Feb 2000 16:30:52 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 5EE399B17; Fri, 25 Feb 2000 19:30:50 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 4E67ABA1D; Fri, 25 Feb 2000 19:30:50 -0500 (EST) Date: Fri, 25 Feb 2000 19:30:50 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: rjk191@psu.edu Cc: freebsd-current@freebsd.org Subject: Re: Is openssl/openssh working right yet for others? In-Reply-To: <20000225191707.A4091@rjk191.rh.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Feb 2000, Ray Kohler wrote: > I know that openssl and openssh were under heavy construction > (yesterday?), but since the commits have stopped (for now), I was > wondering is anyone else is able to build it. Going to > /usr/src/secure and running make produces a problem due to a missing > buildinf.h, which should be automatically generated (in *should* be automatically generated as a depends target, but isn't for some reason. Try 'make depend' in /usr/src/secure before building. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:42:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id A8F4937BEC4 for ; Fri, 25 Feb 2000 16:42:39 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id QAA12492; Fri, 25 Feb 2000 16:47:04 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id QAA82020; Fri, 25 Feb 2000 16:44:16 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: arnee Cc: freebsd-current@FreeBSD.ORG Subject: Re: natd, firewall, and RFC1918...? References: <38B50B92.2D399CA3@geocities.com> From: Joel Ray Holveck Date: 25 Feb 2000 16:44:15 -0800 In-Reply-To: arnee's message of "Thu, 24 Feb 2000 02:44:34 -0800" Message-ID: <86ema0ssgw.fsf@detlev.piqnet.org> Lines: 26 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. Is this right? Is natd behaving correctly when the packet comes back > in for unregistered ips? I would think that it would be aliased to like > this, "machine B's ip" --> machine C's ip".... like a proxy? But this > would still break the rule "... from any ...". I am going to assert that the behavior shown is correct. If you were to change the IP, then machine C would not recognize the packet as part of the same connection. If you want a proxy, use a proxy. If you want NAT, that's something different. I simply address the issue by blocking those packets on a rule before I send them through the NAT. This also has the advantage that after the NAT line, I know that anything internal is part of an established connection; that's invaluable for UDP, or was before we added dynamic rule support. Best, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:47:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 3996B37BEC4 for ; Fri, 25 Feb 2000 16:47:26 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id NAA11004; Sat, 26 Feb 2000 13:47:04 +1300 (NZDT) Message-Id: <200002260047.NAA11004@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: "Jeffrey J. Mountin" Date: Sat, 26 Feb 2000 13:47:00 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: BUILDWORLD Problems Reply-To: dan@freebsddiary.org Cc: freebsd-current@FreeBSD.ORG, "O. Hartmann" In-reply-to: <3.0.3.32.20000225162240.009e3100@207.227.119.2> References: <200002252107.KAA09955@ducky.nz.freebsd.org> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Feb 00, at 16:22, Jeffrey J. Mountin wrote: > AFAIK, the last commit was over 4 hours ago. I'd say try again. > > Should find out myself in the next half-hour or so. my build world just finished. no errors. -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:55:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id E987C37BDBD for ; Fri, 25 Feb 2000 16:55:08 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id TAA99321; Fri, 25 Feb 2000 19:49:47 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38B7232B.5B0FCB06@acm.org> Date: Fri, 25 Feb 2000 19:49:47 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Sherrod Cc: rjk191@psu.edu, freebsd-current@FreeBSD.ORG Subject: Re: Is openssl/openssh working right yet for others? References: <20000226003324.8766.qmail@web110.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Sherrod wrote: > > I had similar problems with mod_ssl (for apache). And > once I completed that, getting it to install, and for > apache to recognize it... > Well, actually still working on it. > Apache tells me to configure ssl, I do, ssl tells me > to run "make certificate" on apache, and I do, apache > crashes then tells me to configure ssl... > and so on, ad infinitum. > > Any ideas? There were some patches committed to apache13-modssl and apache13-php3 a little while ago. They fix the build problems and I got apache13-modssl up and running with them without any problems. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 16:57:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 6AE0137BDBD for ; Fri, 25 Feb 2000 16:57:48 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@21-181.008.popsite.net [209.69.77.181]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA65458; Fri, 25 Feb 2000 16:57:33 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 38F4E19E7; Fri, 25 Feb 2000 19:57:18 -0500 (EST) Date: Fri, 25 Feb 2000 19:57:18 -0500 From: Will Andrews To: Joel Ray Holveck Cc: bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: kdelibs port broken? Message-ID: <20000225195718.A17742@shadow.blackdawn.com> References: <86k8jssx5o.fsf@detlev.piqnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86k8jssx5o.fsf@detlev.piqnet.org>; from joelh@gnu.org on Fri, Feb 25, 2000 at 03:02:58PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 25, 2000 at 03:02:58PM -0800, Joel Ray Holveck wrote: > Not with the port. I was installing Qt to /usr/local/qt, and the port > was putting the libs in a non-standard place where KDE couldn't find > them. :-C I built Qt 1.45 by hand, installed it, set QTDIR, and > everything compiled fine. I haven't done much testing on it yet (only > ran kdehelp a couple of times), but nothing obvious. As far as I can tell, the KDE ports find Qt just fine. KDE insists on putting everything under the same dir, as does Qt. This violates our hierarchy (see hier(7) manpage), so we had to make some mods to the configurations for Qt and KDE ports. It's not that difficult. If you're gonna use a port, use ports for its dependencies too. You'd be stupid not to use the ports whenever you can. No one has ever provided me a convincing reason why this is not true. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 18:20:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from stargate.iss.com.tw (stargate.iss.com.tw [210.68.99.1]) by hub.freebsd.org (Postfix) with ESMTP id 305EC37BF4B for ; Fri, 25 Feb 2000 18:20:33 -0800 (PST) (envelope-from urania@iss.com.tw) Received: from stargate.iss.com.tw (root@localhost) by stargate.iss.com.tw with ESMTP id KAA21781 for ; Sat, 26 Feb 2000 10:27:03 +0800 (CST) Received: from iss.com.tw (mail.iss.com.tw [172.16.6.97]) by stargate.iss.com.tw with SMTP id KAA21777 for ; Sat, 26 Feb 2000 10:27:02 +0800 (CST) Received: (qmail 59576 invoked from network); 26 Feb 2000 02:14:03 -0000 Received: from unknown (HELO iss.com.tw) (172.16.6.98) by 172.16.6.97 with SMTP; 26 Feb 2000 02:14:03 -0000 Message-ID: <38B7395C.948AC8FA@iss.com.tw> Date: Sat, 26 Feb 2000 10:24:28 +0800 From: urania X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with IBM Netfinity 5000 Server References: <38B5F15E.82197160@iss.com.tw> <007301bf7fa7$564b3aa0$020a0a0a@megared.net.mx> Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alejandro Ramirez wrote: > > Hi, > > I have had problems with the 1st PCI slot in the IBM Netfinity 5000, it > reboots my system constantly, I dont know why, but now Im not using this > slot any more, and everything runs great. Could you tell me BIOS version and BIOS setting of your server ? Should I turn pnp,usb ... etc off? > > Greetings > Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 18:36:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 978A137BF4B; Fri, 25 Feb 2000 18:36:49 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id TAA25279; Fri, 25 Feb 2000 19:05:14 -0800 (PST) Date: Fri, 25 Feb 2000 19:05:14 -0800 From: Alfred Perlstein To: Chris Timmons Cc: freebsd-current@FreeBSD.ORG, peter@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: openssh: fatal: rsa_private_decrypt() failed Message-ID: <20000225190510.Q21720@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from skynyrd@opus.cts.cwu.edu on Fri, Feb 25, 2000 at 02:28:38PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 25 Feb 2000, Chris Timmons wrote: > > > I find that if I start /usr/sbin/sshd manually everything works as > > expected. When I allow it to start via the rc scripts, I get upon > > connecting from my 1.2.27 ssh client > > > > sshd[190]: fatal: rsa_private_decrypt() failed Chris answered himself with: * Chris Timmons [000225 15:02] wrote: > > It looks as though sshd is started prematurely (before ldconfig runs) in > /etc/rc. I made the problem disappear on my system by starting sshd > around the time inetd is started. I get the same problem and was going to just move sshd to "network_pass4" but then considered that maybe is _should_ work in network_pass3 and the solution is to fix something in the way sshd is compiled. Can anyone working on the recent sshd black magic linkage stuff please step up and explain? Or shall i move it to network_pass4? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 19:33:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 58BD037BD43 for ; Fri, 25 Feb 2000 19:33:35 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.af.speednet.com.au (andyf@backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id OAA20601; Sat, 26 Feb 2000 14:33:06 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Sat, 26 Feb 2000 14:33:05 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: "Jeffrey J. Mountin" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: adduser(8) removes comments from /etc/group - was: Re: minor nit with 4.0-RC2 In-Reply-To: <3.0.3.32.20000222011805.00844100@207.227.119.2> Message-ID: 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, 22 Feb 2000, Jeffrey J. Mountin wrote: > >I'm not sure I understand this - sysinstall doesn't install an > >/etc/group file so there's really no "sysinstall version" which is > >distinct from that installed as part of the bindist, at least to my > >knowledge. > > Nevermind. > > Manually extracted etc/group and it has the tag line. > > Must/might be losing it, but then I don't strip the tag lines when I edit > files. 8-/ > > Then again maybe adduser does this. Could start fresh again I suppose and > see what went wrong or if I lose my pilots license. > adduser(8) will remove any comments from /etc/group, including the $FreeBSD tag. Does sysinstall call adduser? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 20: 4:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 86F8637BE4B for ; Fri, 25 Feb 2000 20:04:15 -0800 (PST) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id NAA15494; Sat, 26 Feb 2000 13:04:14 +0900 (JST) Received: from unknown(133.253.31.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma015419; Sat, 26 Feb 00 13:03:40 +0900 Received: (from uucp@localhost) by lemond.gkn.kubota.co.jp (8.9.3+3.2W/3.7W00013112) with UUCP id NAA28112 for freebsd-current@freebsd.org; Sat, 26 Feb 2000 13:03:39 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.ttr.kubota.co.jp (8.9.3/3.7W-uucp) with ESMTP id NAA00346 for ; Sat, 26 Feb 2000 13:01:51 +0900 (JST) To: freebsd-current@freebsd.org Subject: buildworld failed in libpam due to crypto changes. X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000226130151R.haro@tk.kubota.co.jp> Date: Sat, 26 Feb 2000 13:01:51 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 44 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Buildworld failed due to crypto related changes in libpam. With following patch, buildworld and installworld went successful for me. They are for: src/lib/libpam/libpam/Makefile rev1.9 src/lib/libpam/modules/Makefile rev 1.4 diff -ru lib.org/libpam/libpam/Makefile lib/libpam/libpam/Makefile --- lib.org/libpam/libpam/Makefile Fri Feb 25 11:53:34 2000 +++ lib/libpam/libpam/Makefile Sat Feb 26 10:00:02 2000 @@ -71,7 +71,7 @@ STATIC_MODULES+= ${MODOBJDIR}/pam_permit/libpam_permit.a STATIC_MODULES+= ${MODOBJDIR}/pam_radius/libpam_radius.a STATIC_MODULES+= ${MODOBJDIR}/pam_skey/libpam_skey.a -.if !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_ssh/libpam_ssh.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_tacplus/libpam_tacplus.a diff -ru lib.org/libpam/modules/Makefile lib/libpam/modules/Makefile --- lib.org/libpam/modules/Makefile Fri Feb 25 11:53:34 2000 +++ lib/libpam/modules/Makefile Sat Feb 26 09:56:48 2000 @@ -35,7 +35,7 @@ SUBDIR+= pam_permit SUBDIR+= pam_radius SUBDIR+= pam_skey -.if !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto) && !defined(NO_OPENSSL) SUBDIR+= pam_ssh .endif SUBDIR+= pam_tacplus Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Development, Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 Email: haro@tk.kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 20:17:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from cummings.uol.com.br (cummings.uol.com.br [200.230.198.69]) by hub.freebsd.org (Postfix) with ESMTP id 7CA1D37BF2C for ; Fri, 25 Feb 2000 20:17:21 -0800 (PST) (envelope-from lioux-alias-ppp-freebsd-current=freebsd.org@uol.com.br) Received: from 200.197.112.65 (bsa-1-as01-7-a17.gd.uol.com.br [200.197.118.17]) by cummings.uol.com.br (8.9.1/8.9.1) with ESMTP id CAA29644 for ; Sat, 26 Feb 2000 02:17:12 -0200 (BRST) Received: (qmail 81114 invoked by uid 1001); 26 Feb 2000 05:13:59 -0000 From: lioux@uol.com.br Date: Sat, 26 Feb 2000 02:13:59 -0300 To: freebsd-current@freebsd.org Subject: -DNOCRYPT and -DNOSECURE? Message-ID: <20000226021359.A81102@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Guys, Could someone shed some light over a simple issue? What exactly does -DNOSECURE and -DNOCRYPT mean on a make world context? I mean, other than the obvious not touching the /usr/src/secure directory tree. I am asking this because on -current context, libcrypto needs to be built and -DNOSECURE/-DNOCRYPT prevents it. However, this was not an issue before. I just want to be able to do a make world but keep my beloved scrypt libraries in place. Summing up, I want DES and all the other packages, but keep md5 as my crypt library. Regards, Mario Ferreira ps: please CC: the message to me for I am not subscribing to this list for the time being. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 21:31:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4873137B94F for ; Fri, 25 Feb 2000 21:31:54 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA72574; Fri, 25 Feb 2000 21:31:46 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002260531.VAA72574@gndrsh.dnsmgr.net> Subject: Re: Streamlining FreeBSD installations across many machines In-Reply-To: <200002252309.PAA42555@vashon.polstra.com> from John Polstra at "Feb 25, 2000 03:09:59 pm" To: jdp@polstra.com (John Polstra) Date: Fri, 25 Feb 2000 21:31:45 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <200002251737.JAA70913@gndrsh.dnsmgr.net>, Rodney W. Grimes > wrote: > > > A much faster way to do this is to just dd the first few megabytes > > of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use > > dump | restore to populate the disk. > > Do you run newfs on the receiving disk before the dump|restore? It > seems like if you didn't then the free block bitmaps in the cylinder > groups would contain garbage. Ooopsss.. left a step out... yes.. we newfs the disk after the dd operations. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 21:35:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E4B3A37BC5C; Fri, 25 Feb 2000 21:35:39 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA65167; Fri, 25 Feb 2000 21:35:39 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Feb 2000 21:35:39 -0800 (PST) From: Kris Kennaway To: Munehiro Matsuda Cc: freebsd-current@freebsd.org Subject: Re: buildworld failed in libpam due to crypto changes. In-Reply-To: <20000226130151R.haro@tk.kubota.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Feb 2000, Munehiro Matsuda wrote: > Hi all, > > Buildworld failed due to crypto related changes in libpam. > With following patch, buildworld and installworld went successful for me. This patch looks correct to me, with one change. However I think the pam_ssh module needs to go under secure/ with the rest of the crypto code because of export restrictions (I know the regulations changed, but we dont yet have a legal ruling on it). > -.if !defined(NO_OPENSSL) > +.if exists(${.CURDIR}/../../../crypto) && !defined(NO_OPENSSL) .if exists(${.CURDIR}/../../../crypto) && !defined(NO_OPENSSL) && !defined(NO_OPENSSH) NO_OPENSSL should imply NO_OPENSSH since the latter depends on the former, but we also use NO_OPENSSH in other places to turn it off more finely. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 21:37: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8604337BED7; Fri, 25 Feb 2000 21:36:59 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA65291; Fri, 25 Feb 2000 21:36:59 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Feb 2000 21:36:59 -0800 (PST) From: Kris Kennaway To: Alfred Perlstein Cc: Chris Timmons , freebsd-current@FreeBSD.ORG, peter@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: openssh: fatal: rsa_private_decrypt() failed In-Reply-To: <20000225190510.Q21720@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Feb 2000, Alfred Perlstein wrote: > Can anyone working on the recent sshd black magic linkage stuff please > step up and explain? > > Or shall i move it to network_pass4? Please just let mark fix it..don't want the too many cooks problem :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 21:57:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 01E4B37BEF2 for ; Fri, 25 Feb 2000 21:57:11 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 16576 invoked from network); 26 Feb 2000 05:57:05 -0000 Received: from lcm208.cvzoom.net (HELO cvzoom.net) (208.230.69.208) by ns.cvzoom.net with SMTP; 26 Feb 2000 05:57:05 -0000 Message-ID: <38B76B1B.6BE859F@cvzoom.net> Date: Sat, 26 Feb 2000 00:56:43 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Will Andrews Cc: Joel Ray Holveck , bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, Daniel O'Connor Subject: Re: kdelibs port broken? References: <86k8jssx5o.fsf@detlev.piqnet.org> <20000225195718.A17742@shadow.blackdawn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews wrote: > As far as I can tell, the KDE ports find Qt just fine. KDE insists on > putting everything under the same dir, as does Qt. This violates our > hierarchy (see hier(7) manpage), so we had to make some mods to the > configurations for Qt and KDE ports. It's not that difficult. This is good if you build/install KDE by hand, instead of using the source. Having everything under /usr/local/kde makes it real easy to uninstall w/out package management; all you do is rm -rf /usr/local/kde. Same goes for Qt: rm -rf /usr/local/qt. BTW, why does the ports system insist on installing Gtk in /usr/X11R6/lib? Almost every other app that you compile by hand expects Gtk in /usr/local/lib. I hardly think we should be putting every X11 dependent software package in /usr/X11R6. The exceptions are the "old" traditional software, such as Motif, that programs expect to see in /usr/X11R6. "xv" is another one of these apps, and it's OK to put that in /usr/X11R6 as well. But, I don't think it's a good idea to be installing ALL X11 dependent stuff there, unless the port uses imake/xmkmf. I think the ports system should stick the "natural flow" of things -- imake stuff -->/usr/X11R6. GNU/configure generated stuff -->/usr/local. Why put everything in /usr/X11R6? Just go with the flow, man. Yes, I do agree with putting Lesstif in /usr/X11R6, because, IMHO, it's one of the exceptions. Motif dependent stuff _expects_ Motif libs there. Most non-ports software packages expect Gtk in /usr/local/lib. Likewise, non-ports compiled from source expect Qt in /usr/local/qt. So, I installed Gtk in /usr/local/lib, as that is its "natural" place. I built Gtk from ports initially, and Mozilla couldn't find it, because it was expected in /usr/local. Instead, it was in /usr/X11R6. Why? Every non-port expects Gtk in /usr/local. That's certainly where *I* expected it. It's in the natural scheme of things. I think there should be an option for ports, something like: COMPATIBLE_WITH_NON_PORTS. So, it would give us guys who use a mixture of ports/non-ports geater flexibility. Stuff would be allowed in their "natural" places, even if it means violating hier. Again, it would be an option for us who want Gtk, Qt, KDE, etc. in their "natural", non-ports conforming, hier-violating habitat > If you're gonna use a port, use ports for its dependencies too. You'd be > stupid not to use the ports whenever you can. No one has ever provided > me a convincing reason why this is not true. Excuse me, but I like to compile my own software by hand every once in a while, thank you very much. The ports system's way of doing things is causing conflicts with software NOT installed by ports. See my example above. Who cares if we violate hier? Sure, we should avoid it whenever possible, and it's great because it allows us to run a tight ship. I myself hated installing both Netscape libs and binaries in /usr/local/netscape. It's stupid to see something like /usr/local/netscape/netscape to run netscape. It's idiotic, to be sure. But, the Linux version of Netscape is broken in that java won't work unless you put netscape in that exact location. Yes, I tried setting MOZILLA_HOME and all kind of other stuff, and that wouldn't work either. The FreeBSD version didnt' have this bug, though. So, I think it's OK to "give" a little on violating hier. Nothing in this world is perfect. Some of us like to maximize compatibility with other "strange" stuff. As for violating hier, I think it's OK to use a little "fuzzines" factor in doing so (e.g. kde, qt, netscape, etc.). - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 22: 9:37 2000 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 0CF8037BF0B; Fri, 25 Feb 2000 22:09:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA13426; Fri, 25 Feb 2000 23:09:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA55697; Fri, 25 Feb 2000 23:08:58 -0700 (MST) Message-Id: <200002260608.XAA55697@harmony.village.org> To: Soren Schmidt Subject: Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader. Cc: msmith@FreeBSD.ORG (Mike Smith), yds@dppl.com (Yarema), FreeBSD-Current@FreeBSD.ORG (FreeBSD Current), sos@FreeBSD.ORG In-reply-to: Your message of "Thu, 24 Feb 2000 20:19:55 +0100." <200002241919.UAA24133@freebsd.dk> References: <200002241919.UAA24133@freebsd.dk> Date: Fri, 25 Feb 2000 23:08:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002241919.UAA24133@freebsd.dk> Soren Schmidt writes: : Busspace is a joke, I'm perfectly fine with calling those macros : in[bwl]/out[bwl] like they should be :) You wouldn't say that if you've had to deal with all the oddities of a mips box. : Busdma, hmm, well I dont see that helping here either.... Or that either.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 22:40: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id AF03837BF30 for ; Fri, 25 Feb 2000 22:39:56 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20663 invoked from network); 26 Feb 2000 06:39:52 -0000 Received: from lcm208.cvzoom.net (HELO cvzoom.net) (208.230.69.208) by ns.cvzoom.net with SMTP; 26 Feb 2000 06:39:52 -0000 Message-ID: <38B77523.4901DFDF@cvzoom.net> Date: Sat, 26 Feb 2000 01:39:31 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Will Andrews , Joel Ray Holveck , bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, Daniel O'Connor Subject: Re: kdelibs port broken? References: <86k8jssx5o.fsf@detlev.piqnet.org> <20000225195718.A17742@shadow.blackdawn.com> <38B76B1B.6BE859F@cvzoom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > So, I installed Gtk in /usr/local/lib, as that is its "natural" > place. I built Gtk from ports initially, and Mozilla couldn't find > it, because it was expected in /usr/local. Instead, it was in > /usr/X11R6. Why? Every non-port expects Gtk in /usr/local. That's > certainly where *I* expected it. It's in the natural scheme of > things. One comment: for me, it's no big deal; I just comment out the Gtk dependencies line in the port's makefile so it doesn't try to install an additional instance of Gtk into /usr/X11R6/lib. I think Gtk-dependent ports should try to compile a test Gtk-versionX.XX program to see if Gtk is installed someplace. The way it stands now, if we don't have Gtk registered as an installed port or package, it will download Gtk, compile, and install it. So, I believe gtk dependent ports should try compiling a test program, or it should try looking for the libs in $LOCALBASE before "writing off" gtk as "not installed" just because it's not registered as installed. Remember, we want to be flexibile with those guys who may want to compile/install gtk (or other software) on our own. (What if we want to build the cvs version? We may want to bypass ports on some things, for whatever reason. We shouldn't try to force people into conforming to the ports maintainer's idea of doing things.) Sorry to be beating you all down on Gtk -- I was just making an example of it for the sake of illustration. > So, I think it's OK to "give" a little on violating hier. Nothing in > this world is perfect. Some of us like to maximize compatibility with > other "strange" stuff. As for violating hier, I think it's OK to use > a little "fuzzines" factor in doing so (e.g. kde, qt, netscape, etc.). I just wanted to clarify this a little. I think the "fuzzines" factor should apply to /usr/local, but not necessarily /usr. My reasoning is that /usr/local isn't part of the main system - /bin /usr/bin, etc., so it's OK to have a little freedom in /usr/local. Hier should be more strictly followed in /usr. But, let's be a little more flexible with /usr/local, as it's really "none of the operating system's business" what we put in there. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 23: 0:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3EF6E37BF60; Fri, 25 Feb 2000 23:00:13 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id XAA02418; Fri, 25 Feb 2000 23:29:55 -0800 (PST) Date: Fri, 25 Feb 2000 23:29:55 -0800 From: Alfred Perlstein To: Kris Kennaway Cc: Chris Timmons , freebsd-current@FreeBSD.org, peter@FreeBSD.org, markm@FreeBSD.org Subject: Re: openssh: fatal: rsa_private_decrypt() failed Message-ID: <20000225232955.V21720@fw.wintelcom.net> References: <20000225190510.Q21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@FreeBSD.org on Fri, Feb 25, 2000 at 09:36:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kris Kennaway [000225 22:06] wrote: > On Fri, 25 Feb 2000, Alfred Perlstein wrote: > > > Can anyone working on the recent sshd black magic linkage stuff please > > step up and explain? > > > > Or shall i move it to network_pass4? > > Please just let mark fix it..don't want the too many cooks problem :-) Ok, I just wanted to make sure people realized it was happening to more than one person. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 23:31:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CBC0937BF22; Fri, 25 Feb 2000 23:31:56 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA71488; Fri, 25 Feb 2000 23:31:56 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Feb 2000 23:31:56 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: markm@freebsd.org Subject: OpenSSH /etc patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this patch fix the problems people are seeing? It also generates the hostkey if it doesnt exist. Oops, the NO_DESCRYPT line in the /etc/defaults/make.conf patch shouldn't be committed yet..I'm still testing that one. Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.211 diff -u -r1.211 rc --- rc 2000/02/23 18:05:57 1.211 +++ rc 2000/02/26 07:18:54 @@ -301,6 +301,15 @@ ;; esac +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it +# so we do it unconditionally on sshd_enable. +# +if [ ! -f /etc/ssh/ssh_host_key -a -x /usr/bin/ssh-keygen ]; then + echo 'generating an SSH host key:' + /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key + echo ' done.' +fi + if [ -n "${network_pass2_done}" ]; then network_pass3 fi @@ -391,6 +400,15 @@ [Yy][Ee][Ss]) if [ -r /etc/mail/sendmail.cf ]; then echo -n ' sendmail'; /usr/sbin/sendmail ${sendmail_flags} + fi + ;; +esac + +case ${sshd_enable} in +[Yy][Ee][Ss]) + if [ -x ${sshd_program:-/usr/sbin/sshd} ]; then + echo -n ' sshd'; + ${sshd_program:-/usr/sbin/sshd} ${sshd_flags} fi ;; esac Index: rc.network =================================================================== RCS file: /home/ncvs/src/etc/rc.network,v retrieving revision 1.71 diff -u -r1.71 rc.network --- rc.network 2000/02/24 23:12:04 1.71 +++ rc.network 2000/02/26 05:49:08 @@ -603,13 +603,6 @@ ;; esac - case ${sshd_enable} in - [Yy][Ee][Ss]) - echo -n ' sshd'; - ${sshd_program:-/usr/sbin/sshd} ${sshd_flags} - ;; - esac - echo '.' network_pass3_done=YES } Index: defaults/make.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/make.conf,v retrieving revision 1.92 diff -u -r1.92 make.conf --- defaults/make.conf 2000/02/24 23:08:17 1.92 +++ defaults/make.conf 2000/02/26 05:56:04 @@ -27,10 +27,11 @@ #PERL_THREADED= true # # To avoid building various parts of the base system: -#NO_SENDMAIL= true #NO_CVS= true +#NO_DESCRYPT= true # Don't build a DES libcrypt #NO_OPENSSH= true -#NO_OPENSSL= true +#NO_OPENSSL= true # Implies NO_OPENSSH +#NO_SENDMAIL= true # # To tell the base system that you are using RSAREF (from ports). # (This needs revisiting) - it is very likely that this is too Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.51 diff -u -r1.51 rc.conf --- defaults/rc.conf 2000/02/24 23:08:19 1.51 +++ defaults/rc.conf 2000/02/26 05:40:20 @@ -124,9 +124,9 @@ pppoed_provider="*" # Provider and ppp(8) config file entry. pppoed_flags="-P /var/run/pppoed.pid" # Flags to pppoed (if enabled). pppoed_interface="fxp0" # The interface that pppoed runs on. -sshd_program="/usr/sbin/sshd" # path to sshd, if you want a different one. -sshd_enable="NO" # Enable sshd -sshd_flags="" # Additional flags for sshd. +sshd_enable="NO" # Enable sshd, if installed. +sshd_program="/usr/sbin/sshd" # Path to sshd, if you want a different one. +sshd_flags="" # Flags to sshd (if enabled). ### Network Time Services options: ### timed_enable="NO" # Run the time daemon (or NO). Index: mtree/BSD.root.dist =================================================================== RCS file: /home/ncvs/src/etc/mtree/BSD.root.dist,v retrieving revision 1.45 diff -u -r1.45 BSD.root.dist --- mtree/BSD.root.dist 2000/02/25 14:18:48 1.45 +++ mtree/BSD.root.dist 2000/02/26 07:19:44 @@ -28,8 +28,8 @@ monthly .. .. - ssh - .. + ssh + .. ssl .. gnats To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 25 23:35:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (nld-dial-196-7-200-142.mweb.co.za [196.7.200.142]) by hub.freebsd.org (Postfix) with ESMTP id CD31D37BF79; Fri, 25 Feb 2000 23:35:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA19578; Sat, 26 Feb 2000 09:36:07 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002260736.JAA19578@grimreaper.grondar.za> To: Kris Kennaway Cc: Alfred Perlstein , Chris Timmons , freebsd-current@FreeBSD.org, peter@FreeBSD.org, markm@FreeBSD.org Subject: Re: openssh: fatal: rsa_private_decrypt() failed References: In-Reply-To: ; from Kris Kennaway "Fri, 25 Feb 2000 21:36:59 PST." Date: Sat, 26 Feb 2000 09:36:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 25 Feb 2000, Alfred Perlstein wrote: > > > Can anyone working on the recent sshd black magic linkage stuff please > > step up and explain? > > > > Or shall i move it to network_pass4? > > Please just let mark fix it..don't want the too many cooks problem :-) In a couple of hours, I'll do this. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 0:18:48 2000 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 E707A37BFA9; Sat, 26 Feb 2000 00:18:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA34739; Sat, 26 Feb 2000 00:18:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch In-reply-to: Your message of "Fri, 25 Feb 2000 23:31:56 PST." Date: Sat, 26 Feb 2000 00:18:38 -0800 Message-ID: <34736.951553118@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it > +# so we do it unconditionally on sshd_enable. Are you sure ssh requires a host key? I could have sworn this was entirely related to sshd and could thus be lumped into the same "if sshd_enable=YES" clause. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 1:39: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id C51E737BFD0; Sat, 26 Feb 2000 01:38:54 -0800 (PST) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.9.3/8.9.3) id KAA02738; Sat, 26 Feb 2000 10:39:02 +0100 (CET) (envelope-from bg) To: Kris Kennaway , jkh@zippy.cdrom.com Cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch References: From: Bjoern Groenvall Date: 26 Feb 2000 10:39:01 +0100 In-Reply-To: Kris Kennaway's message of Fri, 25 Feb 2000 23:31:56 -0800 (PST) Message-ID: Lines: 42 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > Does this patch fix the problems people are seeing? It also generates the > hostkey if it doesnt exist. > > Oops, the NO_DESCRYPT line in the /etc/defaults/make.conf patch shouldn't > be committed yet..I'm still testing that one. > +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it > +# so we do it unconditionally on sshd_enable. > +# > +if [ ! -f /etc/ssh/ssh_host_key -a -x /usr/bin/ssh-keygen ]; then > + echo 'generating an SSH host key:' > + /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key > + echo ' done.' > +fi > + Be careful to only run ssh-keygen if you are confident that the kernel random number-generator has acquired enough entropy, otherwise you'll leave the door open for guessing secret keys! Jordan K. Hubbard writes: > > +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it > > +# so we do it unconditionally on sshd_enable. > > Are you sure ssh requires a host key? I could have sworn this was > entirely related to sshd and could thus be lumped into the same > "if sshd_enable=YES" clause. Jordan is right about this, sshd requires the private key but ssh can't even read the key from the file. Cheers, Björn _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 1:39: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (nld-dial-196-7-200-248.mweb.co.za [196.7.200.248]) by hub.freebsd.org (Postfix) with ESMTP id EEF7037BBD1; Sat, 26 Feb 2000 01:38:32 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id KAA19942; Sat, 26 Feb 2000 10:21:07 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002260821.KAA19942@grimreaper.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.org, markm@FreeBSD.org Subject: Re: OpenSSH /etc patch References: In-Reply-To: ; from Kris Kennaway "Fri, 25 Feb 2000 23:31:56 PST." Date: Sat, 26 Feb 2000 10:21:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does this patch fix the problems people are seeing? It also generates the > hostkey if it doesnt exist. It works, but I'd prefer to see the launch of sshd in rc.network somewhere, not in rc. -- 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 Feb 26 1:50: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id 96DCB37BF46; Sat, 26 Feb 2000 01:50:04 -0800 (PST) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.9.3/8.9.3) id KAA02759; Sat, 26 Feb 2000 10:50:06 +0100 (CET) (envelope-from bg) To: Mark Murray Cc: Kris Kennaway , current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch References: <200002260821.KAA19942@grimreaper.grondar.za> From: Bjoern Groenvall Date: 26 Feb 2000 10:50:06 +0100 In-Reply-To: Mark Murray's message of Sat, 26 Feb 2000 10:21:07 +0200 Message-ID: Lines: 21 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray writes: > > Does this patch fix the problems people are seeing? It also generates the > > hostkey if it doesnt exist. > > It works, but I'd prefer to see the launch of sshd in rc.network somewhere, > not in rc. Since the start of sshd enables logins almost all stuff from the rc files should have been run (mounting homedirs, raising securelevels etc.) before sshd is started. /Björn -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 2:44:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0731037BB9A; Sat, 26 Feb 2000 02:44:10 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA79789; Sat, 26 Feb 2000 02:44:09 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 02:44:09 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch In-Reply-To: <34736.951553118@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 yOn Sat, 26 Feb 2000, Jordan K. Hubbard wrote: > > +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it > > +# so we do it unconditionally on sshd_enable. > > Are you sure ssh requires a host key? I could have sworn this was > entirely related to sshd and could thus be lumped into the same > "if sshd_enable=YES" clause. The code does not lie :-) From ssh.c: /* * If we successfully made the connection, load the host private key * in case we will need it later for combined rsa-rhosts * authentication. This must be done before releasing extra * privileges, because the file is only readable by root. */ if (ok) { host_private_key = RSA_new(); if (load_private_key(HOST_KEY_FILE, "", host_private_key, NULL)) host_private_key_loaded = 1; } Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 2:52:57 2000 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 85B3337BC1B for ; Sat, 26 Feb 2000 02:52:53 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 68553 invoked by uid 1001); 26 Feb 2000 10:52:50 +0000 (GMT) To: kris@FreeBSD.org Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 26 Feb 2000 02:44:09 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 26 Feb 2000 11:52:50 +0100 Message-ID: <68551.951562370@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Are you sure ssh requires a host key? I could have sworn this was > > entirely related to sshd and could thus be lumped into the same > > "if sshd_enable=YES" clause. > > The code does not lie :-) > > >From ssh.c: > > /* > * If we successfully made the connection, load the host private key > * in case we will need it later for combined rsa-rhosts > * authentication. This must be done before releasing extra > * privileges, because the file is only readable by root. But this means that ssh must be setuid root. Some of us insist on *not* using rsa-rhosts authentication, and install ssh without any privileges. Looks to me like we need a couple of alternatives 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 Sat Feb 26 2:58: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E518837BF1C; Sat, 26 Feb 2000 02:58:02 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA80333; Sat, 26 Feb 2000 02:58:02 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 02:58:02 -0800 (PST) From: Kris Kennaway To: sthaug@nethelp.no Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch In-Reply-To: <68551.951562370@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 Sat, 26 Feb 2000 sthaug@nethelp.no wrote: > But this means that ssh must be setuid root. Some of us insist on *not* > using rsa-rhosts authentication, and install ssh without any privileges. > > Looks to me like we need a couple of alternatives here. If you want to tinker with the file permissions, can't you deal with the fact that the startup scripts will create a host key for you the first time you boot with it installed? What do you want alternatives to? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 3: 4: 6 2000 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 E5B0B37BED5 for ; Sat, 26 Feb 2000 03:04:03 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 68688 invoked by uid 1001); 26 Feb 2000 11:04:02 +0000 (GMT) To: kris@FreeBSD.org Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 26 Feb 2000 02:58:02 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 26 Feb 2000 12:04:02 +0100 Message-ID: <68686.951563042@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want to tinker with the file permissions, can't you deal with the > fact that the startup scripts will create a host key for you the first > time you boot with it installed? As long as there is an easy way of running ssh without any special privs, I'm happy. 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 Sat Feb 26 5:17:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id 4E67337BBCF; Sat, 26 Feb 2000 05:17:44 -0800 (PST) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.9.3/8.9.3) id OAA03973; Sat, 26 Feb 2000 14:18:00 +0100 (CET) (envelope-from bg) To: Kris Kennaway Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch References: From: Bjoern Groenvall Date: 26 Feb 2000 14:17:59 +0100 In-Reply-To: Kris Kennaway's message of Sat, 26 Feb 2000 02:44:09 -0800 (PST) Message-ID: Lines: 44 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > yOn Sat, 26 Feb 2000, Jordan K. Hubbard wrote: > > > > +# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it > > > +# so we do it unconditionally on sshd_enable. > > > > Are you sure ssh requires a host key? I could have sworn this was > > entirely related to sshd and could thus be lumped into the same > > "if sshd_enable=YES" clause. > > The code does not lie :-) > > >From ssh.c: > > /* > * If we successfully made the connection, load the host private > key > * in case we will need it later for combined rsa-rhosts > * authentication. This must be done before releasing extra > * privileges, because the file is only readable by root. > */ > if (ok) { > host_private_key = RSA_new(); > if (load_private_key(HOST_KEY_FILE, "", host_private_key, > NULL)) > host_private_key_loaded = 1; > } Right, the code does not lie (if ssh is setuid root). But, if the host key has not yet been created, then no host can have the public key and thus rsa-rhosts authentication won't work anyways. It is not required to run ssh-keygen to make ssh work, Sshd still requires the host key to operate. /Björn -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 7:10: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id D485237BCC2 for ; Sat, 26 Feb 2000 07:10:03 -0800 (PST) (envelope-from ron@zappa.demon.nl) Received: from sonic (moon.demon.nl [192.168.1.3]) by zappa.demon.nl (Postfix) with ESMTP id BF651223C; Sat, 26 Feb 2000 16:14:14 +0100 (CET) From: "Ron Klinkien" To: wpaul@ee.columbia.edu Date: Sun, 27 Feb 2000 16:13:38 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: if_kue.c addition please commit... Cc: current@freebsd.org X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000226151414.BF651223C@zappa.demon.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bill Paul, After all the troubles I had trying to get several PCCards to workin my Compaq Laptop (who all work 100% with Linux). I went out and looked for the cheapest USB->Ethernet adapter I get my hands on. And what I hoped for, I works perfectly with 4.0-CURRENT! No messing with irqs/pccard.conf/broken connectors etc It's an Skymaster DHU-0404 it cost's $46 in the Netherlands It also uses an Kawasaki LSI KL5KUSB101B chip. After adding an entry to if_kue.c like this: ------------------ /* * Various supported device vendors/products. */ static struct kue_type kue_devs[] = { { USB_VENDOR_KLSI, USB_PRODUCT_AOX_USB101 }, .... ------------------ It identifies itself as: kue0: SKYMASTER Inc. USB-Ethernet, rev 1.00/2.02, addr 2 kue0: Ethernet address: 00:c0:26:ae:02:71 ifconfig -a kue0: flags=8843 mtu 1500 inet 192.168.1.4 netmask 0xffffffe0 broadcast 192.168.1.31 ether 00:c0:26:ae:02:71 I tested it with several cvsups and large ftp sessions and works without any trouble. Could you please commit it to 4.0? Regards, Ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 8: 9:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 19D0337BD0E for ; Sat, 26 Feb 2000 08:09:09 -0800 (PST) (envelope-from kibbet@kibby.au.knfpub.com) Received: (from kibbet@localhost) by kibby.au.knfpub.com (8.9.3/8.9.3) id CAA09772 for freebsd-current@freebsd.org; Sun, 27 Feb 2000 02:39:04 +1030 (CST) (envelope-from kibbet) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_" Date: Sun, 27 Feb 2000 02:39:03 +1030 (CST) From: kibbet To: freebsd-current@freebsd.org Subject: bad blocks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_ Content-Type: text/plain; charset=us-ascii Hi all, Quick question, how does the new ata driver handle bad blocks? I've been tracking -current since around Nov 99 but haven't seen this come up. I have a drive which I know has some bad blocks. I install 3.2 (just cause its laying around), use bad block scan in sysinstall everything's fine (it finds the bad blocks), I can cvs, build and install -current on it. Build and install a kernel (with the new ata driver), reboot, still no probs, until I find a bad block :) At this point it dosen't ignore the block but tries to access it, it does give up after a few attempts. So, perhaps its not happy with the 3.2 bad block info, so I try; bad144 -v -s ad0 (the output is attached). It looks like it finds the bad blocks with no problems, but, when I reboot, it can't mount root; [device probe snip] Mounting root from ufs:/dev/ad0d1a ad0: bad sector table not supported ad0s1: bad sector table not supported Root mount failed: 22 Mounting root from ufs:/dev/wd0s1a wd0: bad sector table not supported wd0s1: bad sector table not supported Root mount failed: 22 Mounting root from ufs:/dev/wd0a wd0: bad sector table not supported wd0s1: bad sector table not supported Root mount failed: 22 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input >>> Here's the trace, if its useful; (kgdb) bt #0 Debugger (msg=0xc025fea9 "manual escape to debugger") at ../../i386/i386/db_interface.c:319 #1 0xc02257e6 in scgetc (sc=0xc02bed80, flags=1) at ../../dev/syscons/syscons.c:3134 #2 0xc02236b3 in sccngetch (flags=0) at ../../dev/syscons/syscons.c:1544 #3 0xc022354a in sccngetc (dev=0xc02a6340) at ../../dev/syscons/syscons.c:1470 #4 0xc014d07d in cngetc () at ../../kern/tty_cons.c:406 #5 0xc015cd55 in gets (cp=0xc0324f04 "s") at ../../kern/vfs_conf.c:280 #6 0xc015ccb2 in vfs_mountroot_ask () at ../../kern/vfs_conf.c:254 #7 0xc015ca47 in vfs_mountroot (junk=0x0) at ../../kern/vfs_conf.c:154 #8 0xc0127ec8 in mi_startup (framep=0xc0324fb4) at ../../kern/init_main.c:217 I can't think of what else might be useful (its 2:30am here ATM) :) It was cvs'd and built a few days ago, but I haven't noticed anything commited that would affect this since then. Anyways, coherency isn't my strong point at 2:30am :) If anyone would like further details (or to flame me), I'll be back in the morning :) Cheers, Kent Ibbetson kib@knfpub.com --_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_ Content-Disposition: attachment; filename="bad144.log" Content-Transfer-Encoding: base64 Content-Description: bad144.log Content-Type: application/octet-stream; name=bad144.log; SizeOnDisk=2651 ZnJlZWJpZTQjIGJhZDE0NCAtcyAtdiBhZDAKY3lsOiAzMzA3LCB0cmFja3M6IDE2LCBzZWNzOiA2 Mywgc2VjL2N5bDogMTAwOCwgc3RhcnQ6IDAsIGVuZDogMzMzNDIxMgpiYWQxNDQ6IGNvdWxkbid0 IHNldCBkaXNrIGluICJiYWRzY2FuIiBtb2RlOiBPcGVyYXRpb24gbm90IHN1cHBvcnRlZCBieSBk ZXZpY2UKICAyODIyNCBvZiAzMzM0MjEyIGJsb2NrcyAoICAwJSleQwpmcmVlYmllNCMgYmFkMTQ0 IC1zIC12IGFkMApjeWw6IDMzMDcsIHRyYWNrczogMTYsIHNlY3M6IDYzLCBzZWMvY3lsOiAxMDA4 LCBzdGFydDogMCwgZW5kOiAzMzM0MjEyCmJhZDE0NDogY291bGRuJ3Qgc2V0IGRpc2sgaW4gImJh ZHNjYW4iIG1vZGU6IE9wZXJhdGlvbiBub3Qgc3VwcG9ydGVkIGJ5IGRldmljZQpCbG9jazogMTIw MjEzMSB3aWxsIGJlIG1hcmtlZCBCQUQuCkJsb2NrOiAxMjAyNDA1IHdpbGwgYmUgbWFya2VkIEJB RC4KQmxvY2s6IDEyMDI3NDMgd2lsbCBiZSBtYXJrZWQgQkFELgpCbG9jazogMTIwMzAxNiB3aWxs IGJlIG1hcmtlZCBCQUQuCkJsb2NrOiAxMjAzNjMzIHdpbGwgYmUgbWFya2VkIEJBRC4KQmxvY2s6 IDEyMDQyNDQgd2lsbCBiZSBtYXJrZWQgQkFELgpCbG9jazogMTIwNDg2MSB3aWxsIGJlIG1hcmtl ZCBCQUQuCkJsb2NrOiAxMjA1NDcyIHdpbGwgYmUgbWFya2VkIEJBRC4KQmxvY2s6IDEyMDYwODkg d2lsbCBiZSBtYXJrZWQgQkFELgpCbG9jazogMTIwNjcwMCB3aWxsIGJlIG1hcmtlZCBCQUQuCkJs b2NrOiAxMjA3MzE3IHdpbGwgYmUgbWFya2VkIEJBRC4KQmxvY2s6IDEyMDc5Mjggd2lsbCBiZSBt YXJrZWQgQkFELgpCbG9jazogMTIwODU0NSB3aWxsIGJlIG1hcmtlZCBCQUQuCkJsb2NrOiAxMjA5 MTU2IHdpbGwgYmUgbWFya2VkIEJBRC4KQmxvY2s6IDEyMDk3NzMgd2lsbCBiZSBtYXJrZWQgQkFE LgpCbG9jazogMTIxMDM4NCB3aWxsIGJlIG1hcmtlZCBCQUQuCkJsb2NrOiAxMjExMTU3IHdpbGwg YmUgbWFya2VkIEJBRC4KQmxvY2s6IDEyMTE3Njggd2lsbCBiZSBtYXJrZWQgQkFELgpCbG9jazog MTIxMjM4NSB3aWxsIGJlIG1hcmtlZCBCQUQuCkJsb2NrOiAxMjEyOTk2IHdpbGwgYmUgbWFya2Vk IEJBRC4KQmxvY2s6IDEyMTM2MTMgd2lsbCBiZSBtYXJrZWQgQkFELgozMzMzNDU2IG9mIDMzMzQy MTIgYmxvY2tzICggOTklKQpiYWQxNDQ6IGNvdWxkbid0IHJlc2V0IGRpc2sgZnJvbSAiYmFkc2Nh biIgbW9kZTogT3BlcmF0aW9uIG5vdCBzdXBwb3J0ZWQgYnkgZGV2aWNlCkhhZCAwIGJhZCBzZWN0 b3JzLCBhZGRpbmcgMjEKemVyb2luZyAzMzM0MzE3Cnplcm9pbmcgMzMzNDMxOAp6ZXJvaW5nIDMz MzQzMTkKemVyb2luZyAzMzM0MzIwCnplcm9pbmcgMzMzNDMyMQp6ZXJvaW5nIDMzMzQzMjIKemVy b2luZyAzMzM0MzIzCnplcm9pbmcgMzMzNDMyNAp6ZXJvaW5nIDMzMzQzMjUKemVyb2luZyAzMzM0 MzI2Cnplcm9pbmcgMzMzNDMyNwp6ZXJvaW5nIDMzMzQzMjgKemVyb2luZyAzMzM0MzI5Cnplcm9p bmcgMzMzNDMzMAp6ZXJvaW5nIDMzMzQzMzEKemVyb2luZyAzMzM0MzMyCnplcm9pbmcgMzMzNDMz Mwp6ZXJvaW5nIDMzMzQzMzQKemVyb2luZyAzMzM0MzM1Cnplcm9pbmcgMzMzNDMzNgp6ZXJvaW5n IDMzMzQzMzcKd3JpdGUgYmFkc2VjdCBmaWxlIGF0IDMzMzQzMzgKd3JpdGUgYmFkc2VjdCBmaWxl IGF0IDMzMzQzNDAKd3JpdGUgYmFkc2VjdCBmaWxlIGF0IDMzMzQzNDIKd3JpdGUgYmFkc2VjdCBm aWxlIGF0IDMzMzQzNDQKd3JpdGUgYmFkc2VjdCBmaWxlIGF0IDMzMzQzNDYKYmFkMTQ0OiBjYW4n dCBzeW5jIGJhZC1zZWN0b3IgZmlsZTsgcmVib290IGZvciBjaGFuZ2VzIHRvIHRha2UgZWZmZWN0 CmZyZWViaWU0IyBiYWQxNDQgYWQwCmJhZCBibG9jayBpbmZvcm1hdGlvbiBhdCBzZWN0b3IgMzMz NDMzOCBpbiAvZGV2L3JhZDBjOgpjYXJ0cmlkZ2Ugc2VyaWFsIG51bWJlcjogMCgxMCkKc249MTIw MjEzMSwgY249MTE5MiwgdG49OSwgc249MjgKc249MTIwMjQwNSwgY249MTE5MiwgdG49MTMsIHNu PTUwCnNuPTEyMDI3NDMsIGNuPTExOTMsIHRuPTMsIHNuPTEwCnNuPTEyMDMwMTYsIGNuPTExOTMs IHRuPTcsIHNuPTMxCnNuPTEyMDM2MzMsIGNuPTExOTQsIHRuPTEsIHNuPTE4CnNuPTEyMDQyNDQs IGNuPTExOTQsIHRuPTEwLCBzbj02Mgpzbj0xMjA0ODYxLCBjbj0xMTk1LCB0bj00LCBzbj00OQpz bj0xMjA1NDcyLCBjbj0xMTk1LCB0bj0xNCwgc249MzAKc249MTIwNjA4OSwgY249MTE5NiwgdG49 OCwgc249MTcKc249MTIwNjcwMCwgY249MTE5NywgdG49MSwgc249NjEKc249MTIwNzMxNywgY249 MTE5NywgdG49MTEsIHNuPTQ4CnNuPTEyMDc5MjgsIGNuPTExOTgsIHRuPTUsIHNuPTI5CnNuPTEy MDg1NDUsIGNuPTExOTgsIHRuPTE1LCBzbj0xNgpzbj0xMjA5MTU2LCBjbj0xMTk5LCB0bj04LCBz bj02MApzbj0xMjA5NzczLCBjbj0xMjAwLCB0bj0yLCBzbj00Nwpzbj0xMjEwMzg0LCBjbj0xMjAw LCB0bj0xMiwgc249MjgKc249MTIxMTE1NywgY249MTIwMSwgdG49OCwgc249NDUKc249MTIxMTc2 OCwgY249MTIwMiwgdG49Miwgc249MjYKc249MTIxMjM4NSwgY249MTIwMiwgdG49MTIsIHNuPTEz CnNuPTEyMTI5OTYsIGNuPTEyMDMsIHRuPTUsIHNuPTU3CnNuPTEyMTM2MTMsIGNuPTEyMDMsIHRu PTE1LCBzbj00NApmcmVlYmllNCMgcmVib290Cgo= --_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 9: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (nld-dial-196-7-201-67.mweb.co.za [196.7.201.67]) by hub.freebsd.org (Postfix) with ESMTP id 72A3D37BD81; Sat, 26 Feb 2000 09:05:35 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id TAA01113; Sat, 26 Feb 2000 19:07:31 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002261707.TAA01113@grimreaper.grondar.za> To: Bjoern Groenvall Cc: Mark Murray , Kris Kennaway , current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch References: In-Reply-To: ; from Bjoern Groenvall "26 Feb 2000 10:50:06 +0100." Date: Sat, 26 Feb 2000 19:07:31 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since the start of sshd enables logins almost all stuff from the rc > files should have been run (mounting homedirs, raising securelevels > etc.) before sshd is started. OK- fair enough! 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 Feb 26 9:23:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1CE1537BE5B for ; Sat, 26 Feb 2000 09:23:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA12342; Sat, 26 Feb 2000 18:22:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: kibbet Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad blocks In-reply-to: Your message of "Sun, 27 Feb 2000 02:39:03 +1030." Date: Sat, 26 Feb 2000 18:22:45 +0100 Message-ID: <12340.951585765@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , kibbet writes: >This message is in MIME format >--_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_ >Content-Type: text/plain; charset=us-ascii > >Hi all, > >Quick question, how does the new ata driver handle bad blocks? >I've been tracking -current since around Nov 99 but haven't >seen this come up. It doesn't. The drives have to handle bad blocks now. If you have a drive where bad144 remapping is enabled, try to find out if any sectors have been remapped, if not you can simply turn off bad144. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 9:45:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id CD4DA37B69F; Sat, 26 Feb 2000 09:45:12 -0800 (PST) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.9.3/8.9.3) id SAA04188; Sat, 26 Feb 2000 18:45:26 +0100 (CET) (envelope-from bg) To: Kris Kennaway Cc: Ollivier Robert , "FreeBSD Current Users' list" , markm@FreeBSD.ORG Subject: Re: openssh uses /etc (bad) References: From: Bjoern Groenvall Date: 26 Feb 2000 18:45:24 +0100 In-Reply-To: Kris Kennaway's message of Fri, 25 Feb 2000 10:45:34 -0800 (PST) Message-ID: Lines: 22 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Fri, 25 Feb 2000, Ollivier Robert wrote: > > > I just saw that openssh (thanks Mark!) is using /etc/ for its configuration > > file. As the author of the "--with-etcdir" option of SSH (back in '96) and > > for the sake of consistency, I'd like to create a /etc/ssh directory and > > move everything there. > > In case you hadn't already found out, Peter fixed this. While you are moving things around you might as well move /usr/sbin/sshd to /usr/libexec/sshd where it should have resided in the first place. -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 9:54:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 308E437B5CD for ; Sat, 26 Feb 2000 09:54:13 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id SAA23271; Sat, 26 Feb 2000 18:50:20 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA36640; Sat, 26 Feb 2000 17:37:39 +0100 (CET) (envelope-from wilko) Date: Sat, 26 Feb 2000 17:37:39 +0100 From: Wilko Bulte To: kibbet Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad blocks Message-ID: <20000226173739.A36626@yedi.iaf.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kibbet@knfpub.com on Sun, Feb 27, 2000 at 02:39:03AM +1030 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 27, 2000 at 02:39:03AM +1030, kibbet wrote: > Hi all, > > Quick question, how does the new ata driver handle bad blocks? > I've been tracking -current since around Nov 99 but haven't > seen this come up. ad does not any longer support bad144 (IIRC). Soeren can tell you more. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 10: 4:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from shiba.d.home.dynas.se (cns9-224-242.cm.starport.se [193.150.224.242]) by hub.freebsd.org (Postfix) with ESMTP id A97B337BB7F for ; Sat, 26 Feb 2000 10:04:19 -0800 (PST) (envelope-from mikko@shiba.d.home.dynas.se) Received: (from mikko@localhost) by shiba.d.home.dynas.se (8.9.3/8.9.3) id TAA01067; Sat, 26 Feb 2000 19:04:17 +0100 (CET) (envelope-from mikko) Date: Sat, 26 Feb 2000 19:04:17 +0100 (CET) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-Sender: mikko@shiba.d.home.dynas.se To: freebsd-current@freebsd.org Subject: USB NIC speed? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Reply-To: mikko@dynas.se X-MIME-Autoconverted: to 8bit by snemail 0.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seeing that -current now supports USB network devices, I got a Linksys 100TX "dongle". Question is: what kind of speed is reasonable to expect with this thing? Some unsophisticated tests show that I get around 3.7 Mbit/sec under FreeBSD, and about 5.5 Mbit/sec under Windogs98. This is on a Toshiba Portegé 3110CT (has a UHCI controller). The "fxp" device that comes with the machine can transfer over 8Mbit/sec over the same network (a fairly idle 10 Mbit segment). Is this as good as USB networking gets? Ok, I know that USB won't handle more than 12 Mbit, but right now it does not even reach one half that). At least the USB adapter is more comfortable for laptop use than the big ugly "docking station" thingie containing the fxp NIC :-) Just curious, /Mikko Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 10: 5:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id A5AA437BB7F for ; Sat, 26 Feb 2000 10:05:38 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from gateway.posi.net (root@alc-180.alcnet.com [63.69.28.180]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id NAA80717; Sat, 26 Feb 2000 13:05:27 -0500 (EST) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id NAA43831; Sat, 26 Feb 2000 13:07:05 -0500 (EST) (envelope-from kbyanc@posi.net) Date: Sat, 26 Feb 2000 13:07:03 -0500 (EST) From: Kelly Yancey To: kibbet Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad blocks 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, 27 Feb 2000, kibbet wrote: > Hi all, > > Quick question, how does the new ata driver handle bad blocks? > I've been tracking -current since around Nov 99 but haven't > seen this come up. As I recall, it doesn't. The reasoning is that modern IDE drives perform bad block reassignment so if you are seeing bad block errors, then the entire reserve of blocks available for reassignment has been exhausted. In which case, things are Very Bad and you should start backing up your data ASAP. In you scenario of upgrading from the old wd driver in -stable to the new ad driver in -current, the only advisable action is to just not do a bad block scan under -stable before upgrading. The should stop the complaints from the ad driver about the old-style bad block table. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 10:57:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 5ADA537B524 for ; Sat, 26 Feb 2000 10:57:27 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 33262 invoked by alias); 26 Feb 2000 18:57:03 -0000 Delivered-To: fixup-freebsd-current@freebsd.org@fixme Received: (qmail 33246 invoked by uid 0); 26 Feb 2000 18:57:03 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by pop.ptld.uswest.net with SMTP; 26 Feb 2000 18:57:03 -0000 Content-Length: 2869 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 26 Feb 2000 10:54:23 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Build World dies.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running 4.0-20000214-CURRENT doing a make world on a DEC Alpha 200 4/233 with a cvsup from last night, I get: ------------------------------ ===> libpam/modules/pam_cleartext_pass_ok rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/l ibpam/include -I/usr/obj/usr/src/alpha/usr/include /usr/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c cd /usr/src/lib/libpam/modules/pam_cleartext_pass_ok; make _EXTRADEPEND echo pam_cleartext_pass_ok.so: /usr/obj/usr/src/alpha/usr/lib/libskey.a >> .depend ===> libpam/modules/pam_deny rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/alpha/usr/include /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny /pam_deny.c cd /usr/src/lib/libpam/modules/pam_deny; make _EXTRADEPEND echo pam_deny.so: /usr/obj/usr/src/alpha/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_permit rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_permit/../../../../contrib/libpam/libpam/inclu de -I/usr/src/lib/libpam/modules/pam_permit/../../libpam -I/usr/obj/usr/src/alpha/usr/include /usr/src/lib/libpam/modules/pam_permit/../../../../contrib/libpam/modules/pam_pe rmit/pam_permit.c cd /usr/src/lib/libpam/modules/pam_permit; make _EXTRADEPEND echo pam_permit.so: /usr/obj/usr/src/alpha/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_radius rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/libpam/libpam/inclu de -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -I/usr/obj/usr/src/alpha/usr/include /usr/src/lib/libpam/modules/pam_radius/pam_radius.c cd /usr/src/lib/libpam/modules/pam_radius; make _EXTRADEPEND echo pam_radius.so: /usr/obj/usr/src/alpha/usr/lib/libradius.a /usr/obj/usr/src/alpha/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_skey rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_skey/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modules/pam_skey/../../libpam -I/usr/obj/usr/src/alpha/usr/include /usr/src/lib/libpam/modules/pam_skey/pam_skey.c cd /usr/src/lib/libpam/modules/pam_skey; make _EXTRADEPEND echo pam_skey.so: /usr/obj/usr/src/alpha/usr/lib/libskey.a /usr/obj/usr/src/alpha/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_ssh make: don't know how to make log-client.c. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ------------------------------ How would I fix that. ---------------------------------- E-Mail: William Woods Date: 26-Feb-00 Time: 10:51:44 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 12:53:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D6C8D37B5FC; Sat, 26 Feb 2000 12:52:58 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12OoCc-000D08-00; Sat, 26 Feb 2000 20:52:38 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12OoCc-0001SF-00; Sat, 26 Feb 2000 20:52:38 +0000 Date: Sat, 26 Feb 2000 20:52:38 +0000 From: Ben Smithurst To: bwoods2@uswest.net Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Re: Build World dies.... Message-ID: <20000226205238.C66145@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > ===> libpam/modules/pam_ssh > make: don't know how to make log-client.c. Stop > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > ------------------------------ > > How would I fix that. Add NO_OPENSSH=true and NO_OPENSSL=true to /etc/make.conf, that fixed it for me. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 12:57: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 9A80437B5FC for ; Sat, 26 Feb 2000 12:56:52 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 77538 invoked by alias); 26 Feb 2000 20:56:29 -0000 Delivered-To: fixup-freebsd-current@freebsd.org@fixme Received: (qmail 77523 invoked by uid 0); 26 Feb 2000 20:56:28 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by pop.ptld.uswest.net with SMTP; 26 Feb 2000 20:56:28 -0000 Content-Length: 804 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000226205238.C66145@strontium.scientia.demon.co.uk> Date: Sat, 26 Feb 2000 12:53:47 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Ben Smithurst Subject: Re: Build World dies.... Cc: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grr......cant say I like that idea, I would like to have them both... On 26-Feb-00 Ben Smithurst wrote: > William Woods wrote: > >> ===> libpam/modules/pam_ssh >> make: don't know how to make log-client.c. Stop >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> >> ------------------------------ >> >> How would I fix that. > > Add NO_OPENSSH=true and NO_OPENSSL=true to /etc/make.conf, that fixed it > for me. > > -- > Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D ---------------------------------- E-Mail: William Woods Date: 26-Feb-00 Time: 12:53:16 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 13: 4:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C1C4C37B5CC for ; Sat, 26 Feb 2000 13:04:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA14520; Sat, 26 Feb 2000 13:04:27 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA56970; Sat, 26 Feb 2000 13:04:27 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 26 Feb 2000 13:04:27 -0800 (PST) Message-Id: <200002262104.NAA56970@vashon.polstra.com> To: bg@sics.se Subject: Re: openssh uses /etc (bad) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Bjoern Groenvall wrote: > > While you are moving things around you might as well move > /usr/sbin/sshd to /usr/libexec/sshd where it should have > resided in the first place. No, that would be contrary to the conventions documented in hier(4). /usr/libexec is for things that are executed by other programs. Normal persistent daemons such as sshd belong in /usr/sbin. Take a look at the current contents of those two directories and you'll see the distinction. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 13: 7:25 2000 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 8DD3337B567 for ; Sat, 26 Feb 2000 13:07:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA51889; Sat, 26 Feb 2000 13:06:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Polstra Cc: bg@sics.se, current@FreeBSD.ORG Subject: Re: openssh uses /etc (bad) In-reply-to: Your message of "Sat, 26 Feb 2000 13:04:27 PST." <200002262104.NAA56970@vashon.polstra.com> Date: Sat, 26 Feb 2000 13:06:56 -0800 Message-ID: <51886.951599216@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, that would be contrary to the conventions documented in hier(4). > /usr/libexec is for things that are executed by other programs. > Normal persistent daemons such as sshd belong in /usr/sbin. Take a > look at the current contents of those two directories and you'll see > the distinction. Hmmmm. I hadn't thought of it like that, but you're right. I retract my own objection. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 13: 7:42 2000 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 EE9E737BFC4 for ; Sat, 26 Feb 2000 13:07:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA51861; Sat, 26 Feb 2000 13:04:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: bwoods2@uswest.net Cc: Ben Smithurst , freebsd-current@FreeBSD.ORG Subject: Re: Build World dies.... In-reply-to: Your message of "Sat, 26 Feb 2000 12:53:47 PST." Date: Sat, 26 Feb 2000 13:04:56 -0800 Message-ID: <51858.951599096@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we please stop cross-posting this? -current alone is a more than adequate mailing list. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 13:16:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id EA25037BDC1 for ; Sat, 26 Feb 2000 13:16:08 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12OoZD-000D4w-00; Sat, 26 Feb 2000 21:15:59 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12OoZD-000Cw8-00; Sat, 26 Feb 2000 21:15:59 +0000 Date: Sat, 26 Feb 2000 21:15:59 +0000 From: Ben Smithurst To: bwoods2@uswest.net Cc: freebsd-current@freebsd.org Subject: Re: Build World dies.... Message-ID: <20000226211559.D66145@strontium.scientia.demon.co.uk> References: <20000226205238.C66145@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > Grr......cant say I like that idea, I would like to have them both... Oh. You *have* cvsup'ed the cvs-crypto collection, right? I think that's the one you need. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 13:50:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from heimdall.piqnet.org (adsl-63-197-64-194.dsl.snfc21.pacbell.net [63.197.64.194]) by hub.freebsd.org (Postfix) with ESMTP id 7821F37B541 for ; Sat, 26 Feb 2000 13:50:15 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.piqnet.org (adsl-63-197-64-195.dsl.snfc21.pacbell.net [63.197.64.195]) by heimdall.piqnet.org (8.9.3/8.9.3) with ESMTP id NAA15477; Sat, 26 Feb 2000 13:54:43 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.piqnet.org (8.9.3/8.9.3) id NAA86111; Sat, 26 Feb 2000 13:51:48 -0800 (PST) (envelope-from joelh@gnu.org) X-Authentication-Warning: detlev.piqnet.org: joelh set sender to joelh@gnu.org using -f To: Will Andrews Cc: bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: kdelibs port broken? References: <86k8jssx5o.fsf@detlev.piqnet.org> <20000225195718.A17742@shadow.blackdawn.com> From: Joel Ray Holveck Date: 26 Feb 2000 13:51:47 -0800 In-Reply-To: Will Andrews's message of "Fri, 25 Feb 2000 19:57:18 -0500" Message-ID: <86n1onfx8s.fsf@detlev.piqnet.org> Lines: 30 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Not with the port. I was installing Qt to /usr/local/qt, and the port >> was putting the libs in a non-standard place where KDE couldn't find >> them. :-C I built Qt 1.45 by hand, installed it, set QTDIR, and >> everything compiled fine. I haven't done much testing on it yet (only >> ran kdehelp a couple of times), but nothing obvious. > As far as I can tell, the KDE ports find Qt just fine. KDE insists on > putting everything under the same dir, as does Qt. This violates our > hierarchy (see hier(7) manpage), so we had to make some mods to the > configurations for Qt and KDE ports. It's not that difficult. > If you're gonna use a port, use ports for its dependencies too. You'd be > stupid not to use the ports whenever you can. No one has ever provided > me a convincing reason why this is not true. It appears that you do not care to hear my reasons, so I won't bother. If I have reasons that I want Qt and KDE in their own directories, I will do so. I would rather apps that expect Qt and KDE to be set up the same as they are on other OS's to work, than to require apps to be quirkified for FreeBSD's heir. You may not agree with my decision, and I'm not asking you to. But if bwoods has the same preference that I do, I'll gladly tell him how to implement them, and would appreciate not being told I'm stupid in the process. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 14:45:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from diwanh.stu.rpi.edu (diwanh.stu.rpi.edu [128.113.151.72]) by hub.freebsd.org (Postfix) with ESMTP id D86D237BEA3 for ; Sat, 26 Feb 2000 14:45:24 -0800 (PST) (envelope-from hdiwan@diwanh.stu.rpi.edu) Received: (from hdiwan@localhost) by diwanh.stu.rpi.edu (8.9.3/8.9.3) id RAA07435 for freebsd-current@freebsd.org; Sat, 26 Feb 2000 17:45:14 -0500 (EST) (envelope-from hdiwan) Date: Sat, 26 Feb 2000 17:45:14 -0500 From: Hasan Diwan To: freebsd-current@freebsd.org Subject: installword dies [Feb 26 12:52 EST] Message-ID: <20000226174514.C6001@diwanh.stu.rpi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CblX+4bnyfN0pR09" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --CblX+4bnyfN0pR09 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable /usr/share/man/man3/pam_close_session.3.gz -> /usr/share/man/man3/pam_open_= session.3.gz=0D ln: /usr/share/man/man3/pam_close_session.3.gz: No such file or directory=0D *** Error code 1=0D --=20 Hasan Diwan [hdiwan@pobox.com] :) Rensselaer Polytechnic Institute=20 Computer Science Department --CblX+4bnyfN0pR09 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOLhXefitTU38wbMJAQEU4QP5AamQ5GGizT59mCAzuH4A6xB+SPpvROb7 zfLKP4c1CnPhKuom6kIGFYNdOuQR/MsJADIbssi2BCtU927kjA5VShMMED/Qto4q P95iOTwemfj/IBhbJM8hBaQOsqlJkXO9zk80rx5NbIG3ziGfPPhOggoKk3bcec0j Nh4c7Ji+Yko= =/WTZ -----END PGP SIGNATURE----- --CblX+4bnyfN0pR09-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 15:14:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from Stalker.Alfacom.net (SAT.Alfacom.net [207.241.164.112]) by hub.freebsd.org (Postfix) with ESMTP id BE5FF37B587 for ; Sat, 26 Feb 2000 15:13:28 -0800 (PST) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (dup-102.alfacom.net [62.244.36.102]) by Stalker.Alfacom.net (8.9.0/8.9.0) with ESMTP id AAA28206 for ; Sun, 27 Feb 2000 00:49:41 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.9.3/8.9.3) with ESMTP id AAA25538 for ; Sun, 27 Feb 2000 00:49:35 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Sun, 27 Feb 2000 00:49:34 +0200 (EET) From: Vladimir Kushnir To: freebsd-current@FreeBSD.ORG Subject: Re: Build World dies.... In-Reply-To: <20000226211559.D66145@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for (perhaps) stupid question but how can I get them if I'm using CTM? On Sat, 26 Feb 2000, Ben Smithurst wrote: > William Woods wrote: > > > Grr......cant say I like that idea, I would like to have them both... > > Oh. You *have* cvsup'ed the cvs-crypto collection, right? I think that's > the one you need. > Regards, Vladimir -- ===========================|======================= Vladimir Kushnir | vkushnir@Alfacom.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 Feb 26 15:38: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AEA2D37B573; Sat, 26 Feb 2000 15:37:59 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA99258; Sat, 26 Feb 2000 15:37:59 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 15:37:58 -0800 (PST) From: Kris Kennaway To: Bjoern Groenvall Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch 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 26 Feb 2000, Bjoern Groenvall wrote: > Right, the code does not lie (if ssh is setuid root). But, if the host > key has not yet been created, then no host can have the public key and > thus rsa-rhosts authentication won't work anyways. It is not required > to run ssh-keygen to make ssh work, Sshd still requires the host key > to operate. I don't follow you - if no host key is generated, then you can't ever use the RSA-rhosts authentication mechanism to log into another server until you do. Thus part of ssh's functionality is broken until you generate that key, so we do it for you the first time you boot. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 15:55:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 31AE037B646; Sat, 26 Feb 2000 15:55:38 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA00414; Sat, 26 Feb 2000 15:55:38 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 15:55:37 -0800 (PST) From: Kris Kennaway To: sthaug@nethelp.no Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: OpenSSH /etc patch In-Reply-To: <68686.951563042@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 Sat, 26 Feb 2000 sthaug@nethelp.no wrote: > > If you want to tinker with the file permissions, can't you deal with the > > fact that the startup scripts will create a host key for you the first > > time you boot with it installed? > > As long as there is an easy way of running ssh without any special privs, > I'm happy. ssh 'seemed to work' when not setuid. I could log in using RSA authentication as well as password-based, but didnt try much else. From /usr/src/crypto/openssh/OVERVIEW: - The client is suid root. It tries to temporarily give up this rights while reading the configuration data. The root privileges are only used to make the connection (from a privileged socket). Any extra privileges are dropped before calling ssh_login. This comment doesn't seem to be completely accurate given what I earlier posted from the code (it's also used for RSA-rhosts authentication), but for most purposes you can safely remove the setuid flag. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 16: 2: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id 94E6937B5A3; Sat, 26 Feb 2000 16:01:52 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id DAA06886; Sun, 27 Feb 2000 03:01:49 +0300 (MSK) (envelope-from ache) Date: Sun, 27 Feb 2000 03:01:49 +0300 From: "Andrey A. Chernov" To: markm@freebsd.org, peter@freebsd.org, green@freebsd.org Cc: current@freebsd.org Subject: [PATCH] Fix login.conf, expiration, BSD compatibility in OpenSSH Message-ID: <20000227030149.A6864@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch revive almost all login.conf and password/account expiration features, makes OpenSSH more FreeBSD login compatible and fix non-critical memory leak. Please review and commit. --- sshd.c.old Fri Feb 25 08:23:45 2000 +++ sshd.c Sun Feb 27 02:53:33 2000 @@ -37,9 +37,8 @@ #endif /* LIBWRAP */ #ifdef __FreeBSD__ -#include -#include #define LOGIN_CAP +#define _PATH_CHPASS "/usr/bin/passwd" #endif /* __FreeBSD__ */ #ifdef LOGIN_CAP @@ -1246,6 +1245,7 @@ return 0; } } +#ifndef __FreeBSD__ /* FreeBSD handle it later */ /* Fail if the account's expiration time has passed. */ if (pw->pw_expire != 0) { struct timeval tv; @@ -1254,6 +1254,7 @@ if (tv.tv_sec >= pw->pw_expire) return 0; } +#endif /* !__FreeBSD__ */ /* We found no reason not to let this user try to log on... */ return 1; } @@ -1268,6 +1269,12 @@ struct passwd *pw, pwcopy; int plen, ulen; char *user; +#ifdef LOGIN_CAP + login_cap_t *lc; + char *hosts; + const char *from_host, *from_ip; + int denied; +#endif /* LOGIN_CAP */ /* Get the name of the user that we wish to log in as. */ packet_read_expect(&plen, SSH_CMSG_USER); @@ -1338,6 +1345,38 @@ packet_disconnect("ROOT LOGIN REFUSED FROM %.200s", get_canonical_hostname()); } + +#ifdef LOGIN_CAP + lc = login_getpwclass(pw); + if (lc == NULL) + lc = login_getclassbyname(NULL, pw); + from_host = get_canonical_hostname(); + from_ip = get_remote_ipaddr(); + + denied = 0; + if ((hosts = login_getcapstr(lc, "host.deny", NULL, NULL)) != NULL) { + denied = match_hostname(from_host, hosts, strlen(hosts)); + if (!denied) + denied = match_hostname(from_ip, hosts, strlen(hosts)); + } + if (!denied && + (hosts = login_getcapstr(lc, "host.allow", NULL, NULL)) != NULL) { + denied = !match_hostname(from_host, hosts, strlen(hosts)); + if (denied) + denied = !match_hostname(from_ip, hosts, strlen(hosts)); + } + login_close(lc); + if (denied) { + log("Denied connection for %.200s from %.200s [%.200s].", + pw->pw_name, from_host, from_ip); + packet_disconnect("Sorry, you are not allowed to connect."); + } +#endif /* LOGIN_CAP */ + + if (pw->pw_uid == 0) + log("ROOT LOGIN as '%.100s' from %.100s", + pw->pw_name, get_canonical_hostname()); + /* The user has been authenticated and accepted. */ packet_start(SSH_SMSG_SUCCESS); packet_send(); @@ -2086,6 +2125,11 @@ login_cap_t *lc; char *fname; #endif /* LOGIN_CAP */ +#ifdef __FreeBSD__ +#define DEFAULT_WARN (2L * 7L * 86400L) /* Two weeks */ + struct timeval tv; + time_t warntime = DEFAULT_WARN; +#endif /* __FreeBSD__ */ /* Get remote host name. */ hostname = get_canonical_hostname(); @@ -2157,6 +2201,50 @@ quiet_login = login_getcapbool(lc, "hushlogin", quiet_login); #endif /* LOGIN_CAP */ +#ifdef __FreeBSD__ + if (pw->pw_change || pw->pw_expire) + (void)gettimeofday(&tv, NULL); +#ifdef LOGIN_CAP + warntime = login_getcaptime(lc, "warnpassword", + DEFAULT_WARN, DEFAULT_WARN); +#endif /* LOGIN_CAP */ + /* + * If the password change time is set and has passed, give the + * user a password expiry notice and chance to change it. + */ + if (pw->pw_change != 0) { + if (tv.tv_sec >= pw->pw_change) { + (void)printf( + "Sorry -- your password has expired.\n"); + log("%s Password expired - forcing change", + pw->pw_name); + command = _PATH_CHPASS; + } else if (pw->pw_change - tv.tv_sec < warntime && + !quiet_login) + (void)printf( + "Warning: your password expires on %s", + ctime(&pw->pw_change)); + } +#ifdef LOGIN_CAP + warntime = login_getcaptime(lc, "warnexpire", + DEFAULT_WARN, DEFAULT_WARN); +#endif /* LOGIN_CAP */ + if (pw->pw_expire) { + if (tv.tv_sec >= pw->pw_expire) { + (void)printf( + "Sorry -- your account has expired.\n"); + log( + "LOGIN %.200s REFUSED (EXPIRED) FROM %.200s ON TTY %.200s", + pw->pw_name, hostname, ttyname); + exit(254); + } else if (pw->pw_expire - tv.tv_sec < warntime && + !quiet_login) + (void)printf( + "Warning: your account expires on %s", + ctime(&pw->pw_expire)); + } +#endif /* __FreeBSD__ */ + /* * If the user has logged in before, display the time of last * login. However, don't display anything extra if a command @@ -2203,10 +2291,9 @@ !options.use_login) { #ifdef LOGIN_CAP fname = login_getcapstr(lc, "welcome", NULL, NULL); - login_close(lc); if (fname == NULL || (f = fopen(fname, "r")) == NULL) f = fopen("/etc/motd", "r"); -#else /* LOGIN_CAP */ +#else /* !LOGIN_CAP */ f = fopen("/etc/motd", "r"); #endif /* LOGIN_CAP */ /* Print /etc/motd if it exists. */ @@ -2216,6 +2303,9 @@ fclose(f); } } +#ifdef LOGIN_CAP + login_close(lc); +#endif /* LOGIN_CAP */ /* Do common processing for the child, such as execing the command. */ do_child(command, pw, term, display, auth_proto, auth_data, ttyname); @@ -2363,7 +2453,7 @@ char buf[256]; FILE *f; unsigned int envsize, i; - char **env; + char **env = NULL; extern char **environ; struct stat st; char *argv[10]; @@ -2373,29 +2463,24 @@ lc = login_getpwclass(pw); if (lc == NULL) lc = login_getclassbyname(NULL, pw); -#endif /* LOGIN_CAP */ - + if (pw->pw_uid != 0) + auth_checknologin(lc); +#else /* !LOGIN_CAP */ f = fopen("/etc/nologin", "r"); -#ifdef __FreeBSD__ - if (f == NULL) - f = fopen("/var/run/nologin", "r"); -#endif /* __FreeBSD__ */ if (f) { /* /etc/nologin exists. Print its contents and exit. */ -#ifdef LOGIN_CAP - /* On FreeBSD, etc., allow overriding nologin via login.conf. */ - if (!login_getcapbool(lc, "ignorenologin", 0)) { -#else /* LOGIN_CAP */ - if (1) { -#endif /* LOGIN_CAP */ - while (fgets(buf, sizeof(buf), f)) - fputs(buf, stderr); - fclose(f); - if (pw->pw_uid != 0) - exit(254); - } + while (fgets(buf, sizeof(buf), f)) + fputs(buf, stderr); + fclose(f); + if (pw->pw_uid != 0) + exit(254); } +#endif /* LOGIN_CAP */ + +#ifdef LOGIN_CAP + if (options.use_login) +#endif /* LOGIN_CAP */ /* Set login name in the kernel. */ if (setlogin(pw->pw_name) < 0) error("setlogin failed: %s", strerror(errno)); @@ -2405,12 +2490,42 @@ switch, so we let login(1) to this for us. */ if (!options.use_login) { #ifdef LOGIN_CAP - if (setclasscontext(pw->pw_class, LOGIN_SETPRIORITY | - LOGIN_SETRESOURCES | LOGIN_SETUMASK) == -1) { - perror("setclasscontext"); - exit(1); - } -#endif /* LOGIN_CAP */ + char **tmpenv; + + /* Initialize temp environment */ + envsize = 64; + env = xmalloc(envsize * sizeof(char *)); + env[0] = NULL; + + child_set_env(&env, &envsize, "PATH", + (pw->pw_uid == 0) ? + _PATH_STDPATH : _PATH_DEFPATH); + + snprintf(buf, sizeof buf, "%.200s/%.50s", + _PATH_MAILDIR, pw->pw_name); + child_set_env(&env, &envsize, "MAIL", buf); + + if (getenv("TZ")) + child_set_env(&env, &envsize, "TZ", getenv("TZ")); + + /* Save parent environment */ + tmpenv = environ; + environ = env; + + if (setusercontext(lc, pw, pw->pw_uid, LOGIN_SETALL) < 0) + fatal("setusercontext failed: %s", strerror(errno)); + + /* Restore parent environment */ + env = environ; + environ = tmpenv; + + for (envsize = 0; env[envsize] != NULL; ++envsize) + ; + envsize = (envsize < 100) ? 100 : envsize + 16; + env = xrealloc(env, envsize * sizeof(char *)); + +#else /* !LOGIN_CAP */ + if (getuid() == 0 || geteuid() == 0) { if (setgid(pw->pw_gid) < 0) { perror("setgid"); @@ -2428,18 +2543,15 @@ } if (getuid() != pw->pw_uid || geteuid() != pw->pw_uid) fatal("Failed to set uids to %d.", (int) pw->pw_uid); +#endif /* LOGIN_CAP */ } /* * Get the shell from the password data. An empty shell field is * legal, and means /bin/sh. */ + shell = (pw->pw_shell[0] == '\0') ? _PATH_BSHELL : pw->pw_shell; #ifdef LOGIN_CAP - shell = pw->pw_shell; shell = login_getcapstr(lc, "shell", shell, shell); - if (shell[0] == '\0') - shell = _PATH_BSHELL; -#else /* LOGIN_CAP */ - shell = (pw->pw_shell[0] == '\0') ? _PATH_BSHELL : pw->pw_shell; #endif /* LOGIN_CAP */ #ifdef AFS @@ -2455,29 +2567,31 @@ #endif /* AFS */ /* Initialize the environment. */ - envsize = 100; - env = xmalloc(envsize * sizeof(char *)); - env[0] = NULL; + if (env == NULL) { + envsize = 100; + env = xmalloc(envsize * sizeof(char *)); + env[0] = NULL; + } if (!options.use_login) { /* Set basic environment. */ child_set_env(&env, &envsize, "USER", pw->pw_name); child_set_env(&env, &envsize, "LOGNAME", pw->pw_name); child_set_env(&env, &envsize, "HOME", pw->pw_dir); -#ifdef LOGIN_CAP - child_set_env(&env, &envsize, "PATH", - login_getpath(lc, "path", _PATH_STDPATH)); -#else /* LOGIN_CAP */ +#ifndef LOGIN_CAP child_set_env(&env, &envsize, "PATH", _PATH_STDPATH); -#endif /* LOGIN_CAP */ snprintf(buf, sizeof buf, "%.200s/%.50s", _PATH_MAILDIR, pw->pw_name); child_set_env(&env, &envsize, "MAIL", buf); +#endif /* !LOGIN_CAP */ /* Normal systems set SHELL by default. */ child_set_env(&env, &envsize, "SHELL", shell); } +#ifdef LOGIN_CAP + if (options.use_login) +#endif /* LOGIN_CAP */ if (getenv("TZ")) child_set_env(&env, &envsize, "TZ", getenv("TZ")); @@ -2559,10 +2673,6 @@ */ endpwent(); -#ifdef LOGIN_CAP - login_close(lc); -#endif /* LOGIN_CAP */ - /* * Close any extra open file descriptors so that we don\'t have them * hanging around in clients. Note that we want to do this after @@ -2573,9 +2683,46 @@ close(i); /* Change current directory to the user\'s home directory. */ - if (chdir(pw->pw_dir) < 0) + if ( +#ifdef __FreeBSD__ + !*pw->pw_dir || +#endif /* __FreeBSD__ */ + chdir(pw->pw_dir) < 0 + ) { +#ifdef __FreeBSD__ + int quiet_login = 0; +#endif /* __FreeBSD__ */ +#ifdef LOGIN_CAP + if (login_getcapbool(lc, "requirehome", 0)) { + (void)printf("Home directory not available\n"); + log("LOGIN %.200s REFUSED (HOMEDIR) ON TTY %.200s", + pw->pw_name, ttyname); + exit(254); + } +#endif /* LOGIN_CAP */ +#ifdef __FreeBSD__ + if (chdir("/") < 0) { + (void)printf("Cannot find root directory\n"); + log("LOGIN %.200s REFUSED (ROOTDIR) ON TTY %.200s", + pw->pw_name, ttyname); + exit(254); + } +#ifdef LOGIN_CAP + quiet_login = login_getcapbool(lc, "hushlogin", 0); +#endif /* LOGIN_CAP */ + if (!quiet_login || *pw->pw_dir) + (void)printf( + "No home directory.\nLogging in with home = \"/\".\n"); + +#else /* !__FreeBSD__ */ + fprintf(stderr, "Could not chdir to home directory %s: %s\n", pw->pw_dir, strerror(errno)); +#endif /* __FreeBSD__ */ + } +#ifdef LOGIN_CAP + login_close(lc); +#endif /* LOGIN_CAP */ /* * Must take new environment into use so that .ssh/rc, /etc/sshrc and @@ -2588,26 +2735,6 @@ * in this order). */ if (!options.use_login) { -#ifdef __FreeBSD__ - /* - * If the password change time is set and has passed, give the - * user a password expiry notice and chance to change it. - */ - if (pw->pw_change != 0) { - struct timeval tv; - - (void)gettimeofday(&tv, NULL); - if (tv.tv_sec >= pw->pw_change) { - (void)printf( - "Sorry -- your password has expired.\n"); - syslog(LOG_INFO, - "%s Password expired - forcing change", - pw->pw_name); - if (system("/usr/bin/passwd") != 0) - perror("/usr/bin/passwd"); - } - } -#endif /* __FreeBSD__ */ if (stat(SSH_USER_RC, &st) >= 0) { if (debug_flag) fprintf(stderr, "Running /bin/sh %s\n", SSH_USER_RC); @@ -2675,7 +2802,11 @@ mailbox = getenv("MAIL"); if (mailbox != NULL) { if (stat(mailbox, &mailstat) != 0 || mailstat.st_size == 0) +#ifdef __FreeBSD__ + ; +#else /* !__FreeBSD__ */ printf("No mail.\n"); +#endif /* __FreeBSD__ */ else if (mailstat.st_mtime < mailstat.st_atime) printf("You have mail.\n"); else -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 16:10:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 192CB37BC1E; Sat, 26 Feb 2000 16:10:37 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA01292; Sat, 26 Feb 2000 16:10:37 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 16:10:36 -0800 (PST) From: Kris Kennaway To: Ben Smithurst Cc: bwoods2@uswest.net, freebsd-current@freebsd.org Subject: Re: Build World dies.... In-Reply-To: <20000226211559.D66145@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Feb 2000, Ben Smithurst wrote: > William Woods wrote: > > > Grr......cant say I like that idea, I would like to have them both... > > Oh. You *have* cvsup'ed the cvs-crypto collection, right? I think that's > the one you need. You need: src-crypto src-secure Are you still having the problem with the latest sources? Peter made some more changes last night. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 16:21:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0170837BFDC for ; Sat, 26 Feb 2000 16:21:25 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA01863 for ; Sat, 26 Feb 2000 16:21:24 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 16:21:24 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: NO_DESCRYPT patch Message-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 something which has been requested a fair bit..it will disable the building of the DES CRYPT libraries even if you have the crypto sources installed, so you can e.g. get OpenSSL/OpenSSH without having to deal with the pitfalls of libdescrypt. It seems to work fine for me..if I hear any other positive feedback I'll commit it. Kris Index: lib/Makefile =================================================================== RCS file: /home/ncvs/src/lib/Makefile,v retrieving revision 1.106 diff -u -r1.106 Makefile --- lib/Makefile 2000/01/21 02:00:53 1.106 +++ lib/Makefile 2000/02/26 05:30:38 @@ -43,7 +43,7 @@ .endif _libcrypt= libcrypt -.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) +.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) && !defined(NO_DESCRYPT) # Build both libraries. They have different names, so no harm, # and this avoids having stale libscrypt.* _libcrypt+= ../secure/lib/libcrypt ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 16:31:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 814EB37B56F for ; Sat, 26 Feb 2000 16:31:17 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.5.62]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 665201C8B for ; Sun, 27 Feb 2000 01:31:16 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id E42F44E3F; Sun, 27 Feb 2000 01:31:15 +0100 (CET) Date: Sun, 27 Feb 2000 01:31:15 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Re: openssh uses /etc (bad) Message-ID: <20000227013115.A13714@caerdonn.eurocontrol.fr> Mail-Followup-To: FreeBSD Current Users' list References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bg@sics.se on Sat, Feb 26, 2000 at 06:45:24PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bjoern Groenvall: > While you are moving things around you might as well move > /usr/sbin/sshd to /usr/libexec/sshd where it should have > resided in the first place. I disagree. sshd is like named or moused, a daemon running standalone and not under inetd's control. Most of /usr/libexec is not run by itself. -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 17:52:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 64BF837B5CD; Sat, 26 Feb 2000 17:52:17 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA61960; Sat, 26 Feb 2000 17:52:16 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B88350.515F0206@gorean.org> Date: Sat, 26 Feb 2000 17:52:16 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: NO_DESCRYPT patch References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > This is something which has been requested a fair bit..it will disable the > building of the DES CRYPT libraries even if you have the crypto sources > installed, so you can e.g. get OpenSSL/OpenSSH without having to deal with > the pitfalls of libdescrypt. It seems to work fine for me..if I hear any > other positive feedback I'll commit it. What I'd really like to see is a way to have DES code available for things like front page (yeah, yeah... I know) and other things that just have to have it but not have anything in the base system use it unless I tell it to. This might not be possible of course, but if I can't have that then I'd definitely like to be able to to use the openssl and openssh stuff without being forced to have DES. Meanwhile, it seems that to get all the new bits we have to have cvs-crypto in the cvsup file, yes? And if we do that currently (before your patch) we will end up installing DES, right? Trying to understand, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 17:59:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AB67137B675; Sat, 26 Feb 2000 17:59:29 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA08297; Sat, 26 Feb 2000 17:59:29 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 17:59:28 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: current@FreeBSD.org Subject: Re: NO_DESCRYPT patch In-Reply-To: <38B88350.515F0206@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Feb 2000, Doug Barton wrote: > Meanwhile, it seems that to get all the new bits we have to have > cvs-crypto in the cvsup file, yes? And if we do that currently (before > your patch) we will end up installing DES, right? Yes. The downside is that with the DES crypt library any new user passwords you create will be in the weaker DES format. Existing MD5 passwords will stay MD5 when they're updated, but new users get DES. You can hack around this easily enough (e.g. by changing the logic in libcrypt) but it's not yet available by default. If you need to have a DES-capable libcrypt this patch won't help, but most people don't need that. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 18: 8:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id 39F4437B5E6; Sat, 26 Feb 2000 18:08:13 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id PAA27945; Sun, 27 Feb 2000 15:08:09 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id PAA00870; Sun, 27 Feb 2000 15:08:07 +1300 (NZDT) Date: Sun, 27 Feb 2000 15:08:07 +1300 From: Joerg Micheel To: Michael Lucas Cc: questions@freebsd.org, current@freebsd.org, joerg@cs.waikato.ac.nz Subject: Re: HP servers and FreeBSD? Message-ID: <20000227150807.A859@cs.waikato.ac.nz> References: <200002252007.PAA12839@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200002252007.PAA12839@blackhelicopters.org>; from Michael Lucas on Fri, Feb 25, 2000 at 03:07:18PM -0500 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, On Fri, Feb 25, 2000 at 03:07:18PM -0500, Michael Lucas wrote: > I've been offered a deal on a couple of HP servers. Does anyone have > any experience with the HP Netserver LC3 7/550? I have just installed a 0222 current on a HP Kayak XU800. This is one of the latest models. I'm experiencing problems with the builtin SCSI adapter AIC-7892. It could be BIOS/firmware related, a regular Adaptec works just fine. A detailed report will follow once I have sorted out these issues. > How about the HP Surestore DAT 12/24? Can recommend. I'm running a DAT40i (that's the 40GB drive, native 20GB DAT4). No problems with FreeBSD 3.2 and 3.3. Just bear in mind to use the proper tapes (DATn tapes for DATn density) for whatever purpose you have in mind. Some people have *very* bad experience with helical scan drives in general. If you have time to wait, perhaps one of the upcoming tape technologies (LTO) could be a better choice. Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 18:39:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 47AA137B56F for ; Sat, 26 Feb 2000 18:39:29 -0800 (PST) (envelope-from kibbet@kibby.au.knfpub.com) Received: (from kibbet@localhost) by kibby.au.knfpub.com (8.9.3/8.9.3) id NAA10517 for freebsd-current@freebsd.org; Sun, 27 Feb 2000 13:09:29 +1030 (CST) (envelope-from kibbet) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 27 Feb 2000 13:09:28 +1030 (CST) From: kibbet To: freebsd-current@freebsd.org Subject: Re: bad blocks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On 26-Feb-00 Kelly Yancey wrote: > On Sun, 27 Feb 2000, kibbet wrote: > >> Hi all, >> >> Quick question, how does the new ata driver handle bad blocks? >> I've been tracking -current since around Nov 99 but haven't >> seen this come up. > > As I recall, it doesn't. The reasoning is that modern IDE drives perform bad > block reassignment so if you are seeing bad block errors, then the entire > reserve of blocks available for reassignment has been exhausted. In which > case, things are Very Bad and you should start backing up your data ASAP. Yup, no problem, sounds fair. Just read the docs for this drive, it dosent say anything about bad blocks, but its only a few years old so I'm assuming it does the fancy bad block assignment. :) (its an IBM DJAA-31700) No need to backup, I keep it around for this specific reason :) > In you scenario of upgrading from the old wd driver in -stable to the new ad > driver in -current, the only advisable action is to just not do a bad block > scan under -stable before upgrading. The should stop the complaints from the > ad driver about the old-style bad block table. The new ad driver dosen't seem to complain at all if I've bad block scanned when installing -stable (infact I can't install -stable if I haven't block scanned the drive). The (-current) ad and wd drivers just seem to ignore the fact the drive had been scanned. The problem arises when I use bad144 on -current, rather than just complaining it actually makes the system unbootable. eg.; freebie4# bad144 -s -v ad0 cyl: 3307, tracks: 16, secs: 63, sec/cyl: 1008, start: 0, end: 3334212 bad144: couldn't set disk in "badscan" mode: Operation not supported by device Block: 1202131 will be marked BAD. [snip more blocks marked BAD] Then I reboot, and I get; ad0: bad sector table not supported So this raises a few questions; 1: Should bad144 exit without doing anything if it detects a modern drive that handles its own bad blocks? 2: Should the process of mounting root ignore bad144 info if the drive does its own bad blocks? IMHO one of the above should happen, you shouldn't be left with an unmountable root because you ran bad144 on a drive that dosen't support it. 3: Is it possible (or advisable) to use badd144 info in conjunction with the drives bad block data? (I've got 21 bad blocks on this drive, which haven't grown since they appeared, I'd like these blocks to be ignored) - I guess this would be rather more than just a trivial task :) 4: The $6m question, how do I fix it so I can mount root? :) I have a generic -stable kernel (so I think I can boot), but I can't find any mention of how to tell the drive not to use bad144 info. Anyways, abuse away if I've totally missed the plot :) Cheers, Kent Ibbetson kib@knfpub.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 19:14:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from balrog.net (cvx-mal-1-20.ppp.netlink.se [212.242.97.20]) by hub.freebsd.org (Postfix) with ESMTP id 1144937B525 for ; Sat, 26 Feb 2000 19:13:59 -0800 (PST) (envelope-from johan@balrog.net) Received: (from johan@localhost) by balrog.net (8.9.3/8.9.3) id EAA05275 for current@FreeBSD.ORG; Sun, 27 Feb 2000 04:15:07 GMT (envelope-from johan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 27 Feb 2000 04:15:06 -0000 (GMT) From: Johan=?us-ascii?Q?_M=E5rtensson?= To: current@FreeBSD.ORG Subject: Linux-Netscape-communicator47-Port - problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried installing the linux-netscape-47-communicator port, during the download it kept printing the download message and the % constantly. And then when the download was finished (from ftp.netscape.com) it started over again, deleting the file and downloading it anew from ftp.sunet.se (closer site for me). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 19:14:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1A94C37B50C for ; Sat, 26 Feb 2000 19:14:17 -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.9.3/8.9.3) with SMTP id WAA04180 for ; Sat, 26 Feb 2000 22:15:20 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 26 Feb 2000 22:15:20 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: installing 4.0 2/26 snapshot: edX/hardware probe problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a somewhat old 486 box I'm using as a dual-homed host. It has two SMC EtherEZ ISA cards in it, and works fine under 3.4-STABLE. The cards are on irregular ports/IRQs/et al. My problem is that in the kernel config, it is only possible to hard code ed0's settings, but that ed1 is probed (incorrectly) by the hardware probe later, resulting in a hang. I'd be happy to either have ed1 not probed at all, or to be able to edit the settings ed1 is probed as, but not neither :-). Right now, without pulling hardware, there seems to be no way to install the snapshot, which is unfortunate given that it is a valid configuration, and works fine under 3.4. In fact, it would probably even work fine with a custom 4.0 kernel, but I'd rather not do that if there's an alternative (especially since it seems like there should be a way to make it work). Any suggestions about fixes? I'd really like to just ``disable ed1'' or set the settings correctly, but ed1 is unrecognized by the CLI. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 19:16:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id B5A1C37B50C for ; Sat, 26 Feb 2000 19:16:25 -0800 (PST) (envelope-from kibbet@kibby.au.knfpub.com) Received: (from kibbet@localhost) by kibby.au.knfpub.com (8.9.3/8.9.3) id NAA10577 for freebsd-current@freebsd.org; Sun, 27 Feb 2000 13:46:26 +1030 (CST) (envelope-from kibbet) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 27 Feb 2000 13:46:25 +1030 (CST) From: kibbet To: freebsd-current@freebsd.org Subject: Re: bad blocks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh ho, I'll blame the lack of sleep, lack of coffee, the heat, a flat tyre... something :) Someone has pointed out that bad144 was taken outta the source tree ages ago so I must have been using an old binary. No comments required, I have flamed myself privately :) Kent Ibbetson kib@knfpub.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 19:19:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 1CB3337B5A0; Sat, 26 Feb 2000 19:19:37 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p3-177.hitter.net [207.192.76.177]) by pawn.primelocation.net (Postfix) with ESMTP id 5EFB39B17; Sat, 26 Feb 2000 22:19:34 -0500 (EST) Date: Sat, 26 Feb 2000 22:19:29 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Kris Kennaway Cc: current@freebsd.org Subject: Re: NO_DESCRYPT patch 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, 26 Feb 2000, Kris Kennaway wrote: > This is something which has been requested a fair bit..it will disable the > building of the DES CRYPT libraries even if you have the crypto sources > installed, so you can e.g. get OpenSSL/OpenSSH without having to deal with > the pitfalls of libdescrypt. It seems to work fine for me..if I hear any > other positive feedback I'll commit it. > Works for me... /etc/make.conf: CFLAGS= -O -pipe COPTFLAGS= -O -pipe NO_DESCRYPT= YES RSAREF= YES USA_RESIDENT= YES The resulting libs after installworld: jedgar@earth:~$ ll /usr/lib/*crypt* lrwxr-xr-x 1 root wheel 11 Feb 26 22:12 /usr/lib/libcrypt.a -> libscrypt.a lrwxr-xr-x 1 root wheel 12 Feb 26 22:12 /usr/lib/libcrypt.so -> libscrypt.so lrwxr-xr-x 1 root wheel 14 Feb 26 22:12 /usr/lib/libcrypt.so.2 -> libscrypt.so.2 lrwxr-xr-x 1 root wheel 13 Feb 26 22:12 /usr/lib/libcrypt_p.a -> libscrypt_p.a -r--r--r-- 1 root wheel 1088060 Feb 26 22:16 /usr/lib/libcrypto.a lrwxr-xr-x 1 root wheel 14 Feb 26 22:16 /usr/lib/libcrypto.so -> libcrypto.so.1 -r--r--r-- 1 root wheel 651156 Feb 26 22:16 /usr/lib/libcrypto.so.1 -r--r--r-- 1 root wheel 1161880 Feb 26 22:16 /usr/lib/libcrypto_p.a -r--r--r-- 1 root wheel 8632 Feb 26 22:12 /usr/lib/libscrypt.a lrwxr-xr-x 1 root wheel 14 Feb 26 22:12 /usr/lib/libscrypt.so -> libscrypt.so.2 -r--r--r-- 1 root wheel 5084 Feb 26 22:12 /usr/lib/libscrypt.so.2 -r--r--r-- 1 root wheel 9278 Feb 26 22:12 /usr/lib/libscrypt_p.a jedgar@earth:~$ ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 19:47:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from heidegger.uol.com.br (heidegger.uol.com.br [200.230.198.88]) by hub.freebsd.org (Postfix) with ESMTP id D76F937B525 for ; Sat, 26 Feb 2000 19:47:25 -0800 (PST) (envelope-from lioux-alias-ppp-current=freebsd.org@uol.com.br) Received: from 200.197.112.65 (bsa-1-as01-7-a36.gd.uol.com.br [200.197.118.36]) by heidegger.uol.com.br (8.9.1/8.9.1) with ESMTP id AAA03146 for ; Sun, 27 Feb 2000 00:41:57 -0300 (BRT) Received: (qmail 10520 invoked by uid 1001); 27 Feb 2000 04:07:22 -0000 From: lioux@uol.com.br Date: Sun, 27 Feb 2000 01:07:22 -0300 To: Kris Kennaway Cc: current@freebsd.org Subject: Re: NO_DESCRYPT patch Message-ID: <20000227010722.A10505@Fedaykin.here> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@FreeBSD.org on Sat, Feb 26, 2000 at 04:21:24PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 26, 2000 at 04:21:24PM -0800, Kris Kennaway wrote: > This is something which has been requested a fair bit..it will disable the > building of the DES CRYPT libraries even if you have the crypto sources > installed, so you can e.g. get OpenSSL/OpenSSH without having to deal with > the pitfalls of libdescrypt. It seems to work fine for me..if I hear any > other positive feedback I'll commit it. As for me, not only I don't mind having libdescrypt but I also want it compiled. I just object to it replacing my libcrypt links to libscrypt. I know ppl can be picky, yet I would rather have the best of both worlds: libscrypt for authentication and des around for compiling some progs. Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 20:52:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id BDEE737B54B for ; Sat, 26 Feb 2000 20:52:15 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.79]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FQK0071AO4779@mta3.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 26 Feb 2000 20:50:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id B0BC09156A; Sat, 26 Feb 2000 20:50:31 -0800 (PST) Date: Sat, 26 Feb 2000 20:50:31 -0800 (PST) From: Alex Zepeda Subject: Re: kdelibs port broken? In-reply-to: <20000225195718.A17742@shadow.blackdawn.com> To: Will Andrews Cc: Joel Ray Holveck , bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, Daniel O'Connor Message-id: 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, 25 Feb 2000, Will Andrews wrote: > If you're gonna use a port, use ports for its dependencies too. You'd be > stupid not to use the ports whenever you can. No one has ever provided > me a convincing reason why this is not true. Well when you want to keep multiple versions of kde or qt around.. and want to be able to remove them in one fell swoop.. and the "packing lists" aren't for sure known.. yes it helps to have its own directory. For a normal desktop user you're perhaps right. But not using the ports for some things does not make one stupid, as quite possibly there's a good reason behind it. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 21:21:44 2000 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 EFDB237B550 for ; Sat, 26 Feb 2000 21:21:38 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA84052; Sun, 27 Feb 2000 00:20:32 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 27 Feb 2000 00:20:30 -0500 (EST) From: Chuck Robey To: Alex Zepeda Cc: Will Andrews , Joel Ray Holveck , bwoods2@uswest.net, Maxim Sobolev , freebsd-current@FreeBSD.ORG, "Daniel O'Connor" Subject: Re: kdelibs port broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Feb 2000, Alex Zepeda wrote: > On Fri, 25 Feb 2000, Will Andrews wrote: > > > If you're gonna use a port, use ports for its dependencies too. You'd be > > stupid not to use the ports whenever you can. No one has ever provided > > me a convincing reason why this is not true. > > Well when you want to keep multiple versions of kde or qt around.. and > want to be able to remove them in one fell swoop.. and the "packing > lists" aren't for sure known.. yes it helps to have its own directory. > > For a normal desktop user you're perhaps right. But not using the ports > for some things does not make one stupid, as quite possibly there's a good > reason behind it. Also, for several ports, our ports break build compatibility with any other package of that type. I'm not sure if that's clear ... tcl is a fine example, tho. We break the location of the config files that all tcl packages rely upon to build, for the purpose of allowing folks to run multiple versions simultaneously. Tcl isn't the only one like that, either. Anyone who wants to be able to build other tcl software that isn't derived from a port would be well advised to avoid using our port. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 21:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 5913B37B5BD; Sat, 26 Feb 2000 21:49:09 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id AAA27609; Sun, 27 Feb 2000 00:49:06 -0500 (EST) Message-ID: <38B8BAC5.9927A56E@acm.org> Date: Sun, 27 Feb 2000 00:48:53 -0500 From: Jim Bloom X-Mailer: Mozilla 4.7 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-ipfw@freebsd.org Subject: cpp change breaks ipfw Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using cpp on my firewall to expand my local firewall rules and fill in the local address and subnetmask. This makes things easier my ISP decides to change my IP address using DHCP. My firewall is running an approximately one year old version of current and I'm trying to upgrade it to a recent version. I am running ipfw as "ipfw -p /usr/bin/cpp -Daddr=value1 -Dmask=value2 file". My firewall rules have been using constructs similar to the following if put in a file. #define addr 192.168.2.5 #define mask 255.255.254.0 add pass tcp from addr:mask to any 25 setup On the old version of current this expands to add pass tcp from 192.168.2.5:255.255.254.0 to any 25 setup but on a new version of current this expands to add pass tcp from 192.168.2.5 : 255.255.254.0 to any 25 setup Note the extra spaces around the colon. Unfortunately, this breaks ipfw which interprets the colon where it expects the "to". There are several options here: 1) Fix cpp to not emit the extra spaces 2) Fix ipfw to handle addresses being multiple arguments 3) Document the cpp is not a valid preprocessor for ipfw on the manual page. Option 1 seems like it might be a little difficult. Option 2 looks to be reasonably simple to implement after reading the code. Option 3 is the easiest, but I believe it is the wrong way to handle the problem. I can submit patches for 2 or 3 reasonably quickly. I have no idea about fixing cpp. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 22:36:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 877ED37B562 for ; Sat, 26 Feb 2000 22:36:18 -0800 (PST) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id BAA00258 for freebsd-current@freebsd.org; Sun, 27 Feb 2000 01:36:13 -0500 (EST) (envelope-from ray) Date: Sun, 27 Feb 2000 01:36:13 -0500 (EST) From: Ray Message-Id: <200002270636.BAA00258@rjk191.rh.psu.edu> To: freebsd-current@freebsd.org Subject: success with buildworld Reply-To: rjk191@psu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From ray Sun Feb 27 01:34:25 2000 Return-Path: Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id BAA00249 for freebsd-current; Sun, 27 Feb 2000 01:34:25 -0500 (EST) (envelope-from ray) Date: Sun, 27 Feb 2000 01:34:25 -0500 (EST) From: Ray Message-Id: <200002270634.BAA00249@rjk191.rh.psu.edu> To: freebsd-current Subject: success with building world Reply-To: rjk191@psu.edu Just thought I'd let everyone (and especially mark) know that there's another report of success of building after all the new commits with openssl and ssh and the like. Kudos to you all. Ray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 23: 4:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D851F37B513; Sat, 26 Feb 2000 23:04:54 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA26178; Sat, 26 Feb 2000 23:04:54 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 26 Feb 2000 23:04:54 -0800 (PST) From: Kris Kennaway To: Johan=?us-ascii?Q?_M=E5rtensson?= Cc: current@FreeBSD.ORG Subject: Re: Linux-Netscape-communicator47-Port - problem In-Reply-To: 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 In general, ports questions should go to freebsd-ports and/or the port's maintainer. On Sun, 27 Feb 2000, Johan M=E5rtensson wrote: > I tried installing the linux-netscape-47-communicator port, during the do= wnload > it kept printing the download message and the % constantly. This is because the status line is longer than 80 characters, so it causes a screen scroll each time. > And then when the download was finished (from ftp.netscape.com) it > started over again, deleting the file and downloading it anew from > ftp.sunet.se (closer site for me). Are you sure? I havent seen this. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 23:20:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id D0E9B37B5AD for ; Sat, 26 Feb 2000 23:20:12 -0800 (PST) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id SAA15144 for ; Sun, 27 Feb 2000 18:05:05 +1100 (EDT) Received: (qmail 1147 invoked by uid 1000); 27 Feb 2000 07:05:05 -0000 From: "Andrew Reilly" Date: Sun, 27 Feb 2000 18:05:05 +1100 To: Jim Bloom Cc: freebsd-current@FreeBSD.ORG, freebsd-ipfw@FreeBSD.ORG Subject: Re: cpp change breaks ipfw Message-ID: <20000227180504.A255@gurney.reilly.home> References: <38B8BAC5.9927A56E@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38B8BAC5.9927A56E@acm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 27, 2000 at 12:48:53AM -0500, Jim Bloom wrote: > I have been using cpp on my firewall to expand my local firewall rules and fill > in the local address and subnetmask. This makes things easier my ISP decides to > change my IP address using DHCP. My firewall is running an approximately one > year old version of current and I'm trying to upgrade it to a recent version. Probably not the answer you're looking for, but another approach to consider: I worked around this problem by having the dhclient-exit-hooks script edit the new address into /etc/hosts, and ipfw uses the symbolic name for the rule. Works quite nicely, but then I don't have any rules that rely on the DHCP-supplied netmask. And here's a picture: if [ x$new_ip_address != x ]; then cp /etc/hosts /tmp/hosts-foo sed -e /gurney-/d /tmp/hosts-foo >/etc/hosts echo "$new_ip_address gurney-gw.reilly.home gurney-gw" >>/etc/hosts echo "$new_routers gurney-router.reilly.home gurney-router" >>/etc/hosts echo "$new_domain_name_servers gurney-ns.reilly.home gurney-ns" >>/etc/ hosts rm /tmp/hosts-foo fi I dare say that this would work less well if you were using a local DNS. Maybe m4 (instead of cpp) is the right way to do it? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 23:28:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by hub.freebsd.org (Postfix) with ESMTP id BD70B37B5EC; Sat, 26 Feb 2000 23:28:26 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-02-150.nv.iinet.net.au [203.59.91.150]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id PAA32228; Sun, 27 Feb 2000 15:28:52 +0800 Message-ID: <38B8D0DE.167EB0E7@elischer.org> Date: Sat, 26 Feb 2000 23:23:10 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: fs@freebsd.org Cc: current@freebsd.org Subject: UDF/DVD support Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been hired to add UDF/DVD-R support to FreeBSD I will be spending the next few weeks basically doing research but would like to hear from anyone who is already working in these areas. This may impact un the following areas: SCSI subsystem ATA subsystem Filesystems Raw/Block(sic) device interface Encryption/security stuff. Julian -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 26 23:40:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (nld-dial-196-7-202-127.mweb.co.za [196.7.202.127]) by hub.freebsd.org (Postfix) with ESMTP id C87B337B554; Sat, 26 Feb 2000 23:39:55 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA00938; Sun, 27 Feb 2000 09:41:19 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200002270741.JAA00938@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: markm@freebsd.org, peter@freebsd.org, green@freebsd.org, current@freebsd.org Subject: Re: [PATCH] Fix login.conf, expiration, BSD compatibility in OpenSSH References: <20000227030149.A6864@nagual.pp.ru> In-Reply-To: <20000227030149.A6864@nagual.pp.ru> ; from "Andrey A. Chernov" "Sun, 27 Feb 2000 03:01:49 +0300." Date: Sun, 27 Feb 2000 09:41:19 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This patch revive almost all login.conf and password/account expiration > features, makes OpenSSH more FreeBSD login compatible and fix non-critical > memory leak. Cool! Thank you! > Please review and commit. Will do... 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