GNU GRUB - Bugs: bug #60821, searh --file command does not work...
You are not allowed to post comments on this tracker with your current authentication level.
bug #60821: searh --file command does not work for full path
Submitter: | Vladimir <svv75> | ||
Submitted: | Fri 25 Jun 2021 04:01:17 AM UTC | ||
Category: | Filesystem | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Vladimir |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
Hello!
I found that the search command for a file does not work if the file path is complete. That is, the path already contains the device name and disk partition. For example, "search --file (hd0, gpt1)/EFI/BOOT/grub.cfg" returns "no such device" instead of "(hd0, gpt1)". This is a serious problem. I discovered this on Yocto. There, a similar command was used in early GRUB configuration to extract the device and partition from the "cmdpath" variable. And it always doesn't work. It is strange that there are no complaints about this. This problem also exists in GRUB 2.04 and 2.06. Hope it gets resolved.
Best regards,
Vladimir