Helvede

jbz｢ Solaris 2.1 for x86, also known as SunOS 5.1, was Sun’s first entry into the PC market (technically it was SunSoft, a subsidiary of Sun Microsystems, who released Solaris). However, it wasn’t Sun’s first x86 operating system. In the late 1980s, Sun sold 386i workstations based on Intel 386 processors. The 386i workstations were not PC compatible and ran SunOS 4.0, a BSD UNIX derivative with many custom Sun enhancements ｣<a href="https://www.os2museum.com/wp/pc-unix-history/solaris-2-1-for-x86/" rel="nofollow noopener" translate="no" target="_blank">https://www.os2museum.com/wp/pc-unix-history/solaris-2-1-for-x86/</a><a href="https://indieweb.social/tags/solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#solaris</a> <a href="https://indieweb.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://indieweb.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: time(3) is an illusionHaving revisited the atime, mtime, and time in our last video segment, we now have to come to terms with time(3) itself. We'll discuss managing the data structures and handling arbitrary concepts such as leap seconds, timezones, and (ugh) Daylight Savings Time. It gets silly real quick.<a href="https://youtu.be/3N2aH1vUacQ" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/3N2aH1vUacQ</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Alfonso Siciliano<a href="https://mastodon.bsd.cafe/tags/FAQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#FAQ</a>: “What do you do with <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> ?" "Operating in the financial markets" 😀 <a href="https://mastodon.bsd.cafe/tags/ThePowerToInvest" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThePowerToInvest</a> 😆 <a href="https://mastodon.bsd.cafe/tags/Investing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Investing</a> 📊 <a href="https://mastodon.bsd.cafe/tags/Trading" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trading</a> 📈 <a href="https://mastodon.bsd.cafe/tags/Stocks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stocks</a> 📉 <a href="https://mastodon.bsd.cafe/tags/ETFs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ETFs</a> <a href="https://mastodon.bsd.cafe/tags/Bonds" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bonds</a> <a href="https://mastodon.bsd.cafe/tags/Commodities" class="mention hashtag" rel="nofollow noopener" target="_blank">#Commodities</a> <a href="https://mastodon.bsd.cafe/tags/Derivatives" class="mention hashtag" rel="nofollow noopener" target="_blank">#Derivatives</a> <a href="https://mastodon.bsd.cafe/tags/Forex" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forex</a> 💹 <a href="https://mastodon.bsd.cafe/tags/Crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Crypto</a> 🪙 <a href="https://mastodon.bsd.cafe/tags/NASDAQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#NASDAQ</a> <a href="https://mastodon.bsd.cafe/tags/SP500" class="mention hashtag" rel="nofollow noopener" target="_blank">#SP500</a> <a href="https://mastodon.bsd.cafe/tags/DOWJONES" class="mention hashtag" rel="nofollow noopener" target="_blank">#DOWJONES</a> <a href="https://mastodon.bsd.cafe/tags/WallStreet" class="mention hashtag" rel="nofollow noopener" target="_blank">#WallStreet</a> 🗽 <a href="https://mastodon.bsd.cafe/tags/Bull" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bull</a> 🐂 <a href="https://mastodon.bsd.cafe/tags/Bear" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bear</a> 🐻 <a href="https://mastodon.bsd.cafe/tags/TechFinance" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechFinance</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> :freebsd: <a href="https://mastodon.bsd.cafe/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Alfonso SicilianoWelcome <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> 16.0 on my laptop! Smooth, fast, and running perfectly with Xfce.FreeBSD <a href="https://mastodon.bsd.cafe/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD16" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD16</a> <a href="https://mastodon.bsd.cafe/tags/Xfce" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xfce</a> <a href="https://mastodon.bsd.cafe/tags/DesktopUnix" class="mention hashtag" rel="nofollow noopener" target="_blank">#DesktopUnix</a> <a href="https://mastodon.bsd.cafe/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSDCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSDCommunity</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSDLaptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSDLaptop</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: atime, mtime, ctimeIn this video lecture, we start looking a little bit closer into what our systems think of "time", something that experts most accurately describe as a big ball of wibbly, wobbly, timey, wimey... stuff. In short, analyze how the atime, mtime, and ctimes of a file connect.<a href="https://youtu.be/ffYEEj5vnlw" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/ffYEEj5vnlw</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

