This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
Link 13 is dead. 2003:C7:4F29:8A05:4ECC:6AFF:FE93:1F63 ( talk) 12:40, 16 September 2020 (UTC)
"A process's execution may result in the generation of a hardware exception, for instance, if the process attempts to divide by zero or incurs a TLB miss." Which architectures generate an exception on a TLB miss? x86 and x86_64 CPUs certainly don't (note: page fault != TLB miss). —Preceding unsigned comment added by 147.188.254.195 ( talk) 12:00, 14 October 2010 (UTC)
Currently there are quite a lot of pages created for single signal. Most of them are very short, have very little encyclopedic potential and contain duplicate material. I propose to merge them to this article, since it already contains a signal comparison table. Notable signals could have a separate section added, though I doubt this would be needed because most of the content already fails WP:NOTMANUAL.
The pages in question: SIGABRT, SIGALRM, SIGFPE, SIGHUP, SIGILL, SIGINT, SIGKILL, SIGPIPE, SIGQUIT, SIGSEGV, SIGTERM, SIGUSR1 and SIGUSR2, SIGUSR1 and SIGUSR2, SIGCHLD, SIGCONT, SIGSTOP, SIGTSTP, SIGTTIN, SIGTTOU, SIGBUS, SIGPOLL, SIGPROF, SIGSYS, SIGTRAP, SIGURG, SIGVTALRM, SIGXCPU, SIGXFSZ, SIGRTMIN and SIGRTMAX, SIGEMT, SIGSTKFLT, SIGINFO, SIGPWR, SIGLOST, SIGWINCH, SIGUNUSED
1exec1 ( talk) 14:08, 10 January 2012 (UTC)
It's useful that this page act as a category for each signal -- the details and contexts of which vary. I don't think the formatting consistency of individual signal pages is a strike against it ("almost duplicate across different articles"). And I'm not sure what "(they) have very little encyclopedic potential" means. 98.245.10.124 ( talk) 23:40, 14 January 2012 (UTC)
The comments opposing the merging in the above proposal haven't addressed my main concern about violations of Wikipedia guidelines WP:OR, WP:N and WP:NOT. A second discussion was started here, it seems that the consensus for the merge is unanimous. 1exec1 ( talk) 15:02, 6 October 2012 (UTC)
SIGWINCH became a POSIX signal in Oct 2017:
2601:14A:600:6420:F128:9801:9970:9A2A ( talk) 11:49, 12 October 2017 (UTC)
I placed a citation needed tag on this claim: Signals are similar to interrupts, the difference being that interrupts are mediated by the CPU and handled by the kernel while signals are mediated by the kernel (possibly via system calls) and handled by individual processes. A source is necessary because both the claim and the reasoning are vague . My research indicates that signals are the UNIX implementation of interrupts, not just similar to interrupts. For example, the textbook The Design of the UNIX Operating System by Bach (1986; pages 200-201) classifies signals into 7 categories. The categories are when a process finishes normally, when a process has an error exception, when a process runs out of a system resource, when a process executes an illegal instruction, when a process sets an alarm event, when a process is aborted from the keyboard, and when a process has tracing alerts for debugging. Every category generates an interrupt. Timhowardriley ( talk) 20:28, 10 May 2022 (UTC)
This article was the subject of an educational assignment supported by Wikipedia Ambassadors through the India Education Program.
The above message was substituted from {{IEP assignment}}
by
PrimeBOT (
talk) on 19:58, 1 February 2023 (UTC)
This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
Link 13 is dead. 2003:C7:4F29:8A05:4ECC:6AFF:FE93:1F63 ( talk) 12:40, 16 September 2020 (UTC)
"A process's execution may result in the generation of a hardware exception, for instance, if the process attempts to divide by zero or incurs a TLB miss." Which architectures generate an exception on a TLB miss? x86 and x86_64 CPUs certainly don't (note: page fault != TLB miss). —Preceding unsigned comment added by 147.188.254.195 ( talk) 12:00, 14 October 2010 (UTC)
Currently there are quite a lot of pages created for single signal. Most of them are very short, have very little encyclopedic potential and contain duplicate material. I propose to merge them to this article, since it already contains a signal comparison table. Notable signals could have a separate section added, though I doubt this would be needed because most of the content already fails WP:NOTMANUAL.
The pages in question: SIGABRT, SIGALRM, SIGFPE, SIGHUP, SIGILL, SIGINT, SIGKILL, SIGPIPE, SIGQUIT, SIGSEGV, SIGTERM, SIGUSR1 and SIGUSR2, SIGUSR1 and SIGUSR2, SIGCHLD, SIGCONT, SIGSTOP, SIGTSTP, SIGTTIN, SIGTTOU, SIGBUS, SIGPOLL, SIGPROF, SIGSYS, SIGTRAP, SIGURG, SIGVTALRM, SIGXCPU, SIGXFSZ, SIGRTMIN and SIGRTMAX, SIGEMT, SIGSTKFLT, SIGINFO, SIGPWR, SIGLOST, SIGWINCH, SIGUNUSED
1exec1 ( talk) 14:08, 10 January 2012 (UTC)
It's useful that this page act as a category for each signal -- the details and contexts of which vary. I don't think the formatting consistency of individual signal pages is a strike against it ("almost duplicate across different articles"). And I'm not sure what "(they) have very little encyclopedic potential" means. 98.245.10.124 ( talk) 23:40, 14 January 2012 (UTC)
The comments opposing the merging in the above proposal haven't addressed my main concern about violations of Wikipedia guidelines WP:OR, WP:N and WP:NOT. A second discussion was started here, it seems that the consensus for the merge is unanimous. 1exec1 ( talk) 15:02, 6 October 2012 (UTC)
SIGWINCH became a POSIX signal in Oct 2017:
2601:14A:600:6420:F128:9801:9970:9A2A ( talk) 11:49, 12 October 2017 (UTC)
I placed a citation needed tag on this claim: Signals are similar to interrupts, the difference being that interrupts are mediated by the CPU and handled by the kernel while signals are mediated by the kernel (possibly via system calls) and handled by individual processes. A source is necessary because both the claim and the reasoning are vague . My research indicates that signals are the UNIX implementation of interrupts, not just similar to interrupts. For example, the textbook The Design of the UNIX Operating System by Bach (1986; pages 200-201) classifies signals into 7 categories. The categories are when a process finishes normally, when a process has an error exception, when a process runs out of a system resource, when a process executes an illegal instruction, when a process sets an alarm event, when a process is aborted from the keyboard, and when a process has tracing alerts for debugging. Every category generates an interrupt. Timhowardriley ( talk) 20:28, 10 May 2022 (UTC)
This article was the subject of an educational assignment supported by Wikipedia Ambassadors through the India Education Program.
The above message was substituted from {{IEP assignment}}
by
PrimeBOT (
talk) on 19:58, 1 February 2023 (UTC)