Fosstodon

:rss: Hacker NewsClassic Computer Replicas <a href="https://obsolescence.dev/index.html" rel="nofollow noopener" translate="no" target="_blank">https://obsolescence.dev/index.html</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PDP_8" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDP_8</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PDP_11" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDP_11</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PDP_10" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDP_10</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PiDP_8" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiDP_8</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PiDP_11" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiDP_11</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PiDP_10" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiDP_10</a>

:rss: Hacker NewsBuilding the System/360 Mainframe Nearly Destroyed IBM <a href="https://spectrum.ieee.org/building-the-system360-mainframe-nearly-destroyed-ibm" rel="nofollow noopener" translate="no" target="_blank">https://spectrum.ieee.org/building-the-system360-mainframe-nearly-destroyed-ibm</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/silicon_revolution" class="mention hashtag" rel="nofollow noopener" target="_blank">#silicon_revolution</a> <a href="https://rss-mstdn.studiofreesia.com/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardware</a> <a href="https://rss-mstdn.studiofreesia.com/tags/type_feature" class="mention hashtag" rel="nofollow noopener" target="_blank">#type_feature</a> <a href="https://rss-mstdn.studiofreesia.com/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ibm" class="mention hashtag" rel="nofollow noopener" target="_blank">#ibm</a> <a href="https://rss-mstdn.studiofreesia.com/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ibm_system_360" class="mention hashtag" rel="nofollow noopener" target="_blank">#ibm_system_360</a> <a href="https://rss-mstdn.studiofreesia.com/tags/mainframe" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainframe</a>

ivanfrEvento próximo y con registro gratuito. Las anteriores ediciones han sido realmente enriquecedorasSee You there if interest <a href="https://mastodon.uno/tags/phil" class="mention hashtag" rel="nofollow noopener" target="_blank">#phil</a> <a href="https://mastodon.uno/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mastodon.uno/tags/philsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#philsci</a> <a href="https://mastodon.uno/tags/compBio" class="mention hashtag" rel="nofollow noopener" target="_blank">#compBio</a> <a href="https://mastodon.uno/tags/computerscience" class="mention hashtag" rel="nofollow noopener" target="_blank">#computerscience</a> <a href="https://mastodon.uno/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://mastodon.uno/tags/hist" class="mention hashtag" rel="nofollow noopener" target="_blank">#hist</a> <a href="https://mastodon.uno/tags/history" class="mention hashtag" rel="nofollow noopener" target="_blank">#history</a> <a href="https://mastodon.uno/tags/histsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#histsci</a> <a href="https://mastodon.uno/tags/philosophy" class="mention hashtag" rel="nofollow noopener" target="_blank">#philosophy</a> <a href="https://mastodon.uno/tags/biol" class="mention hashtag" rel="nofollow noopener" target="_blank">#biol</a> <a href="https://mastodon.uno/tags/biology" class="mention hashtag" rel="nofollow noopener" target="_blank">#biology</a> <a href="https://mastodon.uno/tags/cogsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#cogsci</a> <a href="https://mastodon.uno/tags/cognitivescience" class="mention hashtag" rel="nofollow noopener" target="_blank">#cognitivescience</a> <a href="https://mastodon.uno/tags/mind" class="mention hashtag" rel="nofollow noopener" target="_blank">#mind</a> <a href="https://mastodon.uno/tags/mindscience" class="mention hashtag" rel="nofollow noopener" target="_blank">#mindscience</a>

