You are not logged in.
ceel@slitaz:~$ tazpkg -lf ipxe
Installed files by "ipxe"
================================================================================
/boot/ipxe.exe
================================================================================
1 file
ceel@slitaz:~$ tazpkg -lf memtest
Installed files by "memtest"
================================================================================
/boot/memtest.exe
================================================================================
1 file
ceel@slitaz:~$
Offline
Hi Ceel,
In the Linux you can use any names and name extensions for executable files. But in addition to this fact I think here should be a bit different.
Afaik these executables are intended to be executed from the boot loader like Syslinux. This time no OS loaded yet, no system libraries are available, so these executables are static.
And afaik these executables are NOT in the commonly used ELF format, but in the some DOS-like format.
You can install "file" package and test these files if you're interested.
Offline
Hi Aleksej,
I agree with you.
I don't think the bootloaders is affected by the extensions files but its configuration file is.
So for web boot for instance, [c]kernel /boot/ipxe[/c] won't find ipxe.exe :-p
Offline
- ipxe.exe & memtest.exe are DOS executables (like linld.com). DOS/Win9x users can launch them.
- they have a Linux kernel format too. Linux loaders (like isolinux) can launch them.
- they have a disk image format too. You can put it on a floppy (or USB key/memory card) with cp/dd.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]