09-18-2009
Distribution means a certain set of applications that are bundled and pre-configured. The difference in that for Linux distributions (or distros) can range from almost nothing (eg. RHEL vs. CentOS), to a completely different intention, and thus software selection (eg. Slackware vs. Mint)
Different "flavours" are called that because they are based on the same principles (POSIX, Single UNIX Specification), but follow different ways for implementation. For example, while all Unices have a sigaction system call, probably none of them share the same implementation, as the Kernel itself follows different specifications.
I hope I helped clear some of the confusion.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
ehe may i know what are the difference between Unix & Linux, and what are the advantages of having Unix as well as disadvantages of having Unix or if u dun mind i am dumb do pls tell me what are the advantages as well as the disadvantages of having linux as well. thanks (1 Reply)
Discussion started by: cybertechmkteo
1 Replies
2. UNIX for Advanced & Expert Users
:confused: Hi All
Can anyone help me in finding the answer of the question mentioned below.
What is the difference between Unix & linux ?
Thanks in Advance to all
CSaha (1 Reply)
Discussion started by: csaha
1 Replies
3. Shell Programming and Scripting
For executing a shell script, i know 2 ways:
1) using sh command
2) making the script file executable & then use ./
But i can across another way for executing the scripts... using ". ./"
I tried this way.. but i was able to understand the difference between "./" and ". ./"
I would be very... (2 Replies)
Discussion started by: abishekmag
2 Replies
4. UNIX for Dummies Questions & Answers
I've come stuck when I was making sure the hour of the day was not been two times so that the rest of the script could not be executed.
Seems simple enough.
I used the -a to join the two conditions together and it would run if the conditions was t/f ( it is only supposed to run if was t/t).... (3 Replies)
Discussion started by: spookyrtd99
3 Replies
5. UNIX for Advanced & Expert Users
Hi,
What's the difference in taking inputs from <stdin> and terminal.
When by default <stdin> points to terminal itself.
Thanks (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies
6. UNIX for Advanced & Expert Users
Hi,
what is the difference btwn s and S in setuid , access permissions.
I have to make to change the access permissions of a file to rwsr_xr_r
but if i type in 4655 it changes the file to rwSr_xr_r .
How can I make this change ?
Please suggest. (2 Replies)
Discussion started by: astha rais
2 Replies
7. Solaris
Hello Everybody
I would like to know any major difference between sudo & RBAC as I am bit familiar with RBAC but not with sudo (2 Replies)
Discussion started by: girish.batra
2 Replies
8. Solaris
what is the difference b/w sol9 and sol10 booting procedure?? Recently faced this question with HP...
Thiru (2 Replies)
Discussion started by: tirupathiraju_t
2 Replies
9. Shell Programming and Scripting
Hello All,
I was having a look on threads on the Forum about time calculation but didn't find exactly this issue.
For instance, if we have these 2 dates, begin & end :
20100430235830
20100501000200
Is there anyway, awk, ksh, perl to calculate the difference in sec and get for... (6 Replies)
Discussion started by: rany1
6 Replies
10. UNIX for Dummies Questions & Answers
Hi All,
Can anyone please help me understanding what the difference between the below two?
1. script.sh &
2. nohup script.sh & (2 Replies)
Discussion started by: Anupam_Halder
2 Replies
NPTL(7) Linux Programmer's Manual NPTL(7)
NAME
nptl - Native POSIX Threads Library
DESCRIPTION
NPTL (Native POSIX Threads Library) is the GNU C library POSIX threads implementation that is used on modern Linux systems.
NPTL and signals
NPTL makes internal use of the first two real-time signals (signal numbers 32 and 33). One of these signals is used to support thread can-
cellation and POSIX timers (see timer_create(2)); the other is used as part of a mechanism that ensures all threads in a process always
have the same UIDs and GIDs, as required by POSIX. These signals cannot be used in applications.
To prevent accidental use of these signals in applications, which might interfere with the operation of the NPTL implementation, various
glibc library functions and system call wrapper functions attempt to hide these signals from applications, as follows:
* SIGRTMIN is defined with the value 34 (rather than 32).
* The sigwaitinfo(2), sigtimedwait(2), and sigwait(3) interfaces silently ignore requests to wait for these two signals if they are speci-
fied in the signal set argument of these calls.
* The sigprocmask(2) and pthread_sigmask(3) interfaces silently ignore attempts to block these two signals.
* The sigaction(2), pthread_kill(3), and pthread_sigqueue(3) interfaces fail with the error EINVAL (indicating an invalid signal number)
if these signals are specified.
* sigfillset(3) does not include these two signals when it creates a full signal set.
NPTL and process credential changes
At the Linux kernel level, credentials (user and group IDs) are a per-thread attribute. However, POSIX requires that all of the POSIX
threads in a process have the same credentials. To accommodate this requirement, the NPTL implementation wraps all of the system calls
that change process credentials with functions that, in addition to invoking the underlying system call, arrange for all other threads in
the process to also change their credentials.
The implementation of each of these system calls involves the use of a real-time signal that is sent (using tgkill(2)) to each of the other
threads that must change its credentials. Before sending these signals, the thread that is changing credentials saves the new creden-
tial(s) and records the system call being employed in a global buffer. A signal handler in the receiving thread(s) fetches this informa-
tion and then uses the same system call to change its credentials.
Wrapper functions employing this technique are provided for setgid(2), setuid(2), setegid(2), seteuid(2), setregid(2), setreuid(2), setres-
gid(2), setresuid(2), and setgroups(2).
CONFORMING TO
For details of the conformance of NPTL to the POSIX standard, see pthreads(7).
NOTES
POSIX says that any thread in any process with access to the memory containing a process-shared (PTHREAD_PROCESS_SHARED) mutex can operate
on that mutex. However, on 64-bit x86 systems, the mutex definition for x86-64 is incompatible with the mutex definition for i386, meaning
that 32-bit and 64-bit binaries can't share mutexes on x86-64 systems.
SEE ALSO
credentials(7), pthreads(7), signal(7), standards(7)
Linux 2015-08-08 NPTL(7)