Matt PotterHundreds injured by booby-trapped pagers exploding in Lebanon in the hands of Hezbollah targets. This is not an operation that happens without a huge web of collaborators being involved.My 2023 book 'We Are All Targets' covers the moment the CIA, IBM & Yugoslav tech firms teamed up to make the USSR's computers explode simultaneously.<a href="https://c.im/tags/lebanon" class="mention hashtag" rel="nofollow noopener" target="_blank">#lebanon</a> <a href="https://c.im/tags/hezbollah" class="mention hashtag" rel="nofollow noopener" target="_blank">#hezbollah</a> <a href="https://c.im/tags/espionage" class="mention hashtag" rel="nofollow noopener" target="_blank">#espionage</a> <a href="https://c.im/tags/cyberwar" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberwar</a> <a href="https://c.im/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://c.im/tags/wearealltargets" class="mention hashtag" rel="nofollow noopener" target="_blank">#wearealltargets</a> <a href="https://c.im/tags/middleeast" class="mention hashtag" rel="nofollow noopener" target="_blank">#middleeast</a> <a href="https://c.im/tags/history" class="mention hashtag" rel="nofollow noopener" target="_blank">#history</a> <a href="https://c.im/tags/books" class="mention hashtag" rel="nofollow noopener" target="_blank">#books</a> <a href="https://c.im/tags/nonfiction" class="mention hashtag" rel="nofollow noopener" target="_blank">#nonfiction</a> <a href="https://c.im/tags/cia" class="mention hashtag" rel="nofollow noopener" target="_blank">#cia</a> <a href="https://c.im/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://c.im/tags/coldwar" class="mention hashtag" rel="nofollow noopener" target="_blank">#coldwar</a>

:rss: Hacker NewsK340A: The Brain Computer of Chernobyl Duga Radar [video] <a href="https://www.youtube.com/watch?v=kHiCHRB-RlA" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=kHiCHRB-RlA</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/chernobyl" class="mention hashtag" rel="nofollow noopener" target="_blank">#chernobyl</a> <a href="https://rss-mstdn.studiofreesia.com/tags/chornobyl" class="mention hashtag" rel="nofollow noopener" target="_blank">#chornobyl</a> <a href="https://rss-mstdn.studiofreesia.com/tags/russian_woodpecker" class="mention hashtag" rel="nofollow noopener" target="_blank">#russian_woodpecker</a> <a href="https://rss-mstdn.studiofreesia.com/tags/duga" class="mention hashtag" rel="nofollow noopener" target="_blank">#duga</a> <a href="https://rss-mstdn.studiofreesia.com/tags/duga_oth_radar" class="mention hashtag" rel="nofollow noopener" target="_blank">#duga_oth_radar</a> <a href="https://rss-mstdn.studiofreesia.com/tags/vintage_computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#vintage_computer</a> <a href="https://rss-mstdn.studiofreesia.com/tags/retro_computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#retro_computer</a> <a href="https://rss-mstdn.studiofreesia.com/tags/old_computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#old_computer</a> <a href="https://rss-mstdn.studiofreesia.com/tags/mainframe" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainframe</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ibm_370" class="mention hashtag" rel="nofollow noopener" target="_blank">#ibm_370</a> <a href="https://rss-mstdn.studiofreesia.com/tags/pripyat" class="mention hashtag" rel="nofollow noopener" target="_blank">#pripyat</a> <a href="https://rss-mstdn.studiofreesia.com/tags/chernobyl_disaster" class="mention hashtag" rel="nofollow noopener" target="_blank">#chernobyl_disaster</a> <a href="https://rss-mstdn.studiofreesia.com/tags/chernobyl_2" class="mention hashtag" rel="nofollow noopener" target="_blank">#chernobyl_2</a> <a href="https://rss-mstdn.studiofreesia.com/tags/chornobyl_2" class="mention hashtag" rel="nofollow noopener" target="_blank">#chornobyl_2</a> <a href="https://rss-mstdn.studiofreesia.com/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a>

Update Computer ClubVisit the Update Computer Club today at <a href="https://social.linux.pizza/tags/Kulturnatten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kulturnatten</a> <a href="https://social.linux.pizza/tags/Uppsala" class="mention hashtag" rel="nofollow noopener" target="_blank">#Uppsala</a>! We're open until at least 22:00. Free admission!More info: <a href="https://kulturnatten.uppsala.se/en/program/event/?externalId=6c734dc3-8459-4bd2-bf8f-c15d31065e10" rel="nofollow noopener" translate="no" target="_blank">https://kulturnatten.uppsala.se/en/program/event/?externalId=6c734dc3-8459-4bd2-bf8f-c15d31065e10</a><a href="https://social.linux.pizza/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://social.linux.pizza/tags/retrogaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrogaming</a> <a href="https://social.linux.pizza/tags/vintagecomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#vintagecomputing</a> <a href="https://social.linux.pizza/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a>

