Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Reviving my 34-year-old DEC VT320 terminal marks the initial step in its resurrection, paving the way for accessing my Linux boxes through the serial console.
I've conducted a Slackware installation over it too - next episode coming soon!
It's surprising how relaxing it is actually, without a GUI in sight.
This is one of my "reverse bucket list" items I've done: "Programmed computers as big as a room and as small as a credit card."
The latter was of course a Raspberry Pi model B, 12 years ago. The former was a VAX 11/750 2-node cluster running VMS, when I went to uni in 1986. The CPU and the hard drive was mounted on a false floor, with air conditioning to keep it cool. Granted, it was a smaller room, maybe a hotel bathroom, but it was a room.
And I got to play around with it, on VT220, VT102, and other models, plus (shudder!) my Commodore 64 Kermit emulator at 300 baud.
Mr. Winter, you have my respect (plus a bit of jealousy).
This is one of my "reverse bucket list" items I've done: "Programmed computers as big as a room and as small as a credit card."
The latter was of course a Raspberry Pi model B, 12 years ago. The former was a VAX 11/750 2-node cluster running VMS, when I went to uni in 1986. The CPU and the hard drive was mounted on a false floor, with air conditioning to keep it cool. Granted, it was a smaller room, maybe a hotel bathroom, but it was a room.
They're cool aren't they! I worked for a defence company at one point, and because I was the Unix guy they sent me to to look at moving this VAX (I don't know what model it was but it was about the size of two motorhome fridges (the square ones). I had never used VMS, but there was an open root shell on a terminal. I discovered it'd been up for about 15 years, and even the thought of shutting something down after 15 years filled me with dread (when spinning HDs have been online for that long, they sometimes don't spin up again after being re-powered). Fortunately we had "trusted experts" on whom I could call, who referred to themselves as "rusted experts".
David Cantrell worked in the Slackware core team between 1999-2001, created the Slackware logo, co-developed the web site, the Slackware Linux Essentials book, ported Slackware to the SPARC architecture, developed the first Slackware automatic update tool and introduced a number of other core packages into the distribution.
In this discussion, David delves into his journey of discovering Linux and his experience working for Slackware. He offers valuable insights into the early days of the Linux ecosystem, a time when the platform was gradually gaining recognition and acceptance in the tech community. Through his perspective, we gain a deeper understanding of the challenges and opportunities that characterised this formative period in Linux's history.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.