Hi,
FYI
I have extended the "GRASS and Shell" page in the wiki
to explain how to launch parallel GRASS jobs:
http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
Feel free to further improve the page.
cheers
Markus
cool!
jachym
On Thu, Jul 06, 2006 at 06:55:22PM +0200, Markus Neteler wrote:
Hi,
FYI
I have extended the "GRASS and Shell" page in the wiki
to explain how to launch parallel GRASS jobs:
http://grass.gdf-hannover.de/wiki/GRASS_and_ShellFeel free to further improve the page.
cheers
Markus
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser
--
Jachym Cepicky
e-mail: jachym.cepicky@centrum.cz
URL: http://les-ejk.cz
GPG: http://les-ejk.cz/gnupg_public_key/jachym_cepicky-gpg_public_key.asc
-----------------------------------------
OFFICE:
GDF-Hannover
Mengendamm 16d
30177 Hannover
Germany
e-mail: cepicky@gdf-hannover.de
URL: http://gdf-hannover.de
Tel.: +49 511-39088507
On Thu, 6 Jul 2006 18:55:22 +0200
Markus Neteler <neteler@itc.it> wrote:
Hi,
FYI
I have extended the "GRASS and Shell" page in the wiki
to explain how to launch parallel GRASS jobs:
http://grass.gdf-hannover.de/wiki/GRASS_and_ShellFeel free to further improve the page.
Markus,
The page contains bashisms like "export GISBASE=/usr/local/grass60".
Shall I de-bash it in this regard?
Maciek
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/
Maciek Sieczka wrote:
> I have extended the "GRASS and Shell" page in the wiki
> to explain how to launch parallel GRASS jobs:
> http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
>
> Feel free to further improve the page.Markus,
The page contains bashisms like "export GISBASE=/usr/local/grass60".
Shall I de-bash it in this regard?
ash also supports that syntax; coupled with the fact that I don't
recall any reports of problems caused by the numerous occurrences of
that syntax in the supplied scripts, it's probably safe to assume that
it works with any Bourne-style shell which is still in active use.
Aside:
ash is NetBSD's /bin/sh. It used to be Cygwin's /bin/sh, but as the
number of packages grew, fixinng all of the bash-isms in "/bin/sh"
scripts got to be too much work, so they gave up and made bash their
/bin/sh.
bash is living proof that the "embrace, extend, extinguish" strategy
isn't limited to Microsoft 
--
Glynn Clements <glynn@gclements.plus.com>
On Fri, Jul 07, 2006 at 08:54:41PM +0200, Maciek Sieczka wrote:
On Thu, 6 Jul 2006 18:55:22 +0200
Markus Neteler <neteler@itc.it> wrote:> Hi,
>
> FYI
> I have extended the "GRASS and Shell" page in the wiki
> to explain how to launch parallel GRASS jobs:
> http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
>
> Feel free to further improve the page.Markus,
The page contains bashisms like "export GISBASE=/usr/local/grass60".
Shall I de-bash it in this regard?
Please go ahead. It seems that I still didn't learn that "my"
export syntax is a bashism.
Markus
On Fri, 7 Jul 2006 22:59:55 +0100
Glynn Clements <glynn@gclements.plus.com> wrote:
Maciek Sieczka wrote:
> > I have extended the "GRASS and Shell" page in the wiki
> > to explain how to launch parallel GRASS jobs:
> > http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
> >
> > Feel free to further improve the page.
>
> Markus,
>
> The page contains bashisms like "export GISBASE=/usr/local/grass60".
> Shall I de-bash it in this regard?ash also supports that syntax; coupled with the fact that I don't
recall any reports of problems caused by the numerous occurrences of
that syntax in the supplied scripts, it's probably safe to assume that
it works with any Bourne-style shell which is still in active use.
So, do we want such syntax to be corrected? Is it worth the effort at
all given what you are saying?
Aside:
ash is NetBSD's /bin/sh. It used to be Cygwin's /bin/sh, but as the
number of packages grew, fixinng all of the bash-isms in "/bin/sh"
scripts got to be too much work, so they gave up and made bash their
/bin/sh.
bash is living proof that the "embrace, extend, extinguish" strategy
isn't limited to Microsoft
In M$ context, the word "bashism" brings other interesting associations
to my mind ;).
Maciek
--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/
Maciek Sieczka wrote:
> > > I have extended the "GRASS and Shell" page in the wiki
> > > to explain how to launch parallel GRASS jobs:
> > > http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
> > >
> > > Feel free to further improve the page.
> >
> > Markus,
> >
> > The page contains bashisms like "export GISBASE=/usr/local/grass60".
> > Shall I de-bash it in this regard?
>
> ash also supports that syntax; coupled with the fact that I don't
> recall any reports of problems caused by the numerous occurrences of
> that syntax in the supplied scripts, it's probably safe to assume that
> it works with any Bourne-style shell which is still in active use.So, do we want such syntax to be corrected? Is it worth the effort at
all given what you are saying?
I don't think that there's any point.
We can revisit the issue in the (unlikely) event that someone manages
to identify a system where the "export variable=value" syntax doesn't
work (and running GRASS on that system would otherwise be feasible).
--
Glynn Clements <glynn@gclements.plus.com>