On Tue, Oct 30, 2001 at 06:56:00AM -0500, Dan Ellis wrote: > device (disk, cd-rom, etc.). On page 119, we read that the S, in this > case, represents the SUID bit. That is, whoever executes search will > have the uid of the process set to 1 (the uid of the owner of search). > This is meaningless in this case because only uid 1 can execute search > anyway. Hope this helps.
> > b--Sr---w- 1 29812 24375 62, 34 Nov 19 2031 wap A few minor corrections: 1. UID 1 doesn't own these files, UID 27725 and 29812 do. 1 is the number of hard links to the file in question, which is always at least one for a file that actually exists. 2. The S, being capital, also means that the file is *not* marked executable by user. These permission look pretty odd to me, even for a device file. They mean that the owner of the file has NO permissions, only members of the (unknown) group 24375 can read from it, and everyone else can write to it. For the original author: Ever wierder, (I'm assuming this is a Linux kernel) devices in the 60-63 range are experimental or local devices, so unless you are writing your own hardware drivers, that shouldn't even BE there. Offhand, my guess is that something went seriously wrong with your filesystem. While it's possible to change the permissions back to what there were, you can't just "un-device" them. Odds are you'll have to rm these files and restore them from backup. --K
