News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by fred256 on Thursday June 18, 2020 @10:48AM (#23563564)
It's interesting to see all signal names in that early version had six letters (SIGQIT instead of SIGQUIT, even) but SIGPIPE was the exception. Was that one added later?

(Also funny how the article says "this is from around 1978" when the date on the listing says May 24 1976)

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by adrianmonk on Thursday June 18, 2020 @11:09AM (#23563765)
I don't know the real answer, but I've always assumed it's because there's no way to get the right "I" vowel sound without that trailing "E".

Also, when creating abbreviations, it feels weird to create one that is only one letter shorter than the full version.

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by cesarb on Thursday June 18, 2020 @01:21PM (#23565308)
> Also, when creating abbreviations, it feels weird to create one that is only one letter shorter than the full version.

This is Unix, which gave us the "creat" system call (an abbreviation of "create"). https://man7.org/linux/man-pages/man2/creat.2.html

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by rkeene2 on Thursday June 18, 2020 @10:56PM (#23570520)
If it makes you feel any better, the creators of UNIX regrets this.

> Ken Thompson was once asked what he would do differently if he were redesigning the UNIX system. His reply: "I'd spell creat with an e."; Kernighan, Brian W.; Pike, Rob (1984). The UNIX programming environment. Prentice-Hall. ISBN 0139376992. OCLC 10269821., p. 204.

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by coldcat on Saturday June 20, 2020 @12:47PM (#23584908)
The C linker of those years only support function names up to 6 characters. That's maybe why the defines try to match their respective function name in 6 char.