At first I was like WTF but actually it makes sense. A screen showing an error code is much better than a hard reset, blinking cursor, kernel panic, or just black screen you usually get when something bad happens on linux.
The support for RAID56 is in development and will eventually fix the problems with the current implementation. This is a backward incompatible feature and has to be enabled at mkfs time.
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.
Not until I can have my pretty screensavers. Yes, I care. When my laptops are on battery they don’t need to S3 sleep, nor s0idle. They just show pretty animations that prompt for a password and let me in, without waiting ten years for it to wake up from its slumber
As people have said in some of the many, many other threads on this subject, if they really wanted to copy someone else's style of full-screen error message they'd have done much better to go with "Guru Meditation"
Yeah but how is the experience? While I’m not a fan of MacOS the polish and integration with the hardware is excellent. Hmm… I may need to see if I can dual boot this machine and check it out myself.
Haven’t tried myself but looking at a Mac for next time. Seems to be great experience and hardware integration somewhat up to speed. GPU issue is tackled a while back. asahilinux.orgmacdailynews.com/…/asahi-linux-on-an-apple-m1-mac… the fedora version was launched a few months back so I assume there is a lot to do. But active development and usable
What a sensational, over blown article. ArsTechnica this is shitty journalism and you should know it.
The headline would be about as correct if it said “SystemD update will bring Amiga’s Guru Meditation screen to Linux.”
This update has nothing to do with Windows. Error displays with additional information about the crash is not exclusive to windows, nor new. In fact a Kernel Panic screen happened in Unix.
The majority of linux articles have me checking the comments first to see if someone talks about ridiculous click bait crap, honestly saved me a lot of time.
I suppose that’s the main problem, I didn’t check the article since the title reeks clickbaity enough. However I wouldn’t share an article if the the title obviously is a clickbait, I’m sure there are bunch of respectable sources about this development.
Depends on specific machine setup and how good the backup is.
Backup requirements for /usr there are sticky bits set on some binaries. That needs to be preserved. In all cases soft links likely need to be preserved for things to work correctly on future package installs. Hard links can be problematic, but if you have a large enough drive or not that many it wont matter. Running package verification can be help after restore to make sure everything looks right. If running a Linux system with SELinux in enforcing mode (RHEL on many derivatives), then the security context will also need to be preserved BUT running a relabel will probably work if the security context was not included in backups. Sometimes running the relabel process wont work if there are files that needs a specific security context but are not listed in the security context database. Can’t provide more details because most of my experience with that is on systems we just replace (LSPP custom labeling resulted in systems that if you booted into permissive would then be unbootable, so they were just reinstalled once any debugging was done).
For /boot things can get tricky depending on the distribution, what boot manager is used, and /boot was a separate partition or not. Basically the boot manager (probably grub) needs to know how to find the files in boot so it can load the kernel. In most cases if you restore /boot and rerun the tools to update the boot manger everything will be fine. BUT some distributions, hardware setups, or dual boot configurations are more complicated, so extra work might be needed.
You didn’t mention /dev, which is all special files. These don’t need to be restored, just make sure the right processes recreate them. There are tools to do this, hopefully the packages are installed. Or boot from a rescue disk and fix it. Look up instruction for your specific distro.
I appreciate it, I was more so wondering whether or not I could keep my existing build as is aside from the GUI. I’ve done it the headless/CLI via ssh route previously but thought I’d check out using the GUI during the setup stages and being able to enable/disable the GUI at will and how that would affect performance vs installing only CLI at the start of the build.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.