[Sorry for the length. Executive Summary:
There are several things that a project needs to be able to articulate
to themselves, their CG and to the ARC:
What do you intend to do (problem statement, scope),
How will it impact existing promises and expectations (what does it change),
Wh
ic, and as external community
members, we can not always fully relate. (As certain "requirements" make
little sense within the scope of the externally facing realm of OpenSolaris
development).
Thanks,
Brian
>
>-John
>
>
--
- Brian Gupta
http://opensolaris.org/os/project/nycosug/
http://www.genunix.org/wiki/index.php/OpenSolaris_New_User_FAQ
-- next part --
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/install-discuss/attachments/20080211/7cb63ac9/attachment.html>
Robert Harryman wrote:
> I'm involved with a Pegasus CIM-ON port that can be configured to use OpenSLP
> to do a service registration. Is OpenSLP bundled in with nevada? If so,
> what is it's home path?
>
> thx,
> -bob
>
No, but there's a Solaris SLP implementation which is included, it's
fair
John Plocher wrote:
> Brian Gupta wrote:
>> Currently we are have reached a point where we have Conary packaging
>> system running on Solaris (both Sparc and x86).
>
>> We seek guidance as to the proper course of action. (What criteria is the
>> ARC looking for?)
>
>
> There are several questi
I'm involved with a Pegasus CIM-ON port that can be configured to use OpenSLP
to do a service registration. Is OpenSLP bundled in with nevada? If so,
what is it's home path?
thx,
-bob
This message posted from opensolaris.org
Nils -
I would certainly agree that diskless/swapfull clients are an important
part of the OS makeup, but a project would be a better place to start.
The tool enhancement of 'smdiskless' and the OS services necessary to
provide diskless support are welcome.
being an old Sun 3/60 administrator
