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.
BSDCan is in Ottawa, with tutorials June 11-12, 2025, talks June 13-14, 2025
Registration is open - https://www.bsdcan.org/2025/registration.html
Also see https://blog.bsdcan.org/2025/03/18/bsdcan-2025-talks-tutorials-and-registration/ for descriptions and tips
#bsdcan #conference #bsd #unix #development #freebsd #netbsd #openbsd #sysadmin #devops #freesoftware #libresoftware
The Unix Magic Poster in hi-res png:
https://github.com/drio/unixmagic/blob/main/static/ump.png
#unix
The Xerox PARC alumni who contribute to the Medley Interlisp project shared the buttons they collected at computing conferences in the 1980s and 1990s such as AAAI, IJCAI, SIGGRAPH.
The buttons are awesome and span a range of languages and systems such as Interlisp, Lisp Machines, Smalltalk, Unix, Modula-2, Mesa, Pilot, and more. Be sure to go through the whole thread.
https://groups.google.com/g/lispcore/c/ylsMetI3D0I/m/CtGXmMn3AQAJ
Hasit occured to you that #search is not free ?
No i dont mean the ads and attention you lose on internet
I mean even in real life , although the cost if similar
everyone has limited resources . esp time.
Your best bet is to be with the resourceful and thats how majority works and #politics is just about resources
After deadline its really important to close the file, accept the answer could not be found with available resources and move on the only problem is , even that requires one to search for alternatives so the loop continues
That pretty much what the #risk is about
And thats where
> do one thing well
Philosophy of #unix shines
#peertube #archive #lispyGopherClimate https://communitymedia.video/w/bHafNcgW9jDXM1kdmdsyRo
#unix #emacs #theUnixPhilosophy #lisp #interview
https://codeberg.org/ramin_hal9001/lisp-gopher-climate_chat-about-emacs show #git #notes
@sacha I guess the RSS is https://communitymedia.video/feeds/videos.xml?accountId=216498&token=8cb5dc2f-82e7-4d3f-ad2c-95457f46b631 and I am going to put all the years there including your interviews... eventually. Might need to add subtitled/post-ex-facto video content.
#listeningTo the indomitable Praise Then Darkness by (#music) DJ @northernlights on https://anonradio.net:8443/anonradio
before the #emacs & #unix lispy gopher climate interview with @ramin_hal9001 in an hour (0UTC Wednesday = Tuesday evening in the Americas and when-you're-asleep in Europe / #rightNow) @SDF
#emacs #unix Miscellaneous notes on reading @ramin_hal9001 https://tilde.town/~ramin_hal9001/articles/emacs-fulfills-the-unix-philosophy.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-01_emacs-is-an-app-platform.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-02_what-is-the-unix-philosophy.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-03_unix-is-lesser-fp.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-04_lisp-does-fp-better-than-bash.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-05_unix-and-lisp-history.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-06_rebutting-critiques.html
For starters, excellent early history showing that unix and lisp are not direct relatives.
One small note that occurs to me is that in Mashey and Kernighan '84, they point at unix's shell's success at stopping people more C. 1/?? (but two for my purposes here)
Decided to display the VAX-11/750 at the @revspace open day yesterday. All the hard work seems to have paid off, managed to get 18 hours of uptime out of it before shutting it down at the end of the day! #unix #retrocomputing #dec #vax11 #minicomputer #unixhistory #bsd
From Unix: A History and a Memoir by Brian Kernighan.
#KenThompson #Unix #BellLabs #Aviation #ComputerHistory #ComputingHistory #History
I chewed on the tasty food for thought of the blog series by Ramin Honary @ramin_hal9001 on how Emacs fulfills the Unix philosophy. If a Lisp system is extensible, customizable, and self-documenting by design I'd say it's an application platform, or pretty close.
https://tilde.town/~ramin_hal9001/articles/emacs-fulfills-the-unix-philosophy.html
Ramin, @sacha Sacha Chua, and @screwtape will elaborate on this in an upcoming episode of the Lispy Gopher show. Full context:
Registration is open for #bsdcan, program published - see the blog post at https://blog.bsdcan.org/2025/03/18/bsdcan-2025-talks-tutorials-and-registration/ for details, or go to https://bsdcan.org (direct to registration link: https://indico.bsdcan.org/event/5/registrations/8/) #bsd #unix #openbsd #freebsd #netbsd #development #devops #sysadmin #freesoftware #libresoftware
width colour
#glenda #9front #plan9 #art #linux #unix #propaganda #unix_surrealism
Doing some table generation in awk, and is there an easier way to do "all fields n to NF" than this?
function combine(combn, combs) {
for (; combn<=NF; ++combn) {
combs=combs "\t" $(combn)
}
return combs
}
I could use printf on the fragments, but the annoyance is that loop, instead of
(string-join (cddr fields) "\t")
or whatever.
#unix socket files are not automatically removed when the socket is closed. They need to be manually cleaned up when closing if this is desired by calling remove/ unlink with the filepath, but openssh does not do this. However, as I researched the subject further I came to the realisation that the "best practice" with unix sockets is to unlink right before binding to it
--sof
Exploiting #Unix File-System Races via Algorithmic Complexity Attacks
syscall-duration is the
time for the victim to perform one system call and
can be measured before beginning the attack. The
prepare command updates the file-system so that
fname points to the specified file, and performs
any other actions necessary to prepare for the next
race. If the attacker does not know k in advance,
the algorithm can loop until the victim exits
file:///home/xameer/Downloads/cai2009.pdf
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟮/𝟭𝟳 (Valuable News - 2025/02/17) available.
https://vermaden.wordpress.com/2025/02/17/valuable-news-2025-02-17/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
I’ve talked before about how I think NetBSD is “boring”, and that it’s among the highest forms of praise I can give tech as a sysadmin and architect. But I’ve never elaborated why that is. Boring tech is mature, not old https://rubenerd.com/boring-tech-is-mature-not-old/
TODAY is a good day to get that #bsdcan proposal submitted, if you are doing something interesting with #BSD based systems.
The proposal deadline is February 12, 2025, read up here: https://www.bsdcan.org/2025/papers.html and find the submission link!
The conference itself is
June 11-12 for tutorials
June 13-14 for talks, BOFs and sundry events
Looking forward to seeing you in #Ottawa! #openbsd #netbsd #freebsd #unix #development #networking #devops #sysadmin #experience #conference
Fresh from the @bsdcan program committee - submissions are coming in, but we can still take more!
If you have not made your submission, you have until Wednesday, February 12th to get yours in!
Go to https://www.bsdcan.org/2025/papers.html to orient yourself, then submit via the submission link.
BSDCan is in Ottawa, with tutorials June 11-12, 2025, talks June 13-14, 2025
#bsdcan #conference #bsd #unix #development #freebsd #netbsd #openbsd #sysadmin #devops #ottawa #canada
Happy Birthday Kenneth.L.Thompson!!
#UNIX #B #programming #language #computer #luminaries #inventor #creator #visionary #mastermind #brilliant
Classic Unix line-oriented text streams have what I’m going to call semantic locality. Consider as an example a #Unix password file. The semantic boundaries of the records in it – each one serializing a user’s name, numeric user ID, home directory, and various other information – correspond nicely to the syntactic boundary at each end of line.
Semantic locality means you can do a lot by looking at relatively small pieces (like line-at-a-time) using simple state machines or parsers. Well-designed data serializations tend to have this property even when they’re not textual, so you can do Unix-fu tricks on things like the binary packed protocol a uBlox GPS ships
Repository internals are different. A lot of the most important information – for example, the DAG structure of the history – is extremely de-localized; you have to do complicated and failure-prone operations on on an entire serialized dump of the repository (assuming you can get such a thing at all!) to recover it. You can’t do more than the very simplest transforms on the de-localized data without knowing a lot of fragile context.
http://esr.ibiblio.org/?p=7421
Bill Dyer's memories of the Coherent Unix clone.
At $99.95, in the early 1990s it was the first Unix I could afford and run on my laptop. It taught me a lot. It was a product from an era in which you could pay a one-time fee to buy and own good, packaged software that delivered real value and came with excellent printed documentation.
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟭/𝟮𝟳 (Valuable News - 2025/01/27) available.
https://vermaden.wordpress.com/2025/01/27/valuable-news-2025-01-27/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
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
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 #OpenBSD