On Wednesday, November 22, 2000, at 11:43 PM, Justin Hickey wrote:
> > > Sorry, </usr/local/grass-5.0b/dev/fifo.1a> not available
> > > Have GRASS administrator check etc/monitorcap file
> > >
> > > What other files might tcltkgrass may be dependent on??
> >
> > Hmmm. Did you use the installation script grass5install.sh? This
> > script is supposed to create the fifos.
>
> Yessir! Uh-oh!
In that case, please do an ls -Fla in the directory
/usr/local/grass-5.0b/dev/
It should look something like this:
prw-rw-rw- 1 jhickey hpcc 0 Oct 9 11:53 fifo.17b|
prw-rw-rw- 1 jhickey hpcc 0 Oct 9 11:53 fifo.18a|
prw-rw-rw- 1 jhickey hpcc 0 Oct 9 11:53 fifo.18b|
prw-rw-rw- 1 jhickey hpcc 0 Oct 9 11:53 fifo.19a|
prw-rw-rw- 1 jhickey hpcc 0 Oct 9 11:53 fifo.19b|
prw-rw-rw- 1 jhickey hpcc 0 Oct 17 16:10 fifo.1a|
prw-rw-rw- 1 jhickey hpcc 0 Oct 17 16:10 fifo.1b|
If they do look like this, then compare the directory paths in
etc/monitorcap with /usr/local/grass-5.0b/dev/. They should be the same.
Thanks Justin! It turns out that (for whatever reason) grass was installed at /usr/local/grass5.
I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5 and it works!!
(Markus: can you please add this to the installation instructions?: cd /usr/local; ln -s grass-5.0b grass5;)
Cheers,
Jeshua Lacock
Cartographer/Owner http://SierraMaps.com http://3dTopoMaps.com
Telephone: (760) 935-4481
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
Thanks Justin! It turns out that (for whatever reason) grass was
installed at /usr/local/grass5.
You're welcome.
I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
and it works!!
(Markus: can you please add this to the installation instructions?:
cd /usr/local; ln -s grass-5.0b grass5;)
Actually, we need to find where the grass-5.0b is coming from. We made a
decision that it would be grassx where x is the current major version
number to simplify coding and decrease user confusion.
Markus, do you know where the grass-5.0b is coming from?
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
> I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
and it works!!
(Markus: can you please add this to the installation instructions?:
cd /usr/local; ln -s grass-5.0b grass5;)
Actually, we need to find where the grass-5.0b is coming from. We made a
decision that it would be grassx where x is the current major version
number to simplify coding and decrease user confusion.
Yes, however since nearly 2000 people have download the OS X binaries, I think it would be useful to add the symbolic link to the instructions until beta 9 is posted.
---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
>> I made a symbolic link /usr/local/grass-5.0b ->
>> /usr/local/grass5
>> and it works!!
>> (Markus: can you please add this to the installation
>> instructions?: cd /usr/local; ln -s grass-5.0b grass5;)
>
>Actually, we need to find where the grass-5.0b is coming from. We
>made a decision that it would be grassx where x is the current major
>version number to simplify coding and decrease user confusion.
Yes, however since nearly 2000 people have download the OS X
binaries, I think it would be useful to add the symbolic link to the
instructions until beta 9 is posted.
Wow! 2000! Cool! In that case, yes you're right.
BTW, how did so many people find out about it so quickly? Do we have
2000 Mac users on the grasslist?
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
>> I made a symbolic link /usr/local/grass-5.0b ->
>> /usr/local/grass5
>> and it works!!
>> (Markus: can you please add this to the installation
>> instructions?: cd /usr/local; ln -s grass-5.0b grass5;)
>
>Actually, we need to find where the grass-5.0b is coming from. We
>made a decision that it would be grassx where x is the current major
>version number to simplify coding and decrease user confusion.
Yes, however since nearly 2000 people have download the OS X
binaries, I think it would be useful to add the symbolic link to the
instructions until beta 9 is posted.
Wow! 2000! Cool! In that case, yes you're right.
BTW, how did so many people find out about it so quickly? Do we have
2000 Mac users on the grasslist?
Justin,
I just sent out a few emails to mac news sites and Markus posted it on a GIS newsgroup...
---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 03:24:04PM +0700, Justin Hickey wrote:
Hi Jeshua
Jeshua Lacock wrote:
> Thanks Justin! It turns out that (for whatever reason) grass was
> installed at /usr/local/grass5.
You're welcome.
> I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
> and it works!!
> (Markus: can you please add this to the installation instructions?:
> cd /usr/local; ln -s grass-5.0b grass5;)
Actually, we need to find where the grass-5.0b is coming from. We made a
decision that it would be grassx where x is the current major version
number to simplify coding and decrease user confusion.
Markus, do you know where the grass-5.0b is coming from?
Hi,
Huidae just fixed it in configure[.in]. Should be
/usr/local/grass5
now. We have to test this and maybe update INSTALL & friends.
Yours
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>
> > I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
>> and it works!!
>> (Markus: can you please add this to the installation instructions?:
>> cd /usr/local; ln -s grass-5.0b grass5;)
>
>Actually, we need to find where the grass-5.0b is coming from. We made a
>decision that it would be grassx where x is the current major version
>number to simplify coding and decrease user confusion.
Yes, however since nearly 2000 people have download the OS X
binaries, I think it would be useful to add the symbolic link to the
instructions until beta 9 is posted.
Jeshua,
actually I don't understand the problem. We have a grass5b8_mac package
and a grass5install.sh script. The script takes care where to install
the package and generates the startup script depending on the install
path. This works since month.
Why this confusion?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 03:24:04PM +0700, Justin Hickey wrote:
Hi Jeshua
Jeshua Lacock wrote:
> Thanks Justin! It turns out that (for whatever reason) grass was
> installed at /usr/local/grass5.
You're welcome.
> I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
> and it works!!
> (Markus: can you please add this to the installation instructions?:
> cd /usr/local; ln -s grass-5.0b grass5;)
Actually, we need to find where the grass-5.0b is coming from. We made a
decision that it would be grassx where x is the current major version
number to simplify coding and decrease user confusion.
Markus, do you know where the grass-5.0b is coming from?
It's coming from PREFIX= in the configure script. You can change it with
--prefix=DIR. Changing the default to grass5 is a simple matter.
--
Eric G. Miller <egm2@jps.net>
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>
> > I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
>> and it works!!
>> (Markus: can you please add this to the installation instructions?:
>> cd /usr/local; ln -s grass-5.0b grass5;)
>
>Actually, we need to find where the grass-5.0b is coming from. We made a
>decision that it would be grassx where x is the current major version
>number to simplify coding and decrease user confusion.
Yes, however since nearly 2000 people have download the OS X
binaries, I think it would be useful to add the symbolic link to the
instructions until beta 9 is posted.
Jeshua,
actually I don't understand the problem. We have a grass5b8_mac package
and a grass5install.sh script. The script takes care where to install
the package and generates the startup script depending on the install
path. This works since month.
Why this confusion?
Markus,
That's all right, I don't understand either!! ;-D
All I know it that the GUI will not work unless this symbolic link is created....
---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 01:33:37PM -0800, Jeshua Lacock wrote:
>On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>> >
>> > > I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
>> >> and it works!!
>> >> (Markus: can you please add this to the installation instructions?:
>> >> cd /usr/local; ln -s grass-5.0b grass5;)
>> >
>> >Actually, we need to find where the grass-5.0b is coming from. We made a
>> >decision that it would be grassx where x is the current major version
>> >number to simplify coding and decrease user confusion.
>>
>> Yes, however since nearly 2000 people have download the OS X
>> binaries, I think it would be useful to add the symbolic link to the
>> instructions until beta 9 is posted.
>Jeshua,
>
>actually I don't understand the problem. We have a grass5b8_mac package
>and a grass5install.sh script. The script takes care where to install
>the package and generates the startup script depending on the install
>path. This works since month.
>
>Why this confusion?
>
Markus,
That's all right, I don't understand either!! ;-D
All I know it that the GUI will not work unless this symbolic link is
created....
Could you do me the favor, remove the link and send the error
message? Then we might fix it (if something has to be fixed).
Thanks in advance
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 01:33:37PM -0800, Jeshua Lacock wrote:
>On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>> >
>> > > I made a symbolic link /usr/local/grass-5.0b -> /usr/local/grass5
>> >> and it works!!
>> >> (Markus: can you please add this to the installation instructions?:
>> >> cd /usr/local; ln -s grass-5.0b grass5;)
>> >
>> >Actually, we need to find where the grass-5.0b is coming from. We made a
>> >decision that it would be grassx where x is the current major version
>> >number to simplify coding and decrease user confusion.
>>
>> Yes, however since nearly 2000 people have download the OS X
>> binaries, I think it would be useful to add the symbolic link to the
>> instructions until beta 9 is posted.
>Jeshua,
>
>actually I don't understand the problem. We have a grass5b8_mac package
>and a grass5install.sh script. The script takes care where to install
>the package and generates the startup script depending on the install
>path. This works since month.
>
>Why this confusion?
>
Markus,
That's all right, I don't understand either!! ;-D
All I know it that the GUI will not work unless this symbolic link is
created....
Could you do me the favor, remove the link and send the error
message? Then we might fix it (if something has to be fixed).
Markus,
d.mon says:
Sorry, </usr/local/grass-5.0b/dev/fifo.1a> not available
Have GRASS administrator check etc/monitorcap file
And I get this error because grass is installed at/usr/local/grass5/...
---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 01:42:46PM -0800, Jeshua Lacock wrote:
>On Thu, Nov 23, 2000 at 01:33:37PM -0800, Jeshua Lacock wrote:
>> >On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>> >> >
>> >> > > I made a symbolic link /usr/local/grass-5.0b ->
>>/usr/local/grass5
>> >> >> and it works!!
>> >> >> (Markus: can you please add this to the installation instructions?:
>> >> >> cd /usr/local; ln -s grass-5.0b grass5;)
>> >> >
>> >> >Actually, we need to find where the grass-5.0b is coming
>>from. We made a
>> >> >decision that it would be grassx where x is the current major version
>> >> >number to simplify coding and decrease user confusion.
>> >>
>> >> Yes, however since nearly 2000 people have download the OS X
>> >> binaries, I think it would be useful to add the symbolic link to the
>> >> instructions until beta 9 is posted.
>> >Jeshua,
>> >
>> >actually I don't understand the problem. We have a grass5b8_mac package
>> >and a grass5install.sh script. The script takes care where to install
>> >the package and generates the startup script depending on the install
>> >path. This works since month.
>> >
>> >Why this confusion?
>> >
>>
>> Markus,
>>
>> That's all right, I don't understand either!! ;-D
>>
>> All I know it that the GUI will not work unless this symbolic link is
>> created....
>Could you do me the favor, remove the link and send the error
>message? Then we might fix it (if something has to be fixed).
>
Markus,
d.mon says:
Sorry, </usr/local/grass-5.0b/dev/fifo.1a> not available
Have GRASS administrator check etc/monitorcap file
^^^^^^^^^^^^^^^
And I get this error because grass is installed at/usr/local/grass5/...
I see. The /usr/local/grass5/etc/monitorcap references the wrong
path. Please edit this file. Usually the settings are done on
compile time. With current CVS it should be o.k.
Hope this helps
Markus
(going to sleep now)
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Nov 23, 2000 at 01:42:46PM -0800, Jeshua Lacock wrote:
>On Thu, Nov 23, 2000 at 01:33:37PM -0800, Jeshua Lacock wrote:
>> >On Thu, Nov 23, 2000 at 02:21:49AM -0800, Jeshua Lacock wrote:
>> >> >
>> >> > > I made a symbolic link /usr/local/grass-5.0b ->
>>/usr/local/grass5
>> >> >> and it works!!
>> >> >> (Markus: can you please add this to the installation instructions?:
>> >> >> cd /usr/local; ln -s grass-5.0b grass5;)
>> >> >
>> >> >Actually, we need to find where the grass-5.0b is coming
>>from. We made a
>> >> >decision that it would be grassx where x is the current major version
>> >> >number to simplify coding and decrease user confusion.
>> >>
>> >> Yes, however since nearly 2000 people have download the OS X
>> >> binaries, I think it would be useful to add the symbolic link to the
>> >> instructions until beta 9 is posted.
>> >Jeshua,
>> >
>> >actually I don't understand the problem. We have a grass5b8_mac package
>> >and a grass5install.sh script. The script takes care where to install
>> >the package and generates the startup script depending on the install
>> >path. This works since month.
>> >
>> >Why this confusion?
>> >
>>
>> Markus,
>>
>> That's all right, I don't understand either!! ;-D
>>
>> All I know it that the GUI will not work unless this symbolic link is
>> created....
>Could you do me the favor, remove the link and send the error
>message? Then we might fix it (if something has to be fixed).
>
Markus,
d.mon says:
Sorry, </usr/local/grass-5.0b/dev/fifo.1a> not available
Have GRASS administrator check etc/monitorcap file
^^^^^^^^^^^^^^^
And I get this error because grass is installed at/usr/local/grass5/...
I see. The /usr/local/grass5/etc/monitorcap references the wrong
path. Please edit this file. Usually the settings are done on
compile time. With current CVS it should be o.k.
Markus,
I can edit the file, but it will not help all of the people that downloaded the distribution. Until beta 9 is released the best fix (IMHO) is to create a symbolic link..
---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