derSammlerInstalling <a href="https://oldbytes.space/tags/Tru64" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tru64</a> <a href="https://oldbytes.space/tags/UNIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UNIX</a> 5.1B on the <a href="https://oldbytes.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> <a href="https://oldbytes.space/tags/AlphaServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlphaServer</a> DS15. Quite clunky...<a href="https://oldbytes.space/tags/DEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#DEC</a> <a href="https://oldbytes.space/tags/digital" class="mention hashtag" rel="nofollow noopener" target="_blank">#digital</a> <a href="https://oldbytes.space/tags/AXP" class="mention hashtag" rel="nofollow noopener" target="_blank">#AXP</a> <a href="https://oldbytes.space/tags/Alpha" class="mention hashtag" rel="nofollow noopener" target="_blank">#Alpha</a> <a href="https://oldbytes.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a>

Torstein Krause JohansenYes! Meta based Emacs shortcuts now work in my Kitty terminals, thanks to these lines in ~/.config/kitty/kitty.conf. Have been missing these shortcuts in ZSH and "emacs -nw" alike, since moving from Linux.map cmd+x send_text all \x1bx map cmd+f send_text all \x1bf map cmd+b send_text all \x1bb map cmd+w send_text all \x1bw map cmd+backspace send_text all \x1b\x7f<a href="https://hachyderm.io/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://hachyderm.io/tags/kitty" class="mention hashtag" rel="nofollow noopener" target="_blank">#kitty</a> <a href="https://hachyderm.io/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://hachyderm.io/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#macos</a>

KornebluFriends, I'm looking for contracts in HealthCare IT (20+ yrs in this domain, 40+ yrs in IT). Done two <a href="https://mastodon.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> clinical data repository. Now on federated clinical data analytics. Expert in <a href="https://mastodon.social/tags/openEHR" class="mention hashtag" rel="nofollow noopener" target="_blank">#openEHR</a>, <a href="https://mastodon.social/tags/FHIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#FHIR</a>, <a href="https://mastodon.social/tags/SNOMED" class="mention hashtag" rel="nofollow noopener" target="_blank">#SNOMED</a>-CT, PACS, MPI, <a href="https://mastodon.social/tags/Kotlin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kotlin</a>, <a href="https://mastodon.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a>, <a href="https://mastodon.social/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>, DB: <a href="https://mastodon.social/tags/SQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQL</a> (<a href="https://mastodon.social/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#PostgreSQL</a>!), <a href="https://mastodon.social/tags/jOOQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#jOOQ</a>, <a href="https://mastodon.social/tags/distributedSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributedSQL</a>, <a href="https://mastodon.social/tags/KnowledgeGraph" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnowledgeGraph</a>, APIs, <a href="https://mastodon.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a>, <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>, <a href="https://mastodon.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a>... Very keen on medical projects benefiting rural and/or developing communities. Also looking for tutoring, compliance, security and SOPs. TIA!

Martin BishopComputerworld wrote in June 1993, “it was <a href="https://mastodon.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> workstations and object-oriented software programs that helped breathe life into the dinosaurs". Industrial Light & Magic (ILM) used <a href="https://mastodon.social/tags/SGI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SGI</a> workstations running software such as Softimage, along with proprietary <a href="https://mastodon.social/tags/ILM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ILM</a> tools, to create the film’s groundbreaking computer-generated dinosaur effects. Via unix_byte <a href="http://www.sgistuff.net/hardware/systems/crimson.html" rel="nofollow noopener" translate="no" target="_blank">http://www.sgistuff.net/hardware/systems/crimson.html</a><a href="http://www.sgidepot.co.uk/crimson.html" rel="nofollow noopener" translate="no" target="_blank">http://www.sgidepot.co.uk/crimson.html</a>

Martin BishopAt the same time, he proudly noted, “I banned PowerPoint from my company and we've had the best two quarters we've ever had in the history of the company”. McNealy’s outspoken critique of <a href="https://mastodon.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a>, combined with Sun’s promotion of Java and network computing, arguably opened the door for alternatives, helping <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> and <a href="https://mastodon.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> variants gain traction in the server and workstation markets

Martin BishopIn a 1997 interview with BYTE, Scott McNealy, then CEO of Sun Microsystems, arguably the most renowned <a href="https://mastodon.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> company of the time, spoke disparagingly about Unix, remarking, “The problem with Unix is that nobody protected the brand to mean something and the brand lost value”. Continue in next comment. Via @unix_byte

