From owner-freebsd-arch Sun Nov 4 2:28:53 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 90A5937B406 for ; Sun, 4 Nov 2001 02:28:49 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fA4AS0q15788 for ; Sun, 4 Nov 2001 11:28:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org Subject: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API From: Poul-Henning Kamp Date: Sun, 04 Nov 2001 11:28:00 +0100 Message-ID: <15786.1004869680@critter.freebsd.dk> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While thinking about the new cloning behaviour of the PTY driver, my attention again crossed the /etc/ttys vs /var/run/utmp mess. Briefly speaking, all tty devices must be prelisted in /etc/ttys, if they are not, no record will be made in /var/run/utmp and consequently, the user will not show up in who(1). This is a minor security issue. A particular tty's entry in /var/run/utmp is determined by its index in the /etc/ttys file, so if you edit /etc/ttys and change the order, insert or delete a record, you screw up your /var/run/utmp. This is just ugly. To complicate matters, some sessions, like ftp, rsync, scp, ppp and so on should also be registered, but are not reliably so. This is just sloppy, and a minor security hazzle. I guess the correct solution is to implement the Single Unix "{get|put}utx" API backed by a db(3) file. http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html Any comments ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Nov 4 6:14:29 2001 Delivered-To: freebsd-arch@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id 8EC6037B406; Sun, 4 Nov 2001 06:14:21 -0800 (PST) Received: from peace.mahoroba.org (IDENT:cMA7wtYfMaVOX2RRUpUQ4ULn9Y7ahP7UP9WmBbGT4az9rc0T0kOscjeLuke0ifXY@peace.mahoroba.org [IPv6:3ffe:505:2:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.1/8.12.1) with ESMTP/inet6 id fA4EECcQ040969; Sun, 4 Nov 2001 23:14:16 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 04 Nov 2001 23:14:10 +0900 (JST) Message-Id: <20011104.231410.74672513.ume@mahoroba.org> To: arch@FreeBSD.org Cc: hackers@FreeBSD.org, peter@FreeBSD.org Subject: [CFR] IPv6 support for pserver of cvs From: Hajimu UMEMOTO X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 =?iso-2022-jp?B?KBskQjgtTFobKEIp?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I wish to add IPv6 support to pserver of cvs. You can find the patch from: http://www.imasy.or.jp/‾ume/ipv6/FreeBSD/cvs-ipv6.diff This patch is based on the patch by KAME folks. But, the patch is for 1.11 and isn't applied cleanly to our cvs. So, some additional modification was made. Please review it. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Nov 4 7:17: 0 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep11-int.chello.nl (amsfep11-int.chello.nl [213.46.243.19]) by hub.freebsd.org (Postfix) with ESMTP id A62D937B405; Sun, 4 Nov 2001 07:16:56 -0800 (PST) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep11-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20011104151650.VMXP28612.amsfep11-int.chello.nl@daemon.chronias.ninth-circle.org>; Sun, 4 Nov 2001 16:16:50 +0100 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.6/8.11.6) id fA4F7hP83256; Sun, 4 Nov 2001 16:07:43 +0100 (CET) (envelope-from asmodai) Date: Sun, 4 Nov 2001 16:07:43 +0100 From: Jeroen Ruigrok/Asmodai To: Hajimu UMEMOTO Cc: arch@FreeBSD.org, hackers@FreeBSD.org, peter@FreeBSD.org Subject: Re: [CFR] IPv6 support for pserver of cvs Message-ID: <20011104160742.B83053@daemon.ninth-circle.org> References: <20011104.231410.74672513.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011104.231410.74672513.ume@mahoroba.org> User-Agent: Mutt/1.3.23i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20011104 15:28], Hajimu UMEMOTO (ume@mahoroba.org) wrote: >I wish to add IPv6 support to pserver of cvs. You can find the patch >from: > > http://www.imasy.or.jp/?(J?ume/ipv6/FreeBSD/cvs-ipv6.diff > >This patch is based on the patch by KAME folks. But, the patch is for >1.11 and isn't applied cleanly to our cvs. So, some additional >modification was made. Please feed this to the cvshome.org guys, that way we can just import the new version along the vendorbranch. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Those who cannot remember the past are condemned to repeat it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Nov 4 7:31:27 2001 Delivered-To: freebsd-arch@freebsd.org Received: from cheer.mahoroba.org (flets-f0022.kamome.or.jp [211.8.127.22]) by hub.freebsd.org (Postfix) with ESMTP id A7D4837B416; Sun, 4 Nov 2001 07:31:21 -0800 (PST) Received: from peace.mahoroba.org (IDENT:ghRjYVDbWXGKfJ2q93JD+2K42WaCQ4Iqn5ZvlFirqdu1/0PpioEB+Hla7x8NqI5M@peace.mahoroba.org [IPv6:3ffe:505:2:0:200:f8ff:fe05:3eae]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.1/8.12.1) with ESMTP/inet6 id fA4FVGcQ017860; Mon, 5 Nov 2001 00:31:16 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 05 Nov 2001 00:31:15 +0900 (JST) Message-Id: <20011105.003115.08400112.ume@mahoroba.org> To: asmodai@wxs.nl Cc: arch@FreeBSD.org, hackers@FreeBSD.org, peter@FreeBSD.org Subject: Re: [CFR] IPv6 support for pserver of cvs From: Hajimu UMEMOTO In-Reply-To: <20011104160742.B83053@daemon.ninth-circle.org> References: <20011104.231410.74672513.ume@mahoroba.org> <20011104160742.B83053@daemon.ninth-circle.org> X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT X-Mailer: xcite1.38> Mew version 2.1 on Emacs 21.1 / Mule 5.0 =?iso-2022-jp?B?KBskQjgtTFobKEIp?= X-Weather: =?iso-2022-jp?B?GyRCOiNGfCROP0BGYEBuOCkbKEI=?= =?iso-2022-jp?B?GyRCJE9GXjhlMGw7fjErJEckORsoQg==?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, >>>>> On Sun, 4 Nov 2001 16:07:43 +0100 >>>>> Jeroen Ruigrok/Asmodai said: asmodai> -On [20011104 15:28], Hajimu UMEMOTO (ume@mahoroba.org) wrote: >I wish to add IPv6 support to pserver of cvs. You can find the patch >from: > > http://www.imasy.or.jp/?(J?ume/ipv6/FreeBSD/cvs-ipv6.diff > >This patch is based on the patch by KAME folks. But, the patch is for >1.11 and isn't applied cleanly to our cvs. So, some additional >modification was made. asmodai> Please feed this to the cvshome.org guys, that way we can just import asmodai> the new version along the vendorbranch. My patch requires getaddrinfo() and getnameinfo(). To do work on other OSs which doesn't have getaddrinfo() and getnameinfo(), we need extra work. Original KAME patch has such code. I hope KAME folks sending their version to cvs folks. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Nov 4 18: 1: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id 7E97E37B41B; Sun, 4 Nov 2001 18:01:00 -0800 (PST) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id fA5210404370; Sun, 4 Nov 2001 18:01:00 -0800 (PST) (envelope-from bmah) Message-Id: <200111050201.fA5210404370@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-arch@freebsd.org Cc: bmah@freebsd.org Subject: One True Awk licensing 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_1335627404P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 04 Nov 2001 18:01:00 -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_1335627404P Content-Type: text/plain; charset=us-ascii Hi-- About a week ago, I said I'd report back if I heard anything from my query to bwk about the state of licensing for 1TAwk. The high order bit is that although he's retired from Lucent (and therefore isn't an official representative of Lucent), he feels that the license "should not be an impediment to your including awk...in FreeBSD". (I'm paraphrasing here in an attempt to avoid quoting large parts of a private email on a public list.) bwk wanted us to let him know if we decide to use it, because he has a few minor code fixes (no feature changes) he'd like us to take too. (This all happened before we ran into the problem with needing POSIX.1 character class support, and DES's subsequent patch to incorporate this feature.) Bruce. --==_Exmh_1335627404P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE75fLc2MoxcVugUsMRAibLAJ9HiVht2k9aRcryTaB4PLUn+5fuRQCfa4zx GT0ahceBzyIf7TDw22EHEKM= =TqX6 -----END PGP SIGNATURE----- --==_Exmh_1335627404P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 3:46: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 86AD737B417; Mon, 5 Nov 2001 03:46:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id UAA57553; Mon, 5 Nov 2001 20:46:00 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20011105.003115.08400112.ume@mahoroba.org> References: <20011104.231410.74672513.ume@mahoroba.org> <20011104160742.B83053@daemon.ninth-circle.org> <20011105.003115.08400112.ume@mahoroba.org> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 23 From: Makoto MATSUSHITA To: arch@FreeBSD.ORG, hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: [CFR] IPv6 support for pserver of cvs Date: Mon, 05 Nov 2001 20:45:59 +0900 Message-Id: <20011105204559O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a plan to start anoncvs service with both IPv4/IPv6 stack, so it would be a great pleasure that FreeBSD's cvs speaks IPv6. Anyway, ume> Original KAME patch has such code. I hope KAME folks sending ume> their version to cvs folks. I've confirmed to KAME forks that: - IPv6 patch for previous release of cvs (such as 1.11 or before) has been submitted to cvshome, but it is in the old days, it cannot confirm at this time. - Today KAME provides an IPv6 patch for cvs 1.11p1. It *is* submitted to cvshome. I hope that cvshome merges KAME's IPv6 patch in their next release... But as an interim solution, we can put "IPv6-ready cvs(1)" to our ports collections. Is it acceptable solution? or should we wait until cvshome's merge? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 3:46:55 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep16-int.chello.nl (amsfep16-int.chello.nl [213.46.243.25]) by hub.freebsd.org (Postfix) with ESMTP id 545F637B418; Mon, 5 Nov 2001 03:46:47 -0800 (PST) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep16-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20011105114323.VLCE2039.amsfep16-int.chello.nl@daemon.chronias.ninth-circle.org>; Mon, 5 Nov 2001 12:43:23 +0100 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.6/8.11.6) id fA5Bjpn93057; Mon, 5 Nov 2001 12:45:51 +0100 (CET) (envelope-from asmodai) Date: Mon, 5 Nov 2001 12:45:50 +0100 From: Jeroen Ruigrok/Asmodai To: "Bruce A. Mah" Cc: freebsd-arch@freebsd.org Subject: Re: One True Awk licensing Message-ID: <20011105124550.N83053@daemon.ninth-circle.org> References: <200111050201.fA5210404370@c527597-a.cstvl1.sfba.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200111050201.fA5210404370@c527597-a.cstvl1.sfba.home.com> User-Agent: Mutt/1.3.23i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20011105 03:30], Bruce A. Mah (bmah@freebsd.org) wrote: >bwk wanted us to let him know if we decide to use it, because he has a >few minor code fixes (no feature changes) he'd like us to take too. > >(This all happened before we ran into the problem with needing POSIX.1 >character class support, and DES's subsequent patch to incorporate this >feature.) So we can become/are becoming/are willing to become the bwk maintainers? Personally it would be cool to do so. Anyone know or have contact with Henry Spencer? I can remember he was supposed to release his new regexp library, which would speed up freegrep as well. Otherwise I see the necessity to start maintaining this library as well. [Yes, I'd rather push as many GNU utilities from the tree if we can offer sufficient BSDL'd alternatives.] -- Jeroen Ruigrok van der Werven / Asmodai / Kita no Mono asmodai@[wxs.nl|[freebsd|xmach].org], finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Love is suicide... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 6:44:26 2001 Delivered-To: freebsd-arch@freebsd.org Received: from green.bikeshed.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A6F0E37B405; Mon, 5 Nov 2001 06:44:23 -0800 (PST) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.4/8.11.1) with ESMTP id fA5EiIr53729; Mon, 5 Nov 2001 09:44:18 -0500 (EST) (envelope-from green@green.bikeshed.org) Message-Id: <200111051444.fA5EiIr53729@green.bikeshed.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Jeroen Ruigrok/Asmodai Cc: "Bruce A. Mah" , freebsd-arch@freebsd.org Subject: Re: One True Awk licensing In-Reply-To: Message from Jeroen Ruigrok/Asmodai of "Mon, 05 Nov 2001 12:45:50 +0100." <20011105124550.N83053@daemon.ninth-circle.org> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Nov 2001 09:44:17 -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > -On [20011105 03:30], Bruce A. Mah (bmah@freebsd.org) wrote: > >bwk wanted us to let him know if we decide to use it, because he has a > >few minor code fixes (no feature changes) he'd like us to take too. > > > >(This all happened before we ran into the problem with needing POSIX.1 > >character class support, and DES's subsequent patch to incorporate this > >feature.) > > So we can become/are becoming/are willing to become the bwk maintainers? > Personally it would be cool to do so. > > Anyone know or have contact with Henry Spencer? I can remember he was > supposed to release his new regexp library, which would speed up > freegrep as well. > Otherwise I see the necessity to start maintaining this library as well. > > [Yes, I'd rather push as many GNU utilities from the tree if we can > offer sufficient BSDL'd alternatives.] It's part of Tcl 8.3+, actually. I made an attempt to porting it to libc interfaces but failed, however, that was some time ago. We'd just need to adapt it to our multibyte facilities, which probably aren't good enough now unless expanded significantly (c.f. Citrus, I'd imagine). Henry Spencer does seem to be on the planet still but I've never heard of anyone having gotten e-mail back from him, much less myself. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 7:15:11 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep12-int.chello.nl (amsfep12-int.chello.nl [213.46.243.17]) by hub.freebsd.org (Postfix) with ESMTP id 9104437B417; Mon, 5 Nov 2001 07:15:06 -0800 (PST) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep12-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20011105151505.KAHZ7460.amsfep12-int.chello.nl@daemon.chronias.ninth-circle.org>; Mon, 5 Nov 2001 16:15:05 +0100 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.6/8.11.6) id fA5FEpJ94790; Mon, 5 Nov 2001 16:14:51 +0100 (CET) (envelope-from asmodai) Date: Mon, 5 Nov 2001 16:14:50 +0100 From: Jeroen Ruigrok/Asmodai To: Makoto MATSUSHITA Cc: arch@FreeBSD.ORG, hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: [CFR] IPv6 support for pserver of cvs Message-ID: <20011105161450.A94474@daemon.ninth-circle.org> References: <20011104.231410.74672513.ume@mahoroba.org> <20011104160742.B83053@daemon.ninth-circle.org> <20011105.003115.08400112.ume@mahoroba.org> <20011105204559O.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011105204559O.matusita@jp.FreeBSD.org> User-Agent: Mutt/1.3.23i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20011105 12:53], Makoto MATSUSHITA (matusita@jp.freebsd.org) wrote: >I hope that cvshome merges KAME's IPv6 patch in their next release... > >But as an interim solution, we can put "IPv6-ready cvs(1)" to our >ports collections. Is it acceptable solution? or should we wait until >cvshome's merge? Ports is ok. Problem when you apply patches to a vendor branch is lots of conflicts later on. Or you must import the patches alongside the vendorbranch as well. In the end, it is Peter's call. -- Jeroen Ruigrok van der Werven / Asmodai / Kita no Mono asmodai@[wxs.nl|[freebsd|xmach].org], finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Messenger of Fear in sight, dark deception kills the light... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 9: 1:32 2001 Delivered-To: freebsd-arch@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id C5B9637B405; Mon, 5 Nov 2001 09:01:26 -0800 (PST) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id fA5H1OU09029; Mon, 5 Nov 2001 09:01:24 -0800 (PST) (envelope-from bmah) Message-Id: <200111051701.fA5H1OU09029@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Jeroen Ruigrok/Asmodai Cc: "Bruce A. Mah" , freebsd-arch@FreeBSD.ORG Subject: Re: One True Awk licensing In-Reply-To: <20011105124550.N83053@daemon.ninth-circle.org> References: <200111050201.fA5210404370@c527597-a.cstvl1.sfba.home.com> <20011105124550.N83053@daemon.ninth-circle.org> Comments: In-reply-to Jeroen Ruigrok/Asmodai message dated "Mon, 05 Nov 2001 12:45:50 +0100." 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_-1962897152P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 05 Nov 2001 09:01:24 -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_-1962897152P Content-Type: text/plain; charset=us-ascii If memory serves me right, Jeroen Ruigrok/Asmodai wrote: > -On [20011105 03:30], Bruce A. Mah (bmah@freebsd.org) wrote: > >bwk wanted us to let him know if we decide to use it, because he has a > >few minor code fixes (no feature changes) he'd like us to take too. > > > >(This all happened before we ran into the problem with needing POSIX.1 > >character class support, and DES's subsequent patch to incorporate this > >feature.) > > So we can become/are becoming/are willing to become the bwk maintainers? > Personally it would be cool to do so. Ummm...if you're suggesting that the FreeBSD developers would become the "official" maintainers of 1TAwk, no, neither bwk nor I were suggesting any such thing. All I meant was that bwk had some patches that he'd made to 1TAwk that weren't in the sharball on Web page, and that he'd pass them to us. Bruce. --==_Exmh_-1962897152P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD4DBQE75sXk2MoxcVugUsMRAhWUAKD17atvuoSDkzOimHAoytLzuvz1vgCYgwLz oSBSLYALThbdW/vBmK0SjQ== =t4ps -----END PGP SIGNATURE----- --==_Exmh_-1962897152P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 9:14: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 7ADD437B416; Mon, 5 Nov 2001 09:13:58 -0800 (PST) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id B07CF4CE04; Mon, 5 Nov 2001 12:13:57 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA19971; Mon, 5 Nov 2001 12:13:56 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA16064; Mon, 5 Nov 2001 09:13:55 -0800 (PST) Message-Id: <200111051713.JAA16064@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: des@ofug.org Subject: Re: Generating host.conf for backward compatibility Cc: arch@freebsd.org References: <3BC67CBD.1DAAC031@DougBarton.net> <3BC7EA21.15F43811@DougBarton.net> Date: Mon, 5 Nov 2001 09:13:55 -0800 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can we move this multi-line stuff above the "Doing initial network setup:" echo? It makes the echo -n stuff printed afterwards look dumb -- right now, we see: Doing initial network setup: Generating /etc/host.conf for compatibility hostname domain. The "hostname domain" are somewhat orphaned. Perhaps Doing initial network setup: host.conf hostname domain. is sufficient? If not, let's make it Generating /etc/host.conf for compatibility Doing initial network setup: hostname domain. I'm fine with the host.conf -> nsswitch.conf update being a multi-line message, because it happens once. Since the nsswitch.conf->host.conf happens on every boot, I'd like to see it be more integrated into the boot messages. I've got patches pending to turn this script into an awk (instead of gawk) script too, so if someone wants to commit this change I can send the other changes too, or I can make whatever change we decide is appropriate. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 16: 5:50 2001 Delivered-To: freebsd-arch@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 001FB37B416 for ; Mon, 5 Nov 2001 16:05:46 -0800 (PST) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fA605kM88592 for ; Mon, 5 Nov 2001 16:05:46 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 86AC63807; Mon, 5 Nov 2001 16:05:46 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bill Fenner Cc: des@ofug.org, arch@FreeBSD.ORG Subject: Re: Generating host.conf for backward compatibility In-Reply-To: <200111051713.JAA16064@windsor.research.att.com> Date: Mon, 05 Nov 2001 16:05:46 -0800 From: Peter Wemm Message-Id: <20011106000546.86AC63807@overcee.netplex.com.au> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner wrote: > > Can we move this multi-line stuff above the "Doing initial network > setup:" echo? It makes the echo -n stuff printed afterwards > look dumb -- right now, we see: > > Doing initial network setup: > Generating /etc/host.conf for compatibility > hostname domain. > > The "hostname domain" are somewhat orphaned. Perhaps > > Doing initial network setup: host.conf hostname domain. > > is sufficient? Yes it is sufficient, I was going to ask this too. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "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-arch" in the body of the message From owner-freebsd-arch Mon Nov 5 17:56:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D4DC837B405; Mon, 5 Nov 2001 17:56:45 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id EB06014C41; Tue, 6 Nov 2001 02:56:42 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Brian F. Feldman" Cc: Jeroen Ruigrok/Asmodai , "Bruce A. Mah" , freebsd-arch@freebsd.org Subject: Re: One True Awk licensing References: <200111051444.fA5EiIr53729@green.bikeshed.org> From: Dag-Erling Smorgrav Date: 06 Nov 2001 02:56:42 +0100 In-Reply-To: <200111051444.fA5EiIr53729@green.bikeshed.org> Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > Henry Spencer does seem to be on the planet still but I've never heard of > anyone having gotten e-mail back from him, much less myself. I got a prompt reply from him when I contacted him about the regexp library back when I was working on freegrep with JP Howard. At that time, he was still working on the new version but did not have an expected release date. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Nov 6 18:22:26 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11]) by hub.freebsd.org (Postfix) with ESMTP id 353CF37B405 for ; Tue, 6 Nov 2001 18:22:25 -0800 (PST) Received: from mira-sjcd-4.cisco.com (mira-sjcd-4.cisco.com [171.69.43.47]) by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id fA72MPn09106 for ; Tue, 6 Nov 2001 18:22:25 -0800 (PST) Received: from home.com (sugan-nt.cisco.com [171.71.49.126]) by mira-sjcd-4.cisco.com (Mirapoint) with ESMTP id ABW32682; Tue, 6 Nov 2001 18:22:13 -0800 (PST) Message-ID: <3BE89CD7.90307@home.com> Date: Tue, 06 Nov 2001 18:30:47 -0800 From: Sugan Subramanian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-arch@FreeBSD.org Subject: Is there going to be support for MIPS platform Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there going to be support for MIPS cpu platforms in freeBSD? Please let me know. Thanks, -Sugan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Nov 6 19:39:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id 3DA5937B405 for ; Tue, 6 Nov 2001 19:39:37 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BD64D66B10; Tue, 6 Nov 2001 19:39:36 -0800 (PST) Date: Tue, 6 Nov 2001 19:39:36 -0800 From: Kris Kennaway To: Sugan Subramanian Cc: freebsd-arch@FreeBSD.org Subject: Re: Is there going to be support for MIPS platform Message-ID: <20011106193936.A35816@xor.obsecurity.org> References: <3BE89CD7.90307@home.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BE89CD7.90307@home.com>; from sugan1970@home.com on Tue, Nov 06, 2001 at 06:30:47PM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 06, 2001 at 06:30:47PM -0800, Sugan Subramanian wrote: > Hi, > Is there going to be support for MIPS cpu platforms in freeBSD? Only if someone writes such support. Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE76Kz4Wry0BWjoQKURAjyPAKDREjTpZ2TtTCSmUUno2LEA6HaKOgCfa0lq VpO1uB6qdUGlTfJ7tPSYjK8= =OHrN -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 4:58:44 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D5C3B37B405; Wed, 7 Nov 2001 04:58:38 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA7CwUB14502; Wed, 7 Nov 2001 07:58:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 07:58:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: arch@freebsd.org Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: <15786.1004869680@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 4 Nov 2001, Poul-Henning Kamp wrote: > While thinking about the new cloning behaviour of the PTY driver, my > attention again crossed the /etc/ttys vs /var/run/utmp mess. > > Briefly speaking, all tty devices must be prelisted in /etc/ttys, if > they are not, no record will be made in /var/run/utmp and consequently, > the user will not show up in who(1). > > This is a minor security issue. > > A particular tty's entry in /var/run/utmp is determined by its index in > the /etc/ttys file, so if you edit /etc/ttys and change the order, > insert or delete a record, you screw up your /var/run/utmp. > > This is just ugly. > > To complicate matters, some sessions, like ftp, rsync, scp, ppp and so > on should also be registered, but are not reliably so. > > This is just sloppy, and a minor security hazzle. > > I guess the correct solution is to implement the Single Unix > "{get|put}utx" API backed by a db(3) file. > > http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html > > Any comments ? "Yet another thread-unsafe API for managing databases"? If we do implement this, we should really implement the _r versions which presumably exist on thread-aware platforms. However, a little inspection of my local Solaris box reveals that they don't have a thread-safe version either: ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | MT-Level | Unsafe | |_____________________________|_____________________________| The Solaris man page also comments: These functions use buffered standard I/O for input, but pututxline() uses an unbuffered write to avoid race condi- tions between processes trying to modify the utmpx and wtmpx files. With a db file, we'd probably have to make use of appropriate locking. The Solaris version actually supports a more broad set of calls that allows the caller a seperate interface to identify the target utmp file. It would be interesting to know if any applications use it. On occasion, I've wondered if this information couldn't be stored in-kernel and managed using calls similar to get/setlogin(). However, that fails to address a variety of scoping issues, and is probably a bad idea given that "logged in" is a userland concept, not a kernel concept. However, this API still requires privilege (directly or indirectly) to modify the database, and potentially a kernel interface wouldn't (subject to some authorization procedures, presumably -- logged username must == process login name, et al). For applications like xterm, it would be nice if privilege was not required -- presumably with improved devfs support for pty's, it will no long be required for that. This isn't an objection, just some observations on implementation. Go with the db idea if you have time to implement it :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 8:13:38 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 8031E37B41A for ; Wed, 7 Nov 2001 08:13:36 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id fA7GDWZ93452; Wed, 7 Nov 2001 08:13:32 -0800 (PST) (envelope-from obrien) Date: Wed, 7 Nov 2001 08:13:32 -0800 From: "David O'Brien" To: Sugan Subramanian Cc: freebsd-arch@FreeBSD.org Subject: Re: Is there going to be support for MIPS platform Message-ID: <20011107081332.A93311@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <3BE89CD7.90307@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BE89CD7.90307@home.com>; from sugan1970@home.com on Tue, Nov 06, 2001 at 06:30:47PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 06, 2001 at 06:30:47PM -0800, Sugan Subramanian wrote: > Is there going to be support for MIPS cpu platforms in freeBSD? Which particular MIPS machine are you interested in? If it is DEC pmax machines forget it. That just does not fall in FreeBSD's "charter". Are you wondering about some of the newer MIPS in embedded and smart devices? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 10:17:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 987E837B41A; Wed, 7 Nov 2001 10:17:37 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fA7IHaT22823; Wed, 7 Nov 2001 13:17:36 -0500 (EST) (envelope-from wollman) Date: Wed, 7 Nov 2001 13:17:36 -0500 (EST) From: Garrett Wollman Message-Id: <200111071817.fA7IHaT22823@khavrinen.lcs.mit.edu> To: rwatson@FreeBSD.ORG Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: References: <15786.1004869680@critter.freebsd.dk> Organization: MIT Laboratory for Computer Science Cc: arch@FreeBSD.ORG Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article you write: >On occasion, I've wondered if this information couldn't be stored >in-kernel and managed using calls similar to get/setlogin(). In point of fact, some of it is stored in the kernel and managed using precisely those calls! Every tty being used for a login is the controlling terminal of some process group, which is associated with a particular session. lognames are stored in the session structure. - -GAWollman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE76XqxI+eG6b7tlG4RAoqdAKCYknx2Y4x7+5/PZP+zuty/FJJxRACgk+RR TZTrFanNvcxfH7lj2y1Alro= =DJMF -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 11:44:57 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6C15037B417 for ; Wed, 7 Nov 2001 11:44:04 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA7JhuB45492 for ; Wed, 7 Nov 2001 14:43:56 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 14:43:55 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-arch@FreeBSD.org Subject: Changing req->p to req->td in sysctl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm in the process of pushing the (td) reference from ioctl() into if_ioctl() so that the thread information is available in a number of new places in the network stack. However, in order to pass it down, we now need it in a few newer places further up the stack (bpfattach(), ...). One of the places this touches is the sysctl() interface, where the process is passed in via req->p. The attached patch replaces the proc reference with a thread reference. Right now, it slightly increases complexity elsewhere (adds an additional dereference), but when we move to td->td_ucred, suser using the thread reference, and with the pushing of td down the stack, this will actually be a net improvement for simplicity. Please review, I'd like to commit in a day or two. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ? sys/i386/conf/LINT Index: sys/compat/linux/linux_mib.c =================================================================== RCS file: /home/ncvs/src/sys/compat/linux/linux_mib.c,v retrieving revision 1.13 diff -u -r1.13 linux_mib.c --- sys/compat/linux/linux_mib.c 2001/09/08 19:07:03 1.13 +++ sys/compat/linux/linux_mib.c 2001/11/07 19:20:52 @@ -56,11 +56,11 @@ char osname[LINUX_MAX_UTSNAME]; int error; - strcpy(osname, linux_get_osname(req->p)); + strcpy(osname, linux_get_osname(req->td->td_proc)); error = sysctl_handle_string(oidp, osname, LINUX_MAX_UTSNAME, req); if (error || req->newptr == NULL) return (error); - error = linux_set_osname(req->p, osname); + error = linux_set_osname(req->td->td_proc, osname); return (error); } @@ -77,11 +77,11 @@ char osrelease[LINUX_MAX_UTSNAME]; int error; - strcpy(osrelease, linux_get_osrelease(req->p)); + strcpy(osrelease, linux_get_osrelease(req->td->td_proc)); error = sysctl_handle_string(oidp, osrelease, LINUX_MAX_UTSNAME, req); if (error || req->newptr == NULL) return (error); - error = linux_set_osrelease(req->p, osrelease); + error = linux_set_osrelease(req->td->td_proc, osrelease); return (error); } @@ -98,11 +98,11 @@ int oss_version; int error; - oss_version = linux_get_oss_version(req->p); + oss_version = linux_get_oss_version(req->td->td_proc); error = sysctl_handle_int(oidp, &oss_version, 0, req); if (error || req->newptr == NULL) return (error); - error = linux_set_oss_version(req->p, oss_version); + error = linux_set_oss_version(req->td->td_proc, oss_version); return (error); } Index: sys/kern/kern_mib.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mib.c,v retrieving revision 1.48 diff -u -r1.48 kern_mib.c --- sys/kern/kern_mib.c 2001/11/06 20:09:33 1.48 +++ sys/kern/kern_mib.c 2001/11/07 19:21:57 @@ -155,12 +155,12 @@ { int error; - if (jailed(req->p->p_ucred)) { + if (jailed(req->td->td_proc->p_ucred)) { if (!jail_set_hostname_allowed && req->newptr) return(EPERM); error = sysctl_handle_string(oidp, - req->p->p_ucred->cr_prison->pr_host, - sizeof req->p->p_ucred->cr_prison->pr_host, req); + req->td->td_proc->p_ucred->cr_prison->pr_host, + sizeof req->td->td_proc->p_ucred->cr_prison->pr_host, req); } else error = sysctl_handle_string(oidp, hostname, sizeof hostname, req); @@ -186,7 +186,7 @@ struct prison *pr; int error, level; - pr = req->p->p_ucred->cr_prison; + pr = req->td->td_proc->p_ucred->cr_prison; /* * If the process is in jail, return the maximum of the global and Index: sys/kern/kern_sysctl.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_sysctl.c,v retrieving revision 1.117 diff -u -r1.117 kern_sysctl.c --- sys/kern/kern_sysctl.c 2001/10/12 09:16:36 1.117 +++ sys/kern/kern_sysctl.c 2001/11/07 19:21:57 @@ -848,7 +848,7 @@ bzero(&req, sizeof req); - req.p = td->td_proc; + req.td = td; if (oldlenp) { req.oldlen = *oldlenp; @@ -1037,12 +1037,12 @@ /* Is this sysctl sensitive to securelevels? */ if (req->newptr && (oid->oid_kind & CTLFLAG_SECURE)) { - if (req->p == NULL) { + if (req->td == NULL) { error = securelevel_gt(NULL, 0); /* XXX */ if (error) return (error); } else { - error = securelevel_gt(req->p->p_ucred, 0); + error = securelevel_gt(req->td->td_proc->p_ucred, 0); if (error) return (error); } @@ -1050,14 +1050,14 @@ /* Is this sysctl writable by only privileged users? */ if (req->newptr && !(oid->oid_kind & CTLFLAG_ANYBODY)) { - if (req->p != NULL) { + if (req->td != NULL) { int flags; if (oid->oid_kind & CTLFLAG_PRISON) flags = PRISON_ROOT; else flags = 0; - error = suser_xxx(NULL, req->p, flags); + error = suser_xxx(NULL, req->td->td_proc, flags); if (error) return (error); } @@ -1132,7 +1132,7 @@ bzero(&req, sizeof req); - req.p = td->td_proc; + req.td = td; if (oldlenp) { if (inkernel) { Index: sys/kern/uipc_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_usrreq.c,v retrieving revision 1.75 diff -u -r1.75 uipc_usrreq.c --- sys/kern/uipc_usrreq.c 2001/10/29 20:04:03 1.75 +++ sys/kern/uipc_usrreq.c 2001/11/07 19:22:35 @@ -850,7 +850,7 @@ for (unp = LIST_FIRST(head), i = 0; unp && i < n; unp = LIST_NEXT(unp, unp_link)) { if (unp->unp_gencnt <= gencnt) { - if (cr_cansee(req->p->p_ucred, + if (cr_cansee(req->td->td_proc->p_ucred, unp->unp_socket->so_cred)) continue; unp_list[i++] = unp; Index: sys/netinet/ip_divert.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_divert.c,v retrieving revision 1.52 diff -u -r1.52 ip_divert.c --- sys/netinet/ip_divert.c 2001/09/12 08:37:54 1.52 +++ sys/netinet/ip_divert.c 2001/11/07 19:23:14 @@ -46,6 +46,7 @@ #include #include #include +#include #include #include #include @@ -485,7 +486,8 @@ s = splnet(); for (inp = LIST_FIRST(divcbinfo.listhead), i = 0; inp && i < n; inp = LIST_NEXT(inp, inp_list)) { - if (inp->inp_gencnt <= gencnt && !prison_xinpcb(req->p, inp)) + if (inp->inp_gencnt <= gencnt && !prison_xinpcb( + req->td->td_proc, inp)) inp_list[i++] = inp; } splx(s); Index: sys/netinet/raw_ip.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/raw_ip.c,v retrieving revision 1.86 diff -u -r1.86 raw_ip.c --- sys/netinet/raw_ip.c 2001/11/04 22:56:25 1.86 +++ sys/netinet/raw_ip.c 2001/11/07 19:23:14 @@ -627,7 +627,7 @@ for (inp = LIST_FIRST(ripcbinfo.listhead), i = 0; inp && i < n; inp = LIST_NEXT(inp, inp_list)) { if (inp->inp_gencnt <= gencnt) { - if (cr_cansee(req->p->p_ucred, + if (cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred)) continue; inp_list[i++] = inp; Index: sys/netinet/tcp_subr.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_subr.c,v retrieving revision 1.116 diff -u -r1.116 tcp_subr.c --- sys/netinet/tcp_subr.c 2001/10/09 21:40:30 1.116 +++ sys/netinet/tcp_subr.c 2001/11/07 19:23:14 @@ -855,7 +855,7 @@ for (inp = LIST_FIRST(tcbinfo.listhead), i = 0; inp && i < n; inp = LIST_NEXT(inp, inp_list)) { if (inp->inp_gencnt <= gencnt) { - if (cr_cansee(req->p->p_ucred, + if (cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred)) continue; inp_list[i++] = inp; @@ -913,7 +913,7 @@ struct inpcb *inp; int error, s; - error = suser_xxx(0, req->p, PRISON_ROOT); + error = suser_xxx(0, req->td->td_proc, PRISON_ROOT); if (error) return (error); error = SYSCTL_IN(req, addrs, sizeof(addrs)); @@ -926,7 +926,7 @@ error = ENOENT; goto out; } - error = cr_cansee(req->p->p_ucred, inp->inp_socket->so_cred); + error = cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred); if (error) goto out; bzero(&xuc, sizeof(xuc)); @@ -953,7 +953,7 @@ struct inpcb *inp; int error, s, mapped = 0; - error = suser_xxx(0, req->p, PRISON_ROOT); + error = suser_xxx(0, req->td->td_proc, PRISON_ROOT); if (error) return (error); error = SYSCTL_IN(req, addrs, sizeof(addrs)); @@ -982,7 +982,7 @@ error = ENOENT; goto out; } - error = cr_cansee(req->p->p_ucred, inp->inp_socket->so_cred); + error = cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred); if (error) goto out; bzero(&xuc, sizeof(xuc)); Index: sys/netinet/udp_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/udp_usrreq.c,v retrieving revision 1.99 diff -u -r1.99 udp_usrreq.c --- sys/netinet/udp_usrreq.c 2001/10/22 12:43:30 1.99 +++ sys/netinet/udp_usrreq.c 2001/11/07 19:23:14 @@ -583,7 +583,7 @@ for (inp = LIST_FIRST(udbinfo.listhead), i = 0; inp && i < n; inp = LIST_NEXT(inp, inp_list)) { if (inp->inp_gencnt <= gencnt) { - if (cr_cansee(req->p->p_ucred, + if (cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred)) continue; inp_list[i++] = inp; @@ -635,7 +635,7 @@ struct inpcb *inp; int error, s; - error = suser_xxx(0, req->p, PRISON_ROOT); + error = suser_xxx(0, req->td->td_proc, PRISON_ROOT); if (error) return (error); error = SYSCTL_IN(req, addrs, sizeof(addrs)); @@ -648,7 +648,7 @@ error = ENOENT; goto out; } - error = cr_cansee(req->p->p_ucred, inp->inp_socket->so_cred); + error = cr_cansee(req->td->td_proc->p_ucred, inp->inp_socket->so_cred); if (error) goto out; bzero(&xuc, sizeof(xuc)); Index: sys/netinet6/udp6_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netinet6/udp6_usrreq.c,v retrieving revision 1.18 diff -u -r1.18 udp6_usrreq.c --- sys/netinet6/udp6_usrreq.c 2001/09/25 18:40:52 1.18 +++ sys/netinet6/udp6_usrreq.c 2001/11/07 19:23:21 @@ -464,7 +464,7 @@ struct inpcb *inp; int error, s; - error = suser(req->p); + error = suser(req->td->td_proc); if (error) return (error); Index: sys/sys/sysctl.h =================================================================== RCS file: /home/ncvs/src/sys/sys/sysctl.h,v retrieving revision 1.99 diff -u -r1.99 sysctl.h --- sys/sys/sysctl.h 2001/09/12 08:38:05 1.99 +++ sys/sys/sysctl.h 2001/11/07 19:23:25 @@ -111,7 +111,7 @@ * so that we can use the interface from the kernel or from user-space. */ struct sysctl_req { - struct proc *p; /* used for access checking */ + struct thread *td; /* used for access checking */ int lock; void *oldptr; size_t oldlen; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 13:20:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id F098A37B43B; Wed, 7 Nov 2001 13:20:09 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA72632; Wed, 7 Nov 2001 13:02:24 -0800 (PST) Date: Wed, 7 Nov 2001 13:02:23 -0800 (PST) From: Julian Elischer To: Robert Watson Cc: freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 7 Nov 2001, Robert Watson wrote: > > I'm in the process of pushing the (td) reference from ioctl() into > if_ioctl() so that the thread information is available in a number of new > places in the network stack. However, in order to pass it down, we now > need it in a few newer places further up the stack (bpfattach(), ...). this is one of the reasons I left it :-) > One of the places this touches is the sysctl() interface, where the > process is passed in via req->p. The attached patch replaces the proc > reference with a thread reference. Right now, it slightly increases > complexity elsewhere (adds an additional dereference), but when we move to > td->td_ucred, suser using the thread reference, and with the pushing of td > down the stack, this will actually be a net improvement for simplicity. > Please review, I'd like to commit in a day or two. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > ? sys/i386/conf/LINT > Index: sys/compat/linux/linux_mib.c > =================================================================== > RCS file: /home/ncvs/src/sys/compat/linux/linux_mib.c,v Assuming LINT compiles, then This looks fine.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 13:23:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kiste.thiemo.net (kiste.thiemo.net [193.159.181.84]) by hub.freebsd.org (Postfix) with ESMTP id 7F08637B405 for ; Wed, 7 Nov 2001 13:23:11 -0800 (PST) Received: (from uucp@localhost) by kiste.thiemo.net (8.9.3/8.9.3) with UUCP id WAA35012 for freebsd-arch@FreeBSD.ORG; Wed, 7 Nov 2001 22:23:09 +0100 (CET) (envelope-from rk@home.ronald.org) Received: (from rk@localhost) by wallace.home.ronald.org (8.11.6/8.11.6) id fA7LIkm00435; Wed, 7 Nov 2001 22:18:46 +0100 (CET) (envelope-from rk@ronald.org) Date: Wed, 7 Nov 2001 22:18:46 +0100 (CET) Message-Id: <200111072118.fA7LIkm00435@wallace.home.ronald.org> To: freebsd-arch@FreeBSD.ORG Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API Newsgroups: list.freebsd-arch References: <15786.1004869680@critter.freebsd.dk> From: Ronald Kuehn X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In freebsd-arch, Robert Watson wrote: > On Sun, 4 Nov 2001, Poul-Henning Kamp wrote: > > While thinking about the new cloning behaviour of the PTY driver, my > > attention again crossed the /etc/ttys vs /var/run/utmp mess. > > > > Briefly speaking, all tty devices must be prelisted in /etc/ttys, if > > they are not, no record will be made in /var/run/utmp and consequently, > > the user will not show up in who(1). > > > > This is a minor security issue. > > > > A particular tty's entry in /var/run/utmp is determined by its index in > > the /etc/ttys file, so if you edit /etc/ttys and change the order, > > insert or delete a record, you screw up your /var/run/utmp. > > > > This is just ugly. > > > > To complicate matters, some sessions, like ftp, rsync, scp, ppp and so > > on should also be registered, but are not reliably so. > > > > This is just sloppy, and a minor security hazzle. > > > > I guess the correct solution is to implement the Single Unix > > "{get|put}utx" API backed by a db(3) file. > > > > http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html > > > > Any comments ? > "Yet another thread-unsafe API for managing databases"? If we do > implement this, we should really implement the _r versions which > presumably exist on thread-aware platforms. However, a little inspection > of my local Solaris box reveals that they don't have a thread-safe version > either: > ____________________________________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE | > |_____________________________|_____________________________| > | MT-Level | Unsafe | > |_____________________________|_____________________________| > The Solaris man page also comments: > These functions use buffered standard I/O for input, but > pututxline() uses an unbuffered write to avoid race condi- > tions between processes trying to modify the utmpx and wtmpx > files. > With a db file, we'd probably have to make use of appropriate locking. > The Solaris version actually supports a more broad set of calls that > allows the caller a seperate interface to identify the target utmp file. > It would be interesting to know if any applications use it. > On occasion, I've wondered if this information couldn't be stored > in-kernel and managed using calls similar to get/setlogin(). However, > that fails to address a variety of scoping issues, and is probably a bad > idea given that "logged in" is a userland concept, not a kernel concept. > However, this API still requires privilege (directly or indirectly) to > modify the database, and potentially a kernel interface wouldn't (subject > to some authorization procedures, presumably -- logged username must == > process login name, et al). For applications like xterm, it would be nice > if privilege was not required -- presumably with improved devfs support > for pty's, it will no long be required for that. > This isn't an objection, just some observations on implementation. Go > with the db idea if you have time to implement it :-). Hi, a long time ago I implemented a mechanism for changing ownership of ptys in the style used by Solaris or Tru64 Unix using a helper program. Please have a look at PR 9770. I don't know if this is still needed for devfs. It only solves half the problem: Applications don't need to be setuid root just for providing pseudo ttys. Unfortunately, the utmp problem still exists. One way to fix this would be to use something like the SUSv2 described mechanism as described above. I don't think that this can be solved in a clean way w/o kernel support. If non-root processes are allowed to make entries in a utmp-style database, certain risks must be considered: (1) Make sure a process can only make entries for terminals it really owns. (2) How to get rid of out-of-date entries when the processes that made them "forgot" to remove them? Problem (2) usually does not occure on systems that only allow root-processes to make those entries. Those programs can be inspected and are under control of the system administrator or vendor. When normal user processes (like screen) are allowed to make such entries their removal cannot be assured since any user can install them. Maybe some deamon could get information from the kernel when a pseudo terminal is closed. It could then assure that the utmp entry gets removed. Bye, Ronald -- * The whole problem with the world is that fools and fanatics are always * so certain of themselves, but wiser people so full of doubts. * --Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 13:29:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4A17B37B41B; Wed, 7 Nov 2001 13:29:32 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fA7LSbP36295; Wed, 7 Nov 2001 22:28:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: arch@freebsd.org Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: Your message of "Wed, 07 Nov 2001 07:58:30 EST." Date: Wed, 07 Nov 2001 22:28:36 +0100 Message-ID: <36293.1005168516@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >> I guess the correct solution is to implement the Single Unix >> "{get|put}utx" API backed by a db(3) file. >> >> http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html >> >> Any comments ? > >"Yet another thread-unsafe API for managing databases"? Interesting point, I didn't think of that. On the other hand, I don't see much point in multiple threads competing to fiddle this info since they will all have the same session... Anyhow, I'm mightily leaning towards the idea that /var/run/utmp should die and be moved into the session in the kernel, apart from all the obvious things, this would make some interesting information available in kernel dumps. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 14: 3:38 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8FC4437B419 for ; Wed, 7 Nov 2001 14:03:32 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA7M3LB49523; Wed, 7 Nov 2001 17:03:21 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 17:03:21 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: arch@freebsd.org Subject: Re: /etc/ttys, /var/run/utmp, ttyslot(3) and {get|put}utx* API In-Reply-To: <36293.1005168516@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 7 Nov 2001, Poul-Henning Kamp wrote: > In message , Robe > rt Watson writes: > > >> I guess the correct solution is to implement the Single Unix > >> "{get|put}utx" API backed by a db(3) file. > >> > >> http://www.opengroup.org/onlinepubs/007908799/xsh/endutxent.html > >> > >> Any comments ? > > > >"Yet another thread-unsafe API for managing databases"? > > Interesting point, I didn't think of that. On the other hand, I don't > see much point in multiple threads competing to fiddle this info since > they will all have the same session... Well, one of the problems with some of the other thread-unsafe APIs is when they get used by a library. For example, the ACL spec requires an acl_to_text() call, which (among other things) converts numeric uid's into usernames. The issue here is probably more of one of reentrance than thread-safety: when acl_to_text() invokes getpwuid(), it may interfere with the calling program. It's not impossible to imagine these types of calls interfering when used in a program such as a kde-ized or gnome-ized xdm. > Anyhow, I'm mightily leaning towards the idea that /var/run/utmp should > die and be moved into the session in the kernel, apart from all the > obvious things, this would make some interesting information available > in kernel dumps. I'm leaning that way also; there are some minor scoping issues, but I think they can be addressed by caching a struct ucred in the kernel session when the session is created, or possibly when the information is updated. This would allow virtual utmp entries to be ommitted based on (for example) what jail or MLS compartment the user is in. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 14:40:27 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C194B37B419 for ; Wed, 7 Nov 2001 14:40:25 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA7MeHB50126 for ; Wed, 7 Nov 2001 17:40:18 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 17:40:17 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I should mention that both GENERIC and LINT build fine, but that I wasn't sure what to do about the use of req->p in netsmb/netncp. Both appear still to use pre-KSE struct proc all over the place, altough the .h files have been updated (?). I'd be happy to try to update them to post-KSE, although I don't use either so can't test them. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 16:20:19 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 77CF237B405; Wed, 7 Nov 2001 16:20:13 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA73210; Wed, 7 Nov 2001 16:12:33 -0800 (PST) Date: Wed, 7 Nov 2001 16:12:31 -0800 (PST) From: Julian Elischer To: Robert Watson Cc: freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 7 Nov 2001, Robert Watson wrote: > > I should mention that both GENERIC and LINT build fine, but that I wasn't > sure what to do about the use of req->p in netsmb/netncp. Both appear > still to use pre-KSE struct proc all over the place, altough the .h files > have been updated (?). I'd be happy to try to update them to post-KSE, > although I don't use either so can't test them. netsmb and netncp, along with smbfs and nwfs are the two modules that defeated me in trying to change them to a threaded model. This is because they have some idea of a "session" but it is not clear to me that whether a session is a "per thread or Per process" thing. I have been discussing this with Boris but since he is very busy I haven't god a really definitive answer on it.. I don't know the protocols so it's hard for me to figure out what SHOULD be done. In discussions with Boris, it may be that some of the original proc pointers need to be split into both proc and thread pointers, as it appears that they are being used for two purposes, one of wich becomes a thread responsibility and the other of which remains a proc characteristic. i.e. the thread pointer is used to serialise the accesses, but a session is owned by a process and any thread in that process may try use it. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 16:25: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 5ED1037B419; Wed, 7 Nov 2001 16:25:04 -0800 (PST) Received: from dialup-209.245.141.138.dial1.sanjose1.level3.net ([209.245.141.138] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 161d09-0003w5-00; Wed, 07 Nov 2001 16:25:01 -0800 Message-ID: <3BE9D10F.7702D0FE@mindspring.com> Date: Wed, 07 Nov 2001 16:25:51 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > netsmb and netncp, along with smbfs and nwfs > are the two modules that defeated me in trying to change them to > a threaded model. This is because they have some > idea of a "session" but it is not clear to me that > whether a session is a "per thread or Per process" thing. NCP is session per connection. SMB is session over connection, or session per connection. I would _not_ recommend a thread per session. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 16:40:19 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8512337B405; Wed, 7 Nov 2001 16:40:17 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA73311; Wed, 7 Nov 2001 16:38:36 -0800 (PST) Date: Wed, 7 Nov 2001 16:38:35 -0800 (PST) From: Julian Elischer To: Terry Lambert Cc: Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: <3BE9D10F.7702D0FE@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well if you do know the protocols, and have lots of time you could do those two modules.... Thanks :-) On Wed, 7 Nov 2001, Terry Lambert wrote: > Julian Elischer wrote: > > netsmb and netncp, along with smbfs and nwfs > > are the two modules that defeated me in trying to change them to > > a threaded model. This is because they have some > > idea of a "session" but it is not clear to me that > > whether a session is a "per thread or Per process" thing. > > NCP is session per connection. > SMB is session over connection, or session per connection. > > I would _not_ recommend a thread per session. > > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 17: 9:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9F3D637B418 for ; Wed, 7 Nov 2001 17:09:16 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA8194B52286; Wed, 7 Nov 2001 20:09:04 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 20:09:04 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer Cc: freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 7 Nov 2001, Julian Elischer wrote: > On Wed, 7 Nov 2001, Robert Watson wrote: > > > I should mention that both GENERIC and LINT build fine, but that I wasn't > > sure what to do about the use of req->p in netsmb/netncp. Both appear > > still to use pre-KSE struct proc all over the place, altough the .h files > > have been updated (?). I'd be happy to try to update them to post-KSE, > > although I don't use either so can't test them. > > netsmb and netncp, along with smbfs and nwfs are the two modules that > defeated me in trying to change them to a threaded model. This is > because they have some idea of a "session" but it is not clear to me > that whether a session is a "per thread or Per process" thing. Hmm. Well, I'll go ahead and commit my patch as is, and push the thread pointers down into if_ioctl, which will let me expunge a number of curproc references (and continue moving us towards td_ucred). If time permits, I'll look some more at the ncp/smb code, but given its complexity, I'm not sure how much progress I can make. So if someone wants to pick up on this, that would be great--we certainly don't want to let these fall by the wayside for much longer. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 18:34:50 2001 Delivered-To: freebsd-arch@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 98DFE37B418; Wed, 7 Nov 2001 18:34:47 -0800 (PST) Received: from dialup-209.245.141.138.dial1.sanjose1.level3.net ([209.245.141.138] helo=mindspring.com) by hawk.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 161f1g-0000bl-00; Wed, 07 Nov 2001 18:34:45 -0800 Message-ID: <3BE9EF76.5A78796A@mindspring.com> Date: Wed, 07 Nov 2001 18:35:34 -0800 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > Well if you do know the protocols, > and have lots of time > you could do those two modules.... > > Thanks :-) I can't do NCP because I worked for Novell on similar code for UnixWare, and they have a hell of a non-compete agreement, and are agressive about non-disclosure. The point is knowing that it's per connection, it's more than half the battle. The SMB stuff is seriously documented in the CIFS document, but then you know Jeremy as well as I do. 8-). The old code is session per connection; the newer stuff muxes. It is very hard to get a "one size fits all; I'm not sure if I agree entirely with the approach. 8-(. I think that it would be nice to have a pointer to a top object that points to the credential holder, and then late-bind them, rather than distributing cred references around like Halloween candy to trick-or-treaters... Unfortunately, I'm much more busy than I was a week ago, or I'd comment more in depth. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Nov 7 19:14:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dcb.hz.zj.cn (dcb.hz.zj.cn [202.96.103.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A84C37B418 for ; Wed, 7 Nov 2001 19:14:32 -0800 (PST) Received: from c ([61.154.132.141]) by dcb.hz.zj.cn (8.11.0/8.11.0) with SMTP id fA83Anv00402 for ; Thu, 8 Nov 2001 11:10:49 +0800 (CST) From: Reply-To: c.h@china-lutong.com Message-ID: {7C0F0C1F-D429-11D5-A6CB-444553540000}@c Subject: Head & Rotor VE(CHINA-LuTong) 11/08 To: china-diesel.fuel.injection@dcb.hz.zj.cn X-Mailer: DiffondiCool V3,1,7,1 (W95/NT) (Build: Apr 14 2000) Mime-Version: 1.0 Date: Thu, 08 Nov 2001 11:02:32 +0800 Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@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 MIME Message ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi: My name is ChenHua, and I'm writing on behalf of the China-Lutong mechanical company=2E Located in the south east of China, we specialize in hydraulic heads for the VE distributor pump=2E We can supply standard, good quality units at a very competitive price=2E The following types are available: Engine model VE PUMS code NO UNIT PRICE(EX WORKS) ISUZU) NP-VE4/11L 096400-1600 $USD40 (NIPPON DENSO) ISUZU NP-VE4/11R 146402-0820(zexel) $USD45 ISUZU NP-VE4/11L 146402-0920(zexel) $USD40 ISUZU NP-VE4/11L 146402-3820(zexel) $USD45 NISSAN NP-VE4/12R 146402-4320(zexel) $USD50 IVECO NP-VE4/11R 1 468 334 798(BOSCH) $USD45 CUMMINS NP-VE6/12R 1 468 336 423(BOSCH) $USD50 In addition,the following models have been produced by us,but there is no stock at present=2E 096400-1240 (NIPPON DENSO) 1 468 333 323(BOSCH) 2 468 334 021(BOSCH) 2 468 334 050(BOSCH) 1 468 334 565(BOSCH) 1 468 334 580(BOSCH) 1 468 334 590(BOSCH) 1 468 334 596(BOSCH) 1 468 334 603(BOSCH) 1 468 334 604(BOSCH) 1 468 334 837(BOSCH) 1 468 334 874(BOSCH) 1 468 334 899(BOSCH) 2 468 335 022(BOSCH) 1 468 336 528(BOSCH) 1 468 336 464(BOSCH) 1 468 336 480(BOSCH) 2 468 336 013(BOSCH) 1 468 336 614(BOSCH) 146400-8821(zexel) 146402-4020(zexel) VE distributor head: 3-cyl:USD:45/1pcs 4-cyl:USD:45/1pcs 5-cyl:USD:50/1pcs 6-cyl:USD:50/1pcs Minimum order is 48pcs a model=2E We also can make to order for other models as required=2E We use precision forging technology to create our products and surface treat them using an imported shot-blasting machine=2E The constant grinding process guarantees identical clearance in each plunger=2E Because we have been in the field of diesel fuel injection systems for quite a few years, we are acquainted with many domestic manufacturers of, and sales agents for, parts such as injector nozzles, plungers, delivery valves and so on=2E If you are interested in our products, please contact me=2E Thank you for your interest in our company=2E Thanks and best regards ! C=2EHua Sales & purchasing director HTTP://WWW=2EChina-LuTong=2ECOM c=2Eh@china-lutong=2Ecom ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: application/octet-stream; name="error.txt" Content-Transfer-Encoding: quoted-printable Content-Description: error.txt Content-Disposition: inline; filename="error.txt" Sorry, but we couldn't open the attach file when sending this message original file: f:\=D7=CA=C1=CF\=B8=F6=C8=CB=CD=BC=C6=AC\=CD=BC=C6=AC\ve'head&rotor'(146833= 6423)=2Ejpg ------=_NextPart_000_007F_01BDF6C7.FABAC1B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Nov 8 8:57:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ns.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by hub.freebsd.org (Postfix) with ESMTP id C2F4437B419; Thu, 8 Nov 2001 08:57:19 -0800 (PST) Received: from koganei.wide.ad.jp (eAc1Aai074.tky.mesh.ad.jp [202.225.7.74]) (authenticated (0 bits)) by ns.koganei.wide.ad.jp (8.11.6/8.11.6) with ESMTP id fA8Gvjs46230; Fri, 9 Nov 2001 01:57:45 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) Message-ID: <3BEAB96A.6090801@koganei.wide.ad.jp> Date: Fri, 09 Nov 2001 01:57:14 +0900 From: Katsushi Kobayashi User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5+) Gecko/20011101 X-Accept-Language: en-us MIME-Version: 1.0 To: hackers@freebsd.org, arch@freebsd.org Subject: Does CAM support simplified direct-access device ? Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am testing my SBP, SCSI over firewire, driver on some firewire disk. An SCSI device work well under the specific usage. Unfortunately, I have met a CAM related trouble on another disk. This disk responds its device type as "simplefied direct-access device 0Eh", not "direct access device 00h". Does CAM function on FreeBSD support this device type? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Nov 8 9: 3:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id D171537B416; Thu, 8 Nov 2001 09:03:06 -0800 (PST) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id fA8H2wH67097; Thu, 8 Nov 2001 09:02:58 -0800 (PST) (envelope-from mjacob@feral.com) Date: Thu, 8 Nov 2001 09:02:58 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Katsushi Kobayashi Cc: hackers@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: Does CAM support simplified direct-access device ? In-Reply-To: <3BEAB96A.6090801@koganei.wide.ad.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (should be on -scsi list) The answer is "no"- this should be a restated as "does da support this device type". On Fri, 9 Nov 2001, Katsushi Kobayashi wrote: > Hello, > > I am testing my SBP, SCSI over firewire, driver on some firewire > disk. An SCSI device work well under the specific usage. > Unfortunately, I have met a CAM related trouble on another disk. > This disk responds its device type as "simplefied direct-access > device 0Eh", not "direct access device 00h". > > Does CAM function on FreeBSD support this device type? > > Thanks. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Nov 9 10:49:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 91AA137B416 for ; Fri, 9 Nov 2001 10:49:34 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id fA9InDS51338; Fri, 9 Nov 2001 10:49:13 -0800 (PST) (envelope-from obrien) Date: Fri, 9 Nov 2001 10:49:13 -0800 From: "David O'Brien" To: Peter Jeremy Cc: Marcel Moolenaar , arch@FreeBSD.ORG Subject: Re: FYI: A thought on 64-bit time_t on Alpha Message-ID: <20011109104913.B51278@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20011030225720.A39348@dhcp01.pn.xcllnt.net> <20011102073924.O94635@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011102073924.O94635@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Fri, Nov 02, 2001 at 07:39:24AM +1100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 02, 2001 at 07:39:24AM +1100, Peter Jeremy wrote: > My feeling is that Alpha should move to 64-bit time. I realise that > it won't survive to 2038, but it is currently our reference 64-bit > platform. > Others have pointed out that the pain of porting FreeBSD to > a new 64-bit platform will be increased by having to simultaneously > manage a changed time_t size WRT i386. This pain can be minimised if > the 32-bit dependencies have been weeded out in the Alpha. Feh, by all 3 people using -current on their Alpha's? No thanks. Those 3 already have too any irons in the fire. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Nov 9 11:24: 0 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 5F38637B405; Fri, 9 Nov 2001 11:23:57 -0800 (PST) Received: (from marcel@localhost) by kayak.xcllnt.net (8.11.6/8.11.4) id fA9JNuE15856; Fri, 9 Nov 2001 11:23:56 -0800 (PST) (envelope-from marcel) Date: Fri, 9 Nov 2001 11:23:56 -0800 From: Marcel Moolenaar To: "David O'Brien" Cc: Peter Jeremy , arch@FreeBSD.ORG Subject: Re: FYI: A thought on 64-bit time_t on Alpha Message-ID: <20011109112356.D15768@kayak.xcllnt.net> References: <20011030225720.A39348@dhcp01.pn.xcllnt.net> <20011102073924.O94635@gsmx07.alcatel.com.au> <20011109104913.B51278@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011109104913.B51278@dragon.nuxi.com> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 09, 2001 at 10:49:13AM -0800, David O'Brien wrote: > On Fri, Nov 02, 2001 at 07:39:24AM +1100, Peter Jeremy wrote: > > My feeling is that Alpha should move to 64-bit time. I realise that > > it won't survive to 2038, but it is currently our reference 64-bit > > platform. > > > Others have pointed out that the pain of porting FreeBSD to > > a new 64-bit platform will be increased by having to simultaneously > > manage a changed time_t size WRT i386. This pain can be minimised if > > the 32-bit dependencies have been weeded out in the Alpha. > > Feh, by all 3 people using -current on their Alpha's? No thanks. > Those 3 already have too any irons in the fire. This means that there are more FreeBSD/ia64 users than FreeBSD/alpha users on -current. Somehow I don't think this is the case... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Nov 9 13:13:10 2001 Delivered-To: freebsd-arch@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id C8B0937B405; Fri, 9 Nov 2001 13:13:06 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id fA9LCncw010006; Fri, 9 Nov 2001 22:12:50 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fA9LCmQ13856; Fri, 9 Nov 2001 22:12:48 +0100 (CET) (envelope-from wkb) Date: Fri, 9 Nov 2001 22:12:48 +0100 From: Wilko Bulte To: Marcel Moolenaar Cc: "David O'Brien" , Peter Jeremy , arch@FreeBSD.ORG Subject: Re: FYI: A thought on 64-bit time_t on Alpha Message-ID: <20011109221248.A13839@freebie.xs4all.nl> References: <20011030225720.A39348@dhcp01.pn.xcllnt.net> <20011102073924.O94635@gsmx07.alcatel.com.au> <20011109104913.B51278@dragon.nuxi.com> <20011109112356.D15768@kayak.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011109112356.D15768@kayak.xcllnt.net>; from marcel@xcllnt.net on Fri, Nov 09, 2001 at 11:23:56AM -0800 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 09, 2001 at 11:23:56AM -0800, Marcel Moolenaar wrote: > On Fri, Nov 09, 2001 at 10:49:13AM -0800, David O'Brien wrote: > > On Fri, Nov 02, 2001 at 07:39:24AM +1100, Peter Jeremy wrote: > > > My feeling is that Alpha should move to 64-bit time. I realise that > > > it won't survive to 2038, but it is currently our reference 64-bit > > > platform. > > > > > Others have pointed out that the pain of porting FreeBSD to > > > a new 64-bit platform will be increased by having to simultaneously > > > manage a changed time_t size WRT i386. This pain can be minimised if > > > the 32-bit dependencies have been weeded out in the Alpha. > > > > Feh, by all 3 people using -current on their Alpha's? No thanks. > > Those 3 already have too any irons in the fire. > > This means that there are more FreeBSD/ia64 users than FreeBSD/alpha > users on -current. Somehow I don't think this is the case... Depends on what one calls a '-current user'. I build -current on one of my alphas every now and then. But that is hardly 'using' it. My production box is an Athlon. Are we looking for people who (almost) exclusively use FreeBSD/alpha? And to add to that, -current? -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Nov 9 21:44: 9 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 5D5EF37B41D; Fri, 9 Nov 2001 21:44:07 -0800 (PST) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id fAA5i6Q16775; Fri, 9 Nov 2001 21:44:07 -0800 (PST) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id fAA5iIO00778; Fri, 9 Nov 2001 21:44:18 -0800 (PST) (envelope-from marcel) Date: Fri, 9 Nov 2001 21:44:18 -0800 From: Marcel Moolenaar To: Wilko Bulte Cc: "David O'Brien" , Peter Jeremy , arch@FreeBSD.ORG Subject: Re: FYI: A thought on 64-bit time_t on Alpha Message-ID: <20011109214418.A577@dhcp01.pn.xcllnt.net> References: <20011030225720.A39348@dhcp01.pn.xcllnt.net> <20011102073924.O94635@gsmx07.alcatel.com.au> <20011109104913.B51278@dragon.nuxi.com> <20011109112356.D15768@kayak.xcllnt.net> <20011109221248.A13839@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011109221248.A13839@freebie.xs4all.nl> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 09, 2001 at 10:12:48PM +0100, Wilko Bulte wrote: > > Depends on what one calls a '-current user'. I build -current on > one of my alphas every now and then. But that is hardly 'using' it. Same here. > My production box is an Athlon. Are we looking for people who > (almost) exclusively use FreeBSD/alpha? And to add to that, -current? I think anyone who has an Alpha is affected, but I'd like to hear from people who have Alpha in production. -current will become -stable and that's where the pain is felt eventually. I don't think that the -current users are necessarily the right people to make the decision. It probably applies double for me... So far I've only heard that's not worth the trouble, but I'm not convinced that avoiding any changes on the Alpha is less trouble. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Nov 10 9:58:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sydney.worldwide.lemis.com (dhcp243.rocks.bsdconeurope.org [195.40.100.243]) by hub.freebsd.org (Postfix) with ESMTP id 01BF137B425 for ; Sat, 10 Nov 2001 09:58:46 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.6/8.9.3) id fAAHwE931854; Sat, 10 Nov 2001 17:58:14 GMT (envelope-from grog) Date: Sat, 10 Nov 2001 17:58:13 +0000 From: Greg Lehey To: Sugan Subramanian Cc: freebsd-arch@FreeBSD.org Subject: Re: Is there going to be support for MIPS platform Message-ID: <20011110175813.C31680@sydney.worldwide.lemis.com> References: <3BE89CD7.90307@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BE89CD7.90307@home.com>; from sugan1970@home.com on Tue, Nov 06, 2001 at 06:30:47PM -0800 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 6 November 2001 at 18:30:47 -0800, Sugan Subramanian wrote: > Hi, > Is there going to be support for MIPS cpu platforms in freeBSD? There was a port in progress a while back, but it seems to have run out of steam. I don't think it'll restart, but that's a personal opinion. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Nov 10 11:58:43 2001 Delivered-To: freebsd-arch@freebsd.org Received: from femail37.sdc1.sfba.home.com (femail37.sdc1.sfba.home.com [24.254.60.31]) by hub.freebsd.org (Postfix) with ESMTP id 35E9D37B417; Sat, 10 Nov 2001 11:58:41 -0800 (PST) Received: from c1230146a ([24.176.213.244]) by femail37.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20011110195841.YKUV8188.femail37.sdc1.sfba.home.com@c1230146a>; Sat, 10 Nov 2001 11:58:41 -0800 Message-ID: <000501c16a22$c4eec820$f4d5b018@stcla1.sfba.home.com> From: "Sugan Subramanian" To: "Greg Lehey" Cc: References: <3BE89CD7.90307@home.com> <20011110175813.C31680@sydney.worldwide.lemis.com> Subject: Re: Is there going to be support for MIPS platform Date: Sat, 10 Nov 2001 12:03:30 -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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If there is enough interest and support, I would like to pitch in. Many embedded systems now are based on MIPS R4k and R7k CPU systems. I have worked on some inhouse cooked up OSs. They seem to run out of steam and did not scale well over a period of time. I would like to learn freeBSD and possibly help in porting it onto MIPS based CPU systems. I have a decent knowledge of BSD mbuf implementation and how it is used with IP stack and thats about it. Thanks, -Sugan ----- Original Message ----- From: "Greg Lehey" To: "Sugan Subramanian" Cc: Sent: Saturday, November 10, 2001 9:58 AM Subject: Re: Is there going to be support for MIPS platform > On Tuesday, 6 November 2001 at 18:30:47 -0800, Sugan Subramanian wrote: > > Hi, > > Is there going to be support for MIPS cpu platforms in freeBSD? > > There was a port in progress a while back, but it seems to have run > out of steam. I don't think it'll restart, but that's a personal > opinion. > > Greg > -- > See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message