Subject: Re: install/8090
To: Perry E. Metzger <>
From: Luke Mewburn <>
List: netbsd-bugs
Date: 11/14/2004 20:56:56
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 12, 2004 at 08:03:52PM +0000, David Laight wrote:
  | On Fri, Nov 12, 2004 at 02:25:11PM -0500, Perry E. Metzger wrote:
  | >=20
  | > I don't think --chroot in any way fixes the problem. Could you explain
  | > why you think it would? I think this should be reopened.
  | tar -h ... will follow symbolic links in the existing filesystem, but
  | requires that the target actually exists.
  | So if you have /home -> /usr/home then 'tar -h' will require that
  | /usr/home can be found - otherwise it will recreate /home.
  | When sysinst runs tar, the sytems root filesystem is mounted on /target=
  | so /targetroot/home -> /usr/home in the memfs install fs - which won't =
  | With the --chroot (to /targetroot) the symlink in anchored inside the c=
  | so tar will find the systems /usr/home and be happy.
  | I did a test install with one of the directories moved by an absolute
  | symlink - and sysinst just followed the symlink.
  | I think we could add /home back into the sets...

No, we can't.

It's not just this PR which is affected by this problem; it occurs
any time you build the sets and then extract them manually using pax.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.6 (NetBSD)