--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Fri, 2003-10-17 at 02:36, Roland Scheidegger wrote:
> > Keith Whitwell wrote:
> > Well, I've never tried to install the whole XFree86 when it's running,
> > but I'm often lazy and just compile the mesa/src/drv/r200 if only small
> > changes happen and copy the r200_dri.so manually. But as you suggested,
> > if I'll delete the installed r200_dri.so before copying the new one,
> > then no crashes happen - the running kde happily keeps its references to 
> > the old deleted dri driver and new apps will use the new dri driver.
> 
> cp --remove-destination will do that. I'm a bit surprised cp doesn't
> always unlink the destination before replacing it though; is there any
> reason why this shouldn't be considered a bug? (Seems to me the only
> difference should be whether it follows symlinks or not) I can't think
> of an example where overwriting the existing file would be useful, but
> that may well be just me, any clues appreciated. :)
> 
When you do it this way the inode(number) and it's meta data are lost.  cp would have 
to know
about the filesystem and what meta data needs to be saved/restored.  As this results 
in the loss
of permitions it is not the default.



__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise 
Linux in the Boardroom; in the Front Office; & in the Server Room 
http://www.enterpriselinuxforum.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to