Hello Bill
Just to be clear, I'm asking for public access to those bugs,
but I guess someone at Sun needs to authorize this.

It's difficult to know who at Sun makes the decision on this,
and on what basis, if it is private or public.
I do not know who that would be - can you find out?

Before posting to this forum, I contacted Peter Dunlap at Sun,
who I believe is the main technical lead for the comstar iscsi target,
to ask him about this, but he could not shed any light on
why the bugs are currently private.

I've looked at all the other Comstar source code elements, with OpenGrok:

http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/io/comstar/

..and they all seem to have public access to the bugs
- see sample list below.

So it seems that it is just the bugs for the comstar iscsi target that are 'not 
available'.
I'm guessing that maybe someone just missed 'ticking a box' to make these 
public,
and it is just some oversight.

Best Regards
Nigel Smith


For example, the following are all public:

Category:Subcategory     storage_sw:stmf
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6788352
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6795089
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6809466
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6852255

Category:Subcategory     storage_sw:sbd
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6837150

Category:Subcategory     storage_sw:fct
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6764250

Category:Subcategory     storage_sw:srpt
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6775678

Category:Subcategory     storage_sw:fcoe
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6823510
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6819120
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6815792
-- 
This message posted from opensolaris.org
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to