Yeah, I’ve been using systemd-boot for over 6 months, close to a year, and I’ve never had issues with Windows. And I’ve been dualbooting a lot. Multiple times, using different windows editions, like AtlasOS, or Windows after Winutil, and my sytem has never broken because of Windows and boatloader shenanigans. And to top it all off, in all of these instances, I had Windows installed AFTER Linux, and the only tbing I had to fix after install is to change the boot order so Systemd-boot takes priority.
Truthfully, I don’t know what the secret sauce is. In my experience: system d boot is very simple and allows us to hook directly into the bootloader without any fuss. GRUB seems to be an operating system of its own and windows knows how to hook into it if you will.
Trying to install a lot of shit, primarily. I figured out that a lot of programs that I wanted were only available (to my knowledge) in .deb format which I couldn't get working in the distro, That and I'm still not used to using the terminal to install anything. Literally the only thing I miss from Windows is using wizards to install things. I understand a lot of this is purely skill issue though.
I found installing pamac and the enabling the arch user repository gives you most things that are debs, that of course involves using the cli to install pamac though
But installing via terminal is so much more convenient compared to those stupid windows installer. Not to mention you don’t have to download all those stupid installers again each time you want to update, unless the devs provide their own update mention in the software itself.
It spits out all the packages with SEARCHTERM in its name or description. The packages are listed like “REPO/PACKAGE” , where REPO tells you if it’s from the official repos (core/extra/multilib) or from the AUR.
Then pick the number of the package from the list and that’s it.
If you want to update all your packages, even the AUR ones just enter yay and press enter on the follow-up questions. If you update with pacman -Syu then AUR packages won’t get updated.
Also Octopi is a nice frontend for yay and pacman. Not as fancy as Discover or Pamac but it does its job well.
Just using endeavour's bundled yay, you can install most packages including deb ones that users have written a "how to install" for. https://aur.chaotic.cx/ would also be nice.
The meta-analysis on Lobsters is also an interesting read.
Oh thank god, Lobsters is the name of the website. I was not prepared for a rabbit-hole where crustaceans were somehow relevant to a dead-end Intel ISA. I already know too much about MCS-51 because of VHS.
MCS-51, as in the Intel Microcontroller? I’m trying to find some link between that chip and the VHS standard, but I’m not immediately coming up with anything. From my reading, I see that some variants of the MCS-51 incorporate DSP functionality, which would make for a good analogue media device, but I’m not seeing any VHS VCRs that use one.
The same! It’s the “CPU” in the View-Master Interactive Vision. They shipped with a poorly-labeled AMD-manufactured chip that could only be an 8051 or compatible, based on its pinouts. There’s also a 9918-ish video chip, like the ColecoVision, MSX1, or TI-99/4A. The only other big chip is some kind of gate array. I’m almost certain that chip shoves code into 256 bytes of PRG-RAM for the Harvard-architecture MCU… so that Mickey Mouse can fight ghosts with a shotgun.
Yeah, people are trying to make Wayland work so hard… Thanks to the open source community behind it but let’s be honest: Wayland is badly designed and coded.
After 10 years I can still not share my screen easily, always need to switch to X11.
Wayland are for little hobbyist kids who want to have fun with Linux, not people who need to do actual stuff.
If Wayland was doing half of the work it should be doing then we would adopt it. But it’s just bad software and brining all of Linux down with it.
Wayland is not poorly designed or coded, screensharing works perfectly as long as the apps properly support wayland.
That’s not a problem with waylands design or code, that’s a problem with apps design or code, the thing you may want to take issue with is the notion that we could change things like this while still being poorly supported generally.
Back in the 80s/90s there were keyrings that would play an alarm if they heard a whistle at a particular frequency. You're basically playing Marco Polo with your keys.
I assume they lost popularity because the batteries tended to run out at inopportune times. Batteries are better now. Maybe it's time those things made a comeback.
It’s good to know amp sims and VSTs on Linux have come far! The drums still aren’t where I’d like them to be to switch and I’ve tried several times to get Steven Slate Drums and Superior Drummer working with a VST bridge in Ubuntu Studio, with no luck. Still sticking with Apple for now, but at least I finally have Windows out of my house.
Does Wayland allow for the running of a program on a big powerful server (where many users live) and display on a smaller desktop machine that is only providing a screen and keyboard? If not, are they working on that? If it does not and they are not working on it, is it even possible under the way that Wayland works?
Waypipe is not Wayland. Wayland does not natively support this workflow, which is why Waypipe was created. Please don’t confuse the two as being one thing.
You are giving me the impression that Waypipe is an extension to Wayland like XRANDR is to the X11 protocol. I didn’t get that impression from the blogpost. I’m not trying to place value on them being an extension or a separate tool. I’m just trying to figure out if it was a shortheaded response or if Waypipe is an extension to the Wayland protocol.
This may be “moving the goal posts”, if so I apologize in advance. With Waypipe can I have local windows and remote windows on my laptop? Will Waypipe work over a VPN (Tailscale is a VPN right?)
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.