public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Robert Bebee <rbebee@iquest.net>
To: blinux-list@redhat.com
Subject: Re: Java Development Kit
Date: Wed, 16 Oct 2002 22:30:57 -0500	[thread overview]
Message-ID: <3.0.32.20021016223056.0146aa60@iquest.net> (raw)

I wanted to write and run some applications.  The compiler (javac) wouldn't
run.  The problem may have been a simple as revising the PATH variable, but
I decided to wait until I had a more robust Linux than zipslack-- figured
the file zipslack file system might cause Java some problems.  

So far, except for a couple of applets, I've just written apps that run in
a DOS box-- I planned to work mostly with console mode programs under
Linux-- web crawlers, math programs, text manipulation, etc.  

I hadn't seen anything about Java on this list, but hoped some other
blinuxers were at least tinkering with Java.

Thanks for feedback.

At 12:37 PM 10/15/02 +0200, you wrote:
>Robert Bebee <rbebee@iquest.net> writes:
>
>> I've been practicing with a zipslack installation, and I'm considering 
>> going for a purer Linux.  I'd like to work with Java.  I installed a 
>> JDK (Java Development Kit) on my zipslack-- it installed okay, but I 
>> couldn't do anything with it.
>
>What did you want to do?  All command-line / text-output
>based java apps should work (there are practically none...).
>And GUI java stuff does *NOT* work under Linux,
>because there is still no working Java-enabled screen reader.
>IBM wrote the SVK, but they only supported Windows and Solaris.
>
>
>-- 
>CYa,
>  Mario
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>




             reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Robert Bebee [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Robert Bebee
 Robert Bebee
 ` Mario Lang
   ` Osvaldo La Rosa
   ` Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.32.20021016223056.0146aa60@iquest.net \
    --to=rbebee@iquest.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).