Jignesh K. Shah wrote: > > I guess that the option works for SXDE which I guess is targetted at > laptop users.
I'll add my usual reminder that what we (OpenSolaris) are integrating into here isn't SXDE, it's OpenSolaris and thus all the distros built out of it. The SXDE builds specifically might be targeted at the individual developer, but the technology needs to be suitable for use cases ranging from the laptop to the production servers. First it's good to deliver the building blocks which include (maybe not complete list) - Have the package deliver the runtime user for the daemon (Actually you can't do this yet, but see and track http://defect.opensolaris.org/bz/show_bug.cgi?id=217 for progress.) (I see postgres does deliver its user "postgres" already so that's done; later you'll want to change it so it is delivered by the package itself.) - Deliver a suitable set of privilege that can be assigned to users so they can use the component without being root. I see postgres delivers "Postgres Administration" so it appears that's also covered. One consideration to think about is whether it makes sense to have one privilege for it or break it down to separate ones based on functional lines (like backup operator vs. administrator etc) and possibly have an umbrella containing all of them. Might not apply to your case, just something to consider in general. Then on top of these you could deliver GUI sugar coating targeted at the individual laptop developer, such as Ludo's script, which assigns the desired privilege(s) to the chosen user(s). Those administering production systems probably won't use the script but it is ok since they can assign the privileges manually instead. Everyone can be happy. Note that MySQL integration is missing the delivery of both the user and the privileges so it's not the best role model quite yet (there are bugs in the works to fix those weaknesses). It only appears simple via Ludo's developer menu script because the script goes and fixes those problems but that only helps the developer type of user who wants to run that script. There isn't good support yet for the production system kind of user so they have to do more manual steps than they should to get things working (there was a thread here just earlier on that). Looks like Postgres has the core building blocks covered better, now you could just deliver a script (such as James suggested) hooked up to some menu that puts the pieces together for the laptop kind of user. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
