Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010]
Mike, Thanks to you and the team for following up on this, and making the interfaces general to virtualization, rather than LDOMs specific. I believe that will lead to a better user experience. I have re-reviewed this, and offer a +1. -- Rick Mike Christensen wrote: On 01/13/10 15:55, Rick Matthews wrote: There was no meeting scheduled for Jan. 13. I believe a question was asked (and if not, I'll ask it) as to why an LDOMs specific virtualization query? Would there be a query that could give the caller generic virtualization information (working for both Zen and LDOMs)? Was this considered? Could a generic call identify the virtualization technology, and then, if needed, technology specific queries could be made? -- Rick After discussions with the Xen group, I have reworked this proposal to cater to Xen (and other virtualization technologies) implementing this. This involved mostly name changes (e.g. libldoms in the original proposal is now libv12n, function names are now v12n_* rather than ldoms_*, and manifest constants are now V12N_*) and new bit(s) in the v12n_capabilities function to return virtualization implementation technology. The case materials in the directory have been updated and attached is the new case. Thanks. Mike -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010]
are integrated into the Solaris Nevada gate and Solaris 10 Update gates. 4. Technical Description 4.1 Overview On the Solaris operating system, Logical Domains Information API will be implemented as a user library libldoms.so.1 and a user program ldminfo will be provided to display this information. This information will be provided either via the sun4v Machine Description (FWARC/2005/115 and FWARC 2009/680) or via a domain service (FWARC/2009/426) provided by the logical domains agent daemon (PSARC/2009/459) on the control domain. 4.2 Bug/RFE Number(s) 6680702 - Want a mechanism for Solaris to know if it is an LDOM and if so what type 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking 6712763 - Need information about control domain from within a guest domain 4.3 Scope Not Applicable. 4.4 Out of Scope Not Applicable. 4.5 Interfaces 4.5.1 Interfaces 4.5.2 Imported Interfaces Interface ClassificationComments = Domain Services API Consolidation PrivatePSARC/2008/568 (libds.so.1) Logical Domains Sun Private PSARC/2009/459 Agents on Solaris Logical Domains Sun Private FWARC/2009/426 Agents Machine Description Sun Private FWARC/2005/115 Device (/dev/mdesc) Domain UUID property Consolidation PrivateFWARC/2009/680 UUID library API Evolving PSARC/2002/094 (libuuid.so.1) 4.5.3 Exported Interfaces Interface Classification Comments /usr/sbin/ldminfo Committed See ldminfo(1M) /usr/lib/libldoms.so Committed 32-bit library /usr/lib/sparcv9/libldoms.so Committed 64-bit library /usr/include/libldoms.hCommitted Header file ldoms_capabilities() Committed ldoms_domain_roles() Committed ldoms_domain_name()Committed ldoms_domain_uuid()Committed ldoms_control_domain() Committed ldoms_platform_serialno() Committed LDMCAP_SUPPORTED Committed LDMCAP_ENABLED Committed LDMROLE_CONTROLCommitted LDMROLE_IO Committed LDMROLE_SERVICECommitted LDMROLE_ROOT Committed 4.6 Doc Impact Man pages for ldminfo (1M), libldoms (3LIB), ldoms_capabilities(3LDOMS), ldoms_domain_roles(3LDOMS), ldoms_domain_name(3LDOMS), ldoms_domain_uuid(3LDOMS), ldoms_control_domain(3LDOMS), ldoms_platform_serialno(3LDOMS) 4.7 Admin/Config Impact None. 4.8 HA Impact None. 4.9 I18N/L10N Not affected. 4.10 Packaging Delivery The Logical Domains Information API library libldoms and ldminfo program will be delivered as part of the existing Solaris packages SUNWcsl (Solaris 32bit libraries), SUNWcslx (Solaris 64bit libraries), SUNWcsu (Solaris User Core), SUNWhea (Solaris headers) on Sparc platforms only. 4.11 Security Impact None. 4.12 Dependencies None. 5. Reference Documents PSARC 2008/568 Logical Domain's Domain Services PSARC 2009/459 Logical Domain's Agents on Solaris FWARC 2005/115 sun4v machine description FWARC 2009/680 Domain UUID property 6. Resources and Schedule 6.1 Projected Availability Q4FY10 (S10U9) 6.2 Cost of Effort 1 person month 6.3 Cost of Capital Resources 6.4 Product Approval Committee requested information 6.4.1 Consolidation Or Component Name OS-Networking (ON) 6.4.3 Type of CPT Approval Expected FastTrack 6.4.4 Project Boundary Conditions 6.4.5 Is this a necessary project for OEM agreements: No. 6.4.6 Notes 6.4.7 Target RTI Date/Release February 2010 6.4.8 Target Code Design Review Date: 6.4.9 Update approval addition: Not applicable 6.5 ARC review type FastTrack 6.6 ARC Exposure open 7. Prototype Availability: 7.1 Prototype Availability A prototype is already available. 7.2 Prototype Cost: A prototype is already available. -- - Rick Matthews email
EOF of iSCSI Target Daemon [PSARC/2010/006 FastTrack timeout 01/13/2010]
, and an installed based that is using the iSCSI Target in COMSTAR, as a replacement for the iSCSI Target Daemon. 4. Technical Description The iSCSI Target Daemon is an inferior implementation when compared to the iSCSI Target in COMSTAR. The iSCSI Target Daemon, supports only a single SCSI Target implementation, has been noted by storage-discuss, RPE and within the Sun Storage 7000 Unified Storage Server as being underperforming, with known scalability issues when used with Solaris, and other operating systems supporting iSCSI Initiators. A point worth stating is that an iSCSI Target listens for iSCSI Initiator requests on TCP/IP port 3260. This means that two different implementations of iSCSI Target can not run at the same time, on the same Solaris host. Therefore, when iSCSI Target in COMSTAR is active on a Solaris host, ZFS's shareiscsi support no longer works, even though the iSCSI Target Daemon has yet to be removed. All of these issues and more, were eliminated with the design, development and successful release of the iSCSI Target in COMSTAR. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
sdcard conversion to bd, EOF blk2scsa [PSARC/2009/648 FastTrack timeout 12/06/2009]
+1 On 11/30/09 00:05, Garrett D'Amore - sun microsystems wrote: Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: sdcard conversion to bd, EOF blk2scsa 1.2. Name of Document Author/Supplier: Author: Garrett D'Amore 1.3 Date of This Document: 29 November, 2009 4. Technical Description Background: PSARC 2007/654 introduced blk2scsa, as a common framework for exposing block oriented devices as SCSI logical devices. PSARC 2007/659 introduced a common framework for Secure Digital devices, building upon the blk2scsa framework. PSARC 2009/646 offers a new, simpler, and more performant, alternative to blk2scsa which does not depend on SCSI or the SCSA framework at all. We would like convert the SDcard framework for SD and MMC memory cards to use the new bd framework, and EOF the blk2scsa framework at the same time. This case seeks Minor binding. It depends on PSARC 2009/646, which is not yet approved. Architectural Details: In our prototype, we have converted the framework to express a single persistent bd target, for each SDcard slot. The slot is a removable drive. This implementation has a few notable ramifications: a) We can simplify the SDcard framework quite a bit b) There is no longer a need for a separate sdcard pseudo-nexus 2009/648 (12/06/09) open sdcard conversion to bd, EOF blk2scsa driver. The bd device can appear as a direct child of the SD host driver (e.g. sdhost). The sdcard driver will be removed. c) The target device will appear using a cXdYsZ notation, without a a target number. d) Some performance ramifications from using larger transfers will go away. Specifically, we can use large transfers even using the raw device, and not have to fall back to PIO. (Because the bd framework can break the transfers up for us.) e) As we do not currently support SDIO, there is no longer any need to support the use of cfgadm with SDcard. The cfgadm plugin for SDcard can thus be removed. (Note that at this point, we find it unlikely that there will ever be sufficient motivation to implement support for SDIO. While important for certain devices such as mobile hand-sets, SDIO has no place on platforms with a fully capable USB host or Express card implementation. We have designed things in our prototype so that if SDIO support were ever necessary it could be added back in without major architectural changes to the memory card support.) This change will remove the ability to initiate a software reset of the SDcard controller from the command line, but we have found very little reason that such a capability is desirable. f) The sdcard framework itself will be able to eliminate all, or nearly all, of its direct uses of the nexus DDI. (In the event that SDIO support were added later, we would have to reintroduce a lot of NDI interface consumption, though.) As part of this effort, we'd like to remove the blk2scsa layer specified in PSARC 2007/654. There will be no more consumers for it, and the newer bd framework specified in PSARC 2009/646 is superior to it. (The blk2scsa interfaces are all Consolidation Private.) 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Provide minor private interface modifications to support mntfs [PSARC/2009/566 FastTrack timeout 10/23/2009]
This fast track was approved during ARC business today, 10/21/2009. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
ZFS send dedup [PSARC/2009/557 FastTrack timeout 10/21/2009]
+1, although it may be implied from other responses. On 10/13/09 01:25 PM, Matthew Ahrens wrote: Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: ZFS send dedup 1.2. Name of Document Author/Supplier: Author: Lori Alt 1.3 Date of This Document: 13 October, 2009 4. Technical Description This case requests micro/patch binding; new interfaces are Comitted. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
libgnomekbd re-integration [PSARC/2009/532 FastTrack timeout 10/13/2009]
On 10/06/09 14:55, Suresh Chandrasekharan wrote: Thanks Shinobu for correcting the date to 10/13/2009. Suresh Correcting the timeout date in the IAM* file would also have been useful, but not necessary. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
ettcp [PSARC/2009/508 FastTrack timeout 09/29/2009]
As documented in the man page, are suck(1), blow(1), speedto(1) and speedfrom(1) required? Or are they just mis-applied to the man page. -- Rick On 09/22/09 13:04, James Walker wrote: I'm sponsoring this familiarity case for Robin Luo. The requested release binding is minor. The man page has been posted in the materials directory. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: ettcp 1.2. Name of Document Author/Supplier: Author: Robin Luo 1.3 Date of This Document: 22 September, 2009 4. Technical Description Summary === ettcp[1] is a tool for measuring network throughput. It supports both TCP and UDP protocols and allows the tuning of various parameters, such as message buffer size, the time to run. It can transmit data from stdin. Unlike other tools which might be used for this purpose (such as FTP clients), ettcp does not read or write data from or to a disk while operating, which helps ensure more accurate results. ettcp 1.0 will be integrated into the SFW consolidation as part of this proposal, and will be installed as SUNWettcp. This project requests a minor release binding. Dependencies None Interfaces == Exported Interfaces Classification Comment --- -- -- SUNWettcp Uncommitted Package name /usr/bin/ettcpUncommitted Command Imported Interfaces Classification Comment --- -- -- None Reference Documents === [1] http://sourceforge.net/projects/ettcp/ OSR ID# 12282 RFE ID# 685293 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
Nit: The submitted man page had addR, removeR and lookupR. I'm assuming the R is a typo. Should there be a reference to the privilege required for nfsref in the man page? +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
On 09/23/09 11:08, Robert Thurlow wrote: Rick Matthews wrote: Nit: The submitted man page had addR, removeR and lookupR. I'm assuming the R is a typo. Hi Rick, Yes, that was my error in the nroff source; we'll fix it. Should there be a reference to the privilege required for nfsref in the man page? The only limitation is filesystem permissions on the symlink. Would we normally mention that? I don't think so...wasn't sure if other permissions were also needed. Thanks. Rob T -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
SATA Framework Port Multiplier Support resubmit [PSARC/2009/394 Fast-track]
+1 on the resubmitted case On 09/17/09 17:48, Alan Perry wrote: I am sponsoring the resubmission of this case. The timer expires on 9/24/2009. This fast-track was approved back in July. However, after the associated code changes were integrated into Nevada, some issues were discovered and the sata team decided to rework the case. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
PSARC/2009/253 - S10C additional materials
All, As discussed last meeting, Jerry has prepared a short note qa.txt addressing the questions as to how to detect and correct issues that may adversely affect the S10C environment. I have placed this file in the commitment.materials directory for the case. Please review. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Copy Reduction Interfaces [PSARC/2009/478 FastTrack timeout 09/16/2009]
| || Extended uio_t
definition
| ||
| ||
uioa_t | || Deprecated
UIO_ASYNC| || Deprecated
+==+
* The project's deliverables will all go into the OS/NET
Consolidation, so no contracts are required.
== Using the New VOP Interfaces for Zero-copy ==
VOP_REQZCBUF()/VOP_RETZCBUF() are expected to be used in conjunction with
VOP_READ() or VOP_WRITE() to implement zero-copy read or write.
a. Read
In a normal read, the consumer allocates the data buffer and passes it to
VOP_READ(). The provider initiates the I/O, and copies the data from its
own cache buffer to the consumer supplied buffer.
To avoid the copy (initiating a zero-copy read), the consumer first calls
VOP_REQZCBUF() to inform the provider to prepare to loan out its cache
buffer. It then calls VOP_READ(). After the call returns, the consumer
has direct access to the cache buffer loaned out by the provider. After
processing the data, the consumer calls VOP_RETZCBUF() to return the
loaned
cache buffer to the provider.
Here is an illustration using NFSv4 read over TCP:
rfs4_op_read(nfs_argop4 *argop, ...)
{
int zerocopy;
xuio_t *xuio;
...
xuio = kmem_alloc(sizeof(xuio_t), KM_SLEEP);
setup length, offset, etc;
if (VOP_REQZCBUF(vp, UIO_READ, xuio, cr, ct)) {
zerocopy = 0;
allocate the data buffer the normal way;
initialize (uio_t *)xuio;
} else {
/* xuio has been setup by the provider */
zerocopy = 1;
}
do_io(FREAD, vp, (uio_t *)xuio, 0, cr, ct);
...
if (zerocopy) {
setup callback mechanism that makes the network layer call
VOP_RETZCBUF() and free xuio after the data is sent out;
} else {
kmem_free(xuio, sizeof(xuio_t));
}
}
b. Write
In a normal write, the consumer allocates the data buffer, loads the data,
and passes the buffer to VOP_WRITE(). The provider copies the data from
the consumer supplied buffer to its own cache buffer, and starts the I/O.
To initiate a zero-copy write, the consumer first calls VOP_REQZCBUF() to
grab a cache buffer from the provider. It loads the data directly to
the loaned cache buffer, and calls VOP_WRITE(). After the call returns,
the consumer calls VOP_RETZCBUF() to return the loaned cache buffer to
the provider.
Here is an illustration using NFSv4 write via RDMA:
rfs4_op_write(nfs_argop4 *argop, ...)
{
int zerocopy;
xuio_t *xuio;
...
xuio = kmem_alloc(sizeof(xuio_t), KM_SLEEP);
setup length, offset, etc;
if (VOP_REQZCBUF(vp, UIO_WRITE, xuio, cr, ct)) {
zerocopy = 0;
allocate the data buffer the normal way;
initialize (uio_t *)xuio;
xdrrdma_read_from_client(...);
} else {
/* xuio has been setup by the provider */
zerocopy = 1;
xdrrdma_zcopy_read_from_client(..., xuio);
}
do_io(FWRITE, vp, (uio_t *)xuio, 0, cr, ct);
...
if (zerocopy) {
VOP_RETZCBUF(vp, xuio, cr, ct);
}
kmem_free(xuio, sizeof(xuio_t));
}
References:
[1] PSARC/2003/172 File Event Monitoring
[2] PSARC/2007/227 VFS Features
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
--
-
Rick Matthews email: Rick.Matthews at sun.com
Sun Microsystems, Inc. phone:+1(651) 554-1518
1270 Eagan Industrial Road phone(internal): 54418
Suite 160 fax: +1(651) 554-1540
Eagan, MN 55121-1231 USAmain: +1(651) 554-1500
-
Offline attribute [PSARC/2009/464 FastTrack timeout 09/02/2009]
On 08/31/09 09:14 AM, Dean Roehrich wrote: On Fri, Aug 28, 2009 at 12:44:39PM -0700, Alan M Wright wrote: Customers will write applications (maybe a file browser) which query this bit, and they'll file bugs against the HSM products for not setting it. And perhaps that's appropriate because this case is an action item from PSARC/2009/381 to introduce this attribute. Okay, granted, this thing is just a conduit and fsetattr() can ask the HSM, at each call, what value should be used. I'm still not understanding why the file's owner should have the ability to set this bit. What would be the purpose of that? It makes me question whether this bit has any specific meaning. I think you're distracted by this hypothetical HSM/virus scanning interaction but it's not relevant here. An HSM or file system can easily reject attempts to manipulate the offline attribute. This is a non-issue. Yes, it was a surpise to me that a non-HSM use-case was presented. Dean Dean and Alan, I've been following this case, and tend to agree with Alan. Here is why. The introduction of an externalized (user available) status to indicate that a file may not be accessible immediately is of value. I think we all agree here. Particularly since it fits into the existing framework. Where the issue under discussion is whether the architecture behind the flag is sufficient. Dean, from the HSM point of view, is viewing the flag as an HSM attribute. Alan is looking at the attribute as a generic mechanism to communicate the state to a user or users process. Dean correctly points out that the HSM needs an indisputable mechanism for tracking its state, that the user cannot muck with. Alan argues that this bit isn't for that purpose. I can rationalize how an HSM and a file system state process like virus scan could use the same flag. If either are indicating delayed availability is likely, return the flag as set. Where we could use the user process controlled visualization of the flag (some yet to be determined application), the fsetattr() can be used. I don't see (and I think this is where Dean sees incomplete architecture) how we can keep that flag persistent, if a kernel level consumer (HSM, virus scan, ...) is causing it to reflect internal (FS specific) state on each query. That is, if application X fsetattr() the state to off-line, and the file was also under HSM control, I think a query of the attribute will query the HSM portion and clear the attribute, if the file is on-line. This detail may be sketchy, but the persistence of a fsetattr() set flag may be questionable. I can live with this. -- Rick -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
VirtualBox USB Device Capture [PSARC/2009/422 08/12/2009]
+1
Jerry Gilliam wrote:
I am sponsoring this fast-track on behalf of Strony Zhang,
with a timeout set to 08/12/2009. The project desires
minor release binding.
-jg
--
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
VirtualBox USB Device Capture
1.2. Name of Document Author/Supplier:
Author: Strony.Zhang
1.3 Date of This Document:
04 Aug, 2009
4. Technical Description
Background:
The VirtualBox is a virtualization software product. When VirtualBox
runs on Solaris host OS), it should be able to proxy the USB devices
plugged in the host OS to the guest OS depending on user's
configuration. To achieve this, the VirtualBox needs to control the
entire USB device completely and ensure the USB device in the pristine
state for guest OS. No driver in host OS should be attached to the
device. Therefore, the VirtualBox team developed a Monitor driver for
capturing devices using the callback and a VirtualBox-specific USB
client driver for transferring data between guest OS and device.
Problem:
When the USB device is plugged in the Solaris system, usba (7D) will
create the compatible names and then attach the corresponding USB client
driver to it by default. During the process, the VirtualBox doesn't
have a chance to request to attach its own driver to the USB device in
which
it is interested.
Solution:
The usba(7D) provides the registration entry to VirtualBox for the
callback and makes the Virtual-specific USB client driver higher
priority than the default USB client driver. When a USB device is
plugged in the system, the usba(7D) will first call the registered
callback function to query if VirtualBox wants to capture the device.
If yes, the VirtualBox-specific USB client driver will be attached to
the device. Once the VirtualBox exits or user doesn't want to access
the USB device on guest OS, the VirtualBox will unregister the
callback and
then Solaris will take over the USB device taken by VirtualBox.
Interfaces:
The interfaces are Contracted Project Private since they are intended
to be only used by the VirtualBox.
The following new Interfaces provided by this project:
|---
| Interfaces| Class. | Comments |
|---
| struct usb_dev_str(9s)| C.P.P. | usb capture device info |
| usb_register_dev_driver(9f) | C.P.P | usb capture register|
| usb_unregister_dev_driver(9f) | C.P.P | usb capture unregister |
| usb_dev_driver_callback() | C.P.P | usb capture callback|
|---
They will be available in the sys/usb/usbai.h.
/*
* getting the device strings of manufacturer, product and serial number
*/
typedef struct usb_dev_str {
char*usb_mfg; /* manufacturer string */
char*usb_product; /* product string */
char*usb_serialno;/* serial number string */
} usb_dev_str_t;
The callback interface is:
/*
* Return Values:
* USB_SUCCESS - VirtualBox will capture the device
* USB_FAILURE - VirtualBox will not capture the device
*/
typedef int (*usb_dev_driver_callback)(
usb_dev_descr_t*dev_descr,/* ptr to device descriptor */
usb_dev_str_t*dev_str,/* ptr to device strings */
char*path,/* ptr to physical path */
intbus,/* USB bus address */
intport,/* USB port number */
char**drv,/* capture driver name */
void*reserved)
usb_dev_driver_t;
If VirtualBox wants to capture the device, the client driver name
to be attached to the device will be returned by the parameter
(char **drv).
The callback registration and unregistration interfaces are:
int usb_register_dev_driver(dev_info_t *dip, usb_dev_driver_t cb);
void usb_unregister_dev_driver(dev_info_t *dip);
The return value of usb_register_dev_driver() will be USB_SUCCESS
or USB_FAILURE which indicates that the callback registration was
successful or failed.
5. Reference Documents:
PSARC/2000/542 USB Architecture Update project
PSARC/2003/207 USBA2.0: adding USBA interfaces to the DDI
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
--
-
Rick Matthews email: Rick.Matthews at sun.com
Sun Microsystems, Inc. phone:+1(651) 554-1518
1270 Eagan Industrial Road phone(internal): 54418
Suite
PSARC 2009/253 S10C materials
Jerry, The coordinator overlooked the materials you submitted on Tuesday (tied up in CTO review). They should be posted almost immediately. Sorry for the delay, and thank you for the clarification. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
SATA Framework Port Multiplier Support [PSARC/2009/394 Self Review]
+1 On 07/14/09 07:56 PM, Alan Perry wrote: Following the recommendation of Garrett D'Amore and James Carlson, this is being promoted from Self-Review to Fast-Track. The timer expires on 21 July 2009. alan Alan Perry wrote: I am sponsoring this self-review case. This case documents additional changes to an existing case. I believe that this case qualifies for self-review because the interfaces are Consolidation Private and backwards compatible with the existing interfaces. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: SATA Framework Port Multiplier Support 1.2. Name of Document Author/Supplier: Author: Xiaoyu Zhang 1.3 Date of This Document: 14 July, 2009 4. Technical Description -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
prctl usage output [PSARC/2009/392 FastTrack timeout 07/20/2009]
+1 On 07/13/09 03:10 PM, Gerald Jelinek wrote: I'm sponsoring this fast-track for Menno Lageman. Thanks, Jerry Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: prctl usage output 1.2. Name of Document Author/Supplier: Author: Menno Lageman 1.3 Date of This Document: 13 July, 2009 4. Technical Description Summary This case proposes to enhance the output format of prctl(1M) defined by PSARC 2004/183[1] to include the current resource usage. Patch binding is requested. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
Darren, I see that this case is waiting need vote. I hadn't seen a draft opinion, and thought that I had at least asked for one. The discussion between myself and Alan seemed to clarify that this interface would only exist in Solaris 10, with a new interface using PSARC/2007/315 interface framework...in OpenSolaris and Nevada. Does that satisfy the advise which caused you to derail? Just wondering if how this case moves forward. -- Rick On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Support off-line files on SAM-QFS for Samba in Solaris[PSARC/2009/381 FastTrack timeout 07/13/2009]
To do both at the same time is an excellant idea/recommendation. -- Rick On 07/12/09 21:36, Alan.M.Wright wrote: From a practical standpoint, 2009/387 would also require a new system attribute. It would be ideal if we could add both the offline and reparse system attributes at the same time, which would be timely for this case. Alan - Original Message - From: Alan.M.Wright amw at sun.com mailto:amw at sun.com To: Richard.Matthews at Sun.COM mailto:Richard.Matthews at Sun.COM Cc: PSARC-ext at sun.com mailto:PSARC-ext at sun.com; Jiri Sasek - RPE Prague Jiri.Sasek at Sun.COM mailto:Jiri.Sasek at Sun.COM; Daniel Hain dhain at sac.sfbay.sun.com mailto:dhain at sac.sfbay.sun.com Sent: Saturday, July 11, 2009 6:52 PM Subject: Re: Support off-line files on SAM-QFS for Samba in Solaris[PSARC/2009/381 FastTrack timeout 07/13/2009] Having a TCR against Samba in order to allow this (or any) fasttrack to be approved on the basis that the fasttrack is not the right solution but resolves a customer problem seems a bit strange to me. If we agree that adding a system attribute is the appropriate solution, we should pursue that now. The fact that SAMFS would require a change to support system attributes shouldn't really have a bearing on selecting the appropriate architectural solution, and if that's a concern perhaps we can talk about that offline. Alan -- Rick Matthews wrote: Darren, I agree with Alan's proposal that the existing system extended attributes be expanded to include offline or whatever the appropriate tag could be. This would require a change to SAM-QFS to support Solaris extended attributes in at least the case of that flag (a SAM-QFS project/case, I'd guess) and modifying the interfaces introduced in PSARC/2007/315 to include the newly defined flag. This case appears to be asking to use existing interfaces of SAM-QFS to cause the Solaris provided samba to detect a condition that is causing the described customer problem, and mitigate it. The resultant FILE_ATTRIBUTE_OFFLINE within the SMB_QUERY_FILE_BASIC_INFO appears to be standard (at least in the SNIA document). I would think that advise to the PAC about modifying SAM-QFS to at least support an system extended attribute for offline, and for some unknown group to add that to the existing system extended attributes would be an appropriate response. In the mean time, I would think this case could be approved with a TCR to modify the version of Samba shipped by Sun when the architecturally appropriate interfaces (those using the existing infrastructure described in PSARC/2007/315) exist in Sun current and future HSM products. I could help add this to the general opinion, or add it as a minority opinion. == Rick On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). ___ opensolaris-arc mailing list opensolaris-arc at opensolaris.org mailto:opensolaris-arc at opensolaris.org -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
Comments in-line. On 07/11/09 20:52, Alan.M.Wright wrote: Having a TCR against Samba in order to allow this (or any) fasttrack to be approved on the basis that the fasttrack is not the right solution but resolves a customer problem seems a bit strange to me. TCR was probably an unfortunate use of the term. My intended meaning was that for Solaris 10, the existing Solaris 10 interface be used (as defined in this fast track). For OpenSolaris, the requirement should be for Samba to use to the new interface as defined by PSARC/2007/315. If we agree that adding a system attribute is the appropriate solution, we should pursue that now. The fact that SAMFS would require a change to support system attributes shouldn't really have a bearing on selecting the appropriate architectural solution, and if that's a concern perhaps we can talk about that offline. Yes, we should pursue it now in OpenSolaris. I don't think it would be wise to require the project team to implement (or coordinate implementation) of system attributes, the required SAM-QFS change and the Samba change in a Solaris 10 release. Alan -- Rick Matthews wrote: Darren, I agree with Alan's proposal that the existing system extended attributes be expanded to include offline or whatever the appropriate tag could be. This would require a change to SAM-QFS to support Solaris extended attributes in at least the case of that flag (a SAM-QFS project/case, I'd guess) and modifying the interfaces introduced in PSARC/2007/315 to include the newly defined flag. This case appears to be asking to use existing interfaces of SAM-QFS to cause the Solaris provided samba to detect a condition that is causing the described customer problem, and mitigate it. The resultant FILE_ATTRIBUTE_OFFLINE within the SMB_QUERY_FILE_BASIC_INFO appears to be standard (at least in the SNIA document). I would think that advise to the PAC about modifying SAM-QFS to at least support an system extended attribute for offline, and for some unknown group to add that to the existing system extended attributes would be an appropriate response. In the mean time, I would think this case could be approved with a TCR to modify the version of Samba shipped by Sun when the architecturally appropriate interfaces (those using the existing infrastructure described in PSARC/2007/315) exist in Sun current and future HSM products. I could help add this to the general opinion, or add it as a minority opinion. == Rick On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
Darren, I agree with Alan's proposal that the existing system extended attributes be expanded to include offline or whatever the appropriate tag could be. This would require a change to SAM-QFS to support Solaris extended attributes in at least the case of that flag (a SAM-QFS project/case, I'd guess) and modifying the interfaces introduced in PSARC/2007/315 to include the newly defined flag. This case appears to be asking to use existing interfaces of SAM-QFS to cause the Solaris provided samba to detect a condition that is causing the described customer problem, and mitigate it. The resultant FILE_ATTRIBUTE_OFFLINE within the SMB_QUERY_FILE_BASIC_INFO appears to be standard (at least in the SNIA document). I would think that advise to the PAC about modifying SAM-QFS to at least support an system extended attribute for offline, and for some unknown group to add that to the existing system extended attributes would be an appropriate response. In the mean time, I would think this case could be approved with a TCR to modify the version of Samba shipped by Sun when the architecturally appropriate interfaces (those using the existing infrastructure described in PSARC/2007/315) exist in Sun current and future HSM products. I could help add this to the general opinion, or add it as a minority opinion. == Rick On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). I'd, for one, like to see the draft opinion. I have some opinions about these approaches which I will document tomorrow. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
VSD locking update [PSARC/2009/343 FastTrack timeout 06/12/2009]
I've read through this, and see no issue... +1 On 06/05/09 16:07, Rich.Brown at Sun.COM wrote: I'm sponsoring the following fast-track for Bob Mastors. This case is an update to PSARC 2007/456 Vnode Specific Data and adds a new field to the vnode structure (in sys/vnode.h): v_vsd_lock. The case seeks Minor binding which matches the binding of the original case. The timer expires on June 12, 2009. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: VSD locking update 1.2. Name of Document Author/Supplier: Author: Bob Mastors 1.3 Date of This Document: 05 June, 2009 4. Technical Description PSARC 2007/456 Vnode Specific Data was created to easily associate project specific data with a vnode. The current implementation requires consumers of vsd_get() and vsd_set() to hold the vnode v_lock mutex across the calls. However, vsd_set() may go to sleep on kmem_alloc(). This could cause the system to deadlock if the vnode had dirty pages that needed to be written. This problem is described by: 6839233 VSD usage of v_lock could cause deadlock The solution adds a new mutex to vnode_t: kmutex_tv_vsd_lock;/* protects v_vsd field */ Consumers of vsd_get() and vsd_set() would hold v_vsd_lock across the calls instead of v_lock. There are no lock ordering issues since the locks are independent and there is no reason to hold both simultaneously. Currently, the only ON consumer of vsd_get() and vsd_set() is NFS. Exported Interfaces Interface Name | Classification | Comments = || v_vsd_lock | Consolidation | New mutex in the vnode structure | Private| to protect v_vsd field 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jar file man pages - was Re: trove-2.0.4 [LSARC/2009/262 FastTrack timeout 05/05/2009]
I agree in principle with Jim's points. In particular, 1. Provides users stability and availability (taxonomy) information about jar file packages on Solaris/OpenSolaris not available anywhere else. If ARCs are going to require this information, it should be documented somewhere that a user can find it a normal operating environment. Currently, I'd have to agree this is man pages. I think a further point of this discussion is a need for ARCs to adopt a consistent means of doing so, and stick to it. In several of the cited cases with man pages, the man pages were produced as part of the Fast Track process. In the case of LSARC/2009/262, it was questioned why we would have man pages for jar/java release vehicles. That is inconsistent, which is why I believe Jim raised the issue. Toward that end, issues continue to be raised with jar/java FOSS projects. There doesn't seem to be a checklist of items needed for a FOSS jar project (and of course, many checklists are incomplete). As I recall, the following issues resulted from FOSS cases delivering jar s: 1) How to deliver javadocs to OpenSolaris (mostly due to web site volume issues) 2) Man pages for stability and taxonomy 3) What portions need to have declared stability, etc. (like package name) 4) What JDK version(s)? 5) Versioning of jar files Mark Martin brought up number 5 quite awhile ago. There was no further action taken. The jar files really seem to parallel C libraries, and should have a best practice for versioning similar to (or maybe expanded) Library and Shared Object Requirements. IMHO, man page declaration of stability and taxonomy works. Let's keep that until there is a suitable better way. Lloyd's method of documenting is a good start, but we can't hope to force external communities to use such a method, except by general acceptance. We could make it a best practice for non-FOSS jar deliverables that are being ARCed. This assumes Lloyd's proposal is sound, which I don't feel qualified to have opinion. I think the ARCs need to look into these issues (as is being done), and reasonable methods/ practices be established, and then those be consistently applied. -- Rick On 05/13/09 13:30, Jim Walker wrote: For LSARC, PSARC and the opinion writer(s) to consider Michael Kearney wrote: 1. Lloyd, I like the idea of your annotation but have a couple of concerns. - Would teams be expected to update third party, open source jar files with the annotation? - Would the ARC provide the common @Taxonomy annotation Java code? I have concerns too. In general, we will not be able to change FOSS code upstream like this. We normally try to do as little modification as possible (ie. just enough to get it to run well on Solaris/OpenSolaris). This is another reason why short man pages are being tacked on. Is it possible to tack on a page to the javadoc? I don't want to see big javadoc patches in the SFW consolidation that document detailed taxonomy information that we have to carry forever because they will never be accepted into the upstream community. Why would a FOSS project creating jar files even care about our taxonomy rules? 2. What if the man page simple documented the stability at the granularity of the jar file and nothing else. Perhaps the man page could generically reference the Javadoc? Not every jar file in /usr/share/lib/java has a man page, but that is the current practice, for the ones that do: $ man asm $ man mvel $ man janino $ man jettison $ man joda-time $ man jaxen-core $ man junit $ man ant (needs a more direct reference to javadoc) ... As I see it, having jar file man pages... 1. Provides users stability and availability (taxonomy) information about jar file packages on Solaris/OpenSolaris not available anywhere else. 2. Is pretty painless for project teams to produce and support. 3. Man pages do no harm, and I think users are already getting use to having them. Some information is better than no information. 4. Until there is a better way, man pages should be required for any new jar file submissions into Solaris/OpenSolaris. I thought this was already true. 5. Man pages are used by most Solaris/OpenSolaris packages. 6. I appreciate where Java developers are coming from, but not standard practice for Java developers to look for man pages alone, doesn't seem enough reason to stop man pages being delivered with jar file packages. We can't control how jar files are delivered or documented on windows or other environments, but we can on Solaris/OpenSolaris. BTW. ccing Norm (sfw c-team lead) since one of the requirements to integrate into sfw is a man page. Cheers, Jim -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone
zfs snapshot holds [PSARC/2009/297 FastTrack timeout 05/20/2009]
+1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
vdiskadm convert [PSARC/2009/214 FastTrack timeout 04/08/2009]
+1 On 04/01/09 23:38, Tim Marsland wrote: Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: vdiskadm convert 1.2. Name of Document Author/Supplier: Author: Susan Kamm-Worrell 1.3 Date of This Document: 01 April, 2009 4. Technical Description Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: vdiskadm convert 1.2. Name of Document Author/Supplier: Author: Susan Kamm-Worrell 1.3 Date of This Document: 1 April, 2009 4. Technical Description 4.1. Summary This fast-track introduces four new commands to vdiskadm, an administrative tool to manage virtual disks. It also introduces a new virtual disk type, vhd, which is the native Microsoft virtual disk format. Minor release binding is requested. The materials directory contains the updated manpage. 4.2. Discussion The vdiskadm import and export commands listed in the fast-track PSARC/2008/597 are now being allowed for general use. The vdiskadm convert and translate commands are new. Virtual appliances consist of configuration and disk data files. To use disk data files they need to be imported to a virtual disk understood by xvm. Also, block devices used as virtual disks can have their data imported into a virtual disk allowing the disk data to be saved or moved to another system. Conversely, a virtual disk created by xvm may need to be exported in order to be used by Virtual Box or other virtualization technologies. Virtual disk data can also be exported to a block device that can be used as the disk for a guest domain. Both import and export commands can convert the disk data to a different virtual disk type during their execution. The vdiskadm convert command allows the user to convert an existing virtual disk to a different type. This is especially helpful in comparison of virtual disk type performance where different virtual disk types containing the same data can be compared. The translate command is a conversion of a disk data file from one virtual disk type to another without creating an actual vdisk. This allows the user to translate disk data from a virtual appliance directly to a zvol or other block device. This may also be useful for converting disk data from a block device directly to a data file for use with Virtual Box. Listed are the new vdiskadm commands: import Imports a file or block device data into a virtual disk export Exports a virtual disk data into a file or block device. convert Converts a virtual disk to a different type translate Translates data from a file or block device to another of a different type 4.3. Interfaces vdiskadm command is Uncommitted. 5. References: PSARC/2006/260 Solaris on Xen PSARC/2008/597 vdiskadm 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
call for email vote: 2008/772 Command Assistant
I'm voting to approve On 03/19/09 02:03 PM, James Carlson wrote: The project team has placed updated materials in the 'post-inception.materials' directory. The new materials reflect the change of direction (to implement an applet). From looking at them, it appears that we've gotten all that we need, so I'm calling for the vote by email. Members: please let me know if you're not ready to vote. Otherwise, please reply with your vote. I'm voting approve. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
PSARC 2008/769 - Multiple disk sector size support
Larry Liu wrote: Hi Rick, Thanks for your suggestion. We made the changes accordingly. That said, by default, sd(7D) will do RMW to misaligned I/O with warning message. Custormers can configure the behavior as do RMW without warning message and do not do RMW with error returned. The configuration will be per device based (PSARC 2008/465 [s]sd-config-list). We don't have a mechanism to configure the behavior per partition based. I attached the modified rmw design doc. Thanks, Larry I am happier with the proposed changes. Thank you -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jarjar [LSARC/2009/078 FastTrack timeout 02/18/2009]
This case has converged in discussion, received its +1, and belatedly is being marked closed approved. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
JDOM [LSARC/2009/127 FastTrack timeout 03/03/2009]
With corrected documentation, requisite +1, discussion closed and timer expired, I am marking this case closed approved. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
ZFS dataset property to support SMB [PSARC/2009/140 FastTrack timeout 03/05/2009]
Guess I did this improperly +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]
Backing up the verbal +1 Jim Walker wrote: Rick Matthews wrote: Are we supporting a particular version of clisp? The community appears to be very active. The project team will be delivering the current clisp version 2.47. I'll update the checklist. Cheers, Jim -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Shawn, Correct me if I'm wrong, but I think you were going to do an umbrella clarifying this case. Wyllys, I think this should be in waiting needs spec until then. Thanks -- On 02/04/09 12:16, Rick Matthews wrote: Shawn, I think there continues to be lack of understanding on this fast-track. Your suggestion of an umbrella case is a good one. I'd like to de-rail this case until that umbrella has occurred. -- Rick -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]
://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [*] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [ ] Yes [*] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [*] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [*] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface NameClassification Comments --- --- --- SUNWclisp Uncommitted Package /usr/bin/clispUncommitted Command /usr/lib/clisp/ Uncommitted Object Files /usr/share/clisp/ Uncommitted Emacs and Vim lisp support 4.2 Imported Interfaces Interface NameClassification Comments --- -- readline (via SFW)CommittedPSARC/2007/188 libsigsegvUncommitted LSARC/2009/107 Appendix A - References 1. http://clisp.cons.org/ OSR ID# 10665 RFE ID# 6777585 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/126 - xom
Per last weeks meeting, I have modified the case materials as follows: -) Added the package name to the exported interfaces. -) Added the jar file to the exported interfaces. -) Deleted the interface table from the FOSS checklist, and referred to the proposal.txt -) Gathered the FastTrack submission, FOSS checklist and man page into a file called Proposal.txt (in the materials directory). Please inform myself or Vivek if this is less than required. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/127 - JDOM
Per last weeks meeting, I have modified the case materials as follows: -) Added the package name to the exported interfaces. -) Added the jar file to the exported interfaces. -) Deleted the interface table from the FOSS checklist, and referred to the proposal.txt -) Gathered the FastTrack submission, FOSS checklist and man page into a file called Proposal.txt (in the materials directory). Please inform myself or Vivek if this is less than required. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/128 - log4j
Per last weeks meeting, I have modified the case materials as follows: -) Added the package name to the exported interfaces. -) Added the jar file to the exported interfaces. -) Deleted the interface table from the FOSS checklist, and referred to the proposal.txt -) Gathered the FastTrack submission, FOSS checklist and man page into a file called Proposal.txt (in the materials directory). Please inform myself or Vivek if this is less than required. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
cglib-nodep [LSARC/2009/132 FastTrack timeout 03/03/2008]
+1 On 02/24/09 16:05, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jexcelapi [LSARC/2009/131 FastTrack timeout 03/03/2009]
+1 ... minor nit...the .jar file is listed at the top of the interface table, where in your other cases (132, 133, 134, 135) it is listed as an interface. -- Rick On 02/24/09 11:53, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
cglib-nodep [LSARC/2009/132 FastTrack timeout 03/03/2008]
+1 -- Rick On 02/24/09 16:05, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
pullparser [LSARC/2009/133 FastTrack timeout 03/03/2009]
+1, also -- Rick On 02/24/09 17:08, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
dom4j [LSARC/2009/134 FastTrack timeout 03/03/2009]
+1 -- Rick On 02/24/09 17:21, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
xstream [LSARC/2009/135 FastTrack timeout 03/03/2009]
+1 -- Rick On 02/24/09 17:37, Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
log4j [LSARC/2009/128 FastTrack timeout 03/03/2009]
Resending due to FFF (fat finger fault) On 02/22/09 04:56 PM, Richard Jr Matthews wrote: I am sponsoring this fast-track for Vivek Titarmare. The timeout is set at March 3. The case directory contains the supplied materials. This fast-track is a portion of the Drools case LSARC 2008/748, which is a dependency of ADM - PSARC 2007/210. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Log4J 1.2. Name of Document Author/Supplier: Author: Vivek R. Titarmare 1.3 Date of This Document: 22 January, 2009 2. Project Summary 2.1 Project Description Apache log4j is a Java-based logging utility. 4. Technical Description: The architecture of the log4j API is layered. Each layer consists of different objects performing different tasks. The top layer captures the logging information, the middle layer is involved in analyzing and authorizing the logging information, and the bottom layer is responsible for formatting and publishing the logging information to a destination. In essence, log4j consists of three types of primary objects: Logger: The Logger object (formerly known as the Category object in releases prior to log4j 1.2) is responsible for capturing logging information. Logger objects are stored in a namespace hierarchy. Appender: The Appender object is responsible for publishing logging information to various preferred destinations. Each Appender object will have at least one target destination attached to it. For example, a ConsoleAppender object is capable of printing logging information to a console. Layout: The Layout object is used to format logging information in different styles. Appender objects utilize Layout objects before publishing logging information. Layout objects play an important role in publishing logging information in a way that is human readable and reusable. 5. Interfaces Exported interface Classification Interface type === == org.apache.log4j * Appender Uncommitted Interface org.apache.log4j.config * PropertyGetter.PropertyCallback Uncommitted Interface org.apache.log4j.lf5 * LogRecordFilter Uncommitted Interface org.apache.log4j.or * ObjectRendererUncommitted Interface org.apache.log4j.spi * AppenderAttachableUncommitted Interface * Configurator Uncommitted Interface * ErrorCode Uncommitted Interface * ErrorHandler Uncommitted Interface * HierarchyEventListenerUncommitted Interface * LoggerFactory Uncommitted Interface * LoggerRepository Uncommitted Interface * OptionHandler Uncommitted Interface * RendererSupport Uncommitted Interface * RepositorySelectorUncommitted Interface * TriggeringEventEvaluator Uncommitted Interface org.apache.log4j.xml * UnrecognizedElementHandlerUncommitted Interface Imported interfaceClassification Comments === == === Interfaces are imported from javax-mail.jar javax-jms.jar The Jar file would go in usr/share/lib/java 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA
stringtemplate [LSARC/2009/077 FastTrack timeout 02/18/2009]
I have updated the FOS checklist and the Fast-track documantation in the case materials directory to reflect an update to include imported interfaces from previously submitted cases. I have extended the time until Feb 24. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jarjar [LSARC/2009/078 FastTrack timeout 02/18/2009]
I have updated the FOS checklist and the Fast-track documantation in the case materials directory to reflect an update to include imported interfaces from previously submitted cases. I have extended the time until Feb 24. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
antlr runtime [LSARC/2009/075 FastTrack timeout 02/18/2009]]
Having received its +1 and discussion quieted, I've marked this case closed approved. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
joda_time [LSARC/2009/079 FastTrack timeout 02/18/2009]
Having received its +1 and discussion quieted, I've marked this case closed approved. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jettison [LSARC/2009/094 FastTrack timeout 02/18/2009]
Minor nit: jettison spelled as jittison on one place in the FOSS checklist. +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
+1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
JDT Core [LSARC/2009/095 FastTrack timeout 02/18/2009]
+1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
mvel [LSARC/2009/096 FastTrack timeout 02/18/2009]
+1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
libgrubmgmt - library for GRUB menu management [PSARC/2009/092 02/18/2009]
In your examples (4.1.2), you cite: init 6 fast reboot with bootargs from the default GRUB menu entry Would init 6 3, select the 3rd set of bootargs? Does the nth entry in the Grub menu correspond to that in the bootadm list-menu command? -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
More HCA Capabilities [PSARC/2009/060 FastTrack timeout 02/05/2009]
+1 If looked over the materials, and the proposal seems reasonable. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
PSARC 2009/069 802.1Q tag mode link property
A nit question: Is there the means to determine a dropped packet occurred due to the user priority tag, and automatically setting the tagmode to vlanonly? -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/079 - joda-time
I have posted updated man page materials and moved project materials into a materials directory. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/077 - stringtemplate
I have moved the case materials to a materials directory. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/078 - jarjar
I have moved the case materials to a materials directory. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/046 - xsdlib
I have added the proposed man page to the case directory. I am also attaching that page for reference. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An embedded and charset-unspecified text was scrubbed... Name: xsdlib.3m URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090205/6e1117c0/attachment.ksh
More HCA Capabilities [PSARC/2009/060 FastTrack timeout 02/05/2009]
Due to no +1, and no ARC business this week, I'd like to have the timer extended until Feb. 11. -- Rick On 01/29/09 17:56, Ted Kim wrote: Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: More HCA Capabilities 1.2. Name of Document Author/Supplier: Author: Bill Taylor 1.3 Date of This Document: 29 January, 2009 4. Technical Description More HCA Capabilities - -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Shawn, I think there continues to be lack of understanding on this fast-track. Your suggestion of an umbrella case is a good one. I'd like to de-rail this case until that umbrella has occurred. -- Rick On 02/02/09 03:17, Shawn M Emery wrote: Response to questions in-line: Gary Winiger wrote: 4. Technical Description I must say having read through this case, it is non-obvious to me what is being proposed and how it solves the problem of delayed Besides the internal and external presentations I have given on the overall project, perhaps I should file an umbrella PSARC case that outlines the three projects together and how they interact? execution. Perhaps I missed it, what's the relationship between gssd and ccd? For Kerberos, gssd is a client of ccd, just like any other application obtaining service tickets. Is there a persistent (i.e., across reboot) credential cache such that delayed execution jobs will run on a freshly booted system? No, this is part of the future project of getting initial credentials (gic) through keytab PAM module project. To me the works per session mean beween the time of authentication to the exit of that process group. Is there a different definition for this case? No, this case is specific to delayed execution, which uses its own session identifier for processes such as cron/at or anything else that uses the gic through keytab module. This would have a fall-back mechanism to FILE ccaches, if CCAPI failed. How does this all relate to a per-user ccd? See above. On a SRSS server with 100s of users, will there be 100s of ccd/gssd-s? As described in the one-pager, the plan is not to make the CCAPI the default credential cache as to minimize impact in environments such as this. When and how is the per-user cache destroyed? kdestroy(1) or after x minutes of inactivity, afterall initialization of credentials is dynamic with cron, as the PAM module would perform a gic w/keytab during cron's setcred pass. This has an advantage of not having to change applications. With the new module, you could also gic keytab at intervals by creating a simple application. Shawn. -- -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090204/7c7d0ef2/attachment.html
More HCA Capabilities [PSARC/2009/060 FastTrack timeout 02/05/2009]
Yes I will...just didn't have time as of yet. On 02/04/09 12:52, Ted H. Kim wrote: I am okay with extending the timer, but I hope that means at least *you* will volunteer to read and review it? :-) -ted Rick Matthews wrote: Due to no +1, and no ARC business this week, I'd like to have the timer extended until Feb. 11. -- Rick On 01/29/09 17:56, Ted Kim wrote: Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: More HCA Capabilities 1.2. Name of Document Author/Supplier: Author: Bill Taylor 1.3 Date of This Document: 29 January, 2009 4. Technical Description More HCA Capabilities - -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/046 - xsdlib
This fast track has timed out, with no outstanding discussion. I am marking closed approved fast-track. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/047 Janino
This fast track has timed out, with no outstanding discussion. I am marking closed approved fast-track. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/048 - Jaxen
This fast track has timed out, with no outstanding discussion. I am marking closed approved fast-track. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC 2009/049 ANTLR - Another Tool for Language Recognition
This fast track has timed out, with no outstanding discussion. I am marking closed approved fast-track. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
xpp3_min Ver 1.1.4c [LSARC/2009/053 FastTrack timeout 02/04/2009]
Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 02/04/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist and javadoc are in the case directory. -- mark Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: xpp3_min Ver 1.1.4c 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 28 January, 2009 2. Project Summary 2.1 Project Description xpp3_min is a stable XmlPull parsing engine that is based on ideas from XPP and in particular XPP2 4. Technical Description: xpp3_min is a stable XmlPull parsing engine that is based on ideas from XPP and in particular XPP2 5. Interfaces Exported interface Classification Interface type === == org.xmlpull.v1 * XmlPullParser Uncommitted Interface * XmlSerializer Uncommitted Interface The Jar file would go in usr/share/lib/java Imported interfaceClassification Comments === == === None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
[Fwd: Re: asm Ver 3.1 [LSARC/2009/052 FastTrack timeout 02/04/2009]]
Oops (again)... +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An embedded message was scrubbed... From: Rick Matthews richard.matth...@sun.com Subject: Re: asm Ver 3.1 [LSARC/2009/052 FastTrack timeout 02/04/2009] Date: Fri, 30 Jan 2009 08:19:56 -0600 Size: 4525 URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090130/3dbd22e3/attachment.nws
stax-api Ver 1.0.1 [LSARC/2009/055 FastTrack timeout 02/04/2009]
Mark Carlson wrote: I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 02/04/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist and javadoc are in the case directory. -- mark Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: stax-api Ver 1.0.1 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 28 January, 2009 2. Project Summary 2.1 Project Description The StAX API exposes methods for iterative, event-based processing of XML documents. 4. Technical Description: This API specifies a bi-directional API for reading and writing XML. The Streaming API for XML is designed to serve two basic uses. The first allows users to read and write XML as efficiently as possible (cursor API). The second is designed to be easy to use, event based, easy to extend, and allow easy pipelining (iterator API). The iterator API is intended to layer ontop of the cursor API. The cursor API has two interfaces: XMLStreamReader and XMLStreamWriter. The iterator API has two main interfaces: XMLEventReader and XMLEventWriter. A factory is used to instantiate instances of the interfaces. 5. Interfaces Exported interface Classification Interface type === == javax.xml.namespace * NamespaceContext Uncommitted Interface packagejavax.xml.stream * EventFilter Uncommitted Interface * Location Uncommitted Interface * StreamFilter Uncommitted Interface * XMLEventReaderUncommitted Interface * XMLEventWriterUncommitted Interface * XMLReporter Uncommitted Interface * XMLResolver Uncommitted Interface * XMLStreamConstantsUncommitted Interface * XMLStreamReader Uncommitted Interface * XMLStreamWriter Uncommitted Interface packagejavax.xml.stream.events * Attribute Uncommitted Interface * CharactersUncommitted Interface * Comment Uncommitted Interface * DTD Uncommitted Interface * EndDocument Uncommitted Interface * EndElementUncommitted Interface * EntityDeclaration Uncommitted Interface * EntityReference Uncommitted Interface * Namespace Uncommitted Interface * NotationDeclaration Uncommitted Interface * ProcessingInstruction Uncommitted Interface * StartDocument Uncommitted Interface * StartElement Uncommitted Interface * XMLEvent Uncommitted Interface packagejavax.xml.stream.util * XMLEventAllocator Uncommitted Interface * XMLEventConsumer Uncommitted Interface The Jar file would go in usr/share/lib/java Imported interfaceClassification Comments === == === None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
[Fwd: xsdlib - Sun Java SML routines [LSARC/2009/046 FastTrack timeout 02/03/2009]]
I am sponsoring this Fast Track for Vivek Titarmare. The time out is set at 02/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist is in the case directory. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: xsdlib - Sun Java SML routines 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 27 January, 2009 4. Technical Description Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: xsdlib 1.2. Name of Document Author/Supplier: Author: Vivek R. Titarmare 1.3 Date of This Document: 22 January, 2009 2. Project Summary 2.1 Project Description Sun XML Datatypes Library 4. Technical Description: Sun XML Datatypes Library 5. Interfaces Exported interface Classification Interface type === == com.sun.msv.datatype * DatabindableDatatype Uncommitted Interface * SerializationContext Uncommitted Interface com.sun.msv.datatype.xsd * ComparatorUncommitted Interface * XSDatatypeUncommitted Interface com.sun.msv.datatype.xsd.datetime * IDateTimeValueTypeUncommitted Interface * ITimeDurationValueTypeUncommitted Interface com.sun.msv.datatype.xsd.regex * RegExpUncommitted Interface Imported interfaceClassification Comments === == === None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/047 FastTrack timeout 02/03/2009
I am sponsoring this Fast Track for Vivek Titarmare. The time out is set at 02/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist is in the case directory. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Janino 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 27 January, 2009 4. Technical Description Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: janino 1.2. Name of Document Author/Supplier: Author: Vivek R. Titarmare 1.3 Date of This Document: 22 January, 2009 2. Project Summary 2.1 Project Description Janino is a compiler that reads a JavaTM expression, block, class body, source file or a set of source files, and generates JavaTM bytecode that is loaded and executed directly. 4. Technical Description: Janino is a compiler that reads a JavaTM expression, block, class body, source file or a set of source files, and generates JavaTM bytecode that is loaded and executed directly. 5. Interfaces Exported interface Classification Interface type === == org.codhaus.janino * AstCompilationUnitGenerator Uncommitted Interface * CodeContext.FixUp Uncommitted Interface * IClass.IMemberUncommitted Interface * Java.ArrayInitializerOrRvalue Uncommitted Interface * Java.BlockStatement Uncommitted Interface * Java.DocCommentable Uncommitted Interface * Java.LocatableUncommitted Interface * Java.MemberTypeDeclarationUncommitted Interface * Java.NamedTypeDeclaration Uncommitted Interface * Java.PackageMemberTypeDeclaration Uncommitted Interface * Java.ScopeUncommitted Interface * Java.TypeBodyDeclaration Uncommitted Interface * Java.TypeDeclaration Uncommitted Interface * JavaSourceClassLoader.ProtectionDomainFactory Uncommitted Interface * UnitCompiler.ErrorHandler Uncommitted Interface * Visitor.AtomVisitor Uncommitted Interface * Visitor.BlockStatementVisitor Uncommitted Interface * Visitor.ComprehensiveVisitor Uncommitted Interface * Visitor.ImportVisitor Uncommitted Interface * Visitor.LvalueVisitor Uncommitted Interface * Visitor.RvalueVisitor Uncommitted Interface * Visitor.TypeBodyDeclarationVisitorUncommitted Interface * Visitor.TypeDeclarationVisitorUncommitted Interface * Visitor.TypeVisitor Uncommitted Interface * WarningHandlerUncommitted Interface org.codhaus.janino.tools * JGrep.MethodInvocationAction Uncommitted Interface * JGrep.MethodInvocationPredicate Uncommitted Interface org.codhaus.janino.util * Benchmark.ReporterUncommitted Interface * Producer Uncommitted Interface Imported interfaceClassification Comments === == === None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/048 FastTrack timeout 02/03/2009
I am sponsoring this Fast Track for Vivek Titarmare. The time out is set at 02/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist is in the case directory. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Jaxen 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 27 January, 2009 4. Technical Description Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: jaxen-core 1.2. Name of Document Author/Supplier: Author: Vivek R. Titarmare 1.3 Date of This Document: 22 January, 2009 2. Project Summary 2.1 Project Description Jaxen is an open source XPath library written in Java. 4. Technical Description: Jaxen is an open source XPath library written in Java. 5. Interfaces Exported interface Classification Interface type === == org.jaxen * Function Uncommitted Interface * FunctionContext Uncommitted Interface * NamedAccessNavigator Uncommitted Interface * NamespaceContext Uncommitted Interface * Navigator Uncommitted Interface * VariableContext Uncommitted Interface * XPath Uncommitted Interface org.jaxen.expr * AdditiveExpr Uncommitted Interface * AllNodeStep Uncommitted Interface * BinaryExprUncommitted Interface * CommentNodeStep Uncommitted Interface * EqualityExpr Uncommitted Interface * Expr Uncommitted Interface * FilterExprUncommitted Interface * FunctionCallExpr Uncommitted Interface * LiteralExpr Uncommitted Interface * LocationPath Uncommitted Interface * LogicalExpr Uncommitted Interface * MultiplicativeExprUncommitted Interface * NameStep Uncommitted Interface * NumberExprUncommitted Interface * PathExpr Uncommitted Interface * Predicate Uncommitted Interface * PredicatedUncommitted Interface * ProcessingInstructionNodeStep Uncommitted Interface * RelationalExprUncommitted Interface * Step Uncommitted Interface * TextNodeStep Uncommitted Interface * UnaryExpr Uncommitted Interface * UnionExpr Uncommitted Interface * VariableReferenceExpr Uncommitted Interface * XPathExpr Uncommitted Interface * XPathFactory Uncommitted Interface org.jaxen.saxpath * Operator Uncommitted Interface * SAXPathEventSourceUncommitted Interface * XPathHandler Uncommitted Interface * XPathReader Uncommitted Interface Imported interfaceClassification Comments === == === None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
ANTLR - Another Tool for Language Recognition [LSARC/2009/049 FastTrack timeout 02/03/2009
-- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
SAS Management Protocol library [PSARC/2009/019 FastTrack timeout 01/27/2009]
On 01/21/09 02:17 PM, cindi wrote: This case seeks micro binding. This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: SAS Management Protocol library 1.2. Name of Document Author/Supplier: Author: Keith Wesolowski 1.3 Date of This Document: 13 January, 2009 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open In reviewing this case, I was wondering if there is any conflict between it and PSARC 2008/687. It looks like there should be none (I spoke to the owner of the other fast track), but does this project team concur? If so, +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Virtual Keyboard Input Method [PSARC/2009/041 FastTrack timeout 01/28/2009]
Project Private $HOME/.iiim/vkb/* Project Private Customized data RELEASE BINDING The project team asks for Micro/Patch release binding. REFERENCES [1] PSARC 2007/028 EMEA input methods with keyboard layout emulation [2] PSARC 2005/525 IIIMF upgrade to revision 12 [3] Internet/Intranet Input Method Architecture: http://www.openi18n.org/subgroups/im/iiimf/whitepaper/whitepaper.html The same HTML file will be available at the case directory: http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/iiimf-whitepaper.html [4] Internet-Intranet Input Method Protocol (IIIMP) specification: http://www.openi18n.org/subgroups/im/iiimf/protocol/spec.html The same HTML file will be available at the case directory: http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/iiimp-spec.html [5] ASARC 1999/276 /usr/lib/im directory for platform independent Input Method Systems [6] ASARC 1998/515 Multi Script Input Support in UTF-8 locales [7] ASARC 1998/422 IIIMP - Internet/Intranet Input Method Protocol [8] ASARC 1997/359 Multilingual Input Method Server for X/Java/Corba [9] iiim-keyboard(1) man page: http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/iiim-keyboard.1 [10] High-level Virtual Keyboard UI/Module design (v0.2): http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/VKB_design_02.pdf [11] Draft keyboard window screen snapshots: http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/Keyboard.png http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/Input-mode-context-menu.png http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/Edit-mode-context-menu.png [12] Draft control panel window screen dump: http://www.opensolaris.org/os/community/arc/caselog/2009/041/materials/ControlPanel.png 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: G11N 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open A couple of minor nits in VKB_design02.pdf On page 3, first sentence after the Virtual Keyboard header: the the On page 4, right before the diagram: copy/past - copy/paste? Otherwise, +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
FCoE (Fibre Channel over Ethernet) Initiator [PSARC/2008/311 FastTrack timeout 12/19/2008]
The specifications (fcoe_initiator_func_spec_v100.pdf section 1, for example) note that only networks meeting a criteria list are capable of FCoe. Is there any observability as to whether a network is capable? Or indication of what is missing? Provided by this project or outside of this project? Otherwise +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008]
I agree with Rich on the avoidance of an undocumented parameter, unless absolutely necessary. +1 Rich Brown wrote: On 12/12/08 06:23, Pavel Filipensky wrote: Hi Brian, On 12/12/08 11:19, Brian Ruthven - Sun UK wrote: Is it ever likely to be useful to do umountall -Z zonename ? # zlogin zonename umountall is a way to do that Perhaps to help release resources from a single zone, rather than having to umountall across all zones simultaneously? [ My thinking behind this is the recent change to lpstat where the -l flag suddenly started taking an additional parameter, and that broke all sorts of customer scripts which were used to the lpstat -lp command. I'd like to avoid a future incompatibility, but it depends on the expected target audience of this flag... ] Does this additional flag need to be added to the man page at all? Could it simply be a private flag? Is the -Z flag ever expected to be run by the average sysadmin on the command-line, or would it be confined to the zones stop method? -Z option might be interesting for experienced admins and for developers - how they should get to know about the existence of that flag? -Z is proposed to be mentioned in 'Usage' as well: # umountall -? Usage: umountall [-k] [-s] [-F FSType] [-l|-r] [-Z] [-n] umountall [-k] [-s] [-h host] [-Z] [-n] Thanks, Pavel As long as the change to the default behaviour is noted (and frankly I would have expected umountall to operate in the current zone only anyway), and if the only place it is likely to be used is the zones stop method, I imagine the -Z could be an undocumented flag (cf. savecore -m, only used in the bootup sequence). Thanks, Brian In my opinion, adminstrative utilities with a system-wide effect, such as umountall(1M), should have all of their options documented. An administrator may have a use for it or may simply want to know what s/he just accidently did (oops!). I don't see an advantage to make this option private. Unless there's a compelling reason to keep this private, then let's let the proposal stand as a publicly documented option. Rich -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Cluster Brand Zone Interfaces [PSARC/2008/747 FastTrack timeout 12/10/2008]
Seems straight-forward. +1 On 12/ 3/08 09:36 AM, Gerald Jelinek wrote: I am sponsoring this fast-track (which only records a contract) for Ellard Roush. A copy of the contract is in the case directory and both managers will approve the contract before the timeout. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
sg3 utilities 1.25 [PSARC/2008/683]
On 11/13/08 14:19, Darren J Moffat wrote: Gary Winiger wrote: I'll ask the project team to revise the proposal this way. Does everyone agree this is the right approach? No, not without the answers to the various questions posed in the followup to Darren's mail. Of course, the committee can just tell me to shutup. When I asked at the meeting, that wasn't the response I got. I think this case should be marked as waiting need spec. I STRONGLY STRONGLY encourage the project team to work with either or both of Gary and I offline before a new spec is produced. I believe Gary has already offered his help and should be the first point of contact but if my timezone is better for the project team I'm happy to be the second. Gary, I don't think you should be told to shut up. All, I'm interested in this from a far more general position. It didn't seem to me that the sg3 utilities did any more than access the device via its name in the file system. Access to this device shouldn't need to be controlled by the utility, as any program can also attempt to open the device, and send the appropriate commands to get the actions desired. If that is the case, isn't the permissions to access the device provided by Solaris adequate? If that is not the case, I'll continue watching this thread with interest. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Sg3 utilities 1.25 [PSARC/2008/683 Self Review]
On 11/10/08 17:08, Gary Winiger wrote: snip I'm wondering what happend to the thread about superuser and RBAC. Are these commands available to all users? Are they managed through some other existant mechanism? Am I off base and should just shut up? Gary.. Gary, Was Xiao's answer of 11/06/2008 sufficient? (message trimmed) Date: Thu, 06 Nov 2008 14:20:16 +0800 From: xiao li - Sun Microsystems - Beijing China Xiao.L at sun.com Subject: Re: Sg3 utilities 1.25 [PSARC/2008/683 Self Review] I did some investigation on Solaris RBAC, I hope I could answer your questions now. The required privilege should be sys_config, sys_devices, and the profile should be File System Management. Thanks, -Xiao -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/2008/e965f0f7/attachment.html
PSARC/2008/628 - Interrupt Resource Management
Materials have been posted in the case directory under a materials directory. This case is scheduled for review at next weeks meeting. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
ACLs for CIFS/SMB shares [PSARC/2008/641 FastTrack timeout 10/27/2008]
We seem to have no membership participation on this email thread. So, +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
PSARC 2008/625 - Streamline 20Q
Attached is the current versions of the streamlined 20 Questions. There is still active debate about the security question, as to its scope. Perhaps that debate should become part of this case email. Previous versions of the proposed change are also in the case directory, as well as these documents. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- A non-text attachment was scrubbed... Name: proposed20Q.odt Type: application/octet-stream Size: 27323 bytes Desc: not available URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20081021/6de6dfca/attachment.obj -- next part -- A non-text attachment was scrubbed... Name: proposed20Q.pdf Type: application/x-unknown-application-pdf Size: 46031 bytes Desc: not available URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20081021/6de6dfca/attachment.bin -- next part -- An embedded and charset-unspecified text was scrubbed... Name: proposed20Q.txt URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20081021/6de6dfca/attachment.txt
IBTF IO Memory [PSARC/2008/630 FastTrack timeout 10/17/2008]
Minor nit: materials/ibc_operations_t.9s Add ibc_alloc_io_mem(9E) and ibt_alloc_io_mem(9F) to the See also: +1 -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
MMS Disk Archiving [PSARC/2008/621 FastTrack timeout 10/10/2008]
+1 Nit: Should the mmsadm man page have a Disk library/archive example? -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
PSARC 2008/625 - Streamline ARC 20Q
Please use this case to post any discussions of the proposed 20Q document, which I sent on Oct. 2, 2008. Thanks Gary for the suggestion! -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
Today's PSARC meeting - 20Q materials
All, PSARC is attempting to revise the 20 questions document down to something near 20 questions. I had volunteered to take a first crack at this. This proposal was sent to PSARC members and interns. There were some items of feedback. Attached is the original proposal, and the couple of comments (somewhat edited). -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An embedded and charset-unspecified text was scrubbed... Name: proposed20q.txt URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080827/c8797ee1/attachment.txt -- next part -- An embedded and charset-unspecified text was scrubbed... Name: comments.txt URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080827/c8797ee1/attachment-0001.txt
PSARC 2007/420 - SMMS
This note serves as signatures from both the Supplier and Consumer of this contract. The contract (Contract-01) has been posted to the case directory. -- Rick Matthews On 08/13/08 13:43, Gregory Matthews wrote: Allan, Paul, Diana, Rick tells me you need the acsls contract. Attached with Mike's agreement. - Gregor Begin forwarded message: *From:* Michael P. Williams Michael.P.Williams at Sun.COM mailto:Michael.P.Williams at Sun.COM *Date:* May 16, 2008 2:19:27 PM CDT *To:* Gregory Matthews Gregory.Matthews at Sun.COM mailto:Gregory.Matthews at Sun.COM *Cc:* Michael.P.Williams at Sun.COM mailto:Michael.P.Williams at Sun.COM *Subject:* *Re: Whoops, wrong Mike again.* Agreed Gregory Matthews wrote: Mike P. Williams! I just realized I sent this to the wrong Mike again. Sorry. I also added a couple more interfaces that we do use. Thx, - Gregor == Mike, I'd like to get this MMS/CDK contract signed this week of possible. Here are some of the changes I made: * Removed the SAM-QFS references, as it seems like they will need a separate contract and are on different timelines than us. This is an MMS - CDK contract only. Impacted section 3, 4, and 7c. * Updated the language specifying the CDK per Mitch. * Double-checked our interfaces in section 4 per Mitch. * Signed and dated for MMS. Mike, I'd appreciate it if you add your name and date. I'm also sending to Rick Matthews, as he will file with our PSARC case. Let me know if you concur, or need additional changes/info. Thanks much, - Gregor CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES 0. Number: PSARC/2007/420-01 1. This contract is between a SUPPLIER of INTERFACES and a CONSUMER of those INTERFACES, both of whom are entities within Sun Microsystems, Incorporated. 2. The SUPPLIER (definer and/or implementor) is identified by the following: Product or Bundle: CSC Developer's Toolkit (CDK) Version 2.3 Consolidation: Unbundled Department or Group: Systems/Network Storage/ACSLS development Bugster Product/Category/SubCategory: Responsible Manager: Mike Williams 3. The CONSUMER is identified by the following: Product or Bundle: Media Management System (MMS) Consolidation: MMS - NWS Department or Group: Software/Solaris/Archive Products Group Bugster Product/Category/SubCategory: mms Responsible Manager: Gregory Matthews 4. The INTERFACES are: MMS builds shared versions of these libraries. If you follow the steps in the CDK 2.3 user guide you will build the static libraries, libcl.a libutl.a etc...) libcl.so (libcl.a) libutl.so (libutl.a) libapi.so (libapi.a) libipc.so (libipc.a) libssixdr.so (SSIXDR.a) MMS uses the following binaries: mini_el, ssi MMS uses a modified version of t_ssi.sh Types used in lm_acs.h: SAM-QFS Includes (via src/robots/stk/stk.h): ACS_RESPONSE_TYPE SEQ_NO REQ_ID ALIGNED_BYTES Functions called by LM: Interface Stability Level = === acs_type_response Contracted Project Private acs_query_server Contracted Project Private acs_query_driveContracted Project Private acs_query_mountContracted Project Private acs_query_volume Contracted Project Private acs_query_cap Contracted Project Private acs_status Contracted Project Private acs_displayContracted Project Private acs_state Contracted Project Private acs_response Contracted Project Private acs_enter Contracted Project Private acs_eject Contracted Project Private acs_mount Contracted Project Private acs_dismount Contracted Project Private acs_get_packet_version Contracted Project Private acs_type Contracted Project Private acs_query_lsm Contracted Project Private 5. The ARC controlling these INTERFACES is: PSARC 6. The CASE describing (Exporting) these INTERFACES is: TBD (ACSLS is still in the PSARC process. 7. The following SPECIAL ARRANGEMENTS are made which modify the rules imposed by the stability levels listed in section 4 above: 7c. Although the stability level doesn't normally allow it, CONSUMER will import INTERFACES from a separate consolidation. 7d. If SUPPLIER decides to change (including replace or remove) any portion of the INTERFACES, SUPPLIER will notify CONSUMER of the proposed new version, no later than the application for ARC approval of the new version
LSARC/2008/503 - Webalizer
Was approved at todays LSARC meeting. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
MTX 1.3.11 [PSARC/2008/457 FastTrack timeout 07/24/2008]
There are other projects providing media mount services. MMS for example (PSARC/2007/420). I have (due to proximity) informed that team of your work (which addresses SCSI attached libraries, primarily). You may also wish to see if this work already exists (in the familiar form) within Storage in Systems Group. -- Rick Mark Carlson wrote: I am sponsoring this case for Chris Liu. It requests a Patch binding and times out on 7/24/2008. -- mark -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2008/422 - libmikmod
This case was approved in todays LSARC meeting. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
libmikmod [LSARC/2008/422 FastTrack timeout 07/14/2008]
I am sponsoring the following Fast Track for Bill Schoofs. The project requests a minor release binding. All submitted materials are in the case directory. -- 1.0 Project Information 1.1 Name of project/component libmikmod 1.2 Author of document Bill Schoofs 2.0 Project Summary 2.1 Project Description The MikMod sound library is an excellent way for a programmer to add music and sound effects to an application. It is a powerful and flexible library, with a simple and easy-to-learn API. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Originating Community 2.3.1 Community Name MikMod - http://mikmod.raphnet.net/ 2.3.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [X] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [X] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [ ] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a system drive:\Program Files\Sun\product or system drive:\Sun\product directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product\version for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product id\version id\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [X] No 3.2 Libraries Are 64-bit libraries being delivered? [X] Yes [ ] No - ARC review required Are static versions of the library being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [X] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [X] N/A Are
libc printf behaviour for NULL string [PSARC/2008/403 FastTrack timeout 07/02/2008]
Nicolas Williams wrote: On Wed, Jun 25, 2008 at 09:20:54AM -1000, Joseph Kowalski wrote: Jyri Virkki wrote: I read the materials and there are no exported interface changes, no imported interface changes and not even any documentation changes. Sigh,... But its a very visible semantic change. Yes: it lets certain apps run! :) Note: no tongue in cheek. About the fast track length and protocol: I picked Nico's message to reply for no particular reason except the header should ensure it be recorded properly (note: use the ARC ans case as part of the header). This thread is also getting a bit long. Darren, is it time to make it a discussion at PSARC rather than a email trail. About the case: It seems to me this is about being bug compatible with other implementations. This one doesn't seem particularly offensive. WRT compatibility, is this more a gang of four issue as to whether this is the familiarity we want? -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080625/369cfdb6/attachment.html
Full case ? / was: Re: Switch SPARC GNU coreutils+bash from 32 to 64bit [PSARC/2008/351Self Review]
Nicolas Williams wrote: On Mon, Jun 02, 2008 at 09:40:46PM +0200, Roland Mainz wrote: Nicolas Williams wrote: On Mon, Jun 02, 2008 at 12:14:12PM -0700, Garrett D'Amore wrote: [snip] It's a full case now. Who or what decided that ? IMO this still fast-track. Darren Moffat derailed it. In reviewing the email trail (which is getting rather long), Darren said derail, then said at least a fast track. I am going to assume Darren is OK with a fast track until then. I propose we take no more than 5 minutes discussing this fast track at Weds. meeting. During this 5 minutes, ample time will be allowed to derail to a full case, if need be. Perhaps we should table further discussion until Wednesday. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 - -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080602/4c7188e6/attachment.html
SAM-QFS large host table [PSARC/2008/241 FastTrack timeout 04/16/2008]
I am sponsoring the following fast track for Bill Gorrell. The release binding is minor. Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: SAM-QFS Large Host Table 1.2. Name of Document Author/Supplier: William Gorrell 1.3. Date of This Document: 02/29/2008 1.3.1. Date this project was conceived: 05/10/2007 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: NWS PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is Sponsoring this project: Karen.Jourdenais at sun.com 1.4.4. The name of your business unit: SDASH 1.5. Email Aliases: 1.5.1. Responsible Manager: Ted.Pogue at sun.com 1.5.2. Responsible Engineer: William.Gorrell at sun.com 1.5.3. Marketing Manager: Margaret.Hamburger at sun.com 1.5.4. Interest List: samqfs-psarc-interest at sun.com 2. Project Summary 2.1. Project Description: See supplied functional specification document largehosttable.6555811.txt section FEATURE DESCRIPTION. 2.2. Risks and Assumptions: None. 3. Business Summary 3.1. Problem Area: The SAM-QFS HPC initiative requires that a larger number of clients be supported. 3.2. Market/Requester: The SAM-QFS HPC initiative requires that a larger number of clients be supported. 3.3. Business Justification: The SAM-QFS HPC initiative requires that a larger number of clients be supported. 3.4. Competitive Analysis: The SAM-QFS HPC initiative requires that a larger number of clients be supported. 3.5. Opportunity Window/Exposure: FY2009 3.6. How will you know when you are done?: When the HPC target number of SAM-QFS clients can be configured. 4. Technical Description: 4.1. Details: See supplied functional specification document largehosttable.6555811.txt section FUNCTIONAL REQUIREMENTS. 4.2. Bug/RFE Number(s): 6555811: RFE: Increase the size of the client host table. This RFE is currently targeted for the next release of SAM-QFS (FY09). All documentation references to release x.x should be interpreted as that release. 4.3. In Scope: See supplied functional specification document largehosttable.6555811.txt section SCOPE OF THE PROJECT. 4.4. Out of Scope: See supplied functional specification document largehosttable.6555811.txt section SCOPE OF THE PROJECT. 4.5. Interfaces: See supplied functional specification document largehosttable.6555811.txt section FUNCTIONAL REQUIREMENTS. 4.6. Doc Impact: Man pages do not exist for the affected library interfaces. The SAM-QFS administration manual will be updated to describe the extended host table size, and limitations of mounting file systems with a large host table on hosts running a legacy release of SAM-QFS. 4.7. Admin/Config Impact: The administrator will experience the ability to configure a larger number of SAM-QFS clients on a SAM-QFS file system. 4.8. HA Impact: A larger number of supported clients supports improved cluster availability because of the larger number of available failover host candidates. 4.9. I18N/L10N Impact: The error messages that describe a client host table size incompatibility condition will require investigation. 4.10. Packaging Delivery: Providing a larger client host table will not specifically impact package install/upgrade procedures. Associated packages are: SUNWsamfsu, SUNWsamfsr, SUNWqfsu, SUNWqfsr 4.11. Security Impact: None. All client host table operations require administrative authority. 4.12. Dependencies: This feature requires that SAM-QFS voluntary and involuntary failover be reliable prior to release. 5. Reference Documents: See supplied functional specification document. Also reference the full SAM-QFS 5.0 PSARC case 2007/588 at: http://sac.eng/arc/PSARC/2007/588 6. Resources and Schedule: 6.1. Projected Availability: Available with the first release of the SAM-QFS HPC product. 6.2. Cost of Effort: Unspecified. 6.3. Cost of Capital Resources: Unspecified. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Available with the first release of the SAM-QFS HPC product. 6.4.3. Type of CPT Review and Approval expected:
star, rmt, and librmt [PSARC/2008/176 FastTrack timeout 03/12/2008]
Alan Coopersmith wrote: Margot Miller wrote: - /usr/bin/star executable added Joerg just raised an important point on opensolaris-discuss - star has a name-clash with Sun's SAM-QFS star command (which much to Joerg's consternation is based on GNU tar sources instead of his). From PSARC/2001/599 it looks like SAM/QFS ships its star command in /opt/SUNWsamfs/sbin/star so there's not a filename clash, but there could be a $PATH ordering issue for SAM/QFS admins. (I've never used it, so I don't know if they most often use it from $PATH, scripts or other means.) (There's also an open case 2007/588 for the SAM/QFS 5.0 release where this issue may also need to be addressed.) The SAM-QFS star is provided as a disaster recovery tool to recover data from archive tape. As Joerg points out, the original tar format was inadequate for all types and sizes of files. The portability of archive format is very important to customers, as to not lock them into any given O/S, hardware nor tar. It is not used on a regular basis, except when users would do so on their own. The sbin directory is primarily used for SAM-QFS administrators, developers and testers. While this clash will exist, in my opinion, the clash is not likely to happen. I'm adding the SAM-QFS PSARC team (as Margot did) to this thread. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
star, rmt, and librmt [PSARC/2008/176 FastTrack timeout 03/12/2008]
Joerg Schilling wrote: Gary Winiger gww at eng.sun.com wrote: Proposal: Integrate schily tar (star), a tar-like clone with more features Does star(1) support the Trusted Solaris extensions? I should have asked: Does star(1) support all the functionality of tar(1)? If not what's missing? If called as tar, star supports the functionality of Sun's tar with a few exceptions. Once, star is in OpenSolaris, I hope this is no longer a rabbit and hedgehog play. Are there other exceptions other than those addressed below? So, for the purposes of documentation I'd like to see the exceptions noted. There is currently no support for Sun's ACL/extended-attribute archive format that is based on outdated technology. Star however supports a _portable_ ACL archive format that is based on recent POSIX technology for vendor specific extensions. I can understand reasons for not writing Solaris format archives, but what prevents star or the OpenSolaris star project from reading Solaris format archives? Lack of interest may be a satisfactory answer, but there are those who already have tar-like archives from Solaris. From what you've indicated, star supports an archive format WRT ACLs that readable and usable by tar implementations on other OSs (other than a star implementation). Is that correct? The problem with the trusted Solaris extensions is that they are undocumented. Let us discuss the application interface to make it fit nicely into star and let us define an archive format for these extensions. I see no reason why this cannot be implemented. I am also interested in discussing the archive format for extended attribute files. Joerg, I and others are interested in discussing archive format (tar-like) for various applications within Solaris and OpenSolaris. Portability of format is a big deal. Is there a OpenSolaris or other discussion forum in which these are being discussed? J?rg -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
CIFS system attributes support for cpio(1), pax(1), tar(1) [PSARC/2007/459 FastTrack timeout 08/17/2007]
of incompatible options into tar/cpio/pax, the plan to give Solaris modern, safe and feature rich replacements for the dusty old implementations will be made impossible just by this planned act. Yes, it'd be possible _in the future_ to create a project that removes the OpenSolaris tar sources (and pax and cpio) and replaces them with links to star. Yes, it might even be helpful to do so. However, that project doesn't currently exist. There is no ARC case that specifies it. There's no plan showing when (or if) it will ever show up. All that we have is a hint in 2004/480 that this might be a future project. See above and understand what really happened... You're thus asking that we block an otherwise reasonable project on the grounds that maybe -- someday -- there might be a conflict with some other implementation. How far does that extend? How many other people have created their own personal variants of common tools? Should we survey them all, or do just yours alone matter? Sorry, I am just requesting to prevent to implement enhancements in an _unrasonable_ way. I am not trying to prevent feature enhancements. This ARC case however tries to prevent future feature enhancements. J?rg -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
