Java Runtime Environment (SFS)
jre-1.7.0.45
Updated:
jre-1.7.0.45.sfs and jre-1.7.0.25-1.sfs if you want older version.
Both from http://shino.pos.to/party/bridge.cgi?puppy/opt/
jre-1.7.0.45.sfs and jre-1.7.0.25-1.sfs if you want older version.
Both from http://shino.pos.to/party/bridge.cgi?puppy/opt/
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: jre-1.7.0.45
Thank you. I shared your link here for those who use Java along with LibreOffice.shinobar wrote:Updated:
jre-1.7.0.45.sfs and jre-1.7.0.25-1.sfs if you want older version.
Both from http://shino.pos.to/party/bridge.cgi?puppy/opt/
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]
Hi Shinobar
Thanks for continuing to package Java. I recently wanted to run .jnlp webstart files (javaws binary). For some reason your version of jre-1.7u45-i586.sfs didn't work for this purpose (I'm on Slacko 5.3.1).
Details here-
http://www.murga-linux.com/puppy/viewto ... 130#751130
Thanks for continuing to package Java. I recently wanted to run .jnlp webstart files (javaws binary). For some reason your version of jre-1.7u45-i586.sfs didn't work for this purpose (I'm on Slacko 5.3.1).
Details here-
http://www.murga-linux.com/puppy/viewto ... 130#751130
to run .jnlp webstart files
Have you tried jre-1.7.0.45.sfs instead of jre-1.7u45-i586.sfs?darkcity wrote:For some reason your version of jre-1.7u45-i586.sfs didn't work for this purpose (I'm on Slacko 5.3.1).
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
I have now tried jre-1.7.0.45.sfs, it gives the same result as jre-1.7u45-i586.sfs
The javaws binary is stored in /usr/bin
Using /usr/bin/javaws "$@" as the run action for a .jnlp file, gives the unable to launch with an exception error
in the java sfs packaged by OscarTalks the javaws is stored in /usr/local/bin and using /usr/local/bin/javaws "$@" successfully launches the .jnlp app.
The javaws binary is stored in /usr/bin
Using /usr/bin/javaws "$@" as the run action for a .jnlp file, gives the unable to launch with an exception error
in the java sfs packaged by OscarTalks the javaws is stored in /usr/local/bin and using /usr/local/bin/javaws "$@" successfully launches the .jnlp app.
Java Update 51 now current
Java SE 7 Update 51 Released 1 /14/14
When can this be presented?
When can this be presented?
- Puppus Dogfellow
- Posts: 1667
- Joined: Tue 08 Jan 2013, 01:39
- Location: nyc
Re: Java Update 51 now current
gcmartin wrote:Java SE 7 Update 51 Released 1 /14/14
When can this be presented?
jre-1.7u51-i586.pet
or
http://forum.asri-education.org/viewtop ... f=39&t=313
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Users seem to be finding that different versions by different posters may or may not work on their systems. I'm not sure why this is. I would have expected /usr/local/bin to work the same as /usr/bin for the executable symlinks. I just didn't like the idea of a /usr/java directory so I put the main folder in /usr/local instead and from there I kept the symlinks down the /usr/local path. To be honest I don't use jre for anything. I just made one when I was testing jitsi which I have since given up on.
Anyway, not wishing to step on any toes, but a few days ago I did upload a .pet and a .sfs of jre-1.7u51-i586 put together along the same lines as the previous one:-
http://smokey01.com/OscarTalks
Other versions by other posters are available. I haven't tested this one much. Users should experiment and see which one works best for them.
Anyway, not wishing to step on any toes, but a few days ago I did upload a .pet and a .sfs of jre-1.7u51-i586 put together along the same lines as the previous one:-
http://smokey01.com/OscarTalks
Other versions by other posters are available. I haven't tested this one much. Users should experiment and see which one works best for them.
Oscar in England
OscarTalks shares a problem that has existed with PUP over time; namely, different developers install apps differently based upon a concept that they feel is best. This has happened couple years ago when SAMBA was first being tackled and certainly is happening here.
With SAMBA, the problem subsided when @01Micko (32bit) and @TaZoC (64bit) combined in agreement to settle on a consistent Library and executable paths. Other developers, @Pemasu, and others also used this PET and pathing in their distros for consistency. Today, using some of PUP distros, the user sees exactly the same experience when using or 'install and using' that consistent version for sharing information on the LAN. This reduced user efforts and increase user understanding and productive use.
But, that level of consistency has NOT happened here with JAVA, just yet.
This is of issue for PUPs future because of the increase of Smart devices as JAVA and eClipse can be integral in advancing PUPs as a platform for integrating smart devices into the LAN fabric that PUPs reside on.
Wise cooperation and discussion can bring some common light to a pleasant ride into PUP's present and future. Iam NOT suggesting "yielding" one vs another, I am, though, suggesting developers discussion for good and sound direction so that other projects and products which rely on JAVA-JRE & JAVA-JDK are placed such that eClipse and other tools from MIT and others can install and find their way without issue. 2 heads are certainly better than one as it embraces complementary viewpoints for greater achievement in many and most cases.
Maybe JAVA, as is the case with Flash, really should be in base PUPs to reduce user confusion. Some distro developers have already begun addressing this in their PUP distros as they are including Flash, OOTB.
Hope this helps
Puppy Linux References
Link specific to JAVA's pathing issue
JAVA issues and developer comments
JAVA apps that are known to work in Puppy Linux
Puppy Linux Wikis on JAVA need
Puppy Linux Wikis on JAVA locations in Puppyland
etc.....
With SAMBA, the problem subsided when @01Micko (32bit) and @TaZoC (64bit) combined in agreement to settle on a consistent Library and executable paths. Other developers, @Pemasu, and others also used this PET and pathing in their distros for consistency. Today, using some of PUP distros, the user sees exactly the same experience when using or 'install and using' that consistent version for sharing information on the LAN. This reduced user efforts and increase user understanding and productive use.
But, that level of consistency has NOT happened here with JAVA, just yet.
This is of issue for PUPs future because of the increase of Smart devices as JAVA and eClipse can be integral in advancing PUPs as a platform for integrating smart devices into the LAN fabric that PUPs reside on.
Wise cooperation and discussion can bring some common light to a pleasant ride into PUP's present and future. Iam NOT suggesting "yielding" one vs another, I am, though, suggesting developers discussion for good and sound direction so that other projects and products which rely on JAVA-JRE & JAVA-JDK are placed such that eClipse and other tools from MIT and others can install and find their way without issue. 2 heads are certainly better than one as it embraces complementary viewpoints for greater achievement in many and most cases.
Maybe JAVA, as is the case with Flash, really should be in base PUPs to reduce user confusion. Some distro developers have already begun addressing this in their PUP distros as they are including Flash, OOTB.
Hope this helps
Puppy Linux References
Link specific to JAVA's pathing issue
JAVA issues and developer comments
JAVA apps that are known to work in Puppy Linux
Puppy Linux Wikis on JAVA need
Puppy Linux Wikis on JAVA locations in Puppyland
etc.....
running .jnlp file
Strange. I found no problem on Precise-571JP.darkcity wrote:I have now tried jre-1.7.0.45.sfs, it gives the same result as jre-1.7u45-i586.sfs
The javaws binary is stored in /usr/bin
Using /usr/bin/javaws "$@" as the run action for a .jnlp file, gives the unable to launch with an exception error
Will you point some file for testing?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
jre-1.7.0.51.sfs
UPDATE: jre-1.7.0.51.sfs
http://shino.pos.to/party/bridge.cgi?puppy/opt/
NOTE on the difference with the one by OscarTalks:
1. JAVA_HOME is /usr/java for mine, whereas /usr/local/java by OscarTalks.
2. Three executables are under /use/bin for mine, whereas OscarTalks made more links at /usr/local/bin.
3. Mine has the ROX-Filer stuff under /root and under /usr/local/apps/ROX-File.
http://shino.pos.to/party/bridge.cgi?puppy/opt/
NOTE on the difference with the one by OscarTalks:
1. JAVA_HOME is /usr/java for mine, whereas /usr/local/java by OscarTalks.
2. Three executables are under /use/bin for mine, whereas OscarTalks made more links at /usr/local/bin.
3. Mine has the ROX-Filer stuff under /root and under /usr/local/apps/ROX-File.
I tried a couple of apps.
This one for example
CGoban 3 - KGS
http://files.gokgs.com/javaBin/cgoban.jnlp
I downloaded to ~/my-applications and ran from there.
This one for example
CGoban 3 - KGS
http://files.gokgs.com/javaBin/cgoban.jnlp
I downloaded to ~/my-applications and ran from there.
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
I was trying to take a look at some of the other people's jre packages and comparing them with mine. I am no expert on jre, but just to mention a few things I did which may be different:-
I try to go through it and strip everything. This should not affect the function though, it just reduces the size by a very small amount.
I also try to make sure all the permissions are correct and that all the files are owner=root and group=root. Some of the other packages have not done this and although things usually still work if you don't chown to root:root I wonder if that is the cause in this case?
I try to go through it and strip everything. This should not affect the function though, it just reduces the size by a very small amount.
I also try to make sure all the permissions are correct and that all the files are owner=root and group=root. Some of the other packages have not done this and although things usually still work if you don't chown to root:root I wonder if that is the cause in this case?
Oscar in England
@Shinobar & @OscarTalks
Both of you are a credit to the community. Thanks for what each of you are doing to give us this tools and JDK (whose need is becoming more and more apparent as smartDevices are increasing in both number and ability to allow customization by any owner/user).
And certainly, THANKS to both of you, for both of what each is sharing in this thread.
It would be nice to combine your efforts as this is an important need where a consistent PET and SFS for both 32bit and 64bit PUPs can use. Reason: When any user presents a problem if the subsystems were consistent, it could/would reduce developer/member confusion as they assist problem resolution(s).
As such, here is a idea of what is faced with in the PLDF community.
I hope you are able to combined your efforts or come to an agreement on approaches for the mutual benefit of both of you and the community. The 2 of you are providing a very necessary community benefit as smart devices grow as well as cross-system apps continue in numbers. At least the 2 of you understand this need.
Thanks for what you 2 have done thus far with the useful stuff you do.
Both of you are a credit to the community. Thanks for what each of you are doing to give us this tools and JDK (whose need is becoming more and more apparent as smartDevices are increasing in both number and ability to allow customization by any owner/user).
And certainly, THANKS to both of you, for both of what each is sharing in this thread.
It would be nice to combine your efforts as this is an important need where a consistent PET and SFS for both 32bit and 64bit PUPs can use. Reason: When any user presents a problem if the subsystems were consistent, it could/would reduce developer/member confusion as they assist problem resolution(s).
As such, here is a idea of what is faced with in the PLDF community.
- The need for JRE for in 32bit (this may in the future of PUPs become an OOTB in base 32bit PUPs)
- The need for JRE for 64bit(this may in the future of PUPs become an OOTB in base 64bit PUPs)
- The need for JDK in 32bit or at least a consistent install to a system with a JRE.
- The need for JDK in 64bit or at least a consistent install to a system with a JRE.
- The functionality needs to be full.
I hope you are able to combined your efforts or come to an agreement on approaches for the mutual benefit of both of you and the community. The 2 of you are providing a very necessary community benefit as smart devices grow as well as cross-system apps continue in numbers. At least the 2 of you understand this need.
Thanks for what you 2 have done thus far with the useful stuff you do.
the permissions
That's itOscarTalks wrote:I also try to make sure all the permissions are correct and that all the files are owner=root and group=root. Some of the other packages have not done this and although things usually still work if you don't chown to root:root I wonder if that is the cause in this case?
The file darkcity gave me checks the permission and refuses if it is not proper.
CGoban 3 - KGS
http://files.gokgs.com/javaBin/cgoban.jnlp
I take all the contents from the one OscarTalks made. Add the ROX-Filer MIME stuff.
Uploaded jre-1.7.0.51-1.sfs
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Next pet is the ROX-Filer MIME stuff only:
http://shino.pos.to/party/bridge.cgi?pu ... -jre-1.pet
If you install the jre-1.7u51-i586 by OscarTalks and this rox_filer-MIME-jre-1.pet, it is equivalent with the jre-1.7.0.51-1.sfs above.
Thanks both of you, darkcity and OscarTalks.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]