#1728: Chapter 6 - Package Management - Explain why 'install' is generally safer than 'cp' -----------------------------------------+---------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [email protected] Type: enhancement | Status: new Priority: normal | Milestone: Future Component: Book | Version: SVN Severity: normal | Resolution: Keywords: | -----------------------------------------+---------------------------------- Comment (by [EMAIL PROTECTED]):
I took a look at the install.c source and the cp.c source. They both do extensive error checking, but when it comes down to the final operation, both call the same library routine: copy() My review has persuaded me that install is '''not''' safer than cp. The install utility is merely a convenience for installers to copy the file, make prerequsite directories, set permissions and ownership, etc all with one command. I could find no references in either install or cp that try to determine if a file (library) is already loaded in memory. Indeed, the operating system handles that issue automatically and does not actually remove the old file until all open references to it are closed, even though the entry may be removed from the directory structure. The simple am most correct way to address this ticket is to merely remove third bullet in section 6.3.1. -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1728> LFS Trac <http://wiki.linuxfromscratch.org/lfs/> Linux From Scratch: Your Distro, Your Rules. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
