From: Doug Smith (w9wi@earthlink.net)
Date: 11/15/07
>> >> 2. lock a file so that it cannot be changed
>>
>> chmod 555?
>
>Readable, therefore copyable, and printable. All chmod 555 accomplishes
>is a weak ability to maintain that one copy of the file doesn't get
>changed.
Yeah, that's why I erased questions 1 and 3 before posting(grin). I certainly concur with the common wisdom that those are not possible.
As for #2, it depends on how sophisticated the users are and whether you care if modified *copies* of the file exist under different filenames or elsewhere in dataspace. I would suggest chmod 555 would be adequate for a majority of applications - but since we don't know the application in question, it may or may not be adequate here.
-- Send all requests to: nlug-request@linuxlists.org Put your command in the SUBJECT of the message: "subscribe" or "unsubscribe" Quick unsubscribe: <mailto:nlug-request@linuxlists.org?Subject=3Dunsubscribe> Mailing list archives may be found at: <http://www.nlug.org/mail/> ********************************************************************** This list is from your pals at NetCentral <http://www.netcentral.com/>
This archive was generated by hypermail 2.1.6 : 12/02/07 CST