Bugs item #781779, was opened at 2003-08-01 14:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=379534&aid=781779&group_id=23735
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Radestock (mradestock)
Assigned to: Nobody/Anonymous (nobody)
Summary: slib software-type detection broken on some OSes
Initial Comment:
slib need a function SOFTWARE-TYPE that returns the
type of operating system. Currently SISC's slib
bindings call SISC's DETECT-OS function. This is the
only place (other than possible user code) where
DETECT-0S is used.
The problem is twofold:
1) It's also not at all clear what the legal values are
the slib expects - the only way to find that out, it
appears, is to grep through the slib source, which is
subject to change.
2) DETECT-OS analyses the value of the Java os.name
system property. There does not appear to be any
definitive list anywhere of what the legal values for
that property are.
So in order to get SISC's slib integration to work
across multiple platforms we are left in the
unfortunate situation of having to map one unknown set
of data to another unknown set of data.
These issues came up when SISC was run on a sunos box -
the os.name was not a value recognized by DETECT-OS.
Chances are there are quite a few other OSes where SISC
would encounter similar problems.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=379534&aid=781779&group_id=23735
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
|