tallshipOkay I thought I'd share this recent post here on the <a class="hashtag" href="https://public.mitra.social/collections/tags/fediverse" rel="nofollow noopener" target="_blank">#Fediverse</a>. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.So first, the question, posed <a href="https://retrocomputing.stackexchange.com/a/29851/29887" rel="nofollow noopener" target="_blank">HERE</a>.And my answer follows below:There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.## Scroll down to the tl;dr for the succinct answer of your questionEthernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:> People Don't Need To See Paula AbdulOkay, touched on already, but not really treated, is the description of that little memory aid.> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.For instance, NIC <a class="hashtag" href="https://public.mitra.social/collections/tags/1" rel="nofollow noopener" target="_blank">#1</a> has the MAC: 00:b0:d0:63:c2:26 and NIC <a class="hashtag" href="https://public.mitra.social/collections/tags/2" rel="nofollow noopener" target="_blank">#2</a> has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to <a href="https://jvns.ca/blog/2021/05/11/what-s-the-osi-model-/" rel="nofollow noopener" target="_blank">Julia Evans</a>:- Layer 2 (Don't) corresponds to Ethernet. - Layer 3 (Need) corresponds to IP. - Layer 4 (To) corresponds to TCP or UDP (or ICMP etc) - Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)You may wish to give her page a gander for just a bit more of a deeper dive.Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:The IP stack you know and use everyday was fathered by <a href="https://historyofcomputercommunications.info/section/11.8/TCP-IP-and-XNS-1981-1983/" rel="nofollow noopener" target="_blank">Bill Joy</a>, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, <a href="http://chiselapp.com/user/pnr/repository/TUHS_wiki/wiki?name=haverty" rel="nofollow noopener" target="_blank">BBN</a> never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.I highly recommend that you take a look at <a href="https://www.splunk.com/en_us/blog/learn/osi-model.html" rel="nofollow noopener" target="_blank">this excellent resource explaining the OSI model</a>.# tl;dr:So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:> What were the major things that caused TCP/IP to become the internet standard protocol?The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a <a href="https://en.wikipedia.org/wiki/Retroactive_continuity" rel="nofollow noopener" target="_blank">retcon</a>, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on <a href="https://en.wikipedia.org/wiki/Flag_day_(computing)" rel="nofollow noopener" target="_blank">Flag Day - 01 January 1983</a>.So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.### DARPA said 01 January 1983 and that's it, and that was it - Flag Day.Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.Enjoy!<a class="hashtag" href="https://public.mitra.social/collections/tags/tallship" rel="nofollow noopener" target="_blank">#tallship</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/darpa" rel="nofollow noopener" target="_blank">#DARPA</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/ip" rel="nofollow noopener" target="_blank">#IP</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/internet%5Fprotocol" rel="nofollow noopener" target="_blank">#Internet_Protocol</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/computer%5Fhistory" rel="nofollow noopener" target="_blank">#Computer_History</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/internetworking" rel="nofollow noopener" target="_blank">#internetworking</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/internet" rel="nofollow noopener" target="_blank">#Internet</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/arpanet" rel="nofollow noopener" target="_blank">#ARPANET</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/milnet" rel="nofollow noopener" target="_blank">#MILNET</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/nsfnet" rel="nofollow noopener" target="_blank">#NSFnet</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/bill%5Fjoy" rel="nofollow noopener" target="_blank">#Bill_Joy</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/bbn" rel="nofollow noopener" target="_blank">#BBN</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/unix" rel="nofollow noopener" target="_blank">#UNIX</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/bsd" rel="nofollow noopener" target="_blank">#BSD</a>⛵.

