[-] LeFantome@programming.dev 5 points 1 year ago

The timeline is not super abrupt, especially for architectures where all he is asking is to ensure that your Rust toolchain is in order. That is especially true when you consider that Rust is already well maintained on all the Debian architectures that people actually use.

The abruptness (almost rudeness) is in the second part where he basically says that, if you cannot get Rust going in time, you should just stop releasing Debian for that architecture.

It is mostly just poorly worded though. Because none of these architectures have “official” support even now. This will not be the only way they are behind. So, there is not reason to be so dramatic.

And that would be my response to him. Another option here is that these alternative architectures just continue to ship an older version of APT for now. Emergency avoided. Few of them ship with up-to-date versions of APT even now.

Another solution is to use one of the multiple projects that is working to make Rust code build with the GCC compiler back-end. At least one of these projects has already announced that they want to work with these Debian variants to ensure that APT builds with them.

So, the 6 month timeline is a reasonable impetus to make that happen which would be quite a good thing beyond just APT.

There are many other useful tools written in Rust you are going to want to use on these architectures. It will be a fantastic outcome if this pressure from APT kickstarts that happening for some of these long abandoned architectures (by the mainstream at least).

[-] LeFantome@programming.dev 5 points 1 year ago

Agreed. Also, some of these “bugs” will just be differences in interpretation.

For example, the dd problem that prompted all this noise is that uutils was enforcing the full block parameter in slow pipe writes while GNU was not.

So, now uutils matches GNU and the “bug” is gone.

There will only be a limited number of these kinds of issues and they will be quickly harmonized. Mountains out of mole hills.

[-] LeFantome@programming.dev 5 points 1 year ago

It will keep coming.

For GNOME, I think Chimera Linux is working in something with Turnstile that non-Systemd distros can use to get it working again.

[-] LeFantome@programming.dev 5 points 1 year ago

The founder of the Ladybird project is quite good at getting attention for his projects. He used it first to build community around his SerenityOS project. He is using it now to build awareness around Ladybird and, in particular, to attract financial sponsors.

My assumption is that the level of promotion triggers distrust in the commenter.

In my view, it should be a model for Open Source projects in general. He managed to get enough Patreon support to go full-time on SerenityOS. Many devs provide absolutely crucial software used by everyone while struggling to also work ful-time and pay the bills. He was able to use that full-time freedom to start something as ambitious as a ground-up browser project within SerenityOS. And he attracted many collaborators to his cause. Progress was rapid enough that he split off into the dedicated Ladybird browser project for which he now has an impressive list of financial sponsors. This has allowed his to hire full-time staff. There are still volunteers.

If every Open Source project followed his lead, the world would be a difference place.

It is worth noting how much more slowly SerenityOS is evolving now that he is gone. And what is happening is largely invisible to the wider world.

In my mind, the effective community engagement has allowed the Ladybird project to advance with less corporate oversight, not more. There is less risk of this becoming Google or Mozilla. Of course, time will tell.

[-] LeFantome@programming.dev 5 points 1 year ago* (last edited 1 year ago)

Xen is running full virtual machines. You run full operating systems on simulated hardware. The real “host” operating system is the hypervisor (Xen). Inside a VM, you have the concept of one or more CPUs but you do not know which actual CPU cores that maps to. The load can be distributed to any of them by the real host.

In something like Docker, you only run a single host kernel. On top of that you run sandbox environments that run on the kernel that “think” they have an environment to themselves but are actually sharing a single host kernel. The single host kernel directly manages the real hardware. Processes can run on any of the CPUs managed by the single host kernel.

In both of the above, updating the host means shutting the system down.

With this new approach, you have multiple kernels, all running natively on real hardware. Any given CPU is being managed by only one of the kernels. No hypervisor.

[-] LeFantome@programming.dev 5 points 2 years ago

Hardware issue?

I cannot speak for “all distros” but I know from experience that this statement is not true. There are also numerous “retro” YouTube channels where you can watch people burn DVDs to install Linux on older hardware. I have seen at least one of those in the past month.

Finally, the ISO file format is the native format of optical media like DVD. When you use an ISO to create a USB stick, you are starting with a DVD image (typically). If it is a valid ISO, you can burn it to a DVD and go.

In terms of “slow”, is it possible that expectations have simply changed and we have forgotten how slow things were back in the day. DVD throughput that is working fine is going to feel slow to us today. Just like we are no longer super impressed that we can store 4.7 GB on a disc.

[-] LeFantome@programming.dev 5 points 2 years ago

Yes, and this means all the “light weight”, “legacy hardware” distros require at least a Pentium Pro.

The only binary distro I know that still runs on Pentium is Adelie.

