![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Rules & FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UNIX Admin (Papers and study material) | raman1605 | What's on Your Mind? | 10 | 09-28-2007 10:43 AM |
| Unix Material | biyyanimv | Windows & DOS: Issues & Discussions | 1 | 08-17-2007 12:09 AM |
| Good Unix Online Study Material | rahul3894singh | High Level Programming | 2 | 07-21-2007 10:15 PM |
| Reference Material | chrisc@nwark.ne | HP-UX | 0 | 09-30-2006 05:39 PM |
| UniX internals Material | srinivaskathika | I'm new to Unix. Which books should I read? | 7 | 02-01-2002 06:51 AM |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I am currently a student at Bergen Community College. My major is Networking Administration. I am having a tough time with INF-254 (UNIX).
I need some help! What is "README bit" I am having trouble understanding certain concepts: For Example, what does it mean to set SUID, or SGID? e.g., $chmod 4777 testfile1 I know that 777 means: rwxrwxrwx= the 777 is that absolute numeric notation, which is used instead of the symbolic notation (rwx); however, the first bit, the number 4, confuses me. What does the number 4 mean? Also, what in the world is a README bit? Last edited by nelson ele; 02-25-2005 at 09:57 PM. |
| Forum Sponsor | ||
|
|
|
||||
|
According to our rules:
(6) Do not post classroom or homework problems. You may have crossed that line with this post, but I'll help a bit anyway, Until your post I have never encountered the phrase "README bit". You seem to under stand the three read bits so you can't mean those. The suid bit is that 4 that is confusing you. The sgid bit would have been a 2 instead. Briefly, let's say you sign on as "fred". When you run programs, those programs have the rights the "fred" has. For example, fred can read some files but not others. But let's say that fred can run a program called /usr/bin/passwd which is owned by "root". This program is intended to change a password, so it must write to /etc/shadow. "fred" can't write to /etc/shadow, but root can. So we set suid bit on /usr/bin/passwd. Now when fred runs it, the program has the power of "root" (owner of /usr/bin/passwd), not fred. So fred can now change his password. The sgid is similiar but changes the group of the process, not the owner. |
||||
| Google UNIX.COM |