It’s not like you can’t shoot yourself in the foot while using windows (not sure about macs, tho, but likely just as well). I remember breaking windows countless times while figuring out what service crap can be disabled, removing edge or defender, yada yada.
On the contrary, in my experience, if you’re not actively messing with linux, it’s overall more stable than windows. Like I had to install windows on an actual machine a short while ago, and it was a clusterheck. Drivers failed to auto install (touchpad/trackpoint drivers, for Chaos’s sake), random bsod after an hour or so of normal use, etc. As for linux breaking on itself, I remember like 3 times that happened with me in my ~5 yrs of daily driving different distros, and 2 of those were fixable by switching to a tty (the 3rd didn’t boot, as far as I remember, due to some incompatibility between bedrock and arch).
A system update broke a dependency for libre Sprite, which hasn’t had an update in like two years. You can say they should but let’s be real, my apps shouldn’t break with an update. One of my laptop needs was portable graphics creation. This broke one of my major use cases. Yay.
Actually, I have a story that I’d consider an achievement even though it was extremely stupid and by all accounts should’ve bricked the system but didnt.
So I was on windows and wanted to install linux as a dual-boot on the main drive. The problem was that my mobo didnt like this particular and the only flash drive I’ve had, dropping it out mid-boot, before I got any usable terminal, so a usual install method wasn’t an option. So I had this crazy idea to start a vmware vm in windows and pass the linux iso and the boot drive directly to it and try to install it live over the running system. Unfortunately, vmware guys thought of this and there’s a check that disallows passing the boot drive to vms. So i created a bunch of .vmdks for another drive and fiddled with them in notepad until I somehow managed to trick vmware and at some point it started booting the same windows copy that I was sitting on. I quickly powered it off, added the linux iso and proceeded to install like I usually would. It did involve some partition shuffling, but, somehow, it went smoothly, linux installed, grub caught on, and even windows somehow survived, even though it was physically moved around on the disk. It serms that vmware later patched this out, because later in an attempt to re-create the trick of running the same copy of windows twice, but after updates to both windows and vmware, I was met with the same old error that boot drive is not allowed when trying to add that same virtual drive I had laying around.
I had a similar debacle, when I managed to corrupt a btrfs file system to point it wouldn’t mount again…
I was preparing it to have as my main system on bare hardware. I had accidentally mounted the same block device simultaneously in the host and guest: kablamo silent corruption and all 5 hours of progress lost.^*^ :(
I had a similar setup once. Dualboot, plus the VM with the same physical disk, to access windows, while running linux.
All it took was a small distraction… I’ve missed the grub timeout, and accidentally booted the same ubuntu partition in a VM that was running on the real HW. To shreds…
Allrighty, now we officially need a program (I’m hesitant to call it malware since technically it’s for the user’s good XD) that covertly replaces a running copy of windows with linux… Besides, I think it was possible before to install stuff like Ubuntu directly from windows?
Why would I want to use this instead of AWS Session Manager? I have a policy of no SSH enabled on any of my servers. Is this compatible with SSM connections too?
The screenshots are just sample connections, you can connect to arbitrary systems via SSH so it is not really a tool intended specifically for AWS.
Obviously if you are using taylor made tools for AWS by amazon itself, XPipe can probably not compete with that in terms of features. This is more of a general purpose application that you can use with any servers, virtual machines, containers, and more.
I’ve learned from Brodie’s video that Ubuntu upload schedule is basically slightly different gnome’s schedule. So, KDE with rolling releases is what I think is best.
Though IIRC the scheduling of plasma 6 onward will follow gnome’s 6 month period to synchronize with bimonthly releases of distros that does it.
It sounds like the issue is with the lid latch/sensor, not with the graphics. Some laptops may not boot if the lid is closed, and some have options on the firmware to enable to boot when the lid is closed / on a docking station.
This seems unlikely since it boots with a monitor attached. From past experience most laptops that refuse to boot while closed don’t boot even if an HDMI display is connected.
I had an old laptop that I removed the screen from and it still booted. Perhaps if your screen has broken in a way that the GPU detects as a hardware failure, it might prevent booting? Maybe removing the screen entirely might solve the issue? Or at least disconnecting the internal cable from the screen to the motherboard…
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.