Linux

48372 readers

2349 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Ash Vs Bash (lemmy.ca)

submitted 1 year ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

[For reference, I'm talking about Ash in Alpine Linux here, which is part of BusyBox.]

I thought I knew the big differences, but it turns out I've had false assumptions for years. Ash does support [[ double square brackets ]] and (as best I can tell) all of Bash's logical trickery inside them. It also supports ${VARIABLE_SUBSTRINGS:5:12}` which was another surprise.

At this stage, the only things I've found that Bash can do that Ash can't are:

Arrays, which Bash doesn't seem to do well anyway
Brace expansion, which is awesome but I can live without it.

What else is there? Did Ash used to be more limited? The double square bracket thing really surprised me.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (3 children)

ash (and its successor dash found on other distros) is a POSIX-y shell rather than a sh clone, so it has all(? most?) of the POSIX feature set, whose syntax may indeed have been 'borrowed' from shells that came later than sh.

Not sure if there's a "parent" from which both ash and bash inherit the syntax or whether bash is the true source, but that doesn't really matter here.

All that said, it's worth checking to see if your system has a command on the PATH called [[. That has been one way that [[ support can be added to a system when the shell itself might not support it. Note that command names don't have to be alphanumeric like functions tend to be in a programming language (or other languages if you consider that the shell can be used for programming too), so [[ is perfectly valid!

[–] [email protected] 3 points 1 year ago (2 children)

Yup, that looks like exactly what was done in Alpine:

$ docker run --rm -it alpine ls -l /usr/bin/[[
lrwxrwxrwx    1 root     root            12 Sep 28 11:18 /usr/bin/[[ -> /bin/busybox

So while the Ash itself doesn't support the [[ extension, this work-around produces the same effect. Nifty.

[–] jntesteves 5 points 1 year ago (1 children)

Although that link exists, that's not what is being used by default. [[ is a shell builtin in ash/busybox, so that takes precedence.

On Alpine:

❯ which [[
/usr/bin/[[

❯ command -V [[
[[ is a shell builtin

[–] [email protected] 1 points 1 year ago

Huh. So the link is unnecessary and Ash supports [[ out of the box? Good to know, thanks!