On Tue, Sep 21, 2021 at 10:49:30AM +0300, Eric Pozharski wrote:
> On Mon, Sep 20, 2021 at 09:08:16AM -0400, Hendrik Boom wrote:
> > On Sun, Sep 19, 2021 at 10:31:19PM -0500, golinux@??? wrote:
> > > On 2021-09-16 22:30, golinux@??? wrote:
>
> *SKIP*
> > The command for finding the correct display driver:
> > root@devuan:~# apt-cache search xserver-xorg-video-.* | pager
> > Shouldn't the '*' be quoted in some manner so that the apt-cache
> > command gets to interpret it instead of the shell:
>
> No, it might not. It's bashism (zsh has special option to let filename
> generation fail, and it's unset by default; while bash)
>
> % bash
> bash-5.1$ echo abc*
> abc*

So if there's no file matching the pattern, bash leaves the pattern as is
without replacing it with nothing?

Interesting. I'll have to think twice before I use * in a file name in
a shell command.

At least
    rm abc*
will still remove a file actually called abc*

Net question: how to get a '/' in a file name instead of having it
interpreted as a separator in a path.
I needed it once long ago when using a file system that had been built
on another OS.
I resorted to using a hexadecimal editor on the raw disk to get rid of
the thing.

-- hendrik

>
> It's risky indeed, but it's hard to imagine files with
> 'xserver-xorg-video-.' prefix just laying around (these days).
>
> p.s. Ok then. Done with get-off-my-lawn mode this time.
>
> *CUT*
> --
> Torvalds' goal for Linux is very simple: World Domination
> Stallman's goal for GNU is even simpler: Freedom
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng