Re: TW slow to process "post trans script" grub2-i386????
Side note:
The way you post, using digests, breaks threading and makes difficult to follow your posts. I can not easily go back and find out how this issue started.
Carlos: Historically my participation here has been minimal, so digest made/makes sense; but is there another way to make posts into the list-serve, directly on a site?? Otherwise I suppose searching my name on the list search engine??
No, you don't have to edit entries ever.
There are two ways.
One, you use the kernel link:
Telcontar:~ # ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 36 Feb 19 22:27 /boot/vmlinuz -> vmlinuz-5.14.21-150400.24.46-default Telcontar:~ # ls -l /boot/initrd lrwxrwxrwx 1 root root 35 Feb 19 22:27 /boot/initrd -> initrd-5.14.21-150400.24.46-default Telcontar:~ #
Two, you don't create entries for the kernels, but to the grub of those partitions:
cat /boot/grub2/custom.cfg
# If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Needed for changes to the default boot to hold.
menuentry 'Gestor (por uuid)' --id cer-gestor-001 { insmod part_gpt insmod ext2 set root='hd2,gpt2' if search --no-floppy --fs-uuid --set=root 943d6... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi }
menuentry 'oS 12.3, sda1 (label aux_extrasys)' --id cer-sda1-001 { insmod part_msdos insmod ext2 set root='hd0,msdos1' if search --no-floppy --fs-uuid --set=root 3f87... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi }
Thanks for providing that information, right now it doesn't entirely make sense to this non-computer literate reader, seems like there are language changes in the data?? I'll have to read through it many times to get it cleared up . . . . One other issue is again the Mac & EFI aspect to the machine, no "msdos1" is involved.
On 2023-03-17 15:50, Fritz Hudnut wrote:
Side note:
The way you post, using digests, breaks threading and makes difficult to follow your posts. I can not easily go back and find out how this issue started.
Carlos:
Historically my participation here has been minimal, so digest made/makes sense; but is there another way to make posts into the list-serve, directly on a site?? Otherwise I suppose searching my name on the list search engine??
I think you can see the mail list via news. And least you could. <https://lars.ingebrigtsen.no/2020/01/15/news-gmane-org-is-now-news-gmane-io/> Otherwise, change your subscription to normal while you are participating actively.
No, you don't have to edit entries ever.
There are two ways.
One, you use the kernel link:
Telcontar:~ # ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 36 Feb 19 22:27 /boot/vmlinuz -> vmlinuz-5.14.21-150400.24.46-default Telcontar:~ # ls -l /boot/initrd lrwxrwxrwx 1 root root 35 Feb 19 22:27 /boot/initrd -> initrd-5.14.21-150400.24.46-default Telcontar:~ #
This means that grub doesn't have to point at the actual kernel name, like "vmlinuz-5.14.21-150400.24.46-default", but point to "vmlinuz" which is _always_ the current kernel.
Two, you don't create entries for the kernels, but to the grub of those partitions:
cat /boot/grub2/custom.cfg
# If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Needed for changes to the default boot to hold.
menuentry 'Gestor (por uuid)' --id cer-gestor-001 { insmod part_gpt insmod ext2 set root='hd2,gpt2' if search --no-floppy --fs-uuid --set=root 943d6... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi }
menuentry 'oS 12.3, sda1 (label aux_extrasys)' --id cer-sda1-001 { insmod part_msdos insmod ext2 set root='hd0,msdos1' if search --no-floppy --fs-uuid --set=root 3f87... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi }
Obviously, you'd have to adjust for your case. They are simply two entries from my system. I have no idea how it would be for Mac partitions, but you can find that information in the automatic configuration file, /boot/grub2/grub.cfg
Thanks for providing that information, right now it doesn't entirely make sense to this non-computer literate reader, seems like there are language changes in the data?? I'll have to read through it many times to get it cleared up . . . . One other issue is again the Mac & EFI aspect to the machine, no "msdos1" is involved.
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-03-18 13:21 (UTC+0100):
Telcontar:~ # ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 36 Feb 19 22:27 /boot/vmlinuz -> vmlinuz-5.14.21-150400.24.46-default Telcontar:~ # ls -l /boot/initrd lrwxrwxrwx 1 root root 35 Feb 19 22:27 /boot/initrd -> initrd-5.14.21-150400.24.46-default Telcontar:~ #
This means that grub doesn't have to point at the actual kernel name, like "vmlinuz-5.14.21-150400.24.46-default", but point to "vmlinuz" which is _always_ the current kernel.
Usually it points to the most recently installed kernel from a standard location (for Leap: distribution/leap/15.4/repo/oss/, or update/leap/15.4/sle/), but /not/ always. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-03-18 14:44, Felix Miata wrote:
Carlos E. R. composed on 2023-03-18 13:21 (UTC+0100):
Telcontar:~ # ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 36 Feb 19 22:27 /boot/vmlinuz -> vmlinuz-5.14.21-150400.24.46-default Telcontar:~ # ls -l /boot/initrd lrwxrwxrwx 1 root root 35 Feb 19 22:27 /boot/initrd -> initrd-5.14.21-150400.24.46-default Telcontar:~ #
This means that grub doesn't have to point at the actual kernel name, like "vmlinuz-5.14.21-150400.24.46-default", but point to "vmlinuz" which is _always_ the current kernel.
Usually it points to the most recently installed kernel from a standard location (for Leap: distribution/leap/15.4/repo/oss/, or update/leap/15.4/sle/), but /not/ always.
Ok, it can fail. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (3)
-
Carlos E. R. -
Felix Miata -
Fritz Hudnut