Re: Quite Well Done! (offtopic)
Me too. [EMAIL PROTECTED]
Re: UI java-Unix
Laura <[EMAIL PROTECTED]> writes:
> try{
> String[] com_ps=
> {"/bin/sh", "-c", "/bin/chmod 755 esegue", "./esegue"};
> Process p = Runtime.getRuntime().exec(com_ps);
> }catch (IOException e0){
> System.err.println(e0);
> System.exit(0);
> }
> }
Runs fine with me: the permissions of the file esegue is indeed
changed to rwxr-xr-x, consistent with the command you specify in
com_ps.
> Does anybody know what kind of problem is?
I also want to know. What problem? I don't see any problem.
--
[If you post a response, no need to cc me; if you cc me, please say so.]
"Microsoft is now the bottleneck for all significant innovation in the
computer graphics industry." - Alan Akin
Problem starting java with jdk1.1.6v4a-i386-glibc
I just downloaded and installed jdk1.1.6v4a-i386-glibc.tar.gz as the instructions in the README specify. However, I can't seem to get Java running: [chroma@chroma /extra]$ java /usr/local/java/bin/../bin/i486/green_threads/java: error in loading shared libraries libXp.so.6: cannot open shared object file: No such file or directory [chroma@chroma /extra]$ Here's the output of ldconfig -D [chroma@chroma /extra]$ ldconfig -D ldconfig: version 970402 /usr/X11R6/lib: libXpm.so.4 => libXpm.so.4.8 libXaw3d.so.6 => libXaw3d.so.6.0 libXtst.so.6 => libXtst.so.6.0 libXt.so.6 => libXt.so.6.0 libXmu.so.6 => libXmu.so.6.0 libXi.so.6 => libXi.so.6.0 libXext.so.6 => libXext.so.6.0 libXaw.so.6 => libXaw.so.6.0 libXIE.so.6 => libXIE.so.6.0 libX11.so.6 => libX11.so.6.0 libSM.so.6 => libSM.so.6.0 libPEX5.so.6 => libPEX5.so.6.0 libICE.so.6 => libICE.so.6.0 /usr/i486-linuxaout/lib: libvga.so.1 => libvga.so.1.2.7 libtk.so.3 => libtk.so.3.1.1 libtcl.so.3 => libtcl.so.3.1 libm.so.4 => libm.so.4.6.27 libdb.so.1 => libdb.so.1.85.1 libcurses.so.0 => libcurses.so.0.1.2 libc.so.4 => libc.so.4.7.2 libXt.so.6 => libXt.so.6.0 libXt.so.3 => libXt.so.3.1.0 libXpm.so.4 => libXpm.so.4.2 libXaw.so.6 => libXaw.so.6.0 libXaw.so.3 => libXaw.so.3.1.0 libXIE.so.6 => libXIE.so.6.0 libX11.so.6 => libX11.so.6.0 libX11.so.3 => libX11.so.3.1.0 /usr/i486-linux-libc5/lib: ldconfig: warning: /usr/i486-linux-libc5/lib/libform.so.1.9.9e has inconsistent soname (libform.so.3.0) ldconfig: warning: /usr/i486-linux-libc5/lib/libmenu.so.1.9.9e has inconsistent soname (libmenu.so.3.0) ldconfig: warning: /usr/i486-linux-libc5/lib/libncurses.so.1.9.9e has inconsistent soname (libncurses.so.3.0) ldconfig: warning: /usr/i486-linux-libc5/lib/libpanel.so.1.9.9e has inconsistent soname (libpanel.so.3.0) libvgagl.so.1 => libvgagl.so.1.2.11 libvga.so.1 => libvga.so.1.2.11 libtermcap.so.2 => libtermcap.so.2.0.8 libstdc++.so.27 => libstdc++.so.27.1.4 libpanel.so.3.0 => libpanel.so.1.9.9e libncurses.so.3.0 => libncurses.so.1.9.9e libmenu.so.3.0 => libmenu.so.1.9.9e libm.so.5 => libm.so.5.0.6 libg++.so.27 => libg++.so.27.1.4 libform.so.3.0 => libform.so.1.9.9e libc.so.5 => libc.so.5.3.12 libXtst.so.6 => libXtst.so.6.1 libXt.so.6 => libXt.so.6.0 libXpm.so.4 => libXpm.so.4.9 libXmu.so.6 => libXmu.so.6.0 libXi.so.6 => libXi.so.6.0 libXext.so.6 => libXext.so.6.3 libXaw3d.so.6 => libXaw3d.so.6.1 libXaw.so.6 => libXaw.so.6.1 libXIE.so.6 => libXIE.so.6.0 libX11.so.6 => libX11.so.6.1 libSM.so.6 => libSM.so.6.0 libPEX5.so.6 => libPEX5.so.6.0 libICE.so.6 => libICE.so.6.3 /usr/lib: ldconfig: warning: /usr/lib/libhistory.so.2.0 has inconsistent soname (libreadline.so.2) ldconfig: warning: /usr/lib/libform.so.1.9.9e has inconsistent soname (libform.so.3.0) ldconfig: warning: /usr/lib/libmenu.so.1.9.9e has inconsistent soname (libmenu.so.3.0) ldconfig: warning: /usr/lib/libncurses.so.1.9.9e has inconsistent soname (libncurses.so.3.0) ldconfig: warning: /usr/lib/libpanel.so.1.9.9e has inconsistent soname (libpanel.so.3.0) libgimpui.so.1 => libgimpui.so.1.0.0 libgimp.so.1 => libgimp.so.1.0.0 libpng.so.2 => libpng.so.2.1.0 libgtk.so.1 => libgtk.so.1.0.5 libglib.so.1 => libglib.so.1.0.5 libgdk.so.1 => libgdk.so.1.0.5 libgck.so.1 => libgck.so.1.0.0 libqt.so.1 => libqt.so.1.40 libXpm.so.4 => libXpm.so.4.9 libforms.so.0.86 => libforms.so.0.86 libpanel.so.3.0 => libpanel.so.1.9.9e libncurses.so.3.0 => libncurses.so.1.9.9e libopcodes.so.2.7.0.2 => libopcodes.so.2.7.0.2 libbfd.so.2.7.0.2 => libbfd.so.2.7.0.2 libtk4.1.so => libtk4.1.so libtkx.so => libtkx.so libtkx.so.41.2 => libtkx.so.41.2 libtcl7.5.so => libtcl7.5.so libmenu.so.3.0 => libmenu.so.1.9.9e libjpeg.so.62 => libjpeg.so.62.0.0 libstdc++.so.27 => libstdc++.so.27.1.4 libg++.so.27 => libg++.so.27.1.4 libgdbm.so.2 => libgdbm.so.2.0.0 libform.so.3.0 => libform.so.1.9.9e libstdc++.so.2.8 => libstdc++.so.2.8.0 libz.so.1 => libz.so.1.0.4 libtclx.so => libtclx.so libtclx.so.75.2 => libtclx.so.75.2 libvga.so.1 => libvga.so.1.2.10 libvgagl.so.1 => libvgagl.so.1.2.10 libslang.so.0 => libslang.so.0.99.33 libreadline.so.2 => libreadline.so.2.0 libnewt.so.0 => libnewt.so.0.6 libtiff.so.3 => libtiff.so.3.4.28 librle.so.1 => librle.so.1.0.0 libppm.so.1 => libppm.so.1.0.0 libpnm.so.1 => libpnm.so.1.0.0 libpgm.so.1 => libpgm.so.1.0.0 libpbm
using ddd w/ java?
has anyone done an FAQ on this? how do i get started (never used DDD before, as most of my unix work is in perl and generally don't feel the need for an graphical debugger...however with java...) thnx for any help! -- "a gust of wind...a dog barks..."
To read from a port
Hi. There is somebody who can tell me how to get information from a Ethernet card on my PC system? Of course, I know the protocol of the outward system. Thanks.
Reading /dev/cua? or /dev/ttyS?
Brazilian Hello ! I have a CodeBar Reader attached at /dev/cua1 and I can read from it from some applications, opening the "/dev/cua1" file and reading from it ! There is any way to do this with java ? Thanks for any hint ! Fernando Soares Barrocal Technology Analyst TEAM Systems
Re: To read from a port
On Sun, 13 Sep 1998 20:56:35 +0200, Carlos Garcia wrote: >Hi. There is somebody who can tell me how to get information from a >Ethernet card on my PC system? Of course, I know the protocol of the outward >system. >From the ethernet card? Or do you want to read from a TCP/IP (TCP or UDP) data stream? Directly from the card is non-trivial in Java (as in you will need to do native methods and maybe even more complex code to deal with the green threads) However, do networked (Sockets and UDP datagrams) that is all supported in Java at the pure-Java level. Check on the java.net package, and specifically the java.net.Socket and java.net.DatagramSocket Michael Sinz -- Director of Research & Development, NextBus Inc. mailto:[EMAIL PROTECTED] - http://www.nextbus.com My place on the web ---> http://www.users.fast.net/~michael_sinz
Re: Reading /dev/cua? or /dev/ttyS?
On Sun, 13 Sep 1998 17:46:39 -0300, Fernando Soares Barrocal wrote: > >Brazilian Hello ! > >I have a CodeBar Reader attached at /dev/cua1 and I can read from it from >some applications, opening the "/dev/cua1" file and reading from it ! > >There is any way to do this with java ? Well, if you do not need to do anything other than opening and read/write operations, just open that as a file in Java. Then do the byte I/O or stream I/O to/from it. However, controlling the data rate and other serial port parameters will need to be done with either an external program/native methods or the new Java Serial (RXTX) extensions. (I have not played with those as they came out well after I had needed to do serial port stuff...) What I did was to use stty and then to run the Java code with the /dev/cua1 name for the file. (This is not very cross platform other than within Unix worlds and even then stty has some strange behaviors) Michael Sinz -- Director of Research & Development, NextBus Inc. mailto:[EMAIL PROTECTED] - http://www.nextbus.com My place on the web ---> http://www.users.fast.net/~michael_sinz
Re: Well done
Yes! we are all grateful for the wonderful work that they are doing for *US*. A very big Thank You. And it was nice of you James to think of this Regards S.Ramaswamy James Howe wrote: > To Everyone,, > > It is very easy just to get caught up in all the errors about the jdk that get > posted to this list. Therefore we must remember what a huge service the porting > team is doing for *US* ! I would like to see Sun Micro give the guys at > Blackdown a lot of money and resources to do an even better job. Remember > they do it for free and with limited resources. But in the mean time I suggest > we have a "show your support" week, where everyone sends email to the > team and says thankyou. Yeah i know that means a lot of mail but I think it > would still be very worth it. > > what does everyone else think ? > > James Howe > > P.S. Thanks alot guys !!
Re: Well done
> > what does everyone else think ? > > > > James Howe I just joined this list today, and I just started using the Linux Java port today, but I am very appreciative. Not being a proficient coder, I am very grateful that someone has ported this and made it available to schmucks like me. This Java port is helping me keep in touch with my family and friends while I'm at college... (via AIM and ICQ) Thanks, Java-linux team! Ethan
Re: Well done
I could write a long one, but I'll keep it short. Thanks! and amazingly it works. smbinyon
Re: Trouble compiling
Gudmundur Erlingsson wrote: > > Hi there, > > This is probably quite a simple problem with an appropriately simple > solution, but I sure don't know how to solve it. I downloaded the > jdk-sbb-1.1.6-4a.glibc.i386.rpm from the redhat ftp-site and installed it > just fine. But when I try to compile a simple test-program using the > `javac' command the following message is displayed: > > "javac was not found in /usr/bin/jdk-1.1.6/../bin/i586/green_threads/javac" > > Now, I checked the /usr/bin directory and there I have javac linked to > /usr/bin/jdk1.1.6/javac which is in turn linked to .java_wrappers. Does > anyone know how I can work this out? Should I link /usr/bin/javac to > /usr/bin/jdk-1.1.6/i586/green_threads/javac or do something else? It would > be absolutely triffic if someone could help. (In addition, the same error > message is displayed if I try to run appletviewer). since this is the most common problem I will patch .java_wrapper in the next rpm too... you /etc/profile.d/*.sh scripts doesn't run on login time (as it should have to run through /etc/profile). -- Levente -- E-Mail: Levente Farkas <[EMAIL PROTECTED]> Homepage: http://www.inf.u-szeged.hu/~lfarkas/ PGP public key & Geek Code: [EMAIL PROTECTED] --
