@Kiwy Ditto @terdon. The # that you added to the shebang may actually have solved the problem, but since the error itself is never mentioned, it's hard to be sure.

@Kusalananda Kiwi removed it, I added it. It was there in the original question.

Here's the first revision:

unix.stackexchange.com/revisions/458089/1

it was not visible but it turn the first line into a title... I get reck by the presentation I though it wasn't there :D

Can I consult easilly history of the edit I always struggle to find it

If you see the source, you'll see the shebang. That's why the !/bin/bash is huge, the # was interpreted as markdown.

@Kiwy Ah.

Now I see.

@Kiwy Click on the "edited N minutes ago" link under the question. That shows you all revisions.

That's the kind of change I would like to see to the site instead of making thing very hard to find... instead of basic theming

next to edit button history it would be lovely <3

@Kiwy It's pretty easy to find, really. It's been there for ever.

I know but it's not explicit @terdon, though the link exist I would never think to click on date to find the history of anything in any software I'm using

I'll try to remember and now I need to eat something

I've been reading about which directories should be on separate partitions, like var and usr, which should be then mounted in /. One article suggested mounting usr as read-only, my only concern with that is how do I update what is stored in usr? If usr is mounted read-only, then root wouldn't even be able to modify the directory, right?

@Ungeheuer you flip the mount to read-write, upgrade, and flip back to read-only

some tools can take care of that for you (e.g. apt with the appropriate hooks)

I'll be installing centOS, so I'll have to see how to do it with yum. When flipping the mount, I would need to do this before allowing my package manager to do any updates, correct?

@StephenKitt

@Ungeheuer yes

That's a pretty simple solution, but I'll have to find a way to not do that all the time. I'd guess yum has some way to handle that.

Thanks for the help Stephen!

@Ungeheuer you're welcome!

if you run into problems, this would be interesting material for a proper question on the main site

Really? Well, let's hope I run into issues. A prominent website featuring at the top of a google search for such an issue would be a boon to future users.

Another question. I just read the manpage for chown to figure out what's going on here, but I'm still not certain. I've chown-ed files before, but never used this.

@Ungeheuer You can always ask a question, and answer it, tutorial style.

Huh...I thought the ` character was for in-line code formatting...

What does the chmod o= do here? I understand o is for "other users," per the manpage and TLDP.

@FaheemMitha I guess I will, if I'm confident that it won't be a "in the land of the blind, the one-eyed man is king" scenario.

@Ungeheuer it sets the file permissions to nothing for other users, but that was already the case

-rw-rw----

@Ungeheuer Try to word it so someone doing a search for whatever it is might actually stumble on it. I've asked the most seemingly obscure questions, but often people have found them helpful. Similarly with answers.

@StephenKitt That's a damn good answer.

@StephenKitt That's very helpful

@Ungeheuer my first big hit

well deserved

@StephenKitt This link from redhat boils down to "Don't mount /usr read-only." I'm gonna mount it as rw, then when I figure out how to handle ro I'll remount. Still trying to figure stuff out.