From owner-freebsd-arch@FreeBSD.ORG Sun Jul 18 17:51:19 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 578F916A4CE for ; Sun, 18 Jul 2004 17:51:19 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 199FE43D2D for ; Sun, 18 Jul 2004 17:51:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-67-115-75-142.dsl.lsan03.pacbell.net [67.115.75.142]) i6IHp1j2014473; Sun, 18 Jul 2004 13:51:06 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5C2B052BDC; Sun, 18 Jul 2004 10:51:00 -0700 (PDT) Date: Sun, 18 Jul 2004 10:51:00 -0700 From: Kris Kennaway To: Robert Millan Message-ID: <20040718175100.GA27990@xor.obsecurity.org> References: <20040716220848.A35405@armor.freesurf.fr> <20040718031554.GF1070@dragon.nuxi.com> <20040718133330.GA21009@khazad.dyndns.org> <20040718151649.GA53675@gothmog.gr> <20040718165142.GA17142@khazad.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <20040718165142.GA17142@khazad.dyndns.org> User-Agent: Mutt/1.4.2.1i cc: Giorgos Keramidas cc: Nicolas Souch cc: freebsd-arch@freebsd.org Subject: Re: some PRs X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jul 2004 17:51:19 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 18, 2004 at 06:51:42PM +0200, Robert Millan wrote: > On Sun, Jul 18, 2004 at 06:16:49PM +0300, Giorgos Keramidas wrote: > > On 2004-07-18 15:33, Robert Millan wrote: > > > > > > I think it's useful for compatibility. > >=20 > > In general, I'm not against compatibility. However, what's the end of > > this route? To create one special device node in /dev for every > > possible errno value? :-( >=20 > I don't claim that /dev/full is useful just for the sake of it. Your argu= ment > (that having a device just for each errno value is silly) is something I > basicaly agree with. >=20 > But if some applications depend on it, it's still helpful for portability. > I don't know what support for native compatibility is expected or planned= for > FreeBSD, but I know you have a Ports Collection with thousands of package= s, > and this might minimaly reduce the work of your port maintainers. IMHO, y= ou > should ask the people working in the Ports Collection for their opinion b= efore > taking a decision. >=20 > (Note this patch comes from the context of the Debian GNU/kFreeBSD porting > effort, in which we port Debian GNU/Linux packages, which are a bit more > likely to introduce Linuxisms than the average candidate for FreeBSD Port= s. > Thus, our requirements might differ somewhat.) There's no mention of /dev/full in the build logs (e.g. configure script output) of any of the 11000-odd ports in the ports collection. Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA+riEWry0BWjoQKURAtwaAKD/c9VAiA791uSCbAegSlIhatiYewCg0dXz 1TIldHrg41/8zUK/INE1TnA= =txr6 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--