It is similar to "dos-based" in its path and classpath separations, but the long volume names and subtleties in whether or not a path name should be specified with java commands are different. So, I don't know if you can generally lump us in the "dos-based" category, since this assumption breaks down in some places. Maybe I am misunderstanding where you are going to make this distinction, and it will turn out to be fine.
Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net services software. >>> [EMAIL PROTECTED] 11/2/01 12:14:04 AM >>> On Wed, 31 Oct 2001, Jeff Tulley <[EMAIL PROTECTED]> wrote: > It seems like there was an env thing in their somewhere also, that > needed to be cleared up for NetWare. "env" is a system console > command in netware, so can be executed without any path at all. I'll adapt to that, please take a look at my commit that should happen sometime today. > 2) We use ";" (semi-colon) for classpath separators So Os.java will consider it DOS based (whatever that means in detail) - is this a good assumption or should the code specifcally exclude NetWare. Given your description, we probably better say netware is nor DOS-based. > 3) We have something similar to drive letters, volume names, which > can be up to 40 characters large, followed by a colon. data:\ (or > data:/) for example. > 4) if you do not specify a volume name, (/usr/bin), NetWare assumes > the sytem volume, "SYS:/usr/bin" Reminds me on my old VMS days ... Stefan who sometimes misses his VAX-Station. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
