86open https://lobste.rs/s/oqc2sn #historical #unix
https://en.wikipedia.org/wiki/Executable_and_Linkable_Format#86open
#unix
242 posts · Last used 3d
Replying to
Advanced Programming in the #UNIX Environment
Week 7: Reentrant and Interrupted Functions
With this video lecture, we will conclude our coverage of Unix signals, by looking at what happens when we call unsafe functions from within the signal handler as well as what happens when we are interrupted while blocking on certain I/O.
Advanced Programming in the UNIX Environment: Week 07, Segment 5 - Reentrant & interrupted functions
Replying to
Advanced Programming in the #UNIX Environment
Week 8: Interprocess Communications Intro
In this short video lecture, we begin our discussion of Interprocess Communication (IPC). We provide a quick overview of the different properties of IPC mechanisms as well as which mechanisms we will cover in future videos.
Advanced Programming in the UNIX Environment: Week 08, Segment 1 - Interprocess Communication Intro
Replying to
Advanced Programming in the #UNIX Environment
Week 8: System V IPC
In this video lecture, we cover traditional System V IPC: semaphores, shared memory, and message queues (with a quick look at the POSIX message queues implementation). We can then translate those concepts to modern, distributed "message-oriented middleware" such as Apache Kafka, Amazon SQS, or Redis.
Advanced Programming in the UNIX Environment: Week 08, Segment 2 - System V IPC
Boosted by @oxy@social.bsdlab.au
Replying to
Advanced Programming in the #UNIX Environment
Week 8: Pipes and FIFOs
With this video lecture, we continue our discussion of Interprocess Communication and dive into two of the oldest and most ubiquitous forms of Unix IPC: pipes and FIFOs. We also discuss popen(3) and the dangers of shelling out to unverified commands, a persistent cause of vulnerabilities in any number of tech stacks. (shquote(3) can help.)
Advanced Programming in the UNIX Environment: Week 08, Segment 3 - Pipes and FIFOs
groff/troff macros: ms, mm, me or mom https://lobste.rs/s/dbwbvr #unix
https://www.stephenlindholm.com/groff_macros.html
Don't summon the dark forces—just run NetBSD! Portable, clean, and reliable enough to wake the dead (or at least that 20-year-old ThinkPad in your closet). 💻🚩
Happy Halloween to all the BSD daemons out there! 😈🎃
What’s the weirdest hardware you’ve resurrected with NetBSD? 🧙♂️
#NetBSD #Unix #Halloween #RetroComputing #OpenSource #RunBSD #Linux #noai #nollm #noslop
Boosted by @fedicat@pc.cafe
#lispyGopherClimate #live on #peertube again !
https://toobnix.org/w/ogFTHRwVNXm4GXmkNyqg58
#archive Thanks all
Joined by @kentpitman@climatejustice.social and @jhlagado@defcon.social ( @ramin_hal9001@fe.disroot.org had a meeting )
Viz the #climateCrisis I am hoping to talk about the #debian #llm thing viz @cwebber@social.coop https://gamerplus.org/@cwebber@social.coop/117508713815802595
the wonderful @nosrednayduj@hachyderm.io clued me into #symbolics #lisp discussions and the paper on failure https://www.chai.uni-hamburg.de/~moeller/symbolics-info/Symbolics.pdf
ALSO our @dougmerritt@mathstodon.xyz and #unix and #gamedev and #softwareArchaeology
Chat in #lambdaMOO #VR as always!
An Evening with Berferd: In Which a Cracker is Lured, Endured, and Studied (1992) https://lobste.rs/s/7bbzjf #pdf #security #unix
https://www.cheswick.com/ches/papers/berferd.pdf
I like finding and fixing bugs in 52-year-old software, especially when all later versions retain the bug.
#unix #vintagecomputing #retrocomputing
Replying to
Whew! I just finished porting 2,852 lines of PDP-11 assembly to C by hand over the past week!
This is for form/fed, a form letter editor and generator with template substitutions, introduced in 1971. It's the largest UNIX utility that was never ported to C, and has since been forgotten.
1/6
#unix #retrocomputing #vintagecomputing #reverseengineering
Replying to
Most notably, the oldest list of UNIX licensees was produced from a form letter database.
Ken Thompson used form/fed to simplify mailing to early users: rather than hand- or typewriting messages, this fancy tool would substitute each recipient and the date. In 1975, when UNIX News was starting up, he used this form letter database to dump the list of contacts that served as the initial subscriber list.
The circumstances of the UNIX V4 tape found at the University of Utah are still somewhat unclear, as it was apparently not used for research and only sparse traces of its acquisition survived. But some letters to Martin Newell are in that form letter database and I hope to recover more information through forensic analysis.
2/6
#unix #retrocomputing #vintagecomputing
Boosted by @oxy@social.bsdlab.au
Replying to
You've heard of Y2K and the 2038 problem, but what about the 1975 problem?
The UNIX form letter generator converts the current date to a string, but it only handles 1974. Why isn't it more general?
Well, the form utility was written around 1971 when UNIX used a different unit for time, jiffies (60ths of a second) since the current year instead of seconds since 1970. This 60× precision caused times to overflow a signed 32-bit integer every 13.6 months, so the epoch was bumped yearly. This yearly ritual of modifying the kernel meant it wasn't worth generalizing to support any year.
An earlier version of form uses jiffies since a 1972 epoch. The version from UNIX V4–V6 does the bare minimum to update it to the new system of seconds since 1970, while keeping the yearly overflow.
#unix #retrocomputing #vintagecomputing
Boosted by @oxy@social.bsdlab.au
"Tianve" - Dell Latitude e6540 Notebook
- Operating System: OpenBSD 8.0 amd64
- Desktop: LXQt 2.4.0
- Windowmanager: XFWM4
- Qt Version: 6.11.2
- Graphics Platform: X11/xenocara
[1] https://bsd-hardware.info/?computer=887d42919aeb
#runbsd #openbsd #fishlinux #unix #foss #lxqt #desktop #screenshot #shareyourdesktop









