From owner-freebsd-ports@FreeBSD.ORG  Tue Apr 22 13:17:05 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E5AAA37B405
	for <ports@freebsd.org>; Tue, 22 Apr 2003 13:17:05 -0700 (PDT)
Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es
	[213.97.200.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D5DE443FCB
	for <ports@freebsd.org>; Tue, 22 Apr 2003 13:17:04 -0700 (PDT)
	(envelope-from flynn@energyhq.homeip.net)
Received: from isengard.energyhq.tk (christine.energyhq.tk [192.168.100.1])
	by energyhq.homeip.net (Postfix) with SMTP
	id 0FFAF2E3A5; Tue, 22 Apr 2003 22:17:10 +0200 (CEST)
Date: Tue, 22 Apr 2003 22:17:14 +0200
From: Miguel Mendez <flynn@energyhq.homeip.net>
To: Kris Kennaway <kris@obsecurity.org>
Message-Id: <20030422221714.4c080bfc.flynn@energyhq.homeip.net>
In-Reply-To: <20030422200124.GA65276@rot13.obsecurity.org>
References: <20030422092946.39da1c27.flynn@energyhq.homeip.net>
	<20030422200124.GA65276@rot13.obsecurity.org>
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386-portbld-freebsd5.0)
X-Face: 1j}k*2<FF@J5*`)_?pCn}ydC/PB|6|Y;
	HZ!6Z!%^'/H*.8V=9YjDc*mn6ypI'16$yA\IP}.
	j3e/`G#5U"1^bwTR6D1H*wPZm}8(ONGrl85Hx!;V^f#`]Xe]35]75HJ%3\J\<j4@V;
	3kd`C(L_6PA_ sS\5f/c]-:)IF{uj[,!sdoNC?%ne5^:XGp9AG1(?gep3f}#;
	>E>Y\+C~E|/wehi[:dCM,{N7/uE3o#
	P,{t7gA/qnovFDDuyQV.1hdT7&#d)q"xY33}{_GS>kk'S{O]nE$A`T|\4&p\&mQyexOLb8}FO<qX<,
	@*v.fy*'PvzDPQK9iUGzU\
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha1"; boundary="/:82TRhZDW?T=.6:"
cc: ports@freebsd.org
Subject: Re: RFC: the linprocfs problem when portupgrading linux_base
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2003 20:17:06 -0000

--/:82TRhZDW?T=.6:
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 22 Apr 2003 13:01:24 -0700
Kris Kennaway <kris@obsecurity.org> wrote:

> You didn't explain what the problem is, but I have a couple of
> comments on the proposed solution.

Mea culpa, I should have explained it better.

The scenario is as follows: User has linux_base installed, and the port
is updated. User runs portupgrade to update an existing linux_base, and
has linprocfs mounted. When portupgrade tries to backup the old port,
cpio fails in /compat/linux/proc and the upgrade is aborted.

> 1) You don't re-mount it afterwards if you unmount

I have mixed feelings about remounting it, It's trivial to add it,
though.

> 2) This will not work if installed via a package.  You need to use a
> pkg-install script for that (and the pre-install target should call
> the script instead of duplicating code).

Point taken, someone could try to `portupgrade -P'. Note that this only
affects people portupgrade'ing linux_base, not new installs.

Cheers,
-- 
        Miguel Mendez - flynn@energyhq.homeip.net
        GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
        EnergyHQ :: http://www.energyhq.tk
	Tired of Spam? -> http://www.trustic.com

--/:82TRhZDW?T=.6:
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+paNNnLctrNyFFPERAoKxAKCX3+iNpwj/NsvhSLwGcTdDOih9HQCeKeE3
5djBpGjbettUvEMPHwkdCj8=
=NECC
-----END PGP SIGNATURE-----

--/:82TRhZDW?T=.6:--