Grub is basically superfluous in this modern era. At least it will not work with OpenZFS going forward. Just use any other UEFI bootloader.
Announcement
Collapse
No announcement yet.
GRUB 2.04 Release Candidate Brings Globs Of New Features
Collapse
X
-
Originally posted by fuzz View PostYes, my primary workstation is a dual socket Opteron board with a pair of Opteron 6344s. No UEFI, but still serves me well for many things.
Does not make GRUB any less superfluous in the modern (UEFI) era.
Comment
-
Originally posted by starshipeleven View PostAnd I still maintain a ton of Geode systems around the place with OpenWRT (yes they also use GRUB to boot) that are perfectly fine for basic firewall and IP phone server duties.
Does not make GRUB any less superfluous in the modern (UEFI) era.
It exists for hardware that is still in use in the "modern" era. Not superfluous.
With all the legacy stuff out there, I prefer software that is still in use gets maintained as long as possible -- if only for security patches.
America's Cities are Running on Software From the 80's
Comment
-
Originally posted by fuzz View PostSuperfluous: "Being beyond what is required or sufficient."
It exists for hardware that is still in use in the "modern" era. Not superfluous.
But legacy hardware isn't what is most common.
I always said USA is a third world country.
The issue isn't running 80s software, the issue is gross mismanagement of this software so that it can't be just put in a VM and run on a server, while people use a modern frontend for it.
Some more laughs https://arstechnica.com/information-...has-no-backup/
Comment
-
Originally posted by hreindl View Postshow me how i get /boot as RAID1 with UEFI so that it don't matter which of my 4 disks are dying
Have you never seen the warning mdadm spews when you build an array?
Code:mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90
For the UEFI partition you can just set up a generic rEFInd setup (i.e. refind as /EFI/BOOT/bootx64.efi) and then copy the partition to all the disks and never touch them again, or keep a single one on a USB drive inside the server.
I never tried RAID-ing the UEFI partition itself (as with rEFInd it's static, no changes need to be synced) but it should theoretically work too with this method.
Comment
-
Originally posted by monraafNot every system in the world is EFI, there are also a lot of systems which use OpenFirmware (IEEE1275), for example.
But yeah ok fair enough, I was implicitly assuming x86 and ARM devices used in IT, not industrial or embedded.
Comment
Comment