From: forkosh@panix.com   
      
   I've got a regular old fdisk/lilo-based non-uefi boot drive,   
   but the latest (-current64 as of 2/7/23) version created   
   a usb install stick that warned me it couldn't find any   
   efi partitions, and that lilo wouldn't work (which indeed   
   it didn't) and that I'd have to boot from a usb stick.   
   Fortunately, I didn't have to do that (boot from usb) since I was   
   installing on /dev/sda4 and already had an an older slackware   
   on /dev/sda1 with lilo on the mbr, and only had to add an   
   sda4 section to that lilo.conf, and then rerun lilo from there.   
   But I'll eventually want to update that sda1 partition, too,   
   which is slackware from Sept 2019, and had no such efi problem   
   when installed back then.   
      
   So how do you make a -current install usb that just recognizes   
   non-efi fdisk partitions? What I'd done, as usual for me, is   
     rsync -av rsync://mirrors.kernel.org/slackware/slackware64-current/  \   
     myslackwaredirectory/   
   and then ran the usb-and-pxe-installers/usbimg2disk.sh script.   
   But now that I think about it, maybe it did say something about   
   uefi when it ran??? But I'm not seeing anything related to that   
   in the script itself (not so far as I can tell, anyway).   
   Is there any -switch or anything else like that creating   
   the usb boot/install stick? Or, in general, how do you create   
   a usb install stick that will install and correctly run lilo   
   on fdisk partitions, without any efi complaints?   
   --   
   John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)