On Sat, 08 Nov 2014, John Conover wrote:
> and look at the ownership of the cups directory and compare it to the
> ownership in /etc.
In this example, you're not archiving etc/cups or etc, you're just
archiving etc/cups/printers.conf, which means that tar must create
etc/cups itself, and has no re
Don Armstrong writes:
> On Sat, 08 Nov 2014, John Conover wrote:
> > That's true, Don, but the issue is the ownership of the DIRECTORIES
> > when installing, a directory TREE in a non root temporary directory.
> > The file ownerships are, indeed, correct. The ownerships of the
> > directories down
On Sat, 08 Nov 2014, John Conover wrote:
> That's true, Don, but the issue is the ownership of the DIRECTORIES
> when installing, a directory TREE in a non root temporary directory.
> The file ownerships are, indeed, correct. The ownerships of the
> directories down to the files are always root/roo
Don Armstrong writes:
> On Sat, 08 Nov 2014, John Conover wrote:
> > There has been changes in the way a tar(1) restore to a temporary
> > directory constructs directory ownerships; as login theuser, in
> > ${HOME}:
>
> This looks like you're using tar --no-same-owner, possibly via an ENV
> variab
On Sat, 08 Nov 2014, John Conover wrote:
> There has been changes in the way a tar(1) restore to a temporary
> directory constructs directory ownerships; as login theuser, in
> ${HOME}:
This looks like you're using tar --no-same-owner, possibly via an ENV
variable or something else.
% fakeroot ba
There has been changes in the way a tar(1) restore to a temporary
directory constructs directory ownerships; as login theuser, in
${HOME}:
mkdir xxx xxx/yyy; touch xxx/yyy/zzz
su
Password:
# cd /
# tar cvf home/theuser/aaa.tar home/theuser/xxx
home/theuser/xxx/
home/theuser/xxx/yyy/
home/th
6 matches
Mail list logo
