On 4/13/21 2:16 PM, Takashi Iwai wrote:
On 4/13/21 1:23 PM, Olaf Hering wrote:
Am Mon, 12 Apr 2021 14:37:23 -0700 schrieb L A Walsh
: You may have noticed, YaST does not propose a partition for /boot anymore since more than a decade. Well, Yast does not propose RAID10 (with o3 parity - 3 disks in mirror for very high reliability and more than double read speed), but if you want it you can create it in the Partitioner. Yast proposes BTRFS, but I don't want it, so I can use XFS - also from Yast Partitioner. Yast does not propose /boot, but if you try to put / on RAID10 it will warn you that system won't be bootable. Proposal is just that, you don't have to accept it. If I wanted something without control, I'd use Ubuntu or Centos... I don't think that the proposal is about breaking such installations. Instead of putting the stuff like vmlinuz and initrd under /boot
On Tue, 13 Apr 2021 13:36:35 +0200, Sinisa wrote: directly, keep those in the normal place. /boot IS normal place for those And for the system that needs the extra /boot partition, we may tweak somehow, e.g. creating symlinks Won't work, grub couldn't read symlink target. If it could, we wouldn't need /boot partition. or copying the files in post script or such. This might work, but we would need to remember that when manually tweaking things. This sounds like a feasible option. But we have to be really careful; as usual, devils living in details...
Takashi To me, this seems like a "change just for the sake of change". I can see no improvement in that, just more complications. Sort of remind me of that "other OS", where they change things for no real reason...
/boot was/is working since forever, people know about it and know how to handle it. But hey, this is just my ¢2. I got used to "systemctl restart xxxx" instead od "rcxxxx restart", I'll get used to new /boot if necessary. (btw, that was a lie, I still use rcxxxx commands) Srdačan pozdrav / Best regards / Freundliche Grüße / Cordialement / よろしくお願いします Siniša Bandin