[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#248351: tetex-bin: update-texmf: cp -p gives an error



El Jueves 17 Junio 2004 09:45, Frank Küster escribió:

> Hi Pablo,
> >>
> >> cp: preserving permissions for `/tmp/tmp.wRmhQA/texmfXZdf7VA.md5sum.d':
> >> invalid argument
> >>
> >> So, i've just change the line with:
> >>
> >> cp -R ${MD5SUMS} ${TMPTXMF}.md5sum.d
> >
> > Hm. What kind of filesystem do you have on /tmp? It seems one cannot
> > set permissions there, which is odd.
>
> I've played a little: If I mount a floppy with MS-DOS FAT filesystem and
> try to do a "cp -a" on it, even as root, I get the same error
> message. Therefore it seems as if this could be the cause - do you
> indeed use an unusual filesystem for /tmp? If you don't remember, the
> output of "mount" would probably help.
>
> If this is the case, I'm confused. I think most programs in Debian,
> except those that are specifically developped to handle external
> filesystems, rely on being able to do "ordinary" stuff that used to work
> on every UNIX - e.g. setting permissions.
>
> On the other hand, I don't see that this is really required by any
> policy or the like - in fact the Debian Policy only contains
> requirements for developers, not for users and their choice of
> filesystem.
>
> Well, in this particular case, I think the permission stuff is not
> really necessary. But I would like to sort this out more
> generally. Therefore I'd be glad if you would tell us which filesystem
> you use, and why.

	I'm confused about this bug. I'm using xfs in all my system. I installed 
Debian using a XFS netinst image, and I upgraded it to unstable release. I'm 
using 2.4.24 kernel.

	My /tmp directory supports settings permissions and users, so I don't 
understand why I got the error using cp -a

	In fact, I've just tried:

$ cp -a ~/dummy /tmp/.

	and it works correctly.

	I've no clues :'(
	Do you want me to try anything?

	Regards,
		Pedro Pablo

-- 
 18:39:46 up  3:46,  1 user,  load average: 0.04, 0.07, 0.01



Reply to: