None currently, because I live with my family and if I wanted to hide anything from them (which I don’t), I could just switch to a tty, or log out. Most of my work is done in VSCodium or Vivaldi, which save their sessions, although I have considered doing one just in case.
I thought that slock was too complicated so I wrote a tiny one for myself in Go using xgb. Less than 100 lines and pretty straightforward but it makes some assumption about my personal setup so not public. <a href=""></a> <a href=""></a>
Fedora is community owned, it’s just the upstream for RedHat. RHEL is based on Fedora. So I don’t really think there’s a cause for concern, unless RedHat uses its powers within the Fedora project (some people involved with the Fedora project are RedHat employees) to make things worse for Fedora but if they do, Fedora will lose users, so RHEL will lose free testers.
The amount of changes you’d need to make to get Linux to boot on a different partition format and drive would be a lot of work. It would be much faster to install a new copy of Linux to the nvme drive and copy the files from the ssd post install before decommissioning the old drive.
Thanks for the reply. I’m really dreading migrating files manually, because I use this as my server, so all my stuff would be down for an extended period of time while I migrated. :(
Is this mostly for fileserving or apps? If you’re using it as a Fileserver share the relevant parts of the ssd while you rsync all of it over to help ease downtime.
You can also install the nvme through a virtual machine and pass /dev/nvme_whatever to the vm. Then rsync everything over using ssh then reboot the whole machine using the nvme drive for the os (make sure to use UEFI for the vm on kvm).
For apps kinda the same vm deal leave the ssd up and configure the nvme install as needed then copy whatever data you need over before rebooting.
It’s more convoluted to do it that way but it will reduce downtime
I disagree, you usually just need to get /boot and your EFI things right on the new disk, rsync stuff over and fix any references to old disks in /etc/fstab and maybe your grub config and you are done. I have done this migration>10 times over the years onto different filesystems, partition Layout and raid configurations and it’s never been particularly hard.
That’s true if everything is supported on the current kernel. I might just be very out of touch/date here but is btrfs built in to the kernel? I was thinking he’d need to have a different kernel/loaded modules on it
Well dang it’s been a while since I tried it then! I keep hearing how it’s unstable in comments so I tend to assume its fairly new even when I should know better lol
Most of the time, it’s enough to copy the whole EFI partition to the new machine and update whatever boot entries are in there to point to the right new partitions.
In case of a switch to something like zfs, it’s a bit more involved and you need to boot a live Linux, chroot into the new “/” with /boot mounted and /dev, /proc, /sys bind mounted into the chroot.
Then you can run the distro-appropriate command to reinstall/ update grub into the EFI partition and they will usually take care of adding the right drivers.
I use arch because i like to do research mess with things and is fun, manjaro that’s what i would suggest anyone moving to Linux it’s just that good of a distro to use and mostly sre trolls so let them be.
i use arch, it’s amazing, everything i wanna do works other then games since i have some old cheap nvidia gpu which is hardware fault itself, i wanna do developer tasks just works, wanna do tweaks just works and it’s fun to use. i tried using other Distros i just can’t use debian based or arch based just bare bone arch with gnome or xfce depending on my mood. if i switch fedora is always my 2nd choice but not sure after some news released on red hat I didn’t stick to fedora because of lack of package or something like that just package management things kept me in arch.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.