I haven't taken a good look at the rheise.os classes as I should have by now
(been busy with the day job), but from what I understand, they implement a
large set of functionality that is intended for jos.core.* (ie. the process
management). With that in mind I think his using jos.core,
jos.core.process, or just jos.process would be fine. jos.system.* has a
different purpose from process management.
Avery J. Regier
Information Technology Analyst
WebWorks Team
Consumer & Commercial Equipment Division, Deere & Co
> -----Original Message-----
> From: Gilbert Carl Herschberger II [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 15, 2000 11:19 AM
> To: [EMAIL PROTECTED]
> Subject: [JOS-Kernel] [rheise.os 0.1.4] Warning
>
> Warning: Ryan Heise <[EMAIL PROTECTED]> has introduced a second and
> incompatible package called jos.system. Both packages should not be used
> at
> the same time. I have privately encouraged Ryan to select another package
> name, but without success.
>
> The jos.system package inside rheise.os 0.1.4 pre-release clashes with the
> existing jos.system package inside JJOS module from JOS CVS. The original
> jos.system package contains the following classes and are critical to
> operation of decaf:
>
> console
> consoled
> ConsoleDriver
> interrupt
> interrupts
> machine
>
> Ryan says the original jos.system must be renamed to something else so
> that
> Ryan can use jos.system for rheise.os. Ryan wants us to rewrite jJOS/decaf
> and rework all of its documentation to use other package names.
>
> How do you feel about this?
>
>
> _______________________________________________
> Kernel maillist - [EMAIL PROTECTED]
> http://jos.org/mailman/listinfo/kernel
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
