install 816 on Linux(suse 8.1)

Hi All,

when running idea816.bin on Suse i get the following error :

. ./idea816.bin
Preparing to install...
/bin/ls: bash: No such file or directory
/bin/ls: /opt/bash: No such file or directory
Extracting the JRE from the installer archive...
wc: /tmp/install.dir.26343/Linux/resource/vm.tar.Z: No such file or
directory
The included VM could not be extracted. Please try to download
the installer again and make sure that you download using 'binary'
mode. Please do not attempt to install this currently downloaded copy.

When i download 816 without JRE included and and points IDEA_JRE to
an installed JRE in j2sdk1.4.1 it says wrong JRE installed ???

Any pointers ?


Regards,

Frank Bengtsson

5 comments
Comment actions Permalink

Try pointing it to the JRE you used for previous IDEA builds.

Inside the IDEA directory there is a "jre" directory... try copying that to your 816 directory.

Regards, Stefan.

0
Comment actions Permalink

Back on this subject... I have a really convenient way of changing between EAP builds on linux.

I have a directory where I set up all my IDEA EAP builds:
/usr/local/java/ide/aurora/
(in this directory I have idea-813, idea-815, idea-816 and so on).

When I download a new build, I take the tar.gz file that does not have a JRE (I only have one jre and I symlink to that one from within all the different EAP directories). This saves a lot of space.

So what I have is:
../jre | +-.../ | +-idea-815 | | | +-bin/ | +-jre -> ../jre | +-.../ | +-idea-.../ | | | +-.../ | +-current -> idea-xxx (this is a symlink pointing to the "active" idea installation, usually the latest one). ]]>
Each of the idea-XXX directories have a symlink called jre pointing to the jre in the parent directory.

To do this every time I created a shell script that allows me to do everything automatically. All I have to do is download the tar.gz file and extract it into the parent directory and run the script and give the name of the new idea directory.

Following is the shell script:

This needs a little explanation... most of it is self explanitory except maybe:

What this does is that it changes the ownership of all files and assignes them to the group "dev". This is specific for my installation because I have a group called "dev" that I put all users in that are developers and should therefore have access to all development tools... you can use whatever group you see fit. Next, it changes the permission bits on all the files and removes all permission from the the user group "other" (since we don't want anybody to be able to run IDEA). At last, we change the permission on all the files in such a way that we assign the same permission to the user group "group" as the user group "file owner" has. This means that the group "dev" now has the same permission as the owner of the file... so anybody in the group "dev" can run IDEA but everybody else will not be able to experience the bliss ;o)

Hope this will help somebody.
Kind regards, Stefan Freyr.

0
Comment actions Permalink

Tried that, but i am going from 3.0.1 to build 816 and that
requries a jdk 1.4.1_02 which i did not have for 3.0.1

So i installed 1.4.1_02 and copied the JRE to 816 but i get the error:

"IDEA is not configured properly.
The application should be run with the supplied JRE."

Have the done modification to JRE since i cannot take "my own" JRE ?

Regards,

Frank

Stefan Freyr Stefansson wrote:

Try pointing it to the JRE you used for previous IDEA builds.

Inside the IDEA directory there is a "jre" directory... try copying that
to your 816 directory.

Regards, Stefan.


0
Comment actions Permalink

I found out that i needed the jre from the download page on intelliJ !
instead of "my own" JRE from SUN....

Thx

/Frank Bengtsson

Stefan Freyr Stefansson wrote:

Back on this subject... I have a really convenient way of changing between
EAP builds on linux.

I have a directory where I set up all my IDEA EAP builds:
/usr/local/java/ide/aurora/
(in this directory I have idea-813, idea-815, idea-816 and so on).

When I download a new build, I take the tar.gz file that does not
have a JRE (I only have one jre and I symlink to that one from within all
the different EAP directories). This saves a lot of space.

So what I have is:
/usr/local/java/ide/aurora/ > | > +-jre/ > | > +-idea-813 > | | > | +-bin/ > | +-jre -> ../jre > | +-.../ > | > +-idea-815 > | | > | +-bin/ > | +-jre -> ../jre > | +-.../ > | > +-idea-.../ > | | > | +-.../ > | > +-current -> idea-xxx (this is a symlink pointing to > the "active" idea installation, usually the latest > one). > ]]>
Each of the idea-XXX directories have a symlink called jre pointing to the
jre in the parent directory.

To do this every time I created a shell script that allows me to do
everything automatically. All I have to do is download the tar.gz file
and extract it into the parent directory and run the script and give the
name of the new idea directory.

Following is the shell script:
#!/bin/bash > > INSTALL_DIR=$1 > > echo "Changing permissions for IDEA installation: $INSTALL_DIR" > > chown -R :dev $INSTALL_DIR > chmod -R o-rwx $INSTALL_DIR > chmod -R g+u $INSTALL_DIR > > rm current > ln -s $INSTALL_DIR current > ln -s ../jre $INSTALL_DIR/jre > ]]>
This needs a little explanation... most of it is self explanitory except
maybe:
chown -R :dev $INSTALL_DIR > chmod -R o-rwx $INSTALL_DIR > chmod -R g+u $INSTALL_DIR > ]]>
What this does is that it changes the ownership of all files and assignes
them to the group "dev". This is specific for my installation because I
have a group called "dev" that I put all users in that are developers and
should therefore have access to all development tools... you can use
whatever group you see fit. Next, it changes the permission bits on all
the files and removes all permission from the the user group "other"
(since we don't want anybody to be able to run IDEA). At last, we change
the permission on all the files in such a way that we assign the same
permission to the user group "group" as the user group "file owner" has.
This means that the group "dev" now has the same permission as the owner
of the file... so anybody in the group "dev" can run IDEA but everybody
else will not be able to experience the bliss ;o)

Hope this will help somebody.
Kind regards, Stefan Freyr.


0
Comment actions Permalink

There's one more thing you have to do:
copy the bin and lib directories from the JDK to idea's (or any other) JRE directory.

Idea expects the javac compiler in jre/bin (though it is usually loacted in jdk/bin).

0

Please sign in to leave a comment.