[-] LeFantome@programming.dev 5 points 11 months ago

“I didn’t betray the client and get killed”

Betrayed the client and lived? /s

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

You can use VirtualBox with KVM as well.

https://github.com/cyberus-technology/virtualbox-kvm

You are probably not recompiling the kernel but rather just a kernel module (DKMS). Still annoying.

You do not need a kernel module for the version above as it KVM is already in the kernel. That is why QEMU does not need a kernel module either.

[-] 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

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

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

Except it is going to cost them more in the end. So, this is best explained as idiocy.

[-] 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

Your last sentence is chilling given how much I agree with the rest of what you are saying.

Can you expand on “The income from it is not available for taxation”? I feel like I am missing part of your point here.

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

No love for bcachefs?

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

One of my first memories with Linux was getting the same X config from a Sun Workstation at school onto my Linux box at home. Just seeing similar behaviour made it seem like my computer was suddenly more powerful. In the 90’s, I got an actual copy of Solaris ( in the box ) and I felt like one of the global elite. One of the first things I did after making real money was buy a Sun Ultra.

Now, I can essentially get Solaris for free and I cannot even be bothered to install it. I want to say that the hardware still interests me but honestly I have no desire to use that either. It would be more of a decoration and act of preservation, like a classic painting hanging on the wall.

If anything, the fun project these days might be to create a WiFi card that had a PicoPi or MilkV board on it running Linux as the firmware. Open Source has really changed the game. What makes old hardware fun is modding it to do stuff it never could. The software that is fun to run on old hardware is something still being actively developed—again, maybe Linux.

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

I completely agree.

An OS is defined by its ecosystem ( applications, users, and philosophy ). Everybody knows what an actual Linux distribution is and the kinds of desktop environments ( eg. GNOME, KDE, XFCE ) and applications that Linux implies ( eg. Docker, Podman, Emacs, GIMP, OBS, LibreOffice ). It does not matter if the C library is Glibc or MUSL. It does not matter if things were compiled with GCC or Clang. It does not matter who wrote the version of ‘ls’ installed. It is not confusing when somebody tells you they are using “Linux” on the desktop, the server, or the cloud. You know what they mean.

Saying GNU / Linux does not add any clarity in my view and could be confusing or wrong. If you use Alpine in the cloud, you are using Linux ( very clear ) but not GNU / Linux. If you are using Void on your desktop, you are using Linux ( but maybe not Glibc ). Is one version of Void Linux called GNU / Linux and the other one isn’t? It is not a useful label other than politically.

Android and ChromeOS use the Linux kernel but are not Linux distributions by any useful use of that term. If I switch you from Void to Arch, you could use it for hours without noticing the change. You might not notice until you went to update software. If I moved you to Android or ChromeOS, you would certainly notice right away. In some ways, Windows is a more similar environment than Android is.

If I say, “I use Linux”, you do not have to ask me if I mean Android or if I have a Chromebook. People that don’t “know” that these other systems use the Linux kernel would never make that mistake. The “confusion” is artificial.

As a non-Linux example, is there anybody that is confused that the XBox uses the Windows kernel? Even if I say “I game on Windows”, would you honestly wonder if I meant XBox? Or would it be super obvious that I meant on a PC?

If I say, “I game on Linux”, you again know that I do not mean Android or ChromeOS ( unless I am purposely trying to be arrogant or funny about it ). You might ask if I am using a Stream Deck but, guess what, the Deck also boots into KDE. It really is Linux.

My Nest thermometer and my IP camera both run the Linux kernel as well. Do we need a special name for them? No. Nobody is truthfully confused by that either. Would we call them GNU / Linux even if they use Glibc? I hope not. So what does GNU / Linux even refer to outside of the political meaning?

view more: ‹ prev next ›

LeFantome

0 post score
0 comment score
joined 3 years ago