At least the ISO would comply to the specs, although this is in no way
mandatory for boot success. :))
> this does not address the /EFI/BOOT consideration at this point
Akeo has a valid point with demanding support for the method of unpacking
the ISO content to a FAT filesystem. Not only is it less dangerous than
our flat image copy onto the whole USB stick, but it is also something
that MS-Windows users are used to.
The price for having a copy of the EFI partition tree in the ISO should
be bearable.
On the other hand, this won't work with legacy BIOS (at least not without
tricky post-processing of ISOLINUX) and it invites problems with filenames.
Being a mere sponsored uplader, i fail to find the description how the
version gets transmogrified before becomming part of the .deb file name.
If it is clear that no ":" can sneak in via version, this risk about FAT
filenames would be much reduced.
(There remains the risk of stubborn package maintainers, though.)
I understand from Akeo's initial protest that currently the filenames in
Ubuntu ISOs are not an obstacle for the copy method which he defends.
Nevertheless, it would be re-assuring if there was a rule or algorithm
which prevents ":" from getting into .deb names.
Hi,
Steve Langasek wrote: /lists. debian. org/debian- cd/2019/ 07/msg00007. html was very
> Reading https:/
> helpful in clarifyingthe options needed to get the image structure we
> are looking for.
At least the ISO would comply to the specs, although this is in no way
mandatory for boot success. :))
> this does not address the /EFI/BOOT consideration at this point
Akeo has a valid point with demanding support for the method of unpacking
the ISO content to a FAT filesystem. Not only is it less dangerous than
our flat image copy onto the whole USB stick, but it is also something
that MS-Windows users are used to.
The price for having a copy of the EFI partition tree in the ISO should
be bearable.
On the other hand, this won't work with legacy BIOS (at least not without
tricky post-processing of ISOLINUX) and it invites problems with filenames.
This brings me to a question about .deb file names. /packages. debian. org/sid/ allpackages? format= txt.gz ftp.de. debian. org/debian/ pool/main/ a/a2ps/ a2ps_4. 14-5_amd64. deb
I see in
https:/
that many packages have version texts with ":". Like
a2ps (1:4.14-5 [alpha, amd64, ...
But the .deb file of a2ps does not show the "1:" part:
http://
Being a mere sponsored uplader, i fail to find the description how the
version gets transmogrified before becomming part of the .deb file name.
If it is clear that no ":" can sneak in via version, this risk about FAT
filenames would be much reduced.
(There remains the risk of stubborn package maintainers, though.)
I understand from Akeo's initial protest that currently the filenames in
Ubuntu ISOs are not an obstacle for the copy method which he defends.
Nevertheless, it would be re-assuring if there was a rule or algorithm
which prevents ":" from getting into .deb names.
Have a nice day :)
Thomas