NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
Robert Thurlow schrieb: Joerg Barfurth wrote: Rich Brown schrieb: I forgot to include the man page for the proposed nfsref(1M) command when I submitted this case on Friday afternoon. This command, as proposed, is straightforward and is already described in the text of the fast-track. I've put a copy of the man page in the case directory for completeness and have attached a copy to this note. You only give 'Committed' as overall nfsref stability. Does this extend to nfsref lookup output? Can you provide a way to (optionally) have an output format better suited to parsing/scripting than path points to: location [ location]* (format of multi-location output my assumption)? I should have specified the output as Unstable; What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still more stable than you think. From what you say below, you want output to be 'Not an Interface'. I don't think scripting based on the command is a good idea, and Why not. Things like wrapping a simple GUI (for example in python) around this come to mind. Doing a C app built on libreparse.so is significantly more effort. it may change as we get more experience with this stuff. Since the symlink format is Committed, you could script on ls -l output with some parsing effort, or your application could make use of libreparse.so. And picking up the question of spaces: how will spaces be handled in nfsref lookup output? Embedded spaces are currently just printed: # nfsref add /bbb h1:/p1 h2:/p2 p2a Added to reparse point /bbb # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Uh. Here even human parsing reaches its limits, needing to reconstruct quotes as location boundaries in one's mind. - J?rg -- Joerg Barfurth phone: +49 40 23646662 / x2 Software Engineermailto:joerg.barfurth at sun.com Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbHhttp://www.sun.com/software/javadesktopsystem/
GDB: The GNU Project Debugger [LSARC/2009/492 FastTrack timeout 09/22/2009]
Raj Prakash Raj.Prakash at sun.com writes: 2. Project Summary 2.1. Project Description: Upgrade GDB from version 6.3 to 6.8, the latest released version. Also, add support for debugging 64 bit executables. 4. Technical Description: 4.1. Details: The GDB 6.8 source will be built both -m32 and -m64. The 64 bit build is required to support debugging of 64 bit executables. Users running on 64 bit systems will get the 64 bit version of GDB by default allowing them to debug both 32 bit and 64 bit executables while users running on 32 bit systems will get the 32 bit version of GDB allowing them to debug 32 bit executables. The isaexec command will be used to invoke the appropriate version of the debugger depending on the system. Is there a reason to use isaexec on SPARC? There's no 32-bit kernel anymore, so the 32-bit binary will not be used by isaexec, but could only invoked manually. Unless the 64-bit GDB has trouble debugging 32-bit programs, there's no reason to ship the 32-bit version on SPARC at all. From the file listing below, it seems there is no /usr/bin/sparcv7/gdb*, but this should be stated explicitly and the isaexec step omitted to avoid the unnecessary overhead. 4.5. Interfaces: GDB 6.8 will be installed in /usr/bin with compatibility links added to /usr/sfw/bin similar to the the current 6.3 version: I think those should be listed in this case as well. What about symlinks for info and man pages? usr usr/bin usr/bin/amd64 usr/bin/amd64/gdb usr/bin/amd64/gdbtui usr/bin/gdb=../lib/isaexec usr/bin/gdbtui=../lib/isaexec usr/bin/i86 usr/bin/i86/gdb usr/bin/i86/gdbtui usr/bin/sparcv9 usr/bin/sparcv9/gdb usr/bin/sparcv9/gdbtui usr/sfw usr/sfw/bin usr/sfw/bin/gdb=../../bin/gdb usr/sfw/bin/gdbtui=../../bin/gdbtui usr/share usr/share/info usr/share/info/annotate.info usr/share/info/gdb.info usr/share/info/gdb.info-1 usr/share/info/gdb.info-2 usr/share/info/gdb.info-3 usr/share/info/gdb.info-4 usr/share/info/gdbint.info usr/share/info/gdbint.info-1 usr/share/info/gdbint.info-2 usr/share/info/stabs.info usr/share/man usr/share/man/man1 usr/share/man/man1/gdb.1 usr/share/man/man1/gdbtui.1 Rather than list all files and directories in SUNWgdb, it would be better to list the exported (and imported) interfaces and their stability. In particular, what about readline support? Will it be included? Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
Joerg Barfurth wrote: I should have specified the output as Unstable; What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still more stable than you think. From what you say below, you want output to be 'Not an Interface'. That does match my intent, thanks for correcting. I do think this could change with more real-world experience. And picking up the question of spaces: how will spaces be handled in nfsref lookup output? Embedded spaces are currently just printed: # nfsref add /bbb h1:/p1 h2:/p2 p2a Added to reparse point /bbb # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Uh. Here even human parsing reaches its limits, needing to reconstruct quotes as location boundaries in one's mind. Would this format be better? I could do this instead: # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Rob T
GDB: The GNU Project Debugger [LSARC/2009/492 FastTrack timeout 09/25/2009]
I have received the replies. I am on the opensolaris arc alias and open cases seem to be forwarded there. Thanks, George Raj Prakash wrote: Please copy George Vasick on your emails. -- Raj Original Message Subject: Re: GDB: The GNU Project Debugger [LSARC/2009/492 FastTrack timeout 09/22/2009] Date: Wed, 23 Sep 2009 13:14:08 +0200 From: Rainer Orth ro at techfak.uni-bielefeld.de To: Raj Prakash Raj.Prakash at Sun.COM CC: Raj Prakash rprak at antler.sfbay.sun.com, LSARC-ext at sun.com Raj Prakash Raj.Prakash at sun.com writes: 2. Project Summary 2.1. Project Description: Upgrade GDB from version 6.3 to 6.8, the latest released version. Also, add support for debugging 64 bit executables. 4. Technical Description: 4.1. Details: The GDB 6.8 source will be built both -m32 and -m64. The 64 bit build is required to support debugging of 64 bit executables. Users running on 64 bit systems will get the 64 bit version of GDB by default allowing them to debug both 32 bit and 64 bit executables while users running on 32 bit systems will get the 32 bit version of GDB allowing them to debug 32 bit executables. The isaexec command will be used to invoke the appropriate version of the debugger depending on the system. Is there a reason to use isaexec on SPARC? There's no 32-bit kernel anymore, so the 32-bit binary will not be used by isaexec, but could only invoked manually. Unless the 64-bit GDB has trouble debugging 32-bit programs, there's no reason to ship the 32-bit version on SPARC at all. From the file listing below, it seems there is no /usr/bin/sparcv7/gdb*, but this should be stated explicitly and the isaexec step omitted to avoid the unnecessary overhead. 4.5. Interfaces: GDB 6.8 will be installed in /usr/bin with compatibility links added to /usr/sfw/bin similar to the the current 6.3 version: I think those should be listed in this case as well. What about symlinks for info and man pages? usr usr/bin usr/bin/amd64 usr/bin/amd64/gdb usr/bin/amd64/gdbtui usr/bin/gdb=../lib/isaexec usr/bin/gdbtui=../lib/isaexec usr/bin/i86 usr/bin/i86/gdb usr/bin/i86/gdbtui usr/bin/sparcv9 usr/bin/sparcv9/gdb usr/bin/sparcv9/gdbtui usr/sfw usr/sfw/bin usr/sfw/bin/gdb=../../bin/gdb usr/sfw/bin/gdbtui=../../bin/gdbtui usr/share usr/share/info usr/share/info/annotate.info usr/share/info/gdb.info usr/share/info/gdb.info-1 usr/share/info/gdb.info-2 usr/share/info/gdb.info-3 usr/share/info/gdb.info-4 usr/share/info/gdbint.info usr/share/info/gdbint.info-1 usr/share/info/gdbint.info-2 usr/share/info/stabs.info usr/share/man usr/share/man/man1 usr/share/man/man1/gdb.1 usr/share/man/man1/gdbtui.1 Rather than list all files and directories in SUNWgdb, it would be better to list the exported (and imported) interfaces and their stability. In particular, what about readline support? Will it be included? Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
On Wed, Sep 23, 2009 at 09:05:03AM -0600, Robert Thurlow wrote: Joerg Barfurth wrote: I should have specified the output as Unstable; What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still more stable than you think. From what you say below, you want output to be 'Not an Interface'. That does match my intent, thanks for correcting. I do think this could change with more real-world experience. You can always evolve Committed output by adding more options. I agree with Joerg here: stable output for this command, if parseable, would be very valuable. And picking up the question of spaces: how will spaces be handled in nfsref lookup output? Would this format be better? I could do this instead: # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Embedded newlines are still a problem. Here's what I suggest: a) Add an option (say, -q) to do backslash quoting of whitespace and backslash. b) When (a) is used the output format should be Committed. c) Since the NFS referral does depend somewhat on NFS protocol version (referrals carry more information in v4.1 than in v4.0), I'd say: add a protocol version number option (say, -p), and default to v4.1. d) Don't forget that '/' too is allowed as a character in NFSv4 path components, even though POSIX doesn't, so '/' needs quoting. e) Use this output format: # nfsref lookup -q /bbb h1:/some\ path/with/\ \ crazy\ whitespace/and\/even\ slashes h2:/p2 # Note the lack of /bbb points to: -- that was always redundant. If you really want that in the output, then have an option for parseable output to select the above output format. Nico --
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
On 09/23/09 10:56, Rick Matthews wrote: Nit: The submitted man page had addR, removeR and lookupR. I'm assuming the R is a typo. Yes, I thought I responded to this already but I realize it was from an off-list comment. This will be corrected in the final version. Should there be a reference to the privilege required for nfsref in the man page? Yes, it will be added in the final version. +1 Thanks, Rich
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
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? Rob T
LatencyTOP for OpenSolaris [PSARC/2009/339 FastTrack timeout 06/10/2009]
The project team would like the latest man page reflected in the case archive. man-page.txt and man-page-diff.txt can be found in the materials directory. They have also been attached for easy viewing. Sherry -- Sherry Moore, Solaris Core Kernel http://blogs.sun.com/sherrym -- next part -- System Administration Commands latencytop(1M) NAME latencytop - report statistics related to latencies in the system and in applications SYNOPSIS latencytop [-t interval] [-o log-file] [-k log-level] [c config-file] [-f (no)feature,...] [-l log-interval] [-h] DESCRIPTION LatencyTOP is an observability tool that reports statistics about latencies in the system and in applications. The tool reports statistics about where and what kind of latencies are happening in the system and in the applications that are running on the system. The statistics then can be used to improve performance throughput of applications and system by removing the latencies. The tool analyzes system activity periodically and displays the data in the output window. Two types of latencies are tracked - an LWP going in and out of sleep and an LWP spinning order to acquire a synchronization object. The tool uses the Solaris DTrace framework to collect the statistics corresponding to these two scenarios of inactivity of the system and application LWPs. The output window is divided into two sections - upper part displays the system-wide statistics while the lower part displays statistics about individual processes. The user can navigate the list of processes (using the and the keys) and select the one they are interested in, and the tool will display statistics about that selected process in the lower part of the window; if the t or T key is pressed, the tool displays the LWP-specific view of that selected process. Thus, the t or T key can be used to toggle between the process-view and the thread-view. During execution, a user can force a refresh of the analysis by pressing the r or R key. The interval time is restored to the default or to a specified value (if -t was used). To quit the application, the user must press the q or Q key. OPTIONS The following options are supported: -o [log-file] Specifies the log file where output will be written. The default log file is /var/log/latencytop.log. -k [log-level] Specifies the level of logging in the log file. Valid values are: 0 = none (default), 1 = unknown, and 2 = all; -t [interval] Specifies the interval, in seconds, at which the tool collects statistics from the system. The possible values are between 1 and 60; the default is 5 seconds. -f, --feature [no]feature1,[no]feature2,... Enables/disables features in LatencyTOP. Features can only be one of the following : [no]filter: Filter large interruptible latencies, e.g. sleep. Default: off [no]sched: Monitors sched (PID=0). Default: off [no]sobj: Monitors synchronize objects. Default: on [no]low: Lower overhead by sampling small latencies. Enabling this feature will lower CPU utilization by estimating small latencies statistically. Use it for heavy workloads such as a very busy web server. Default: off -l [log-interval] Writes data to the log file every log-interval seconds; log-interval must be 60. -h Displays the command's usage. EXAMPLES Example 1 Running the tool The following command launches the tool with default values for options. % latencytop Example 2 Setting the Interval The following command sets the interval to two seconds. % latencytop -t 2 Example 3 Setting the log file The following command sets the log file to /tmp/latencytop.log. % latencytop -o /tmp/latencytop.log Example 4 Setting the log level The following command sets the log level to all. % latencytop -l 2 Example 4 Enabling tracing of latencies caused by synchronization objects. The following command enables the tracing of latencies caused by synchronization objects. % latencytop -f sobj EXIT STATUS 0 Successful operation. 1 An error occurred. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: | ATTRIBUTE TYPE| ATTRIBUTE VALUE |
x86 Generic FMA Topology Enumerator [PSARC/2009/490 FastTrack timeout 09/22/2009]
Tim Haley wrote: I am sponsoring this case on behalf of Tom Pothier. The case seeks micro/patch binding. Timeout is 09/22/2009. The case introduces a variety of interfaces to support a new generic x86 FMA topology enumerator. Graciously requesting a member's +1. :-) thanks, -tim
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
Nicolas Williams wrote: You can always evolve Committed output by adding more options. I agree with Joerg here: stable output for this command, if parseable, would be very valuable. To be clear, the proposed committment level of the nfsref output is Not An Interface. We could add a Committed parsable output when we know more about what we'd use it for. c) Since the NFS referral does depend somewhat on NFS protocol version (referrals carry more information in v4.1 than in v4.0), I'd say: add a protocol version number option (say, -p), and default to v4.1. To be clear, this project is about v4.0 referrals only. v4.1 referrals will compel us to revisit this, when we get there. Rob T
PSARC 2009/477 Addition of NE_IFINDEX_CHANGE to sys/neti.h
Garrett D'Amore wrote: +1 on this case. - Garrett This case was approved at PSARC last week. - Garrett
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
On Wed, Sep 23, 2009 at 10:26:27AM -0600, Robert Thurlow wrote: Nicolas Williams wrote: You can always evolve Committed output by adding more options. I agree with Joerg here: stable output for this command, if parseable, would be very valuable. To be clear, the proposed committment level of the nfsref output is Not An Interface. We could add a Committed parsable output when we know more about what we'd use it for. The command can clearly be used to script creation of referrals. Therefore it stands to reason that it should be scriptable for maintaining referrals data as well, which to me means being able to parse its output. I am not an ARC member, so you're free to ignore these comments, but I do think you'll make the product better if you accept my comments. c) Since the NFS referral does depend somewhat on NFS protocol version (referrals carry more information in v4.1 than in v4.0), I'd say: add a protocol version number option (say, -p), and default to v4.1. To be clear, this project is about v4.0 referrals only. v4.1 referrals will compel us to revisit this, when we get there. Understood. But this is not a reason to have Not-An-Interface for the output, since you can always evolve the command by adding options. Nico --
x86 Generic FMA Topology Enumerator [PSARC/2009/490 FastTrack timeout 09/22/2009]
Tim Haley wrote: Tim Haley wrote: I am sponsoring this case on behalf of Tom Pothier. The case seeks micro/patch binding. Timeout is 09/22/2009. The case introduces a variety of interfaces to support a new generic x86 FMA topology enumerator. Graciously requesting a member's +1. :-) thanks, -tim +1 There you go. :-) - Garrett
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 -
x86 Generic FMA Topology Enumerator [PSARC/2009/490 FastTrack timeout 09/22/2009]
This case was approved in today's meeting. -tim
IP_DONTFRAG socket option [PSARC/2009/494 FastTrack timeout 09/23/2009]
On Wed, 2009-09-16 at 12:03 -0400, Sebastien Roy wrote: I'm submitting this fast-track for Erik Nordmark, it times out on 09/23/2009. The release binding is Patch. This case was approved during today's PSARC meeting. -Seb
netstat -r flags for blackhole and reject routes [PSARC/2009/495 FastTrack timeout 09/23/2009]
On Wed, 2009-09-16 at 12:10 -0400, Sebastien Roy wrote: I'm submitting this fast-track for Erik Nordmark. It times out on 09/23/2009. The release binding is Minor due to the change in semantics of the netstat -r 'B' route flag. This case was approved during today's PSARC meeting. -Seb
EOF of XRESOLV [PSARC/2009/496 FastTrack timeout 09/23/2009]
On Wed, 2009-09-16 at 16:29 -0400, Sebastien Roy wrote: I'm submitting this fast-track for Sowmini Varadhan. It times out on 09/23/2009. The release binding is Minor. This case was approved during today's PSARC meeting. -Seb
Synergy - Mouse/Keyboard sharing [LSARC/2009/489 FastTrack timeout 09/21/2009]
LSARC, This case could have been automatically approved as a Familiarity case if it hadn't been for the fact that it does not support IPv6. Is the committee OK with the project not supporting IPv6? Thanks, John Alan Coopersmith wrote: I am sponsoring this case for Stuart Kreitman of the X team. The timeout is set for next Monday, Sept. 21, 2009. -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering FCL--FOSS Check List 0. Introduction 0.1 Document History Version Author Changes Date 0.1 John Fischer Initial Draft 01/11/2008 0.2 John Fischer Modified based upon feedback from ARC members01/29/2008 0.3 John Fischer Modified based upon feedback during committee02/12/2008 review 0.4 John Fischer Modified based upon SAC review feedback 04/01/2008 0.5 John Fischer Modified based upon LSARC business meeting 06/10/2008 adding familiarity question and mod dates. 0.6 John Fischer Modified based upon user feedback about 06/20/2008 sections that were unanswerable. 0.2 Purpose Architecture review at Sun has allowed the company to evolve our projects within multiple disjoint groups while still maintaining a cohesive product line. Each architecture review was conducted within Sun's control. With the advent of Free Open Source Software processes the control that Sun as a company can wield has been diminished. Now that Sun is moving to a more fluid delivery mechanism with project Indiana we need to evolve the architecture review process. This document is meant to aid in the architecture review process. Each new project must complete this check list to help ensure that the overall resulting product conforms to Sun product standards. If the project deviates from these standards further review would be necessary by an architecture review committee. After the check list is completed the project team should be able to determine if a project can be automatically approved. This will occur if all checks result in no ARC review required answers. A committee member will assist the project team in filing the automatically approved fast track. An automatically approved fast track is still required in order to record the interfaces for future reference. If the project needs to have further review then follow the regular process for getting projects reviewed. 1.0 Project Information 1.1 Name of project/component Synergy - Mouse/Keyboard sharing 1.3.1, April 02-2006 1.2 Author of document Stuart Kreitman 2.0 Project Summary 2.1 Project Description Synergy lets you easily share a single mouse and keyboard between multiple computers with different operating systems, each with its own display, without special hardware. It's intended for users with multiple computers on their desk since each system uses its own monitor(s). Redirecting the mouse and keyboard is as simple as moving the mouse off the edge of your screen. Synergy also merges the clipboards of all the systems into one, allowing cut-and-paste between systems. Furthermore, it synchronizes screen savers so they all start and stop together and, if screen locking is enabled, only one screen requires a password to unlock them all. 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 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name Synergy is hosted on Sourceforge. http://synergy2.sourceforge.net 2.4.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]
NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009]
This case was approved at today's PSARC meeting. I've put an updated man page in the case directory. Thank you for your time and help, Rich
OpenSolaris ARC Minutes - 09/23/2009
SYSTEM ARCHITECTURE COUNCIL Platform Software ARC - PSARC Regular Meeting time: Wednesdays 10:00-1:00pm in MPK17-3507. 09-23-2009 MEETING MINUTES Send CORRECTIONS, additions, deletions to psarc-coord at sun.com. Minutes are archived in sac.Eng:/sac/export/sac/Minutes/PSARC. Co-Chair(s): Garrett D'Amore:Yes Tim Marsland: no ATTENDEES - Members: (6 active members) Kais Belgaied: Yes Mark Carlson: no Richard Matthews: Yes Darren Moffat: no (on sabbatical) Sebastien Roy: Yes Glenn Skinner: Yes Bill Sommerfeld:no (on sabbatical) Gary Winiger: Yes (on sabbatical) STAFF - Asa Romberger (PM): Yes ATTENDEES - Interns: Frank Che no James Falkner: no (on sabbatical) Daniel Hain:Yes Michael Haines: no Alan Hargreaves:no Phil Harman:no Wyllys Ingersoll: no Darren Reed:no Dean Roehrich no Ienup Sung: no Phi TranYes Brian Utterback:no James WalkerYes Suhasini PeddadaYes Calum MackayYes Mark Martin Yes (external) Don Cragun Yes (external) Guests: -- GUESTS -- Rich Brown Rob Thurlow Tim Haley Gerry Jelinek Not all names are captured. Please send email to Asa.Romberger at Sun.com, if you attended the meeting and your name is missing from the list. --- MEETING SUMMARY: AGENDA 09/23/2009 10:00-10:10 Open ARC Business (use open dial in above) 10:10-10:55 Commitment: S10C (2009/253) Submitter: Gerald Jelinek Owner: Rick Matthews Intern: Dean Roehrich Exposure: open --- Case Anchors: br A HREF=#case1S10C (2009/253)/A br A HREF=#case2 Solaris ATCA IPMI Driver (2009/467)/A br === Fast Tracks: Case (Timeout) Exposure Title 2009/394 (09/24/09) open SATA Framework Port Multiplier Support approved 2009/477 (09/15/09) open Addition of NE_IFINDEX_CHANGE to sys/neti.h approved 2009/490 (09/22/09) open x86 Generic FMA Topology Enumerator approved 2009/494 (09/23/09) open IP_DONTFRAG socket option approved 2009/495 (09/23/09) open netstat -r flags for blackhole and reject routes approved 2009/496 (09/23/09) open EOF of XRESOLV approved 2009/499 (09/24/09) open iBus integration extend to 9/30 2009/501 (09/25/09) open Dynamic Ring Grouping on NICs let it run 2009/502 (09/25/09) open NFS Referrals approved 2009/503 (09/28/09) open usr/lib links for OpenSSL approved 2009/504 (09/28/09) open libstmf validate view interface let it run 2009/505 (09/28/09) open IRM Framework Extension(s) let it run 2009/507 (09/29/09) open FIPS Capable OpenSSL let it run 2009/508 (09/29/09) open ettcp let it run ARC Business: = Seb Roy will take over as Chair starting next week Next Meeting: = 09/30/2009 10:00-10:10 Open ARC Business (use open dial in above) 10:10-10:55 Commitment: Brussels II - ipadm and libipadm (2009/306) Submitter: Girish Moodalbail Owner: Sebastien Roy Exposure: open --- --- 2009/253 Name: S10C Submitter: Gerald Jelinek Owner: Rick Matthews Exposure: open SUMMARY === Use the BrandZ infrastructure to deliver a Solaris 10 (S10) brand for Solaris.next (S.next). This will be provided as an adoption and compatibility aid to enable customers currently running S10 to easily adopt S.next while also continuing to run their S10 software within branded zones. This allows the customer to rapidly switch over to S.next,
GDB: The GNU Project Debugger [LSARC/2009/492 FastTrack timeout 09/22/2009]
Rainer Orth wrote: Raj Prakash Raj.Prakash at sun.com writes: 2. Project Summary 2.1. Project Description: Upgrade GDB from version 6.3 to 6.8, the latest released version. Also, add support for debugging 64 bit executables. 4. Technical Description: 4.1. Details: The GDB 6.8 source will be built both -m32 and -m64. The 64 bit build is required to support debugging of 64 bit executables. Users running on 64 bit systems will get the 64 bit version of GDB by default allowing them to debug both 32 bit and 64 bit executables while users running on 32 bit systems will get the 32 bit version of GDB allowing them to debug 32 bit executables. The isaexec command will be used to invoke the appropriate version of the debugger depending on the system. Is there a reason to use isaexec on SPARC? There's no 32-bit kernel anymore, so the 32-bit binary will not be used by isaexec, but could only invoked manually. Unless the 64-bit GDB has trouble debugging 32-bit programs, there's no reason to ship the 32-bit version on SPARC at all. From the file listing below, it seems there is no /usr/bin/sparcv7/gdb*, but this should be stated explicitly and the isaexec step omitted to avoid the unnecessary overhead. The thread 64-bit only projects? was posted by Chris the day after I filed this case. It looks like the consensus is to put the 64 bit binary directly into /usr/bin and eliminate isaexec for Sparc. I'll make the change. 4.5. Interfaces: GDB 6.8 will be installed in /usr/bin with compatibility links added to /usr/sfw/bin similar to the the current 6.3 version: I think those should be listed in this case as well. Agreed. I'll make the correction. What about symlinks for info and man pages? The existing gdb 6.3 package does not include include man or info links in sfw, only /usr/sfw/bin/gdb. It is my understanding the sfw is scheduled to go away at some point in the future. Given that, I think it does not make sense to add these links. usr usr/bin usr/bin/amd64 usr/bin/amd64/gdb usr/bin/amd64/gdbtui usr/bin/gdb=../lib/isaexec usr/bin/gdbtui=../lib/isaexec usr/bin/i86 usr/bin/i86/gdb usr/bin/i86/gdbtui usr/bin/sparcv9 usr/bin/sparcv9/gdb usr/bin/sparcv9/gdbtui usr/sfw usr/sfw/bin usr/sfw/bin/gdb=../../bin/gdb usr/sfw/bin/gdbtui=../../bin/gdbtui usr/share usr/share/info usr/share/info/annotate.info usr/share/info/gdb.info usr/share/info/gdb.info-1 usr/share/info/gdb.info-2 usr/share/info/gdb.info-3 usr/share/info/gdb.info-4 usr/share/info/gdbint.info usr/share/info/gdbint.info-1 usr/share/info/gdbint.info-2 usr/share/info/stabs.info usr/share/man usr/share/man/man1 usr/share/man/man1/gdb.1 usr/share/man/man1/gdbtui.1 Rather than list all files and directories in SUNWgdb, it would be better to list the exported (and imported) interfaces and their stability. exported interfaces: * CLI commands: volatile * MI commands: volatile imported interfaces: * ELF * DWARF * /proc * libdl.so.1 * libcurses.so.1 * libsocket.so.1 * libnsl.so.1 * libm.so.2 * libexpat.so.1 * libc.so.1 * libmp.so.2 * libmd.so.1 * libscf.so.1 * libuutil.so.1 * libgen.so.1 * libsmbios.so.1 In particular, what about readline support? Will it be included? readline support is present. gdb 6.8 includes its own copy of readline-5.1 source which is used during the build. Thanks, George Rainer
Dynamical assembling the bootpath for iSCSI boot on sparc [PSARC 2009/480 FastTrack timeout 09/23/2009]
The enclosed updated proposal has been placed in the case directory documenting the discussions and decisions in this thread. Changes made to the spec include: 1. The name of the project has been changed to Dynamical assembling the bootpath for iSCSI boot on sparc 2. The proposed solution in the original case is withdrawn. 3. 3 options are listed with a detailed explanation/justification of each one, including the prposed option 3 of dynamical assembling the bootpath for iSCSI boot. 4. The Interfaces section has been updated to remove the boot_archive interface and an additional import of the property from OBP used in assembling the bootpath has been added. Anybody need more time? -- mark Garrett D'Amore wrote: This case has failed to meet the obviousness requirements for self-review. At PSARC today, the agreement was to turn this into a fast track with a timer set for Sept 23. I've updated the IAM file to reflect this. - Garrett ___ opensolaris-arc mailing list opensolaris-arc at opensolaris.org -- next part -- An embedded and charset-unspecified text was scrubbed... Name: iscsibootpath.txt URL: http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090923/992efab7/attachment-0001.txt
Dynamical assembling the bootpath for iSCSI boot on sparc [PSARC 2009/480 FastTrack timeout 09/23/2009]
Mark A. Carlson wrote: The enclosed updated proposal has been placed in the case directory documenting the discussions and decisions in this thread. Changes made to the spec include: 1. The name of the project has been changed to Dynamical assembling the bootpath for iSCSI boot on sparc 2. The proposed solution in the original case is withdrawn. 3. 3 options are listed with a detailed explanation/justification of each one, including the prposed option 3 of dynamical assembling the bootpath for iSCSI boot. 4. The Interfaces section has been updated to remove the boot_archive interface and an additional import of the property from OBP used in assembling the bootpath has been added. Anybody need more time? The approach chosen seems like a hack to me, but if it works, I'm ok with it. (I still feel like the objections raised by the OBP group here are a bit... ahem... arbitrary. But I also think the fact that we still have split sd and ssd drivers is a very unfortunate circumstance.) - Garrett -- mark Garrett D'Amore wrote: This case has failed to meet the obviousness requirements for self-review. At PSARC today, the agreement was to turn this into a fast track with a timer set for Sept 23. I've updated the IAM file to reflect this. - Garrett ___ opensolaris-arc mailing list opensolaris-arc at opensolaris.org
