The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Anyone excited for the broken mess that is going to be Plasma 6.0 launch? I think I will keep my Arch out of date for a month.

Speaking of, this is something that's creeping back up in my mind rent-free.

After getting everything tweaked out on a KDE Plasma install, being perfectly content and not touching it further, everything goes smoothly until SDDM refuses to log me in and I get stuck on a black screen. I run into this after messing with the splash screen settings, or tinkering with the display managers background a few times. The most aggravating shit ever, I hope at the very least whatever the fuck that bug is, is fixed.
 
  • Thunk-Provoking
Reactions: jeff7989
Anyone excited for the broken mess that is going to be Plasma 6.0 launch? I think I will keep my Arch out of date for a month.
I've upgraded, it's okay. Not much has changed. There's a couple of minor visual bugs.

The most frustrating thing was that it tried to change my default session from X to Wayland. Lol, fuck off.
 
Speaking of, this is something that's creeping back up in my mind rent-free.

After getting everything tweaked out on a KDE Plasma install, being perfectly content and not touching it further, everything goes smoothly until SDDM refuses to log me in and I get stuck on a black screen. I run into this after messing with the splash screen settings, or tinkering with the display managers background a few times. The most aggravating shit ever, I hope at the very least whatever the fuck that bug is, is fixed.
Giggles in Mint Cinnamon install.
 
SDDM is not under KDE umbrella. And it's dogshit.
Edit. KDE devs tried to take over before 6.0 but main dev wasn't happy about it or something.

Display managers suck in general, especially when they are dependencies for screen lockers. You can use a conditional in your '.profile' to treat the tty as a pseudo login screen instead, so startx runs automatically.
 
Unless that's recent the mach kernel which was the basis of OS X was directly from the actual BSD codebase, I think 4.2. Maybe that's subsequent history. FreeBSD took from the same codebase so of course they share a lot of code but that doesn't mean MacOS took it from FreeBSD.

The macOS unix user land is based on FreeBSD, and I thought they ran mach as a micro kernel in like a BSD style macro-kernel. In fact, Apple at one stage had hired many of the freebsd developers. Those days are long gone, but things like pf still exist in macos.

From the macOS Dev Documentation

In OS X, however, the kernel environment contains much more than the Mach kernel itself. The OS X kernel environment includes the Mach kernel, BSD, the I/O Kit, file systems, and networking components. These are often referred to collectively as the kernel. Each of these components is described briefly in the following sections. For further details, refer to the specific component chapters or to the reference material listed in the bibliography.

Because OS X contains three basic components (Mach, BSD, and the I/O Kit), there are also frequently as many as three APIs for certain key operations. In general, the API chosen should match the part of the kernel where it is being used, which in turn is dictated by what your code is attempting to do. The remainder of this chapter describes Mach, BSD, and the I/O Kit and outlines the functionality that is provided by those components.

Mach​

Mach manages processor resources such as CPU usage and memory, handles scheduling, provides memory protection, and provides a messaging-centered infrastructure to the rest of the operating-system layers. The Mach component provides

  • untyped interprocess communication (IPC)
  • remote procedure calls (RPC)
  • scheduler support for symmetric multiprocessing (SMP)
  • support for real-time services
  • virtual memory support
  • support for pagers
  • modular architecture
General information about Mach may be found in the chapter Mach Overview. Information about scheduling can be found in the chapter Mach Scheduling and Thread Interfaces. Information about the VM system can be found in Memory and Virtual Memory.

BSD​

Above the Mach layer, the BSD layer provides “OS personality” APIs and services. The BSD layer is based on the BSD kernel, primarily FreeBSD. The BSD component provides

  • file systems
  • networking (except for the hardware device level)
  • UNIX security model
  • syscall support
  • the BSD process model, including process IDs and signals
  • FreeBSD kernel APIs
  • many of the POSIX APIs
  • kernel support for pthreads (POSIX threads)
The BSD component is described in more detail in the chapter BSD Overview.

BSD Overview​