:rss: Hacker NewsThe Rise and Fall of 3M's Floppy Disk <a href="https://spectrum.ieee.org/3m-floppy" rel="nofollow noopener" translate="no" target="_blank">https://spectrum.ieee.org/3m-floppy</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/3m_floppy" class="mention hashtag" rel="nofollow noopener" target="_blank">#3m_floppy</a> <a href="https://rss-mstdn.studiofreesia.com/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://rss-mstdn.studiofreesia.com/tags/audio_tape" class="mention hashtag" rel="nofollow noopener" target="_blank">#audio_tape</a> <a href="https://rss-mstdn.studiofreesia.com/tags/masking_tape" class="mention hashtag" rel="nofollow noopener" target="_blank">#masking_tape</a>

:rss: Hacker NewsNTP Timelord Dies <a href="https://www.i-programmer.info/news/82-heritage/16929-ntp-timelord-dies.html" rel="nofollow noopener" translate="no" target="_blank">https://www.i-programmer.info/news/82-heritage/16929-ntp-timelord-dies.html</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Programming_book_reviews" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming_book_reviews</a> <a href="https://rss-mstdn.studiofreesia.com/tags/programming_tutorials" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming_tutorials</a> <a href="https://rss-mstdn.studiofreesia.com/tags/programming_news" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming_news</a> <a href="https://rss-mstdn.studiofreesia.com/tags/developer_news" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer_news</a> <a href="https://rss-mstdn.studiofreesia.com/tags/software_programmer_news" class="mention hashtag" rel="nofollow noopener" target="_blank">#software_programmer_news</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ruby</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://rss-mstdn.studiofreesia.com/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> <a href="https://rss-mstdn.studiofreesia.com/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Visual_Basic" class="mention hashtag" rel="nofollow noopener" target="_blank">#Visual_Basic</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Computer_book_reviews" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computer_book_reviews</a> <a href="https://rss-mstdn.studiofreesia.com/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> <a href="https://rss-mstdn.studiofreesia.com/tags/programming_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming_history</a> <a href="https://rss-mstdn.studiofreesia.com/tags/joomla" class="mention hashtag" rel="nofollow noopener" target="_blank">#joomla</a> <a href="https://rss-mstdn.studiofreesia.com/tags/theory" class="mention hashtag" rel="nofollow noopener" target="_blank">#theory</a> <a href="https://rss-mstdn.studiofreesia.com/tags/spreadsheets" class="mention hashtag" rel="nofollow noopener" target="_blank">#spreadsheets</a> <a href="https://rss-mstdn.studiofreesia.com/tags/developer_book_reviews" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer_book_reviews</a> <a href="https://rss-mstdn.studiofreesia.com/tags/programmer_news" class="mention hashtag" rel="nofollow noopener" target="_blank">#programmer_news</a> <a href="https://rss-mstdn.studiofreesia.com/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

