this post was submitted on 18 Sep 2024
7 points (88.9% liked)
linux4noobs
1388 readers
1 users here now
linux4noobs
Noob Friendly, Expert Enabling
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
Seeking Support?
- Mention your Linux distro and relevant system details.
- Describe what you've tried so far.
- Share your solution even if you found it yourself.
- Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
- Properly format any scripts, code, logs, or error messages.
- Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.
Community Rules
- Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
- Posts must be Linux oriented
- Spam or affiliate links will not be tolerated.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The script is complaining that it can't find curl? What is this script that you are using? It's probably got a super-basic check for curl (in the wrong location) that can be modified. (Type in the source URL for it here, or something.)
However, running any script without fully understanding it is not advisable to begin with.
Typing in 'which curl' at the command line should give you the proper location of the existing binary of curl.
Typed which curl, and it just went to the next line.
The script location is https://download.argon40.com/argon1.sh
There are about a million different flavors of how to download and execute a shell script. Regardless, you need to redirect the output of curl into bash with the -s flag. Bash needs to know that it is reading from STDIN.
Here is an over-thought stackoverflow page on it: https://stackoverflow.com/questions/5735666/execute-bash-script-from-url
Also, if the script is not being read properly, that might explain the dpkg lock issue. Running two instances of dpkg simultaneously is likely causing that collision you are seeing. (If one instance is running, it will touch a lock file and then delete it when it stops. It prevents "bad things" from happening when two instances of the same app want the same resources.)
That is odd if your path is broken. It curl should be in /usr/bin and 'which' should find it. Are you somehow launching another shell inside a shell? Like zsh inside of bash, or something in that flavor? (In some rare cases, that would break paths and profile configs for your active shell.)
Regardless of why curl isn't being found, or only partially found, or something, learn "env". You need to get a decent picture of what your working environment is and why something as basic as curl "isn't found". ('which' is about as a baseline of a command as there is.)