PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Laszlo (Laca) Peter
On Mon, 2008-02-04 at 13:56 -0600, Nicolas Williams wrote: > What about class action scripts that can't run in alternate boot / LU? Well, JDS doesn't have any so an example would help me picture it. I would normally recommend using class action scripts when it's simple enough to be scriptable an

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Laszlo (Laca) Peter
On Mon, 2008-02-04 at 20:29 -0500, Sebastien Roy wrote: > John Fischer wrote: > > Instead, JDS in Nevada uses postrun for running these programs. > > Postrun generalizes the above idea by putting the complex > > script into a shared script (postrun itself) and using a > > single smf

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Laszlo (Laca) Peter
A question for LSARC regarding these libs: Given that these are c++ libs, is it acceptable to ship duplicate copies built with g++ (/usr/sfw/bin/g++) and if so, where should they be installed? Why would that be useful? For building gtkmm-based applications that are difficult (to say the least) t

Libgc for Indiana [LSARC/2008/067 FastTrack timeout 02/13/2008]

2008-02-05 Thread Jerry Tan
Yes, these API should be labeled as "Committed" . James Carlson wrote: > Irene Huang writes: > >> There are many projects that use gc, including >> > [...] > >> /usr/lib/libcord.so Volatilelibrary >> /usr/lib/libgc.so Volatile

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread casper....@sun.com
>So that's the earliest they will be run. At the other end, >gnome-session waits for all postrun scripts in the JDS_wait >class to complete before the session is started. (A progress bar >is displayed, the label is something like 'completing post >installation confirugation'.). > >The current c

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread simon.zh...@sun.com
Danek Duvall wrote: > > >> /usr/lib/libglibmm_generate_extra_defs-2.4.so Volatile >> > > Does anyone ever need to link to this library specifically? This seems > like a very private implementation detail that should either be a filter > library or simply not exist on Solaris.

PSARC/2008/069 Additional USB Device Properties

2008-02-05 Thread Edward Pilatowicz
one comment. a boolean "high-speed" property makes sense when there are only two speeds available (ie, use 1.0 and usb 2.0) but i keep hearing about usb 3.x compared with the next version of firewire, etc. perhaps something more future proof would make sense for a committed interfaces? ed ps - i ha

2008/057 Default Route For Zones

2008-02-05 Thread Edward Pilatowicz
On Thu, Jan 31, 2008 at 07:03:47AM -0800, Glenn Faden wrote: > James Carlson wrote: > >Jarrett Lu writes: > > > >>So far, I don't see a cliff yet. Ed's concern is mostly about not > >>cleaning up > >>default routes after zones are halted. While I think Ed has a point, I > >>don't > >>see zones not

PSARC/2008/069 Additional USB Device Properties

2008-02-05 Thread Darren J Moffat
Edward Pilatowicz wrote: > one comment. > a boolean "high-speed" property makes sense when there are only > two speeds available (ie, use 1.0 and usb 2.0) but i keep hearing > about usb 3.x compared with the next version of firewire, etc. > perhaps something more future proof would make sense for a

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread John Plocher
Laszlo (Laca) Peter wrote: > gnome-session waits for all postrun scripts in the JDS_wait A few questions/comments ... jmp-1) Brand and organization names like JDS should never be used in architectural level artifacts - rather a descriptive word should be used instead. jmp-2) There should be a

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Danek Duvall
On Tue, Feb 05, 2008 at 06:19:56PM +0800, simon.zheng at sun.com wrote: > Danek Duvall wrote: > >>> /usr/lib/glibmm-2.4/proc/gmmprocVolatile >> >> What goes here and why is it Public? > > Gtkmm or other libraries needs this program to generate gtkmm-style source

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Brian Cameron
Simon: >>> /usr/lib/libglibmm_generate_extra_defs-2.4.so Volatile >>> >> >> Does anyone ever need to link to this library specifically? This seems >> like a very private implementation detail that should either be a filter >> library or simply not exist on Solaris. >> > Fin

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Alan Coopersmith
Brian Cameron wrote: > > Simon: > /usr/lib/libglibmm_generate_extra_defs-2.4.so Volatile >>> >>> Does anyone ever need to link to this library specifically? This seems >>> like a very private implementation detail that should either be a filter >>> library or simply

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Ghee Teo
Danek Duvall wrote: > I'll echo Jim's comments in the SQLite case about calling everything > Volatile. It's really not appropriate, especially since these are > components that exist specifically for other projects to build on top of. > I take your point about not to throw "Volatile" at every

Gtkmm, Glibmm, Cairomm and libsigc++ for Indiana [LSARC/2008/074 FastTrack timeout 02/13/2008]

