Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not bash so much, but I started with O'Reilly's "UNIX in a Nutshell" back in the day.
There is a lot of good information on the 'net. DuckDuckGo is your friend.
On tip I read was that ending scripts with .sh is bad form. Not sure why this would be.
This is what the #bash IRC channel bot says about it:
Quote:
Don't use extensions for your scripts. Scripts define new commands that you can run, and commands are generally not given extensions. Do you run ls.elf? Also: bash scripts are *not* sh scripts (so don't use .sh) and the extension will only cause dependencies headaches if the script gets rewritten in another language. See http://www.talisman.org/~erlkonig/do...idered-harmful
Idling in that channel, #bash, will teach you quite a bit (or at least it helped me, but i got rather basic needs).
If you (think you must) use the web, as proposed, then you will probably make sure to compare the results with this: http://mywiki.wooledge.org/BashPitfalls
lots of times you will run into one of these pitfalls when searching the web.
The "guide" and the "FAQ" at that site, mywiki.wooledge.org, are also pretty good.
Else there is: http://wiki.bash-hackers.org/ as a good guide.
and then help cmdname will print help about cmdname
Code:
onk@XEON4 ~ $ help bg
bg: bg [job_spec ...]
Move jobs to the background.
Place the jobs identified by each JOB_SPEC in the background, as if they
had been started with `&'. If JOB_SPEC is not present, the shell's notion
of the current job is used.
Exit Status:
Returns success unless job control is not enabled or an error occurs.
jonk@XEON4 ~ $
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.