#bourneshell — Public Fediverse posts on home.social

Vassil Nikolov | Васил Николов @[email protected] · 2025-11-05 · 20:21 UTC

Live a whole century, keep learning for a whole century, the Russians say.
Today I Learned™ how the Bourne-again shell catches bullets carefully
aimed at my foot.

I have a `bash' script, call it `baz', that post-processes text
produced by `foo-bar' (rest assured, though, that it remains within
all recognition).

Doing due diligence documentation-wise, I wanted to collect an example
of the end result into a comment in the same script.

So naive, I took myself for a ride:

$ foo-bar | baz | sed 's/^/### /' >> baz
bash: baz: Text file busy

(I expected that the shell would (try to) execute the appended lines,
so I commented them Just In Time. Running this with `strace' is left
as an exercise.)

PIPESTATUS was (0 141 1) and the output "softly and suddenly vanished away"...

--
"For the Snark was a Boojum, you see."

#BourneAgainShell
#BourneShell
#ComputerProgramming
#Hunting
#LewisCarrol
#Queen
#QuoteAbuse

#bourneagainshell #bourneshell #computerprogramming #hunting #lewiscarrol #queen

Vassil Nikolov | Васил Николов @[email protected] · 2025-11-05 · 20:21 UTC

Live a whole century, keep learning for a whole century, the Russians say.
Today I Learned™ how the Bourne-again shell catches bullets carefully
aimed at my foot.

I have a `bash' script, call it `baz', that post-processes text
produced by `foo-bar' (rest assured, though, that it remains within
all recognition).

Doing due diligence documentation-wise, I wanted to collect an example
of the end result into a comment in the same script.

So naive, I took myself for a ride:

$ foo-bar | baz | sed 's/^/### /' >> baz
bash: baz: Text file busy

(I expected that the shell would (try to) execute the appended lines,
so I commented them Just In Time. Running this with `strace' is left
as an exercise.)

PIPESTATUS was (0 141 1) and the output "softly and suddenly vanished away"...

--
"For the Snark was a Boojum, you see."

#BourneAgainShell
#BourneShell
#ComputerProgramming
#Hunting
#LewisCarrol
#Queen
#QuoteAbuse

#bourneagainshell #bourneshell #computerprogramming #hunting #lewiscarrol #queen

Vassil Nikolov | Васил Николов @[email protected] · 2025-11-05 · 20:21 UTC

Live a whole century, keep learning for a whole century, the Russians say.
Today I Learned™ how the Bourne-again shell catches bullets carefully
aimed at my foot.

I have a `bash' script, call it `baz', that post-processes text
produced by `foo-bar' (rest assured, though, that it remains within
all recognition).

Doing due diligence documentation-wise, I wanted to collect an example
of the end result into a comment in the same script.

So naive, I took myself for a ride:

$ foo-bar | baz | sed 's/^/### /' >> baz
bash: baz: Text file busy

(I expected that the shell would (try to) execute the appended lines,
so I commented them Just In Time. Running this with `strace' is left
as an exercise.)

PIPESTATUS was (0 141 1) and the output "softly and suddenly vanished away"...

--
"For the Snark was a Boojum, you see."

#BourneAgainShell
#BourneShell
#ComputerProgramming
#Hunting
#LewisCarrol
#Queen
#QuoteAbuse

#quoteabuse #queen #lewiscarrol #hunting #computerprogramming #bourneshell

Vassil Nikolov | Васил Николов @[email protected] · 2025-11-05 · 20:21 UTC

Live a whole century, keep learning for a whole century, the Russians say.
Today I Learned™ how the Bourne-again shell catches bullets carefully
aimed at my foot.

