Your chances are pretty good if you copy them back - ultimately, that’s what the restoration function of backup software does.
As for ownership of the directories and files, that’s a bit trickier and might involve some trial and error. root:root is a safe bet for most of it, but there is a lot of stuff in /var that is owned by system accounts.
What distro are you running? That’ll help figure it out.
I’m running Fedora 39 KDE. I think I’m going to see what the file metadata of my other Fedora systems look like and try to replicate that. Worst case I just reinstall. At this point I’m a little curious how the system will react.
I won’t buy a laptop without it. My earlier Dell Precision had it, but under warranty they ended up replacing it for a slightly “better” model, because the damage from the swollen battery was too hard to repair. I hate the new one. I have to make this 64gig laptop hibernate to get close to what I had with S3 sleep… but it’s nowhere near instant. I hate them for doing that to me. And this newer laptop (Precision 5550) keeps losing screws and it has stray clicks from the chassis flexing when you try to pick it up. Miss the old one. Think it was a 5540.
I was about to say the same. I usually run Dell XPS or Macs. The good thing about Macs is that the sleep modes and stuff all work really really well. The XPSs are solid, and the hardware support in Linux is pretty good.
A notable third entry recent entry for me is framework. Customizable, upgradable and not too expensive (when compared to the other two), it’s a great option.
So I don’t get it, I have my entire boot image in a signed EFI binary, the logo is in there as well. I don’t think I’m susceptible to this, right? I don’t think systemd-boot or the kernel reads an unsigned logo file anywhere. (Using secure boot)
Depending on how the UEFI is configured, a simple copy/paste command, executed either by the malicious image or with physical access, is in many cases all that’s required to place the malicious image into what’s known as the ESP, short for EFI System Partition, a region of the hard drive that stores boot loaders, kernel images, and any device drivers, system utilities, or other data files needed before the main OS loads.
Right, I know EFI images are stored in the EFI partition, but with secure boot, only signed images can be executed, so they’d need to steal someone’s signing key to do this.
The longer you spend in these internet communities, the more you’ll realize there’s a substantial amount of losers who can’t form their own opinions. They’ll just repeat whatever is popular in order to fit in.
I am not gonna lie… Hardware video acceleration on Linux has traumatized me so much. I have spend soooooo much time over the years dealing with this shit. I has gotten better, i admit. But before you had to make sure all the stars aligned perfectly to make this shit work properly. Hell, even last week i found out that hardware video acceleration did not seem to work on twitch.tv on my firefox browser. After 2 days of reinstalling my Linux distro, drivers, many different ways of running firefox such as the rpm version, flatpak etc. I found out opensuse removed the mesa drivers that included the codecs i needed… i found out about it through some old reddit post comment with 2 upvotes… Even now i am having issues with running sunshine streaming. And it drives me insane because it SHOULD work. But it doesn’t. It could be the flatpak not having correct access. It could be the driver. It could be wayland. I don’t even know anymore… it just refuses to find available codecs. Then i tried steam remote play instead. And it streams… a black screen with only my cursor showing.
I don’t know anymore. I don’t care anymore.
Oh another fun one is geforce now. On Linux if you use hardware acceleration, a certain part of the grey/black color spectrum is missing from the video stream. So games are quite darker and it makes games like dead by daylight completely unplayable as most dark spots are completely black. If you run it without hardware acceleration it works fine… but then you get very bad lag, stuttering and slowmotion at higher bitrate. So that is also unplayable.
Hardware video acceleration on Linux is a disaster and really deserves more attention. Every now and then it works and then something updates and everything is broken again. I currently just dual boot because i use sunshine and geforce now a lot.
Sorry for the long rant. I didn’t know i typed this much. But it honestly really deserves some attention as it can really mess up the users experience. Often without their knowledge.
Yes, in my opinion. The configuration of grub (boot loader) is just another step to go wrong, and this will eliminate that possibility. Additionally, it will prevent stupider operating systems (cough Windows) from accidentally overwriting the boot loader during an update.
It basically means instead of relying on a bootloader (e.g. GRUB or systemd-boot) the computer boots the kernel directly. Generally there should be no change besides having to use the BIOS menu to manually select a kernel.
FWIW, a lot of the DIY distros (Arch and Gentoo being the ones on most minds) allow this already so it’s nothing new. It’s just Fedora implementing it that’s new I guess. If you’re curious, the term to search is “EFISTUB”.
I think for most people they won’t care either way.
Some people do legitimately occasionally need to poke around in GRUB before loading the kernel. Setting up certain kernel parameters or looking for something on the filesystem or something like that. For those people, booting directly into the kernel means your ability to “poke around” is now limited by how nice your motherboard’s firmware is. But even for those people, they should always at least have the option of setting up a 2-stage boot.
I’ve had it break many times during update. Don’t get me wrong, I liked it at first, but if you want a system that works after update, you’re probably better checking elsewhere. Linux Mint, and Kubuntu are far better simplicity wise. Open Suse or Arch if you want rolling updates.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.