Hi,
i am working on a patch to let GRUB delay the execution of a ISO 9660
SUSP CE hop until the current SUSP area is consumed. Currently it hops
immediately which is wrongly relying on implementation details of the
ISO producer. SUSP 1.12 specs are clear. Linux obeys them.
The code works but the test makes problems because grub-fstest adds a
blank to the filename. That's probably a preparation for the next name
to be listed and a bit inappropriate with the last and only name of the
output list.
Is this behavior of grub-fstest reliable ?
Do other tests already handle such blanks ? If so: how ?
May i expect the trailing blank in the test ? Like:
# grub-fstest adds a blank to the name. So expect that blank too.
if [ "${ret:-0}" -ne 0 -o x"$output" != x"RockRidgeName:x " ]; then
I fail to find the answers in ./grub-fs-tester .
Have a nice day :)
Thomas
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
