At 06:57 PM 3/17/00 -0500, "Todd L. Miller" <[EMAIL PROTECTED]> wrote:
> The 1.1.8 JDK classes.zip I've got is 9122642 bytes, so I guess
>Corrado is using a different version. Whatever works.
Starting with rt.jar or classes.zip from Java 1, you can safely remove the
JavaDoc application, the javac application, and some of the un-used,
un-necessary packages. Here are a few packages that you can't use (yet).
java.applet
java.awt.*
java.beans
java.rmi.*
java.sql
sun.applet.*
sun.awt.*
sun.beans.*
sun.jdbc.odbc
sun.rmi.*
And, here are some of the packages you can't use without a TCP/IP stack:
java.net
sun.net.*
If you're not going to use them, why should you load them? If you have a
machine with 8MB+, you should be able to load and run JOS for a few
seconds. Our recommendation will be 16MB+ of RAM.
Consumers do not want to load packages they don't use. Consumers do not
want JavaDoc in their toaster. The rt.jar and classes.zip architecture
doesn't work for Sun either.
Regardless, Sun Microsystems frowns upon anyone removing *any* class from
rt.jar or classes.zip.
JOS should not carry the JavaDoc application around in its core classes,
should it? JOS should not carry all those classes that use JNI-based native
methods, should it? Ultimate JOS should load packages on demand, delaying
the load from disk or network service until they are actually used. We are
not required to use it.
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