vermadenLatest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟭𝟬/𝟬𝟲 (Valuable News - 2025/10/06) available. <a href="https://vermaden.wordpress.com/2025/10/06/valuable-news-2025-10-06/" rel="nofollow noopener" translate="no" target="_blank">https://vermaden.wordpress.com/2025/10/06/valuable-news-2025-10-06/</a>Past releases: <a href="https://vermaden.wordpress.com/news/" rel="nofollow noopener" translate="no" target="_blank">https://vermaden.wordpress.com/news/</a><a href="https://mastodon.bsd.cafe/tags/verblog" class="mention hashtag" rel="nofollow noopener" target="_blank">#verblog</a> <a href="https://mastodon.bsd.cafe/tags/vernews" class="mention hashtag" rel="nofollow noopener" target="_blank">#vernews</a> <a href="https://mastodon.bsd.cafe/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a> <a href="https://mastodon.bsd.cafe/tags/bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#bsd</a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> <a href="https://mastodon.bsd.cafe/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> <a href="https://mastodon.bsd.cafe/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> <a href="https://mastodon.bsd.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.bsd.cafe/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> <a href="https://mastodon.bsd.cafe/tags/opnsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#opnsense</a> <a href="https://mastodon.bsd.cafe/tags/ghostbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#ghostbsd</a> <a href="https://mastodon.bsd.cafe/tags/solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#solaris</a> <a href="https://mastodon.bsd.cafe/tags/vermadenday" class="mention hashtag" rel="nofollow noopener" target="_blank">#vermadenday</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: getpwuid(2) and /etc/groupsIn this video lecture, we look at the library functions used to look up account information. We learn about how primary and supplementary groups are handled as well as how the hashed passwords are stored outside of the world readable /etc/passwd file.<a href="https://youtu.be/aomkx6_aWpc" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/aomkx6_aWpc</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: /etc/passwdIn this short video, we try to answer the awkward question "Mommy, where do UIDs come from?". We look at the /etc/passwd user database and identify the various fields before we look at how things can get weird.<a href="https://youtu.be/fv16TWDnLYM" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/fv16TWDnLYM</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Jamie in Cuckooland@<a href="https://fosstodon.org/@demiguru" rel="nofollow noopener" target="_blank">Zach  🇮🇱 🇺🇸</a> To continue from where I left off, the pure Unix conception didn't envisage dynamic languages and scriptability and explicitly eshewed large programs.  The utility of (some) dynamism was realised early, but corrected in hamstrung sort of ways — especially from a Lisp perspective,  but anyone can see the limitations of shell scripting languages. And the 'small programs' in practice has not played out either.  X isn't small, vim isn't small (not by trad Unix standards - it's similar order of magnitude to emacs in fact), webbrowser aren't small...   The other side of the equation is that the Lisp (esp. in the form of Lisp Machines)/Smalltalk world supposed that you would live entirely within the environment and everything would be written in the one language.  The notion of interoperating with anything outside this was alien and resisted.  It was some years, I believe, before a C compiler became available for Lisp Machines. Emacs transcends all of this.  It participates in the Unix world just fine.  If you want to load, edit something, and exit, you can do that (if it's running in the background as a server, this is plenty fast, too, as you're just executing emacsclient).  If you want to use it as a filter on the command line, it can do that too, as has been demonstrated. And the unix world is also available from within emacs.  You can filter or send any block of text through external commands, it has wrappers for classic unix tools like grep, also modes for interacting with shells, terminal emulators, and its own shell from which you can run both elisp functions and unix commands together. (And, of course, it's great at handling Unix's common data format: text.) Moreover, org-mode has a great multilingual environment where you run source code in numerous languages and even pass data between them with ease.   This is all completely the opposite of the Lisp Machine/Smalltalk notion of an isolated world.  It's more in line with the Unix shell, which doesn't care what your programs are written, except better. So I think we can say it transcends the two purisms.  It does this by rejecting the 'small specialized program' dictum (which I don't think is important and I'd argue has been effectively rejected by all but the most purist Unix-heads), and centering itself in place of a unix shell (without demanding this) but keeping to the spirit of all the other ideas.   And on the other hand, also rejecting Lisp Machine solipsism. (I haven't really thought of this in quite this way before so thanks for the discussion, in particular @<a href="https://piaille.fr/@Zenie" rel="nofollow noopener" target="_blank">Zenie</a> who pushed the idea that emacs is actually better at what's important about unix than unix is, and @<a href="https://social.linux.pizza/@restorante" rel="nofollow noopener" target="_blank">restorante</a> and @<a href="https://ieji.de/@eruwero" rel="nofollow noopener" target="_blank">eruwero</a>'s demonstration of emacs as a unix command line tool) #<a class="" href="https://zotum.net/search?tag=emacs" rel="nofollow noopener" target="_blank">emacs</a> #<a class="" href="https://zotum.net/search?tag=lisp" rel="nofollow noopener" target="_blank">lisp</a> #<a class="" href="https://zotum.net/search?tag=unix" rel="nofollow noopener" target="_blank">unix</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: Directory SizeIn this video lecture, we dive deep into the structure of the directory on a traditional Unix File System and see how its size is independent of the file sizes of its entries, but dependent on the filename lengths. We'll also use hexdump(1) to cheat a bit and look at the directory structure on disk.<a href="https://youtu.be/gY0SE-71LZA" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/gY0SE-71LZA</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Jamie in Cuckooland@<a href="https://fosstodon.org/@demiguru" rel="nofollow noopener" target="_blank">Zach  🇮🇱 🇺🇸</a> I think you're basically correct to point out that Emacs does not adhere to the unix philosophy as it is classically understood. The locus classicus is presumably the widely quoted McIlroy et. al. in the 'Unix Time-Sharing System" where Emacs clearly violates the first maxim: <blockquote>Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new "features."</blockquote> Or to take a later articulation, Gancarz in Linux and the Unix Philosophy's first two tenets: 'Small is Beautiful', 'Each Program Does One Thing Well'  — again Emacs is the opposite of this. (This kind of thing comes up constantly in every mention of the Unix philosophy that I've ever seen until this conversation and is easily verified by simply searching.  It's strange to see people insisting that there is simply no emphasis on small, special purpose programs. Of course one can decide that principle isn't important, but let's not ignore that it was (and I believe usually still is) considered to be so) We can also note that in the original incarnation of Unix ('Research Unix') there was nothing remotely like emacs and there was, as far as I know, very little scriptability.  The Thompson shell allowed for piping but not scripting.  OG unix is everything is written in C, with a simple interactive shell and if you want anything else it's back to C programming. Whereas Emacs does (as you say) have more in common with the Lisp ethos, where there aren't separate programs per se and everything is a function in one giant Lisp environment (same is true of Smalltalk) — although there are differences there, too which I might get on to later. I think it pays to note that these views are informed by very different language traditions.  C is a static language with an explicit and slow compilation step.  Lisp on the other hand has always been a dynamic language where you can just throw a new function into your environment pretty much immediately, usually without having to (explicitly) compile or restart anything. If you think about it a bit you might start to see that if all you've got is C, small programs that don't keep their own state but write to text files may be the simplest option for getting any composibility, particularly on limited machines. However, I think we can fairly say that Unix found that only having a statically compiled language available was far too limiting and early on started haltingly down a path to acquiring dynamic programming abilities, starting with scriptable shells, and later larger programs with their own scripting languages. People often cite the Unix philosophy as though it's obviously the right way to program.  Modularity, clear interfaces, and composibilty we all think are good things, of course.  But why is 'one program does one thing' better - or even equal to - 'one function does one thing'? #<a class="" href="https://zotum.net/search?tag=emacs" rel="nofollow noopener" target="_blank">emacs</a> #<a class="" href="https://zotum.net/search?tag=lisp" rel="nofollow noopener" target="_blank">lisp</a> #<a class="" href="https://zotum.net/search?tag=unix" rel="nofollow noopener" target="_blank">unix</a>

