Re: [solved, partly] Re: Grub menu entry for a system on a second drive.
On Thu, Oct 31, 2024 at 23:10:22 -0500, David Wright wrote:
> On Mon 28 Oct 2024 at 07:08:12 (-0400), Greg Wooledge wrote:
> > On Sun, Oct 27, 2024 at 22:42:15 -0500, David Wright wrote:
> > > type
> > > set -x
> > > before you run os-prober and
> > > set +x
> > > afterwards, and track what it does.
> >
> > os-prober is a script, so that won't work as written. You'd either
> > need to modify os-prober (change the second line from "set -e" to
> > "set -ex" for example) and then run it; or do something like:
> >
> > script
> > set -x
> > source /usr/bin/os-prober
> > exit
> >
> > (That assumes your interactive shell is bash.)
>
> I see what you mean. I guess one could make the shell explicit
> and then set x with:
>
> script
> bash -x /usr/bin/os-prober
> exit
>
> (I can't remember where I saw that construction.)
Yeah, that would actually be better, because it doesn't assume anything
about your interactive shell. Even better still would be
"sh -x /usr/bin/os-prober", since it's a #!/bin/sh script, not a bash
script.
Reply to: