Post AXubS4x6PTYGBjgqCe by birnim@fosstodon.org
(DIR) More posts by birnim@fosstodon.org
(DIR) Post #AXubS4AtIizFmD8L3Y by ram@sfba.social
2023-07-21T05:37:15Z
0 likes, 0 repeats
The brat at home is turning into a gaming nerd and wants to try #windows #pc. Except for a brief period in 1997, after several #BSOD I have never ever wanted to have anything to do with that thing. Any #linux … even the notoriously easy to break #slackware was way better than that half baked paid excuse of an OS in the last century. Now… I write this post after having ordered a PC with windows 11. Pray for me my friends… 🤦🏾♂️
(DIR) Post #AXubS4x6PTYGBjgqCe by birnim@fosstodon.org
2023-07-21T06:13:25Z
0 likes, 0 repeats
@ram > notoriously easy to break #slackware what?
(DIR) Post #AXubS5zGYusPOji5DM by ram@sfba.social
2023-07-21T06:18:26Z
0 likes, 0 repeats
@birnim Slackware 0.x never had anything called package manager. Everything had to be built from source and you had to manage the dependencies yourself. Was a nightmare until we moved to Debian.
(DIR) Post #AXubS6r9KZyi5qv7Ca by josemanuel@qoto.org
2023-07-21T07:25:34Z
0 likes, 0 repeats
@ram What do you mean Slackware 0.x? The first public release was version 1.00 thirty years ago.@birnim
(DIR) Post #AXvEw4xyomtf8FOeMS by ram@sfba.social
2023-07-21T14:47:59Z
0 likes, 0 repeats
@josemanuel @birnim couldn’t remember version number. Only remember it was the very first version. we had to compile everything from the kernel because we were tweaking it to make it run as a router and we had our own Ethernet driver because we tried to emulate atm switches and needed custom headers in the frame. Fun times…
(DIR) Post #AXvKnfWo72oje33lGC by josemanuel@qoto.org
2023-07-21T15:53:42Z
0 likes, 0 repeats
@ram I fail to see how that was Slackware’s fault. The Linux kernel itself was barely two years old and it would take another year for it to reach version 1.0. Were you really expecting it to be an easy ride? That’s like trying to use Plan 9 or Temple OS for serious work and feeling cheated when one realises they’re not well suited for it.But that’s not important. What really made me curious was the reason why you said that Slackware was “notoriously easy to break” when it is universally regarded as the most stable and rock-solid distro in existence. What did you do to break the actual distribution?@birnim
(DIR) Post #AXvMd16DlrSvGmflYG by ram@sfba.social
2023-07-21T16:14:10Z
0 likes, 0 repeats
@josemanuel @birnim I never said it was Slackwares fault. Just had too many instances of having to go correct versions of glibc or associated libraries to make certain applications work and it definitely was a nightmare if you were not handy with makefiles and C code. I don’t know which version of Slackware you refer to. The first versions had the latest kernel versions but nothing much beyond that. Try bypassing the package manager on today's distros and bringing up X windows for instance. That was pretty much what we were doing in the last century. What versions worked on one computer will most definitely not work on another just because the graphics card was different. And with no google around to help you figure out which ones worked. That is what I had in mind when I wrote “notorious” ;-)Windows hid all the details behind their bsods which was really hell compared to Slackware’s inconvenience :)