Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Dec 2014 16:34:55 +1100
From:      Jan Mikkelsen <janm@transactionware.com>
To:        Ronald Klop <ronald-lists@klop.ws>
Cc:        libarchive-discuss@googlegroups.com, freebsd-stable@freebsd.org
Subject:   Re: bsdtar POLA change in 10.0?
Message-ID:  <5BEC32C8-3611-419C-A0C8-3AB4DA776A27@transactionware.com>
In-Reply-To: <op.xccilipxkndu52@ronaldradial.radialsg.local>
References:  <53171DAE.5070203@li.ru> <1394110822.21224.91297125.0B659AFB@webmail.messagingengine.com> <56BC2D25-7163-43A2-AB04-9A808AA98F85@gmail.com> <op.xccilipxkndu52@ronaldradial.radialsg.local>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 7 Mar 2014, at 20:42, Ronald Klop <ronald-lists@klop.ws> wrote:
>=20
> On Thu, 06 Mar 2014 19:43:28 +0100, Warner Losh <imp@bsdimp.com> =
wrote:
>=20
>>=20
>> On Mar 6, 2014, at 6:00 AM, Mark Felder <feld@freebsd.org> wrote:
>>=20
>>>=20
>>>=20
>>> On Wed, Mar 5, 2014, at 6:50, Marat N.Afanasyev wrote:
>>>> I wonder why
>>>>=20
>>>> bsdtar --one-file-system
>>>>=20
>>>> suddenly started to skip archiving of mount-points? And no mention =
of
>>>> such behaviour change either in UPDATING or errata :(
>>>>=20
>>>=20
>>>    --one-file-system
>>>            (c, r, and u modes) Do not cross mount points.
>>>=20
>>> Isn't that what it's supposed to do? Skip any mounted filesystems? =
Was
>>> it broken before? Or do I simply not understand the behavior you're
>>> seeing.
>>=20
>> Before it would archive the directory where the other filesystem was =
mounted, but nothing else.
>>=20
>> Now it doesn=E2=80=99t archive that directory.
>>=20
>> I believe this is a bug, since that directory (but nothing in it or =
under it) still belongs to this filesystem...
>>=20
>> Warner
>=20
> I cc'ed libarchive-discuss@googlegroups.com for more exposure to the =
issue.
>=20

Reviving an old discussion =E2=80=94 this just caused my build process =
for 10.1 to create root filesystems without /dev, which is obviously =
constraining.

Using the --one-file-system option should should preserve mount point =
directories. Will this be fixed?

Jan.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5BEC32C8-3611-419C-A0C8-3AB4DA776A27>