linux-lunarium: fix description for script-pipe - #172
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c0b9dc2308
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| echo COLLEGE | ||
| hacker@dojo:~$ bash script.sh > output | ||
| hacker@dojo:~$ cat output | ||
| hacker@dojo:~$ ./script.sh | cat |
There was a problem hiding this comment.
Add chmod before invoking ./script.sh in example
The new example runs ./script.sh | cat immediately after showing file contents, but it never shows setting the execute bit; in a normal workflow (cat > script.sh, editor save, etc.), script.sh is typically created without execute permissions, so this command fails with “Permission denied.” Because this level comes before “Executable Shell Scripts,” readers can follow the snippet exactly and still fail; please either add chmod +x script.sh in the example or use bash script.sh | cat for a runnable demonstration.
Useful? React with 👍 / 👎.
|
Using /bin/bash instead of just bash also works. |
The challenge will not complete successfully if you run it as shown in the example.
The challenge actually wants to get his input from an executable script like this:
.script.sh | /challenge/solveI suggest moving "Redirect Script Output" after the "Executable Shell Scripts" challenge on the website, but I don't know if this is done in this repository or somewhere else.
This would make sense because the user needs the knowledge to find a solution for this challenge.
I also suggest using the updated description from this pull request for more precision.