Skip Navigation

Posts
18
Comments
230
Joined
3 yr. ago

  • Systemd does one thing, it manages services, and does so reliably, without messing around with spagettified shell scripts, with a fuckload of options, and all of that easily is configurable by dropping in files without editing stuff that arrived from the package manager. Seems pretti "do one (complex) thing and do it well"

    If you add other things built around it, it can do more. For example, if you install systemd-nspawn it can start and stop containers like it starts and stops services.

    Other things that you think of as systemd are entirely separate things (like systemd-networkd) that are just built around systemd. You don't have to use them if you don't like.

    On the other hand, you know what does not follow the Unix philosophy? The Xserver, which manages screens, graphic acceleration, input devices, printers, remoting, etc. And it doesn't even do it well

  • The hardware still needs to be brought up and initialised. But the software is the real problem here. The kernel gets fully up in seconds, but then you have to initialize the rest of the OS

  • The pc ecosystem is modular by design. The kernel will figure out itself the available hardware, moreover there are only two major CPU manufacturers (in the pc space of course), which means you have only two platforms to support.

    Mobile phones instead are not modular, they use SoC. While most common socs are from Qualcomm and mediatek, there are a lot more smaller manufacturers. Plus, even if most often they use the same reference design for compute cores, the rest of the soc is often custom and wildly different from others. All of this to say that the kernel needs to already know exactly how the specific soc of the device works, instead of figuring it out on the fly. Which is why you need to check compatibility.

    The brick thing instead is because the bootloaders in these devices are usually very locked down, so sometimes you need to replace the bootloader with a more open one, with all the risks that this entails

  • Did you solve this in the end?

  • Try checking the sampling rate in your pipewire config. It should be 48000. I don't remember exactly how to set it, check on the arch wiki.

    Last time I had issues with digital audio that was it.

  • Flatpak 🤷

  • Kali user

    found the problem

  • Wsl runs on hyper-v. I don't think you can use it in a VM

  • And what was the severe intellectual disability that got you this treatment?

  • Deleted

    Permanently Deleted

    Jump
  • Italy, 16€/month 5gbps down 600mbps up. Also I have a /60 IPv6, and a static but shared IPv4 (3 other users have the same IPv4 and each of us only get a range of 16000 ports) tunneled over IPv6.

  • Unix needed only \n because it had complex drivers that could replace \n with whatever sequence of special characters the printer needed. Also, while carriage return is useful, they saw little use for line feed

    On dos (which was intended for less powerful hardware than unix) you had to actually use the correct sequence which often but not always was \r\n (because teleprinters used that and because it's the "most correct" one).

    Now that teleprinters don't exist, and complex drivers are not an issue for windows, and everyone prefers to have a single \n, windows still uses \r\n, for backward compatibility.

  • Is this supposed to replace bluez?

  • Try to draw a full semicircle and extend the 7 units long red line, you will notice it falls on the other corner of the semicircle. In fact, every way of drawing two segments from a semicircle corner to the same point if the circumference forms a right triangle.

    Now, on the original figure, draw the hypotenuse of the red triangle, you will notice the hypotenuse is as long as the extension you draw earlier, because both start from the same height and fall on a corner of the same semicircle. That means that you can find the extension by calculating the hypotenuse.

    Now, you can calculate 7+extension to get the cathetes of the extended triangle, and it's hypotenuse is the diameter of the semicircle. You can divide the diameter by two to get the radius.

    Now, you notice that: X, the radius, and the red hypotenuse form a right triangle, and you know the length of the red hypotenuse and of the radius, so you can find X.

  • Try to draw a full semicircle and extend the 7 units long red line, you will notice it falls on the other corner of the semicircle. In fact, every way of drawing two segments from a semicircle corner to the same point if the circumference forms a right triangle.

    Now, on the original figure, draw the hypotenuse of the red triangle, you will notice the hypotenuse is as long as the extension you draw earlier, because both start from the same height and fall on a corner of the same semicircle. That means that you can find the extension by calculating the hypotenuse.

    Now, you can calculate 7+extension to get the cathetes of the extended triangle, and it's hypotenuse is the diameter of the semicircle. You can divide the diameter by two to get the radius.

    Now, you notice that: X, the radius, and the red hypotenuse form a right triangle, and you know the length of the red hypotenuse and of the radius, so you can find X.

  • You are missing the point. They care when money is involved, and yet they failed to maintain a browser engine, which would have (for the better or for the worse) a central part of most people's computing.

    And yet, despite the browser being so important... They gave up and handed the cake to Google.

  • LMAO

    Microsoft pays for a lot of opensource development, you may not like it but you still need its work, including Lennart Pottering's salary (and don't even start with "systemd bad").

    "Hyperv is the worst"... Shut up and come back when your hypervisor has proper GPU paravirtualization on all vendors.

  • Bad argument, Microsoft is among the three most valuable companies in the world, when something is important to them they get it done properly (e.g. hyperv is the best made part of windows, because they need it for azure). The settings page doesn't get them money, only nerds care if it's bad, a browser does.

  • Maybe if all the forks merge into a single project, and if that project becomes part of some foundation like the Linux foundation or most likely freedesktop, and if some folks from big tech companies get paid to work on it full time (probably google would, for obvious reasons, but it wouldn't be enough), and if distros start shipping that in place of firefox, and if for some reason the less tech savvy get to know about this project...

    ...Then if all of that happens, forks might have a chance of still existing.

    This is how most big open source projects (like Linux, gnome, mesa, etc) thrive. With the catch that while most tech companies have some stake in Linux and friends, no company other than google has any stake in Firefox existing.

  • They die. Full stop.

    Not even Microsoft had the strength to maintain a browser engine, that's why they moved Edge to Chromium, they gave up.