Sponsored Content
Full Discussion: question on UNIX material
Top Forums UNIX for Dummies Questions & Answers question on UNIX material Post 64022 by nelson ele on Saturday 26th of February 2005 12:51:02 AM
Old 02-26-2005
Question question on UNIX material

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-26-2005 at 01:57 AM..
 

10 More Discussions You Might Find Interesting

1. New to Unix. Which books should I read?

UniX internals Material

Hi! I have 1.5 years experience in unix environment and shell scripting. Now, I started learning UNIX internals and network programming. Can you please help in finding the same material on the net Thanks Srinivas. (7 Replies)
Discussion started by: srinivaskathika
7 Replies

2. HP-UX

Reference Material

I'm having to write 'C' programs for a group of HP-UX 11.X systems. While I have found many 'C' reference books which I like, none of them reference using 'C' in the UNIX environment. Anyone have any good recommendations for books about 'C' programming under UNIX? Thanks. Chris (0 Replies)
Discussion started by: chrisc@nwark.ne
0 Replies

3. Programming

Good Unix Online Study Material

HI Friends, I wanted to start this thread inorder to keep all the Unix starters to easily find useful material through this thread...I request you all to provide with the URL address of any gud material you know... thanks and regards... (2 Replies)
Discussion started by: rahul3894singh
2 Replies

4. Windows & DOS: Issues & Discussions

Unix Material

Hi, Can anyone provide the UNIX material. Thanks. (1 Reply)
Discussion started by: biyyanimv
1 Replies

5. Shell Programming and Scripting

PDF material required

Does anyone here have the AU23 Course material........ Edit: Please do not post your e-mail address while asking for help. (0 Replies)
Discussion started by: gurpreets
0 Replies

6. UNIX for Dummies Questions & Answers

Having trouble finding good unix study material

I am trying to read about a UNIX distribution list but I cannot seem to find out what it is or where I can find a website to read more on it any help would be greatly appreciated (2 Replies)
Discussion started by: starshot
2 Replies

7. UNIX for Dummies Questions & Answers

Any study material for begineers for UNIX please??

Any study material for begineers for UNIX please?? (2 Replies)
Discussion started by: niranjany
2 Replies

8. What is on Your Mind?

UNIX Admin (Papers and study material)

Hi, I want to prepare and then appear for Unix admin certification. Please guide me for the study material and Exams that are required to be taken for UNIX certifcation. Thanks in advance. (11 Replies)
Discussion started by: raman1605
11 Replies

9. Solaris

Required UNIX shell scripting material

As I am new in UNIX , and I want to learn UNIX shell scripting. where shall I get material for Scripting ( For basics fundamentals and production environmental scripts) Kindly provide me ...................... (7 Replies)
Discussion started by: sunray
7 Replies

10. UNIX for Dummies Questions & Answers

UNIX Study Material

Hi , Can anyone suggest me any UNIX Study material and UNIX Certification specific for TELECOM-DOMAIN. Best Regards, Om Prakash. (14 Replies)
Discussion started by: omprakash1986
14 Replies
EXECVE(2)						     Linux Programmer's Manual							 EXECVE(2)

NAME
execve - execute program SYNOPSIS
#include <unistd.h> int execve(const char *filename, char *const argv [], char *const envp[]); DESCRIPTION
execve() executes the program pointed to by filename. filename must be either a binary executable, or a script starting with a line of the form "#! interpreter [arg]". In the latter case, the interpreter must be a valid pathname for an executable which is not itself a script, which will be invoked as interpreter [arg] filename. argv is an array of argument strings passed to the new program. envp is an array of strings, conventionally of the form key=value, which are passed as environment to the new program. Both, argv and envp must be terminated by a null pointer. The argument vector and environ- ment can be accessed by the called program's main function, when it is defined as int main(int argc, char *argv[], char *envp[]). execve() does not return on success, and the text, data, bss, and stack of the calling process are overwritten by that of the program loaded. The program invoked inherits the calling process's PID, and any open file descriptors that are not set to close on exec. Signals pending on the calling process are cleared. Any signals set to be caught by the calling process are reset to their default behaviour. The SIGCHLD signal (when set to SIG_IGN) may or may not be reset to SIG_DFL. If the current program is being ptraced, a SIGTRAP is sent to it after a successful execve(). If the set-uid bit is set on the program file pointed to by filename the effective user ID of the calling process is changed to that of the owner of the program file. Similarly, when the set-gid bit of the program file is set the effective group ID of the calling process is set to the group of the program file. If the executable is an a.out dynamically-linked binary executable containing shared-library stubs, the Linux dynamic linker ld.so(8) is called at the start of execution to bring needed shared libraries into core and link the executable with them. If the executable is a dynamically-linked ELF executable, the interpreter named in the PT_INTERP segment is used to load the needed shared libraries. This interpreter is typically /lib/ld-linux.so.1 for binaries linked with the Linux libc version 5, or /lib/ld-linux.so.2 for binaries linked with the GNU libc version 2. RETURN VALUE
On success, execve() does not return, on error -1 is returned, and errno is set appropriately. ERRORS
EACCES The file or a script interpreter is not a regular file. EACCES Execute permission is denied for the file or a script or ELF interpreter. EACCES The file system is mounted noexec. EPERM The file system is mounted nosuid, the user is not the superuser, and the file has an SUID or SGID bit set. EPERM The process is being traced, the user is not the superuser and the file has an SUID or SGID bit set. E2BIG The argument list is too big. ENOEXEC An executable is not in a recognised format, is for the wrong architecture, or has some other format error that means it cannot be executed. EFAULT filename points outside your accessible address space. ENAMETOOLONG filename is too long. ENOENT The file filename or a script or ELF interpreter does not exist, or a shared library needed for file or interpreter cannot be found. ENOMEM Insufficient kernel memory was available. ENOTDIR A component of the path prefix of filename or a script or ELF interpreter is not a directory. EACCES Search permission is denied on a component of the path prefix of filename or the name of a script interpreter. ELOOP Too many symbolic links were encountered in resolving filename or the name of a script or ELF interpreter. ETXTBSY Executable was open for writing by one or more processes. EIO An I/O error occurred. ENFILE The limit on the total number of files open on the system has been reached. EMFILE The process has the maximum number of files open. EINVAL An ELF executable had more than one PT_INTERP segment (i.e., tried to name more than one interpreter). EISDIR An ELF interpreter was a directory. ELIBBAD An ELF interpreter was not in a recognised format. CONFORMING TO
SVr4, SVID, X/OPEN, BSD 4.3. POSIX does not document the #! behavior but is otherwise compatible. SVr4 documents additional error condi- tions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL, EIS- DIR or ELIBBAD error conditions. NOTES
SUID and SGID processes can not be ptrace()d. Linux ignores the SUID and SGID bits on scripts. The result of mounting a filesystem nosuid vary between Linux kernel versions: some will refuse execution of SUID/SGID executables when this would give the user powers she did not have already (and return EPERM), some will just ignore the SUID/SGID bits and exec success- fully. A maximum line length of 127 characters is allowed for the first line in a #! executable shell script. SEE ALSO
chmod(2), fork(2), execl(3), environ(5), ld.so(8) Linux 2.0.30 1997-09-03 EXECVE(2)
All times are GMT -4. The time now is 03:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy