Comments on: Learning Bash

By: rdsears

rdsears — Tue, 06 Apr 2010 21:52:53 +0000

Hi there,

I’m glad you like my blog, but what do you mean by unnecessary comments? My blog section will of course be populated with my thoughts, but the technical stuff I’ve segregated into individual pages. The comments in there are either meant to be humorous or helpful. I’ll keep that in mind though!

By: Privatik

Privatik — Mon, 29 Mar 2010 03:55:18 +0000

Blog liked, but a lot of unnecessary comments.

By: Satya

Satya — Sat, 19 Dec 2009 14:59:53 +0000

Thanks for this nice and short tutorial!

Those who have hard time reading this web page may select Print Preview from Firefox. That makes it pretty clean and readable!!

By: rdsears

rdsears — Mon, 30 Nov 2009 19:31:36 +0000

Hey,

Thanks for that. I was defiantly unaware of this, but that’s why I started this in the first place! To share and learn

By: Fred

Fred — Wed, 25 Nov 2009 09:34:09 +0000

> (the space (or lack thereof one) after the hashbang has never
> mattered, but there were rumors back in the day that it did)

Yes it does, I just had to deal with such a broken shebang. It doesn’t matter when you call your script from the shell (it doesn’t even look at the shebang!) but you can’t exec(2) such a script. Demonstration:

frlanw0f03384:/tmp$ rm example launcher
frlanw0f03384:/tmp$ cat – > example
# !/bin/bash
echo Hello, this is example
frlanw0f03384:/tmp$ cat – > launcher
#!/usr/bin/python
from subprocess import call
call(["/tmp/example"])
frlanw0f03384:/tmp$ chmod +x launcher example
frlanw0f03384:/tmp$ ./launcher
Traceback (most recent call last):
File “./launcher”, line 3, in ?
call(["/tmp/example"])
File “/usr/lib/python2.4/subprocess.py”, line 412, in call
return Popen(*args, **kwargs).wait()
File “/usr/lib/python2.4/subprocess.py”, line 542, in __init__
errread, errwrite)
File “/usr/lib/python2.4/subprocess.py”, line 975, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
frlanw0f03384:/tmp$ ./example
Hello, this is example
frlanw0f03384:/tmp$ cat – > example
#! /bin/bash
echo Hello, this is example –reloaded
frlanw0f03384:/tmp$ chmod +x example
frlanw0f03384:/tmp$ ./launcher
Traceback (most recent call last):
File “./launcher”, line 3, in ?
call(["/tmp/example"])
File “/usr/lib/python2.4/subprocess.py”, line 412, in call
return Popen(*args, **kwargs).wait()
File “/usr/lib/python2.4/subprocess.py”, line 542, in __init__
errread, errwrite)
File “/usr/lib/python2.4/subprocess.py”, line 975, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
frlanw0f03384:/tmp$ cat ->example
#!/bin/bash
echo Hello, this is example –corrected.
frlanw0f03384:/tmp$ chmod +x example
frlanw0f03384:/tmp$ ./launcher
Hello, this is example –corrected.

So, now I have to do something like:
call(["/bin/bash", "-c", "/path/to/script"])
because of people who can’t write shebangs.

By: neur0

neur0 — Thu, 19 Nov 2009 14:52:26 +0000

Good stuff.
The only color I’m having trouble with is that Comment Blue which IMO should be lighter on this background.

By: Ken Schumacher

Ken Schumacher — Tue, 17 Nov 2009 15:08:00 +0000

I too wanted to comment on text colors. Right at the top you have the darker blue text on a gray background. There is not enough contrast between those two to make it readable. There are other spots in your post where you use that same blue on a darker gray which are at least better. I find that green on black is easier to read than white on black.

My suggestion would be to do something more like book publishers. Use different fonts to differentiate the commands being entered from the messages that are returned.

Your posting is good, just a bit awkward to read through. Thanks for sharing.

Ken S.

By: rdsears

rdsears — Sun, 15 Nov 2009 01:41:57 +0000

Hey, I’m sorry you’re having trouble reading it…What color would you suggest?

By: Unix Links

Unix Links — Sat, 14 Nov 2009 10:41:28 +0000

White Text on Black backgroung is hard to read…

Remember users with poor eyesight.#

Please change this