LobstersGhosts of Unix Past: a historical search for design patterns (2010) <a href="https://lobste.rs/s/dsk4xn" rel="nofollow noopener" translate="no" target="_blank">https://lobste.rs/s/dsk4xn</a> <a href="https://mastodon.social/tags/historical" class="mention hashtag" rel="nofollow noopener" target="_blank">#historical</a> <a href="https://mastodon.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://lwn.net/Articles/411845/" rel="nofollow noopener" translate="no" target="_blank">https://lwn.net/Articles/411845/</a>

Jan SchaumannAdvanced Programming in the UNIX EnvironmentWeek 4: DirectoriesIn this video lecture, we take a look at how directories are created and removed, as well as how to move around the filesystem hierarchy. We also learn why the 'cd' command must be a shell builtin in order to work.<a href="https://youtu.be/xZ7dNXZ58G8" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/xZ7dNXZ58G8</a><a href="https://mstdn.social/tags/apue" class="mention hashtag" rel="nofollow noopener" target="_blank">#apue</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Martin BishopLayers was AT&T’s proprietary windowing system, shipped with the <a href="https://mastodon.social/tags/UNIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UNIX</a> PC (PC 7300), predating the widespread adoption of X11. Layers acted like a graphical multiplexer—a distant ancestor of tmux or screen—but ran directly on a bitmap display with rudimentary window management. Via @Unix_byte

Recent searches

Search options

Administered by:

Server stats:

#unix