You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
I have been trying using -f with wildcards in some .sh batch files with * and have been seeing errors or it just does not work sometimes.
In this case I was testing my own version of loop_detect.sh from grubfm.
There seems to be a problem with memory maybe ??
I see you use wildcards in loop_detect.sh so I assumed they should work.
This is UEFI64 boot to grubfm.
On first run it works, but during testing .sh files multiple times, it stops working and I have to reboot.
I have seen this behaviour on many different versions of grubfm so I don't think it is version specific.
It happens on both NTFS and FAT32 volumes so it is not specific to one filesystem.
Note that specifying the exact filename always works, so it is something to do with using wildcards.
Have you ever come across this?
The text was updated successfully, but these errors were encountered:
OK, my bad test in console, but I used code where I have not used quotes and it did not work until a reboot.
There is something odd about using wildcards sometimes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have been trying using -f with wildcards in some .sh batch files with * and have been seeing errors or it just does not work sometimes.
In this case I was testing my own version of loop_detect.sh from grubfm.
There seems to be a problem with memory maybe ??
I see you use wildcards in loop_detect.sh so I assumed they should work.
This is UEFI64 boot to grubfm.
On first run it works, but during testing .sh files multiple times, it stops working and I have to reboot.
I have seen this behaviour on many different versions of grubfm so I don't think it is version specific.
It happens on both NTFS and FAT32 volumes so it is not specific to one filesystem.
Note that specifying the exact filename always works, so it is something to do with using wildcards.
Have you ever come across this?
The text was updated successfully, but these errors were encountered: