From owner-freebsd-hackers Sun Dec 29 0:10:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6825037B401; Sun, 29 Dec 2002 00:10:13 -0800 (PST) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B0E743EC2; Sun, 29 Dec 2002 00:10:12 -0800 (PST) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.6/8.12.6) with ESMTP id gBT89OQB072890; Sun, 29 Dec 2002 08:09:24 GMT (envelope-from mark@grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.6/8.12.6/Submit) with UUCP id gBT89O7a072889; Sun, 29 Dec 2002 08:09:24 GMT Received: from grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.6/8.12.6) with ESMTP id gBT89QXb010011; Sun, 29 Dec 2002 10:09:26 +0200 (SAST) (envelope-from mark@grondar.org) Message-Id: <200212290809.gBT89QXb010011@grimreaper.grondar.org> To: phk@FreeBSD.ORG Cc: kientzle@acm.org, freebsd-hackers@FreeBSD.ORG Subject: Re: Can dhclient rely on /dev/random? In-Reply-To: Your message of "Sat, 28 Dec 2002 22:19:43 +0100." <6360.1041110383@critter.freebsd.dk> Date: Sun, 29 Dec 2002 10:09:26 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >Policy Question: is a fast, high-quality > >/dev/random a gauranteed feature starting with 5.0? > > yes. More like "Yes, effectively". It is a module, and its conceivable under the right (Wrong?) circumstances that this module is not loaded. This would not be the default case, and it breaks Much(tm) if you don't include it. The kernel-building individual would have had to have made a decision to not include the RNG, and as such is assumed to know what she is doing. M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 0:22: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F61137B401 for ; Sun, 29 Dec 2002 00:22:05 -0800 (PST) Received: from patrocles.silby.com (d155.as14.nwbl0.wi.voyager.net [169.207.136.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 869E143EB2 for ; Sun, 29 Dec 2002 00:22:03 -0800 (PST) (envelope-from silby@silby.com) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.6/8.12.6) with ESMTP id gBT8T38U014101; Sun, 29 Dec 2002 02:29:03 -0600 (CST) (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.6/8.12.6/Submit) with ESMTP id gBT8T1db014098; Sun, 29 Dec 2002 02:29:02 -0600 (CST) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 29 Dec 2002 02:29:00 -0600 (CST) From: Mike Silbersack To: Tim Kientzle Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can dhclient rely on /dev/random? In-Reply-To: <3E0E1879.6090801@acm.org> Message-ID: <20021229022705.L12856-100000@patrocles.silby.com> References: <3E0E02F3.6030205@acm.org> <20021228150348.Y10588-100000@patrocles.silby.com> <3E0E1879.6090801@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 28 Dec 2002, Tim Kientzle wrote: > I've clocked /dev/random on -current at > just about 10MB/s (on a 1GHz AMD Duron). That's > plenty fast enough for generating session keys. ;-) Sounds like it, I didn't realize it was that fast. :) > If this code is just used for generating occasional > keys, 4.x's /dev/random may well suffice. As I > dig deeper, though, I'm starting to suspect that > this code isn't actually used by dhclient at all. > That would suggest a much simpler fix... ;-) > > Tim Warning! Warning! Under 4.x, you probably want to use /dev/urandom. The reason for this is that /dev/random is only guaranteed to give you values when it can guarantee that you're getting "good" randomness. And as 4.x doesn't harvest many entropy sources by default, there's little "good" randomness, and you'll get nothing! /dev/urandom's "bad" randomness is certainly better than no randomness at all. :) Of course, if dhclient doesn't need any randomness, then I guess you don't have to worry. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 0:50: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D29C537B401 for ; Sun, 29 Dec 2002 00:50:02 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 507EB43EC2 for ; Sun, 29 Dec 2002 00:49:52 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0164.cvx21-bradley.dialup.earthlink.net ([209.179.192.164] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18SZ8c-0000xS-00; Sun, 29 Dec 2002 00:49:38 -0800 Message-ID: <3E0EB6CF.6D1BFAD6@mindspring.com> Date: Sun, 29 Dec 2002 00:48:15 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kientzle@acm.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can dhclient rely on /dev/random? References: <3E0E02F3.6030205@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f5e67a32691c30a23b734f0eb3213fd8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tim Kientzle wrote: > The obvious fix would alter dhclient to rely only > on /dev/random for entropy. (It seems this code is > common to bind as well.) The "obvious fix", I think, is to just use the boot time as the start for the exponential backoff. The only place this might be a problem is in a big installation where a lot of machines come on at the same time. That's probably going to melt your building's wiring, anyway. 8-). > Technical Question: is /dev/random sufficient > for the cryptographic requirements of programs > like dhclient, bind, etc? Uh, what "cryptographic requirements" of dhclient? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 1:54: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 550D637B401 for ; Sun, 29 Dec 2002 01:54:06 -0800 (PST) Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA19243E4A for ; Sun, 29 Dec 2002 01:54:05 -0800 (PST) (envelope-from jkh@apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id gBT9s5I28827 for ; Sun, 29 Dec 2002 01:54:05 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Sun, 29 Dec 2002 01:53:38 -0800 Received: from apple.com (vpn-scv-x1-37.apple.com [17.219.193.37]) by scv3.apple.com (8.11.3/8.11.3) with ESMTP id gBT9s4f03332 for ; Sun, 29 Dec 2002 01:54:05 -0800 (PST) Date: Sun, 29 Dec 2002 01:54:15 -0800 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Anyone like obscure stdio problems? From: Jordan Hubbard To: FreeBSD Hackers Content-Transfer-Encoding: 7bit Message-Id: <7D91340A-1B13-11D7-A2B1-000393BB9222@apple.com> X-Mailer: Apple Mail (2.551) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have no problem admitting that I've traced through the innards of _fseeko a few times now and am no closer to finding out exactly where the problem is, though I have a suspicion it has to do with when the file pointer's buffer is allocated and initially populated. In any case, here's a particularly weird one from the Apple Files that also occurs on FreeBSD The following program, also available from http://narcissus.queasyweasel.com/fump.c, demonstrates the problem. If you change the top #define of FIRST_SEEK to 0 instead of 1, the program will work. If you leave it at 1, the initial (and theoretically redundant and no-op) fseek on readMidFP will bugger up stdio's internal state somehow. If anyone with more stdio-fu than me would like to poke at it, I'd be interested in hearing what you find out. If this is breaking some undocumented rule of stdio I'd like to know that too so that I can document it both in FreeBSD and Mac OS X. Thanks. - Jordan #include #define SIZE 40 #define NBS 5 #define FIRST_SEEK 1 int main( void ) { FILE *writeFP ; FILE *readMidFP ; int err , i , n = 0 , count , SizeOfFile , nerr = 0 ; char ch ; writeFP = fopen( "test_fseek_outfile" , "w" ) ; if ( writeFP == NULL ) { fprintf( stderr , "open for write failed.\n" ) ; exit( 1 ) ; } readMidFP = fopen( "test_fseek_outfile" , "r" ) ; if ( readMidFP == NULL ) { fprintf( stderr , "open readMidFP for read failed.\n" ) ; exit( 1 ) ; } /* write SIZE a's to output file. */ SizeOfFile = SIZE ; for ( count = 0 ; ( count <= SizeOfFile ) && ( n != -1 ) ; count++ ) { n = fprintf( writeFP , "a" ) ; if ( n == -1 ) break ; } fflush( writeFP ) ; /* seek to middle of file. */ // THIS IS CRUCIAL TO MAKING IT FAIL // REMOVE THIS fseek() AND THE PROGRAM SUCCEEDS #if FIRST_SEEK err = fseek( readMidFP , (long) (SizeOfFile / 2) , SEEK_SET ) ; if ( err != 0 ) { fprintf( stderr , "first fseek() to middle of file on readMidFP failed.\n" ) ; exit( 1 ) ; } #endif /* seek to middle of file. */ err = fseek( writeFP , (long) (SizeOfFile / 2) , SEEK_SET ) ; if ( err != 0 ) { fprintf( stderr , "first fseek() to middle of file on writeFP failed.\n" ) ; exit( 1 ) ; } /* write NBS b's. */ for ( i = 0 ; i < NBS ; i++ ) fprintf( writeFP , "b" ) ; fflush( writeFP ) ; /* seek to middle of file. should be NBS b's there. */ err = fseek( readMidFP , (long) (SizeOfFile / 2) , SEEK_SET ) ; if ( err != 0 ) { fprintf( stderr , "second fseek() to middle of file on readMidFP failed.\n" ) ; exit( 1 ) ; } for ( i = 0 ; i < NBS ; i++ ) { fscanf( readMidFP , "%c" , &ch ) ; if ( ch != 'b' ) { fprintf( stderr , "** ERROR ** \'%c\' at position: %d\n" , ch , (SizeOfFile / 2)+i ) ; nerr++ ; } } if ( nerr == 0 ) fprintf( stderr , "Program was succesful.\n" ) ; else fprintf( stderr , "Program failed.\n" ) ; return( 0 ) ; } -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 2:32:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D58A337B401 for ; Sun, 29 Dec 2002 02:32:46 -0800 (PST) Received: from holly.dyndns.org (adsl-208-191-149-232.dsl.hstntx.swbell.net [208.191.149.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E2443E4A for ; Sun, 29 Dec 2002 02:32:45 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.12.6/8.11.6) id gBTAWt5k051974; Sun, 29 Dec 2002 04:32:55 -0600 (CST) (envelope-from chris) Date: Sun, 29 Dec 2002 04:32:54 -0600 From: Chris Costello To: Jordan Hubbard Cc: FreeBSD Hackers Subject: Re: Anyone like obscure stdio problems? Message-ID: <20021229103254.GB48772@holly.machined.net> Reply-To: chris@FreeBSD.ORG References: <7D91340A-1B13-11D7-A2B1-000393BB9222@apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7D91340A-1B13-11D7-A2B1-000393BB9222@apple.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, December 29, 2002, Jordan Hubbard wrote: > I have no problem admitting that I've traced through the innards of > _fseeko a few times now and am no closer to finding out exactly where > the problem is, though I have a suspicion it has to do with when the > file pointer's buffer is allocated and initially populated. In any > case, here's a particularly weird one from the Apple Files that also > occurs on FreeBSD > > The following program, also available from > http://narcissus.queasyweasel.com/fump.c, demonstrates the problem. > > If you change the top #define of FIRST_SEEK to 0 instead of 1, the > program will work. If you leave it at 1, the initial (and > theoretically redundant and no-op) fseek on readMidFP will bugger up > stdio's internal state somehow. > > If anyone with more stdio-fu than me would like to poke at it, I'd be > interested in hearing what you find out. If this is breaking some > undocumented rule of stdio I'd like to know that too so that I can > document it both in FreeBSD and Mac OS X. Thanks. As we discussed on IRC, the problem lies in line 254 of libc/stdio/fseek.c. Since in your case the buffer is not modified (no __SMOD flag, see a few lines back in fseek.c), it assumes that the buffer that it filled after the first fseek but before the write is still OK, and simply copies out from it when you read it looking for your B's. Placing a pointless fgetln() after the first fseek() will make this obvious: if (fseek(rp, (long)(i / 2), SEEK_SET) != 0) err(1, "fseek on rp"); (void)fgetln(rp, throwaway); fgetln() will set __SMOD for rp's buffer and so stdio is forced to discard it and refill it from the file (which contains the B's). -- Chris Costello FreeBSD Project http://www.FreeBSD.org/ TrustedBSD Project http://www.TrustedBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 6:15:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F81137B401 for ; Sun, 29 Dec 2002 06:15:45 -0800 (PST) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id A523543EB2 for ; Sun, 29 Dec 2002 06:15:44 -0800 (PST) (envelope-from hiten@unixdaemons.com) Received: from unixdaemons.com (pc3-nfds1-5-cust242.nott-b.cable.ntl.com [80.5.196.242]) (authenticated bits=0) by angelica.unixdaemons.com (8.12.6/8.12.1) with ESMTP id gBTEFKsB056266; Sun, 29 Dec 2002 09:15:26 -0500 (EST) Message-ID: <3E0F032F.7020702@unixdaemons.com> Date: Sun, 29 Dec 2002 14:14:07 +0000 From: Hiten Pandya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Pedro F. Giffuni" , Emiel Kollof , Mayuresh Kathe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Framebuffer howto? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- "Pedro F. Giffuni" wrote: > Actually I suggested on private email to use GGI. GGI > can work on top of VGL or Linux's framebuffer, and > when KGI becomes available it will work fine. Hmm, someone said earlier on in this thread, that FreeBSD does not have a framebuffer device; if so: 1) What is the FB_INSTALL_CDEV kernel option for? 2) What is the purpose of ? Clarification will be appreciated. Cheers. -- Hiten Pandya http://www.unixdaemons.com/~hiten/ hiten@unixdaemons.com, hiten@uk.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 7:34: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4221D37B401 for ; Sun, 29 Dec 2002 07:34:07 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id F263143EA9 for ; Sun, 29 Dec 2002 07:34:05 -0800 (PST) (envelope-from mdcki@gmx.net) Received: (qmail 31664 invoked by uid 0); 29 Dec 2002 15:34:04 -0000 Received: from cvpn017.gwdg.de (HELO gmx.net) (134.76.22.17) by mail.gmx.net (mp005-rz3) with SMTP; 29 Dec 2002 15:34:04 -0000 Message-ID: <3E0F15ED.9070301@gmx.net> Date: Sun, 29 Dec 2002 16:34:05 +0100 From: Marcin Dalecki User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hiten Pandya Cc: "Pedro F. Giffuni" , Emiel Kollof , Mayuresh Kathe , freebsd-hackers@FreeBSD.ORG Subject: Re: Framebuffer howto? References: <3E0F032F.7020702@unixdaemons.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > --- "Pedro F. Giffuni" wrote: > > Actually I suggested on private email to use GGI. GGI > > can work on top of VGL or Linux's framebuffer, and > > when KGI becomes available it will work fine. > > Hmm, someone said earlier on in this thread, that FreeBSD does not have > a framebuffer device; if so: > > 1) What is the FB_INSTALL_CDEV kernel option for? > 2) What is the purpose of ? > > Clarification will be appreciated. > Cheers. Well as far as I can see the text console is considered as kind of a frame buffer. Surely not what quite what you are looking for. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 8:54:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBA3837B401 for ; Sun, 29 Dec 2002 08:54:46 -0800 (PST) Received: from web13405.mail.yahoo.com (web13405.mail.yahoo.com [216.136.175.63]) by mx1.FreeBSD.org (Postfix) with SMTP id 47EEF43ED8 for ; Sun, 29 Dec 2002 08:54:46 -0800 (PST) (envelope-from giffunip@yahoo.com) Message-ID: <20021229165446.85897.qmail@web13405.mail.yahoo.com> Received: from [200.24.79.213] by web13405.mail.yahoo.com via HTTP; Sun, 29 Dec 2002 17:54:46 CET Date: Sun, 29 Dec 2002 17:54:46 +0100 (CET) From: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" Subject: Re: Framebuffer howto? To: Hiten Pandya Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <3E0F032F.7020702@unixdaemons.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Hiten Pandya ha scritto: ... > > Clarification will be appreciated. I understand the Linux framebuffer device was initially based on our VESA driver, but it has evolved into a specialized device for specific graphic cards. It's also a moving target, not something anyone in FreeBSD has been willing to follow. There are more important things to do in FreeBSD's graphics end; fully newbussifying the VESA driver would be nice, perhaps supporting VBE/AF (like in this dead project (http://www.talula.demon.co.uk/freebe/index.html), or of course helping the KGI porting effort* (Hi Nicholas ;) ). cheers, Pedro. * I understand a VM guru is needed there BTW ______________________________________________________________________ Yahoo! Cellulari: scarica i loghi e le suonerie per le tue feste! http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 13:25:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6702137B401 for ; Sun, 29 Dec 2002 13:25:33 -0800 (PST) Received: from clover.kientzle.com (user-112uh9a.biz.mindspring.com [66.47.69.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F38B43EB2 for ; Sun, 29 Dec 2002 13:25:32 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org (c43 [66.47.69.43]) by clover.kientzle.com (8.11.3/8.11.3) with ESMTP id gBTLPUE22281; Sun, 29 Dec 2002 13:25:30 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3E0F6849.5060904@acm.org> Date: Sun, 29 Dec 2002 13:25:29 -0800 From: Tim Kientzle Reply-To: kientzle@acm.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can dhclient rely on /dev/random? References: <3E0E02F3.6030205@acm.org> <3E0EB6CF.6D1BFAD6@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Uh, what "cryptographic requirements" of dhclient? I'm not really sure. ;-) The dhclient source has a 'dst' directory with source for an HMAC/MD5 digest authentication toolkit. I haven't figured out exactly what it's used for, though. (Dynamic DNS updates for secure BIND? Some form of authenticated DHCP?) Maybe someone else around here knows. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 21:35:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60B7C37B401 for ; Sun, 29 Dec 2002 21:35:58 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D444C43EB2 for ; Sun, 29 Dec 2002 21:35:57 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gBU5Zw1Z094401; Mon, 30 Dec 2002 00:35:58 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 30 Dec 2002 00:35:58 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: joe mcguckin Cc: freebsd-hackers@freebsd.org Subject: Re: NFS & ACLS's ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 27 Dec 2002, joe mcguckin wrote: > Are there any strange interactions between NFS and filesystems that are > not UFS? E.g. UFS2? Does NFS support new features that these fs's may > implement? NFS can represent many but not all of the services found in UFS1 and UFS2. Among things it doesn't support are the retrieval and manipulation of BSD file user flags, system flags, extended attributes, and access control lists (ACLs). However, NFSv3 does correctly handle enforcement with these features because clients rely on the server to evaluate protections on file system objects using an ACCESS RPC. NFS2 evaluates protections on the client (if I recall correctly) so may not behave properly. There are RPC extensions to NFSv3 to retrieve and manipulate ACLs on Solaris, IRIX, et al, but we don't currently implement those extensions. Likewise, NFSv4 supports ACL management, but we don't yet implement NFSv4. It shouldn't be too hard to dig up information on the NFSv3 ACL RPC extensions and implement them on FreeBSD 5, since the semantics of our ACLs are highly compatible with Solaris and IRIX. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 22:22:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7292737B401 for ; Sun, 29 Dec 2002 22:22:23 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02F1943E4A for ; Sun, 29 Dec 2002 22:22:23 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0067.cvx22-bradley.dialup.earthlink.net ([209.179.198.67] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18StJd-0005R8-00 for hackers@freebsd.org; Sun, 29 Dec 2002 22:22:22 -0800 Message-ID: <3E0FE5D0.A77F56B6@mindspring.com> Date: Sun, 29 Dec 2002 22:21:04 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: [FAQ] The Open Source Stackable PC BIOS (fwd)] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40341897032c1397a7645eb1f88fbe8ad387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Forwarded, per request of the author. Original email address on file. -- Terry Bruce M Simpson wrote: > > Terry, > > On Fri, Dec 13, 2002 at 08:04:12AM -0800, Terry Lambert wrote: > > "Ronald G. Minnich" wrote: > > > On Thu, 12 Dec 2002, Terry Lambert wrote: > > > > > > > I guess it's not OK to make BIOS calls into the BIOS? > > > > > > not if it's my lazy bios that doesn't support them. > > > > Actually, the interesting part would be a survey of which BIOS > > calls are actually used (a survey by a BIOS writer, maybe, hint > > hint 8-)). > > > > The real question is fail-safe on unimplemented BIOS calls, > > which should return a characteristic error. > > I have done this work. The results can be seen at: > > http://www.incunabulum.com/code/projects/freebsd/freebsd-bios-interaction.txt > > I have also rewritten boot0.s to use the BIOS COM Port Services (INT 14h): > > http://www.incunabulum.com/code/projects/freebsd/boot0sio.s > > Comments, suggestions, flames etc. to the usual address. > > P.S. The PTRs for this machine may be FUBAR, so if you could repost to > hackers@ I should be most grateful. > > yours, > BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 29 22:32: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F3DB37B401; Sun, 29 Dec 2002 22:32:05 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FB0443EC2; Sun, 29 Dec 2002 22:32:05 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0067.cvx22-bradley.dialup.earthlink.net ([209.179.198.67] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18StT1-0006AL-00; Sun, 29 Dec 2002 22:32:04 -0800 Message-ID: <3E0FE815.653A4844@mindspring.com> Date: Sun, 29 Dec 2002 22:30:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson Cc: joe mcguckin , freebsd-hackers@freebsd.org Subject: Re: NFS & ACLS's ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40341897032c1397ac7a5c7c1b58887e8387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Robert Watson wrote: > On Fri, 27 Dec 2002, joe mcguckin wrote: > > Are there any strange interactions between NFS and filesystems that are > > not UFS? E.g. UFS2? Does NFS support new features that these fs's may > > implement? > > NFS can represent many but not all of the services found in UFS1 and UFS2. > Among things it doesn't support are the retrieval and manipulation of BSD > file user flags, system flags, extended attributes, and access control > lists (ACLs). However, NFSv3 does correctly handle enforcement with these > features because clients rely on the server to evaluate protections on > file system objects using an ACCESS RPC. Participation in the enforcement protocol is, unfortunately, voluntary, however. 8-(. > NFS2 evaluates protections on > the client (if I recall correctly) so may not behave properly. s/may not/will not/ > There are > RPC extensions to NFSv3 to retrieve and manipulate ACLs on Solaris, IRIX, > et al, but we don't currently implement those extensions. Last I tried, they were not implemented identically on the various platforms, so I scrapped the idea as being bogus. Without a standard, code is useless. > Likewise, NFSv4 > supports ACL management, but we don't yet implement NFSv4. It shouldn't > be too hard to dig up information on the NFSv3 ACL RPC extensions and > implement them on FreeBSD 5, since the semantics of our ACLs are highly > compatible with Solaris and IRIX. They aren't identical, unforntunately. You can get close by passing one at a time, but it's not really worth it to do local enforcement. I'm actually not a fan of NFSv4. The biggest NFS problems that exist are timesync and locking, and it doesn't solve either one of those very well. I suggested to the RFC authors several times at the draft stage that they include a local timestamp on all operations, which would have eliminated the timesync problem (all times could be represented in responses as deltas from the system time minus the timesync). The only real project to implement, outside of commercial vendors, appears to be a university project on Linux, which from my reckoning is not going well (I greatly admire the CS department attempting the work, so I don't know why that's the case...). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 2:43:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACDFE37B401; Mon, 30 Dec 2002 02:43:44 -0800 (PST) Received: from phoenix.infradead.org (carisma.slowglass.com [195.224.96.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED89943ED1; Mon, 30 Dec 2002 02:43:27 -0800 (PST) (envelope-from hch@infradead.org) Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18SxNr-0006ZS-00; Mon, 30 Dec 2002 10:42:59 +0000 Date: Mon, 30 Dec 2002 10:42:59 +0000 From: Christoph Hellwig To: Robert Watson Cc: joe mcguckin , freebsd-hackers@freebsd.org Subject: Re: NFS & ACLS's ? Message-ID: <20021230104259.A25035@infradead.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@freebsd.org on Mon, Dec 30, 2002 at 12:35:58AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 30, 2002 at 12:35:58AM -0500, Robert Watson wrote: > supports ACL management, but we don't yet implement NFSv4. It shouldn't > be too hard to dig up information on the NFSv3 ACL RPC extensions and > implement them on FreeBSD 5, since the semantics of our ACLs are highly > compatible with Solaris and IRIX. The IRIX code implementing extended attributes over nfs can be found at http://oss.sgi.com/projects/ob1/src/nfs/kern/.. (GPLed, so only useful as reference for FreeBSD). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 3:46:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BFAE37B401 for ; Mon, 30 Dec 2002 03:46:45 -0800 (PST) Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by mx1.FreeBSD.org (Postfix) with SMTP id 2479F43ED4 for ; Mon, 30 Dec 2002 03:46:44 -0800 (PST) (envelope-from bra@fsn.hu) Received: (qmail 28317 invoked by uid 1000); 30 Dec 2002 11:46:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Dec 2002 11:46:43 -0000 Date: Mon, 30 Dec 2002 12:46:43 +0100 (CET) From: Attila Nagy To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: FEC on 5.x In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, > you should post to -current for 5.x Oops, sorry, subscribed to that list too :) ----------[ Free Software ISOs - http://www.fsn.hu/?f=download ]---------- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 7:48:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 825CE37B401 for ; Mon, 30 Dec 2002 07:48:08 -0800 (PST) Received: from shaft.noc.clara.net (shaft.noc.clara.net [195.8.70.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8B5743EA9 for ; Mon, 30 Dec 2002 07:48:07 -0800 (PST) (envelope-from mivens@clara.net) Received: by shaft.noc.clara.net (Postfix, from userid 100) id 6AA9F46D6; Mon, 30 Dec 2002 15:47:56 +0000 (GMT) Date: Mon, 30 Dec 2002 15:47:56 +0000 From: Mark Ivens To: freebsd-hackers@freebsd.org Subject: deadlock: procs stuck in vmpfw Message-ID: <20021230154756.GD26089@uk.clara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-NCC-RegID: uk.claranet Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On one of our 4.3-STABLE boxen running apache, we're seeing apache processes getting stuck in disk wait, wait channel vmpfw. Only way out is to reboot. The box is a NFS client with a jail, including the apache documentroot mounted on a Network Appliance. I've got a stack backtrace of several of the stuck proccesses from the live kernel, although I didn't force a coredump. A couple copied below: (kgdb) proc 21846 (kgdb) bt #0 mi_switch () at ../../kern/kern_synch.c:858 #1 0xc0153e6d in tsleep (ident=0xc12d5ee0, priority=4, wmesg=0xc022d8cc "vmpfw", timo=0) at ../../kern/kern_synch.c:467 #2 0xc01d1152 in vm_fault (map=0xea69bd80, vaddr=674340864, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_page.h:569 #3 0xc01fda4e in trap_pfault (frame=0xea7f8db0, usermode=0, eva=674340862) at ../../i386/i386/trap.c:824 #4 0xc01fd69f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = -550698992, tf_edi = -1037885128, tf_esi = 674340862, tf_ebp = -360739300, tf_isp = -360739364, tf_ebx = 2048, tf_edx = 674342598, tf_ecx = 434, tf_eax = -360747008, tf_trapno = 12, tf_err = 0, tf_eip = -1071658167, tf_cs = 8, tf_eflags = 66054, tf_esp = -360739060, tf_ss = -360739116}) at ../../i386/i386/trap.c:443 #5 0xc01fcb49 in generic_copyin () #6 0xc016e518 in sosend (so=0xdf2df000, addr=0x0, uio=0xea7f8f0c, top=0x0, control=0x0, flags=0, p=0xea76ad80) at ../../kern/uipc_socket.c:585 #7 0xc01626b8 in soo_write (fp=0xc419a900, uio=0xea7f8f0c, cred=0xc405db80, flags=0, p=0xea76ad80) at ../../kern/sys_socket.c:81 #8 0xc015f420 in writev (p=0xea76ad80, uap=0xea7f8f80) at ../../sys/file.h:162 #9 0xc01fe08d in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = -1078001617, tf_edi = 0, tf_esi = 2, tf_ebp = -1077938516, tf_isp = -360738860, tf_ebx = 674183052, tf_edx = 0, tf_ecx = 32768, tf_eax = 121, tf_trapno = 12, tf_err = 2, tf_eip = 672109608, tf_cs = 31, tf_eflags = 663, tf_esp = -1077938560, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #10 0xc01f2e85 in Xint0x80_syscall () (kgdb) proc 26316 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:858 #1 0xc0153e6d in tsleep (ident=0xc08822e0, priority=4, wmesg=0xc022d8cc "vmpfw", timo=0) at ../../kern/kern_synch.c:467 #2 0xc01d1152 in vm_fault (map=0xea69df40, vaddr=674336768, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_page.h:569 #3 0xc01fda4e in trap_pfault (frame=0xe53bddb0, usermode=0, eva=674340862) at ../../i386/i386/trap.c:824 #4 0xc01fd69f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = -550567920, tf_edi = -1041225416, tf_esi = 674340862, tf_ebp = -449061348, tf_isp = -449061412, tf_ebx = 2048, tf_edx = 674342598, tf_ecx = 434, tf_eax = -449069056, tf_trapno = 12, tf_err = 0, tf_eip = -1071658167, tf_cs = 8, tf_eflags = 66054, tf_esp = -449061108, tf_ss = -449061164}) at ../../i386/i386/trap.c:443 #5 0xc01fcb49 in generic_copyin () #6 0xc016e518 in sosend (so=0xdf2f4c00, addr=0x0, uio=0xe53bdf0c, top=0x0, control=0x0, flags=0, p=0xe53a82a0) at ../../kern/uipc_socket.c:585 #7 0xc01626b8 in soo_write (fp=0xc4028440, uio=0xe53bdf0c, cred=0xc45f1e00, flags=0, p=0xe53a82a0) at ../../kern/sys_socket.c:81 #8 0xc015f420 in writev (p=0xe53a82a0, uap=0xe53bdf80) at ../../sys/file.h:162 #9 0xc01fe08d in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = -1078001617, tf_edi = 0, tf_esi = 2, tf_ebp = -1077938516, tf_isp = -449060908, tf_ebx = 674183052, tf_edx = 0, tf_ecx = 32768, tf_eax = 121, tf_trapno = 7, tf_err = 2, tf_eip = 672109608, tf_cs = 31, tf_eflags = 663, tf_esp = -1077938560, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #10 0xc01f2e85 in Xint0x80_syscall () USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND claranet 26316 0.0 0.3 4148 2636 ?? DL 1:43PM 0:10.68 /usr/local/sbin/ 5000 26316 98582 1 -18 0 4148 2636 vmpfw DL ?? 0:10.68 /usr/local/sbin/httpd -DMOD_FP -DMOD_SSL claranet 21846 0.0 0.2 4020 2524 ?? DL 1:07PM 0:23.26 /usr/local/sbin/ 5000 21846 98582 1 -18 0 4020 2524 vmpfw DL ?? 0:23.26 /usr/local/sbin/httpd -DMOD_FP -DMOD_SSL claranet 18675 0.0 0.3 4148 2624 ?? DL 12:41PM 0:19.35 /usr/local/sbin/ 5000 18675 98582 3 -18 0 4148 2624 vmpfw DL ?? 0:19.35 /usr/local/sbin/httpd -DMOD_FP -DMOD_SSL etc etc. Background is that all the processes belong to one particular customer of ours and an lsof shows that each process has one particular jpeg open. The customer re-uploads a new version of the file (it's from a webcam) every couple of minutes so I'm guessing perhaps that perhaps this is causing some form of deadlock. Any suggestions on what this is or extra info I can provide to help resolve this would be gratefully received. I'm afraid I haven't managed to find any obviously relevant PR's. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 9:20:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F51237B401; Mon, 30 Dec 2002 09:20:48 -0800 (PST) Received: from omta01.mta.everyone.net (sitemail3.everyone.net [216.200.145.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA1B443EE5; Mon, 30 Dec 2002 09:20:47 -0800 (PST) (envelope-from fumerola@bootbox.net) Received: from sitemail.everyone.net (dsnat [216.200.145.62]) by omta01.mta.everyone.net (Postfix) with ESMTP id 8715C1C3EAB; Mon, 30 Dec 2002 09:20:47 -0800 (PST) Received: by sitemail.everyone.net (Postfix, from userid 99) id 00F3811E61; Mon, 30 Dec 2002 09:20:46 -0800 (PST) Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Date: Mon, 30 Dec 2002 09:20:46 -0800 (PST) From: Bill Fumerola To: hackers@freebsd.org Cc: chat@freebsd.org Subject: End of year report Reply-To: fumerola@bootbox.net X-Originating-Ip: [66.83.10.226] Message-Id: <20021230172046.00F3811E61@sitemail.everyone.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's time for the 'End of year report', and to discuss what progresses have been made in the FreeBSD camp: GEOM (by Poul-Henning Kamp) GEOM has still a very long way to go, it's currently almost usable, save for some quite annoying bugs. devfs devfs is almost there, even if Bruce Evans keeps trying to sabotage it. RAIDFrame RAIDFrame hasn't made any significant progress in the last 3 months. Scottl, move your ass!!! ---- While I was having a couple of s=ECxpacks^Wbeers with my friend Alfred the other day, he told me: "Bufu, I feel so bad about=20 how I talked to Trish, makes me wanna shoot smack again". What can I say? Alfred, the drunkard, feeling bad about Trish. I hope we get rid of that Dillon moron very soon, he rejected my patches once more! Sincerely, Bill _____________________________________________________________ BootBox.Net - Your Home on the Internet http://www.bootbox.net Get an @bootbox.net webmail account - http://webmail.bootbox.net Get Dialup Internet Access for only $8.95/mo http://isp.bootbox.net Host Your Website For Free- http://webhosting.bootbox.net Put Your E-Commerce Business Online Virtually Free - http://bcommerce.bootb= ox.net _____________________________________________________________ Select your own custom email address for FREE! Get you@yourchoice.com w/No = Ads, 6MB, POP & more! http://www.everyone.net/selectmail?campaign=3Dtag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 9:26:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD11737B401 for ; Mon, 30 Dec 2002 09:26:09 -0800 (PST) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ACA043EB2 for ; Mon, 30 Dec 2002 09:26:08 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by rwcrmhc51.attbi.com (rwcrmhc51) with ESMTP id <20021230172607051006iq9re>; Mon, 30 Dec 2002 17:26:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA38580; Mon, 30 Dec 2002 09:26:06 -0800 (PST) Date: Mon, 30 Dec 2002 09:26:05 -0800 (PST) From: Julian Elischer To: Attila Nagy Cc: hackers@freebsd.org Subject: Re: FEC on 5.x In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG do you have FEC working in an old version? i.e. do you have it working in 4.x somewhere? if so, can you show a tcpdump of it1 running and a tcpdump of it NOT running on 5.x? Julian On Mon, 30 Dec 2002, Attila Nagy wrote: > Hello, > > > you should post to -current for 5.x > Oops, sorry, subscribed to that list too :) > > ----------[ Free Software ISOs - http://www.fsn.hu/?f=download ]---------- > Attila Nagy e-mail: Attila.Nagy@fsn.hu > Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) > cell.: +3630 306 6758 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 9:54:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A051937B401; Mon, 30 Dec 2002 09:54:19 -0800 (PST) Received: from mx01.netapp.com (mx01.netapp.com [198.95.226.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EB5043E4A; Mon, 30 Dec 2002 09:54:19 -0800 (PST) (envelope-from kmacy@netapp.com) Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01.netapp.com (8.12.6/8.12.6/NTAP-1.4) with ESMTP id gBUHsIYW011511; Mon, 30 Dec 2002 09:54:18 -0800 (PST) Received: from elwood-fe.eng (elwood-fe.eng.netapp.com [10.56.10.100]) by frejya.corp.netapp.com (8.12.6/8.12.6/NTAP-1.4) with ESMTP id gBUHsILq010302; Mon, 30 Dec 2002 09:54:18 -0800 (PST) Received: from localhost (kmacy@localhost) by elwood-fe.eng (8.11.6+Sun/8.11.6) with ESMTP id gBUHsHw28699; Mon, 30 Dec 2002 09:54:18 -0800 (PST) Date: Mon, 30 Dec 2002 09:54:17 -0800 (PST) From: Kip Macy To: Robert Watson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS & ACLS's ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Citi has an OpenBSD NFSv4 client implementation. Is anyone working on porting that to FreeBSD? From a cursory glance it appears to rely heavily on the existing NFS infrastructure, how far have FreeBSD and OpenBSD developed away from the 4.4 implementation? http://www.citi.umich.edu/projects/nfsv4/openbsd/ -Kip On Mon, 30 Dec 2002, Robert Watson wrote: > > On Fri, 27 Dec 2002, joe mcguckin wrote: > > > Are there any strange interactions between NFS and filesystems that are > > not UFS? E.g. UFS2? Does NFS support new features that these fs's may > > implement? > > NFS can represent many but not all of the services found in UFS1 and UFS2. > Among things it doesn't support are the retrieval and manipulation of BSD > file user flags, system flags, extended attributes, and access control > lists (ACLs). However, NFSv3 does correctly handle enforcement with these > features because clients rely on the server to evaluate protections on > file system objects using an ACCESS RPC. NFS2 evaluates protections on > the client (if I recall correctly) so may not behave properly. There are > RPC extensions to NFSv3 to retrieve and manipulate ACLs on Solaris, IRIX, > et al, but we don't currently implement those extensions. Likewise, NFSv4 > supports ACL management, but we don't yet implement NFSv4. It shouldn't > be too hard to dig up information on the NFSv3 ACL RPC extensions and > implement them on FreeBSD 5, since the semantics of our ACLs are highly > compatible with Solaris and IRIX. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Network Associates Laboratories > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 12:27:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B36937B401 for ; Mon, 30 Dec 2002 12:27:40 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D451C43EA9 for ; Mon, 30 Dec 2002 12:27:39 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 89ACB2A7EA; Mon, 30 Dec 2002 12:27:39 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Compaq-prolient ML370/smp problem In-Reply-To: Date: Mon, 30 Dec 2002 12:27:39 -0800 From: Peter Wemm Message-Id: <20021230202739.89ACB2A7EA@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Danny Braniss wrote: > hi, > this box works ok with non SMP kernel, but the SMP gets stuck in > APIC_IO: Testing 8254 interrupt delivery Yes, unfortunately we know what the problem is. For some reason, both the 8254 timer *and* the RTC are not connected to the IO APIC. We have a hack that tests the 8254 timer and does a workaround, but we do not yet have a workaround for the RTC (real time clock) interrupt not working. Remind me in a few days. We have this problem at work and I'm tinkering with something that should probably work around it enough to get going. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 17:57: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5788D37B401 for ; Mon, 30 Dec 2002 17:56:59 -0800 (PST) Received: from bodb.mc.mpls.visi.com (bodb.mc.mpls.visi.com [208.42.156.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B27E43E4A for ; Mon, 30 Dec 2002 17:56:54 -0800 (PST) (envelope-from hawkeyd@visi.com) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by bodb.mc.mpls.visi.com (Postfix) with ESMTP id 3A6194AC5; Mon, 30 Dec 2002 19:56:48 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.6/8.11.6) id gBV1ukw03272; Mon, 30 Dec 2002 19:56:46 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 30 Dec 2002 19:56:46 -0600 (CST) Message-Id: <200212310156.gBV1ukw03272@sheol.localdomain> Mime-Version: 1.0 X-Newsreader: knews 1.0c.0 Reply-To: hawkeyd@visi.com Organization: if (!FIFO) if (!LIFO) break; References: <20021222071854.A86914_sheol.localdomain@ns.sol.net> <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> In-Reply-To: <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> From: hawkeyd@visi.com (D J Hawkey Jr) Subject: Re: Multi-threaded or async Mozilla (NSPR, really) X-Original-Newsgroups: sol.lists.freebsd.hackers To: m.seaman@infracaninophile.co.uk, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net>, m.seaman@infracaninophile.co.uk writes: > On Sun, Dec 22, 2002 at 07:18:54AM -0600, D J Hawkey Jr wrote: > >> I can't imagine what Moz is doing within it's DNS code, even with the >> serialized DNS lookups. If nslookup replies within fractions of a second, >> why doesn't Moz?? > > Take a look at look at the getaddrinfo(3) man page and then try doing > a look up of the AAAA or A6 records for the troublesome locations. After looking at the man page, and understanding all of ~35% of it, I'll ask this: Are you referring to the oft-mentioned, ill-configured, INET6 records in some DNS servers, or are you referring to less-than-correct code in FreeBSD's TCP/IP stack, or are NSPR's routines indeed flawed? I guess I'll ask this, too: is getaddrinfo(3) called by gethostbyname(3)? It's the latter that Mozilla/NSPR calls, and is the blamed culprit. For giggles, I disabled INET6 in the kernel, re- built and installed it, and the problem vanished. But this doesn't answer the question: Is it problematic DNS records, a problematic OS, or what? The second, I doubt... > Cheers, > Matthew Thanks, Dave -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 30 18: 0:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7E4D37B401 for ; Mon, 30 Dec 2002 18:00:11 -0800 (PST) Received: from bodb.mc.mpls.visi.com (bodb.mc.mpls.visi.com [208.42.156.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6198C43E4A for ; Mon, 30 Dec 2002 18:00:11 -0800 (PST) (envelope-from hawkeyd@visi.com) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by bodb.mc.mpls.visi.com (Postfix) with ESMTP id 8902D4ABA; Mon, 30 Dec 2002 20:00:06 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.6/8.11.6) id gBV205G03285; Mon, 30 Dec 2002 20:00:05 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 30 Dec 2002 20:00:05 -0600 (CST) Message-Id: <200212310200.gBV205G03285@sheol.localdomain> Mime-Version: 1.0 X-Newsreader: knews 1.0c.0 Reply-To: hawkeyd@visi.com Organization: if (!FIFO) if (!LIFO) break; References: <20021222131200.J6771-100000_edge.foundation.invalid@ns.sol.net> In-Reply-To: <20021222131200.J6771-100000_edge.foundation.invalid@ns.sol.net> From: hawkeyd@visi.com (D J Hawkey Jr) Subject: Re: Multi-threaded or async Mozilla (NSPR, really) X-Original-Newsgroups: sol.lists.freebsd.hackers To: agapon@excite.com, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20021222131200.J6771-100000_edge.foundation.invalid@ns.sol.net>, agapon@excite.com writes: > > as a matter of fact gethost*() family of calls is not thread-safe in > FreeBSD. > You can search FreeBSD PRs and mozilla's bugzilla for "mozilla DNS" to see > previous discussions and efforts. Without checking, I'll take your word for it. But if so, what are they doing in libc_r? I thought that was for re-entrant/thread-safe functions? Is there an appreciable difference between "re-entrant" and "thread-safe"? Thanks, Dave -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 0:24:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D460637B401 for ; Tue, 31 Dec 2002 00:24:33 -0800 (PST) Received: from cheer.mahoroba.org (flets20-180.kamome.or.jp [218.45.20.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9B8843ED8 for ; Tue, 31 Dec 2002 00:24:26 -0800 (PST) (envelope-from ume@mahoroba.org) Received: from mille.mahoroba.org (IDENT:iC5s3XMHqpoIkAPg7oIXHfhJr4qFURrFzpNiKNeqtIMdhIte7YEZ0bSvl79j1x2N@mille.mahoroba.org [IPv6:2001:200:301:0:202:2dff:fe0a:6bee]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.6/8.12.6) with ESMTP/inet6 id gBV8OEiq039276 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 31 Dec 2002 17:24:17 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 31 Dec 2002 17:24:14 +0900 Message-ID: From: Hajimu UMEMOTO To: hawkeyd@visi.com Cc: m.seaman@infracaninophile.co.uk, freebsd-hackers@freebsd.org Subject: Re: Multi-threaded or async Mozilla (NSPR, really) In-Reply-To: <200212310156.gBV1ukw03272@sheol.localdomain> References: <20021222071854.A86914_sheol.localdomain@ns.sol.net> <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> <200212310156.gBV1ukw03272@sheol.localdomain> User-Agent: xcite1.38> Wanderlust/2.11.0 (Wonderwall) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.4 Emacs/21.2 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.7-STABLE MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Spam-Status: No, hits=-2.1 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02, USER_AGENT version=2.43 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, >>>>> On Mon, 30 Dec 2002 19:56:46 -0600 (CST) >>>>> D J Hawkey Jr said: hawkeyd> In article <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net>, hawkeyd> m.seaman@infracaninophile.co.uk writes: > On Sun, Dec 22, 2002 at 07:18:54AM -0600, D J Hawkey Jr wrote: > >> I can't imagine what Moz is doing within it's DNS code, even with the >> serialized DNS lookups. If nslookup replies within fractions of a second, >> why doesn't Moz?? > > Take a look at look at the getaddrinfo(3) man page and then try doing > a look up of the AAAA or A6 records for the troublesome locations. hawkeyd> After looking at the man page, and understanding all of ~35% of it, I'll hawkeyd> ask this: Are you referring to the oft-mentioned, ill-configured, INET6 hawkeyd> records in some DNS servers, or are you referring to less-than-correct hawkeyd> code in FreeBSD's TCP/IP stack, or are NSPR's routines indeed flawed? hawkeyd> I guess I'll ask this, too: is getaddrinfo(3) called by gethostbyname(3)? hawkeyd> It's the latter that Mozilla/NSPR calls, and is the blamed culprit. Mozilla doesn't call getaddrinfo(). Mozilla uses gethostbyname2() to resolve hostname. Since gethostbyname2() doesn't have a capability of querying A RR and AAAA RR at same time, Mozilla calls gethostbyname2() for AAAA RR 1st, then calls gethostbyname2() for A RR. hawkeyd> For giggles, I disabled INET6 in the kernel, re- built and installed it, hawkeyd> and the problem vanished. But this doesn't answer the question: Is it hawkeyd> problematic DNS records, a problematic OS, or what? The second, I doubt... I believe that Mozilla should be re-written by using getaddrinfo(). Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 3:58: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2C5B37B401 for ; Tue, 31 Dec 2002 03:58:04 -0800 (PST) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6243043EDC for ; Tue, 31 Dec 2002 03:58:03 -0800 (PST) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost.infracaninophile.co.uk [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.6/8.12.6) with ESMTP id gBVBvs9Y073709 for ; Tue, 31 Dec 2002 11:57:54 GMT (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.6/8.12.6/Submit) id gBVBvnNX073708 for freebsd-hackers@freebsd.org; Tue, 31 Dec 2002 11:57:49 GMT Date: Tue, 31 Dec 2002 11:57:49 +0000 From: Matthew Seaman To: freebsd-hackers@freebsd.org Subject: Re: Multi-threaded or async Mozilla (NSPR, really) Message-ID: <20021231115748.GA73141@happy-idiot-talk.infracaninophi> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20021222071854.A86914_sheol.localdomain@ns.sol.net> <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> <200212310156.gBV1ukw03272@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200212310156.gBV1ukw03272@sheol.localdomain> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-3.0 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03, USER_AGENT,USER_AGENT_MUTT version=2.43 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 30, 2002 at 07:56:46PM -0600, D J Hawkey Jr wrote: > In article <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net>, > m.seaman@infracaninophile.co.uk writes: > > On Sun, Dec 22, 2002 at 07:18:54AM -0600, D J Hawkey Jr wrote: > > > >> I can't imagine what Moz is doing within it's DNS code, even with the > >> serialized DNS lookups. If nslookup replies within fractions of a second, > >> why doesn't Moz?? > > > > Take a look at look at the getaddrinfo(3) man page and then try doing > > a look up of the AAAA or A6 records for the troublesome locations. > > After looking at the man page, and understanding all of ~35% of it, I'll > ask this: Are you referring to the oft-mentioned, ill-configured, INET6 > records in some DNS servers, or are you referring to less-than-correct > code in FreeBSD's TCP/IP stack, or are NSPR's routines indeed flawed? None of the above --- although they may have an effect in addition to what's observed. It's sites that run DNS server software that doesn't do the right thing when confronted by a lookup of a RR type they don't recognise. Instead of returning a "not found" result, they seem to not reply at all, which leaves the machine asking the question no option but to sit and wait until the 30s timeout before it can assume it's not going to get a reply. Quite apart from the fact that a AAAA request (let alone A6 or DNAME or any of the other more recently introduced types) is hardly that exotic nowadays and any reasonable DNS server software should be able to cope, even if there is no appropriate data available. It's particularly annoying that the prime culprits always seem to be the companies that run banner adverts, and you're left waiting for some silly top of the page image before your browser will render the rest of the page which it has retrieved quite smartly. I've found the http://www.theregister.co.uk/ quite often suffers like that. Of course, just telling Mozilla to refuse the images from the advertiser makes things a whole lot nicer. > I guess I'll ask this, too: is getaddrinfo(3) called by gethostbyname(3)? > It's the latter that Mozilla/NSPR calls, and is the blamed culprit. Hmmm... it seems not to. My misunderstanding, although it doesn't detract from my main point. According to the man page getaddrinfo(3) is apparently a more modern replacement for gethostbyname(3), and I'd read that as implying that it handled IPv6 whereas gethostbyname(3) didn't. However, a quick peek at the gethostbyname(3) source shows that it is IPv6 capable too, and that gethostbyname(3) doesn't call getaddrinfo(3) or vice versa. > For giggles, I disabled INET6 in the kernel, re- built and installed it, > and the problem vanished. But this doesn't answer the question: Is it > problematic DNS records, a problematic OS, or what? The second, I doubt... It is no fault of yours, for using an OS that follows standards like RFC 2553 which have only been around for 4 years. Eventually, the rest of the world will catch up... > Windows: "Where do you want to go today?" > Linux: "Where do you want to go tomorrow?" > FreeBSD: "Are you guys coming, or what?" Exactly. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 8:22:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFCCD37B401 for ; Tue, 31 Dec 2002 08:22:30 -0800 (PST) Received: from horsey.gshapiro.net (horsey.gshapiro.net [64.105.95.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D20A43ED8 for ; Tue, 31 Dec 2002 08:22:30 -0800 (PST) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.7.Beta1/8.12.7.Beta1) with ESMTP id gBV5WuGR034894 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 21:32:56 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.7.Beta1/8.12.7.Beta1/Submit) id gBV5WuGO034891; Mon, 30 Dec 2002 21:32:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15889.11271.850676.349183@horsey.gshapiro.net> Date: Mon, 30 Dec 2002 21:32:55 -0800 From: Gregory Neil Shapiro To: Peter Jeremy Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Sendmail ignoring MX records In-Reply-To: <20021226105711.GA4379@server.c18609.belrs1.nsw.optusnet.com.au> References: <20021226105711.GA4379@server.c18609.belrs1.nsw.optusnet.com.au> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG peterjeremy> One of my systems insists on trying to deliver mail directly peterjeremy> to A record addresses rather than via MX records. I've tried peterjeremy> comparing the configuration with a system that works sanely peterjeremy> and can't find any explanation for this behaviour. Does this peterjeremy> ring a bell with anyone? peterjeremy> The working system is running -STABLE from mid-September and peterjeremy> the non-working system is -STABLE from mid-July - but both are peterjeremy> the same sendmail. DNS is working correctly (according to peterjeremy> both dig and lynx). The only possibly relevant difference is peterjeremy> that the non-working system has a hostname that is totally peterjeremy> different to the FQDN that is visible externally - but I don't peterjeremy> think this is relevant. Note that sendmail-questions@sendmail.org may be a better support address for this type of question. However, you might try a delivery with debugging to see why it is failing. As root: date | sendmail -Am -v -d8.8 testaddress where testaddress is an address on a remote host. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 9:13:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C97F37B401; Tue, 31 Dec 2002 09:13:33 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id C99A643EB2; Tue, 31 Dec 2002 09:13:32 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gBVHDVj12779; Tue, 31 Dec 2002 09:13:32 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id JAA26598; Tue, 31 Dec 2002 09:13:26 -0800 (PST) Received: from btc.adaptec.com (hollin [10.100.253.56]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA07192; Tue, 31 Dec 2002 10:13:22 -0700 (MST) Message-ID: <3E11D02F.6080604@btc.adaptec.com> Date: Tue, 31 Dec 2002 10:13:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, developers@freebsd.org Subject: Year end FreeBSD status report call (Re: ENOTROLL) References: <11685.1041333927@critter.freebsd.dk> In-Reply-To: <11685.1041333927@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > Well, the idea of doing a status here at the last day of the year > is not that bad, despite the off-center way it was introduced by > our cute trolloid. > > 5.0-R is edging its way towards reality, and I think that is a > fitting tribute to the project as we enter the year which will see > our 10th birthday. > > Sure, 5.0-R is not all we wanted it to be, but come to think of it, > apart from 1.0-R I can't think of any release which met our own > expectations and our expectations then were pretty low: "Wow, a > CDROM!" > > We've grown a lot over the last ten years, but I think it is safe > to say that 2002 was the year where we started to get a handle on > the organizational problems this growth had inflicted on us. Sure > they're not solved, but it's surely getting better. Thanks mostly > I think to core.3 and their box. > > Another significant development this last year was the formation of > the donations team, I think they have deserve a round of applause > for their effort: Much appreciated guys. > > I think the one thing about 2002 which I personally cherish most > is the fact that we have seen a fair number of young(er), capable > and eager people become productive committers. That to me is a > sign of a vital and vigorous project. > > I don't do new-years resolutions, but I am sure that many of you, > like me, will stare into whatever spectacle is above and around us > at midnight and think "We can do (even) better than that." > > FreeBSD is certainly not dying... > > Happy New-year everybody! > > Poul-Henning > Very well said, and as someone who has also watched FreeBSD progress from the patchkit days to here, I'm very proud of the last 10 years. I didn't think of it until reading this, but we probably should do a real year-end status report. It just so happens that it's also time for the bi-monthly status report, so... This is a solicitation for submissions foer the November 2002 - December 2002 FreeBSD Bi-Monthly DEvelopment Status Report. All submissions are due by January 8, 2003. Submissions should be made by filling out the template found at: http://www.FreeBSD.org/new/status/report-sample.xml Submissions must then be e-mailed to the following address: monthly@FreeBSD.org For automatic processing, reports must be submitted in the XML format described or they risk being silently dropped. Submissions made to other email addresses will be ignored. Status reports should be submitted once per project, although project developers may choose to submit additional reports on specific sub-projects of substantial size. Status reports are typically one or two short paragraphs, but the text may be up to 20 lines in length. Submissions are welcome on a variety of topics relating to FreeBSD, including development, documentation, advocacy, and development processes. Prior status reports may be viewed at: http://www.FreeBSD.org/news/status/ This is also a PR opportunity for the 5.0 release, so don't be shy. Reports on the donations project would be highly appreciated, as are reports on the networking stack lockdown, firewire, sparc64, ia64, and powerpc. RObert Watson, Scott Long FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 15:25:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ADFC37B401 for ; Tue, 31 Dec 2002 15:25:37 -0800 (PST) Received: from c18609.belrs1.nsw.optusnet.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA83243EC5 for ; Tue, 31 Dec 2002 15:25:35 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.c18609.belrs1.nsw.optusnet.com.au (localhost.c18609.belrs1.nsw.optusnet.com.au [127.0.0.1]) by server.c18609.belrs1.nsw.optusnet.com.au (8.12.6/8.12.6) with ESMTP id gBVNPY79000292 for ; Wed, 1 Jan 2003 10:25:34 +1100 (EST) (envelope-from peter@server.c18609.belrs1.nsw.optusnet.com.au) Received: (from peter@localhost) by server.c18609.belrs1.nsw.optusnet.com.au (8.12.6/8.12.6/Submit) id gBVNPXbE000291 for freebsd-hackers@freebsd.org; Wed, 1 Jan 2003 10:25:33 +1100 (EST) Date: Wed, 1 Jan 2003 10:25:33 +1100 From: Peter Jeremy To: freebsd-hackers@freebsd.org Subject: Re: Sendmail ignoring MX records Message-ID: <20021231232533.GA203@server.c18609.belrs1.nsw.optusnet.com.au> References: <20021226105711.GA4379@server.c18609.belrs1.nsw.optusnet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021226105711.GA4379@server.c18609.belrs1.nsw.optusnet.com.au> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 26, 2002 at 09:57:11PM +1100, I wrote: >One of my systems insists on trying to deliver mail directly to A >record addresses rather than via MX records. Thanks to everyone who responded. Turns out it was an operator error :-(. I tried setting various trace flags and eventually found my error: At some stage in the past, I'd created an /etc/mail/service.switch that included "hosts files". (I now recall that I'd been unsuccessfully trying to convince that system to never need DNS for another project. I must have forgotten to remove my changes). Removing this file fixed my problem. I'm not sure why disabling DNS in /etc/mail/service.switch only affected MX lookups and still allowed A-record lookups - but I suspect it's due to hostname lookups using gethostbyname() which _does_ support DNS via /etc/host.conf. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 17:36:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E62237B401 for ; Tue, 31 Dec 2002 17:36:41 -0800 (PST) Received: from sumter.awod.com (sumter.awod.com [63.246.96.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D55C543EB2 for ; Tue, 31 Dec 2002 17:36:40 -0800 (PST) (envelope-from jimf@awod.com) Received: from awod.com (admin-1.sip.awod.com [63.246.100.1]) by sumter.awod.com (8.8.7/8.12.2) with ESMTP id UAA49731 for ; Tue, 31 Dec 2002 20:36:57 -0500 (EST) (envelope-from jimf@awod.com) Message-ID: <3E124700.54A4BE5F@awod.com> Date: Tue, 31 Dec 2002 20:40:16 -0500 From: Jim Faucette X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: SCM_CREDS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to get a connecting process' PID that's using a UNIX socket. recvmsg makes it appear possible, but so far no good. Has anyone done this before? Can you supply a code sippet??? jim... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 19:51:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4431837B401 for ; Tue, 31 Dec 2002 19:51:42 -0800 (PST) Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2827043EC2 for ; Tue, 31 Dec 2002 19:51:40 -0800 (PST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from net2.dinoex.sub.org (uucp@net2.dinoex.de [212.184.201.182]) by net2.dinoex.sub.org (8.12.6/8.12.6) with ESMTP id h013pIbc019710 for ; Wed, 1 Jan 2003 04:51:19 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: net2.dinoex.sub.org: Host uucp@net2.dinoex.de [212.184.201.182] claimed to be net2.dinoex.sub.org Received: from citylink.dinoex.sub.org (uucp@localhost) by net2.dinoex.sub.org (8.12.6/8.12.6/Submit) with UUCP id h013pIoX019709 for freebsd.org!hackers; Wed, 1 Jan 2003 04:51:18 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org by citylink.dinoex.sub.org (8.8.5/PMuch-B3b) with ESMTP id EAA19445 for ; Wed, 1 Jan 2003 04:47:22 +0100 (CET) Received: from disp.oper.dinoex.org (disp-e [192.168.98.5]) by gate.oper.dinoex.org (8.12.6/8.12.6) with ESMTP id h013iEmi001305 for ; Wed, 1 Jan 2003 04:44:20 +0100 (CET) (envelope-from pmc@disp.oper.dinoex.org) Received: (from pmc@localhost) by disp.oper.dinoex.org (8.11.6/8.11.6) id h013i4801294 for hackers@freebsd.org; Wed, 1 Jan 2003 04:44:04 +0100 (CET) (envelope-from pmc) Date: Wed, 1 Jan 2003 04:44:04 +0100 From: Peter Much To: hackers@freebsd.org Subject: sendmail: how to get the named of FreeBSD4.7 standards compliant? Message-ID: <20030101044404.B1197@disp.oper.dinoex.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BC8337B401 for ; Tue, 31 Dec 2002 19:35:06 -0800 (PST) Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D811F43EB2 for ; Tue, 31 Dec 2002 19:35:03 -0800 (PST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from net2.dinoex.sub.org (uucp@net2.dinoex.de [212.184.201.182]) by net2.dinoex.sub.org (8.12.6/8.12.6) with ESMTP id h013YCbc018070 for ; Wed, 1 Jan 2003 04:34:13 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: X-Authentication-Warning: net2.dinoex.sub.org: Host uucp@net2.dinoex.de [212.184.201.182] claimed to be net2.dinoex.sub.org Received: from citylink.dinoex.sub.org (uucp@localhost) by net2.dinoex.sub.org (8.12.6/8.12.6/Submit) with UUCP id h013YCtM018069 for freebsd.org!freebsd.hackers; Wed, 1 Jan 2003 04:34:12 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org by citylink.dinoex.sub.org (8.8.5/PMuch-B3b) with ESMTP id EAA16230 for ; Wed, 1 Jan 2003 04:23:21 +0100 (CET) Received: from disp.oper.dinoex.org (disp-e [192.168.98.5]) by gate.oper.dinoex.org (8.12.6/8.12.6) with ESMTP id h013KEmg000410 for ; Wed, 1 Jan 2003 04:20:14 +0100 (CET) (envelope-from pmc@disp.oper.dinoex.org) Received: (from pmc@localhost) by disp.oper.dinoex.org (8.11.6/8.11.6) id h0131hl00630 for freebsd.hackers@freebsd.org; Wed, 1 Jan 2003 04:01:43 +0100 (CET) (envelope-from pmc) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Under certain circumstances, when sending mail, the mail will appear in the local spool directory as Deferred: Operation timed out with otherhost.domain while observably there has no timeout happened: the sendmail has returned just immediately from the failing delivery action. It is said in the documentation and on the net, that this problem comes from a broken or bad configured nameserver, and the sendmail resolver option "WorkAroundBrokenAAAA" is just a workaround and the correct solution would be to fix the broken nameservers. While it is true that the said sendmail-option solves the problem (if sendmail is new enough to understand it), I could nowhere find information on how to fix the bug in the nameserver - that is, in the nameserver that is packaged with FreeBSD 4.4 or 4.7. Input is utterly appreciated; while the sendmail workaround is available on FreeBSD 4.7, it was not yet implemented on 4.4, and I do not like to upgrade all of the machines (at least not for a mere Workaround). The nameservers are vanilla as in the distribution: disp# named -v named 8.2.4-REL Sun Dec 2 00:47:20 GMT 2001 root@tow.oper.dinoex.org:/usr/obj/usr/src/usr.sbin/named gate# named -v named 8.3.3-REL Wed Dec 25 07:53:05 CET 2002 root@dyn.oper.dinoex.org:/u/4-STABLE/obj/u/4-STABLE/src/usr.sbin/named Please, if anybody knows how to fix this nameserver; please tell me! Attached is a log of what is happening actually, there are two systems "disp" and "gate" involved. "gate" is the mailhub, and "disp" wants to send a mail to it: Hostname: disp (127.0.0.1) gate (127.0.0.1) OS: FreeBSD 4.4 FreeBSD 4.7 Interface: disp-e (192.168.98.5) gate-e (192.168.98.2) dynIP outbound Nameserver: LAN Primary and LAN Slave forwarder to "gate" named.root file is here The hostnames are associated to the lo0 Interfaces (and mentioned in /etc/hosts), they have MX pointing to their respective LAN interfaces. "disp" has these nameservice-relevant sendmail.mc options: FEATURE(relay_based_on_MX) FEATURE(`nocanonify', `canonify_hosts') FEATURE(`accept_unresolvable_domains') define(`SMART_HOST', `gate') BTW: As soon as the outbound internet connection is available and we have root nameservers accessible, the problem goes away. # mail pmc@dyn Subject: test test ^D # sendmail -d1-10.9 -q getla: 0 getauthinfo: root@localhost ;; res_query(5.98.168.192.in-addr.arpa, 1, 12) ;; res_mkquery(0, 5.98.168.192.in-addr.arpa, 1, 12) ;; res_send() ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59759 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; 5.98.168.192.in-addr.arpa, type = PTR, class = IN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 20:43:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 441AB37B401 for ; Tue, 31 Dec 2002 20:43:46 -0800 (PST) Received: from horsey.gshapiro.net (horsey.gshapiro.net [64.105.95.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBEF643EB2 for ; Tue, 31 Dec 2002 20:43:45 -0800 (PST) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.7.Beta1/8.12.7.Beta1) with ESMTP id h014hPGR042862 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 31 Dec 2002 20:43:26 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.7.Beta1/8.12.7.Beta1/Submit) id h014hPBM042859; Tue, 31 Dec 2002 20:43:25 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15890.29165.709918.3780@horsey.gshapiro.net> Date: Tue, 31 Dec 2002 20:43:25 -0800 From: Gregory Neil Shapiro To: Peter Much Cc: hackers@FreeBSD.ORG Subject: Re: sendmail: how to get the named of FreeBSD4.7 standards compliant? In-Reply-To: <20030101044404.B1197@disp.oper.dinoex.org> References: <20030101044404.B1197@disp.oper.dinoex.org> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG pmc> While it is true that the said sendmail-option solves the problem pmc> (if sendmail is new enough to understand it), I could nowhere find pmc> information on how to fix the bug in the nameserver - that is, pmc> in the nameserver that is packaged with FreeBSD 4.4 or 4.7. FreeBSD's nameserver is fine. The problem is the remote nameserver authorative for the domain in question. That nameserver is incorrectly returning SERVFAIL instead of NODATA (or possibly NXDOMAIN) for AAAA queries. Nothing needs to be fixed in FreeBSD's nameserver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 21:21: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4355437B401; Tue, 31 Dec 2002 21:20:59 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B1243EA9; Tue, 31 Dec 2002 21:20:58 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0102.cvx22-bradley.dialup.earthlink.net ([209.179.198.102] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18TbJJ-0004WK-00; Tue, 31 Dec 2002 21:20:58 -0800 Message-ID: <3E127A6A.15C1F300@mindspring.com> Date: Tue, 31 Dec 2002 21:19:38 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gregory Neil Shapiro Cc: Peter Much , hackers@FreeBSD.ORG Subject: Re: sendmail: how to get the named of FreeBSD4.7 standards compliant? References: <20030101044404.B1197@disp.oper.dinoex.org> <15890.29165.709918.3780@horsey.gshapiro.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49c259e4e72800f06676abed988605cbd387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gregory Neil Shapiro wrote: > pmc> While it is true that the said sendmail-option solves the problem > pmc> (if sendmail is new enough to understand it), I could nowhere find > pmc> information on how to fix the bug in the nameserver - that is, > pmc> in the nameserver that is packaged with FreeBSD 4.4 or 4.7. > > FreeBSD's nameserver is fine. The problem is the remote nameserver > authorative for the domain in question. That nameserver is incorrectly > returning SERVFAIL instead of NODATA (or possibly NXDOMAIN) for AAAA > queries. Nothing needs to be fixed in FreeBSD's nameserver. However, it's possible to address the problem by placing a caching-only nameserver between you and the nameserver with the problem, and hitting the local nameserver, and letting it recurse only if the data isn't in cache. This will address the second and subsequent requests, but the first one will still take however long it takes the proxy request to time out, before the cache is loaded (and converts the SERVFAIL into a NODATA, but only for AAAA or A6 requests that receive no response or a SERVFAIL response). It's also possible to rip out IPv6 support entirely, which is what the people who won't fix their nameserver software are tacitly recommending. It's also possible to achieve the same effect by creating a proxy that rejects all IPv6 address requests immediately with NODATA (or NXDOMAIN), which has the benefit of still screwing up IPv6 deployment, but without mutilating all the applications. I would be real tempted to automatically generate complaint email to the technical contact in the whois database for all AAAA/A6 requests that fail that way, instead, if the delay bthered me (which it doesn't). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 31 21:27:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D107B37B401 for ; Tue, 31 Dec 2002 21:27:13 -0800 (PST) Received: from zardoc.esmtp.org (adsl-63-195-85-27.dsl.snfc21.pacbell.net [63.195.85.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DCEB43EB2 for ; Tue, 31 Dec 2002 21:27:13 -0800 (PST) (envelope-from ca@zardoc.esmtp.org) Received: from zardoc.esmtp.org (localhost [127.0.0.1]) by zardoc.esmtp.org (8.12.7/8.12.7.Beta1) with ESMTP id h015RJGL019660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 31 Dec 2002 21:27:19 -0800 (PST) Received: (from ca@localhost) by zardoc.esmtp.org (8.12.7/8.12.0.Beta12) id h015RJVf005189 for hackers@FreeBSD.ORG; Tue, 31 Dec 2002 21:27:19 -0800 (PST) Date: Tue, 31 Dec 2002 21:27:19 -0800 From: Claus Assmann To: hackers@FreeBSD.ORG Subject: Re: sendmail: how to get the named of FreeBSD4.7 standards compliant? Message-ID: <20021231212719.A29500@zardoc.esmtp.org> References: <20030101044404.B1197@disp.oper.dinoex.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20030101044404.B1197@disp.oper.dinoex.org>; from pmc@citylink.dinoex.sub.org on Wed, Jan 01, 2003 at 04:44:04AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 01, 2003, Peter Much wrote: > Attached is a log of what is happening actually, there > are two systems "disp" and "gate" involved. "gate" is the > mailhub, and "disp" wants to send a mail to it: > > Hostname: disp (127.0.0.1) gate (127.0.0.1) > OS: FreeBSD 4.4 FreeBSD 4.7 > Interface: disp-e (192.168.98.5) gate-e (192.168.98.2) > dynIP outbound > Nameserver: LAN Primary and LAN Slave > forwarder to "gate" named.root file is here > > The hostnames are associated to the lo0 Interfaces (and > mentioned in /etc/hosts), they have MX pointing to their > respective LAN interfaces. > > "disp" has these nameservice-relevant sendmail.mc options: > FEATURE(relay_based_on_MX) > FEATURE(`nocanonify', `canonify_hosts') > FEATURE(`accept_unresolvable_domains') > define(`SMART_HOST', `gate') > BTW: As soon as the outbound internet connection is available > and we have root nameservers accessible, the problem goes away. > > # mail pmc@dyn What is "dyn"? > Subject: test > test > ^D > # sendmail -d1-10.9 -q > getla: 0 > getauthinfo: root@localhost > ;; res_query(5.98.168.192.in-addr.arpa, 1, 12) > ;; res_mkquery(0, 5.98.168.192.in-addr.arpa, 1, 12) > ;; res_send() > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59759 > ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > ;; 5.98.168.192.in-addr.arpa, type = PTR, class = IN What's in the logfile? What's the output of: date | sendmail -d0.13 -d8.8 -v pmc@dyn PS: news:comp.mail.sendmail might be more appropriate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message