Forums

Installing Quartus-II software on Ubuntu Linux

Started by Bruce Varley April 26, 2011
On 05/01/2011 07:38 PM, jacko wrote:
> should not 'bash script' execute a script within bash with the #! having an effect, as #! is a system feature to find the shell to use?
Correct.
On 01/05/11 19:38, jacko wrote:
> should not 'bash script' execute a script within bash with the #! > having an effect, as #! is a system feature to find the shell to > use?
#! is not a feature to find the shell to use - you specify the shell you want in the #! line. Is there any way you could get a proper newsreader, or at least correct your settings for google groups (assuming that's what you use)? You seem to make knowledgeable and potentially useful posts in a number of groups, but because your posts don't track references properly, and you don't include any quoted context, it is extremely difficult to follow you. No one knows what or whom you are replying to. Thanks, David
David Brown <david.brown@removethis.hesbynett.no> writes:

> On 30/04/11 16:13, Petter Gustad wrote: >> David Brown<david@westcontrol.removethisbit.com> writes: >> >>> The easiest way to make sure you are running bash for a job like this, >>> is simply to type "bash" - then do your install inside this shell. >> >> Note that if you run a script which starts with the bang notation: >> #!/bin/sh it will launch dash, as /bin/sh is a link to /bin/dash on >> Ubuntu. Some users replace this link with a link to bash instead. >> > > That can certainly happen - but only if the script is badly written. > If a script requires certain functionality from its shell, it should > use the appropriate shell in the #! line. You only use #!/bin/sh if > you are happy with any posix-sh compliant shell - including dash.
It might be history, but I think the problem was that dash is/was(?) not POSIX compliant. It's been a while since I looked into this, but currently http://en.wikipedia.org/wiki/Debian_Almquist_shell says: "much smaller than bash but still aiming at POSIX-compliancy" which I interpret as it not being fully POSIX compliant. I have seen issues with this in the past and had sufficient amount of problems which caused me to abandon dash completely as a POSIX compliant shell. But as I said it might be history. However, somebody should have updated Wikipedia if that was the case. //Petter -- .sig removed by request.
Petter Gustad <newsmailcomp6@gustad.com> writes:

> It might be history, but I think the problem was that dash is/was(?)
I should rephrase that as: The problems is that dash is not POSIX compliant. I think that still is the case. //Petter -- .sig removed by request.