Victor Bogado<a href="https://hachyderm.io/@dylanbeattie" class="u-url mention" rel="nofollow noopener" target="_blank">@dylanbeattie</a> not exactly yaml (corrected by the cell to y'all) faults here. It's just following the C parsing convention.I'm not even sure if that is not even older than C, would be nice to hear from some <a href="https://hachyderm.io/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> expert on that

Update Computer ClubIn Update's <a href="https://social.linux.pizza/tags/computer_of_the_month" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_of_the_month</a> project we pick one computer from our collection each month and examine its condition, possibly repair it, and explore its architecture, history, and software.In June 2023 we selected the Swedish educational computer Compis from 1985.<a href="https://social.linux.pizza/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://social.linux.pizza/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a>

shenlebantongying🏳️‍⚧️✅Windows 1.0 is actually a tiling window manager.To resize: left-click top right -> hold -> right-click dragDouble click top right -> temporarily full screen an app -> double click again -> get back to the original layout.<a href="https://moe.cat/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a><a href="https://archive.org/details/windows-1-0" rel="nofollow noopener" target="_blank">https://archive.org/details/windows-1-0</a>

manuelcaeiro ☕> <a href="https://mastodon.social/tags/computer_history" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer_history</a> and <a href="https://mastodon.social/tags/reverse_engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#reverse_engineering</a> <a href="https://mastodon.social/tags/old_chips" class="mention hashtag" rel="nofollow noopener" target="_blank">#old_chips</a> > currently <a href="https://mastodon.social/tags/restoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#restoring</a> a <a href="https://mastodon.social/tags/Xerox_Alto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xerox_Alto</a><a href="https://www.righto.com/p/about-ken-shirriff.html" rel="nofollow noopener" target="_blank">https://www.righto.com/p/about-ken-shirriff.html</a>

tallship<a class="u-url mention" href="https://social.linux.pizza/@redstarfish" rel="nofollow noopener" target="_blank">@redstarfish</a> <a class="u-url mention" href="https://social.linux.pizza/@cobra" rel="nofollow noopener" target="_blank">@cobra</a> There is, perhaps, a distinct flaw in your logic, although I do concur with the spirit of your inference. > Is linux, the kernel finished? Then why does it keep growing and getting new version numbers? :-) The notion of whether Linux is finished could have been, one might suppose, assigned to 14 March 1994, with the release of version 1.0.0. Considering that LInux and the BSDs have been running production business services for nigh thirty years, the more relevant question in this given scenario might be to ask: "Is it soup yet?" Fighting to keep my old surplus PDP-11 acquired at auction running with coat hangers and duck tape for my <a class="hashtag" href="https://pleroma.cloud/tag/isp" rel="nofollow noopener" target="_blank">#ISP</a> business was a daunting task. Being one of the first four consumer targeted ISPs in the greater Los Angeles area, I think the sheer novelty of public Internet access via <a class="hashtag" href="https://pleroma.cloud/tag/dialup" rel="nofollow noopener" target="_blank">#dialup</a> was what enabled my subscriber base to grow (mostly within a 12 mile radius of Redondo Beach) so quickly, and defray the costs of the electric bill required to run that beast. 4.3BSD with a Net/2 IP stack was pretty reliable, but operation was costly. <a class="hashtag" href="https://pleroma.cloud/tag/gte" rel="nofollow noopener" target="_blank">#GTE</a>'s Centranet service made incoming calls a breeze, and we could expand the service with blocks of as little as 3 lines at a time. Usually, we ordered in blocks of 12. This way, would could publish one <a class="hashtag" href="https://pleroma.cloud/tag/did" rel="nofollow noopener" target="_blank">#DID</a> (Phone number) in the <a class="hashtag" href="https://pleroma.cloud/tag/yellow_pages" rel="nofollow noopener" target="_blank">#Yellow_Pages</a> or whatever other advertising we availed ourselves of. We were on Artesia Blvd., a major thoroughfare through Torrance, Redondo Beach, Hermosa Beach, and Manhattan Beach, so signage on my building and word of mouth in the geek community did most of the legwork for us. <a class="hashtag" href="https://pleroma.cloud/tag/centranet" rel="nofollow noopener" target="_blank">#Centranet</a> was a breath of fresh air for another aspect of our business, originally going back a few years earlier to professional BBS hosting services (basically, early managed Co-location services, if you will). At that time, we used BBS Doors to drop the users who had dialed in to a BSD UNIX shell. We were originally a retail <a class="hashtag" href="https://pleroma.cloud/tag/microcomputer" rel="nofollow noopener" target="_blank">#Microcomputer</a> sales and service outfit, so when <a class="hashtag" href="https://pleroma.cloud/tag/jolix" rel="nofollow noopener" target="_blank">#Jolix</a> (386BSD) came out we took advantage of the pile of #386 boxes that had accumulated during the recent few years due to customer upgrades or purchases of new <a class="hashtag" href="https://pleroma.cloud/tag/486sx" rel="nofollow noopener" target="_blank">#486SX</a> machines, etc., cannibalized them to make several stable hardware platforms, and began the migration to UNIX on PCs. This migration proved to be premature - <a class="hashtag" href="https://pleroma.cloud/tag/386bsd" rel="nofollow noopener" target="_blank">#386BSD</a> was not very stable. Forks of this work in the form of NetBSD, followed by <a class="hashtag" href="https://pleroma.cloud/tag/freebsd" rel="nofollow noopener" target="_blank">#FreeBSD</a>, and the eventual <a class="hashtag" href="https://pleroma.cloud/tag/openbsd" rel="nofollow noopener" target="_blank">#OpenBSD</a> fork of NetBSD were right around the corner. But we didn't go that route, because one of my techs stumbled upon something else first - Linux. So in the meantime, we began experimenting with <a class="hashtag" href="https://pleroma.cloud/tag/soft_landing_systems" rel="nofollow noopener" target="_blank">#Soft_Landing_Systems</a> (SLS). Not really all that stable either, but we went to work on shaping our own Linux distro to replace <a class="hashtag" href="https://pleroma.cloud/tag/sls" rel="nofollow noopener" target="_blank">#SLS</a> and install on the 386 and 486 boxes stacked up along one wall of the shop. Between our own <a class="hashtag" href="https://pleroma.cloud/tag/linboard" rel="nofollow noopener" target="_blank">#Linboard</a> Linux and <a class="hashtag" href="https://pleroma.cloud/tag/yggdrasil" rel="nofollow noopener" target="_blank">#Yggdrasil</a> Linux "LGX" (Linux 0.98.1) we had something relatively stable that our dialup customers could trust and so we decommisioned the old DEC and it wasn't hard finding a buyer for a PDP-11 at that time. Next, we began building #486 boxes with Linux installed, preconfigured with static IP addresses from one of my many IP blocks that I had been issued by the military (I'm a former ARPANET engineer from the Dept. of Defense). These machines were sold as a turnkey solution with a Graphical User Interface - you simply took it out of the box, plugged it into your wall socket and phone jack, and powered it on - Voila! You're now an actual legit host on the Internet, care of a dedicated dialup <a class="hashtag" href="https://pleroma.cloud/tag/slip" rel="nofollow noopener" target="_blank">#SLIP</a> connection to our network! Kinda dumb, in retrospect, but I branded these "Personal Internet Stations", and soon thereafter, people started affectionately calling them "Piss boxes", or "Piss computers". Okay, you live and learn :) We still supported BBS doors too for the regular dialup users, but instead of the <a class="hashtag" href="https://pleroma.cloud/tag/almquist" rel="nofollow noopener" target="_blank">#Almquist</a> shell (Ash), users now had <a class="hashtag" href="https://pleroma.cloud/tag/bash" rel="nofollow noopener" target="_blank">#Bash</a> (Yay!) as their default, as well as a choice of others such as <a class="hashtag" href="https://pleroma.cloud/tag/foss" rel="nofollow noopener" target="_blank">#FOSS</a> versions of the Korn and C shells, because Linux was now ubiquitous throughout our offerings. Since we no longer had the <a class="hashtag" href="https://pleroma.cloud/tag/dec" rel="nofollow noopener" target="_blank">#DEC</a>, I needed a better way to network. Now, Linux/UNIX based <a class="hashtag" href="https://pleroma.cloud/tag/bbses" rel="nofollow noopener" target="_blank">#BBSes</a> weren't very.... What little you could find wasn't much to speak of, so this was realm of the land of DOS, and companies like <a class="hashtag" href="https://pleroma.cloud/tag/esoft" rel="nofollow noopener" target="_blank">#eSoft</a> (TBBS), <a class="hashtag" href="https://pleroma.cloud/tag/galacticomm" rel="nofollow noopener" target="_blank">#Galacticomm</a> (The Major BBS) and <a class="hashtag" href="https://pleroma.cloud/tag/mustang_software" rel="nofollow noopener" target="_blank">#Mustang_Software</a> (Wildcat BBS) produced some of the most popular <a class="hashtag" href="https://pleroma.cloud/tag/bbs" rel="nofollow noopener" target="_blank">#BBS</a> systems at the time - all of them DOS based BBSes. Although a <a class="hashtag" href="https://pleroma.cloud/tag/dos" rel="nofollow noopener" target="_blank">#DOS</a> BBS could (can, actually) indeed support several simultaneous dialup connections on it's own, known as "nodes", how do we get those users to a real UNIX shell on the PDP-11 running 4.4BSD? Enter Quarterdeck's <a class="hashtag" href="https://pleroma.cloud/tag/desqview" rel="nofollow noopener" target="_blank">#DESQview</a>/X - an <a class="hashtag" href="https://pleroma.cloud/tag/x11r5" rel="nofollow noopener" target="_blank">#X11R5</a> X-server, from the folks that brought us <a class="hashtag" href="https://pleroma.cloud/tag/qemm386" rel="nofollow noopener" target="_blank">#QEMM386</a>. Now we've got an IP stack, but this is DOS, so we still need a NetBIOS networking layer to get it across the network. Hmm..... Well the usual answer would be to purchase some add-in crap for <a class="hashtag" href="https://pleroma.cloud/tag/novell" rel="nofollow noopener" target="_blank">#Novell</a> <a class="hashtag" href="https://pleroma.cloud/tag/netware" rel="nofollow noopener" target="_blank">#Netware</a>. But that's expensive, and totally DOS-centric thinking (and it's overkill). I didn't want to install Netware on a bunch of PCs, install a Netware server, the bridges, etc., - because we were (and I always have been) a <a class="hashtag" href="https://pleroma.cloud/tag/unix" rel="nofollow noopener" target="_blank">#UNIX</a> shop!!! Solution: Install the latest version of <a class="hashtag" href="https://pleroma.cloud/tag/dr_dos" rel="nofollow noopener" target="_blank">#DR_DOS</a> (Digital Research DOS), and DESQview/X (which includes QEMM), and <a class="hashtag" href="https://pleroma.cloud/tag/artisoft" rel="nofollow noopener" target="_blank">#Artisoft</a> <a class="hashtag" href="https://pleroma.cloud/tag/lantastic" rel="nofollow noopener" target="_blank">#LANtastic</a>'s <a class="hashtag" href="https://pleroma.cloud/tag/ailanbio" rel="nofollow noopener" target="_blank">#AILANBIO</a> (the <a class="hashtag" href="https://pleroma.cloud/tag/netbios" rel="nofollow noopener" target="_blank">#NetBIOS</a> layer - no need for their server software, we've got TCP/IP thanks to <a class="hashtag" href="https://pleroma.cloud/tag/quarterdeck" rel="nofollow noopener" target="_blank">#Quarterdeck</a>! Now we've got a full blown <a class="hashtag" href="https://pleroma.cloud/tag/unix" rel="nofollow noopener" target="_blank">#UNIX</a> environment across the entirety of our network - almost, I'm obtuse, but not stupid. Most customers off the street were MS Windows users so we fully supported that under MS DOS (but mostly DR DOS after Gary found and disabled Bill's <a class="hashtag" href="https://pleroma.cloud/tag/aard" rel="nofollow noopener" target="_blank">#AARD</a> code exploit - that's another story). I should note here, to avoid questions about the notion of long distance services. At that time, even after the divestiture of AT&T which occured in 1984, a so-called "Local call", meant anything within a 12 mile radius of your local CO (Central Office of your <a class="hashtag" href="https://pleroma.cloud/tag/lec" rel="nofollow noopener" target="_blank">#LEC</a>, or local exchange carrier - AKA, the telephone company, General Telephone in our case, but Pacific Bell customers could dial as a local call as well with respect to these considerations). Anything farther out than 12 miles from the CO was billed as "Message Units" - and that could get VERY expensive for the caller. Beyond that, anything requiring AT&T long distance was.... well, long distance lolz. I still operate an active BBS network and can be contacted directly via <a class="hashtag" href="https://pleroma.cloud/tag/netmail" rel="nofollow noopener" target="_blank">#Netmail</a> at: SysOP@1:102/127 So basically, the majority of our customer base was from LAX and Inglewood to the north of us, Wilmington and parts of Long Beach to the east, Gardena to the norheast, and San Pedro/Rancho Palos Verdes to the South (for anyone familar with the South Bay in the Los Angeles area). But I digress... Cyclades Corporation also released their Cyclom-Y FSX/FSO cards , which also helped a lot with all of the spaghetti wire and USR external modems literally hanging from the ceiling. Since we could now accommodate between 4 and 32 modems that had DB-25 serial cables per card (in reality, we couldn't actually get more than one or two of these Cyclades cards to work reliably per PC at a time). This really made the shop look a lot nicer and we were able to streamline our cable management and begin stacking the Modems on shelves once more.... but we still had problems with Stability in Linux, until I discovered some <a class="hashtag" href="https://pleroma.cloud/tag/deadhead" rel="nofollow noopener" target="_blank">#Deadhead</a> named <a class="hashtag" href="https://pleroma.cloud/tag/patrick_volkerding" rel="nofollow noopener" target="_blank">#Patrick_Volkerding</a> at Moorhead State University in Minnesota had done a much better job of patching up SLS, making it available via FTP. The move to <a class="hashtag" href="https://pleroma.cloud/tag/slackware" rel="nofollow noopener" target="_blank">#Slackware</a>, at a time before <a class="hashtag" href="https://pleroma.cloud/tag/debian" rel="nofollow noopener" target="_blank">#Debian</a> even existed was a great move, I never looked back, and to this day deploy Slackware Linux as a rock solid server platform in the enterprise as well as using it as one of my workstation daily drivers. <a class="hashtag" href="https://pleroma.cloud/tag/netbsd" rel="nofollow noopener" target="_blank">#NetBSD</a> by this time looked promising, but I was really mesmerized by the potential of this Linux thing that some drunken college student in a Helsinki dorm room had created. There was a buzz in the air, and you could just feel it was going to take over the world. I had to be a part of this revolution! As my profile states, I'm a bit of a <a class="hashtag" href="https://pleroma.cloud/tag/debiantard" rel="nofollow noopener" target="_blank">#Debiantard</a> too, but <a class="hashtag" href="https://pleroma.cloud/tag/ian_murdock" rel="nofollow noopener" target="_blank">#Ian_Murdock</a> (RIP) wouldn't even release the first beta of Debian for several months and their first stable release was still almost two years away. All of this occurred prior to the 1.0.0 release of <a class="hashtag" href="https://pleroma.cloud/tag/linux" rel="nofollow noopener" target="_blank">#Linux</a>... when it was arguably, "Finished", so to speak :) <a class="hashtag" href="https://pleroma.cloud/tag/tallship" rel="nofollow noopener" target="_blank">#tallship</a> <a class="hashtag" href="https://pleroma.cloud/tag/vger" rel="nofollow noopener" target="_blank">#Vger</a> <a class="hashtag" href="https://pleroma.cloud/tag/foss" rel="nofollow noopener" target="_blank">#FOSS</a> <a class="hashtag" href="https://pleroma.cloud/tag/retrocomputing" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a class="hashtag" href="https://pleroma.cloud/tag/retro" rel="nofollow noopener" target="_blank">#retro</a> <a class="hashtag" href="https://pleroma.cloud/tag/computer_history" rel="nofollow noopener" target="_blank">#computer_history</a> <a class="hashtag" href="https://pleroma.cloud/tag/hurd" rel="nofollow noopener" target="_blank">#Hurd</a> <a class="hashtag" href="https://pleroma.cloud/tag/gnu" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://pleroma.cloud/media/228380d02f28b34ee6c1fdf5e5446e38823d40fee496c783dbb1538022df45c3.jpg?name=Yggdrasil_Linux.jpg" class="" rel="nofollow noopener" target="_blank">Yggdrasil_Linux.jpg</a>

Recent searches

Search options

Administered by:

Server stats:

#computer_history