I have a `bash' script, call it `baz', that post-processes text
produced by `foo-bar' (rest assured, though, that it remains within
all recognition).

Doing due diligence documentation-wise, I wanted to collect an example
of the end result into a comment in the same script.

So naive, I took myself for a ride:

$ foo-bar | baz | sed 's/^/### /' >> baz
bash: baz: Text file busy

(I expected that the shell would (try to) execute the appended lines,
so I commented them Just In Time. Running this with `strace' is left
as an exercise.)

PIPESTATUS was (0 141 1) and the output "softly and suddenly vanished away"...

--
"For the Snark was a Boojum, you see."

#BourneAgainShell
#BourneShell
#ComputerProgramming
#Hunting
#LewisCarrol
#Queen
#QuoteAbuse

#bourneagainshell #bourneshell #computerprogramming #hunting #lewiscarrol #queen

Vassil Nikolov | Васил Николов @[email protected] · 2025-11-05 · 20:21 UTC

Live a whole century, keep learning for a whole century, the Russians say.
Today I Learned™ how the Bourne-again shell catches bullets carefully
aimed at my foot.

I have a `bash' script, call it `baz', that post-processes text
produced by `foo-bar' (rest assured, though, that it remains within
all recognition).

Doing due diligence documentation-wise, I wanted to collect an example
of the end result into a comment in the same script.

So naive, I took myself for a ride:

$ foo-bar | baz | sed 's/^/### /' >> baz
bash: baz: Text file busy

(I expected that the shell would (try to) execute the appended lines,
so I commented them Just In Time. Running this with `strace' is left
as an exercise.)

PIPESTATUS was (0 141 1) and the output "softly and suddenly vanished away"...

--
"For the Snark was a Boojum, you see."

#BourneAgainShell
#BourneShell
#ComputerProgramming
#Hunting
#LewisCarrol
#Queen
#QuoteAbuse

#bourneagainshell #bourneshell #computerprogramming #hunting #lewiscarrol #queen

adingbatponder :nixos: 👾 @adingbatponder · 2025-09-05 · 12:07 UTC

If a public foss repo offers a foss setup.sh command line script which, step by step, performs the installation / usage steps the repo readme lists for use at the command line to set up/use the code, what trust measures would you insist upon before downloading and before running the setup.sh script at your local command line? Is there a better way of offering an helpful automated but trustworthy #Heredoc than a scary .sh ?

#ShellProgramming #git #security #codeberg #shellscript #bourneshell

#heredoc #shellprogramming #git #security #codeberg #shellscript

adingbatponder :nixos: 👾 @[email protected] · 2025-09-05 · 12:07 UTC

If a public foss repo offers a foss setup.sh command line script which, step by step, performs the installation / usage steps the repo readme lists for use at the command line to set up/use the code, what trust measures would you insist upon before downloading and before running the setup.sh script at your local command line? Is there a better way of offering an helpful automated but trustworthy #Heredoc than a scary .sh ?

#ShellProgramming #git #security #codeberg #shellscript #bourneshell

#heredoc #shellprogramming #git #security #codeberg #shellscript

adingbatponder :nixos: 👾 @[email protected] · 2025-09-05 · 12:07 UTC

If a public foss repo offers a foss setup.sh command line script which, step by step, performs the installation / usage steps the repo readme lists for use at the command line to set up/use the code, what trust measures would you insist upon before downloading and before running the setup.sh script at your local command line? Is there a better way of offering an helpful automated but trustworthy #Heredoc than a scary .sh ?

#ShellProgramming #git #security #codeberg #shellscript #bourneshell

#heredoc #shellprogramming #git #security #codeberg #shellscript

adingbatponder :nixos: 👾 @[email protected] · 2025-09-05 · 12:07 UTC

If a public foss repo offers a foss setup.sh command line script which, step by step, performs the installation / usage steps the repo readme lists for use at the command line to set up/use the code, what trust measures would you insist upon before downloading and before running the setup.sh script at your local command line? Is there a better way of offering an helpful automated but trustworthy #Heredoc than a scary .sh ?

#ShellProgramming #git #security #codeberg #shellscript #bourneshell

