On 1/26/07, Jerzy Goca <[EMAIL PROTECTED]> wrote: > I am experimenting with bluetooth and I have to change permissions to > /var/lock. > I looked into (B)LFS books, to the FHS but could not find any directions > about the "proper" way to give permissions to /var/lock directory. > I think this may be solved in a distribution policy level.
I woudn't change permissions on the whole /var/lock directory. Other packages might want to use it, too. Instead, make a /var/lock/bluetooth directory with the necessary permissions. > I think that making it chmod 1777 would be what I need, but I may be not > aware of something. Can you advise me what permissions should be given? So, I guess what you're trying to do is allow all users to create a lock file to indicate ownership of bluetooth or something? There are better systems, but I don't think there's anything really insecure about that. /tmp is that way. You might worry about people abusing the permissions and filling the directory with crap. > BTW, the search of the (B)LFS mailing list is not working.... Try this out. http://google.com/coop/cse?cx=012845676306904203607%3Azsvebyymzw8 -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
