From: syl@therockgarden.ca   
      
   On 2025-01-29, root wrote:   
      
   > After following through on this, I assert that grub is *NOT* on   
   > the slackware 15.0 install iso. Moreover, elilo did not work.   
      
   Ah ... then perhaps the FILELIST.TXT file is simply incorrect?   
      
      : elvira[syl] ~; grep -is grub /local/var/slackware/slackware   
   4-15.0/FILELIST.TXT   
      -rw-r--r--  1 root root        78 2013-09-23 20:35 ./EFI/BOOT   
   grub-embedded.cfg   
      -rw-r--r--  1 root root       893 2018-04-17 21:17 ./EFI/BOOT/grub.cfg   
      -rwxr-xr-x  1 root root      2504 2019-07-05 18:54 ./EFI/BOOT/make-grub.sh   
      -rw-r--r--  1 root root       182 2021-09-10 18:45 ./slackwar   
   64/a/grub-2.06-x86_64-4.txt   
      -rw-r--r--  1 root root  10176528 2021-09-10 18:45 ./slackwar   
   64/a/grub-2.06-x86_64-4.txz   
      -rw-r--r--  1 root root       163 2021-09-10 18:45 ./slackwar   
   64/a/grub-2.06-x86_64-4.txz.asc   
      -rw-r--r--  1 root root       202 2022-01-04 21:34 ./slackwar   
   64/kde/breeze-grub-5.23.5-x86_64-1.txt   
      -rw-r--r--  1 root root   3140496 2022-01-04 21:34 ./slackwar   
   64/kde/breeze-grub-5.23.5-x86_64-1.txz   
      -rw-r--r--  1 root root       163 2022-01-04 21:34 ./slackwar   
   64/kde/breeze-grub-5.23.5-x86_64-1.txz.asc   
      drwxr-xr-x   2 root root     4096 2021-09-10 18:39 ./source/a/grub   
      -rw-r--r--   1 root root      291 2021-09-10 18:33 ./source/a   
   grub/0001-skip-new-files-in-etc-grub.d.patch.gz   
      -rw-r--r--   1 root root      639 2018-05-16 15:18 ./source/a   
   grub/0198-align-struct-efi_variable-better.patch.gz   
      -rw-r--r--   1 root root     1743 2021-09-09 03:04 ./source/a   
   grub/a4b495520e4dc41a896a8b916a64eda9970c50ea.patch.gz   
      -rw-r--r--   1 root root      307 2021-09-10 18:36 ./source/a   
   grub/doinst.sh.gz   
      -rw-r--r--   1 root root      926 2016-06-13 03:14 ./source/a   
   grub/etc.default.grub   
      -rw-r--r--   1 root root  6581924 2021-06-08 17:22 ./source/a   
   grub/grub-2.06.tar.xz   
      -rw-r--r--   1 root root      566 2021-06-08 17:22 ./source/a   
   grub/grub-2.06.tar.xz.sig   
      -rwxr-xr-x   1 root root     7468 2021-09-10 18:35 ./source/a   
   grub/grub.SlackBuild   
      -rw-r--r--   1 root root      704 2016-12-25 09:49 ./source/a   
   grub/grub.dejavusansmono.gfxterm.font.diff.gz   
      -rw-r--r--   1 root root      299 2012-09-29 04:34 ./source/a   
   grub/initrd_naming.patch.gz   
      -rw-r--r--   1 root root      634 2018-11-29 19:15 ./source/a   
   grub/slack-desc   
      -rw-r--r--   1 root root         2 2021-10-14 16:34 ./source/   
   de/kde/build/breeze-grub   
      -rw-r--r--   1 root root        95 2016-04-11 07:41 ./source/   
   de/kde/post-install/breeze-grub.post-install   
      -rw-r--r--   1 root root       661 2020-11-01 20:11 ./source/   
   de/kde/slack-desc/breeze-grub   
      -rw-r--r--   1 root root   3154068 2022-01-04 09:49 ./source/   
   de/kde/src/plasma/breeze-grub-5.23.5.tar.xz   
      -rw-r--r--   1 root root       833 2022-01-04 09:49 ./source/   
   de/kde/src/plasma/breeze-grub-5.23.5.tar.xz.sig   
      
   Others have suggested you use grub2, and I've indicated that it is   
   indeed there in the local mirror I have (with timestamps matching the   
   above, in fact).  It must be that we're all mistaken, then.  (have you   
   checked that your installation disk is complete?  Have you *looked* on   
   the installation disk in the "a" subset?  Did you know that you can?)   
      
      
   > After the install stopped chugging away I was asked about   
   > lilo and I declined. I installed elilo instead. When   
   > the install finished I did not reboot, I did   
   > which grub and which grub2, neither came up.   
   > So I exited and rebooted the system.   
   >   
   > Upon boot the elilo stuff came up and delivered   
   > some messages like installing intrd and something   
   > else, but the system just locked up after that.   
      
   You didn't create an initrd and re-run (e)lilo prior to rebooting.   
   Common mistake.  Mildly annoying when it happens, but easily   
   recoverable in general.   
      
   > ...   
   > It shouldn't be this much trouble.   
      
   I agree that it shouldn't be, but I'm inclined to think that perhaps   
   you simply haven't read enough about how this is supposed to work.   
      
   One of the great things about Slackware is that it will not try   
   to protect you from your own lack of knowledge.  The system will   
   gleefully do as you say, right from the get-go.  As great as that is,   
   it can be a cause of grief if you try to proceed with either incomplete   
   or incorrect information (such as that which might be applicable to   
   other Linux distributions).   
      
   Here's what I suggest at this point:   
      
      Get Slackware running on a non-UEFI system, and get to really   
      know how it works.  Get to a point where something like Ubuntu   
      (or many others, either "deb" derivatives or "rpm" derivatives)   
      is something you can work with (for example if your employer needs   
      it), but thanks to experience with Slackware, you understand what's   
      really going on behind the scenes with them.  THEN go ahead and   
      install Slackware on a UEFI system.  You won't have any of the   
      trouble you've been ranting about here.  If, on the other hand, you   
      continue to just poke around in the dark, well ...   
      
   --   
   ----------------------------------------------------------------------   
   Sylvain Robitaille                                syl@therockgarden.ca   
   ----------------------------------------------------------------------   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)