From owner-freebsd-hackers Sun Jan 19 5:10:43 2003 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 A8A9037B401 for ; Sun, 19 Jan 2003 05:10:41 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C83243F13 for ; Sun, 19 Jan 2003 05:10:41 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0034.cvx21-bradley.dialup.earthlink.net ([209.179.192.34] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18aFDi-00057w-00; Sun, 19 Jan 2003 05:10:39 -0800 Message-ID: <3E2AA0A9.C8386AED@mindspring.com> Date: Sun, 19 Jan 2003 04:57:13 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Arun Sharma Cc: hackers@freebsd.org Subject: Re: listing sysinit order ? References: <20030118203706.GA21624@sharma-home.net> <3E29D775.EA2323A9@mindspring.com> <3E29DDDB.6000906@sharma-home.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40fc8718038de15868b5643a3b761107893caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c 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 Arun Sharma wrote: > Terry Lambert wrote: > > Arun Sharma wrote: > > > >>So my question is, is there a simple tool to list the order in which > >>various initialization/probe routines get called in mi_startup ? If not, > >>what would it take to write one ? > > > > more /sys/sys/kernel.h > > Yes, I'm aware of this one, but it doesn't tell me very pricisely which > drivers get initialized in what order. They get initialized by the ordinal value of the initializer; if you know the ordinal value, then you can know the driver. If you are asking for a reverse map... it's not there. That's because the kernel doesn't know what's linked into it (or we would not have needed SYSINIT in the first place). If you are asking for a reverse map, the closes you are going to get is: find /sys -name \*.x | xargs fgrep SYSINIT | more > > You can not cause messages to be printed until after SI_SUB_CONSOLE; > > if you want to put a printf in the init_main.c, verify that the > > sysinit_sub_id is > SI_SUB_CONSOLE before attempting to call the > > printf. > > At that point only a function pointer is available. Is there a good way > of converting it into a printable string ? No, actually, it's a sysinit structure. The function pointer is only one member, e.g.: if ((*sipp)->subsystem == SI_SUB_DONE) continue; /* Call function */ (*((*sipp)->func))((*sipp)->udata); If you change this to: if ((*sipp)->subsystem == SI_SUB_DONE) continue; if ((*sipp)->subsystem > SI_SUB_CONSOLE) printf( "init_main: SYSINIT %d %s\n", (*sipp)->subsystem, (*sipp)->order); /* Call function */ (*((*sipp)->func))((*sipp)->udata); You will get the information you seem to be asking for (unless I'm misunderstanding you, and you are trying to lead upo asking for a string identifier, and for some reason you don't want to come out and ask for a modification of the SYSINIT macro, for some reason...). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 7:43:40 2003 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 9C19237B40D for ; Sun, 19 Jan 2003 07:43:35 -0800 (PST) Received: from postbode02.zonnet.nl (postbode02.zonnet.nl [62.58.50.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id C90EB43FAF for ; Sun, 19 Jan 2003 07:43:22 -0800 (PST) (envelope-from lijst10sec@hotmail.com) Received: (qmail 25690 invoked by uid 0); 19 Jan 2003 15:43:21 -0000 Received: from unknown (HELO smtp.com) ([62.59.141.29]) (envelope-sender ) by postbode02.zonnet.nl (qmail-ldap-1.03) with SMTP for ; 19 Jan 2003 15:43:21 -0000 Date: Sun, 19 Jan 2003 15:54:13 +0100 From: lijst10sec@hotmail.com Subject: First Seconds: 40+ dating To: lijst10sec@hotmail.com Reply-To: info@firstseconds.nl X-Bulkmail: 2.05 Message-Id: <20030119154324.C90EB43FAF@mx1.FreeBSD.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 L.s. Onder single dertigers is "speeddating" een trend. Het snelle daten is een vrolijke en spannende manier om in korte tijd veel mensen te ontmoeten. First Seconds organiseert deze vorm van kennismaken voor alleenstaanden van begin 40 tot eind 50. In Hotel New York te Rotterdam op 23 februari zullen 25 dames 25 heren ontmoeten. Gedurende enkele minuten knopen zij een gesprekje aan, stellen wat vragen, beslissen of ze hun gespreksparter nog eens willen ontmoeten en gaan naar de volgende persoon. Aan het einde van de middag geeft men aan First Seconds door wie men leuk genoeg vindt voor een vervolg. Als er een 'match' is, ontvangen deelnemers de volgende dag het e-mailadres of telefoonnummer van de andere partij. Interesse in een vrolijk en spannend middagje uit? Bezoek onze site: http://www.firstseconds.nl Met vriendelijke groet, First Seconds To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 9:50:47 2003 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 C293B37B406 for ; Sun, 19 Jan 2003 09:50:43 -0800 (PST) Received: from crf-consulting.co.uk (pc-80-194-99-19-hy.blueyonder.co.uk [80.194.99.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DAD944355 for ; Sun, 19 Jan 2003 09:46:54 -0800 (PST) (envelope-from nik@crf-consulting.co.uk) Received: from canyon.nothing-going-on.org (localhost [127.0.0.1]) by crf-consulting.co.uk (8.12.6/8.12.6) with ESMTP id h0JH38Pk000505; Sun, 19 Jan 2003 17:03:08 GMT (envelope-from nik@canyon.nothing-going-on.org) Received: (from nik@localhost) by canyon.nothing-going-on.org (8.12.6/8.12.6/Submit) id h0JH37Ar000504; Sun, 19 Jan 2003 17:03:07 GMT Date: Sun, 19 Jan 2003 17:03:06 +0000 From: Nik Clayton To: void Cc: hackers@freebsd.org Subject: Re: Mac iBook OS10 + BSD Message-ID: <20030119170306.GB298@canyon.nothing-going-on.org> References: <15883.6486.551402.144752@grasshopper.cs.duke.edu> <6D4C8B03-284B-11D7-B66E-003065D4F4F2@firedrake.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0" Content-Disposition: inline In-Reply-To: <6D4C8B03-284B-11D7-B66E-003065D4F4F2@firedrake.org> User-Agent: Mutt/1.4i Organization: FreeBSD Project 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 --LyciRD1jyfeSSjG0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 15, 2003 at 12:37:25AM -0500, void wrote: > On Thursday, December 26, 2002, at 09:59 AM, Andrew Gallatin wrote: > >I think he means text-only syscons like vtys. MacOSX does not have > >them. >=20 > I don't know about *multiple* text-only vtys, but it's easy enough to=20 > get the system into a no-graphics mode. In case anyone's wondering how you do this on OS X, just log in at the GUI with the username '>console' (no quotes). N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --LyciRD1jyfeSSjG0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+KtpJk6gHZCw343URAi1BAKCKpF88eQDuHCBNb/GtF1+MDvBBKgCfZK0T mMEz7N52KN8GrBz2SZEct+0= =DM3b -----END PGP SIGNATURE----- --LyciRD1jyfeSSjG0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 14:16: 8 2003 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 33E5E37B401 for ; Sun, 19 Jan 2003 14:16:07 -0800 (PST) Received: from mail.cult.cu (mail.cult.cu [169.158.120.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9055A43E4A for ; Sun, 19 Jan 2003 14:15:57 -0800 (PST) (envelope-from admin@atenas.cult.cu) Received: from mail by mail.cult.cu with local-bsmtp (Exim 3.03 #2) id 18aNjE-000NbO-00 for freebsd-hackers@freebsd.org; Sun, 19 Jan 2003 17:15:44 -0500 Received: from [169.158.120.178] (helo=mail.atenas.cult.cu) by mail.cult.cu with esmtp (Exim 3.03 #2) id 18aNj6-000Nai-00 for freebsd-hackers@freebsd.org; Sun, 19 Jan 2003 17:15:36 -0500 Received: from ceisic.cult.cu ([192.168.1.3] helo=Design) by mail.atenas.cult.cu with smtp (Exim 3.34 #1) id 18aNhl-0000Ew-00 for freebsd-hackers@FreeBSD.ORG; Sun, 19 Jan 2003 17:14:13 -0500 Message-ID: <000501c2c008$390a6890$0301a8c0@Design> From: "Mynx" To: Subject: Forwarding packages... Date: Sun, 19 Jan 2003 17:15:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 hackers: Listen, I got two servers, first (MAIL) running Exim and Tacacs+, second (FTP) running WWW, Squid, Samba, FTP ok, now MAILīs IP is xxx.yyy.120.178 and FTP share two Ethernet cards (xxx.yyy.120.179 and 192.168.1.1). Then a LAN connects to server (FTP) by the 192.168.1.1 IP. To connect the LAN with MAIL, enable Gateway in Inetd.conf, right. Note: There is a Cisco with xxx.yyy.120.177 IP. Question 1: there is another way to do the same thing. Question 2: Why I cannot see FTP and Samba services when start, just Squid and Apache. Thaks, by the way... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 16:57: 2 2003 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 4960437B401 for ; Sun, 19 Jan 2003 16:57:01 -0800 (PST) Received: from spork.pantherdragon.org (spork.pantherdragon.org [206.29.168.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 949E243EB2 for ; Sun, 19 Jan 2003 16:57:00 -0800 (PST) (envelope-from dmp@pantherdragon.org) Received: from sparx.techno.pagans (12-224-208-117.client.attbi.com [12.224.208.117]) by spork.pantherdragon.org (Postfix) with ESMTP id 56A511005F; Sun, 19 Jan 2003 16:56:54 -0800 (PST) Received: from pantherdragon.org (speck.techno.pagans [172.21.42.2]) by sparx.techno.pagans (Postfix) with ESMTP id 18CFCAA8F; Sun, 19 Jan 2003 16:56:52 -0800 (PST) Message-ID: <3E2B4953.7060008@pantherdragon.org> Date: Sun, 19 Jan 2003 16:56:51 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Morozovsky Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD firewall for high profile hosts - waste of time ? References: <20030116124254.J9642-100000@mail.econolodgetulsa.com> <3E2738BA.4090806@pantherdragon.org> <20030119001015.S46739@woozle.rinet.ru> 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 Dmitry Morozovsky wrote: > On Thu, 16 Jan 2003, Darren Pilgrim wrote: > > DP> There is sorting that you can do, like putting the highest-traffic rules > DP> near the top. ipfw terminates the search on the first matching rule except > DP> for count and skipto. Also, the fewer items that have to be checked the > DP> faster the rule is. Perhaps there is some aggregation that can be done with > DP> the rules themselves? > > By the way, is (moderately complex) aggregated rule faster than mix of simple > rules? (for now, we drop accounting issues) > > So, will > > permit tcp from {a.b.c.0/24 or e.f.g.0/20} to any 22,25,80,443 setup > perform measurably better than set of 8 corresponding rules? I'm not sure if the {a.b.c.0/24 or e.f.g.0/20} part is valid, but in theory this rule should require fewer ops on average than 8 seperate rules. What I meant when I said aggregate is that if you have a contiguous block of IPs, say 1.2.3.1 through 1.2.3.63, most need ports 22, 25, 80, and 443 open, then create one rule: pass tcp from any to 1.2.3.0/26 22,25,80,443 Then turn on the tcp.blackhole sysctl on the machines and you have the same effect with just one rule instead of 60 or configure firewalls with just two rules: allow tcp from any to me porta,portb,portc allow tcp from me to any To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 19: 1:40 2003 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 E870737B401 for ; Sun, 19 Jan 2003 19:01:39 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id B67B243E4A for ; Sun, 19 Jan 2003 19:01:37 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 300C08115; Sun, 19 Jan 2003 19:04:22 -0800 (PST) Date: Sun, 19 Jan 2003 19:04:22 -0800 From: Arun Sharma To: Terry Lambert Cc: hackers@freebsd.org Subject: Re: listing sysinit order ? Message-ID: <20030120030421.GA3176@sharma-home.net> References: <20030118203706.GA21624@sharma-home.net> <3E29D775.EA2323A9@mindspring.com> <3E29DDDB.6000906@sharma-home.net> <3E2AA0A9.C8386AED@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E2AA0A9.C8386AED@mindspring.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 Sun, Jan 19, 2003 at 04:57:13AM -0800, Terry Lambert wrote: > You will get the information you seem to be asking for (unless I'm > misunderstanding you, and you are trying to lead upo asking for a > string identifier, and for some reason you don't want to come out > and ask for a modification of the SYSINIT macro, for some reason...). That may be the right thing to do. I was worried about the unnecessary bloat it would add to a non-debug kernel. However, I figured that I was barking up the wrong tree. To debug driver initialization hangs, I need to put printfs in kern/subr_bus.c, not the sysinit code. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 22:48: 2 2003 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 8CE4A37B401 for ; Sun, 19 Jan 2003 22:48:01 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F63B43ED8 for ; Sun, 19 Jan 2003 22:48:01 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0314.cvx22-bradley.dialup.earthlink.net ([209.179.199.59] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18aVis-00045O-00; Sun, 19 Jan 2003 22:47:55 -0800 Message-ID: <3E2B9AEE.AF897AAB@mindspring.com> Date: Sun, 19 Jan 2003 22:45:02 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Arun Sharma Cc: hackers@freebsd.org Subject: Re: listing sysinit order ? References: <20030118203706.GA21624@sharma-home.net> <3E29D775.EA2323A9@mindspring.com> <3E29DDDB.6000906@sharma-home.net> <3E2AA0A9.C8386AED@mindspring.com> <20030120030421.GA3176@sharma-home.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c6afcb7a505719c55bc40a11bc65601a666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c 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 Arun Sharma wrote: > On Sun, Jan 19, 2003 at 04:57:13AM -0800, Terry Lambert wrote: > > You will get the information you seem to be asking for (unless I'm > > misunderstanding you, and you are trying to lead upo asking for a > > string identifier, and for some reason you don't want to come out > > and ask for a modification of the SYSINIT macro, for some reason...). > > That may be the right thing to do. I was worried about the unnecessary > bloat it would add to a non-debug kernel. > > However, I figured that I was barking up the wrong tree. To debug driver > initialization hangs, I need to put printfs in kern/subr_bus.c, not the > sysinit code. SYSINIT would at least get you to where it's hanging, and you may not need information over and above that, FWIW. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 22:53:24 2003 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 42CC237B401 for ; Sun, 19 Jan 2003 22:53:23 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDB6843F18 for ; Sun, 19 Jan 2003 22:53:22 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 41BC180D6; Sun, 19 Jan 2003 22:56:14 -0800 (PST) Date: Sun, 19 Jan 2003 22:56:14 -0800 From: Arun Sharma To: hackers@freebsd.org Subject: verbose device probing ? Message-ID: <20030120065614.GA4212@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Having just spent 5 hours debugging a silent hang in EISA bus probe (even with boot -v) I'm tempted to ask, why doesn't device_probe_and_attach explicitly announce the device it's going to probe if bootverbose is set ? Thought I'd ask here before I submit a PR. -Arun BTW: There seem to be 30+ critical + 130+ serious bugs against 5.0 at the time of its release. Are developers looking at the gnats db at all ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 19 23: 3: 1 2003 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 00CDC37B401 for ; Sun, 19 Jan 2003 23:03:01 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61C3E43F43 for ; Sun, 19 Jan 2003 23:03:00 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id B98D480D6; Sun, 19 Jan 2003 23:05:51 -0800 (PST) Date: Sun, 19 Jan 2003 23:05:51 -0800 From: Arun Sharma To: Terry Lambert Cc: hackers@freebsd.org Subject: Re: listing sysinit order ? Message-ID: <20030120070551.GA4293@sharma-home.net> References: <20030118203706.GA21624@sharma-home.net> <3E29D775.EA2323A9@mindspring.com> <3E29DDDB.6000906@sharma-home.net> <3E2AA0A9.C8386AED@mindspring.com> <20030120030421.GA3176@sharma-home.net> <3E2B9AEE.AF897AAB@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E2B9AEE.AF897AAB@mindspring.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 Sun, Jan 19, 2003 at 10:45:02PM -0800, Terry Lambert wrote: > > SYSINIT would at least get you to where it's hanging, and you > may not need information over and above that, FWIW. Well, knowing that the kernel hangs in a function called "configure" (SI_SUB_CONFIGURE, SI_ORDER_THIRD) isn't terribly useful. However, knowing that it specifically hangs in eisa_probe() is useful. Also, see the mail I just sent to -hackers about making device_probe_and_attach verbose if bootverbose is set. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 3:19:27 2003 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 DE73F37B401 for ; Mon, 20 Jan 2003 03:19:25 -0800 (PST) Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ADE343F18 for ; Mon, 20 Jan 2003 03:19:24 -0800 (PST) (envelope-from flynn@energyhq.homeip.net) Received: from christine.energyhq.tk (christine.energyhq.tk [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id A3414AF5A6 for ; Mon, 20 Jan 2003 12:19:21 +0100 (CET) Date: Mon, 20 Jan 2003 12:18:51 +0100 From: Miguel Mendez To: hackers@freebsd.org Subject: RFC: Adding a new (safer) data entry function to libdialog Message-Id: <20030120121851.30ff961f.flynn@energyhq.homeip.net> X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386-portbld-freebsd5.0) X-Face: 1j}k*2E>Y\+C~E|/wehi[:dCM,{N7/uE 3o# P,{t7gA/qnovFDDuyQV.1hdT7&#d)q"xY33}{_GS>kk'S{O]nE$A`T|\4&p\&mQyexOLb8}FO List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=.bazDYk+xshb?Om Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello hackers, Currently, when one wants the user to enter data in a libdialog based program, one uses the following function: int dialog_inputbox(unsigned char *title, unsigned char *prompt, int height, int width, unsigned char *result); The problem this routine has, is that there's nowhere to specify the max length of the input buffer (think gets vs fgets here). I know that not many programs use this lib, or even if there are plans to EOL it, but this change could be helpful IMHO. My suggestion is to create a new function, e.g, dialog_inputbox_n that would let you specify the length of the input buffer. Comments? Ideas? If people find it useful I can come with patches, since the implementation would be trivial. Cheers, -- Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! --=.bazDYk+xshb?Om Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+K9sfnLctrNyFFPERAs6rAKCbS1HupNDL3zTAaUEvh+qjsfVUOACffRoa Q4wPXJUpDPpjHoMK61DIR6g= =jSHK -----END PGP SIGNATURE----- --=.bazDYk+xshb?Om-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 6:52:13 2003 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 D538B37B401 for ; Mon, 20 Jan 2003 06:52:11 -0800 (PST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1160D43F13 for ; Mon, 20 Jan 2003 06:52:07 -0800 (PST) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id h0KEq5Aq022800 for ; Mon, 20 Jan 2003 15:52:05 +0100 Received: (nullmailer pid 4947 invoked by uid 1000); Mon, 20 Jan 2003 14:52:05 -0000 Date: Mon, 20 Jan 2003 15:52:05 +0100 From: Mark Santcroos To: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030120145205.GA4911@laptop.6bone.nl> References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030117232729.GA5908@HAL9000.homeunix.com> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE 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, Jan 17, 2003 at 03:27:29PM -0800, David Schultz wrote: > Thus spake Mark Santcroos : > > in : > > extern int nswap; /* size of swap space */ > > > > in : > > static int nswap; /* first block after the interleaved devs */ > > > > Is the extern pointing to this variable? (It seems so, don't see any other > > such variable in the three) > > If so, is there any problem with making nswap non-static? > > It's a constant that is only relevant to the management of the > swap allocation bitmap, so it is properly static. It shouldn't be > declared in sys/systm.h. I need to get access to the swap interface. More precisely, I want to turn it off. Either some of the values and functions need to be made global or the interface should be changed. I need this for software suspending on which I am working. (Page in processes and turn off swap devices before I write out the memory to it) Is it worth my time to produce patches that change the swapoff interface? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 8:33:28 2003 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 BD10637B401 for ; Mon, 20 Jan 2003 08:33:26 -0800 (PST) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27DB743EB2 for ; Mon, 20 Jan 2003 08:33:18 -0800 (PST) (envelope-from bmah@employees.org) Received: from bmah.dyndns.org (12-240-204-110.client.attbi.com[12.240.204.110]) by sccrmhc01.attbi.com (sccrmhc01) with ESMTP id <2003012016331200100hqkt2e>; Mon, 20 Jan 2003 16:33:12 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.6/8.12.6) with ESMTP id h0KGXAA8087837; Mon, 20 Jan 2003 08:33:10 -0800 (PST) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.6/8.12.6/Submit) id h0KGX9B9087836; Mon, 20 Jan 2003 08:33:09 -0800 (PST) Message-Id: <200301201633.h0KGX9B9087836@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20021120 with nmh-1.0.4 To: Arun Sharma Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? In-Reply-To: <20030120065614.GA4212@sharma-home.net> References: <20030120065614.GA4212@sharma-home.net> Comments: In-reply-to Arun Sharma message dated "Sun, 19 Jan 2003 22:56:14 -0800." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_567580200P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 20 Jan 2003 08:33:09 -0800 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 --==_Exmh_567580200P Content-Type: text/plain; charset=us-ascii If memory serves me right, Arun Sharma wrote: > BTW: There seem to be 30+ critical + 130+ serious bugs against 5.0 at > the time of its release. Are developers looking at the gnats db at all ? Yes. Bruce. PS. I personally ignore the severity and priority fields of PRs. The importance of many PRs I've dealt with is very much inflated. --==_Exmh_567580200P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) Comment: Exmh version 2.5+ 20020506 iD8DBQE+LCTE2MoxcVugUsMRAtTCAJ9/aaCVqwQokaaUmXQoFCLiEUDV6ACg+zA4 ndD8Eobn6/wXVxbtg6eYF7g= =g4AG -----END PGP SIGNATURE----- --==_Exmh_567580200P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 11: 9:40 2003 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 CAA5D37B401 for ; Mon, 20 Jan 2003 11:09:38 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2BE43F18 for ; Mon, 20 Jan 2003 11:09:38 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0KJ9b0L003212; Mon, 20 Jan 2003 11:09:37 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0KJ9aSw003211; Mon, 20 Jan 2003 11:09:36 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Mon, 20 Jan 2003 11:09:36 -0800 From: David Schultz To: Mark Santcroos Cc: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030120190936.GA3192@HAL9000.homeunix.com> Mail-Followup-To: Mark Santcroos , hackers@FreeBSD.ORG References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> <20030120145205.GA4911@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030120145205.GA4911@laptop.6bone.nl> 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 Thus spake Mark Santcroos : > On Fri, Jan 17, 2003 at 03:27:29PM -0800, David Schultz wrote: > > Thus spake Mark Santcroos : > > > in : > > > extern int nswap; /* size of swap space */ > > > > > > in : > > > static int nswap; /* first block after the interleaved devs */ > > > > > > Is the extern pointing to this variable? (It seems so, don't see any other > > > such variable in the three) > > > If so, is there any problem with making nswap non-static? > > > > It's a constant that is only relevant to the management of the > > swap allocation bitmap, so it is properly static. It shouldn't be > > declared in sys/systm.h. > > I need to get access to the swap interface. More precisely, I want to turn > it off. > > Either some of the values and functions need to be made global or the > interface should be changed. > > I need this for software suspending on which I am working. (Page in processes > and turn off swap devices before I write out the memory to it) > > Is it worth my time to produce patches that change the swapoff interface? What exactly do you need to change about the swapoff interface? Unless you're trying to write a module, anything that's going to be invasive into the swap subsystem's data structures probably belongs in vm_swap.c. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 17:59:50 2003 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 DF79637B401 for ; Mon, 20 Jan 2003 17:59:48 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-106-179.dsl.lsan03.pacbell.net [64.169.106.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F2B443ED8 for ; Mon, 20 Jan 2003 17:59:48 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id DF73766B60; Mon, 20 Jan 2003 17:59:47 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id B656F163D; Mon, 20 Jan 2003 17:59:47 -0800 (PST) Date: Mon, 20 Jan 2003 17:59:47 -0800 From: Kris Kennaway To: Miguel Mendez Cc: hackers@freebsd.org Subject: Re: RFC: Adding a new (safer) data entry function to libdialog Message-ID: <20030121015947.GA7310@rot13.obsecurity.org> References: <20030120121851.30ff961f.flynn@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <20030120121851.30ff961f.flynn@energyhq.homeip.net> 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 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 20, 2003 at 12:18:51PM +0100, Miguel Mendez wrote: > Hello hackers, >=20 > Currently, when one wants the user to enter data in a libdialog based > program, one uses the following function: >=20 > int > dialog_inputbox(unsigned char *title, unsigned char *prompt, > int height, int width, unsigned char *result); >=20 > The problem this routine has, is that there's nowhere to specify the max > length of the input buffer (think gets vs fgets here). I know that not > many programs use this lib, or even if there are plans to EOL it, but > this change could be helpful IMHO. My suggestion is to create a new > function, e.g, dialog_inputbox_n that would let you specify the length > of the input buffer. Comments? Ideas? If people find it useful I can > come with patches, since the implementation would be trivial. libdialog is rife with overflowable buffers..I'm not sure it would be safe even with this input method. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LKmTWry0BWjoQKURAnDTAKDLuIkDvNAQv3+cbAAyL3KhNQ3RyACgvfyD BwCEyACQtzfwWTSN/lOUzJ0= =WLns -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 21:14:24 2003 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 571C437B401; Mon, 20 Jan 2003 21:14:23 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 787A743F1E; Mon, 20 Jan 2003 21:14:22 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id B65AC8115; Mon, 20 Jan 2003 21:17:13 -0800 (PST) Date: Mon, 20 Jan 2003 21:17:13 -0800 From: Arun Sharma To: "Bruce A. Mah" Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? Message-ID: <20030121051713.GA12845@sharma-home.net> References: <20030120065614.GA4212@sharma-home.net> <200301201633.h0KGX9B9087836@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200301201633.h0KGX9B9087836@intruder.bmah.org> 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 Mon, Jan 20, 2003 at 08:33:09AM -0800, Bruce A. Mah wrote: > > PS. I personally ignore the severity and priority fields of PRs. The > importance of many PRs I've dealt with is very much inflated. > Perhaps you should change the severity field to a lower level then ? Or is there a different problem (such as lack of good tools) that prevent you from doing that ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 20 21:50:23 2003 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 7049337B401; Mon, 20 Jan 2003 21:50:22 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 104EE43F18; Mon, 20 Jan 2003 21:50:22 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 4196E8115; Mon, 20 Jan 2003 21:53:19 -0800 (PST) Date: Mon, 20 Jan 2003 21:53:19 -0800 From: Arun Sharma To: FreeBSD-gnats-submit@freebsd.org Cc: hackers@freebsd.org Subject: device probing not verbose when using boot -v Message-ID: <20030121055319.GA13113@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 >Submitter-Id: current-users >Originator: Arun Sharma >Organization: >Confidential: no >Synopsis: device probing not verbose when using boot -v >Severity: >Priority: >Category: kern >Class: sw-bug >Release: FreeBSD 5.0 i386 >Environment: When FreeBSD has trouble booting on some hardware, the lockup is silent and leaves no clues about where the hang is happening, even if the user is using boot -v. This makes it very hard for a tester to report meaningful bugs. Specific case in question: kern/44619. The hang was in eisa_probe, but the kernel messages don't provide a clue. So the proposal is to print the name of the device being probed and attached before attempting to do it in kern/subr_bus.c:device_probe_and_attach() if (bootverbose) is set. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 0: 3:40 2003 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 9657737B401 for ; Tue, 21 Jan 2003 00:03:39 -0800 (PST) Received: from priv-edtnes61.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C256043F5B for ; Tue, 21 Jan 2003 00:03:38 -0800 (PST) (envelope-from sh@bel.bc.ca) Received: from reason ([216.232.192.156]) by priv-edtnes61.telusplanet.net (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP id <20030121080333.SVVO7527.priv-edtnes61.telusplanet.net@reason> for ; Tue, 21 Jan 2003 01:03:33 -0700 Message-ID: <002101c2c123$9a4d2b80$9cc0e8d8@slugabed.org> From: "Sean Hamilton" To: Subject: kldload random.ko panic Date: Tue, 21 Jan 2003 00:03:37 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 Greetings, Running 5.0-RELEASE, # kldload random induces a panic, presumably unless it is not compiled into the kernel. sh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 0:41:28 2003 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 8F25937B401 for ; Tue, 21 Jan 2003 00:41:26 -0800 (PST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id E372E43F3F for ; Tue, 21 Jan 2003 00:41:24 -0800 (PST) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id h0L8fNAq018746 for ; Tue, 21 Jan 2003 09:41:23 +0100 Received: (nullmailer pid 938 invoked by uid 1000); Tue, 21 Jan 2003 07:41:28 -0000 Date: Tue, 21 Jan 2003 08:41:28 +0100 From: Mark Santcroos To: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030121074128.GA880@laptop.6bone.nl> References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> <20030120145205.GA4911@laptop.6bone.nl> <20030120190936.GA3192@HAL9000.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030120190936.GA3192@HAL9000.homeunix.com> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE 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, Jan 20, 2003 at 11:09:36AM -0800, David Schultz wrote: > What exactly do you need to change about the swapoff interface? > Unless you're trying to write a module, anything that's going to > be invasive into the swap subsystem's data structures probably > belongs in vm_swap.c. Yes, that is also what I meant. We now have a swapoff() system call that does all the work itself. My idea was to split that up: /* turn of swap device */ static int swapoff_one(struct swdevt *sp) { /* Do all things that we don't want to know about outside this function */ } /* turn off all swap devices */ int swapoff_all() { int index; struct swdevt *sp; for (sp = swdevt, index = 0; index < nswdev; index++, sp++) swapoff_one(sp); } So the swapoff() system call would call swapoff_one() and my code in kern/kern_swsuspend.c would call swapoff_all(). Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 1:15:44 2003 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 EC15237B401 for ; Tue, 21 Jan 2003 01:15:42 -0800 (PST) Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 181DC43ED8 for ; Tue, 21 Jan 2003 01:15:41 -0800 (PST) (envelope-from flynn@energyhq.homeip.net) Received: from christine.energyhq.tk (christine.energyhq.tk [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id CDD63AF5A6; Tue, 21 Jan 2003 10:15:34 +0100 (CET) Date: Tue, 21 Jan 2003 10:15:02 +0100 From: Miguel Mendez To: Kris Kennaway Cc: hackers@freebsd.org Subject: Re: RFC: Adding a new (safer) data entry function to libdialog Message-Id: <20030121101502.049abd8e.flynn@energyhq.homeip.net> In-Reply-To: <20030121015947.GA7310@rot13.obsecurity.org> References: <20030120121851.30ff961f.flynn@energyhq.homeip.net> <20030121015947.GA7310@rot13.obsecurity.org> X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386-portbld-freebsd5.0) X-Face: 1j}k*2E>Y\+C~E|/wehi[:dCM,{N7/uE 3o# P,{t7gA/qnovFDDuyQV.1hdT7&#d)q"xY33}{_GS>kk'S{O]nE$A`T|\4&p\&mQyexOLb8}FO List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=.FFp0jP1l_YaCs( Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 20 Jan 2003 17:59:47 -0800 Kris Kennaway wrote: >> [making libdialog safer } > libdialog is rife with overflowable buffers..I'm not sure it would be > safe even with this input method. Okay, I have another idea that might be a bit more productive, since the code in libdialog seems to be nothing but a huge hack. How about adopting tvision to replace dialog(3)? Libh uses tvision, and I've thought about writing a small API compat glue (libtdialog.{so,a}) that would allow legacy libdialog code to be linked with tvision without modification. The only (big) drawback I see in tvision is that it's in C++, otherwise is lightyears ahead of what dialog(3) currently offers. -- Cheers, Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! --=.FFp0jP1l_YaCs( Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LQ+anLctrNyFFPERAoEyAJ4yRiRMFwxaoogx3ngpaQRrhF+POgCfRp2R Zo2Mxh7wJv6fE4kuZKmuSnY= =w+bY -----END PGP SIGNATURE----- --=.FFp0jP1l_YaCs(-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 1:33: 4 2003 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 6752C37B401 for ; Tue, 21 Jan 2003 01:33:03 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id B532143F18 for ; Tue, 21 Jan 2003 01:33:02 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0L9X10L006620; Tue, 21 Jan 2003 01:33:01 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0L9X1t2006619; Tue, 21 Jan 2003 01:33:01 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 21 Jan 2003 01:33:01 -0800 From: David Schultz To: Mark Santcroos Cc: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030121093301.GB6497@HAL9000.homeunix.com> Mail-Followup-To: Mark Santcroos , hackers@FreeBSD.ORG References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> <20030120145205.GA4911@laptop.6bone.nl> <20030120190936.GA3192@HAL9000.homeunix.com> <20030121074128.GA880@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030121074128.GA880@laptop.6bone.nl> 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 Thus spake Mark Santcroos : > Yes, that is also what I meant. We now have a swapoff() system call that > does all the work itself. > > My idea was to split that up: > > /* turn of swap device */ > static int swapoff_one(struct swdevt *sp) > { > /* Do all things that we don't want to know about outside this function > */ > } > > /* turn off all swap devices */ > int swapoff_all() > { > int index; > struct swdevt *sp; > > for (sp = swdevt, index = 0; index < nswdev; index++, sp++) > swapoff_one(sp); > } > > So the swapoff() system call would call swapoff_one() and my code in > kern/kern_swsuspend.c would call swapoff_all(). See swapoff(8), in particular the -a flag. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 1:39:44 2003 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 56F6837B401 for ; Tue, 21 Jan 2003 01:39:43 -0800 (PST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7080143F13 for ; Tue, 21 Jan 2003 01:39:42 -0800 (PST) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id h0L9dfAq000908 for ; Tue, 21 Jan 2003 10:39:41 +0100 Received: (nullmailer pid 1697 invoked by uid 1000); Tue, 21 Jan 2003 09:39:42 -0000 Date: Tue, 21 Jan 2003 10:39:42 +0100 From: Mark Santcroos To: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030121093942.GD620@laptop.6bone.nl> References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> <20030120145205.GA4911@laptop.6bone.nl> <20030120190936.GA3192@HAL9000.homeunix.com> <20030121074128.GA880@laptop.6bone.nl> <20030121093301.GB6497@HAL9000.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030121093301.GB6497@HAL9000.homeunix.com> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE 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 Tue, Jan 21, 2003 at 01:33:01AM -0800, David Schultz wrote: > Thus spake Mark Santcroos : > > Yes, that is also what I meant. We now have a swapoff() system call that > > does all the work itself. > > > > My idea was to split that up: > > > > /* turn of swap device */ > > static int swapoff_one(struct swdevt *sp) > > { > > /* Do all things that we don't want to know about outside this function > > */ > > } > > > > /* turn off all swap devices */ > > int swapoff_all() > > { > > int index; > > struct swdevt *sp; > > > > for (sp = swdevt, index = 0; index < nswdev; index++, sp++) > > swapoff_one(sp); > > } > > > > So the swapoff() system call would call swapoff_one() and my code in > > kern/kern_swsuspend.c would call swapoff_all(). > > See swapoff(8), in particular the -a flag. I'm aware of that, but imho it doesn't suite my purpose. Are you strongly against having such code inside the kernel? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 1:44: 9 2003 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 4184837B401 for ; Tue, 21 Jan 2003 01:44:08 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-106-48.dsl.lsan03.pacbell.net [64.169.106.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5554543ED8 for ; Tue, 21 Jan 2003 01:44:07 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 2E32166B60; Tue, 21 Jan 2003 01:44:06 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 130F58DE; Tue, 21 Jan 2003 01:44:05 -0800 (PST) Date: Tue, 21 Jan 2003 01:44:05 -0800 From: Kris Kennaway To: Miguel Mendez Cc: Kris Kennaway , hackers@freebsd.org Subject: Re: RFC: Adding a new (safer) data entry function to libdialog Message-ID: <20030121094405.GA21197@rot13.obsecurity.org> References: <20030120121851.30ff961f.flynn@energyhq.homeip.net> <20030121015947.GA7310@rot13.obsecurity.org> <20030121101502.049abd8e.flynn@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20030121101502.049abd8e.flynn@energyhq.homeip.net> 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 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2003 at 10:15:02AM +0100, Miguel Mendez wrote: > On Mon, 20 Jan 2003 17:59:47 -0800 > Kris Kennaway wrote: >=20 > >> [making libdialog safer } > > libdialog is rife with overflowable buffers..I'm not sure it would be > > safe even with this input method. >=20 > Okay, I have another idea that might be a bit more productive, since the > code in libdialog seems to be nothing but a huge hack. How about > adopting tvision to replace dialog(3)? Libh uses tvision, and I've > thought about writing a small API compat glue (libtdialog.{so,a}) that > would allow legacy libdialog code to be linked with tvision without > modification. The only (big) drawback I see in tvision is that it's in > C++, otherwise is lightyears ahead of what dialog(3) currently offers. That could be quite a worthwhile project. Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LRZlWry0BWjoQKURAhlwAKDVgi0ev3/dVK7kAXM5tOT3aJMJWACeMbxp cFfV7NogSJMDGkd/Fyxu4mg= =96wu -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 1:58:11 2003 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 F3DCC37B401 for ; Tue, 21 Jan 2003 01:58:09 -0800 (PST) Received: from postal.sdsc.edu (postal.sdsc.edu [132.249.20.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84B1343E4A for ; Tue, 21 Jan 2003 01:58:08 -0800 (PST) (envelope-from okumoto@ucsd.edu) Received: from multivac.sdsc.edu (IDENT:u2l2y5XuI4aI/m+/dCcsA37n6GpzX02f@multivac.sdsc.edu [132.249.20.57]) by postal.sdsc.edu (8.11.6/8.11.6/server/51) with ESMTP id h0L9vbK10797; Tue, 21 Jan 2003 01:57:37 -0800 (PST) Received: by multivac (8.11.6+Sun/1.11-SolarisClient) id h0L9vaq05562; Tue, 21 Jan 2003 01:57:36 -0800 (PST) To: Kris Kennaway Cc: Miguel Mendez , hackers@FreeBSD.ORG Subject: Re: RFC: Adding a new (safer) data entry function to libdialog References: <20030120121851.30ff961f.flynn@energyhq.homeip.net> <20030121015947.GA7310@rot13.obsecurity.org> <20030121101502.049abd8e.flynn@energyhq.homeip.net> <20030121094405.GA21197@rot13.obsecurity.org> From: Max Okumoto Date: 21 Jan 2003 01:57:36 -0800 In-Reply-To: <20030121094405.GA21197@rot13.obsecurity.org> Message-ID: Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 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 Kris Kennaway writes: > On Tue, Jan 21, 2003 at 10:15:02AM +0100, Miguel Mendez wrote: > > On Mon, 20 Jan 2003 17:59:47 -0800 Kris Kennaway wrote: > > >> [making libdialog safer } > > > libdialog is rife with overflowable buffers..I'm not sure it would be > > > safe even with this input method. > > > > Okay, I have another idea that might be a bit more productive, since the > > code in libdialog seems to be nothing but a huge hack. How about > > adopting tvision to replace dialog(3)? Libh uses tvision, and I've > > thought about writing a small API compat glue (libtdialog.{so,a}) that > > would allow legacy libdialog code to be linked with tvision without > > modification. The only (big) drawback I see in tvision is that it's in > > C++, otherwise is lightyears ahead of what dialog(3) currently offers. > > That could be quite a worthwhile project. > > Kris There are alot of problems in the tvision library too. I made the patch that 'allows' it to compile with gcc3.2.1. I did not correct the problems in the since I am trying to focus on libh. Max Okumoto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 3: 8:37 2003 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 16DD037B401 for ; Tue, 21 Jan 2003 03:08:36 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58B4A43F5F for ; Tue, 21 Jan 2003 03:08:35 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0LB8Y0L007216; Tue, 21 Jan 2003 03:08:34 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0LB8YCY007215; Tue, 21 Jan 2003 03:08:34 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 21 Jan 2003 03:08:34 -0800 From: David Schultz To: Mark Santcroos Cc: hackers@FreeBSD.ORG Subject: Re: nswap Message-ID: <20030121110834.GA6842@HAL9000.homeunix.com> Mail-Followup-To: Mark Santcroos , hackers@FreeBSD.ORG References: <20030117000917.GA7277@laptop.6bone.nl> <20030117232729.GA5908@HAL9000.homeunix.com> <20030120145205.GA4911@laptop.6bone.nl> <20030120190936.GA3192@HAL9000.homeunix.com> <20030121074128.GA880@laptop.6bone.nl> <20030121093301.GB6497@HAL9000.homeunix.com> <20030121093942.GD620@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030121093942.GD620@laptop.6bone.nl> 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 Thus spake Mark Santcroos : > On Tue, Jan 21, 2003 at 01:33:01AM -0800, David Schultz wrote: > > Thus spake Mark Santcroos : > > > Yes, that is also what I meant. We now have a swapoff() system call that > > > does all the work itself. > > > > > > My idea was to split that up: > > > > > > /* turn of swap device */ > > > static int swapoff_one(struct swdevt *sp) > > > { > > > /* Do all things that we don't want to know about outside this function > > > */ > > > } > > > > > > /* turn off all swap devices */ > > > int swapoff_all() > > > { > > > int index; > > > struct swdevt *sp; > > > > > > for (sp = swdevt, index = 0; index < nswdev; index++, sp++) > > > swapoff_one(sp); > > > } > > > > > > So the swapoff() system call would call swapoff_one() and my code in > > > kern/kern_swsuspend.c would call swapoff_all(). > > > > See swapoff(8), in particular the -a flag. > > I'm aware of that, but imho it doesn't suite my purpose. Are you strongly > against having such code inside the kernel? In that case, I'm not sure I understand what you're trying to do. There's already a sysctl interface to get the names of all the swap devices in the system, and from there you can call swapoff(2) on each one. Anyway, it doesn't really bother me to add similar functionality to the kernel if that seems useful, but it's also not my decision. Perhaps if you posted patches, someone could make more specific comments. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 8:26:20 2003 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 61F1137B401; Tue, 21 Jan 2003 08:26:18 -0800 (PST) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F92043ED8; Tue, 21 Jan 2003 08:26:17 -0800 (PST) (envelope-from bmah@employees.org) Received: from bmah.dyndns.org (12-240-204-110.client.attbi.com[12.240.204.110]) by sccrmhc01.attbi.com (sccrmhc01) with ESMTP id <2003012116261100100hpjobe>; Tue, 21 Jan 2003 16:26:11 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.6/8.12.6) with ESMTP id h0LGQAA8001308; Tue, 21 Jan 2003 08:26:10 -0800 (PST) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.6/8.12.6/Submit) id h0LGQ88B001307; Tue, 21 Jan 2003 08:26:08 -0800 (PST) Message-Id: <200301211626.h0LGQ88B001307@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20021120 with nmh-1.0.4 To: Arun Sharma Cc: "Bruce A. Mah" , hackers@FreeBSD.ORG Subject: Re: verbose device probing ? In-Reply-To: <20030121051713.GA12845@sharma-home.net> References: <20030120065614.GA4212@sharma-home.net> <200301201633.h0KGX9B9087836@intruder.bmah.org> <20030121051713.GA12845@sharma-home.net> Comments: In-reply-to Arun Sharma message dated "Mon, 20 Jan 2003 21:17:13 -0800." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_2074436656P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 21 Jan 2003 08:26:08 -0800 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 --==_Exmh_2074436656P Content-Type: text/plain; charset=us-ascii If memory serves me right, Arun Sharma wrote: > On Mon, Jan 20, 2003 at 08:33:09AM -0800, Bruce A. Mah wrote: > > > > PS. I personally ignore the severity and priority fields of PRs. The > > importance of many PRs I've dealt with is very much inflated. > > > > Perhaps you should change the severity field to a lower level then ? Or > is there a different problem (such as lack of good tools) that prevent you > from doing that ? The severity and priority fields can be changed manually but that doesn't solve the problem that relying on the user-specified severity and priority fields for anything meaningful just doesn't work. The only point that I was trying to make with my comment was that you shouldn't place much weight on the contents of the severity and priority fields in the database. Bruce. --==_Exmh_2074436656P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) Comment: Exmh version 2.5+ 20020506 iD8DBQE+LXSg2MoxcVugUsMRAr4OAJ43Chdu4w3VW5lioGSTl5VihyYNugCeNK7Y +2MXHm4+zuEFn3ti+zfk1Jg= =uX6z -----END PGP SIGNATURE----- --==_Exmh_2074436656P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 9:36:51 2003 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 AB88937B401; Tue, 21 Jan 2003 09:36:50 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D5C43F1E; Tue, 21 Jan 2003 09:36:48 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id B840E8115; Tue, 21 Jan 2003 09:39:43 -0800 (PST) Date: Tue, 21 Jan 2003 09:39:43 -0800 From: Arun Sharma To: "Bruce A. Mah" Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? Message-ID: <20030121173943.GA18856@sharma-home.net> References: <20030120065614.GA4212@sharma-home.net> <200301201633.h0KGX9B9087836@intruder.bmah.org> <20030121051713.GA12845@sharma-home.net> <200301211626.h0LGQ88B001307@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200301211626.h0LGQ88B001307@intruder.bmah.org> 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 Tue, Jan 21, 2003 at 08:26:08AM -0800, Bruce A. Mah wrote: > > The severity and priority fields can be changed manually but that > doesn't solve the problem that relying on the user-specified severity > and priority fields for anything meaningful just doesn't work. > If you override the user-specified severity manually, you're no longer relying on the user-specified field. But yes, that means more work for the developer responsible for looking at incoming bugs and assigning them. All I'm trying to do here is to find a good channel to raise my issues. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 14:59: 1 2003 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 33EB137B401 for ; Tue, 21 Jan 2003 14:59:00 -0800 (PST) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 045D343ED8 for ; Tue, 21 Jan 2003 14:58:59 -0800 (PST) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.5/8.12.5) with ESMTP id h0LMwtTJ078790; Wed, 22 Jan 2003 01:58:56 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 22 Jan 2003 01:58:55 +0300 (MSK) From: Dmitry Morozovsky To: Darren Pilgrim Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD firewall for high profile hosts - waste of time ? In-Reply-To: <3E2B4953.7060008@pantherdragon.org> Message-ID: <20030122015428.E77616@woozle.rinet.ru> References: <20030116124254.J9642-100000@mail.econolodgetulsa.com> <3E2738BA.4090806@pantherdragon.org> <20030119001015.S46739@woozle.rinet.ru> <3E2B4953.7060008@pantherdragon.org> X-NCC-RegID: ru.rinet 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 Sun, 19 Jan 2003, Darren Pilgrim wrote: [snip-a-bit] DP> > By the way, is (moderately complex) aggregated rule faster than mix of simple DP> > rules? (for now, we drop accounting issues) DP> > DP> I'm not sure if the {a.b.c.0/24 or e.f.g.0/20} part is valid, but in theory DP> this rule should require fewer ops on average than 8 seperate rules. What I DP> meant when I said aggregate is that if you have a contiguous block of IPs, DP> say 1.2.3.1 through 1.2.3.63, most need ports 22, 25, 80, and 443 open, then DP> create one rule: DP> DP> pass tcp from any to 1.2.3.0/26 22,25,80,443 Yeah, I suppose we both got the point ;-) The only side note I have for now is: it would be _extremely_ useful to describe firewall tuning either in firewall.7 or security.7 or even excplicit manpage as well as bring it under attention into the Handbook. However, not being native speaker and/or kernel deep-knowledge-man, /me just silently crouches into his corner ;-) Anyway, thank you all the Crew and congrats for 5.0 releasing! Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 15: 4:56 2003 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 3AB2337B405; Tue, 21 Jan 2003 15:04:54 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id A76C343F13; Tue, 21 Jan 2003 15:04:53 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0183.cvx40-bradley.dialup.earthlink.net ([216.244.42.183] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18b7Rr-0001OK-00; Tue, 21 Jan 2003 15:04:52 -0800 Message-ID: <3E2DD1C0.3D0ED169@mindspring.com> Date: Tue, 21 Jan 2003 15:03:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: bmah@FreeBSD.ORG Cc: Arun Sharma , hackers@FreeBSD.ORG Subject: Re: verbose device probing ? References: <20030120065614.GA4212@sharma-home.net> <200301201633.h0KGX9B9087836@intruder.bmah.org> <20030121051713.GA12845@sharma-home.net> <200301211626.h0LGQ88B001307@intruder.bmah.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c1d7a7c200bf7d32dab5b25f5d35af4b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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 "Bruce A. Mah" wrote: > If memory serves me right, Arun Sharma wrote: > > On Mon, Jan 20, 2003 at 08:33:09AM -0800, Bruce A. Mah wrote: > > > PS. I personally ignore the severity and priority fields of PRs. The > > > importance of many PRs I've dealt with is very much inflated. > > > > > > > Perhaps you should change the severity field to a lower level then ? Or > > is there a different problem (such as lack of good tools) that prevent you > > from doing that ? > > The severity and priority fields can be changed manually but that > doesn't solve the problem that relying on the user-specified severity > > The only point that I was trying to make with my comment was that you > shouldn't place much weight on the contents of the severity and priority > fields in the database. > and priority fields for anything meaningful just doesn't work. I would go much, much farther than that... Users should not be setting priority fields, period. The severity they set can be revised, if necessary. But mostly, it will be ignored by the people who do the work, who will end up working on whatever the hell they want to, anyway, and screw priority, severity, and anything else, unless the person who is filing the report is their IRC buddy (in which case, there was probably never a report filed, and the communication was, instead, something like "UR C0D3 SUX, L9M3R FIX IT K PLZ THX"). The priority field is rather ridiculous, in a volunteer project, at least one that does not have some sort of scheduling enforcement (i.e. one could envision a system where all changes must have PR's associated with them, and priority was assigned by consensus through the email moral equivalent of a "manager's meeting", and people were not permitted to check in priority N items, if there were any PR's of priority > N+1 outstanding, etc.). FreeBSD does not have these rules in place, and, as Brett Glass is maybe finally noticing, once established, adding or changing rules is a hairy three-toed bitch. 8-) 8-). What this boils down to for FreeBSD is that priority is not relevent, unless the person doing the work sets it in order to create ordering of items in their own personal "to do" list. Even so, there is no requirement for that person to spend their time in descending priority order, and assignment of problems to yourself is voluntary (in fact, there are many people who work on FreeBSD by partially completing something to the point that it has everything they personally require, and then letting the actual finish work trickle in over months or years -- either done by someone else, or done by them, only when someone threatens to back out their changes). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 16: 9:30 2003 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 EDA7C37B401; Tue, 21 Jan 2003 16:09:28 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF5BE43F5B; Tue, 21 Jan 2003 16:09:27 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h0M09POs033357; Wed, 22 Jan 2003 02:09:26 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.12.3/8.12.3/Submit) with ESMTP id h0M09NBU033354; Wed, 22 Jan 2003 02:09:23 +0200 (EET) Date: Wed, 22 Jan 2003 02:09:23 +0200 (EET) From: Narvi To: "Bruce A. Mah" Cc: Arun Sharma , Subject: Re: verbose device probing ? In-Reply-To: <200301211626.h0LGQ88B001307@intruder.bmah.org> Message-ID: <20030122014658.I43637-100000@haldjas.folklore.ee> 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 Tue, 21 Jan 2003, Bruce A. Mah wrote: > If memory serves me right, Arun Sharma wrote: > > On Mon, Jan 20, 2003 at 08:33:09AM -0800, Bruce A. Mah wrote: > > > > > > PS. I personally ignore the severity and priority fields of PRs. The > > > importance of many PRs I've dealt with is very much inflated. > > > > > > > Perhaps you should change the severity field to a lower level then ? Or > > is there a different problem (such as lack of good tools) that prevent you > > from doing that ? > > The severity and priority fields can be changed manually but that > doesn't solve the problem that relying on the user-specified severity > and priority fields for anything meaningful just doesn't work. > > The only point that I was trying to make with my comment was that you > shouldn't place much weight on the contents of the severity and priority > fields in the database. > This sounds like throwing the baby out with the water - it would be better to find a relatively clueful volutnteer(s) who would make sure the fields are set to sensible values. This is sometimes reffered to asbug triaging. > Bruce. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 16:14:27 2003 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 916F337B401 for ; Tue, 21 Jan 2003 16:14:26 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9546843F5F for ; Tue, 21 Jan 2003 16:14:25 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h0M0EMOs033392; Wed, 22 Jan 2003 02:14:22 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.12.3/8.12.3/Submit) with ESMTP id h0M0ELph033389; Wed, 22 Jan 2003 02:14:22 +0200 (EET) Date: Wed, 22 Jan 2003 02:14:21 +0200 (EET) From: Narvi To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? In-Reply-To: <3E2DD1C0.3D0ED169@mindspring.com> Message-ID: <20030122021013.C43637-100000@haldjas.folklore.ee> 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 Tue, 21 Jan 2003, Terry Lambert wrote: > > The priority field is rather ridiculous, in a volunteer project, > at least one that does not have some sort of scheduling enforcement > (i.e. one could envision a system where all changes must have PR's > associated with them, and priority was assigned by consensus > through the email moral equivalent of a "manager's meeting", and > people were not permitted to check in priority N items, if there > were any PR's of priority > N+1 outstanding, etc.). > This is not really true - you can always use the field as a hint to wannabee hackers and patch submitters as to what they should be spending their time on. And while nothing can make sure they actually spend time on those and not other things (whetever related to FreeBSD at all or not) , its better than a mass of largely uncategorized bugs. > -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 16:26:23 2003 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 9B81037B401 for ; Tue, 21 Jan 2003 16:26:21 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB6AF43F18 for ; Tue, 21 Jan 2003 16:26:20 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0183.cvx40-bradley.dialup.earthlink.net ([216.244.42.183] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18b8if-0005CZ-00; Tue, 21 Jan 2003 16:26:18 -0800 Message-ID: <3E2DE4BB.CCD8F4A5@mindspring.com> Date: Tue, 21 Jan 2003 16:24:27 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Narvi Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? References: <20030122021013.C43637-100000@haldjas.folklore.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a492244f64bd622ba5d2b4f1868177f195548b785378294e88350badd9bab72f9c350badd9bab72f9c 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 Narvi wrote: > On Tue, 21 Jan 2003, Terry Lambert wrote: > > The priority field is rather ridiculous, in a volunteer project, > > at least one that does not have some sort of scheduling enforcement > > (i.e. one could envision a system where all changes must have PR's > > associated with them, and priority was assigned by consensus > > through the email moral equivalent of a "manager's meeting", and > > people were not permitted to check in priority N items, if there > > were any PR's of priority > N+1 outstanding, etc.). > > This is not really true - you can always use the field as a hint to > wannabee hackers and patch submitters as to what they should be spending > their time on. And while nothing can make sure they actually spend time on > those and not other things (whetever related to FreeBSD at all or not) , > its better than a mass of largely uncategorized bugs. You miss the point, I think. Nothing you have said has contradicted my statement that priority is a group/management decision, not a bug-filer's decision. Severity means "how bad the bug is biting me personally". Priority means "how much does the group value having this fixed". If the problem is that the wi driver panics the kernel when Joe-Bob inserts a prototype card that noly he has, the severity is 5 (on a scale of 0-5), but the priority on fixing it for the project is probably 0. In any case, if the priority field is to be meaningful at all, there must be a group decision (of some kind) on its value. It is *not* something that should be set by the person reporting the problem. I'll admit that there is some value for newly arrived uncommitted resources to a priority field. On the other hand, realize that in most cases, if the priority is really that high, trivial things will be fixed, and it will leave only non-trivial problems, which are not really in the scope of ability of a "newby off the street" who is looking for some way to start contributing. For that, you almost need a third field "complexity"... which implies analysis of problems, which implies scheduling of unschedulable resources, etc.. It's a hard problem, with only volunteer resources available; I would argue it was intractable, except on an individual basis, in fact. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 17:38:11 2003 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 611AC37B401 for ; Tue, 21 Jan 2003 17:38:08 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92E7F43E4A for ; Tue, 21 Jan 2003 17:38:07 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h0M1c5Os034014; Wed, 22 Jan 2003 03:38:06 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.12.3/8.12.3/Submit) with ESMTP id h0M1c4Ys034011; Wed, 22 Jan 2003 03:38:04 +0200 (EET) Date: Wed, 22 Jan 2003 03:38:04 +0200 (EET) From: Narvi To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? In-Reply-To: <3E2DE4BB.CCD8F4A5@mindspring.com> Message-ID: <20030122024713.I43637-100000@haldjas.folklore.ee> 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 Tue, 21 Jan 2003, Terry Lambert wrote: > Narvi wrote: > > On Tue, 21 Jan 2003, Terry Lambert wrote: > > > The priority field is rather ridiculous, in a volunteer project, > > > at least one that does not have some sort of scheduling enforcement > > > (i.e. one could envision a system where all changes must have PR's > > > associated with them, and priority was assigned by consensus > > > through the email moral equivalent of a "manager's meeting", and > > > people were not permitted to check in priority N items, if there > > > were any PR's of priority > N+1 outstanding, etc.). > > > > This is not really true - you can always use the field as a hint to > > wannabee hackers and patch submitters as to what they should be spending > > their time on. And while nothing can make sure they actually spend time on > > those and not other things (whetever related to FreeBSD at all or not) , > > its better than a mass of largely uncategorized bugs. > > You miss the point, I think. > > Nothing you have said has contradicted my statement that priority > is a group/management decision, not a bug-filer's decision. > > Severity means "how bad the bug is biting me personally". > As submited - yes. One can easily argue though that it should change to reflect something larger once in the database. > Priority means "how much does the group value having this > fixed". > > If the problem is that the wi driver panics the kernel when > Joe-Bob inserts a prototype card that noly he has, the severity > is 5 (on a scale of 0-5), but the priority on fixing it for the > project is probably 0. > If only Joe-Bob or some other very limited set of people have the card, then the severity of the bug in the *FreeBSD* bug database should probably not be 5 - orherwise the database will contain a large amount of bugs that claim to be of high severity but only ever affect neglible amounts of people. That inserting a prototype card can cause a crash in one particular driver is not really a high impact / severity bug as far as FreeBSD users/developers as a whole is concerned. > In any case, if the priority field is to be meaningful at all, > there must be a group decision (of some kind) on its value. It > is *not* something that should be set by the person reporting > the problem. > This really applies to both fields. It is a question of labelling and application - for both what the fields and the potential numerical values for the fields - mean. Some assignemts of meaning are more useful (according to a metric) than others. > I'll admit that there is some value for newly arrived uncommitted > resources to a priority field. On the other hand, realize that > in most cases, if the priority is really that high, trivial things > will be fixed, and it will leave only non-trivial problems, which > are not really in the scope of ability of a "newby off the street" > who is looking for some way to start contributing. For that, you > almost need a third field "complexity"... which implies analysis > of problems, which implies scheduling of unschedulable resources, > etc.. It's a hard problem, with only volunteer resources available; > I would argue it was intractable, except on an individual basis, in > fact. > And complexity need not be always determinably until the problem is largely fixed either. But it would be of a large relevenace only if hard rules were associated with the bug categorisations, instead of being merely indicators of a sort of the state of the codebase. Knowing how many 'complex' problems there are with a codebase is normaly less useful information than knowing how many reported problems have a large impact or need application of otherwise unallocated resources. At least with FreeBSD the meaning of the fields can be just technical and doesn't need an additional layer for marketing. > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 19:25:55 2003 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 8D9CF37B401 for ; Tue, 21 Jan 2003 19:25:45 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E645243ED8 for ; Tue, 21 Jan 2003 19:25:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0M3Pi0i099891; Tue, 21 Jan 2003 19:25:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0M3PiNt099890; Tue, 21 Jan 2003 19:25:44 -0800 (PST) Date: Tue, 21 Jan 2003 19:25:44 -0800 (PST) From: Matthew Dillon Message-Id: <200301220325.h0M3PiNt099890@apollo.backplane.com> To: hackers@freebsd.org Cc: Hiten Pandya Subject: patch to remove random #define MIN/MAX implementations from around the kernel 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 This patch is going to go in on the weekend unless someone has any worthwhile nits about it. It was submitted by Hiten Pandya. The patch basically removes random MIN/MAX implementations from 22 files in the kernel and modifies the one in sys/param.h (see the last part of the patch) so it is present for all kernel builds. -Matt Matthew Dillon Index: alpha/alpha/busdma_machdep.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/alpha/alpha/busdma_machdep.c,v retrieving revision 1.24 diff -u -r1.24 busdma_machdep.c --- alpha/alpha/busdma_machdep.c 4 Oct 2002 20:40:39 -0000 1.24 +++ alpha/alpha/busdma_machdep.c 18 Jan 2003 18:39:27 -0000 @@ -45,8 +45,6 @@ #include #include -#define MAX(a,b) (((a) > (b)) ? (a) : (b)) -#define MIN(a,b) (((a) < (b)) ? (a) : (b)) #define MAX_BPAGES 128 struct bus_dma_tag { Index: cam/scsi/scsi_cd.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/cam/scsi/scsi_cd.c,v retrieving revision 1.68 diff -u -r1.68 scsi_cd.c --- cam/scsi/scsi_cd.c 23 Nov 2002 22:51:50 -0000 1.68 +++ cam/scsi/scsi_cd.c 18 Jan 2003 18:39:55 -0000 @@ -172,10 +172,6 @@ } }; -#ifndef MIN -#define MIN(x,y) ((x b) ? b : a) - /* Offsets into our private CCB area for storing accept information */ #define ccb_type ppriv_field0 #define ccb_descr ppriv_ptr1 Index: compat/svr4/svr4_stream.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/compat/svr4/svr4_stream.c,v retrieving revision 1.41 diff -u -r1.41 svr4_stream.c --- compat/svr4/svr4_stream.c 13 Jan 2003 00:28:57 -0000 1.41 +++ compat/svr4/svr4_stream.c 18 Jan 2003 18:41:41 -0000 @@ -329,9 +329,6 @@ if (len <= 0 || fromsa == 0) len = 0; else { -#ifndef MIN -#define MIN(a,b) ((a)>(b)?(b):(a)) -#endif /* save sa_len before it is destroyed by MSG_COMPAT */ len = MIN(len, fromsa->sa_len); error = copyout(fromsa, Index: contrib/dev/oltr/if_oltr.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/contrib/dev/oltr/if_oltr.c,v retrieving revision 1.21 diff -u -r1.21 if_oltr.c --- contrib/dev/oltr/if_oltr.c 15 Nov 2002 00:00:14 -0000 1.21 +++ contrib/dev/oltr/if_oltr.c 18 Jan 2003 18:42:53 -0000 @@ -92,7 +92,6 @@ #define PCI_VENDOR_OLICOM 0x108D -#define MIN(A,B) (((A) < (B)) ? (A) : (B)) #define MIN3(A,B,C) (MIN(A, (MIN(B, C)))) char *AdapterName[] = { Index: contrib/ipfilter/netinet/ip_proxy.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/contrib/ipfilter/netinet/ip_proxy.c,v retrieving revision 1.20 diff -u -r1.20 ip_proxy.c --- contrib/ipfilter/netinet/ip_proxy.c 28 Aug 2002 13:41:36 -0000 1.20 +++ contrib/ipfilter/netinet/ip_proxy.c 18 Jan 2003 18:43:09 -0000 @@ -84,10 +84,6 @@ extern KRWLOCK_T ipf_nat, ipf_state; #endif -#ifndef MIN -#define MIN(a,b) (((a)<(b))?(a):(b)) -#endif - static int appr_fixseqack __P((fr_info_t *, ip_t *, ap_session_t *, int )); Index: dev/advansys/advlib.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/advansys/advlib.c,v retrieving revision 1.17 diff -u -r1.17 advlib.c --- dev/advansys/advlib.c 15 Oct 2000 14:17:58 -0000 1.17 +++ dev/advansys/advlib.c 18 Jan 2003 18:43:24 -0000 @@ -1170,8 +1170,6 @@ period = &dummy_period; } -#define MIN(a,b) (((a) < (b)) ? (a) : (b)) - *offset = MIN(ADV_SYN_MAX_OFFSET, *offset); if (*period != 0 && *offset != 0) { for (i = 0; i < adv->sdtr_period_tbl_size; i++) { Index: dev/advansys/adwcam.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/advansys/adwcam.c,v retrieving revision 1.11 diff -u -r1.11 adwcam.c --- dev/advansys/adwcam.c 1 Mar 2001 17:08:55 -0000 1.11 +++ dev/advansys/adwcam.c 18 Jan 2003 18:43:42 -0000 @@ -72,8 +72,6 @@ #define ccb_acb_ptr spriv_ptr0 #define ccb_adw_ptr spriv_ptr1 -#define MIN(a, b) (((a) < (b)) ? (a) : (b)) - u_long adw_unit; static __inline cam_status adwccbstatus(union ccb*); Index: dev/aha/aha.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/aha/aha.c,v retrieving revision 1.43 diff -u -r1.43 aha.c --- dev/aha/aha.c 1 Jan 2003 18:48:49 -0000 1.43 +++ dev/aha/aha.c 18 Jan 2003 18:44:02 -0000 @@ -84,10 +84,6 @@ */ #define PROBABLY_NEW_BOARD(REV) (REV > 0x43 && REV < 0x56) -#ifndef MAX -#define MAX(a, b) ((a) > (b) ? (a) : (b)) -#endif - /* MailBox Management functions */ static __inline void ahanextinbox(struct aha_softc *aha); static __inline void ahanextoutbox(struct aha_softc *aha); Index: dev/ahb/ahb.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/ahb/ahb.c,v retrieving revision 1.24 diff -u -r1.24 ahb.c --- dev/ahb/ahb.c 24 May 2002 05:21:36 -0000 1.24 +++ dev/ahb/ahb.c 18 Jan 2003 18:44:23 -0000 @@ -55,8 +55,6 @@ #define ccb_ecb_ptr spriv_ptr0 #define ccb_ahb_ptr spriv_ptr1 -#define MIN(a, b) ((a) < (b) ? (a) : (b)) - #define ahb_inb(ahb, port) \ bus_space_read_1((ahb)->tag, (ahb)->bsh, port) Index: dev/buslogic/bt.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/buslogic/bt.c,v retrieving revision 1.34 diff -u -r1.34 bt.c --- dev/buslogic/bt.c 6 Nov 2002 20:34:38 -0000 1.34 +++ dev/buslogic/bt.c 18 Jan 2003 18:45:21 -0000 @@ -72,10 +72,6 @@ #include -#ifndef MAX -#define MAX(a, b) ((a) > (b) ? (a) : (b)) -#endif - /* MailBox Management functions */ static __inline void btnextinbox(struct bt_softc *bt); static __inline void btnextoutbox(struct bt_softc *bt); Index: dev/sound/pci/cs4281.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/sound/pci/cs4281.c,v retrieving revision 1.12 diff -u -r1.12 cs4281.c --- dev/sound/pci/cs4281.c 23 Aug 2002 06:19:28 -0000 1.12 +++ dev/sound/pci/cs4281.c 18 Jan 2003 18:45:56 -0000 @@ -50,9 +50,6 @@ /* Misc */ -#define MIN(x,y) (x) < (y) ? (x) : (y) -#define MAX(x,y) (x) > (y) ? (x) : (y) - #define inline __inline #ifndef DEB Index: dev/sym/sym_hipd.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/dev/sym/sym_hipd.c,v retrieving revision 1.38 diff -u -r1.38 sym_hipd.c --- dev/sym/sym_hipd.c 1 Jan 2003 18:48:52 -0000 1.38 +++ dev/sym/sym_hipd.c 18 Jan 2003 18:47:06 -0000 @@ -398,13 +398,6 @@ #define MAX_QUEUE SYM_CONF_MAX_QUEUE /* - * These ones should have been already defined. - */ -#ifndef MIN -#define MIN(a, b) (((a) < (b)) ? (a) : (b)) -#endif - -/* * Active debugging tags and verbosity. */ #define DEBUG_ALLOC (0x0001) Index: i386/i386/busdma_machdep.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/i386/i386/busdma_machdep.c,v retrieving revision 1.28 diff -u -r1.28 busdma_machdep.c --- i386/i386/busdma_machdep.c 4 Oct 2002 20:40:37 -0000 1.28 +++ i386/i386/busdma_machdep.c 18 Jan 2003 18:47:20 -0000 @@ -44,8 +44,6 @@ #include #include -#define MAX(a,b) (((a) > (b)) ? (a) : (b)) -#define MIN(a,b) (((a) < (b)) ? (a) : (b)) #define MAX_BPAGES 128 struct bus_dma_tag { Index: i386/isa/gpib.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/i386/isa/gpib.c,v retrieving revision 1.35 diff -u -r1.35 gpib.c --- i386/isa/gpib.c 9 Nov 2002 12:55:06 -0000 1.35 +++ i386/isa/gpib.c 18 Jan 2003 18:47:33 -0000 @@ -35,8 +35,6 @@ #error "The gpib device requires the old isa compatibility shims" #endif -#define MIN(a, b) (((a) < (b)) ? (a) : (b)) - #define GPIBPRI (PZERO + 8) | PCATCH #define SLEEP_MAX 1000 #define SLEEP_MIN 4 Index: i386/isa/gsc.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/i386/isa/gsc.c,v retrieving revision 1.41 diff -u -r1.41 gsc.c --- i386/isa/gsc.c 4 Nov 2001 08:52:11 -0000 1.41 +++ i386/isa/gsc.c 18 Jan 2003 18:47:45 -0000 @@ -80,8 +80,6 @@ #define lprintf(args) #endif -#define MIN(a, b) (((a) < (b)) ? (a) : (b)) - #define TIMEOUT (hz*15) /* timeout while reading a buffer - default value */ #define LONG (hz/60) /* timesteps while reading a buffer */ #define GSCPRI PRIBIO /* priority while reading a buffer */ Index: ia64/ia64/busdma_machdep.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/ia64/ia64/busdma_machdep.c,v retrieving revision 1.10 diff -u -r1.10 busdma_machdep.c --- ia64/ia64/busdma_machdep.c 4 Oct 2002 20:40:35 -0000 1.10 +++ ia64/ia64/busdma_machdep.c 18 Jan 2003 18:48:16 -0000 @@ -42,8 +42,6 @@ #include #include -#define MAX(a,b) (((a) > (b)) ? (a) : (b)) -#define MIN(a,b) (((a) < (b)) ? (a) : (b)) #define MAX_BPAGES 128 struct bus_dma_tag { Index: kern/uipc_syscalls.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/kern/uipc_syscalls.c,v retrieving revision 1.135 diff -u -r1.135 uipc_syscalls.c --- kern/uipc_syscalls.c 13 Jan 2003 00:28:55 -0000 1.135 +++ kern/uipc_syscalls.c 18 Jan 2003 18:48:06 -0000 @@ -947,9 +947,6 @@ if (len <= 0 || fromsa == 0) len = 0; else { -#ifndef MIN -#define MIN(a,b) ((a)>(b)?(b):(a)) -#endif /* save sa_len before it is destroyed by MSG_COMPAT */ len = MIN(len, fromsa->sa_len); #ifdef COMPAT_OLDSOCK Index: net/zlib.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/net/zlib.c,v retrieving revision 1.15 diff -u -r1.15 zlib.c --- net/zlib.c 9 Nov 2002 12:55:06 -0000 1.15 +++ net/zlib.c 18 Jan 2003 18:48:31 -0000 @@ -2055,8 +2055,6 @@ } #endif /* DEBUG_ZLIB */ - -#define MAX(a,b) (a >= b ? a : b) /* the arguments must not have side effects */ /* =========================================================================== Index: netinet6/nd6.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/netinet6/nd6.c,v retrieving revision 1.20 diff -u -r1.20 nd6.c --- netinet6/nd6.c 2 Aug 2002 20:49:14 -0000 1.20 +++ netinet6/nd6.c 18 Jan 2003 18:48:44 -0000 @@ -204,7 +204,6 @@ nd6_setmtu(ifp) struct ifnet *ifp; { -#define MIN(a,b) ((a) < (b) ? (a) : (b)) struct nd_ifinfo *ndi = &nd_ifinfo[ifp->if_index]; u_long oldmaxmtu = ndi->maxmtu; u_long oldlinkmtu = ndi->linkmtu; Index: pccard/pccard.c =================================================================== RCS file: /home/hiten/ncvs/src/sys/pccard/pccard.c,v retrieving revision 1.152 diff -u -r1.152 pccard.c --- pccard/pccard.c 13 Sep 2002 16:23:41 -0000 1.152 +++ pccard/pccard.c 18 Jan 2003 18:48:59 -0000 @@ -52,8 +52,6 @@ #include -#define MIN(a,b) ((a)<(b)?(a):(b)) - static int allocate_driver(struct slot *, struct dev_desc *); static void inserted(void *); static void disable_slot(struct slot *); Index: sys/param.h =================================================================== RCS file: /home/hiten/ncvs/src/sys/sys/param.h,v retrieving revision 1.139 diff -u -r1.139 param.h --- sys/param.h 1 Nov 2002 09:38:33 -0000 1.139 +++ sys/param.h 18 Jan 2003 18:49:55 -0000 @@ -252,10 +252,8 @@ #define powerof2(x) ((((x)-1)&(x))==0) /* Macros for min/max. */ -#ifndef _KERNEL #define MIN(a,b) (((a)<(b))?(a):(b)) #define MAX(a,b) (((a)>(b))?(a):(b)) -#endif #ifdef _KERNEL /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 19:58: 6 2003 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 1B58A37B401 for ; Tue, 21 Jan 2003 19:58:05 -0800 (PST) Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id A07F243E4A for ; Tue, 21 Jan 2003 19:58:04 -0800 (PST) (envelope-from kris@citusc.usc.edu) Received: (from kris@localhost) by citusc.usc.edu (8.11.6/8.11.2) id h0M3w3O32733; Tue, 21 Jan 2003 19:58:03 -0800 Date: Tue, 21 Jan 2003 19:58:03 -0800 From: Kris Kennaway To: Matthew Dillon Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel Message-ID: <20030121195803.A32701@citusc.usc.edu> References: <200301220325.h0M3PiNt099890@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200301220325.h0M3PiNt099890@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 21, 2003 at 07:25:44PM -0800 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 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jan 21, 2003 at 07:25:44PM -0800, Matthew Dillon wrote: > This patch is going to go in on the weekend unless someone has any > worthwhile nits about it. It was submitted by Hiten Pandya. > Index: contrib/dev/oltr/if_oltr.c > Index: contrib/ipfilter/netinet/ip_proxy.c > Index: netinet6/nd6.c You shouldn't modify vendor code for minor purposes. Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+LhbLWry0BWjoQKURAoriAJ0Xqs+wi710Oy40di48l3pirz2twQCg8iOe +1eXoOnJz1xn0rV1aSyNoLs= =Khbx -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 20: 3: 1 2003 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 B29AE37B401 for ; Tue, 21 Jan 2003 20:03:00 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5579F43F13 for ; Tue, 21 Jan 2003 20:03:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0M42x0i000194; Tue, 21 Jan 2003 20:02:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0M42xBo000193; Tue, 21 Jan 2003 20:02:59 -0800 (PST) Date: Tue, 21 Jan 2003 20:02:59 -0800 (PST) From: Matthew Dillon Message-Id: <200301220402.h0M42xBo000193@apollo.backplane.com> To: Kris Kennaway Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel References: <200301220325.h0M3PiNt099890@apollo.backplane.com> <20030121195803.A32701@citusc.usc.edu> 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 Tue, Jan 21, 2003 at 07:25:44PM -0800, Matthew Dillon wrote: :> This patch is going to go in on the weekend unless someone has any :> worthwhile nits about it. It was submitted by Hiten Pandya. : :> Index: contrib/dev/oltr/if_oltr.c : :> Index: contrib/ipfilter/netinet/ip_proxy.c : :> Index: netinet6/nd6.c : :You shouldn't modify vendor code for minor purposes. : :Kris The vendor code in question has been modified *extensively* since it was imported, (and of course I would give Darren a head's up in regards to ipfilter). Unless you have a more specific reason I don't really think a general blanket statement is sufficient reason to not do the commit, at least not in this case. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 20: 7: 2 2003 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 989CA37B401 for ; Tue, 21 Jan 2003 20:07:01 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BCEC43EB2 for ; Tue, 21 Jan 2003 20:07:01 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 37A442A7EA; Tue, 21 Jan 2003 20:07:01 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Dillon Cc: Kris Kennaway , hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel In-Reply-To: <200301220402.h0M42xBo000193@apollo.backplane.com> Date: Tue, 21 Jan 2003 20:07:01 -0800 From: Peter Wemm Message-Id: <20030122040701.37A442A7EA@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 Matthew Dillon wrote: > > :On Tue, Jan 21, 2003 at 07:25:44PM -0800, Matthew Dillon wrote: > :> This patch is going to go in on the weekend unless someone has any > :> worthwhile nits about it. It was submitted by Hiten Pandya. > : > :> Index: contrib/dev/oltr/if_oltr.c > : > :> Index: contrib/ipfilter/netinet/ip_proxy.c > : > :> Index: netinet6/nd6.c > : > :You shouldn't modify vendor code for minor purposes. > : > :Kris > > The vendor code in question has been modified *extensively* since > it was imported, (and of course I would give Darren a head's up in > regards to ipfilter). Unless you have a more specific reason I don't > really think a general blanket statement is sufficient reason to not > do the commit, at least not in this case. Didn't we explicitly make it like this? ie: you'd be backing out a previous set of intentional commits by doing this... 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 Tue Jan 21 20:11:34 2003 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 1F65437B401 for ; Tue, 21 Jan 2003 20:11:33 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1D5143ED8 for ; Tue, 21 Jan 2003 20:11:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0M4BW0i000319; Tue, 21 Jan 2003 20:11:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0M4BW7B000318; Tue, 21 Jan 2003 20:11:32 -0800 (PST) Date: Tue, 21 Jan 2003 20:11:32 -0800 (PST) From: Matthew Dillon Message-Id: <200301220411.h0M4BW7B000318@apollo.backplane.com> To: Peter Wemm Cc: Kris Kennaway , hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel References: <20030122040701.37A442A7EA@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 :Didn't we explicitly make it like this? ie: you'd be backing out a :previous set of intentional commits by doing this... : :Cheers, :-Peter :-- :Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com I'm not aware of anything like that. The MIN code appears to be in rev 1.1 of oltr, ipfilter, and netinet6/nd6.c. Is there a commit rev you want me to review on any of these? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 20:31:49 2003 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 2A81D37B401 for ; Tue, 21 Jan 2003 20:31:44 -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 7471143F13 for ; Tue, 21 Jan 2003 20:31:38 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0003.cvx40-bradley.dialup.earthlink.net ([216.244.42.3] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18bCXs-0005Ut-00; Tue, 21 Jan 2003 20:31:25 -0800 Message-ID: <3E2E1E26.2CE307C2@mindspring.com> Date: Tue, 21 Jan 2003 20:29:26 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Narvi Cc: hackers@FreeBSD.ORG Subject: Re: verbose device probing ? References: <20030122024713.I43637-100000@haldjas.folklore.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a456ecdcfa52d6024a83696c9cac205e49a7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c 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 Narvi wrote: > > Priority means "how much does the group value having this > > fixed". > > > > If the problem is that the wi driver panics the kernel when > > Joe-Bob inserts a prototype card that noly he has, the severity > > is 5 (on a scale of 0-5), but the priority on fixing it for the > > project is probably 0. > > If only Joe-Bob or some other very limited set of people have the > card, then the severity of the bug in the *FreeBSD* bug database > should probably not be 5 - orherwise the database will contain a > large amount of bugs that claim to be of high severity but only > ever affect neglible amounts of people. That inserting a prototype > card can cause a crash in one particular driver is not really a > high impact / severity bug as far as FreeBSD users/developers as a > whole is concerned. I intentionally picked my example so that a negligible number of people would have the card (it's a prototype, so, by definition, it has a tiny production run, usually less than you can count without having to take your shoes off). This was to emphasize the difference between "priority", which is assigned by the project, and "severity", which is either assigned by the user, or assigned as a result of a report by a user, on the basis of some objective criteria, e.g.: Severity Objective criteria 5 Esthetic differences between designers and users 4 Failure to expose a feature in UI 3 Loss of functionality, workaround exists 2 Loss of functionality, no workaround exists 1 Loss of customer data So for the Pentium, we have: FPU bug Sev 1 F00F bug Sev 3 Intel byte order Sev 5 Note that this is merely one possible range and domain set, out of many... I'm not insisting on adoption of a particular objective criteria. The only way this works in a self-submission management system is to ask yes/no questions based on escalation criteria, rather than allowing a user to pick from a list... a user will alsways pick the most severe one they feel they can justify, in context, to try to make the problem report "more important" to the people to whom they're reporting the problem. In FreeBSD's case, this is pretty much moot, but it's how user's have been trained to interact with vendors in order to get timely responses out of them, so it's what will happen. > > In any case, if the priority field is to be meaningful at all, > > there must be a group decision (of some kind) on its value. It > > is *not* something that should be set by the person reporting > > the problem. > > This really applies to both fields. It is a question of labelling > and application - for both what the fields and the potential > numerical values for the fields - mean. Some assignemts of meaning > are more useful (according to a metric) than others. Severity has little or nothing to do with whether or not the project will choose to do anything about the problem. It's based on subjective application of a technology in order to cause an ovjectively classifiable result. For example, say you had an editor that could bomb and take out your file; is that a sev 1 bug, according to the criteria? Or... is it sev 3, because you could copy the file before firing up the editor? Or is it a sev 4, because the editor should be renamed and replaced with a shell script that does the copying for you, before invoking the real editor? > > I'll admit that there is some value for newly arrived uncommitted > > resources to a priority field. On the other hand, realize that > > in most cases, if the priority is really that high, trivial things > > will be fixed, and it will leave only non-trivial problems, which > > are not really in the scope of ability of a "newby off the street" > > who is looking for some way to start contributing. For that, you > > almost need a third field "complexity"... which implies analysis > > of problems, which implies scheduling of unschedulable resources, > > etc.. It's a hard problem, with only volunteer resources available; > > I would argue it was intractable, except on an individual basis, in > > fact. > > And complexity need not be always determinably until the problem is > largely fixed either. But it would be of a large relevenace only if > hard rules were associated with the bug categorisations, instead of > being merely indicators of a sort of the state of the codebase. > Knowing how many 'complex' problems there are with a codebase is > normaly less useful information than knowing how many reported > problems have a large impact or need application of otherwise > unallocated resources. Even if there were a system, where each user impacted by a particular problem could "vote" a higher priority to a bug that effected them, all you would end up with is a system where the number of people impacted on each bug was effectively "polled" to assign some figure of merit. But unless/until that figure of merit has an impact on scheduling of resources to deal with the issue, it's pretty much meaningless to do anything like that, because it won't have any real effect on what work gets done, and what work gets left on the table. > At least with FreeBSD the meaning of the fields can be just technical > and doesn't need an additional layer for marketing. The bugs database is, in fact, a "customer facing system". It exists primarily for marketing. It does serve one technical purpose: by making people post problems there, instead of posting them to a mailing list, it makes it much easier to ignore people who raise inconvenient problems on mailing lists. 8-). That's more of a political benefit. The same purpose could be served by demoting the severity of the filed bug, regardless of the filers intended severity, or the objective severity. That's actually a systems purpose: it's a relief valve, which protects the people doing the work from the people consuming it, in order to maintain their participation in the project, which would likely go away, if they were being beat on by end users for code changes, directly. One of the early postings in this thread was about IBM having meetings to deescalate sev 1 bugs so that "products are not be shipped with sev 1 bugs"; this weasels around an objective quality criteria that is being enforced by release engineers. That's the real intent of such meetings: to work around quality criteria, and ship a lower quality product, so as to meet objective performance criteria, relative to scheduled vs. actual ship date. The difference in the IBM case is that IBM is, effectively, paying people to work around the objective criteria system like this, by basing pay on performance relative to schedules. It doesn't take someone with a profound understanding of games theory to guess at the result: "You get what you pay for". 8-). The problem with applying this sort of thing to volunteer efforts is that you *can't* "just hire someone else". There is no such thing as "an unallocated resource": there's only "self allocated resources". I submit that the severity in the FreeBSD bugs database is far from objectively assigned, and there is no process in place for it to be revisited, once the severity is set, except for arbitrary changes made by people who don't want to have the project be seen with a large number of sever bugs, and therfore have a vested interest in underestimating severity (i.e. "the right answer" on the editor, earlier, is that it's a sev 3, and a user who just lost six hours of work on their Master's Thesis since their last exit/entry would likely consider it a sev 1, and someone who'd rather codify the workaround, rather than fix the root cause, would write the script, mark it a sev 2, and close it). Priority... priority is totally meaningless, unless you are willing to accept stall barriers, either in terms of resource scheduling, or in terms of resource levelling across available problems (the second is less likely, since software engineering is very hard to resource-level, even if the project managers who have found that menu button in "Microsoft Project" would wish otherwise, since not all engineers know the VM system or the serial drivers or the EMACS LISP interpreter equally well). Short of not letting Joe-Bob check in code against a sev 4 while he has a sev 2 outstanding that he "owns" -- *and* assigning ownership of bugs, so it's his bug, and not an unassigned one -- there's really very little you can do in terms of scheduling. Even so, many people will just say "screw you", and not work on anything (they are volunteers... it's not like you could fire them and deprive them of a paycheck as a punative measure), rather than work on something they don't want to work on. So it still comes down to enforcement, and you don't have enforcement available. The closest you can possibly come is "peer pressure", and that only works if the group assigning the priorities is generally well respected by the volunteers. So it's not like you can just "declare process" and have it fix things, either (that only works if you have a stick to go with the carrot that got people to do the work in the first place). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 20:57:45 2003 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 194AF37B401 for ; Tue, 21 Jan 2003 20:57:44 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 203D843ED8 for ; Tue, 21 Jan 2003 20:57:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.6/8.12.5) with ESMTP id h0M4vevA098042; Tue, 21 Jan 2003 23:57:40 -0500 (EST) (envelope-from winter@jurai.net) Date: Tue, 21 Jan 2003 23:57:40 -0500 (EST) From: "Matthew N. Dodd" To: Matthew Dillon Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel In-Reply-To: <200301220325.h0M3PiNt099890@apollo.backplane.com> Message-ID: <20030121235501.N59276-100000@sasami.jurai.net> 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 Tue, 21 Jan 2003, Matthew Dillon wrote: > This patch is going to go in on the weekend unless someone has any > worthwhile nits about it. It was submitted by Hiten Pandya. > > The patch basically removes random MIN/MAX implementations from > 22 files in the kernel and modifies the one in sys/param.h (see the > last part of the patch) so it is present for all kernel builds. I'd like to see all of these changed to the inlines in sys/libkern.h since the compiler will do type checking for us. This is a little more work which is why I didn't do it myself when I dealt with the abs() stuff. Consider this my objection. I don't think that it really stands in the way of the cleanup of all the definitions of min/max etc. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 21:19:50 2003 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 A71C637B401 for ; Tue, 21 Jan 2003 21:19:49 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BA9C43ED8 for ; Tue, 21 Jan 2003 21:19:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0M5Jm0i000825; Tue, 21 Jan 2003 21:19:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0M5JmhD000824; Tue, 21 Jan 2003 21:19:48 -0800 (PST) Date: Tue, 21 Jan 2003 21:19:48 -0800 (PST) From: Matthew Dillon Message-Id: <200301220519.h0M5JmhD000824@apollo.backplane.com> To: "Matthew N. Dodd" Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel References: <20030121235501.N59276-100000@sasami.jurai.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 :I'd like to see all of these changed to the inlines in sys/libkern.h since :the compiler will do type checking for us. : :This is a little more work which is why I didn't do it myself when I dealt :with the abs() stuff. : :Consider this my objection. : :I don't think that it really stands in the way of the cleanup of all the :definitions of min/max etc. : :-- :| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | This might be useful follow-up work. i.e. the idea of getting rid of the use of the MIN and MAX macros in the kernel altogether. Though I'm not sure I like the fact that 'min' and 'max' in sys/libkern.h refer to unsigned ints (it really should be umin and umax or uimin and uimax). That's a real problem. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 21:26:38 2003 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 584AF37B401 for ; Tue, 21 Jan 2003 21:26:37 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-106-48.dsl.lsan03.pacbell.net [64.169.106.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA56B43F18 for ; Tue, 21 Jan 2003 21:26:36 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 4435266B3A; Tue, 21 Jan 2003 21:26:36 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 203401658; Tue, 21 Jan 2003 21:26:36 -0800 (PST) Date: Tue, 21 Jan 2003 21:26:36 -0800 From: Kris Kennaway To: Matthew Dillon Cc: Kris Kennaway , hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel Message-ID: <20030122052636.GA25050@rot13.obsecurity.org> References: <200301220325.h0M3PiNt099890@apollo.backplane.com> <20030121195803.A32701@citusc.usc.edu> <200301220402.h0M42xBo000193@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline In-Reply-To: <200301220402.h0M42xBo000193@apollo.backplane.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 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2003 at 08:02:59PM -0800, Matthew Dillon wrote: > :You shouldn't modify vendor code for minor purposes. > : > :Kris >=20 > The vendor code in question has been modified *extensively* since > it was imported, (and of course I would give Darren a head's up in > regards to ipfilter). Unless you have a more specific reason I don't > really think a general blanket statement is sufficient reason to not > do the commit, at least not in this case. I think you need to respect vendor code, and the FreeBSD committers who maintain it. Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LiuLWry0BWjoQKURAj7lAKDEAQFmznNxGSP+5jvKIDkrCD7l5QCgwhI1 qr8sLV+sFKnoasGUe1TCeyQ= =iQqz -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 21 21:44:45 2003 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 8D70337B401 for ; Tue, 21 Jan 2003 21:44:44 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5EE243F5F for ; Tue, 21 Jan 2003 21:44:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.6/8.12.5) with ESMTP id h0M5ifvA098807; Wed, 22 Jan 2003 00:44:42 -0500 (EST) (envelope-from winter@jurai.net) Date: Wed, 22 Jan 2003 00:44:41 -0500 (EST) From: "Matthew N. Dodd" To: Matthew Dillon Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel In-Reply-To: <200301220519.h0M5JmhD000824@apollo.backplane.com> Message-ID: <20030122004138.E59276-100000@sasami.jurai.net> 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 Tue, 21 Jan 2003, Matthew Dillon wrote: > This might be useful follow-up work. i.e. the idea of getting rid of > the use of the MIN and MAX macros in the kernel altogether. Though I'm > not sure I like the fact that 'min' and 'max' in sys/libkern.h refer to > unsigned ints (it really should be umin and umax or uimin and uimax). libkern.h defines them the same way as stand.h does. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 5: 6:46 2003 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 7EA6D37B401 for ; Wed, 22 Jan 2003 05:06:45 -0800 (PST) Received: from thufir.bluecom.no (thufir.bluecom.no [217.118.32.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C47143F18 for ; Wed, 22 Jan 2003 05:06:44 -0800 (PST) (envelope-from eirik@odin.eirikn.net) Received: from odin.eirikn.net (a217-118-47-71.bluecom.no [217.118.47.71]) by thufir.bluecom.no (Postfix) with ESMTP id 27D5450EC41 for ; Wed, 22 Jan 2003 14:06:36 +0100 (CET) Received: by odin.eirikn.net (Postfix, from userid 1001) id 62D1241F8; Wed, 22 Jan 2003 14:06:37 +0100 (CET) Date: Wed, 22 Jan 2003 14:06:37 +0100 From: Eirik Nygaard To: hackers@freebsd.org Subject: NIC driver Message-ID: <20030122130637.GA10760@eirikn.net> Reply-To: eirikn@bluezone.no Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline 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 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I just got a new computer with a network card I don't seem to find any FreeBSD drivers for. It got a realtek 8201 chipset so I thought I could make my own driver, but I am not sure where to start. Are there any guides on how to make a simpel driver out there?=20 Any hint & tips would be great, where to start, what I need to know. --=20 Eirik Nygaard PGP Key: 83C55EDE --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+Lpdd1JB0Z4PFXt4RAnpzAJ98dXJoYbPLVRZUfupYeBCWNkGU6gCfXSaS +hsBZy9Nv7hlgiDXvgd0T+k= =4aFi -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 5:26:28 2003 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 801E737B401 for ; Wed, 22 Jan 2003 05:26:27 -0800 (PST) Received: from mail.sznsec.za.org (mail.sznsec.za.org [196.22.208.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45C5743F13 for ; Wed, 22 Jan 2003 05:26:22 -0800 (PST) (envelope-from vortexia@sznsec.za.org) Received: from [196.22.208.212] (helo=[196.22.208.212]) by mail.sznsec.za.org with esmtp (Exim 4.10) id 18bAX5-000D5I-00 for hackers@freebsd.org; Wed, 22 Jan 2003 02:22:27 +0000 Date: Wed, 22 Jan 2003 02:22:27 +0000 (GMT) From: Andrew Alston To: hackers@freebsd.org Subject: SSHD PRNG Not seeded under jail Message-ID: <20030122022122.W78046-100000@mail.sznsec.za.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 Hi All, FBSD 5-RC2 was giving me a SSHD PRNG not seeded problem when running under jails, is this a problem with my configuration or a bug? And if a bug, has it been fixed in -RELEASE? Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 6:11:21 2003 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 8BF8537B401 for ; Wed, 22 Jan 2003 06:11:20 -0800 (PST) Received: from out7.mx.nwbl.wi.voyager.net (out7.mx.nwbl.wi.voyager.net [169.207.3.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id D718943F1E for ; Wed, 22 Jan 2003 06:11:19 -0800 (PST) (envelope-from silby@silby.com) Received: from [10.1.1.6] (d99.as9.nwbl0.wi.voyager.net [169.207.132.227]) by out7.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id 5BF3D93A93; Wed, 22 Jan 2003 08:11:13 -0600 (CST) Date: Wed, 22 Jan 2003 08:18:57 -0600 (CST) From: Mike Silbersack To: Eirik Nygaard Cc: hackers@freebsd.org Subject: Re: NIC driver In-Reply-To: <20030122130637.GA10760@eirikn.net> Message-ID: <20030122081837.X6780-100000@patrocles.silby.com> References: <20030122130637.GA10760@eirikn.net> 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 Wed, 22 Jan 2003, Eirik Nygaard wrote: > I just got a new computer with a network card I don't seem to find any > FreeBSD drivers for. It got a realtek 8201 chipset so I thought I > could make my own driver, but I am not sure where to start. Are there > any guides on how to make a simpel driver out there? > Any hint & tips would be great, where to start, what I need to know. > > -- > > Eirik Nygaard That should be a supported card. What version of FreeBSD are you running? 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 Wed Jan 22 6:17:37 2003 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 44D9337B401 for ; Wed, 22 Jan 2003 06:17:35 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DA3343E4A for ; Wed, 22 Jan 2003 06:17:14 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 16196 invoked by uid 1000); 22 Jan 2003 14:16:15 -0000 Date: Wed, 22 Jan 2003 16:16:15 +0200 From: Peter Pentchev To: lemon Cc: freebsd-hackers@freebsd.org Subject: Re: getnameinfo contacting 'wrong' resolver for lookup Message-ID: <20030122141615.GF379@straylight.oblivion.bg> Mail-Followup-To: lemon , freebsd-hackers@freebsd.org References: <3E182B54.4090007@aldigital.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x4pBfXISqBoDm8sr" Content-Disposition: inline In-Reply-To: <3E182B54.4090007@aldigital.co.uk> User-Agent: Mutt/1.5.3i 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 --x4pBfXISqBoDm8sr Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 05, 2003 at 12:55:48PM +0000, lemon wrote: > hi, >=20 > i have a 4.7-STABLE box running two nameservers: a djbdns dnscache on > 127.0.0.1 to serve local requests, and have recently added a djbdns > tinydns on my external address to serve domains i host, viz: >=20 > $ sockstat -4 | grep :53 > dnscache dnscache 37679 3 udp4 127.0.0.1:53 *:* > dnscache dnscache 37679 4 tcp4 127.0.0.1:53 *:* > tinydns tinydns 37672 3 udp4 192.168.1.2:53 *:* >=20 > the box's resolv.conf has a single nameserver entry for localhost. >=20 > my problem: since adding the external tinydns listener, my openssh > sessions take ages to log in. thinking a reverse lookup oddity i did > some digging, and saw that the getnameinfo call in sshd appears to query > the external listener (albeit thru loopback) first. this external > listener can't reverse the connection's address since it only resolves > domains hosted on the box itself. after a long timeout, the correct > nameserver is contacted and the login succeeds. some tcpdumping reveals: My previous attempts at analyzing this aside, could this be related to the problem described in PR bin/40984 and ports/39953? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3D40894 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3D39953 G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence would be seven words long if it were six words shorter. --x4pBfXISqBoDm8sr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+Lqev7Ri2jRYZRVMRAlaOAJ9M/oOntQEFH+IKMLOYm6Ct6QKSSgCgv9Md JPM6kJ/FCIbphfGnAY2Vx2M= =g49u -----END PGP SIGNATURE----- --x4pBfXISqBoDm8sr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 6:35:58 2003 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 AD5BB37B401 for ; Wed, 22 Jan 2003 06:35:56 -0800 (PST) Received: from thufir.bluecom.no (thufir.bluecom.no [217.118.32.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C5B543F3F for ; Wed, 22 Jan 2003 06:35:56 -0800 (PST) (envelope-from eirik@odin.eirikn.net) Received: from odin.eirikn.net (a217-118-47-71.bluecom.no [217.118.47.71]) by thufir.bluecom.no (Postfix) with ESMTP id AB00A50ECAB for ; Wed, 22 Jan 2003 15:35:53 +0100 (CET) Received: by odin.eirikn.net (Postfix, from userid 1001) id 898CE41F8; Wed, 22 Jan 2003 15:35:54 +0100 (CET) Date: Wed, 22 Jan 2003 15:35:54 +0100 From: Eirik Nygaard To: hackers@freebsd.org Subject: Re: NIC driver Message-ID: <20030122143554.GB10760@eirikn.net> Reply-To: eirikn@bluezone.no Mail-Followup-To: hackers@freebsd.org References: <20030122130637.GA10760@eirikn.net> <20030122081837.X6780-100000@patrocles.silby.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rJwd6BRFiFCcLxzm" Content-Disposition: inline In-Reply-To: <20030122081837.X6780-100000@patrocles.silby.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 --rJwd6BRFiFCcLxzm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 22, 2003 at 08:18:57AM -0600, Mike Silbersack wrote: >=20 > > I just got a new computer with a network card I don't seem to find any > > FreeBSD drivers for. It got a realtek 8201 chipset so I thought I > > could make my own driver, but I am not sure where to start. Are there > > any guides on how to make a simpel driver out there? > > Any hint & tips would be great, where to start, what I need to know. > > > That should be a supported card. What version of FreeBSD are you running? >=20 > Mike "Silby" Silbersack >=20 I am running 5.0-RELEASE, nothing shows up in neither dmesg nor ifconfig. It is a built-in network card on an Asus A7N266-VM motherboard. --=20 Eirik Nygaard PGP Key: 83C55EDE --rJwd6BRFiFCcLxzm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LqxK1JB0Z4PFXt4RAgYiAJ9TbrQ0zNhXkgsQvEEICs5GZEMBiQCgg91i gHCQ064WyVzEuz+uBYZvqxk= =Ojv2 -----END PGP SIGNATURE----- --rJwd6BRFiFCcLxzm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 6:44:29 2003 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 825BE37B401 for ; Wed, 22 Jan 2003 06:44:28 -0800 (PST) Received: from bosvwl01.infosys.com (bosvwl01.itlinfosys.com [216.52.49.35]) by mx1.FreeBSD.org (Postfix) with SMTP id BCF6643F18 for ; Wed, 22 Jan 2003 06:44:27 -0800 (PST) (envelope-from abhay_srivastava@infosys.com) Received: from 192.168.200.82 by bosvwl01.infosys.com (InterScan E-Mail VirusWall NT); Wed, 22 Jan 2003 09:33:16 -0500 Received: from kecmsg11.ad.infosys.com ([192.168.200.69]) by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 22 Jan 2003 20:18:42 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: NIC driver Date: Wed, 22 Jan 2003 20:18:41 +0530 Message-ID: <882B7E812BE14E4BA7E86387242C8DB9070442@kecmsg11.ad.infosys.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NIC driver Thread-Index: AcLCF9Ma0PyExH6iSASJe1foq0zLXQABXfCw From: "Abhay Kumar Srivastava" To: , X-OriginalArrivalTime: 22 Jan 2003 14:48:42.0262 (UTC) FILETIME=[5B637B60:01C2C225] 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 Eirik, You can try out with the explanation of Pseudo driver in FreeBsd HandBook. Then you can look at the driver of existing Network Cards like pci/if_fxp.c Which is the driver for "Intel EtherExpress Pro/100B PCI Fast Ethernet driver". Regards, Abhay. -----Original Message----- From: Eirik Nygaard [mailto:eirikn@bluezone.no]=20 Sent: Wednesday, January 22, 2003 6:37 PM To: hackers@freebsd.org Subject: NIC driver I just got a new computer with a network card I don't seem to find any FreeBSD drivers for. It got a realtek 8201 chipset so I thought I could make my own driver, but I am not sure where to start. Are there any guides on how to make a simpel driver out there?=20 Any hint & tips would be great, where to start, what I need to know. --=20 Eirik Nygaard PGP Key: 83C55EDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 7: 5: 6 2003 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 C4F8C37B401 for ; Wed, 22 Jan 2003 07:05:05 -0800 (PST) Received: from out4.mx.nwbl.wi.voyager.net (out4.mx.nwbl.wi.voyager.net [169.207.3.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C4043E4A for ; Wed, 22 Jan 2003 07:05:05 -0800 (PST) (envelope-from silby@silby.com) Received: from [10.1.1.6] (d99.as9.nwbl0.wi.voyager.net [169.207.132.227]) by out4.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id C3600C7531; Wed, 22 Jan 2003 09:05:03 -0600 (CST) Date: Wed, 22 Jan 2003 09:12:47 -0600 (CST) From: Mike Silbersack To: Eirik Nygaard Cc: hackers@freebsd.org Subject: Re: NIC driver In-Reply-To: <20030122143554.GB10760@eirikn.net> Message-ID: <20030122091204.R7064-100000@patrocles.silby.com> References: <20030122130637.GA10760@eirikn.net> <20030122081837.X6780-100000@patrocles.silby.com> <20030122143554.GB10760@eirikn.net> 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 Wed, 22 Jan 2003, Eirik Nygaard wrote: > I am running 5.0-RELEASE, nothing shows up in neither dmesg nor > ifconfig. It is a built-in network card on an Asus A7N266-VM > motherboard. > > -- > > Eirik Nygaard Ok, please post the output of a "pciconf -l", run as root. Perhaps it's just a slightly different pci ID. 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 Wed Jan 22 7:19:35 2003 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 81A1537B401 for ; Wed, 22 Jan 2003 07:19:34 -0800 (PST) Received: from pip.lemonia.org (pc-80-192-57-7-az.blueyonder.co.uk [80.192.57.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 4415643EB2 for ; Wed, 22 Jan 2003 07:19:32 -0800 (PST) (envelope-from lemon@aldigital.co.uk) Received: (qmail 68838 invoked from network); 22 Jan 2003 15:19:42 -0000 Received: from unknown (HELO aldigital.co.uk) (192.168.1.3) by 192.168.1.4 with SMTP; 22 Jan 2003 15:19:42 -0000 Message-ID: <3E2EB682.9040504@aldigital.co.uk> Date: Wed, 22 Jan 2003 15:19:30 +0000 From: lemon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Pentchev Cc: freebsd-hackers@freebsd.org Subject: Re: getnameinfo contacting 'wrong' resolver for lookup References: <3E182B54.4090007@aldigital.co.uk> <20030122141615.GF379@straylight.oblivion.bg> 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 Peter Pentchev wrote: > > My previous attempts at analyzing this aside, could this be related to > the problem described in PR bin/40984 and ports/39953? > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=40894 > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=39953 > the patch in the latter sorted the problem out, thanks for the pointer. it also explains why a little getnameinfo programlet never succeeded in reproducing the problem. echoing the comments in 40894, it'd be great if this made it into -STABLE. rgds, l. -- lemon@aldigital.co.uk +44 020 8742 0755 www.aldigital.co.uk system administrivia c6 h8 o7 www.thebunker.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 7:49:27 2003 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 78CAA37B401 for ; Wed, 22 Jan 2003 07:49:26 -0800 (PST) Received: from grsu.by (grsu.by [194.158.202.115]) by mx1.FreeBSD.org (Postfix) with SMTP id C924243F1E for ; Wed, 22 Jan 2003 07:49:16 -0800 (PST) (envelope-from grog@grsu.by) Received: (qmail 30378 invoked from network); 22 Jan 2003 15:48:02 -0000 Received: from unknown (HELO grsu.by) (grog@195.50.13.201) by grsu.by with SMTP; 22 Jan 2003 15:48:02 -0000 Message-ID: <3E2EBC79.5020704@grsu.by> Date: Wed, 22 Jan 2003 17:44:57 +0200 From: Yury Tarasievich User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020829 X-Accept-Language: be, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: verbose device probing ? References: <20030122024713.I43637-100000@haldjas.folklore.ee> 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 Narvi wrote: >If only Joe-Bob or some other very limited set of people have the >card, then the severity of the bug in the *FreeBSD* bug database >should probably not be 5 - orherwise the database will contain a >large amount of bugs that claim to be of high severity but only >ever affect neglible amounts of people > I'd say there is *no* such thing as "negligible amount of people" in FreeBSD community. In Windows community, perhaps. Not here. Remember we aren't yet talking millions of installations and must-setup thing. No negligible (discardable) amount of people, then. Please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 7:51:42 2003 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 64B0137B401 for ; Wed, 22 Jan 2003 07:51:40 -0800 (PST) Received: from thufir.bluecom.no (thufir.bluecom.no [217.118.32.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B02543F18 for ; Wed, 22 Jan 2003 07:51:39 -0800 (PST) (envelope-from eirik@odin.eirikn.net) Received: from odin.eirikn.net (a217-118-47-71.bluecom.no [217.118.47.71]) by thufir.bluecom.no (Postfix) with ESMTP id CD00650ED30 for ; Wed, 22 Jan 2003 16:51:37 +0100 (CET) Received: by odin.eirikn.net (Postfix, from userid 1001) id 7BA7E3FB1; Wed, 22 Jan 2003 16:51:38 +0100 (CET) Date: Wed, 22 Jan 2003 16:51:38 +0100 From: Eirik Nygaard To: hackers@freebsd.org Subject: Re: NIC driver Message-ID: <20030122155138.GA928@eirikn.net> Mail-Followup-To: hackers@freebsd.org References: <20030122130637.GA10760@eirikn.net> <20030122081837.X6780-100000@patrocles.silby.com> <20030122143554.GB10760@eirikn.net> <20030122091204.R7064-100000@patrocles.silby.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20030122091204.R7064-100000@patrocles.silby.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 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 22, 2003 at 09:12:47AM -0600, Mike Silbersack wrote: >=20 > On Wed, 22 Jan 2003, Eirik Nygaard wrote: >=20 > > I am running 5.0-RELEASE, nothing shows up in neither dmesg nor > > ifconfig. It is a built-in network card on an Asus A7N266-VM > > motherboard. > > > > -- > > > > Eirik Nygaard >=20 > Ok, please post the output of a "pciconf -l", run as root. Perhaps it's > just a slightly different pci ID. >=20 > Mike "Silby" Silbersack >=20 Here we go: # pciconf -l hostb0@pci0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x01a410d= e rev=3D0xb2 hdr=3D0x00 none0@pci0:0:1: class=3D0x050000 card=3D0x0c1110de chip=3D0x01ac10de rev=3D= 0xb2 hdr=3D0x00 none1@pci0:0:2: class=3D0x050000 card=3D0x0c1110de chip=3D0x01ad10de rev=3D= 0xb2 hdr=3D0x00 none2@pci0:0:3: class=3D0x050000 card=3D0x0c1110de chip=3D0x01aa10de rev=3D= 0xb2 hdr=3D0x00 isab0@pci0:1:0: class=3D0x060100 card=3D0x0c1110de chip=3D0x01b210de rev=3D= 0xc3 hdr=3D0x00 none3@pci0:1:1: class=3D0x0c0500 card=3D0x0c1110de chip=3D0x01b410de rev=3D= 0xc1 hdr=3D0x00 none4@pci0:4:0: class=3D0x020000 card=3D0x0c111043 chip=3D0x01c310de rev=3D= 0xc2 hdr=3D0x00 pcib1@pci0:8:0: class=3D0x060400 card=3D0x00000044 chip=3D0x01b810de rev=3D= 0xc2 hdr=3D0x01 atapci0@pci0:9:0: class=3D0x01018a card=3D0x0c1110de chip=3D0x01bc10d= e rev=3D0xc3 hdr=3D0x00 pcib2@pci0:30:0: class=3D0x060400 card=3D0x00000000 chip=3D0x01b710d= e rev=3D0xb2 hdr=3D0x01 rl0@pci1:8:0: class=3D0x020000 card=3D0x813910ec chip=3D0x813910ec rev=3D= 0x10 hdr=3D0x00 none5@pci2:0:0: class=3D0x030000 card=3D0x0c1110de chip=3D0x01a010de rev=3D= 0xb1 hdr=3D0x00 rl0@pci1:8:0 is another realtek card I put into the computer to be abel to copy the pciconf -l info without manually writing it over. The network card is none4@pci0:4:0 it seems if I use the -v switch also. none4@pci0:4:0: class=3D0x020000 card=3D0x0c111043 chip=3D0x01c310de rev=3D= 0xc2 hdr=3D0x00 vendor =3D 'Nvidia Corporation' device =3D 'nForce MCP Networking Adapter' class =3D network subclass =3D ethernet --=20 Eirik Nygaard PGP Key: 83C55EDE --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+Lr4K1JB0Z4PFXt4RApbcAJwPlQ2ALUnbSn1QE1b7MVpcwBmaogCfaHlJ nBxEf3c17m5L+RlMNf+5Xgs= =FZUu -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 9:35:57 2003 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 6A64437B401 for ; Wed, 22 Jan 2003 09:35:55 -0800 (PST) Received: from out0.mx.nwbl.wi.voyager.net (out0.mx.nwbl.wi.voyager.net [169.207.3.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB2C143E4A for ; Wed, 22 Jan 2003 09:35:54 -0800 (PST) (envelope-from silby@silby.com) Received: from [10.1.1.6] (d99.as9.nwbl0.wi.voyager.net [169.207.132.227]) by out0.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id C1459835F5; Wed, 22 Jan 2003 11:35:52 -0600 (CST) Date: Wed, 22 Jan 2003 11:43:37 -0600 (CST) From: Mike Silbersack To: Eirik Nygaard Cc: hackers@freebsd.org Subject: Re: NIC driver In-Reply-To: <20030122155138.GA928@eirikn.net> Message-ID: <20030122112649.S7613-100000@patrocles.silby.com> References: <20030122130637.GA10760@eirikn.net> <20030122081837.X6780-100000@patrocles.silby.com> <20030122143554.GB10760@eirikn.net> <20030122091204.R7064-100000@patrocles.silby.com> <20030122155138.GA928@eirikn.net> 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 Wed, 22 Jan 2003, Eirik Nygaard wrote: > none4@pci0:4:0: class=0x020000 card=0x0c111043 chip=0x01c310de rev=0xc2 hdr=0x00 > > rl0@pci1:8:0 is another realtek card I put into the computer to be > abel to copy the pciconf -l info without manually writing it over. > The network card is none4@pci0:4:0 it seems if I use the -v switch > also. > > none4@pci0:4:0: class=0x020000 card=0x0c111043 chip=0x01c310de rev=0xc2 hdr=0x00 > vendor = 'Nvidia Corporation' > device = 'nForce MCP Networking Adapter' > class = network > subclass = ethernet > > -- > > Eirik Nygaard Hm, I guess we don't support that chipset. Apologies for the confusion, I was confused by an earlier commit regarding NForce2 boards; apparently some vendors are shipping boards with Nvidia's onboard ethernet _and_ a secondary 3com interface. (The reason for the secondary interace will become clear in a second.) The Realtek 8201L is merely the PHY part of the chip, which we already support. As for the main ethernet chip, we don't currently have a driver. While a Linux driver does exist, it's totally useless in our situation. Nvidia has the driver split into a closed binary and a wrapper; there's no way to figure out how to program the chip from the wrapper alone. Your only option is to bug Nvidia into releasing either the chip's documentation or the source code to the Linux network driver. You might want to look around various Linux mailing lists and see if someone has already figured out who to contact; I doubt that anyone is happy with the binary only driver. (Especially given that virtually every other NIC has at least a GPL'd driver, even if it's poorly documented.) I'd recommend getting used to the realtek card you threw into the box; it seems unlikely that you're going to be able to get Nvidia to cave into giving out documentation without a prolonged fight. 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 Wed Jan 22 10:15: 2 2003 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 0047437B405 for ; Wed, 22 Jan 2003 10:15:00 -0800 (PST) Received: from virtucon.warpcore.org (swalker.theiqgroup.com [216.81.249.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B8AF43FCF for ; Wed, 22 Jan 2003 10:14:44 -0800 (PST) (envelope-from drevil@virtucon.warpcore.org) Received: from virtucon.warpcore.org (localhost.localdomain [127.0.0.1]) by virtucon.warpcore.org (8.12.6/8.12.6) with ESMTP id h0MIEf4q006324 for ; Wed, 22 Jan 2003 12:14:41 -0600 Received: (from drevil@localhost) by virtucon.warpcore.org (8.12.6/8.12.6/Submit) id h0MIEeCs006322 for freebsd-hackers@freebsd.org; Wed, 22 Jan 2003 12:14:40 -0600 Date: Wed, 22 Jan 2003 12:14:40 -0600 From: drevil@virtucon.warpcore.org Message-Id: <200301221814.h0MIEeCs006322@virtucon.warpcore.org> To: freebsd-hackers@freebsd.org Subject: Questions regarding 5.x series driver/emu10k1 development 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 been using *nix-like operating systems since 1996 or so. Since 2000, I've used a *nix-like OS as my everyday desktop and rarely use Windows. Recently, I decided to try FreeBSD, the setup was fairly similar to some other OS's I've used and the documentation I've read so far seems to be fairly thorough. Obviously, a lot of it is still being updated for the 5.x series. Forgive me if the following has been thoroughly answered somewhere, but I feel like I've done my due diligence in reading the 5.0 documentation and scouring the mailing lists. I have discovered that my SoundBlaster Audigy can be detected by the current emu10k1 driver, but the PCI ID detection case for it has been commented out for whatever reason. Uncommenting it causes the driver to load and to create the various /dev/dsp devices, but starting up XMMS or Gnome CD player produces no sound, the volume control application runs and I can set volume levels, but it has no effect either. The card works fine in other operating systems present on my system so I know the speakers and other things are connected correctly. Is there someone familiar with the development of the emu10k1 driver for FreeBSD that I could either assist in debugging the driver, or that could give me some helpful pointers in regards to fixing the driver myself. I am amicable to either solution. While I'm waiting for the rotten fruit to duck, is there documentation or some "hacking resources" available for writing drivers that work under FreeBSD 5.0? -- Shawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 10:49:11 2003 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 6AFBB37B401 for ; Wed, 22 Jan 2003 10:49:09 -0800 (PST) Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6991043ED8 for ; Wed, 22 Jan 2003 10:49:08 -0800 (PST) (envelope-from Vijay.Singh@nokia.com) Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax1.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0MImnB21300 for ; Wed, 22 Jan 2003 12:48:59 -0600 (CST) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 22 Jan 2003 12:48:33 -0600 Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 22 Jan 2003 12:48:05 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Subject: panic with kqueue Date: Wed, 22 Jan 2003 10:48:04 -0800 Message-ID: <4D7B558499107545BB45044C63822DDE8588CD@mvebe001.americas.nokia.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: panic with kqueue Thread-Index: AcLCRsuWgIZPoC3nEdeaKgAAhky2+w== From: To: X-OriginalArrivalTime: 22 Jan 2003 18:48:05.0330 (UTC) FILETIME=[CC71BB20:01C2C246] 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 Greetings. I am trying to port kqueue to a FreeBSD 2.x based system. I = have taken the base code from the 4.4.0-Release and then merged fixes = all the way to the current version of the kern_event.c file. Some other = changes needed were=20 1. adding struct klist p_klist to the proc struct 2. adding struct klist si_note to the selinfo struct 3. adding function pointer fo_kqfilter and file type DTYPE_KUEUE to the = file struct etc I have added a KNOTE(&p1->p_klist, NOTE_FORK | p2->p_pid); to = kern_fork.c and I get this panic Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x46 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc01716c8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 1 (init) interrupt mask =3D=20 kernel: type 12 trap, code=3D0 panic: page fault syncing disks... done kernel stack backtrace: _panic(fmt=3D100) at _panic+0x64 _panic(fmt=3Dc02dbdac) at _panic+0x64 _trap_fatal(frame=3Dbfbffebc) at _trap_fatal+0x2b3 _trap_pfault(frame=3Dbfbffebc,usermode=3D0) at _trap_pfault+0x1ac _trap(frame=3De7710010) at _trap+0x277 calltrap() at calltrap+0x15 --- trap 12, eip =3D 0xc01716c8, ebp =3D 0xbfbfff00 --- _knote(list=3Dc7c8f700,hint=3D40000005) at _knote+0x14 _fork1(p1=3Dc7c8f600,isvfork=3D0,retval=3Dbfbfff8c) at _fork1+0x3fb _fork(p=3Dc7c8f600,uap=3Dbfbfff94,retval=3Dbfbfff8c) at _fork+0x10 _syscall(frame=3D27) at _syscall+0x172 _Xsyscall() at _Xsyscall+0x2b --- syscall 2, eip =3D 0x7d05, ebp =3D 0xbfbfbd3c --- Rebooting... I would really appreciate if someone could offer some help as this is my = first real kernel work. I am guessing that either the kqueue module has = not been inited (I dont have SYSINIT and zalloc stuff, I replaced the = zalloc with malloc) or the p->p_klist isnt being initialized probably = with a SLIST_INIT( ). Please help. regards vijay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 12: 3:51 2003 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 EA28537B401 for ; Wed, 22 Jan 2003 12:03:49 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79EE843E4A for ; Wed, 22 Jan 2003 12:03:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0MK3n0i009189; Wed, 22 Jan 2003 12:03:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0MK3mq0009188; Wed, 22 Jan 2003 12:03:48 -0800 (PST) Date: Wed, 22 Jan 2003 12:03:48 -0800 (PST) From: Matthew Dillon Message-Id: <200301222003.h0MK3mq0009188@apollo.backplane.com> To: "Matthew N. Dodd" Cc: hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: patch to remove random #define MIN/MAX implementations from around the kernel References: <20030122004138.E59276-100000@sasami.jurai.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 : :On Tue, 21 Jan 2003, Matthew Dillon wrote: :> This might be useful follow-up work. i.e. the idea of getting rid of :> the use of the MIN and MAX macros in the kernel altogether. Though I'm :> not sure I like the fact that 'min' and 'max' in sys/libkern.h refer to :> unsigned ints (it really should be umin and umax or uimin and uimax). : :libkern.h defines them the same way as stand.h does. : :-- :| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | That's not saying much. stand.h is even more specialized then libkern.h. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 15:13:10 2003 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 7C47437B401 for ; Wed, 22 Jan 2003 15:13:08 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCC3643E4A for ; Wed, 22 Jan 2003 15:13:07 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0182.cvx40-bradley.dialup.earthlink.net ([216.244.42.182] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18bU33-0006JB-00; Wed, 22 Jan 2003 15:12:46 -0800 Message-ID: <3E2F251A.A471CC49@mindspring.com> Date: Wed, 22 Jan 2003 15:11:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yury Tarasievich Cc: freebsd-hackers@freebsd.org Subject: Re: verbose device probing ? References: <20030122024713.I43637-100000@haldjas.folklore.ee> <3E2EBC79.5020704@grsu.by> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a447cf5551a207e3fecaf0c42dd72ebe0ba7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c 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 Yury Tarasievich wrote: > Narvi wrote: > >If only Joe-Bob or some other very limited set of people have the > >card, then the severity of the bug in the *FreeBSD* bug database > >should probably not be 5 - orherwise the database will contain a > >large amount of bugs that claim to be of high severity but only > >ever affect negliblme amounts of pevple > > I'd say there is *no* such thing as "negligible amount of people" in > FreeBSD community. In Windows community, perhaps. Not here. Remember we > aren't yet talking millions of installations and must-setup thing. No > negligible (discardable) amount of people, then. Please. I understand your point, by my example implied "one person who can't program well enough to fix it themselves, and who has a one of a kind oddball variation on a standard card, which could be taken ito account by the driver, with code specific to that one card in all of human controlled space". It's the degenerate border case. I didn't expect Joe-Bob to be supported, unless he did something like spend enough on postage to send the card itself, along with documentation, to someone who cared enough about their personal relationship with Joe-Bob, and/or evangelizing FreeBSD, to do the work. With that much postage, and that much desire to help out, there are three real fixes: 1) Joe-Bob can spend the postage on a new card instead 2) The samaritan can buy a new card, and replace Joe-Bob's prototype card's guts, and just not tell him (what Joe-Bob doesn't know, won't hurt him). 3) The samaritan can actually do the changes, and fight the uphill battle to get the code committed to FreeBSD proper These also happen to be the order in which I would consider addressing the problem... ;^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 18:55: 4 2003 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 D6A3537B401 for ; Wed, 22 Jan 2003 18:55:02 -0800 (PST) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C20843F18 for ; Wed, 22 Jan 2003 18:55:00 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-a139.otenet.gr [212.205.215.139]) by mailsrv.otenet.gr (8.12.6/8.12.6) with ESMTP id h0N2sf58002786 for ; Thu, 23 Jan 2003 04:54:51 +0200 (EET) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.6/8.12.6) with ESMTP id h0N2sbxu040546 for ; Thu, 23 Jan 2003 04:54:37 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.6/8.12.6/Submit) id h0N2sbvs040545 for hackers@freebsd.org; Thu, 23 Jan 2003 04:54:37 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 23 Jan 2003 04:54:37 +0200 From: Giorgos Keramidas To: hackers@freebsd.org Subject: Checking sockaddr_in port number for overflow Message-ID: <20030123025437.GA40516@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 been trying to think of a good way to check for overflow of port numbers of PF_INET sockets that are passed by the user. So far, this is what I have come up with: : #include : : #include : #include : #include : #include : #include : : int : main(int argc, char *argv[]) : { : static long tmp; : static char *errp; : in_port_t port; : : if (argc != 2) : errx(1, "usage: %s port", argv[0]); : : errno == 0; : tmp = strtol(argv[1], &errp, 0); : if (errp == argv[1] || errno == EINVAL || errno == ERANGE) : errx(1, "invalid number '%s'", argv[1]); : if (tmp > IPPORT_MAX) : errx(1, "%ld will overflow as a port number (max %d)", : tmp, IPPORT_MAX); : : port = (in_port_t)tmp; : printf("Using port number %d\n", port); : return (0); : } Does this look ok to you all? Have I missed anything obvious that I should also check? - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 19:38: 3 2003 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 4E3E537B401 for ; Wed, 22 Jan 2003 19:38:01 -0800 (PST) Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A42FC43ED8 for ; Wed, 22 Jan 2003 19:37:59 -0800 (PST) (envelope-from enache@rdslink.ro) Received: (qmail 18448 invoked from network); 23 Jan 2003 03:36:55 -0000 Received: from unknown (HELO ratsnest.hole) (213.157.186.188) by mail.rdslink.ro with SMTP; 23 Jan 2003 03:36:55 -0000 Received: from ratsnest.hole (localhost [127.0.0.1]) by ratsnest.hole (8.12.5/8.12.5) with ESMTP id h0N3SXeq005083 for ; Thu, 23 Jan 2003 05:28:34 +0200 Received: (from adi@localhost) by ratsnest.hole (8.12.5/8.12.5/Submit) id h0N3SXmF005081 for hackers@freebsd.org; Thu, 23 Jan 2003 05:28:33 +0200 Date: Thu, 23 Jan 2003 05:28:33 +0200 From: Enache Adrian To: hackers@freebsd.org Subject: signals lost when linked with libc_r ? Message-ID: <20030123032833.GA5075@ratsnest.hole> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 FreeBSD seems to loose signals in programs linked with libc_r. sigaction.c ( freely translated from Perl's ext/POSIX/t/posix.t test) -----------------8x---------------------- #include #include #include void sighup(int dummy) { kill(getpid(),SIGINT); sleep(1); printf("sigint delayed ...\n"); } void sigint(int dummy) { printf("SIGINT !\n"); } struct sigaction act; int main() { act.sa_handler = sighup; sigaddset(&act.sa_mask, SIGINT); sigaction(SIGHUP, &act, NULL); signal(SIGINT,sigint); kill(getpid(),SIGHUP); sleep(2); printf("*\n"); return 0; } -----------------8x----------------------- csh# cc sigaction.c -o sigaction csh# ./sigaction sigint delayed ... SIGINT ! * csh# cc -lc_r sigaction.c -o sigaction csh# ./sigaction sigint delayed ... * (this is -CURRENT, cvsup'ed 3 days ago) Please enlighten me. Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 21:49:40 2003 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 7164F37B405 for ; Wed, 22 Jan 2003 21:49:39 -0800 (PST) Received: from smtp.netli.com (ip2-pal-focal.netli.com [66.243.52.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 527B243F3F for ; Wed, 22 Jan 2003 21:49:38 -0800 (PST) (envelope-from vlm@netli.com) Received: (qmail 11435 invoked by uid 84); 23 Jan 2003 05:49:25 -0000 Received: from vlm@netli.com by l3-1 with qmail-scanner-0.96 (uvscan: v4.1.40/v4121. . Clean. Processed in 0.119551 secs); 23 Jan 2003 05:49:25 -0000 Received: from unknown (HELO netli.com) (192.168.238.32) by mx01-pal-lan.netli.lan with SMTP; 23 Jan 2003 05:49:25 -0000 Message-ID: <3E2F8250.3080300@netli.com> Date: Wed, 22 Jan 2003 21:49:04 -0800 From: Lev Walkin Organization: Netli, Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021117 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas Cc: hackers@freebsd.org Subject: Re: Checking sockaddr_in port number for overflow References: <20030123025437.GA40516@gothmog.gr> 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 Giorgos Keramidas wrote: > I have been trying to think of a good way to check for overflow of > port numbers of PF_INET sockets that are passed by the user. So far, > this is what I have come up with: > > : > : errno == 0; > : tmp = strtol(argv[1], &errp, 0); > : if (errp == argv[1] || errno == EINVAL || errno == ERANGE) > : errx(1, "invalid number '%s'", argv[1]); > : if (tmp > IPPORT_MAX) > : errx(1, "%ld will overflow as a port number (max %d)", > : tmp, IPPORT_MAX); > > Does this look ok to you all? > Have I missed anything obvious that I should also check? tmp <= 0. -- Lev Walkin vlm@netli.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 22 23:15:37 2003 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 63E1237B401 for ; Wed, 22 Jan 2003 23:15:36 -0800 (PST) Received: from mailhost.gu.edu.au (kraken.itc.gu.edu.au [132.234.250.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF83643F1E for ; Wed, 22 Jan 2003 23:15:34 -0800 (PST) (envelope-from steve@cit.gu.edu.au) Received: from hobbit.cit.gu.edu.au (IDENT:ky5zE5zdEOQd26tq14UGZOzxTgKDOVEl@hobbit.cit.gu.edu.au [132.234.86.7]) by mailhost.gu.edu.au (8.10.1/8.10.1) with ESMTP id h0N7AtH27868; Thu, 23 Jan 2003 17:10:55 +1000 (EST) Received: from localhost (steve@localhost) by hobbit.cit.gu.edu.au (8.11.6/8.11.6) with ESMTP id h0N7AqE20869; Thu, 23 Jan 2003 17:10:53 +1000 Date: Thu, 23 Jan 2003 17:10:52 +1000 (EST) From: Steven Goodwin To: hackers@freebsd.org Cc: Giorgos Keramidas Subject: Re: Checking sockaddr_in port number for overflow In-Reply-To: <3E2F8250.3080300@netli.com> 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 Wed, 22 Jan 2003, Lev Walkin wrote: > Giorgos Keramidas wrote: > > I have been trying to think of a good way to check for overflow of > > port numbers of PF_INET sockets that are passed by the user. So far, > > this is what I have come up with: > > > > : > > : errno == 0; I hope I'm not being pedantic, but don't you mean errno = 0; > > : tmp = strtol(argv[1], &errp, 0); > > : if (errp == argv[1] || errno == EINVAL || errno == ERANGE) > > : errx(1, "invalid number '%s'", argv[1]); > > : if (tmp > IPPORT_MAX) > > : errx(1, "%ld will overflow as a port number (max %d)", > > : tmp, IPPORT_MAX); > > > > Does this look ok to you all? > > Have I missed anything obvious that I should also check? > > tmp <= 0. > Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 5:48:54 2003 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 128B737B405 for ; Thu, 23 Jan 2003 05:48:48 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 0532343F5B for ; Thu, 23 Jan 2003 05:48:40 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 18384 invoked by uid 1000); 23 Jan 2003 13:47:49 -0000 Date: Thu, 23 Jan 2003 15:47:49 +0200 From: Peter Pentchev To: Ceri Davies Cc: Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, Yar Tikhiy , hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123134749.GA377@straylight.oblivion.bg> Mail-Followup-To: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, Yar Tikhiy , hackers@FreeBSD.org References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="v9Ux+11Zm5mwPlX6" Content-Disposition: inline In-Reply-To: <20030123101216.GA2856@submonkey.net> User-Agent: Mutt/1.5.3i 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 --v9Ux+11Zm5mwPlX6 Content-Type: multipart/mixed; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 23, 2003 at 10:12:16AM +0000, Ceri Davies wrote: [longish exchange preserved for the benefit of the newly-CC'd people: yar@ as a de-facto maintainer of libexec/ftpd, and -hackers for additional discussion] > On Thu, Jan 23, 2003 at 10:12:24AM +0200, Peter Pentchev wrote: > > On Thu, Jan 23, 2003 at 01:09:29AM +0100, Julian Mayer wrote: > > > hello > > > there is a bug in portupgrade-20021216: when you change the FTP port = in=20 > > > /etc/services to run the FTP demon on another port, portupgrade is=20 > > > unable to download ports/packages via ftp > > > is there a workaround? > >=20 > > Errr.. this is not a bug in portupgrade, but the way most (all?) FTP > > clients work. If you change the port for the 'ftp' service, *any* > > program that asks about the 'ftp' service will use the new port, > > including all FTP clients that try to make outgoing connections. >=20 > In that case, it sounds like a bug in our stock ftpd. >=20 > DESCRIPTION > Ftpd is the Internet File Transfer Protocol server process. The ser= ver > uses the TCP protocol and listens at the port specified in the ``ftp= '' > service specification; see services(5). >=20 > If this breaks outgoing ftp connections, then that's quite serious. >=20 > > The appropriate way to "fix" that problem is to NOT change the port for > > the 'ftp' service, but merely specify a different port on which to run > > the FTP server. >=20 > RTF ftpd(8) manual - there isn't any other (documented) way to do it. >=20 > If I'm not missing something obvious, then I'll file a PR for this later. Yes, it would seem that the stock ftpd does not provide a way to specify a different port/service to use in daemon mode. In inetd mode, everything is fine and dandy. Attached is a patch to the libexec/ftpd source, which adds a new -P option taking an argument of either a numeric port number or a service name as described in the getaddrinfo(3) manual page. What do people think about adding this functionality? G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 The rest of this sentence is written in Thailand, on --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=windows-1251 Content-Disposition: attachment; filename="libexec-ftpd.patch" Content-Transfer-Encoding: quoted-printable Index: src/libexec/ftpd/ftpd.8 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/libexec/ftpd/ftpd.8,v retrieving revision 1.56 diff -u -r1.56 ftpd.8 --- src/libexec/ftpd/ftpd.8 27 Dec 2002 12:15:31 -0000 1.56 +++ src/libexec/ftpd/ftpd.8 23 Jan 2003 13:35:57 -0000 @@ -43,6 +43,7 @@ .Op Fl 46ADdEMmOoRrSUvW .Op Fl l Op Fl l .Op Fl a Ar address +.Op Fl P Ar port .Op Fl p Ar file .Op Fl T Ar maxtimeout .Op Fl t Ar timeout @@ -133,6 +134,14 @@ .It Fl o Put server in write-only mode. RETR is disabled, preventing downloads. +.It Fl P +When +.Fl D +is specified, accept connections on the specified +.Ar port +or service name instead of using the default +.Nm ftp +port. .It Fl p When .Fl D Index: src/libexec/ftpd/ftpd.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/libexec/ftpd/ftpd.c,v retrieving revision 1.133 diff -u -r1.133 ftpd.c --- src/libexec/ftpd/ftpd.c 21 Jan 2003 05:13:02 -0000 1.133 +++ src/libexec/ftpd/ftpd.c 23 Jan 2003 12:48:42 -0000 @@ -277,6 +277,7 @@ FILE *fd; int error; char *bindname =3D NULL; + const char *bindport =3D "ftp"; int family =3D AF_UNSPEC; int enable_v4 =3D 0; struct sigaction sa; @@ -296,7 +297,7 @@ #endif /* OLD_SETPROCTITLE */ =20 =20 - while ((ch =3D getopt(argc, argv, "46a:AdDElmMoOp:rRSt:T:u:UvW")) !=3D -1= ) { + while ((ch =3D getopt(argc, argv, "46a:AdDElmMoOp:P:rRSt:T:u:UvW")) !=3D = -1) { switch (ch) { case '4': enable_v4 =3D 1; @@ -352,6 +353,10 @@ pid_file =3D optarg; break; =20 + case 'P': + bindport =3D optarg; + break; + case 'r': readonly =3D 1; break; @@ -436,11 +441,11 @@ hints.ai_socktype =3D SOCK_STREAM; hints.ai_protocol =3D 0; hints.ai_flags =3D AI_PASSIVE; - error =3D getaddrinfo(bindname, "ftp", &hints, &res); + error =3D getaddrinfo(bindname, bindport, &hints, &res); if (error) { if (family =3D=3D AF_UNSPEC) { hints.ai_family =3D AF_UNSPEC; - error =3D getaddrinfo(bindname, "ftp", &hints, + error =3D getaddrinfo(bindname, bindport, &hints, &res); } } --a8Wt8u1KmwUX3Y2C-- --v9Ux+11Zm5mwPlX6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+L/KF7Ri2jRYZRVMRAnjoAKC6dH9ZjYxYIaeiXittk5hXHnth/gCeIM3L kNYfRbACZ4ljF3KKmHvIvGU= =djhX -----END PGP SIGNATURE----- --v9Ux+11Zm5mwPlX6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 6: 9: 1 2003 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 F3DC337B401 for ; Thu, 23 Jan 2003 06:08:59 -0800 (PST) Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1707E43F18 for ; Thu, 23 Jan 2003 06:08:59 -0800 (PST) (envelope-from corecode@corecode.ath.cx) Received: from fwd03.sul.t-online.de by mailout09.sul.t-online.com with smtp id 18bhqt-0005D8-0C; Thu, 23 Jan 2003 14:57:07 +0100 Received: from pride.uni.stoert.net (320050403952-0001@[217.224.162.215]) by fmrl03.sul.t-online.com with esmtp id 18bhqQ-0ZPjWaC; Thu, 23 Jan 2003 14:56:38 +0100 Received: from terrorfish.uni.stoert.net (terrorfish.uni.stoert.net [10.150.180.178]) by pride.uni.stoert.net (Postfix) with ESMTP id 82F9813560B; Thu, 23 Jan 2003 14:56:38 +0100 (CET) Received: from terrorfish.uni.stoert.net (localhost [127.0.0.1]) by terrorfish.uni.stoert.net (8.12.6/8.12.6) with ESMTP id h0NDvNag003594; Thu, 23 Jan 2003 14:57:23 +0100 (CET) (envelope-from corecode@terrorfish.uni.stoert.net) Received: (from corecode@localhost) by terrorfish.uni.stoert.net (8.12.6/8.12.6/Submit) id h0NDvMaw003593; Thu, 23 Jan 2003 14:57:22 +0100 (CET) Date: Thu, 23 Jan 2003 14:57:19 +0100 From: "Simon 'corecode' Schubert" To: Peter Pentchev Cc: hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-Id: <20030123145719.68f43d12.corecode@corecode.ath.cx> In-Reply-To: <20030123134749.GA377@straylight.oblivion.bg> References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="oQGps=.8ZY4o=ABj" X-Sender: 320050403952-0001@t-dialin.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 --oQGps=.8ZY4o=ABj Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Lately Peter Pentchev told: > Attached is a patch to the libexec/ftpd source, which adds a new -P > option taking an argument of either a numeric port number or a service > name as described in the getaddrinfo(3) manual page. What do people > think about adding this functionality? looks good cheers simon -- /"\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News --oQGps=.8ZY4o=ABj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+L/TCr5S+dk6z85oRAk/oAKCy4vnYYtO1t5Jx48seB1r+IER0kwCguypv Hxv1H2nKuiLAX1iz6Quv4yA= =xTGI -----END PGP SIGNATURE----- --oQGps=.8ZY4o=ABj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 8: 6:30 2003 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 3451C37B405; Thu, 23 Jan 2003 08:06:28 -0800 (PST) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3A5943EB2; Thu, 23 Jan 2003 08:06:22 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3/8.12.3) with ESMTP id h0NG69sA004077; Thu, 23 Jan 2003 19:06:13 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3/8.12.3/Submit) id h0NG66tR004076; Thu, 23 Jan 2003 19:06:06 +0300 (MSK) (envelope-from yar) Date: Thu, 23 Jan 2003 19:06:05 +0300 From: Yar Tikhiy To: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123160605.GA2473@comp.chem.msu.su> References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030123134749.GA377@straylight.oblivion.bg> User-Agent: Mutt/1.5.3i 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, Jan 23, 2003 at 03:47:49PM +0200, Peter Pentchev wrote: > On Thu, Jan 23, 2003 at 10:12:16AM +0000, Ceri Davies wrote: > > On Thu, Jan 23, 2003 at 10:12:24AM +0200, Peter Pentchev wrote: > > > On Thu, Jan 23, 2003 at 01:09:29AM +0100, Julian Mayer wrote: > > > > hello > > > > there is a bug in portupgrade-20021216: when you change the FTP port in > > > > /etc/services to run the FTP demon on another port, portupgrade is > > > > unable to download ports/packages via ftp > > > > is there a workaround? > > > > > > Errr.. this is not a bug in portupgrade, but the way most (all?) FTP > > > clients work. If you change the port for the 'ftp' service, *any* > > > program that asks about the 'ftp' service will use the new port, > > > including all FTP clients that try to make outgoing connections. > > > > In that case, it sounds like a bug in our stock ftpd. > > > > DESCRIPTION > > Ftpd is the Internet File Transfer Protocol server process. The server > > uses the TCP protocol and listens at the port specified in the ``ftp'' > > service specification; see services(5). > > > > If this breaks outgoing ftp connections, then that's quite serious. > > > > > The appropriate way to "fix" that problem is to NOT change the port for > > > the 'ftp' service, but merely specify a different port on which to run > > > the FTP server. > > > > RTF ftpd(8) manual - there isn't any other (documented) way to do it. > > > > If I'm not missing something obvious, then I'll file a PR for this later. > > Yes, it would seem that the stock ftpd does not provide a way to specify > a different port/service to use in daemon mode. In inetd mode, > everything is fine and dandy. > > Attached is a patch to the libexec/ftpd source, which adds a new -P > option taking an argument of either a numeric port number or a service > name as described in the getaddrinfo(3) manual page. What do people > think about adding this functionality? As for me, I think that a) editing standard lines in /etc/services is a rather bad idea since the file lists _standard_ service endpoints; OTOH, adding a site-specific service endpoint to the file is all right, b) the port option to ftpd(8) would be nice. However, there seems to be a hard-coded value for not only the FTP control port, but the FTP default data port as well. I'd like to fix both issues at once since RFC 959 specifies explicitly that the default data port should be 1 less than the control port. I hope I'll introduce the port option to our stock ftpd(8) in a couple of days. Thanks for the patch. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 9:47:18 2003 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 94E1437B401; Thu, 23 Jan 2003 09:47:14 -0800 (PST) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B5CA43E4A; Thu, 23 Jan 2003 09:47:12 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3/8.12.3) with ESMTP id h0NHl8sA009149; Thu, 23 Jan 2003 20:47:08 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3/8.12.3/Submit) id h0NHl6gE009148; Thu, 23 Jan 2003 20:47:06 +0300 (MSK) (envelope-from yar) Date: Thu, 23 Jan 2003 20:47:06 +0300 From: Yar Tikhiy To: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123174706.GA8943@comp.chem.msu.su> References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030123134749.GA377@straylight.oblivion.bg> User-Agent: Mutt/1.5.3i 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, Jan 23, 2003 at 03:47:49PM +0200, Peter Pentchev wrote: > > Attached is a patch to the libexec/ftpd source, which adds a new -P > option taking an argument of either a numeric port number or a service > name as described in the getaddrinfo(3) manual page. What do people > think about adding this functionality? Peter, here is a bit reworked version of your patch. Does it look reasonable? -- Yar Index: ftpd.8 =================================================================== RCS file: /home/ncvs/src/libexec/ftpd/ftpd.8,v retrieving revision 1.56 diff -u -r1.56 ftpd.8 --- ftpd.8 27 Dec 2002 12:15:31 -0000 1.56 +++ ftpd.8 23 Jan 2003 17:39:59 -0000 @@ -43,6 +43,7 @@ .Op Fl 46ADdEMmOoRrSUvW .Op Fl l Op Fl l .Op Fl a Ar address +.Op Fl P Ar port .Op Fl p Ar file .Op Fl T Ar maxtimeout .Op Fl t Ar timeout @@ -55,7 +56,9 @@ server process. The server uses the .Tn TCP protocol -and listens at the port specified in the +and listens at the port specified with the +.Fl P +option or in the .Dq ftp service specification; see .Xr services 5 . @@ -133,6 +136,14 @@ .It Fl o Put server in write-only mode. RETR is disabled, preventing downloads. +.It Fl P +When +.Fl D +is specified, accept connections at +.Ar port , +specified as a numeric value or service name, instead of at the default +.Dq ftp +port. .It Fl p When .Fl D Index: ftpd.c =================================================================== RCS file: /home/ncvs/src/libexec/ftpd/ftpd.c,v retrieving revision 1.133 diff -u -r1.133 ftpd.c --- ftpd.c 21 Jan 2003 05:13:02 -0000 1.133 +++ ftpd.c 23 Jan 2003 17:40:01 -0000 @@ -115,6 +115,7 @@ int daemon_mode; int data; +int dataport; int logged_in; struct passwd *pw; int ftpdebug; @@ -277,6 +278,7 @@ FILE *fd; int error; char *bindname = NULL; + const char *bindport = "ftp"; int family = AF_UNSPEC; int enable_v4 = 0; struct sigaction sa; @@ -296,7 +298,7 @@ #endif /* OLD_SETPROCTITLE */ - while ((ch = getopt(argc, argv, "46a:AdDElmMoOp:rRSt:T:u:UvW")) != -1) { + while ((ch = getopt(argc, argv, "46a:AdDElmMoOp:P:rRSt:T:u:UvW")) != -1) { switch (ch) { case '4': enable_v4 = 1; @@ -352,6 +354,10 @@ pid_file = optarg; break; + case 'P': + bindport = optarg; + break; + case 'r': readonly = 1; break; @@ -436,11 +442,11 @@ hints.ai_socktype = SOCK_STREAM; hints.ai_protocol = 0; hints.ai_flags = AI_PASSIVE; - error = getaddrinfo(bindname, "ftp", &hints, &res); + error = getaddrinfo(bindname, bindport, &hints, &res); if (error) { if (family == AF_UNSPEC) { hints.ai_family = AF_UNSPEC; - error = getaddrinfo(bindname, "ftp", &hints, + error = getaddrinfo(bindname, bindport, &hints, &res); } } @@ -553,6 +559,7 @@ syslog(LOG_ERR, "getsockname (%s): %m",argv[0]); exit(1); } + dataport = ntohs(ctrl_addr.su_port) - 1; /* as per RFC 959 */ #ifdef VIRTUAL_HOSTING /* select our identity from virtual host table */ selecthost(&ctrl_addr); @@ -1722,7 +1729,7 @@ syslog(LOG_WARNING, "data setsockopt (SO_REUSEADDR): %m"); /* anchor socket to avoid multi-homing problems */ data_source = ctrl_addr; - data_source.su_port = htons(20); /* ftp-data port */ + data_source.su_port = htons(dataport); for (tries = 1; ; tries++) { if (bind(s, (struct sockaddr *)&data_source, data_source.su_len) >= 0) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 9:54:56 2003 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 2F59937B401 for ; Thu, 23 Jan 2003 09:54:54 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id F3A1543F13 for ; Thu, 23 Jan 2003 09:54:42 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 20364 invoked by uid 1000); 23 Jan 2003 17:53:44 -0000 Date: Thu, 23 Jan 2003 19:53:44 +0200 From: Peter Pentchev To: Yar Tikhiy Cc: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123175344.GC19717@straylight.oblivion.bg> Mail-Followup-To: Yar Tikhiy , Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> <20030123174706.GA8943@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <20030123174706.GA8943@comp.chem.msu.su> User-Agent: Mutt/1.5.3i 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 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 23, 2003 at 08:47:06PM +0300, Yar Tikhiy wrote: > On Thu, Jan 23, 2003 at 03:47:49PM +0200, Peter Pentchev wrote: > >=20 > > Attached is a patch to the libexec/ftpd source, which adds a new -P > > option taking an argument of either a numeric port number or a service > > name as described in the getaddrinfo(3) manual page. What do people > > think about adding this functionality? >=20 > Peter, here is a bit reworked version of your patch. > Does it look reasonable? Yes, this looks fine; the data connection port issue was brought up by Matthew Seaman in a private message to me, which I did not respond to immediately, because I wanted to feel the general thoughts on the subject. Now that you have incorporated it into your patch, it all sounds great :) I see that you have also changed my '.Nm' macro for the 'ftp' service to '.Dq'; that's fine too, I was in quite a bit of doubt myself over exactly which mdoc macro to use. The '.Nm' came from the telnet(1) manual page, but it did not look quite right to me. Thanks for your fast reaction :) I guess libexec/ftpd is your code, so it's your call to commit at will if nobody objects. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 "yields falsehood, when appended to its quotation." yields falsehood, when = appended to its quotation. --K8nIJk4ghYZn606h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+MCwo7Ri2jRYZRVMRAg5bAJ9/LZIyfPy8auzMhWQ59m0riZ/wBQCgixWT AAPf9PIEJgyggJp000OWgq4= =gbNo -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 10:11:27 2003 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 9AAC437B401; Thu, 23 Jan 2003 10:11:26 -0800 (PST) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9147D43ED8; Thu, 23 Jan 2003 10:11:24 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3/8.12.3) with ESMTP id h0NIBMsA010444; Thu, 23 Jan 2003 21:11:22 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3/8.12.3/Submit) id h0NIBLdU010435; Thu, 23 Jan 2003 21:11:21 +0300 (MSK) (envelope-from yar) Date: Thu, 23 Jan 2003 21:11:21 +0300 From: Yar Tikhiy To: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123181121.GB8943@comp.chem.msu.su> References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> <20030123174706.GA8943@comp.chem.msu.su> <20030123175344.GC19717@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030123175344.GC19717@straylight.oblivion.bg> User-Agent: Mutt/1.5.3i 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, Jan 23, 2003 at 07:53:44PM +0200, Peter Pentchev wrote: > > Peter, here is a bit reworked version of your patch. > > Does it look reasonable? > > Yes, this looks fine; the data connection port issue was brought up by > Matthew Seaman in a private message to me, which I did not respond to > immediately, because I wanted to feel the general thoughts on the > subject. Now that you have incorporated it into your patch, it all > sounds great :) Thanks! > I see that you have also changed my '.Nm' macro for the 'ftp' service to > '.Dq'; that's fine too, I was in quite a bit of doubt myself over > exactly which mdoc macro to use. The '.Nm' came from the telnet(1) > manual page, but it did not look quite right to me. As far as I know mdoc, .Nm should be used once with an argument, the subject of the page, and then it may be used with no argument to refer to the subject since it remembers its argument. Therefore excuse me, but your using ".Nm ftp" in the middle of the page to refer to "ftp" as a TCP service wasn't quite correct :-) -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 10:16:27 2003 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 5751B37B401 for ; Thu, 23 Jan 2003 10:16:25 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 0B6B143F5F for ; Thu, 23 Jan 2003 10:16:19 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 20744 invoked by uid 1000); 23 Jan 2003 18:15:27 -0000 Date: Thu, 23 Jan 2003 20:15:27 +0200 From: Peter Pentchev To: Yar Tikhiy Cc: Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org Subject: Re: FreeBSD Port: portupgrade-20021216 Message-ID: <20030123181527.GB19722@straylight.oblivion.bg> Mail-Followup-To: Yar Tikhiy , Ceri Davies , Julian Mayer , knu@FreeBSD.org, ports@FreeBSD.org, hackers@FreeBSD.org References: <20030123081224.GA471@straylight.oblivion.bg> <20030123101216.GA2856@submonkey.net> <20030123134749.GA377@straylight.oblivion.bg> <20030123174706.GA8943@comp.chem.msu.su> <20030123175344.GC19717@straylight.oblivion.bg> <20030123181121.GB8943@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <20030123181121.GB8943@comp.chem.msu.su> User-Agent: Mutt/1.5.3i 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 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 23, 2003 at 09:11:21PM +0300, Yar Tikhiy wrote: > On Thu, Jan 23, 2003 at 07:53:44PM +0200, Peter Pentchev wrote: > > > Peter, here is a bit reworked version of your patch. > > > Does it look reasonable? > >=20 > > Yes, this looks fine; the data connection port issue was brought up by > > Matthew Seaman in a private message to me, which I did not respond to > > immediately, because I wanted to feel the general thoughts on the > > subject. Now that you have incorporated it into your patch, it all > > sounds great :) >=20 > Thanks! >=20 > > I see that you have also changed my '.Nm' macro for the 'ftp' service to > > '.Dq'; that's fine too, I was in quite a bit of doubt myself over > > exactly which mdoc macro to use. The '.Nm' came from the telnet(1) > > manual page, but it did not look quite right to me. > =20 > As far as I know mdoc, .Nm should be used once with an argument, > the subject of the page, and then it may be used with no argument > to refer to the subject since it remembers its argument. > Therefore excuse me, but your using ".Nm ftp" in the middle of the > page to refer to "ftp" as a TCP service wasn't quite correct :-) Yes, I know it wasn't; but a quick test revealed that at least with -STABLE's groff, '.Nm ftp' used in the middle of the ftpd manual page did not influence the further calls of '.Nm' without arguments - all the rest of the page correctly displayed 'ftpd' at each '.Nm' usage. Still, it was not correct, and I freely admit it :) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 You have, of course, just begun reading the sentence that you have just fin= ished reading. --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+MDE/7Ri2jRYZRVMRAvrKAJ4rpiSv8Oa2lurdoCpnzimS+pRysgCffYwV PsFgViorJJm+BjJJQn6bWAY= =xAy4 -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 11:59:16 2003 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 21E1E37B401 for ; Thu, 23 Jan 2003 11:59:16 -0800 (PST) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id A924C43EB2 for ; Thu, 23 Jan 2003 11:59:14 -0800 (PST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost [127.0.0.1]) by fump.kawo2.rwth-aachen.de (8.12.6/8.12.6) with ESMTP id h0NJxCkb063381; Thu, 23 Jan 2003 20:59:12 +0100 (CET) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.6/8.12.6/Submit) id h0NJxBkm063380; Thu, 23 Jan 2003 20:59:11 +0100 (CET) Date: Thu, 23 Jan 2003 20:59:11 +0100 From: Alexander Langer To: Patrick Soltani Cc: Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: panic: icmp_error: bad length Message-ID: <20030123195911.GA40248@fump.kawo2.rwth-aachen.de> References: <3DBB075EEB95944492E127F2B9A96FAF5DDDDC@ultra-exchange.ultradns.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DBB075EEB95944492E127F2B9A96FAF5DDDDC@ultra-exchange.ultradns.com> X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. User-Agent: Mutt/1.5.1i 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 JFYI, the patch Ian recently MFCed does fix the problem here on our 4.7 box. Thanks Ian :-) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 20:14:43 2003 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 C2EA237B401 for ; Thu, 23 Jan 2003 20:14:42 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A87543E4A for ; Thu, 23 Jan 2003 20:14:41 -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 h0O4Eei07490 for ; Thu, 23 Jan 2003 20:14:40 -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 UAA16346 for ; Thu, 23 Jan 2003 20:14:40 -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 VAA22692 for ; Thu, 23 Jan 2003 21:14:37 -0700 (MST) Message-ID: <3E30BDA6.8060200@btc.adaptec.com> Date: Thu, 23 Jan 2003 21:14:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021125 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: November-December 2002 FreeBSD Bi-Monthly Status report Content-Type: text/plain; charset=ISO-8859-1; 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 20:16: 4 2003 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 5460437B401 for ; Thu, 23 Jan 2003 20:15:51 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9964843FE9 for ; Thu, 23 Jan 2003 20:15:11 -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 h0O4FAi07543 for ; Thu, 23 Jan 2003 20:15:10 -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 UAA16372 for ; Thu, 23 Jan 2003 20:15:04 -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 VAA22696 for ; Thu, 23 Jan 2003 21:15:00 -0700 (MST) Message-ID: <3E30BDBD.3010909@btc.adaptec.com> Date: Thu, 23 Jan 2003 21:14:53 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021125 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: November-December 2002 FreeBSD Bi-Monthly Status report Content-Type: multipart/mixed; boundary="------------040704040107010308060008" 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 This is a multi-part message in MIME format. --------------040704040107010308060008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit --------------040704040107010308060008 Content-Type: text/plain; name="report-nov-2002-dec-2002.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="report-nov-2002-dec-2002.txt" November-December 2002 Status Report Introduction: At long last, FreeBSD 5.0 is here. Along with putting the final polish on the tree, FreeBSD developers somehow found the time to work on other things too. IA64 took some major steps towards working on the Itanium2 platform, an effort was started to convert all drivers to use busdma and ban vtophys(), hardware crypto support and DEVD hit the tree, NewReno was fixed and effort began on locking down the network layer of the kernel. Also high performance, modular scheduler started taking shape and will be a welcome addition to the kernel soon. Looking forward, the focus will be on stabilizing and improving the performance of 5.0. The RELENG_5 (aka 5-STABLE) branch will be created once we've reached our goals in this area, so hopefully we will get there quickly. Meanwhile, preparations for the next release from the 4.x series, 4.8, will begin soon. Of course, the best way to get 5.x to stabilize os to install and run it! Thanks, Scott Long, Robert Watson _________________________________________________________________ Bluetooth stack for FreeBSD (Netgraph implementation) URL: http://www.geocities.com/m_evmenkin/ URL: http://bluez.sf.net URL: http://sourceforge.net/projects/openobex Contact: Maksim Yevmenkin I'm very pleased to announce that all kernel modules and few userland tools made it to the FreeBSD source tree. Many thanks to Julian Elischer. Unfortunately no big changes since the last report. Some minor problems have been discovered and patches are available on request. I will prepare all the patches and submit them to Julian for review. OBEX server and client (based on OpenOBEX library) is almost complete. I'm currently doing interoperability testing. If anyone has hardware and time please contact me. The HCI security daemon has been implemented and tested with Sony Ericsson T68i cell phone and Windows stack. It is now possible to setup secure Bluetooth connections. A few people have complained about RFCOMM daemon. These individuals want to use GPRS and Bluetooth enabled cell phone to access Internet. If you have this problem please contact me for possible workaround. My next goal is to get robust RFCOMM implementation to address all these issues. _________________________________________________________________ busdma driver conversion project URL: http://www.FreeBSD.org/projects/busdma/ Contact: Maxime Henrion This project has been coming along pretty well. The amd(4) and xl(4) drivers have now been converted to use the busdma API, sparc64 got the bus_dmamap_load_mbuf() and bus_dmamap_load_uio() functions, and the gem(4) and hme(4) drivers have been updated to use bus_dmamap_load_mbuf() instead of bus_dmamap_load(). A lot more still needs to be done, as shown on the project's page. A fair number of conversions are on their way though, and we can expect a fair number of drivers to be converted soon, thanks to all the developers who are working on this project. _________________________________________________________________ DEVD Contact: Warner Losh Devd has been integrated into FreeBSD 5.0-RELEASE. The integrated code supports a range of configuration options. The config files are fully parsed now and their actions are performed. Future work in this area are likely to be limited to imporving the devctl interface. /dev/devctl likely will be a cloneable device in future versions. Individual device control via devctl is also planned. _________________________________________________________________ Donations Team Status Report URL: http://www.FreeBSD.org/donations/ URL: http://www.FreeBSD.org/donations/wantlist.html URL: http://www.FreeBSD.org/donations/donors.html Contact: Michael Lucas The Donations project expedited several dozen donations during 2002, and was able to place most of what was offered. We still are in dire need of SMP and Sparc systems. You can see information on our needs and donations that have been handled by the team on the donations web page. We are relying increasingly upon the developer wantlist to place items offered to the Project, and using the commit statistics to help place items. As such, active committers who ask for what they want beforehand have a decent chance of getting it. Less active committers, and committers who do not ask for what they want, will be lower in our priorities but will not be excluded. We are in the process of streamlining the tax deduction process for donations, and hope to have news on that shortly. We are also always working to accelerate and reduce our internal processes, to get the most equipment in the hands of the most people as quickly as possible. I especially want to thank David O'Brien and Tom Rhodes for stepping up and making the team far more successful. Also, the FreeBSD Foundation has been quite helpful in handling tax-deductible contributions. _________________________________________________________________ Fast IPsec Status Contact: Sam Leffler The main goal of this project is to modify the IPsec protocols to use the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A secondary goal is to do general performance tuning of the IPsec protocols. This work will be part of the 5.0 release. Performance has been improved due to work on the crypto subsystem. _________________________________________________________________ FFS volume label support URL: http://people.freebsd.org/~gordon/patches/volume.diff Contact: Gordon Tetlow The goal of the project is to use a small amount of space in the FFS superblock to store a volume label of the user's choice. A GEOM module will then expose the volume labels into a namespace in devfs. The idea is to make it easier to manage filesystems across disk swaps and movement from system to system. At this point, everything pretty much works. I've submitted parts of the patch to respective subsystem maintainers for review. There are some issues with namespace collision that I haven't addressed yet, but the basic functionality is there _________________________________________________________________ FreeBSD C99 & POSIX Conformance Project URL: http://www.FreeBSD.org/projects/c99/ URL: http://people.FreeBSD.org/~schweikh/posix-utilities.html Contact: Mike Barcroft Contact: FreeBSD-Standards Mailing List The POSIX Utility Conformance in FreeBSD list (link above) has been updated to reflect current reality. Not much work remains to complete base utility conformance. On the API front, grantpt(), posix_openpt(), unlockpt(), wordexp(), and wordfree() were implemented. The header was added. There are currently about 40 unassigned tasks on our project's status board ranging from documentation, utilities, to kernel hacking. We would encourage any developers looking for something to work on to check out the status board and see if anything interests them. _________________________________________________________________ FreeBSD GNOME Project URL: http://www.freebsd.org/gnome/ Contact: Joe Marcus Contact: Maxim Sobolev Contact: Adam Weinberger Since the ports tree has been frozen for most of this reporting period, there have not been too many GNOME updates going into the official CVS tree. However, development has not stopped. GNOME 2.2 is nearing completion, and quite a few FreeBSD users have stepped up to test the GNOME 2.1 port sources from the MarcusCom CVS repository. If anyone else is interested, follow the instructions on the aforementioned cvsweb URL, and checkout the "ports" module. The upcoming FreeBSD 5.0-RELEASE will be the first release to have the GNOME 2.0 desktop as the default GNOME desktop choice. During the previously mentioned ports freeze, all the GNOME 2 ports were fixed up so that they build and package on both i386 and Alpha platforms. Alas, the one port that will not make the cut for Alpha is Mozilla. There are still problems with the xpcom code, but work is ongoing to get a working Alpha port. Finally, the FreeBSD Mono (an OpenSource C# runtime) port has also received some new life. Mono has been updated to 0.17 (the latest released version), and Juli Mallett has ported gtk-sharp (GTK+ bindings for C#). _________________________________________________________________ FreeBSD Package Cluster work URL: http://bento.freebsd.org/ Contact: Kris Kennaway The 3 FreeBSD package clusters (i386, alpha, sparc64) have been unified to run from the same master machine, instead of using 3 separate masters. This has freed up some machine resources to use as additional client machine, as well as simplifying administrative overheads. Build logs for all 3 architectures can now be found on the http://bento.freebsd.org webpage. The sparc64 package cluster now has 3 build machines (an u5 and two u10s), and an ia64 cluster is about to be created. Package builds now keep track of how many sequential times a port has failed to build (html summaries are available on the bento website). This allows tracking of ports which have suddenly become broken (e.g. due to a bad upgrade, or due to changes in the FreeBSD source tree), and in the future will be used to send out notifications to port maintainers when their port fails to build 5 times in a row. This feature is currently experimental, and further code changes will be needed to stabilize it. _________________________________________________________________ FreeBSD Release Engineering URL: http://www.freebsd.org/releng/index.html Contact: Scott Long November and December were especially busy for the release egineering team. Scott Long joined the team to help with secretary and communications tasks while Brian Somers bowed out to focus on other projects. FreeBSD 5.0-DP2 was released in November after much delay and anticipation, and marked the final milestone needed for 5.0 to become a reality. Shortly after that, we imposed a code freeze on the HEAD branch of CVS and released 5.0-RC1. Creation of the RELENG_5_0 branch came next, followed by the release of 5.0-RC2 from this branch. At this point, enough critical problems still existed that we scheduled an RC3 release for the new year, and pushed the final 5.0-RELEASE date to mid-January. By the time this is published, FreeBSD 5.0-RELEASE should be a reality. For the time being, there will not be a RELENG_5 (aka 5-STABLE) branch. FreeBSD 4.x releases will continue, with 4.8 being scheduled for March 2003. Release in the 4.x series will be lead by Murray Stokely, and releases in the 5.x series will be lead by Scott Long. Once HEAD has reached acceptable performance and stability goals, the RELENG_5 branch will be created and HEAD will move towards 6.0 development. We hope to reach this with the 5.1 release this spring. _________________________________________________________________ FreeBSD/ia64 Status URL: http://people.freebsd.org/~peter/ia64.diff URL: http://www.freebsd.org/platforms/ia64/ Contact: Peter Wemm Contact: Marcel Moolenaar The ia64 port is up and running on the new Itanium2 based hp machines thanks to a lot of hard work by Marcel Moolenaar. So far we are running on the hp rx2600 as these were the machines graciously donated by Hewlett-Packard and Intel. We had a prototype Intel Tiger4 system for a while, but we had to return the machine and we do not know if it currently runs. Most of the changes necessary to run these are sitting in the perforce tree and are not in the -current or RELENG_5 cvs tree. As a result, the cvs derived builds (-current and the 5.0-RC series and presumably 5.0-RELEASE) are only useable on obsolete Itanium1 systems. Lots of other stability and functionality fixes have been made over the last few months, including initial libc_r support. The OS appears to be stable enough for sustained workloads - it is building packages now, for example. We still do not have gdb support, even for reading core files. _________________________________________________________________ French FreeBSD Documentation Project URL: http://www.freebsd-fr.org URL: http://www.freebsd-fr.org/index-trad.html URL: http://people.freebsd.org/~blackend/doc/fr_FR.ISO8859-1/books/hand book/ URL: http://www.FreeBSD-fr.info Contact: Sebastien Gioria Contact: Marc Fonvieille Contact: Stéphane Legrand Most of the articles are translated too. Marc is still translating the handbook, 60% is currently translated. Stéphane has began the integration of our French localization web site in the US CVS Tree. Sébastien is still maintaining the Release Notes. We launched a new site, www.FreeBSD-fr.info, consisting in a French Dameon News like site. Netasq have donated our new server; we will install it in a new hosting provider in the few next weeks. One of the big job now, project now, is the translation of the FAQ, and the big project will be the manual pages _________________________________________________________________ Hardware Crypto Support Status Contact: Sam Leffler The goal of this project is to import the OpenBSD kernel-level crypto subsystem. This facility provides kernel- and user-level access to hardware crypto devices for the calculation of cryptographic hashes, ciphers, and public key operations. The main clients of this facility are the kernel RNG (/dev/random), network protocols (e.g. IPsec), and OpenSSL (through the /dev/crypto device). This work will be part of the 5.0 release and has been committed to the -stable source tree for inclusion in the 4.8 release. Recent work has focused on improving performance. System statistics are now maintained and an optional profiling facility was added for analyzing performance. Using this facility the overhead for using the crypto API has been significantly reduced. The ubsec (Broadcom) driver was changed to significantly improve performance under load. In addition several memory leaks were fixed in the driver and the public key support was enabled for use. Upcoming work will focus on load-balancing requests across multiple crypto devices and integrating OpenSSL 0.9.7 which will automatically enable application use of crypto hardware. _________________________________________________________________ jpman project URL: http://www.jp.FreeBSD.org/man-jp/ Contact: Kazuo Horikawa We have been updating our Japanese translated manual pages to RELENG_5 based. All existing entries have been updated, but 15 exceptions are not, most of which require massive update. We will also need to add translations which did not exist on RELENG_4. _________________________________________________________________ KGI/FreeBSD Status Report URL: http://www.freebsd.org/~nsouch/ggiport.html URL: http://www.kgi-project.org Contact: Nicholas Souchu KGI (Kernel Graphic Interface) is a kernel infrastructure providing user applications with means to access hardware graphic resources (dma, irqs, mmio). KGI is already available under Linux as a seperate standalone project. The KGI/FreeBSD project aims at integrating KGI in the FreeBSD kernel. KGI/FreeBSD has been recently donated 2 PCI graphic cards (Matrox Millenium II and a coming Mach64) and other have been proposed. Please see the FreeBSD web pages for details. Thanks to donation@ for organizing and promoting donations. Thanks to the donators for their contribution to KGI/FreeBSD. KGI/FreeBSD progressed fine the last months. Most of the VM issues for mapping HW resources in user space have been addressed and a first attempt of coding was made. This prototyping raised some API compatibility problems with the current Linux implementation and was discussed heavily on the kgi devel lists. Ask if you're interested in such issues, I'll be pleased to share them. Most of coding is now done. Let's start debugging! _________________________________________________________________ SMP aware scheduler Contact: Jeff Roberson A new scheduler will be available as an optional component along side the current scheduler in the 5.1 release. It has been designed to work well with KSE and SMP. Some ideas have been borrowed from solaris and linux along with many novel approaches. It has O(1) performance with regard to the number of processes in the system. It also has cpu affinity which should provide a speed boost for many applications. The scheduler has a few loose ends and lots of tuning before it is production quality although it is quite stable. Please see the post to arch and subsequent discussion for more details. _________________________________________________________________ SMP locking for network stack Contact: Jeffrey Hsu Work is ongoing to continue to lock up the network stack. Recently, the focus has been on the IP stack. The plan there involves a series of inter-related pieces to lock up the ifaddr ref count, the inet list, the ifaddr uses, the ARP code, the routing tree, and the routing entries. We are over 3/5 of the way done down this path. In addition to TCP and UDP, the other networking protocols such as raw IP, IPv6, AppleTalk, and XNS need to be locked up. Around 1/4 these remaining protocols have been locked and will be commited after the IP stack is locked. The protocol independent socket layer needs to be locked and operating correctly with the protocol dependent locks. This part is mostly done save for much needed testing and code cleanup. Finally, a pass will be need to be made to lock up the devices drivers and various statistics counters. _________________________________________________________________ TCP congestion control Contact: Jeffrey Hsu This effort fixes some outstanding problems in our TCP stack with regard to congestion control. The first item is to fix our NewReno implementation. Following that, the next urgent correction is to fix a problem involving window updates and dupack counts. When that stabilizes, we will then change the recovery code to make use of SACK information. Eventually, this project will update the BSD stack to add Limited Transmit and other new internet standards and standards-track improvements. _________________________________________________________________ TrustedBSD Project: Access Control Lists URL: http://www.TrustedBSD.org/ Contact: Robert Watson Contact: TrustedBSD Discussion List Largely bug-fixing and userland application tweaks; new interfaces were added to manipulate ACLs on extended attributes; bugs were fixed in ls relating to ACL flagging. Patches to teach cp, mv, gzip, bzip, and other apps about ACL preservation are in testing and review. tunefs flags were added to ease configuration of ACLs, especially on UFS2 file systems. Possible changes to make use of Linux/Solaris umask semantics are under consideration: right now we implement verbatim POSIX.1e/IRIX merging of the umask, ACL mask, and requested creation mode during file, device, fifo, and directory creation. Solaris and the most recent Linux patches ignore the umask in the context of a default ACL; this requires some rearrangement of umask handling in our VFS, although the results would be quite useful. We're exploring how to do this in a low impact way. _________________________________________________________________ TrustedBSD Project: MAC Framework URL: http://www.TrustedBSD.org/ Contact: Robert Watson Contact: TrustedBSD Discussion List Framework changes: Instrument KLD system calls (module and kld load, unload, stat) Instrument NFSd system call. Instrument swapoff(2). Instrument per-architecture privileged parts of sysarch(). Make use of condition variables to allow callers to wait for the framework to "unbusy" when loading/unloading policies, rather than returning EBUSY. Store mount pointer in devfs_mount structure for use by policies. Improve handling of labels in loopback interface "re-align" packet copy case. Provide full paths on devfs object creations to help policies label them properly (not merged). Experimentation with moving MAC labels into m_tags (not merged). NFS server now uses real ucreds, not hacked up ucreds, meaning we can start laying the groundwork for enforcement on NFS operations. (not merged) Policy changes LOMAC: mac_lomac replaces lomac (LOMAC now uses the MAC Framework), SEBSD: Improved support for devfs labeling based on SELinux genfs. Handling of hard link checks. Support export of process transition information for login and others using sysctl. Login now prompts for roles. Allow policy reload. TTY labeling. Locking adaptation from Linux. Many, many policy adaptations and fixes. We can now boot in enforcing mode! mac_bsdextended: fix a bug in which VAPPEND wasn't mapped to VWRITE, so opens with the O_APPEND bug failed improperly. Userland changes setfmac(8) now supports a setfsmac(8) execution mode, which accepts initial labeling specification files. Supports an SELinux compatibility mode so it can accept SELinux label specfiles using the SEBSD module. sendmail(8) now sets user labels as part of the context switch for mail delivery. Documentation changes Man page updates for MAC command line tools, modules, admin hints, etc. Updates to the FreeBSD Developer's Handbook chapter on MAC policies and entry points. MAC section in FreeBSD Handbook. _________________________________________________________________ Wireless Networking Status Contact: Sam Leffler The goal of this project is to improve the wireless networking support in the system. By the time of this report the 802.11 link layer code should be committed. A version of the wi driver that uses this code should be committed shortly. Conversion of other drivers is planned as are drivers for new devices. Support for 802.1x/EAP is the next planned milestone (both as a supplicant and authenticator). --------------040704040107010308060008-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 20:23:24 2003 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 37CE137B401 for ; Thu, 23 Jan 2003 20:23:23 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-106-48.dsl.lsan03.pacbell.net [64.169.106.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DE6243E4A for ; Thu, 23 Jan 2003 20:23:16 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 5446D66B3A; Thu, 23 Jan 2003 20:23:10 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 1AABD160B; Thu, 23 Jan 2003 20:23:10 -0800 (PST) Date: Thu, 23 Jan 2003 20:23:10 -0800 From: Kris Kennaway To: Andrew Alston Cc: hackers@FreeBSD.ORG Subject: Re: SSHD PRNG Not seeded under jail Message-ID: <20030124042309.GA62413@rot13.obsecurity.org> References: <20030122022122.W78046-100000@mail.sznsec.za.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <20030122022122.W78046-100000@mail.sznsec.za.org> 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 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 22, 2003 at 02:22:27AM +0000, Andrew Alston wrote: > Hi All, >=20 > FBSD 5-RC2 was giving me a SSHD PRNG not seeded problem when running under > jails, is this a problem with my configuration or a bug? And if a bug, > has it been fixed in -RELEASE? Do you have a devfs instance mounted in the jail? Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ML+tWry0BWjoQKURAvKRAJ4gPMFxklcA4J5PFTjGnnUW4N878QCfTtX3 d9zrnmJ6CKX1rzbxPvtpeWE= =hPOP -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 20:45:33 2003 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 407FC37B409 for ; Thu, 23 Jan 2003 20:45:31 -0800 (PST) Received: from cache2.telkomsel.co.id (cache2.telkomsel.co.id [202.155.14.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id A871D43EB2 for ; Thu, 23 Jan 2003 20:45:24 -0800 (PST) (envelope-from arief@bna.telkomsel.co.id) Received: from gsi-wall1 (252.83.1.10.in-addr.arpa [10.1.83.252]) by cache2.telkomsel.co.id (8.12.6/8.12.6) with SMTP id h0O4ifFb053682; Fri, 24 Jan 2003 11:45:06 +0700 (JAVT) (envelope-from arief@bna.telkomsel.co.id) Received: from ([10.1.92.57]) by gsi-wall1; Fri, 24 Jan 2003 11:44:33 +0700 (WIT) Message-ID: <3E30C2A5.5040502@bna.telkomsel.co.id> Date: Fri, 24 Jan 2003 11:35:49 +0700 From: arief_mulya Organization: damai itu indah User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Technical Differences of *BSD and Linux 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 Dear all, I Apologize, If this thread has existed before, and so if this is very offtopic and tiredsome for most of you here. I'm a newbie, and just about to get my feet wet into the kernel-code, been using (GNU/)Linux (or whatever the name is, I personally don't really care, I caremost at the technical excellence) for the last two years, I personally think it's a toupper(great); system. But after recently reviewing some BSD based systems, I began to wonder. And these are my questions (I'm trying to avoid flame and being a troll here, so if there's any of my questions is not on technical basis, or are being such a jerk troll please just trash filter my name and email address): 1. In what technical area of the kernel are Linux and *BSD differ? 2. How does it differ? What are the technical reasoning behind the decisions? 3. Is there any group of developer from each project that review each other changes, and tries to make the best code out, or is the issues very system specific (something that work best on Linux might not be so on FreeBSD or NetBSD or OpenBSD)? 4. Any chance of merging the very best part of each kernel? 5. Or is it possible to do so? Anything else that matters, are welcome. Please answer technically, I don't wanna be a troll here, and I hope so do everyone that answers this. I really like to learn, not to read some flame of who's the best. To freebsd and openbsd list, please CC the answer to me directly, as I don't get response from the majordomo of my subscription requests, yet. Best Regards, arief_mulya -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 20:52:14 2003 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 8AC2037B401 for ; Thu, 23 Jan 2003 20:52:12 -0800 (PST) Received: from cvs.openbsd.org (cvs.openbsd.org [199.185.137.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C58A43F18 for ; Thu, 23 Jan 2003 20:52:11 -0800 (PST) (envelope-from deraadt@cvs.openbsd.org) Received: from cvs.openbsd.org (localhost [127.0.0.1]) by cvs.openbsd.org (8.12.6/8.12.1) with ESMTP id h0O4tt1D019060; Thu, 23 Jan 2003 21:55:55 -0700 (MST) Message-Id: <200301240455.h0O4tt1D019060@cvs.openbsd.org> To: arief_mulya Cc: linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux In-reply-to: Your message of "Fri, 24 Jan 2003 11:35:49 +0700." <3E30C2A5.5040502@bna.telkomsel.co.id> Date: Thu, 23 Jan 2003 21:55:55 -0700 From: Theo de Raadt 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 Dear Arief, I Apologize, If this thread has existed before, and so if this is very offtopic and tiredsome for most of you here. I'm a newbie, and just about to get my feet wet into the world, been living in (ASIA/)Indonesia (or whatever the name is, I personally don't really care, I caremost at the nationalist excellence) for the last two years, I personally think it's a toupper(great); country. But after recently reviewing some Malaysian based systems, I began to wonder. And these are my questions (I'm trying to avoid flame and being a troll here, so if there's any of my questions is not on technical basis, or are being such a jerk troll please just trash filter my name and email address): 1. In what technical area of the countries are Indonesia and Malayasian differ? 2. How are they different countries? What are the technical reasoning behind the decisions? 3. Is there any group of ruler from each country that review each other policies, and tries to make the best civil life out, or is the issues very country specific (something that work best in Indonesia might not be so on Malaysia or Phillipines or Singapore)? 4. Any chance of merging the very best part of each country? 5. Or is it possible to do so? Anything else that matters, are welcome. Please answer technically, I don't wanna be a troll here, and I hope so do everyone that answers this. I really like to learn, not to read some flame of who's the best. To freebsd and openbsd list, please CC the answer to me directly, as I don't get response from the majordomo of my subscription requests, yet. Best Regards, arief_mulya -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 21: 1:32 2003 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 DF83537B406 for ; Thu, 23 Jan 2003 21:01:28 -0800 (PST) Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by mx1.FreeBSD.org (Postfix) with SMTP id A71D043F43 for ; Thu, 23 Jan 2003 21:01:26 -0800 (PST) (envelope-from gjb@gbch.net) Received: (qmail 92110 invoked by uid 1001); 24 Jan 2003 15:01:19 +1000 X-Posted-By: GJB-Post 2.29 08-Nov-2002 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Uptime: 30 days, 16:13 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Message-Id: Date: Fri, 24 Jan 2003 15:01:19 +1000 From: Greg Black To: arief_mulya Cc: linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux References: <3E30C2A5.5040502@bna.telkomsel.co.id> In-reply-to: <3E30C2A5.5040502@bna.telkomsel.co.id> of Fri, 24 Jan 2003 11:35:49 +0700 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 arief_mulya wrote: | I Apologize, If this thread has existed before, and so if | this is very offtopic and tiredsome for most of you here. Have you considered Windows? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 22:34:10 2003 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 7424037B401 for ; Thu, 23 Jan 2003 22:34:09 -0800 (PST) Received: from mail.sznsec.za.org (mail.sznsec.za.org [196.22.208.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 278A443ED8 for ; Thu, 23 Jan 2003 22:34:04 -0800 (PST) (envelope-from vortexia@sznsec.za.org) Received: from [196.22.208.212] (helo=[196.22.208.212]) by mail.sznsec.za.org with esmtp (Exim 4.10) id 18bzHI-0002iu-00; Fri, 24 Jan 2003 08:33:32 +0000 Date: Fri, 24 Jan 2003 08:33:32 +0000 (GMT) From: Andrew Alston To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: SSHD PRNG Not seeded under jail In-Reply-To: <20030124042309.GA62413@rot13.obsecurity.org> Message-ID: <20030124083304.J10092-100000@mail.sznsec.za.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 Nope, I will try that though I simply went and did a MAKEDEV jail in /dev in the jail Could that be my problem? On Thu, 23 Jan 2003, Kris Kennaway wrote: > On Wed, Jan 22, 2003 at 02:22:27AM +0000, Andrew Alston wrote: > > Hi All, > > > > FBSD 5-RC2 was giving me a SSHD PRNG not seeded problem when running under > > jails, is this a problem with my configuration or a bug? And if a bug, > > has it been fixed in -RELEASE? > > Do you have a devfs instance mounted in the jail? > > Kris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 22:41:22 2003 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 547BC37B401 for ; Thu, 23 Jan 2003 22:40:56 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E71C943ED8 for ; Thu, 23 Jan 2003 22:40:54 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.51]) by kientzle.com (8.11.3/8.11.3) with ESMTP id h0O6eeR04331; Thu, 23 Jan 2003 22:40:40 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3E30DFE7.50401@acm.org> Date: Thu, 23 Jan 2003 22:40:39 -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: "M. Warner Losh" Cc: freebsd-hackers@FreeBSD.ORG, Nate Lawson Subject: Re: /rescue References: <3E248D85.10201@acm.org> <20030114.231723.49603038.imp@bsdimp.com> Content-Type: multipart/mixed; boundary="------------030407000308050805040706" 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 This is a multi-part message in MIME format. --------------030407000308050805040706 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit M. Warner Losh wrote: > I'm curious why you did things this way, rather then with .PATH in the > makefile? > > *** /dev/null Wed Jan 8 20:22:00 2003 > --- rescue/librescue/exec.c Mon Dec 9 21:56:20 2002 > *************** > *** 0 **** > --- 1 ---- > + #include "../../lib/libc/gen/exec.c" Yep, .PATH does simplify things. Revised diff attached. Thanks for the suggestion. Tim --------------030407000308050805040706 Content-Type: text/plain; name="kientzle_rescue_2.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kientzle_rescue_2.diff" Index: Makefile.inc1 =================================================================== RCS file: /mnt/cvs/src/Makefile.inc1,v retrieving revision 1.314 diff -c -r1.314 Makefile.inc1 *** Makefile.inc1 30 Dec 2002 10:01:25 -0000 1.314 --- Makefile.inc1 7 Jan 2003 05:52:24 -0000 *************** *** 51,56 **** --- 51,60 ---- SUBDIR+= lib .endif + .if exists(${.CURDIR}/rescue) + SUBDIR+= rescue + .endif + .if exists(${.CURDIR}/bin) SUBDIR+= bin .endif Index: bin/csh/Makefile =================================================================== RCS file: /mnt/cvs/src/bin/csh/Makefile,v retrieving revision 1.29 diff -c -r1.29 Makefile *** bin/csh/Makefile 24 Jul 2002 22:26:44 -0000 1.29 --- bin/csh/Makefile 7 Jan 2003 02:07:46 -0000 *************** *** 10,16 **** --- 10,20 ---- .PATH: ${TCSHDIR} PROG= csh + .if defined(RESCUE) + DFLAGS= -D_PATH_TCSHELL='"/rescue/${PROG}"' + .else DFLAGS= -D_PATH_TCSHELL='"/bin/${PROG}"' + .endif CFLAGS+= -I. -I${.CURDIR} -I${TCSHDIR} ${DFLAGS} SRCS= sh.c sh.dir.c sh.dol.c sh.err.c sh.exec.c sh.char.c \ sh.exp.c sh.file.c sh.func.c sh.glob.c sh.hist.c sh.init.c \ Index: bin/mv/mv.c =================================================================== RCS file: /mnt/cvs/src/bin/mv/mv.c,v retrieving revision 1.39 diff -c -r1.39 mv.c *** bin/mv/mv.c 9 Jul 2002 17:45:13 -0000 1.39 --- bin/mv/mv.c 7 Jan 2003 18:13:50 -0000 *************** *** 67,74 **** #include #include - #include "pathnames.h" - int fflg, iflg, nflg, vflg; int copy(char *, char *); --- 67,72 ---- Index: bin/mv/pathnames.h =================================================================== RCS file: /mnt/cvs/src/bin/mv/pathnames.h,v retrieving revision 1.6 diff -c -r1.6 pathnames.h *** bin/mv/pathnames.h 17 May 2002 11:38:48 -0000 1.6 --- bin/mv/pathnames.h 9 Jan 2003 02:34:27 -0000 *************** *** 34,37 **** * $FreeBSD: src/bin/mv/pathnames.h,v 1.6 2002/05/17 11:38:48 jmallett Exp $ */ ! #define _PATH_RM "/bin/rm" --- 34,37 ---- * $FreeBSD: src/bin/mv/pathnames.h,v 1.6 2002/05/17 11:38:48 jmallett Exp $ */ ! /* This file is empty and can be safely deleted */ Index: bin/sh/var.c =================================================================== RCS file: /mnt/cvs/src/bin/sh/var.c,v retrieving revision 1.23 diff -c -r1.23 var.c *** bin/sh/var.c 1 Oct 2002 00:54:14 -0000 1.23 --- bin/sh/var.c 1 Jan 2003 23:35:53 -0000 *************** *** 44,49 **** --- 44,50 ---- #include #include + #include /* * Shell variables. *************** *** 105,111 **** NULL }, { &vmpath, VSTRFIXED|VTEXTFIXED|VUNSET, "MAILPATH=", NULL }, ! { &vpath, VSTRFIXED|VTEXTFIXED, "PATH=/bin:/usr/bin", changepath }, { &vppid, VSTRFIXED|VTEXTFIXED|VUNSET, "PPID=", NULL }, --- 106,112 ---- NULL }, { &vmpath, VSTRFIXED|VTEXTFIXED|VUNSET, "MAILPATH=", NULL }, ! { &vpath, VSTRFIXED|VTEXTFIXED, "PATH=" _PATH_DEFPATH, changepath }, { &vppid, VSTRFIXED|VTEXTFIXED|VUNSET, "PPID=", NULL }, Index: contrib/isc-dhcp/client/clparse.c =================================================================== RCS file: /mnt/cvs/src/contrib/isc-dhcp/client/clparse.c,v retrieving revision 1.9 diff -c -r1.9 clparse.c *** contrib/isc-dhcp/client/clparse.c 16 Jan 2003 07:22:32 -0000 1.9 --- contrib/isc-dhcp/client/clparse.c 24 Jan 2003 06:01:43 -0000 *************** *** 53,59 **** struct client_config top_level_config; ! char client_script_name [] = "/sbin/dhclient-script"; u_int32_t default_requested_options [] = { DHO_SUBNET_MASK, --- 53,59 ---- struct client_config top_level_config; ! char client_script_name [] = _PATH_DHCLIENT_SCRIPT; u_int32_t default_requested_options [] = { DHO_SUBNET_MASK, Index: contrib/isc-dhcp/includes/cf/freebsd.h =================================================================== RCS file: /mnt/cvs/src/contrib/isc-dhcp/includes/cf/freebsd.h,v retrieving revision 1.5 diff -c -r1.5 freebsd.h *** contrib/isc-dhcp/includes/cf/freebsd.h 30 Sep 2002 08:45:34 -0000 1.5 --- contrib/isc-dhcp/includes/cf/freebsd.h 9 Jan 2003 02:35:47 -0000 *************** *** 103,108 **** --- 103,112 ---- #define SOCKLEN_T int #endif + #ifdef RESCUE + #define _PATH_DHCLIENT_SCRIPT "/rescue/dhclient-script" + #endif + #if defined (USE_DEFAULT_NETWORK) # define USE_BPF #endif *************** *** 113,118 **** --- 117,125 ---- #endif /* HAVE_DEV_RANDOM */ const char *cmds[] = { + #ifndef RESCUE + /* rescue environment can't rely on these ... */ + /* Actually, /sbin/dhclient shouldn't use these, either. */ "/bin/ps -axlw 2>&1", "/usr/sbin/arp -an 2>&1", "/usr/bin/netstat -an 2>&1", *************** *** 123,132 **** --- 130,141 ---- "/usr/sbin/iostat 2>&1", "/usr/bin/vmstat 2>&1", "/usr/bin/w 2>&1", + #endif NULL }; const char *dirs[] = { + #ifndef RESCUE "/tmp", "/usr/tmp", ".", *************** *** 136,148 **** --- 145,160 ---- "/var/mail", "/home", "/usr/home", + #endif NULL }; const char *files[] = { + #ifndef RESCUE "/var/log/messages", "/var/log/wtmp", "/var/log/lastlog", + #endif NULL }; #endif /* NEED_PRAND_CONF */ Index: contrib/tar/src/buffer.c =================================================================== RCS file: /mnt/cvs/src/contrib/tar/src/buffer.c,v retrieving revision 1.5 diff -c -r1.5 buffer.c *** contrib/tar/src/buffer.c 9 Oct 2002 07:33:29 -0000 1.5 --- contrib/tar/src/buffer.c 22 Nov 2002 21:37:10 -0000 *************** *** 25,30 **** --- 25,36 ---- #include + #if __FreeBSD__ + # include + #else + # define _PATH_BSHELL "/bin/sh" + #endif + #if MSDOS # include #endif *************** *** 1549,1555 **** pid_t child; const char *shell = getenv ("SHELL"); if (! shell) ! shell = "/bin/sh"; child = xfork (); if (child == 0) { --- 1555,1561 ---- pid_t child; const char *shell = getenv ("SHELL"); if (! shell) ! shell = _PATH_BSHELL; child = xfork (); if (child == 0) { Index: etc/mtree/BSD.root.dist =================================================================== RCS file: /mnt/cvs/src/etc/mtree/BSD.root.dist,v retrieving revision 1.58 diff -c -r1.58 BSD.root.dist *** etc/mtree/BSD.root.dist 10 Jun 2002 04:47:26 -0000 1.58 --- etc/mtree/BSD.root.dist 7 Jan 2003 05:57:14 -0000 *************** *** 67,72 **** --- 67,74 ---- .. proc mode=0555 .. + rescue + .. root .. sbin Index: include/paths.h =================================================================== RCS file: /mnt/cvs/src/include/paths.h,v retrieving revision 1.17 diff -c -r1.17 paths.h *** include/paths.h 14 Jul 2002 13:04:15 -0000 1.17 --- include/paths.h 7 Jan 2003 06:34:34 -0000 *************** *** 40,57 **** --- 40,84 ---- #include /* Default search path. */ + #ifdef RESCUE + #define _PATH_DEFPATH "/rescue:/usr/bin:/bin" + #else #define _PATH_DEFPATH "/usr/bin:/bin" + #endif + /* All standard utilities path. */ + #ifdef RESCUE + #define _PATH_STDPATH \ + "/rescue:/usr/bin:/bin:/usr/sbin:/sbin" + #else #define _PATH_STDPATH \ "/usr/bin:/bin:/usr/sbin:/sbin:" + #endif #define _PATH_AUTHCONF "/etc/auth.conf" + + #ifdef RESCUE + #define _PATH_BSHELL "/rescue/sh" + #else #define _PATH_BSHELL "/bin/sh" + #endif + #define _PATH_CAPABILITY "/etc/capability" #define _PATH_CAPABILITY_DB "/etc/capability.db" #define _PATH_CONSOLE "/dev/console" + + #ifdef RESCUE + #define _PATH_CP "/rescue/cp" + #else #define _PATH_CP "/bin/cp" + #endif + + #ifdef RESCUE + #define _PATH_CSHELL "/rescue/csh" + #else #define _PATH_CSHELL "/bin/csh" + #endif + #define _PATH_DEFTAPE "/dev/sa0" #define _PATH_DEVDB "/var/run/dev.db" #define _PATH_DEVNULL "/dev/null" *************** *** 59,79 **** --- 86,136 ---- #define _PATH_DRUM "/dev/drum" #define _PATH_ETC "/etc" #define _PATH_FTPUSERS "/etc/ftpusers" + + #ifdef RESCUE + #define _PATH_IFCONFIG "/rescue/ifconfig" + #else + #define _PATH_IFCONFIG "/sbin/ifconfig" + #endif + #define _PATH_KMEM "/dev/kmem" #define _PATH_LOGIN "/usr/bin/login" #define _PATH_MAILDIR "/var/mail" #define _PATH_MAN "/usr/share/man" #define _PATH_MEM "/dev/mem" #define _PATH_NOLOGIN "/var/run/nologin" + + #ifdef RESCUE + #define _PATH_RCP "/rescue/rcp" + #else #define _PATH_RCP "/bin/rcp" + #endif + #define _PATH_RLOGIN "/usr/bin/rlogin" + + #ifdef RESCUE + #define _PATH_RM "/rescue/rm" + #else + #define _PATH_RM "/bin/rm" + #endif + #define _PATH_RSH "/usr/bin/rsh" #define _PATH_SENDMAIL "/usr/sbin/sendmail" #define _PATH_SHELLS "/etc/shells" #define _PATH_TTY "/dev/tty" #define _PATH_UNIX "don't use _PATH_UNIX" + + #ifdef RESCUE + #define _PATH_VI "/rescue/vi" + #else #define _PATH_VI "/usr/bin/vi" + #endif + + #ifdef RESCUE + #define _PATH_WALL "/rescue/wall" + #else #define _PATH_WALL "/usr/bin/wall" + #endif /* Provide trailing slash, since mostly used for building pathnames. */ #define _PATH_DEV "/dev/" Index: sbin/dhclient/Makefile =================================================================== RCS file: /mnt/cvs/src/sbin/dhclient/Makefile,v retrieving revision 1.17 diff -c -r1.17 Makefile *** sbin/dhclient/Makefile 28 Feb 2002 16:17:18 -0000 1.17 --- sbin/dhclient/Makefile 9 Jan 2003 02:38:00 -0000 *************** *** 47,54 **** # though, so we must run ``make all'' instead when we are asked to # generate an individual object file. ${OBJS}: all ! .endif .include --- 47,55 ---- # though, so we must run ``make all'' instead when we are asked to # generate an individual object file. + # Note: Must have some commands here to override the default build action ${OBJS}: all ! @true .endif .include Index: sbin/dhclient/client/Makefile =================================================================== RCS file: /mnt/cvs/src/sbin/dhclient/client/Makefile,v retrieving revision 1.2 diff -c -r1.2 Makefile *** sbin/dhclient/client/Makefile 19 Feb 2002 22:23:49 -0000 1.2 --- sbin/dhclient/client/Makefile 7 Jan 2003 05:43:08 -0000 *************** *** 8,14 **** PROG= dhclient SRCS= clparse.c dhclient.c ! CFLAGS+= -DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"' -Dwarn=dhcp_warn DPADD= ${LIBDHCP} ${LIBRES} ${LIBOMAPI} ${LIBDST} LDADD= ${LIBDHCP} ${LIBRES} ${LIBOMAPI} ${LIBDST} --- 8,19 ---- PROG= dhclient SRCS= clparse.c dhclient.c ! .if defined(RESCUE) ! CFLAGS+= -DCLIENT_PATH='"PATH=/rescue:/sbin:/bin:/usr/sbin:/usr/bin"' ! .else ! CFLAGS+= -DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"' ! .endif ! CFLAGS+= -Dwarn=dhcp_warn DPADD= ${LIBDHCP} ${LIBRES} ${LIBOMAPI} ${LIBDST} LDADD= ${LIBDHCP} ${LIBRES} ${LIBOMAPI} ${LIBDST} Index: sbin/fsck/fsck.c =================================================================== RCS file: /mnt/cvs/src/sbin/fsck/fsck.c,v retrieving revision 1.12 diff -c -r1.12 fsck.c *** sbin/fsck/fsck.c 31 Oct 2002 15:32:39 -0000 1.12 --- sbin/fsck/fsck.c 7 Jan 2003 05:43:26 -0000 *************** *** 283,288 **** --- 283,291 ---- { /* List of directories containing fsck_xxx subcommands. */ static const char *edirs[] = { + #ifdef RESCUE + _PATH_RESCUE, /* /rescue/fsck tries /rescue first */ + #endif _PATH_SBIN, _PATH_USRSBIN, NULL Index: sbin/fsck/pathnames.h =================================================================== RCS file: /mnt/cvs/src/sbin/fsck/pathnames.h,v retrieving revision 1.1 diff -c -r1.1 pathnames.h *** sbin/fsck/pathnames.h 9 Oct 2000 10:23:08 -0000 1.1 --- sbin/fsck/pathnames.h 10 Dec 2002 05:43:11 -0000 *************** *** 31,35 **** --- 31,36 ---- * $FreeBSD: src/sbin/fsck/pathnames.h,v 1.1 2000/10/09 10:23:08 adrian Exp $ */ + #define _PATH_RESCUE "/rescue" #define _PATH_SBIN "/sbin" #define _PATH_USRSBIN "/usr/sbin" Index: sbin/mdmfs/pathnames.h =================================================================== RCS file: /mnt/cvs/src/sbin/mdmfs/pathnames.h,v retrieving revision 1.2 diff -c -r1.2 pathnames.h *** sbin/mdmfs/pathnames.h 22 Sep 2002 09:46:28 -0000 1.2 --- sbin/mdmfs/pathnames.h 9 Jan 2003 04:20:16 -0000 *************** *** 2,9 **** --- 2,16 ---- #ifndef MDMFS_PATHNAMES_H #define MDMFS_PATHNAMES_H + /* Shouldn't all of these be moved into /usr/include/paths.h?? */ + #ifndef RESCUE #define PATH_MDCONFIG "/sbin/mdconfig" #define PATH_NEWFS "/sbin/newfs" #define PATH_MOUNT "/sbin/mount" + #else + #define PATH_MDCONFIG "/rescue/mdconfig" + #define PATH_NEWFS "/rescue/newfs" + #define PATH_MOUNT "/rescue/mount" + #endif #endif /* !MDMFS_PATHNAMES_H */ Index: sbin/mount/mount.c =================================================================== RCS file: /mnt/cvs/src/sbin/mount/mount.c,v retrieving revision 1.50 diff -c -r1.50 mount.c *** sbin/mount/mount.c 14 Oct 2002 19:40:00 -0000 1.50 --- sbin/mount/mount.c 7 Jan 2003 05:44:01 -0000 *************** *** 391,396 **** --- 391,399 ---- { /* List of directories containing mount_xxx subcommands. */ static const char *edirs[] = { + #ifdef RESCUE + _PATH_RESCUE, /* /rescue/mount tries /rescue first */ + #endif _PATH_SBIN, _PATH_USRSBIN, NULL Index: sbin/mount/pathnames.h =================================================================== RCS file: /mnt/cvs/src/sbin/mount/pathnames.h,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 pathnames.h *** sbin/mount/pathnames.h 26 May 1994 06:34:21 -0000 1.1.1.1 --- sbin/mount/pathnames.h 10 Dec 2002 05:34:02 -0000 *************** *** 33,38 **** --- 33,39 ---- * @(#)pathnames.h 8.2 (Berkeley) 3/27/94 */ + #define _PATH_RESCUE "/rescue" #define _PATH_SBIN "/sbin" #define _PATH_USRSBIN "/usr/sbin" #define _PATH_MOUNTDPID "/var/run/mountd.pid" Index: sbin/shutdown/pathnames.h =================================================================== RCS file: /mnt/cvs/src/sbin/shutdown/pathnames.h,v retrieving revision 1.2 diff -c -r1.2 pathnames.h *** sbin/shutdown/pathnames.h 17 May 2002 11:47:12 -0000 1.2 --- sbin/shutdown/pathnames.h 9 Jan 2003 04:21:08 -0000 *************** *** 36,41 **** #include ! #define _PATH_FASTBOOT "/fastboot" #define _PATH_HALT "/sbin/halt" #define _PATH_REBOOT "/sbin/reboot" --- 36,49 ---- #include ! /* No longer used? */ ! /* #define _PATH_FASTBOOT "/fastboot" */ ! ! /* Shouldn't these be moved into /usr/include/paths.h?? */ ! #ifndef RESCUE #define _PATH_HALT "/sbin/halt" #define _PATH_REBOOT "/sbin/reboot" + #else + #define _PATH_HALT "/rescue/halt" + #define _PATH_REBOOT "/rescue/reboot" + #endif Index: sbin/startslip/startslip.c =================================================================== RCS file: /mnt/cvs/src/sbin/startslip/startslip.c,v retrieving revision 1.34 diff -c -r1.34 startslip.c *** sbin/startslip/startslip.c 21 Mar 2002 13:20:48 -0000 1.34 --- sbin/startslip/startslip.c 1 Jan 2003 22:04:30 -0000 *************** *** 256,262 **** username, (long)conn_time); sprintf(buf, "LINE=%d %s %s down", diali ? (dialc - 1) % diali : 0, ! downscript ? downscript : "/sbin/ifconfig" , unitname); (void) system(buf); logged_in = 0; } --- 256,262 ---- username, (long)conn_time); sprintf(buf, "LINE=%d %s %s down", diali ? (dialc - 1) % diali : 0, ! downscript ? downscript : _PATH_IFCONFIG , unitname); (void) system(buf); logged_in = 0; } *************** *** 458,464 **** sprintf(buf, "LINE=%d %s %s up", diali ? (dialc - 1) % diali : 0, ! upscript ? upscript : "/sbin/ifconfig" , unitname); (void) system(buf); printd(", ready\n"); --- 458,464 ---- sprintf(buf, "LINE=%d %s %s up", diali ? (dialc - 1) % diali : 0, ! upscript ? upscript : _PATH_IFCONFIG , unitname); (void) system(buf); printd(", ready\n"); Index: sbin/vinum/commands.c =================================================================== RCS file: /mnt/cvs/src/sbin/vinum/commands.c,v retrieving revision 1.44 diff -c -r1.44 commands.c *** sbin/vinum/commands.c 16 Jan 2003 23:49:34 -0000 1.44 --- sbin/vinum/commands.c 24 Jan 2003 06:07:50 -0000 *************** *** 83,89 **** editor = getenv("EDITOR"); if (editor == NULL) ! editor = "/usr/bin/vi"; sprintf(tempfile, "/var/tmp/" VINUMMOD ".create.%d", getpid()); /* create a temp file */ tf = fopen(tempfile, "w"); /* open it */ if (tf == NULL) { --- 83,89 ---- editor = getenv("EDITOR"); if (editor == NULL) ! editor = _PATH_VI; sprintf(tempfile, "/var/tmp/" VINUMMOD ".create.%d", getpid()); /* create a temp file */ tf = fopen(tempfile, "w"); /* open it */ if (tf == NULL) { Index: share/mk/bsd.lib.mk =================================================================== RCS file: /mnt/cvs/src/share/mk/bsd.lib.mk,v retrieving revision 1.138 diff -c -r1.138 bsd.lib.mk *** share/mk/bsd.lib.mk 20 Sep 2002 19:32:51 -0000 1.138 --- share/mk/bsd.lib.mk 7 Jan 2003 02:01:16 -0000 *************** *** 21,26 **** --- 21,28 ---- SONAME?= ${SHLIB_NAME} .endif + CFLAGS+= ${CRUNCH_CFLAGS} + .if defined(DEBUG_FLAGS) CFLAGS+= ${DEBUG_FLAGS} .endif Index: share/mk/bsd.prog.mk =================================================================== RCS file: /mnt/cvs/src/share/mk/bsd.prog.mk,v retrieving revision 1.129 diff -c -r1.129 bsd.prog.mk *** share/mk/bsd.prog.mk 17 Oct 2002 13:48:13 -0000 1.129 --- share/mk/bsd.prog.mk 7 Jan 2003 02:01:20 -0000 *************** *** 6,11 **** --- 6,12 ---- .SUFFIXES: .out .o .c .cc .cpp .cxx .C .m .y .l .ln .s .S .asm CFLAGS+=${COPTS} ${DEBUG_FLAGS} + CFLAGS+= ${CRUNCH_CFLAGS} .if !defined(DEBUG_FLAGS) STRIP?= -s Index: usr.bin/vi/pathnames.h =================================================================== RCS file: /mnt/cvs/src/usr.bin/vi/pathnames.h,v retrieving revision 1.2 diff -c -r1.2 pathnames.h *** usr.bin/vi/pathnames.h 4 Nov 1996 02:28:31 -0000 1.2 --- usr.bin/vi/pathnames.h 22 Nov 2002 21:50:47 -0000 *************** *** 1,5 **** --- 1,8 ---- /* @(#)pathnames.h.in 8.4 (Berkeley) 6/26/96 */ + /* Read standard system paths first */ + #include + #ifndef _PATH_BSHELL #define _PATH_BSHELL "/bin/sh" #endif Index: usr.sbin/crunch/crunchgen/crunchgen.c =================================================================== RCS file: /mnt/cvs/src/usr.sbin/crunch/crunchgen/crunchgen.c,v retrieving revision 1.31 diff -c -r1.31 crunchgen.c *** usr.sbin/crunch/crunchgen/crunchgen.c 30 Mar 2002 16:48:30 -0000 1.31 --- usr.sbin/crunch/crunchgen/crunchgen.c 20 Nov 2002 04:07:07 -0000 *************** *** 691,705 **** fprintf(f, ".endif\n"); fprintf(f, "loop:\n\t@echo 'OBJS= '${%s}\n", objvar); ! fprintf(f, "crunchgen_objs:\n\t@make -f %s $(BUILDOPTS) $(%s_OPTS)", ! tempfname, p->ident); for (s = p->buildopts; s != NULL; s = s->next) fprintf(f, " %s", s->str); fprintf(f, " loop\n"); fclose(f); ! snprintf(line, MAXLINELEN, "make -f %s crunchgen_objs 2>&1", tempfname); if ((f = popen(line, "r")) == NULL) { warn("submake pipe"); goterror = 1; --- 691,708 ---- fprintf(f, ".endif\n"); fprintf(f, "loop:\n\t@echo 'OBJS= '${%s}\n", objvar); ! fprintf(f, "crunchgen_objs:\n\t@cd %s && make -f %s $(BUILDOPTS) $(%s_OPTS)", ! p->srcdir, tempfname, p->ident); for (s = p->buildopts; s != NULL; s = s->next) fprintf(f, " %s", s->str); fprintf(f, " loop\n"); fclose(f); ! snprintf(line, MAXLINELEN, "cd %s && make -f %s crunchgen_objs 2>&1", ! p->srcdir, ! tempfname); ! if ((f = popen(line, "r")) == NULL) { warn("submake pipe"); goterror = 1; *** /dev/null Thu Jan 23 22:33:00 2003 --- rescue/README Thu Jan 2 21:44:29 2003 *************** *** 0 **** --- 1,42 ---- + The /rescue build system here has three goals: + + 1) Produce a reliable standalone set of /rescue tools. + + The contents of /rescue are all statically linked and do not depend on + anything in /bin or /sbin. In particular, they'll continue to + function even if you've hosed your dynamic /bin and /sbin. For + example, note that /rescue/mount runs /rescue/mount_nfs and not + /sbin/mount_nfs. This is more subtle than it looks. + + As an added bonus, /rescue is fairly small (thanks to crunchgen) and + includes a number of tools (such as gzip, bzip2, vi) that are not + normally found in /bin and /sbin. + + 2) Demonstrate robust use of crunchgen. + + These Makefiles recompile each of the crunchgen components and include + support for overriding specific library entries. Such techniques + should be useful elsewhere. For example, boot floppies could use this + to conditionally compile out features to reduce executable size. + + 3) Produce a toolkit suitable for small distributions. + + Install /rescue on a CD or CompactFlash disk, and symlink /bin and + /sbin to /rescue to produce a small and fairly complete FreeBSD + system. + + These tools have one big disadvantage: being statically linked, they + cannot use some advanced library functions that rely on dynamic + linking. In particular, nsswitch, locales, and pam are likely to all + rely on dynamic linking in the near future. + + + To compile: + + # cd /usr/src/rescue + # make obj + # make + # make install + + Note that rebuilds don't always work correctly; if you run into + trouble, try 'make clean' before recompiling. *** /dev/null Thu Jan 23 22:33:00 2003 --- rescue/Makefile Wed Jan 8 18:41:52 2003 *************** *** 0 **** --- 1,3 ---- + SUBDIR=librescue rescue + + .include *** /dev/null Thu Jan 23 22:33:00 2003 --- rescue/librescue/Makefile Thu Jan 23 21:48:13 2003 *************** *** 0 **** --- 1,36 ---- + # + # $FreeBSD: src/rescue/librescue/Makefile,v Exp $ + # + + # Certain library entries have hard-coded references to + # /bin, /sbin, etc, that require those entries to be + # recompiled for use in /rescue. This Makefile + # accomplishes that. Note that this is pure build hackery. + # This library should never be installed, and isn't even linked + # with in the normal way. (See ../rescue/Makefile for details.) + + LIB= rescue + NOPROFILE= yes # Don't generate profile version + INTERNALLIB= yes # Don't install this library + + CFLAGS+= -DRESCUE + # Flags copied from src/lib/libc and src/lib/libutil + CFLAGS+= -I${.CURDIR}/../../lib/libc/include + CFLAGS+= -I${.CURDIR}/../../include + CFLAGS+= -D__DBINTERFACE_PRIVATE + CFLAGS+= -DINET6 + CFLAGS+= -I${.OBJDIR}/../../lib/libc + CFLAGS+= -DPOSIX_MISTAKE + CFLAGS+= -I${.CURDIR}/../../lib/libc/locale + CFLAGS+= -DBROKEN_DES + CFLAGS+= -DPORTMAP + CFLAGS+= -DDES_BUILTIN + CFLAGS+= -DYP + CFLAGS+= -DHESIOD + CFLAGS+= -Wall -Wwrite-strings -Wpointer-arith + + .PATH: ${.CURDIR}/../../lib/libc/gen ${.CURDIR}/../../lib/libutil ${.CURDIR}/../../lib/libc/net ${.CURDIR}/../../lib/libc/stdlib + + SRCS = exec.c getusershell.c login_class.c popen.c rcmdsh.c sysctl.c system.c + + .include *** /dev/null Thu Jan 23 22:33:00 2003 --- rescue/rescue/Makefile Wed Jan 8 20:25:05 2003 *************** *** 0 **** --- 1,259 ---- + # $FreeBSD: src/rescue/Makefile Exp $ + # @(#)Makefile 8.1 (Berkeley) 6/2/93 + + PROG= rescue + BINDIR?= /rescue + + # Uncomment to exclude tcsh + #NO_TCSH=1 + + # Shell scripts need #! line to be edited from /bin/sh to /rescue/sh + SCRIPTS= nextboot_FIXED + SCRIPTSNAME_nextboot_FIXED= nextboot.sh + nextboot_FIXED: ../../sbin/reboot/nextboot.sh + sed '1s/\/bin\//\/rescue\//' ${.ALLSRC} > ${.TARGET} + CLEANFILES+= nextboot_FIXED + + SCRIPTS+= dhclient_FIXED + SCRIPTSNAME_dhclient_FIXED= dhclient-script + dhclient_FIXED: ../../contrib/isc-dhcp/client/scripts/freebsd + sed '1s/\/bin\//\/rescue\//' ${.ALLSRC} > ${.TARGET} + CLEANFILES+= dhclient_FIXED + + ################################################################# + # + # General notes: + # + # A number of Make variables are used to generate the crunchgen config file. + # + # CRUNCH_SRCDIRS: lists directories to search for included programs + # CRUNCH_PROGS: lists programs to be included + # CRUNCH_LIBS: libraries to link with + # CRUNCH_BUILDOPTS: generic build options to be added to every program + # + # Special options can be specified for individual programs + # CRUNCH_SRCDIR_$(P): base source directory for program $(P) + # CRUNCH_BUILDOPTS_$(P): additional build options for $(P) + # CRUNCH_ALIAS_$(P): additional names to be used for $(P) + # + # By default, any name appearing in CRUNCH_PROGS or CRUNCH_ALIAS_${P} + # will be used to generate a hard link to the resulting binary. + # Specific links can be suppressed by setting + # CRUNCH_SUPPRESS_LINK_$(NAME) to 1. + # + + # Define Makefile variable RESCUE + CRUNCH_BUILDOPTS+= -DRESCUE + # Define compile-time RESCUE symbol when compiling components + CRUNCH_BUILDOPTS+= CRUNCH_CFLAGS=-DRESCUE + + # Hackery: 'librescue' exists merely as a tool for appropriately + # recompiling specific library entries. We _know_ they're needed, and + # regular archive searching creates ugly library ordering problems. + # Easiest fix: tell the linker to include them into the executable + # first, so they are guaranteed to override the regular lib entries. + # Note that if 'librescue' hasn't been compiled, we'll just get the + # regular lib entries from libc and friends. + CRUNCH_LIBS+= ${.OBJDIR}/../librescue/*.o + + ################################################################### + # Programs from stock /bin + # + # WARNING: Changing this list may require adjusting + # /usr/include/paths.h as well! You were warned! + # + CRUNCH_SRCDIRS+=$(.CURDIR)/../../bin $(.CURDIR)/../../usr.bin + CRUNCH_PROGS=cat chflags chio chmod cp date dd df domainname echo ed \ + expr getfacl hostname kenv kill ln ls mkdir mv pax ps pwd \ + realpath rm rmdir setfacl sh sleep stty sync test + CRUNCH_LIBS+=-lcrypt -ledit -lkvm -ll -lm -ltermcap -lutil + + # Additional options for specific programs + CRUNCH_ALIAS_test= [ + CRUNCH_ALIAS_sh= -sh + # The -sh alias shouldn't appear in /rescue as a hard link + CRUNCH_SUPPRESS_LINK_-sh=1 + CRUNCH_ALIAS_ln= link + CRUNCH_ALIAS_rm= unlink + CRUNCH_ALIAS_ed= red + + .if !defined(NO_RCMNDS) + CRUNCH_PROGS+= rcp + .endif + + .if !defined(NO_TCSH) + CRUNCH_PROGS+= csh + CRUNCH_ALIAS_csh= -csh tcsh -tcsh + CRUNCH_SUPPRESS_LINK_-csh=1 + CRUNCH_SUPPRESS_LINK_-tcsh=1 + .endif + + #Is rmail of any use at all here? I think not. + #CRUNCH_PROGS+= rmail + + ################################################################### + # Programs from standard /sbin + # + # WARNING: Changing this list may require adjusting + # /usr/include/paths.h as well! You were warned! + # + # Note that mdmfs and shutdown have their own private 'pathnames.h' + # headers in addition to the standard 'paths.h' header. + # + CRUNCH_SRCDIRS+=$(.CURDIR)/../../sbin + CRUNCH_PROGS+=atm adjkerntz atacontrol badsect camcontrol ccdconfig \ + clri comcontrol conscontrol devfs disklabel dmesg dump \ + dumpfs dumpon fdisk fore_dnld fsck fsck_ffs fsck_msdosfs fsdb \ + fsirand gbde growfs ifconfig ilmid init ip6fw ipf ipfs ipfstat \ + ipfw ipmon ipnat kldconfig kldload kldstat kldunload ldconfig \ + md5 mdconfig mdmfs mknod mount mount_cd9660 mount_ext2fs \ + mount_msdosfs mount_nfs mount_ntfs mount_nullfs mount_portalfs \ + mount_std mount_udf mount_umapfs mount_unionfs natd newfs \ + newfs_msdos nfsiod nos-tun ping ping6 quotacheck raidctl reboot \ + restore rcorder route routed rtquery rtsol savecore shutdown \ + slattach spppcontrol startslip swapon sysctl tunefs umount vinum + + # crunchgen does not like C++ programs; this should be fixed someday + # CRUNCH_PROGS+= devd + + CRUNCH_LIBS+=-lalias -latm -lcam -lcurses -ldevstat -lipsec -lipx -lmd \ + -lncp -lreadline -lsbuf -lsmb -lufs -lz + + .if ${MACHINE_ARCH} == "i386" + CRUNCH_PROGS+= cxconfig mount_nwfs mount_smbfs + .endif + + .if ${MACHINE} == "pc98" + CRUNCH_PROGS+= fdisk_pc98 + .endif + + .if ${MACHINE_ARCH} == "ia64" + CRUNCH_PROGS+= mca gpt + .endif + + .if ${MACHINE_ARCH} == "sparc" + .endif + + .if ${MACHINE_ARCH} == "alpha" + .endif + + CRUNCH_SRCDIR_atm=$(.CURDIR)/../../sbin/atm/atm + CRUNCH_SRCDIR_fore_dnld=$(.CURDIR)/../../sbin/atm/fore_dnld + CRUNCH_SRCDIR_ilmid=$(.CURDIR)/../../sbin/atm/ilmid + CRUNCH_SRCDIR_rtquery=$(.CURDIR)/../../sbin/routed/rtquery + CRUNCH_ALIAS_reboot= fastboot halt fasthalt + CRUNCH_ALIAS_restore=rrestore + CRUNCH_ALIAS_dump= rdump + CRUNCH_ALIAS_fsck_ffs=fsck_4.2bsd fsck_ufs + CRUNCH_ALIAS_mount_std= mount_devfs mount_fdescfs mount_linprocfs mount_procfs + + # dhclient has historically been troublesome... + CRUNCH_PROGS+=dhclient + CRUNCH_BUILDOPTS_dhclient=-DRELEASE_CRUNCH -Dlint + + ################################################################## + # Programs from stock /usr/bin + # + CRUNCH_SRCDIRS+=$(.CURDIR)/../../usr.bin + CRUNCH_SRCDIRS+=$(.CURDIR)/../../gnu/usr.bin + + CRUNCH_PROGS+=wall + + CRUNCH_PROGS+=gzip + CRUNCH_ALIAS_gzip=gunzip gzcat zcat + + CRUNCH_PROGS+=bzip2 + CRUNCH_ALIAS_bzip2=bunzip2 bzcat + CRUNCH_LIBS+=-lbz2 + + CRUNCH_PROGS+=tar + CRUNCH_PROGS+=vi + CRUNCH_ALIAS_vi=ex + + ################################################################## + # The following is pretty nearly a generic crunchgen-handling makefile + # + + CONF= $(PROG).conf + OUTMK= $(PROG).mk + OUTC= $(PROG).c + OUTPUTS= $(OUTMK) $(OUTC) $(PROG).cache + CRUNCHOBJS= ${.OBJDIR} + .if defined(MAKEOBJDIRPREFIX) + CANONICALOBJDIR:=${MAKEOBJDIRPREFIX}${.CURDIR} + .else + CANONICALOBJDIR:=/usr/obj${.CURDIR} + .endif + + NOMAN= true + CLEANFILES+= $(CONF) *.o *.lo *.c *.mk *.cache *.a *.h + + # Program names and their aliases contribute hardlinks to 'rescue' executable, + # except for those that get suppressed. + .for P in $(CRUNCH_PROGS) + .ifndef CRUNCH_SUPPRESS_LINK_${P} + LINKS += $(BINDIR)/$(PROG) $(BINDIR)/$(P) + .endif + .for A in $(CRUNCH_ALIAS_$(P)) + .ifndef CRUNCH_SUPPRESS_LINK_${A} + LINKS += $(BINDIR)/$(PROG) $(BINDIR)/$(A) + .endif + .endfor + .endfor + + all: $(PROG) + exe: $(PROG) + + $(CONF): Makefile + echo \# Auto-generated, do not edit >$(.TARGET) + .for D in $(CRUNCH_SRCDIRS) + echo srcdirs $(D) >>$(.TARGET) + .endfor + .ifdef CRUNCH_BUILDOPTS + echo buildopts $(CRUNCH_BUILDOPTS) >>$(.TARGET) + .endif + .ifdef CRUNCH_BUILDOPTS + echo libs $(CRUNCH_LIBS) >>$(.TARGET) + .endif + .for P in $(CRUNCH_PROGS) + echo progs $(P) >>$(.TARGET) + .ifdef CRUNCH_SRCDIR_${P} + echo special $(P) srcdir $(CRUNCH_SRCDIR_${P}) >>$(.TARGET) + .endif + .ifdef CRUNCH_BUILDOPTS_${P} + echo special $(P) buildopts $(CRUNCH_BUILDOPTS_${P}) >>$(.TARGET) + .endif + .for A in $(CRUNCH_ALIAS_$(P)) + echo ln $(P) $(A) >>$(.TARGET) + .endfor + .endfor + + + $(OUTPUTS): $(CONF) + MAKEOBJDIRPREFIX=${CRUNCHOBJS} crunchgen -q -m $(OUTMK) -c $(OUTC) $(CONF) + + $(PROG): $(OUTPUTS) + MAKEOBJDIRPREFIX=${CRUNCHOBJS} make -f $(OUTMK) + + objs: + MAKEOBJDIRPREFIX=${CRUNCHOBJS} make -f $(OUTMK) objs + + # Use a separate build tree to hold files compiled for this crunchgen binary + # Yes, this does seem to partly duplicate bsd.subdir.mk, but I can't + # get that to cooperate with bsd.prog.mk. Besides, many of the standard + # targets should NOT be propagated into the components. + cleandepend cleandir obj objlink: + .for D in $(CRUNCH_SRCDIRS) + cd ${D} && MAKEOBJDIRPREFIX=${CANONICALOBJDIR} make ${.TARGET} + .endfor + + clean: + if [ -e ${.OBJDIR}/$(OUTMK) ]; then \ + MAKEOBJDIRPREFIX=${CRUNCHOBJS} make -f $(OUTMK) clean; \ + fi + .for D in $(CRUNCH_SRCDIRS) $(EXTRA_SRCDIRS) + cd ${D} && MAKEOBJDIRPREFIX=${CRUNCHOBJS} make clean + .endfor + rm -f ${CLEANFILES} + + .include --------------030407000308050805040706-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 23 23:29:55 2003 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 5DBAC37B401 for ; Thu, 23 Jan 2003 23:29:54 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-64-169-106-48.dsl.lsan03.pacbell.net [64.169.106.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 762B943F43 for ; Thu, 23 Jan 2003 23:29:53 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id BCC9466B3A; Thu, 23 Jan 2003 23:29:52 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 91D69165A; Thu, 23 Jan 2003 23:29:52 -0800 (PST) Date: Thu, 23 Jan 2003 23:29:52 -0800 From: Kris Kennaway To: Andrew Alston Cc: Kris Kennaway , hackers@FreeBSD.ORG Subject: Re: SSHD PRNG Not seeded under jail Message-ID: <20030124072952.GA64138@rot13.obsecurity.org> References: <20030124042309.GA62413@rot13.obsecurity.org> <20030124083304.J10092-100000@mail.sznsec.za.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <20030124083304.J10092-100000@mail.sznsec.za.org> 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 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 24, 2003 at 08:33:32AM +0000, Andrew Alston wrote: > Nope, I will try that though >=20 > I simply went and did a MAKEDEV jail in /dev in the jail >=20 > Could that be my problem? Yes. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+MOtvWry0BWjoQKURAoqLAJ9eoBIwS5PSR5aau2mDsLuSzIMc2gCeIFes z3yvAcehHosMQqGwUB1peok= =QR6w -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 2:58:54 2003 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 32A6037B401 for ; Fri, 24 Jan 2003 02:58:53 -0800 (PST) Received: from satanii.enemy.org (satanii.enemy.org [62.116.11.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F31543E4A for ; Fri, 24 Jan 2003 02:58:52 -0800 (PST) (envelope-from shammer@satanii.enemy.org) Received: from satanii.enemy.org (shammer@localhost [IPv6:::1]) by satanii.enemy.org (8.12.6/8.12.6) with ESMTP id h0OB0Tb0056398; Fri, 24 Jan 2003 12:00:30 +0100 (CET) (envelope-from shammer@satanii.enemy.org) Received: (from shammer@localhost) by satanii.enemy.org (8.12.6/8.12.6/Submit) id h0OB0Mfs056363; Fri, 24 Jan 2003 12:00:22 +0100 (CET) Date: Fri, 24 Jan 2003 12:00:22 +0100 From: Josef El-Rayes To: arief@bna.telkomsel.co.id Cc: linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux Message-ID: <20030124110022.GA56181@satanii.enemy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Dear Arief, as you can see your questions are not very welcome on the mailinglists, therefore i advice you to have a look at this book if you are interested in BSD's technical background Title: The Design and Implementation of the 4.4BSD Operating System Authors: McKusick, Bostic, Karels and Quarterman Publisher: Addison-Wesley 4.4BSD is what NetBSD, OpenBSD and FreeBSD are basing on. For Linux i cant help you. Take this approach to read about technicals issues yourself, by finding the differences yourself you learn much more than being told. greets, josef To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 3:35:40 2003 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 CE3BA37B401 for ; Fri, 24 Jan 2003 03:35:38 -0800 (PST) Received: from ns1.ovis.net (ns1.ovis.net [207.0.147.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5488143F5F for ; Fri, 24 Jan 2003 03:35:38 -0800 (PST) (envelope-from chromexa@ovis.net) Received: from ovis.net (s39.pm5.ovis.net [207.0.147.105]) by ns1.ovis.net (Postfix) with ESMTP id E3BAB3B06; Fri, 24 Jan 2003 06:35:29 -0500 (EST) Message-ID: <3E3125D2.B17764AA@ovis.net> Date: Fri, 24 Jan 2003 11:38:58 +0000 From: Steve Kudlak Reply-To: chromexa@ovis.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD ezn/58/n (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef El-Rayes , "'hackers@freebsd.org'" Subject: Re: Technical Differences of *BSD and Linux References: <20030124110022.GA56181@satanii.enemy.org> 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 Josef El-Rayes wrote: > Dear Arief, > > as you can see your questions are not very welcome on the mailinglists, therefore i advice you to have a look at this book if you are interested in BSD's technical background > > Title: The Design and Implementation of the 4.4BSD Operating System > > Authors: McKusick, Bostic, Karels and Quarterman > Publisher: Addison-Wesley > > 4.4BSD is what NetBSD, OpenBSD and FreeBSD are basing on. > > For Linux i cant help you. > > Take this approach to read about technicals issues yourself, by finding the differences yourself you learn much more than being told. > > greets, josef > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Overall this is not the place to go into all that Linux vs. BSD stuff. Usually hacker lists are for technical details. Although sometimes general issues like security will get floated. I don't know if I (1) Feel Competent Enough (2)Have the Time to throw together a *NIX reading list. Generally one can glean a lot of information by just putting oneself on several mailing lists. Some devoted to BSD, some to Linux and just lurking around. One can get a lot of useful information that way. If one really wanted to have fun, and I have thought of this. A "triple boot system" would be the real way to find out the differences and compare the *BSD, Linux and the Windows Universes. Oh well that is my 5 cents worth (inflation you know) and now I will go back to lurking. Have Fun, Sends Steve P.S. Does anyone ever do much on advocacy mailing lists? So far hackers is the best list for technical stuff about *BSD I know of. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 4:30:16 2003 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 DD84337B401 for ; Fri, 24 Jan 2003 04:30:15 -0800 (PST) Received: from dove.penix.org (dove.penix.org [216.144.7.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF2843F13 for ; Fri, 24 Jan 2003 04:30:15 -0800 (PST) (envelope-from dp@dove.penix.org) Received: from dove.penix.org (dp@localhost.nls.net [127.0.0.1]) by dove.penix.org (8.12.6/8.12.2) with ESMTP id h0OCU9lk056753; Fri, 24 Jan 2003 07:30:09 -0500 (EST) (envelope-from dp@dove.penix.org) Received: from localhost (dp@localhost) by dove.penix.org (8.12.6/8.12.2/Submit) with ESMTP id h0OCU84x056750; Fri, 24 Jan 2003 07:30:08 -0500 (EST) (envelope-from dp@dove.penix.org) Date: Fri, 24 Jan 2003 07:30:08 -0500 (EST) From: Paul Halliday To: Steve Kudlak Cc: Josef El-Rayes , "'hackers@freebsd.org'" Subject: Re: Technical Differences of *BSD and Linux In-Reply-To: <3E3125D2.B17764AA@ovis.net> Message-ID: <20030124072701.L56746@dove.penix.org> References: <20030124110022.GA56181@satanii.enemy.org> <3E3125D2.B17764AA@ovis.net> 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, 24 Jan 2003, Steve Kudlak wrote: > > If one really wanted to have fun, and I have > thought of this. A "triple boot system" would > be the real way to find out the differences and > compare the *BSD, Linux and the Windows > Universes. What a unique idea. http://www.maximumpc.com/features/feature_2002-09-24.html Paul H. http://dp.penix.org ------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 5:15:59 2003 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 55CDC37B401 for ; Fri, 24 Jan 2003 05:15:58 -0800 (PST) Received: from 5-116.ctame701-1.telepar.net.br (5-116.ctame701-1.telepar.net.br [200.193.163.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68B0C43F5F for ; Fri, 24 Jan 2003 05:15:56 -0800 (PST) (envelope-from riel@conectiva.com.br) Received: from localhost ([IPv6:::ffff:127.0.0.1]:12756 "EHLO localhost") by imladris.surriel.com with ESMTP id ; Fri, 24 Jan 2003 11:15:30 -0200 Date: Fri, 24 Jan 2003 11:15:28 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Josef El-Rayes Cc: arief@bna.telkomsel.co.id, "" , "" , "" , "" , "" Subject: Re: Technical Differences of *BSD and Linux In-Reply-To: <20030124110022.GA56181@satanii.enemy.org> Message-ID: References: <20030124110022.GA56181@satanii.enemy.org> X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.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 [follow-ups to kernelnewbies@kernelnewbies.org, please] On Fri, 24 Jan 2003, Josef El-Rayes wrote: > as you can see your questions are not very welcome on the mailinglists, > therefore i advice you to have a look at this book if you are interested > in BSD's technical background There is one mailing list where this kind of discussion probably would be welcome, the kernelnewbies mailing list. Personally I'd really like more things related to BSD, Hurd and other freely available systems on the kernelnewbies mailing list, irc channel, etc. I might have founded #kernelnewbies to help people with Linux questions, but it was never my intention to limit it to Linux kernel stuff only. > Title: The Design and Implementation of the 4.4BSD Operating System > > Authors: McKusick, Bostic, Karels and Quarterman > Publisher: Addison-Wesley > > 4.4BSD is what NetBSD, OpenBSD and FreeBSD are basing on. > > For Linux i cant help you. I can recommend Understanding the Linux Kernel, 2nd edition. Other people have recommended various other kernel related books, you can find a small list on: http://kernelnewbies.org/books.php3 cheers, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://guru.conectiva.com/ Current spamtrap: october@surriel.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 5:36: 2 2003 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 AC25537B401 for ; Fri, 24 Jan 2003 05:36:00 -0800 (PST) Received: from ns1.ovis.net (ns1.ovis.net [207.0.147.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D22E43F13 for ; Fri, 24 Jan 2003 05:36:00 -0800 (PST) (envelope-from chromexa@ovis.net) Received: from ovis.net (s39.pm5.ovis.net [207.0.147.105]) by ns1.ovis.net (Postfix) with ESMTP id 14EE43B28; Fri, 24 Jan 2003 08:35:51 -0500 (EST) Message-ID: <3E3141F9.43194EFA@ovis.net> Date: Fri, 24 Jan 2003 13:39:05 +0000 From: Steve Kudlak Reply-To: chromexa@ovis.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD ezn/58/n (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Paul Halliday Cc: Josef El-Rayes , "'hackers@freebsd.org'" Subject: Re: Technical Differences of *BSD and Linux References: <20030124110022.GA56181@satanii.enemy.org> <3E3125D2.B17764AA@ovis.net> <20030124072701.L56746@dove.penix.org> 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 Paul Halliday wrote: > On Fri, 24 Jan 2003, Steve Kudlak wrote: > > > > If one really wanted to have fun, and I have > > thought of this. A "triple boot system" would > > be the real way to find out the differences and > > compare the *BSD, Linux and the Windows > > Universes. > > What a unique idea. > > http://www.maximumpc.com/features/feature_2002-09-24.html > > Paul H. > http://dp.penix.org > ------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message I have seen these things before. The only problem is that they are kind of curiousities. It would be nice to have say a bunch of art tools, publishing tools and communications tools etc. running on each of these operating systems too. Anyway I don't think these sorts of questions belong on hackers. I would love to know where they could be discussed as right now having another alternative to the PC vs. MAC discussion in the publication world would be very nice. Like speaking of technical things has anyone brought up a raytrace/rendering or other fancy computer graphics system under FreeBSD? Have Fun, Sends Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 6:38:55 2003 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 EB07737B401 for ; Fri, 24 Jan 2003 06:38:54 -0800 (PST) Received: from rootshell.be (phenix.rootshell.be [195.74.192.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC2B43F18 for ; Fri, 24 Jan 2003 06:38:53 -0800 (PST) (envelope-from nmlabs@phenix.rootshell.be) Received: from localhost (nmlabs@localhost) by rootshell.be (8.11.5/8.11.5) with ESMTP id h0OEcoV07127 for ; Fri, 24 Jan 2003 15:38:50 +0100 Date: Fri, 24 Jan 2003 15:38:50 +0100 (CET) From: Nicolas Mallet To: freebsd-hackers@FreeBSD.org Subject: Re: kld && inetsw.pr_protocol overriding + old reuse 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 A proof of concept : http://www.rootshell.be/~nmlabs/hacktcp.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 10: 5: 9 2003 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 7184A37B401 for ; Fri, 24 Jan 2003 10:05:07 -0800 (PST) Received: from mail.netbsd.org (mail.netbsd.org [155.53.1.253]) by mx1.FreeBSD.org (Postfix) with SMTP id 08E5343F79 for ; Fri, 24 Jan 2003 10:05:07 -0800 (PST) (envelope-from wrstuden@netbsd.org) Received: (qmail 6972 invoked by uid 1130); 24 Jan 2003 18:04:27 -0000 Date: Fri, 24 Jan 2003 10:03:53 -0800 (PST) From: Bill Studenmund X-X-Sender: To: arief_mulya Cc: , , , Subject: Re: Technical Differences of *BSD and Linux In-Reply-To: <3E30C2A5.5040502@bna.telkomsel.co.id> 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, 24 Jan 2003, arief_mulya wrote: > Dear all, > > > I Apologize, If this thread has existed before, and so if > this is very offtopic and tiredsome for most of you here. > > I'm a newbie, and just about to get my feet wet into the > kernel-code, been using (GNU/)Linux (or whatever the name > is, I personally don't really care, I caremost at the > technical excellence) for the last two years, I personally > think it's a toupper(great); system. > > But after recently reviewing some BSD based systems, I began > to wonder. And these are my questions (I'm trying to avoid > flame and being a troll here, so if there's any of my > questions is not on technical basis, or are being such a > jerk troll please just trash filter my name and email address): Evidently others opted to not pursue that option. > 1. In what technical area of the kernel are Linux and *BSD > differ? > 2. How does it differ? What are the technical reasoning > behind the decisions? They differ in most technical areas. Mainly as the *BSD kernels were derived from 4.4-Lite, and Linux was derived, I believe, from Minux. The difference grew since they were developed by differing groups of people. Within the BSDs, the main focus of each one is different. To put it in terms of sound bites, FreeBSD wants to make kick-ass servers, NetBSD wants to support lots & lots of hardware, and OpenBSD is concerned all about security. That doesn't mean that the others ignore those areas; all three are interested in security, and being servers, and they all run on more than just one platform. There also is a lot of polination between BSDs. Things will show up in one and then get ported to another. > 3. Is there any group of developer from each project that > review each other changes, and tries to make the best code > out, or is the issues very system specific (something that > work best on Linux might not be so on FreeBSD or NetBSD or > OpenBSD)? Sometimes changes will apply to all, and a comparable fix will happen to each. This usually shows up in dealing with security advisories, but happens in other places too. For the most part though, what the BSDs need is different from what Linux needs, or at least the expertise doesn't overlap. > 4. Any chance of merging the very best part of each kernel? > 5. Or is it possible to do so? No, I don't forsee merging. der Mouse pointed out the GPL issue, which is one where I think the BSD and Linux folks will just agree to disagree. Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 10:49:16 2003 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 61C7D37B401 for ; Fri, 24 Jan 2003 10:49:15 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10E6743F3F for ; Fri, 24 Jan 2003 10:49:15 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id E7F1C2A7EA; Fri, 24 Jan 2003 10:49:14 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bill Studenmund Cc: arief_mulya , tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux In-Reply-To: Date: Fri, 24 Jan 2003 10:49:14 -0800 From: Peter Wemm Message-Id: <20030124184914.E7F1C2A7EA@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 [dropped linux-kernel] Bill Studenmund wrote: > On Fri, 24 Jan 2003, arief_mulya wrote: > > 4. Any chance of merging the very best part of each kernel? > > 5. Or is it possible to do so? > > No, I don't forsee merging. der Mouse pointed out the GPL issue, which is > one where I think the BSD and Linux folks will just agree to disagree. Besides some big issues of ideology, there is also the issue of some strong personalities in the various camps that simply do not get along well with the other strong personalities in other camps. Some of the lines of division just happen to keep these people apart and further away from each others throats. Trying to do mergers in the past (yes, it has been tried) has caused collisions with consequences that lingered for quite some time. Past experience has shown that failed merger attempts have been damaging because the resulting bad feelings interfere with cooperation and cross-pollination for some time. To the original poster: This kind of posting is very unhelpful. If you want to learn about the different systems, subscribe to some of the mailing lists for each group, and watch for a while so that you can build your own understanding of what is going on in the respective groups. 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 Fri Jan 24 13:48: 4 2003 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 481F037B401 for ; Fri, 24 Jan 2003 13:47:59 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F43643F13 for ; Fri, 24 Jan 2003 13:47:58 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0212.cvx40-bradley.dialup.earthlink.net ([216.244.42.212] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18cBfu-0000XD-00; Fri, 24 Jan 2003 13:47:47 -0800 Message-ID: <3E31B42C.FCD85165@mindspring.com> Date: Fri, 24 Jan 2003 13:46:20 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: chromexa@ovis.net Cc: Paul Halliday , Josef El-Rayes , "'hackers@freebsd.org'" Subject: Re: Technical Differences of *BSD and Linux References: <20030124110022.GA56181@satanii.enemy.org> <3E3125D2.B17764AA@ovis.net> <20030124072701.L56746@dove.penix.org> <3E3141F9.43194EFA@ovis.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a45567c1b11ddda4cfa75ed12bc8cd27d2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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 Steve Kudlak wrote: > Like speaking of technical things has anyone brought > up a raytrace/rendering or other fancy computer graphics > system under FreeBSD? Yes. Manex Visual Effects did. Perhaps you've heard of the movie "The Matrix", whose computer graphics were rendered on FreeBSD systems? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 14:15: 9 2003 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 BF8E537B401 for ; Fri, 24 Jan 2003 14:15:07 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2025343F5B for ; Fri, 24 Jan 2003 14:15:07 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org (UGLY.x.kientzle.comg [66.166.149.51] (may be forged)) by kientzle.com (8.11.3/8.11.3) with ESMTP id h0OMF6R07099 for ; Fri, 24 Jan 2003 14:15:06 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3E31BAEA.7000500@acm.org> Date: Fri, 24 Jan 2003 14:15:06 -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: freebsd-hackers@FreeBSD.ORG Subject: Ugly mount argv[0] trickery Content-Type: multipart/mixed; boundary="------------020100050001020302010807" 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 This is a multi-part message in MIME format. --------------020100050001020302010807 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The attached patch eliminates a bit of unnecessary cleverness from 'mount.' If someone would do me the favor of committing this, I would greatly appreciate it. Namely, some mount_XXX helpers support multiple filesystem types and therefore must consider argv[0]. For no apparent reason, mount puts the filesystem type (e.g., 'nfs') into argv[0] rather than the executable name (e.g., 'mount_nfs'). This is unnecessary, counter-intuitive, and also makes it rather ugly to put 'mount' into a crunchgen binary. ;-) Tim Kientzle --------------020100050001020302010807 Content-Type: text/plain; name="kientzle_mount.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kientzle_mount.diff" Index: mount.c =================================================================== RCS file: /mnt/cvs/src/sbin/mount/mount.c,v retrieving revision 1.50 diff -c -r1.50 mount.c *** mount.c 14 Oct 2002 19:40:00 -0000 1.50 --- mount.c 24 Jan 2003 21:47:00 -0000 *************** *** 400,405 **** --- 400,406 ---- pid_t pid; int argc, i, status; char *optbuf, execname[MAXPATHLEN + 1], mntpath[MAXPATHLEN]; + char progname[MAXPATHLEN+1]; #if __GNUC__ (void)&optbuf; *************** *** 441,448 **** if (strcmp(vfstype, "msdos") == 0) vfstype = "msdosfs"; argc = 0; ! argv[argc++] = vfstype; mangle(optbuf, &argc, argv); argv[argc++] = spec; argv[argc++] = name; --- 442,451 ---- if (strcmp(vfstype, "msdos") == 0) vfstype = "msdosfs"; + snprintf(progname,sizeof(progname),"mount_%s",vfstype); + argc = 0; ! argv[argc++] = progname; mangle(optbuf, &argc, argv); argv[argc++] = spec; argv[argc++] = name; --------------020100050001020302010807-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 24 14:56:47 2003 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 70EF237B401 for ; Fri, 24 Jan 2003 14:56:46 -0800 (PST) Received: from lindt.urgle.com (lindt.urgle.com [80.177.40.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AE7D43EB2 for ; Fri, 24 Jan 2003 14:56:45 -0800 (PST) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 4.10) id 18cCkK-0006IA-00; Fri, 24 Jan 2003 22:56:24 +0000 Date: Fri, 24 Jan 2003 22:56:24 +0000 From: Mike Bristow To: Bill Studenmund Cc: arief_mulya , linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux Message-ID: <20030124225624.GB23410@lindt.urgle.com> Reply-To: mike@urgle.com References: <3E30C2A5.5040502@bna.telkomsel.co.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i 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 [ Reply-To set to me: This is probably off topic for all of the lists: all of the ones I read, anyway. ] On Fri, Jan 24, 2003 at 10:03:53AM -0800, Bill Studenmund wrote: > > 2. How does it differ? What are the technical reasoning > > behind the decisions? > > They differ in most technical areas. Mainly as the *BSD kernels were > derived from 4.4-Lite, and Linux was derived, I believe, from Minux. Point of order: Linux was a cleanroom implementation, using IIRC Minux as the host OS until such time as it became self-hosting. -- You can't do maths without e -- David Walters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 25 11: 0:23 2003 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 2D89937B401 for ; Sat, 25 Jan 2003 11:00:22 -0800 (PST) Received: from web13402.mail.yahoo.com (web13402.mail.yahoo.com [216.136.175.60]) by mx1.FreeBSD.org (Postfix) with SMTP id CA7EA43F1E for ; Sat, 25 Jan 2003 11:00:21 -0800 (PST) (envelope-from giffunip@yahoo.com) Message-ID: <20030125190021.80728.qmail@web13402.mail.yahoo.com> Received: from [200.24.79.46] by web13402.mail.yahoo.com via HTTP; Sat, 25 Jan 2003 20:00:21 CET Date: Sat, 25 Jan 2003 20:00:21 +0100 (CET) From: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" Subject: idea from NetBSD: signal trampoline on libc ? To: freebsd-hackers@FreeBSD.org 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 Hi; I was reading an interview about IRIX binary compatibility on NetBSD, and it looks like they learned a few tricks. This article gets into their native implementation of signals: http://www.onlamp.com/pub/a/bsd/2002/10/10/irix.html At the end of the article Emmanuel Dreyfus mentions: "One other interesting thing to note is that since that code was written, Jason Thorpe implemented signal trampolines provided by libc for NetBSD native processes, thus adopting the same scheme IRIX used. The libc provided signal trampoline was adopted in NetBSD because it removes the need to execute code on the stack. Memory pages mapped on the stack can therefore be made non executable (the Memory Management Unit of all modern CPU are able to enforce such rules), and we are able to fix a whole class of security problems. With a non executable stack, it is not possible anymore to exploit a buffer overflow on a local variable by executing some user-supplied code stored on the stack." A drastic change that maybe we should consider? cheers, Pedro. ______________________________________________________________________ Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino 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 Sat Jan 25 12:45:54 2003 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 60C3637B401 for ; Sat, 25 Jan 2003 12:45:53 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE43A43EB2 for ; Sat, 25 Jan 2003 12:45:52 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id h0PKjk4a029054; Sat, 25 Jan 2003 15:45:46 -0500 (EST) Date: Sat, 25 Jan 2003 15:45:46 -0500 (EST) From: Daniel Eischen To: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: idea from NetBSD: signal trampoline on libc ? In-Reply-To: <20030125190021.80728.qmail@web13402.mail.yahoo.com> 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 Sat, 25 Jan 2003, [iso-8859-1] Pedro F. Giffuni wrote: > Hi; > > I was reading an interview about IRIX binary > compatibility on NetBSD, and it looks like they > learned a few tricks. > > This article gets into their native implementation of > signals: > > http://www.onlamp.com/pub/a/bsd/2002/10/10/irix.html > > At the end of the article Emmanuel Dreyfus mentions: > > "One other interesting thing to note is that since > that code was written, Jason Thorpe implemented signal > trampolines provided by libc for NetBSD native > processes, thus adopting the same scheme IRIX used. > The libc provided signal trampoline was adopted in > NetBSD because it removes the need to execute code on > the stack. Memory pages mapped on the stack can > therefore be made non executable (the Memory > Management Unit of all modern CPU are able to enforce > such rules), and we are able to fix a whole class of > security problems. With a non executable stack, it is > not possible anymore to exploit a buffer overflow on a > local variable by executing some user-supplied code > stored on the stack." I think Jake already did this for sparc64, and Jon Mini was working on doing it for i386. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 25 13:37:23 2003 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 F0BBE37B401 for ; Sat, 25 Jan 2003 13:37:20 -0800 (PST) Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5590743F5B for ; Sat, 25 Jan 2003 13:37:20 -0800 (PST) (envelope-from bicknell@ussenterprise.ufp.org) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id h0PLbJh20529 for freebsd-hackers@freebsd.org; Sat, 25 Jan 2003 16:37:19 -0500 (EST) (envelope-from bicknell) Date: Sat, 25 Jan 2003 16:37:19 -0500 From: Leo Bicknell To: freebsd-hackers@freebsd.org Subject: DNS / UDP Port Logging Wierdness Message-ID: <20030125213719.GA20359@ussenterprise.ufp.org> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline Organization: United Federation of Planets X-PGP-Key: http://www.ufp.org/~bicknell/ 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 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've been getting errors like the ones below, well, for as long as I can remember: Jan 25 16:27:43 myhost /kernel: Connection attempt to UDP 10.0.0.1:2663 fro= m 10.1.0.1:53 Jan 25 16:27:43 myhost /kernel: Connection attempt to UDP 10.0.0.1:2683 fro= m 10.1.0.1:53 Jan 25 16:28:53 myhost /kernel: Connection attempt to UDP 10.0.0.1:2705 fro= m 10.0.0.1:53 Jan 25 16:28:53 myhost /kernel: Connection attempt to UDP 10.0.0.1:2707 fro= m 10.0.0.1:53 Jan 25 16:28:53 myhost /kernel: Connection attempt to UDP 10.0.0.1:2716 fro= m 10.0.0.1:53 Jan 25 16:28:53 myhost /kernel: Connection attempt to UDP 10.0.0.1:2737 fro= m 10.0.0.1:53 Jan 25 16:28:58 myhost /kernel: Connection attempt to UDP 10.0.0.1:2706 fro= m 10.1.0.1:53 Jan 25 16:28:58 myhost /kernel: Connection attempt to UDP 10.0.0.1:2708 fro= m 10.1.0.1:53 Jan 25 16:28:58 myhost /kernel: Connection attempt to UDP 10.0.0.1:2734 fro= m 10.1.0.1:53 Jan 25 16:28:58 myhost /kernel: Connection attempt to UDP 10.0.0.1:2751 fro= m 10.1.0.1:53 myhost =3D=3D 10.0.0.1, which is a nameserver. 10.1.0.1 is also a nameserver. They are they two nameservers listed in /etc/resolv.conf. Any ideas why these would occur so often? I get them all day, every day. Long ago I assumed they were caused by any number of programs running on the box that might ask for a DNS query, but then timeout/quit before the reponse was returned. I can't see any other programs having problems resolving names, or erroring out on a frequent basis. =20 Any theories or other things I should look at? While searching for last night's attacks this finally annoyed me enough to do something about it. --=20 Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+MwOPNh6mMG5yMTYRAjE4AJ9f64ioxfOPGsMTBsWj8p9nU1DQlwCZAc+e wov0l+OIxWAcylt/Dccc/4s= =8UtM -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 25 17:55:16 2003 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 A184637B401 for ; Sat, 25 Jan 2003 17:55:15 -0800 (PST) Received: from priv-edtnes61.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADBD143E4A for ; Sat, 25 Jan 2003 17:55:14 -0800 (PST) (envelope-from sh@bel.bc.ca) Received: from reason ([207.6.227.22]) by priv-edtnes61.telusplanet.net (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP id <20030126015509.XGHV7527.priv-edtnes61.telusplanet.net@reason> for ; Sat, 25 Jan 2003 18:55:09 -0700 Message-ID: <000501c2c4dd$f43ed450$16e306cf@slugabed.org> From: "Sean Hamilton" To: Subject: Random disk cache expiry Date: Sat, 25 Jan 2003 17:55:08 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 Greetings, I have a situation where I am reading large quantities of data from disk sequentially. The problem is that as the data is read, the oldest cached blocks are thrown away in favor of new ones. When I start re-reading data from the beginning, it has to read the entire file from disk again. Is there some sort of sysctl which could be changed to induce a more random expiry of cached disk blocks? Wouldn't it seem logical to have something like this in place at all times? thanks, sh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 25 18:38:22 2003 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 3D4E537B401 for ; Sat, 25 Jan 2003 18:38:20 -0800 (PST) Received: from kestrel.alerce.com (kestrel.alerce.com [209.182.219.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74A4043ED8 for ; Sat, 25 Jan 2003 18:38:19 -0800 (PST) (envelope-from hartzell@rosebud.alerce.com) Received: from rosebud.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) by kestrel.alerce.com (8.12.4/8.12.4) with ESMTP id h0Q2c2k6081348 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Sat, 25 Jan 2003 18:38:03 -0800 (PST) (envelope-from hartzell@rosebud.alerce.com) X-Authentication-Warning: kestrel.alerce.com: Host w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92] claimed to be rosebud.alerce.com Received: from rosebud.alerce.com (rosebud.alerce.com [127.0.0.1]) by rosebud.alerce.com (8.12.7/8.12.7) with ESMTP id h0Q2c8N0090373 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 25 Jan 2003 18:38:09 -0800 (PST) (envelope-from hartzell@rosebud.alerce.com) Received: (from hartzell@localhost) by rosebud.alerce.com (8.12.7/8.12.6/Submit) id h0Q2c79N090370; Sat, 25 Jan 2003 18:38:07 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15923.18959.507300.156728@rosebud.alerce.com> Date: Sat, 25 Jan 2003 18:38:07 -0800 To: freebsd-hackers@freebsd.org Subject: Problem opening /dev/ad0{,s2} O_RDWR (also disklabel, grub) on 5.0. X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: hartzell@kestrel.alerce.com (George Hartzell) 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 I'm trying to set up my first 5.0 machine, and I've run into a problem right off of the bat. The machine is a Dell OptiPlex GX110 that has three slices. The first contains Windows 2000, the second has historically contained FreeBSD 4.7,and the third contains Linux. Since I use the system to test stuff before I roll it onto my laptop, and since the laptop seems to need it's original MBR in place so that suspend to disk works properly, I've been running the Dell with GRUB installed in the beginning of the freebsd slice (which is active) [(hd0,1) or /dev/ad0s2] and it's been working great. I tried to do a standard install from the 5.0 release ISO images. After answering all of the standard questions and telling it to go ahead, it spat out an error message as it was presumably setting up the disk. The screen redraws fast enough that I cant' catch the message, but I've tried a couple of times and it's happened each time. When I tried to boot up, I get a message about an unbootable operating system from the code in the MBR. Booting from CD 2, interrupting the loader, setting currdev=disk1s2a: and then "boot /boot/kernel/kernel" brings the machine up just fine. I tried building grub and it wouldn't admit that there was an (hd0,1). Oddly enough, starting grub with --read-only made it able to see (hd0,1). Inside gdb, I noticed that an open of "/dev/ad0" with O_RDWR was returning -1 and setting errno = 1 (EPERM, "Operation not permitted"). Some playing with 'call open("/dev/ad0", 0)', 'call open("/dev/ad0", 1)', and 'call open("/dev/ad0", 2)' made it clear that anything that would write to the disk was failing. I stepped back and started digging around with disklabel, and got some results that seem similar. disklabel -B /dev/ad0s2 auto should reinstall the boot stuff on that slice, but instead it says disklabel: /dev/ad0s2: Operation not permitted and I get the same error message from disklabel -W /dev/ad0s2. So, my questions are: 1) does this ring a bell with anyone? 2) Is there something in 5.0 that requires special magic to write to the raw disk devices? 3) Am I being a bonehead? g. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 25 23:47:17 2003 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 D8E9137B401 for ; Sat, 25 Jan 2003 23:47:15 -0800 (PST) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A752743ED8 for ; Sat, 25 Jan 2003 23:47:14 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-a130.otenet.gr [212.205.215.130]) by mailsrv.otenet.gr (8.12.6/8.12.6) with ESMTP id h0Q7kwBb026270; Sun, 26 Jan 2003 09:46:59 +0200 (EET) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.6/8.12.6) with ESMTP id h0Q7kwZC001722; Sun, 26 Jan 2003 09:46:58 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.6/8.12.6/Submit) id h0Q7kkaM001721; Sun, 26 Jan 2003 09:46:46 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 26 Jan 2003 09:46:46 +0200 From: Giorgos Keramidas To: Mike Bristow Cc: Bill Studenmund , arief_mulya , linux-kernel@vger.kernel.org, tech@openbsd.org, freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org Subject: Re: Technical Differences of *BSD and Linux Message-ID: <20030126074646.GA1683@gothmog.gr> References: <3E30C2A5.5040502@bna.telkomsel.co.id> <20030124225624.GB23410@lindt.urgle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030124225624.GB23410@lindt.urgle.com> 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 2003-01-24 22:56, Mike Bristow wrote: > [ Reply-To set to me: This is probably off topic for all of the lists: > all of the ones I read, anyway. ] > > On Fri, Jan 24, 2003 at 10:03:53AM -0800, Bill Studenmund wrote: > > > 2. How does it differ? What are the technical reasoning > > > behind the decisions? > > > > They differ in most technical areas. Mainly as the *BSD kernels were > > derived from 4.4-Lite, and Linux was derived, I believe, from Minux. > > Point of order: Linux was a cleanroom implementation, using IIRC Minux > as the host OS until such time as it became self-hosting. It was "Minix", not Minux. And Linux started as a clean room implementation that was free from any Minix code, to avoid problems with the license of Minix. See the thread where Linus Torvalds announced the creation of Linux in comp.os.minix below (if the URL wraps, cut n' paste it to one line before checking it out): http://groups.google.com/groups?amp;th=d161e94858c4c0b9&rnum=6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message