From: Osvaldo La Rosa <blinuxman@tuxfamily.org>
To: blinux-list@redhat.com
Subject: Re: Java Development Kit
Date: Wed, 16 Oct 2002 08:52:31 +0200 [thread overview]
Message-ID: <20021016085231.F247@torvalds> (raw)
In-Reply-To: <878z10kmxi.fsf@lexx.delysid.org>; from mlang@teleweb.at on Tue, Oct 15, 2002 at 12:37:29PM +0200
Hello Roberet,
If you are talking about the latest ZipSlack, v8.1, you must know that
there is probably no make no other dev elements on it, since I have used
a zipslack to build BrlZip, i wasn't able to compile brltty, but v8.0
still contains a development part.
Maybe this can resolve your problem, but of course it's better to switch
to a real-full Gnu/Linux distro.
Osvaldo La Rosa - http://www.brlspeak.net/brlzip/
On Tue, Oct 15, 2002 at 12:37:29PM +0200, Mario Lang 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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Robert Bebee
` Mario Lang
` Osvaldo La Rosa [this message]
` Janina Sajka
Robert Bebee
Robert Bebee
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=20021016085231.F247@torvalds \
--to=blinuxman@tuxfamily.org \
--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).