[-] LeFantome@programming.dev 5 points 2 years ago

IRL many sleeping bags have handles on both sides of the zipper.

[-] LeFantome@programming.dev 5 points 2 years ago* (last edited 2 years ago)

Well, XFree86 ( before Xorg and before KMS ) was an adventure. I spent hours guessing the vertical and horizontal frequencies of my monitor trying to get decent resolutions.

Other than that, Linux was way more work but “felt” powerful relative to OS options of the time. Windows was still crashy. The five of us that used OS/2 hated that it still had a lot of 16 bit under the hood. Linux was pure 32 bit.

Later in the 90’s, you could run a handful of Windows apps on Linux and they seemed to run better on Linux. For example, file system operations were dramatically faster.

And Linux was improving incredibly rapidly so it felt inevitable that it would outpace everything else.

The reality though was that it was super limited and a pain in the ass. “Normal” people would never have put up with it. It did not run anything you wanted it to ( if you had apps you liked on Mac, Windows, OS/2, Amiga, NeXTstep, BeOS, or whatever else you were using ( there were of potential options at the time ). But even for the pure UNIX and POSIX stuff, it was hard.

Obviously installation was technical and complex. And everything was a hodge-podge of independently developed software. “Usability” was not a thing. Ubuntu was not release until 2004.

Linux back then was a lot of hitting FTP sites to download software that you would build yourself from source. Stuff could be anywhere on the Internet and your connection was probably slow. And it was dependency hell so you would be building a lot of software just to be able to build the software you want. And there was a decent chance that applications would disagree about what dependencies they needed ( like versions ). Or the config files would be expected in a different location. Or the build system could not find the required libraries because they were not where the Makefile was looking for them.

Linux in the 90’s had no package management. This is maybe the biggest difference between Linux then and Linux now. When package management finally arrived, it came in two stages. First, came packages but you were still grabbing them individually from FTP. Second came the package manager which handled dependencies and retrieval.

The most popular Linux in the mid to late 90’s was Red Hat. This was before RHEL and before Fedora. There was just “Red Hat Linux”. Red Hat featured RPMs ( packages ) but you were still installing them and any required dependencies yourself at the command line. YUM ( precursor to NRF ) was not added until Fedora Core 1 was release in 2003!

APT ( apt-get ) was not added to Debian until 1998.

And all of this meant that every Linux system ( not distro — individual computer ) was a unique snowflake. No two were alike. So bundling binary software to work on “Linux” was a real horror-show. People like Loki gave it a good run but I cannot imagine the pain they went through. To make matters worse, the Linux “community” was almost entirely people that had self-selected to give up pre-packaged software and to trade sweat-equity for paying for stuff. Getting large number of people to give you money for software was hard. I mean, as far as we have come, that is still harder on Linux than on Windows or macOS.

You can download early Debian or Red Hat distros today if you want to experience it for yourself. That said, even the world of hardware has changed. You will probably not be wrestling IRQs to get sound or networking running on modern hardware or in a VM. Your BIOS will probably not be buggy. You will have VESA at least and not be stuck on VGA. But all of that was just “computing” in the 90’s and the Windows crowd had the same problems.

One 90s hardware quirk was “Windows” printers or modems though where the firmware was half implanted in Windows drivers. This was because the hardware was too limited or too dumb to work on its own and to save money your computer would do some of the work. Good luck having Linux support for those though.

Even without trying old distros, just try to go a few days on you current Linux distro without using apt, nrf, pacman, zypper, the GUI App Store, or what have you. Imagine never being able to use those tools again. What would that be like?

Finally, on my much, much slower 90’s PC, I compiled my own kernel all the time. Honestly multiple times per month I would guess. Compiling new kernels was a significant fraction of where my computing resources went at the time. I cannot remember the last time I compiled a kernel.

It was a different world.

When Linus from LTT tried Linux not that long ago ( he wanted to game ), he commented that he felt like he was playing “with” his computer instead of playing “on” his computer. That comment still describes Linux to some extent but it really, really captures Linux in the 90’s.

[-] LeFantome@programming.dev 5 points 2 years ago

SLS

https://en.m.wikipedia.org/wiki/Softlanding_Linux_System

I used to have to head into University to use the Sun Lab ( Sun Microsystems workstations ) to download all the floppy images. Took forever.

I would copy the X configuration from the Sun machines so that my 486 at home looked the same. For some reason, that made me feel like my PC was a “real” UNIX workstation.

[-] LeFantome@programming.dev 5 points 3 years ago

It sounds like avoiding cookies would be a part of that movement

view more: ‹ prev next ›

LeFantome

0 post score
0 comment score
joined 3 years ago