From: Rich Shepard <rshepard@appl-ecosys.com>
Subject: Major problem trying to install 5.0beta3 for linux
I gunzipped and untarred the file in one step and watched files being put
into directories with names of /bin, /dev, /etc, /driver, /fonts, /garde.
/txt and so on. These all showed up as subdirectories under the /usr3
partition. Since I want all of GRASS in a directory called
/usr3/GRASS-5.0beta3, I started rm'ing the files and directories. It was
after I invoked 'rm -rf /bin' that I discovered that I trashed the /bin
directory on my main workstation!!
This is not a subdirectory under /usr3 located on a nfs-mounted partition,
but the basic /bin directory on the machine to which I am logged in! The
only thing I can figure has happened is that a symbolic link has been
created from the system directories under / so that they appear as
directories under /usr3.
Ouch!
I know this is a little late, but wouldn't it have been better to do
'rm -rf bin' from /usr3 or 'rm -rf /usr3/bin'.
'rm -rf /bin' to me means "go to the root partition (/) and then remove the bin
directory" - which is what happened.
Alternative: make directory and mv other dirs into it instead of removing.
'cd /usr3; mkdir GRASS-5.0beta3; mv bin dev etc driver fonts garde txt ...
GRASS-5.0beta3'
I also thought there was an install script (grass5install.sh) available in
the same directory as the binary tar.gz file
sh grass5install.sh grass5beta3_linuxbin.tar.gz /usr/local/grass5
Your case would be:
sh grass5install.sh grass5beta3_linuxbin.tar.gz /usr3/GRASS-5.0beta3.
Hope this helps...
Ben Horner-Johnson
ben@earth.nwu.edu
On Wed, 22 Sep 1999, Ben Horner-Johnson wrote:
I know this is a little late, but wouldn't it have been better to do
'rm -rf bin' from /usr3 or 'rm -rf /usr3/bin'.
'rm -rf /bin' to me means "go to the root partition (/) and then remove the bin
directory" - which is what happened.
I was in /usr3 and I did type rm -r bin/ (messed up in the message).
Somehow, the directories are appearing in two places.
Regardless of how I screwed up, untarring the tarball should not have made
bin, dev, etc and so on appear as directories under /usr3. _That's_ what got
me in trouble in the first place.
After almost 30 hours, the backup is 98% complete. When it's done I'll go
the route of restoring the /bin directory. Then I'll change out the hardware
and clean up the messy GRASS install.
Wonder why it did this to me when no one else reported spurious
directories during installation.
Sigh.
I also thought there was an install script (grass5install.sh) available in
the same directory as the binary tar.gz file
Not that I saw. In the /binary directory there was only the tarball. Once
I untarred it grass5install.sh was in the /usr3 directory.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
On Wed, Sep 22, 1999 at 01:50:53PM -0700, Rich Shepard wrote:
On Wed, 22 Sep 1999, Ben Horner-Johnson wrote:
I was in /usr3 and I did type rm -r bin/ (messed up in the message).
Somehow, the directories are appearing in two places.
Okay.
Regardless of how I screwed up,
It is probably hard to reconstrucht what happened.
untarring the tarball should not have made
bin, dev, etc and so on appear as directories under /usr3. _That's_ what got
me in trouble in the first place.
Tar untarrs relativ to the directory, per default.
I haven't checked the tarball myself, but it would have worked, if
you would have been in "/".
Good luck with fixing your system.
Bernhard
--
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Association for a Free Informational Infrastructure (ffii.org)