#bourneshell #shellscript #codeberg #security #git #shellprogramming

adingbatponder :nixos: 👾 @[email protected] · 2025-09-05 · 12:07 UTC

If a public foss repo offers a foss setup.sh command line script which, step by step, performs the installation / usage steps the repo readme lists for use at the command line to set up/use the code, what trust measures would you insist upon before downloading and before running the setup.sh script at your local command line? Is there a better way of offering an helpful automated but trustworthy #Heredoc than a scary .sh ?

#ShellProgramming #git #security #codeberg #shellscript #bourneshell

#heredoc #shellprogramming #git #security #codeberg #shellscript

David Cantrell 🏏 @[email protected] · 2024-05-01 · 22:58 UTC

I saw someone else do this, so I thought I should too ...

Languages I have used to write software for other people to use, in roughly chronological order: #BASIC #Z80assembler #Pascal #C #BCPL #MIPSassembler #LotusAmiproMacros 😃 #VisualBASIC #DataEase #SQL #Java #Javascript #Perl #BourneShell #bash #Postscript #Rust. It saddens me that I have never perpetrated #Forth or #Lisp for any other audience than myself. It doesn't sadden me that I have forgotten at least some of them due to lack of use.

#basic #z80assembler #pascal #c #bcpl #mipsassembler

David Cantrell 🏏 @DrHyde · 2024-05-01 · 22:58 UTC

I saw someone else do this, so I thought I should too ...

Languages I have used to write software for other people to use, in roughly chronological order: #BASIC #Z80assembler #Pascal #C #BCPL #MIPSassembler #LotusAmiproMacros 😃 #VisualBASIC #DataEase #SQL #Java #Javascript #Perl #BourneShell #bash #Postscript #Rust. It saddens me that I have never perpetrated #Forth or #Lisp for any other audience than myself. It doesn't sadden me that I have forgotten at least some of them due to lack of use.

#basic #z80assembler #pascal #c #bcpl #mipsassembler

David Cantrell 🏏 @[email protected] · 2024-05-01 · 22:58 UTC

I saw someone else do this, so I thought I should too ...

Languages I have used to write software for other people to use, in roughly chronological order: #BASIC #Z80assembler #Pascal #C #BCPL #MIPSassembler #LotusAmiproMacros 😃 #VisualBASIC #DataEase #SQL #Java #Javascript #Perl #BourneShell #bash #Postscript #Rust. It saddens me that I have never perpetrated #Forth or #Lisp for any other audience than myself. It doesn't sadden me that I have forgotten at least some of them due to lack of use.

#basic #z80assembler #pascal #c #bcpl #mipsassembler

David Cantrell 🏏 @[email protected] · 2024-05-01 · 22:58 UTC

I saw someone else do this, so I thought I should too ...

Languages I have used to write software for other people to use, in roughly chronological order: #BASIC #Z80assembler #Pascal #C #BCPL #MIPSassembler #LotusAmiproMacros 😃 #VisualBASIC #DataEase #SQL #Java #Javascript #Perl #BourneShell #bash #Postscript #Rust. It saddens me that I have never perpetrated #Forth or #Lisp for any other audience than myself. It doesn't sadden me that I have forgotten at least some of them due to lack of use.

#lisp #forth #rust #postscript #bash #bourneshell

David Cantrell 🏏 @[email protected] · 2024-05-01 · 22:58 UTC

I saw someone else do this, so I thought I should too ...

Languages I have used to write software for other people to use, in roughly chronological order: #BASIC #Z80assembler #Pascal #C #BCPL #MIPSassembler #LotusAmiproMacros 😃 #VisualBASIC #DataEase #SQL #Java #Javascript #Perl #BourneShell #bash #Postscript #Rust. It saddens me that I have never perpetrated #Forth or #Lisp for any other audience than myself. It doesn't sadden me that I have forgotten at least some of them due to lack of use.