[plug] install problems with StarOffice 5.2, what would this command do, moving around....

[Ari Finander]

Original message from: Peter Wright <pete at cygnus.uwa.edu.au>
>
>Hi Ari,
>
>No! No no no no no no no no no.
>
>You shouldn't install StarOffice 5.2 as root. Well, I'd recommend you
not,
>at least :). During the install of Linux you _did_ create an ordinary
user
>(eg. "ari"), didn't you? Log in as ari and run the StarOffice install
>program.  It'll try to make a directory called 'office52' in your
home
>directory and install itself there.


What if I want all users to be able to use StarOffice?  I have 3 user
accounts.

>
>Note that you'll need (from memory) around about 150-200 megabytes of
free
>space on whatever partition you try to install it. If that doesn't
make
>sense, try installing and if it comes up with a "you've run out of
space"
>error, you don't have enough space. :)
>


Checked it before and during the installation using GDiskFree, and
there's about 4 Gigabytes of space left on my Red Hat 7.0 partition.
Hence I'm leaning towards the corrupt download theory.

> From memory, I've found StarOffice to not work out very well if you
try to
>install it as root and make it accessible for all users. At least,
this
>certainly applied to earlier versions of it.
>

>
>A quick explanation of the "chmod 777" that you casually refer to...
:)
>
>7 = 4 + 2 + 1
>
>4 => read permission
>2 => write permission
>1 => execute permission
>
>Hence, 7 => read, write, and execute permission.
>       6 => read and write permission.
>       5 => read and execute permission, etc...
>
>chmod OGA (where O, G, A are numbers from 0 to 7)
>
>O => owner
>G => group
>A => all (everyone on the system)
>
>Hence, "chmod 777" means... "give read, write, execute permission to
the
>owner; read, write, execute permission to the group; oh, and read,
write,
>execute permission to everyone else as well. :)
>


Ummm...not something I really want to do, I think I'll ignore Sun's
advice on that one.


>  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>WOOP WOOP WOOP
>

>
>Or perhaps the install error message might possibly be correct, and
there
>really isn't enough disk space! *grin*
>


See above, I checked before and during with GDiskFree, there's tonnes
o' room on this partition (a little less than 4GB left).


>
>Oooookkkaaaaay..... I'm puzzled as to what you mean here by "when I
try to
>navigate that partition with the command line". What _exactly_ do you
do?
>If possible, can you open a window, type whatever you type that
causes the
>problem (btw, type "df" before this just to list your mounted
partitions),
>then copy and paste the text from the window into an email (much as I
did
>above when showing how to use "df")?

Well, I can do it from memory:

I typed:

cd /mnt/winc/Ari's Backup/Disk
1/Downloads/Downloads98/Linux/Star_Office/

and it resulted in an unending never changing series of > prompts
without the root at boxie prefix (boxie is my machine's name :-) no
matter what I typed (cd, dir, ls, quit, exit, q, damnit, bastard,
etc...)

I also tried commands like:

'cd cd /mnt/winc/' which was okay, and responded as normal, then 'cd
/mnt/winc/Ari's Backup' went to those damned > prompts again (and
that's the entire prompt, no user/machine name prefix).  It works fine
using the Gnome File Manager though, I can move programs and do
whatever in /mnt/winc, I just cannot do anything with
/mnt/winc/<directory> when using a terminal window.

>
>Pete.
>-- 


Ari
spodosaurus at start.com.au


__________________________________________________________________
Get your free Australian email account at http://www.start.com.au