Re: cp: cannot stat '/usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32': Not a directory

Eventually ... remembering these are 'just' scripts ...

Changing:

cp $LDLINUXE64/../libutil.c32 $efidir 2>> $LOGFILE || Die "Cannot copy
$LDLINUXE64 to $efidir). Did you run out of disk space

To:

# cp $LDLINUXE64/../libutil.c32 $efidir 2>> $LOGFILE || Die "Cannot copy
$LDLINUXE64 to $efidir). Did you run out of disk space

cp /usr/lib/syslinux/modules/efi64/libutil.c32 $efidir 2>> $LOGFILE ||
Die "Cannot copy $LDLINUXE64 to $efidir). Did you run

Let's me get through that and on to the next issue.

Granted, it's not a good / robust change, but it's not like this
system's going to change its lib paths.


On 05/29/2017 02:14 AM, B. S. wrote:
> Echoing a report from 2016-10-15 21:57:10,
> https://sourceforge.net/p/mondo/mailman/message/35430469/ ...
> 
> <<<<<
> Trying to back up my UEFI-based Fedora 24 system. First, there was a
> whine about syslinux.efi missing. I dug up that from the syslinux folks
> and installed it, not I'm getting an issue regarding copying stuff to
> the temp directory...specifically "cp: cannot stat
> '/usr/share/syslinux/efi64/ldlinux.e64/../libutil.c32': Not a directory".
> 
> Near as I can tell ldlinux.e64 is a file, not a directory.
> 
> 
> I'm including the mindi.log from this. Perhaps you can have a look.
> 
> 
> Rick Stevens, Systems Engineer
> AllDigital, Inc.
>>>>>>
> 
> Same thing happening here on a new Debian Stretch system.
> 
> What goofy strange thing has Linux done now?
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32
> ls: cannot access
> '/usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32': Not a
> directory
> 
> Which triggers at the end of the (failing) mindi log:
> 
> -----------------------------------
> INFO: Found ldlinux.c32 at /usr/lib/syslinux/modules/bios/ldlinux.c32
> INFO: Found syslinux.efi at /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi
> INFO: Found syslinux boot type
> INFO: Found ldlinux.e64 at /usr/lib/syslinux/modules/efi64/ldlinux.e64
> INFO: Copying /usr/lib/syslinux/modules/efi64/ldlinux.e64 to
> /tmp/mindi.qAJsbZsfqX/bigdir/EFI/BOOT
> cp: cannot stat
> '/usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32': Not a
> directory
> FATAL ERROR. Cannot copy /usr/lib/syslinux/modules/efi64/ldlinux.e64 to
> /tmp/mindi.qAJsbZsfqX/bigdir/EFI/BOOT). Did you run out of disk space?
> 
> 
> -----
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/ldlinux.e64
> -rw-r--r-- 1 root root 132K Jan 28 13:39
> /usr/lib/syslinux/modules/efi64/ldlinux.e64
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/libutil.c32
> -rw-r--r-- 1 root root 24K Jan 28 13:39
> /usr/lib/syslinux/modules/efi64/libutil.c32
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32
> ls: cannot access
> '/usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32': Not a
> directory
> 
> -----
> 
> Since when has '../file' constructs stopped working as they always have?
> 
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/ldlinux.e64/..
> ls: cannot access '/usr/lib/syslinux/modules/efi64/ldlinux.e64/..': Not
> a directory
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/ldlinux.e64
> -rw-r--r-- 1 root root 132K Jan 28 13:39
> /usr/lib/syslinux/modules/efi64/ldlinux.e64
> 
> $ ls -l /usr/lib/syslinux/modules/efi64
> ... lots of files.
> 
> $ ls -l /usr/lib/syslinux/modules/efi64/libutil.c32
> -rw-r--r-- 1 root root 24K Jan 28 13:39
> /usr/lib/syslinux/modules/efi64/libutil.c32
> 
> -----
> 
> $ ls /etc/apt/apt.conf.d/70debconf
> /etc/apt/apt.conf.d/70debconf
> $ ls /etc/apt/apt.conf.d/../sources.list
> /etc/apt/apt.conf.d/../sources.list
> 
> -----
> 
> Something special about some things?
> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot