linuxusers.in is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
When I run it from my default shell, zsh, I get this:
4 % ./segv
zsh: 13512 segmentation fault ./segv
When I run it from bash, I get what you noted in your question:
bediger@flq123:csrc % ./segv
Segmentation fault
#zsh #bash
#Unix signal mechanism is entirely different from the CPU-specific events that start the process.
In general, when a bad address is accessed (or written to a read-only area, attempt to execute a non-executable section, etc.), the CPU will generate some CPU-specific event (on traditional non-VM architectures this was called a segmentation violation, since each "segment" (traditionally, the read-only executable "text", the writable and variable-length "data", and the stack traditionally at the opposite end of memory) had a fixed range of addresses - on a modern architecture it's more likely to be a page fault [for unmapped memory] or an access violation [for read, write, and execute permission issues], and I'll focus on this for the rest of the answer).
Now, at this point, the kernel can do several things. Page faults are also generated for memory that is valid but not loaded (e.g. swapped out, or in a mmapped file, etc.), and in this case the kernel will map the memory and then restart the user program from the instruction that caused the error. Otherwise, it sends a signal. This doesn't exactly "direct [the original event] to the offending program", since the process for installing a signal handler is different and mostly architecture-independent, vs. if the program were expected to simulate installing an interrupt handler.
https://unix.stackexchange.com/questions/257598/how-does-a-segmentation-fault-work-under-the-hood
How #Unix Spell Ran in 64kB RAM
https://blog.codingconfessions.com/p/how-unix-spell-ran-in-64kb-ram
What operating systems do you use?
This includes on your PC/computer and mobile devices, or anywhere else for that matter. Select all that apply!
Please BOOST for maximum exposure to the #Fediverse
If your choice isn't listed, simply comment and let's discuss things!
#Poll #Polls #POTD #Question #Questions #QOTD #Windows #MacOS #Linux #Unix #ChromeOS #iOS #Android #Tech #Technology #AllThingsTech
Windows: | 343 |
Linux: | 617 |
MacOS: | 270 |
Unix: | 49 |
ChromeOS: | 39 |
iOS: | 262 |
Android: | 471 |
Other -> Comment below!: | 40 |
The rsync utility in Linux, *BSD, and Unix-like systems are vulnerable to multiple security issues, including arbitrary code execution, arbitrary file upload, information disclosure, and privilege escalation. Hence, you must patch the system ASAP https://www.cyberciti.biz/linux-news/cve-2024-12084-rsyn-security-urgent-update-needed-on-unix-bsd-systems/
OTD 1973: #UNIX seminar at Bell Labs. pdf: https://drive.google.com/file/d/1HAISQ_LTJTBRGtKbIsrsIAM54k8Zub22/view?usp=sharing
bash
after 20 plus years to oksh
to see how I get on with this ksh
variant. So far so good and I'm having to read the man page to get my self used to a slightly different way of doing things but this does feel nice and Unixy as I said earlier. Only time will tell if I switch back. 😉 #FreeBSD #Unix #Bash #KSH #OKSH #OpenBSDBash
since the beginning. I did look at #FreeBSD default sh
but it's history is a tad clunky. Yesterday I was introduced to oksh
a public domain Korn shell via a blog by @rubenerd@bsd.network and it does look interesting. I'd obviously continue writing my scripts to be posix compliant and running with sh
but for interactive use this might be more me ?oksh
AKA korn shell
.BSDCan 2025 Call for Papers is open, see https://www.bsdcan.org/2025/papers.html
Important dates
Submission deadline 2025-02-12
Accept notified by 2025-03-04
Tutorials 2025-06-11 - 2025-06-12
Conference 2025-06-13 - 2025-06-14
#bsdcan #freebsd #openbsd #netbsd #bsd #unix #conference #development #freesoftware #libresoftware
Plan 9 is a Unix-like operating system first developed by Bell Labs.
https://comp.os.plan9.narkive.com/SnexHy94/we-re-alive-again
"comp.os.plan9 is a moderated newsgroup for discussion of the Plan 9 operating system and related systems. It's a forum to ask questions and share information about installing, administering, using, and developing the system. Discussion of the original Plan 9 from Bell Labs as well as all forks, derivitives, or otherwise related systems are on topic. "
http://9srv.net/comp.os.plan9/index.html
My stock answer to all the oh-so-tired "how to exit vim(1)" schtick includes ref to https://nxdomain.no/~peter/ed_mastery_is_a_must_for_real_unix_person.html (alternatively https://bsdly.blogspot.com/2018/04/ed1-mastery-is-must-for-real-unix-person.html if you really don't mind being tracked) #vi #vim #howtoexitvim #ed #editors #standardeditor #unix #oldfart #greybeard
You're a #Unix / #Linux fan and looking for a simple and minimalistic #blog engine?
#manpageblog might be your solution and comes in a simple and familiar manpage design without big dependencies as a static blog generator.
You can find more about manpageblog right here: https://github.com/gyptazy/manpageblog
#opensource #alternatives #wordpress #blogging #python #sitegenerator #bsd #minimalism #minimalistic #fediverse #tech