Hi,

Here's OpenSolaris Weekly News #4. As always feedback, or content [from
the missing represented communities] welcome.

Glynn

==

John Cui posted [1] about a problem he had hit while trying to get st_ino
from stat using DTrace. Chris Gerhard replied [2] that it was because he 
was trying to copy a 32 bit stat structure into a 64 bit one. Adam Leventhal
followed up [3] to say that he was copying in the stat structure for both
lstat and lstat64 system calls.

1. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-March/001213.html
2. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-March/001215.html
3. http://mail.opensolaris.org/pipermail/dtrace-discuss/2006-March/001216.html

Dermot McCluskey announced [4] that build 07 of project Vermillion, a set of 
alpha release of the next version of JDS [currently based on GNOME 2.14.0], was
now available.

4. http://mail.opensolaris.org/pipermail/desktop-discuss/2006-March/000584.html

Roland Mainz asked [5] if it was possible to turn add '-xstrconst 
-xbuiltin=%all'
to the build. Jonathan Adams replied [6] saying that using -xbuiltin could
be very costly, since inlining bloated the text segment, and that some 
benchmarks
would be required. Keith Wesolowki replied [7] that he would welcome a patch
for -xstrconst provided that the test coverage included every single binary 
whose compile time options changed as a result. Keith followed up [8] with one
way of going about it, and explained some of the processes involved.

5. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014287.html
6. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014290.html
7. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014329.html
8. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014335.html

Carol Gayo mailed [9] with a proposal for project Crossbow, a network 
virtualization
technology that greatly improves resource control, performance and network 
utilization need to achieve a true OS virtualization, utility computing and 
server consolidation. Nicolas Droux proposed [10] project Nemo, aiming to 
improve
the performance, and accelerate development and adoption of high-performance 
network
drivers.

9.  
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014149.html
10. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014120.html

Karyn Ritter announced [11] that build 35 of Solaris Express Community Release 
was
now available.

11. 
http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-March/000079.html

Marilyn Shoemaker mailed [12] announcing that the SFW consolidation expected to 
begin regular source tarball releases from next week. She commented that bug 
fixes
from the community would be dealt with following the current ON model.

12. http://mail.opensolaris.org/pipermail/request-sponsor/2006-March/000315.html

Nils Nieuwejaar proposed [13] a Solaris internals community specifically 
targetted
on providing a low level, technical forum for design and development of the core
operating system. Stephen Hahn replied [14] asking for further clarification on
how this project overlapped with existing communities and projects.

13. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014186.html
14. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014194.html

Eric Lowe followed up [15] asking for feedback from the documentation 
community. 
Susan Weber replied [16] saying that it would be a good pilot for a mechanism 
for 
gathering and releasing documentation. Eric reassured [17] that the proposd 
project complement and not replace hype of the new version of the Solaris 
Internals
book. Keith Wesolowski commented [18] that it was up to the individual members 
of 
each of the communities to figure out what they found most important in terms
of content, rather than it being mandated by Sun.

15. http://mail.opensolaris.org/pipermail/docs-discuss/2006-March/000313.html
16. http://mail.opensolaris.org/pipermail/docs-discuss/2006-March/000316.html
17. http://mail.opensolaris.org/pipermail/docs-discuss/2006-March/000320.html
18. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014328.html

Mike Kupfer mailed [19] suggesting that opensolaris-{code, rfe, bugs} could go
away, since they now had better replacements in the various communities and 
projects that have since been formed, along with the online bug database. Peter
Tribble argued [20] that they should not go away until the submission process 
for
bugs and rfes is significantly improved.

19. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014215.html
20. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014322.html

Jonathan Adams proposed [21] a libumem project, within the Performance and 
Moduler
Debugger communities aimed at discussion and development of libumem(3lib). 

21. 
http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/014213.html

Bonnie Corwin mailed [22] a presentation about the current status of SCM on
OpenSolaris. A centralized server is scheduled for completion, budget pending,
by the end of May; while a distributed server for ON is scheduled for multiple
targets, completing in early 2007. Bonnie also posted [23] the latest version
of the contributor agreement.

22. http://mail.opensolaris.org/pipermail/program-team/2006-March/000172.html
23. 
http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-March/000077.html

Liane Praza mailed [24] with a process of how someone might go about changing 
the
behavior of a system-provided manifest, noting that it was important that SMF
know that it was an explicit administrator configuration so that it would be
preserved during a system upgrade.

24. http://mail.opensolaris.org/pipermail/smf-discuss/2006-March/000384.html


_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to