The BSD portion of the OS X kernel is derived primarily from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features. BSD variants in general are derived (sometimes indirectly) from 4.4BSD-Lite Release 2 from the Computer Systems Research Group (CSRG) at the University of California at Berkeley. BSD provides many advanced features, including the following:

  • Preemptive multitasking with dynamic priority adjustment. Smooth and fair sharing of the computer between applications and users is ensured, even under the heaviest of loads.
  • Multiuser access. Many people can use an OS X system simultaneously for a variety of things. This means, for example, that system peripherals such as printers and disk drives are properly shared between all users on the system or the network and that individual resource limits can be placed on users or groups of users, protecting critical system resources from overuse.
  • Strong TCP/IP networking with support for industry standards such as SLIP, PPP, and NFS. OS X can interoperate easily with other systems as well as act as an enterprise server, providing vital functions such as NFS (remote file access) and email services, or Internet services such as HTTP, FTP, routing, and firewall (security) services.
  • Memory protection. Applications cannot interfere with each other. One application crashing does not affect others in any way.
  • Virtual memory and dynamic memory allocation. Applications with large appetites for memory are satisfied while still maintaining interactive response to users. With the virtual memory system in OS X, each application has access to its own 4 GB memory address space; this should satisfy even the most memory-hungry applications.
  • Support for kernel threads based on Mach threads. User-level threading packages are implemented on top of kernel threads. Each kernel thread is an independently scheduled entity. When a thread from a user process blocks in a system call, other threads from the same process can continue to execute on that or other processors. By default, a process in the conventional sense has one thread, the main thread. A user process can use the POSIX thread API to create other user threads.
  • SMP support. Support is included for computers with multiple CPUs.
  • Source code. Developers gain the greatest degree of control over the BSD programming environment because source is included.
  • Many of the POSIX APIs.
 
Anyone excited for the broken mess that is going to be Plasma 6.0 launch? I think I will keep my Arch out of date for a month.
I just did the update, then SDDM got borked. Doesn't load anymore, but I was able to switch TTY and restore my drive with Timeshift. Oh well.

Edit: trying out the testing repos, since I had many errors saying the current installed version is higher than those in the main repos, even though KDE Unstable was already enabled.
 
Last edited:
  • Informative
Reactions: Miller
TBF MacOS uses cuck-licensed code from various BSDs, including FreeBSD.
Unless that's recent the mach kernel which was the basis of OS X was directly from the actual BSD codebase, I think 4.2. Maybe that's subsequent history. FreeBSD took from the same codebase so of course they share a lot of code but that doesn't mean MacOS took it from FreeBSD.
holy fuck that reminds me of a /g/ shitpost video I've been trying to find
It took me a few minutes but I found it
https://preservetube.com/watch?v=2oLuJSFZKEs
 
It's out.

1709222266969.png


1709222292176.png


And it supports HDR, sweet.

I might read some reviews to see how well it works, if it's good enough, I might just ditch Win11 altogether and go back to Fedora 39 (on my main rig).
 
It's KDE, you can configure it to look almost indistinguishable from MacOS or CDE or whatever you prefer.
Ah yes, KDE Plasma: The DE everyone uses to make it look like another DE but worse instead of actually just using the DE that was designed to work that way in the first place thus avoiding *Krashes* lol
 
Ah yes, KDE Plasma: The DE everyone uses to make it look like another DE but worse instead of actually just using the DE that was designed to work that way in the first place thus avoiding *Krashes* lol
If I could use ZFS, Solidworks, and a number of other small but important things in MacOS, I would.
I don't think Linux is many users' first choice, I imagine most of its userbase are like me, people who need the advanced capabilities, but prefer a more practical operating system.

That's not to say KDE isn't good on its own. It's basically a better Windows than Windows. "Krashes" hasn't been accurate for years in my experience, it's very stable nowadays. I grew up on Macs so that's the UI I prefer. KDE is the best way to get close to that on Linux. For someone who grew up on Windows, I'm sure out of the box KDE is just fine.
 
  • Agree
Reactions: 419
After getting everything tweaked out on a KDE Plasma install, being perfectly content and not touching it further, everything goes smoothly until SDDM refuses to log me in and I get stuck on a black screen. I run into this after messing with the splash screen settings, or tinkering with the display managers background a few times. The most aggravating shit ever, I hope at the very least whatever the fuck that bug is, is fixed.
Do you get to the desktop after waiting 5-10 minutes after you get a black screen?
 
Back