2008-02-05 Thread Ghee Teo
Danek Duvall wrote: > On Tue, Feb 05, 2008 at 06:19:56PM +0800, simon.zheng at sun.com wrote: > > >> Danek Duvall wrote: >> >> /usr/lib/glibmm-2.4/proc/gmmprocVolatile >>> What goes here and why is it Public? >>> >> Gtkmm or other

PSARC/2008/069 Additional USB Device Properties

2008-02-05 Thread Artem Kachitchkine
> I was initially going to send a very similar comment then I remembered > that "high-speed" is actually USB terminology in common use. > > IMO it wasn't forward thinking terminology for considering future faster > (even-higher-speed then no-really-we-mean-it-this-time-high-speed) but > looked

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Stephen Hahn
* John Plocher [2008-02-05 15:00]: > jmp-3) How does this relate to the work being done in IPS, which is also > trying to fix/eliminate postinstall scripts? Image packaging will need something like postrun, but I would expect to see the actual commands delivered as files, rather than via a pi

BIGNUM kernel module [PSARC/2008/080 Self Review]

2008-02-05 Thread Darren J Moffat
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: BIGNUM kernel module 1.2. Name of Document Author/Supplier: Author: Ferenc Rakoczi 1.3 Date of This Document

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Danek Duvall
On Mon, Feb 04, 2008 at 10:41:16AM -0800, John Fischer wrote: > Several software projects ship with programs needed for updating the > project's databases or caches whenever the configuration changes or > new files/data added that invalidate the cache. Examples from the > GNOME wo

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Joseph Kowalski
Stephen Hahn wrote: > I'd also like to separate the tasks that need > to be done every reboot/reconstruction from version-specific > transitions, which I don't believe is done in the current tool. > I'm behind in this discussion (so maybe I'm missing something), but isn't "reboot" somethin

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Nicolas Williams
On Tue, Feb 05, 2008 at 09:12:55AM +0100, Casper.Dik at Sun.COM wrote: > I note that this is a lot worse for people who update biweekly,, > but I also wonder why postrun needs to run at standard priority? > > Some systems will run certain services faster and appear up more quickly > if postrun is

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread casper....@sun.com
>On Tue, Feb 05, 2008 at 09:12:55AM +0100, Casper.Dik at Sun.COM wrote: >> I note that this is a lot worse for people who update biweekly,, >> but I also wonder why postrun needs to run at standard priority? >> >> Some systems will run certain services faster and appear up more quickly >> if post

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Nicolas Williams
On Tue, Feb 05, 2008 at 09:11:26PM +0100, Casper.Dik at Sun.COM wrote: > So what will happen when you lvieupgrade the same partition twice without > even once booting into it? That's easily done and should not cause > any breakage. Well, our class action scripts tend to be written so this just w

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Bart Smaalders
Nicolas Williams wrote: > On Tue, Feb 05, 2008 at 09:11:26PM +0100, Casper.Dik at Sun.COM wrote: >> So what will happen when you lvieupgrade the same partition twice without >> even once booting into it? That's easily done and should not cause >> any breakage. > > Well, our class action scripts

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Bill Sommerfeld
On Tue, 2008-02-05 at 09:12 +0100, Casper.Dik at sun.com wrote: > I find that postrun currently is an abomination (or at least the > consumers are); it runs 10,000s of processes (literally) and takes > a long time; making it public would likely make this worse. The amount of run-on-first-boot wo

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread casper....@sun.com
> >On Tue, 2008-02-05 at 09:12 +0100, Casper.Dik at sun.com wrote: >> I find that postrun currently is an abomination (or at least the >> consumers are); it runs 10,000s of processes (literally) and takes >> a long time; making it public would likely make this worse. > >The amount of run-on-first

PSARC/2008/078 - postrun - delayed execution environment for procedural package scripts

2008-02-05 Thread Nicolas Williams
On Tue, Feb 05, 2008 at 12:51:09PM -0800, Bart Smaalders wrote: > /etc/passwd is one of the examples of something we're handling > at install time w/ IPS; the packaging system has to know how > to manipulate this file in order to install new files owned > by new users correctly. I thought IPS woul

PSARC/2008/069 Additional USB Device Properties

2008-02-05 Thread Joerg Schilling
Artem Kachitchkine wrote: > 1.5 Mbit/s is Low-Speed > 12 Mbit/s is Full-Speed > 480 Mbit/s is Hi-Speed > > Rumor has it, the USB 3.0 mode will be called "SuperSpeed". Then I would guess that USB-4.0 mode will be called "UltraSparc" ;-) J?rg -- EMail:joerg at schily.isdn.cs.tu-berlin.de (home

LSARC/2008/058 - dcraw

2008-02-05 Thread John Fischer
Brian, This fast track was approved today during the LSARC business portion of the meeting. Thanks, John

PSARC/2008/081 - MySQL Python

2008-02-05 Thread John Fischer
: proposal.txt URL: <http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080205/d31306c7/attachment.txt>