Re: [oi-dev] [developer] how to fix support for system_locale in sysidcfg for non global zone installation
DavidHalko davidha...@gmail.com wrote: Sparse zones were probably one of the most innovative features of Solaris 10, providing significant value, and one of out biggest issues with moving off of Solaris 10. If OpenIndiana supported SPARC with Sparse Zones, managed service providers would have a serious time trying to justify not moving to OpenIndiana. There are at least 2 distro's based on SVR4 packaging right now with at least 2 SVR4 package provider. The issue with all Illumos-based distro's is no distro is providing security patches and enough backwards compatibility with Solaris 10. Which distros do you refer to? BTW: illumos does not support SVr4 packaging, SchilliX-ON does. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [developer] how to fix support for system_locale in sysidcfg for non global zone installation
Garrett D'Amore garr...@damore.org wrote: BTW: illumos does not support SVr4 packaging, SchilliX-ON does. That is a false statement. We have support for SVR4 packaging in the illumos gate. The *distros* have not elected to deliver SVR4 packages, and furthermore, we don't have tools *in-tree* to generate SVR4 packages from the IPS manifests, but I submit writing such a tool would be a nearly trivial matter. (In fact, I've written a tool that parses IPS manifests to build a distribution for my company, although it lacks any packaging metadata, as our distro is just an ISO. But I could have just as easily emitted pkginfo and prototype files to generate SVR4 package binaries.) We *do* have most (all?) of the SVR4 tool set in-tree though. So you just verified that your statement is false as you confirmed that Illumos does not create SVr4 packages. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [developer] how to fix support for system_locale in sysidcfg for non global zone installation
Garrett D'Amore garr...@damore.org On May 29, 2012, at 8:15 AM, Joerg Schilling wrote: Garrett D'Amore garr...@damore.org wrote: BTW: illumos does not support SVr4 packaging, SchilliX-ON does. That is a false statement. We have support for SVR4 packaging in the illumos gate. The *distros* have not elected to deliver SVR4 packages, and furthermore, we don't have tools *in-tree* to generate SVR4 packages from the IPS manifests, but I submit writing such a tool would be a nearly trivial matter. (In fact, I've written a tool that parses IPS manifests to build a distribution for my company, although it lacks any packaging metadata, as our distro is just an ISO. But I could have just as easily emitted pkginfo and prototype files to generate SVR4 package binaries.) We *do* have most (all?) of the SVR4 tool set in-tree though. So you just verified that your statement is false as you confirmed that Illumos does not create SVr4 packages. Does not create != does not support. - Garrett Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily --- illumos-developer Archives: https://www.listbox.com/member/archive/182179/=now RSS Feed: https://www.listbox.com/member/archive/rss/182179/21239177-c925e33f Modify Your Subscription: https://www.listbox.com/member/?member_id=21239177id_secret=21239177-4dba8197 Powered by Listbox: http://www.listbox.com ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [developer] how to fix support for system_locale in sysidcfg for non global zone installation
On 26 May 2012, at 17:46, Garrett D'Amore wrote: sysidtool (where this lives) is not part of illumos-gate. Its a part of OpenIndiana. I'm having trouble locating the sources they used for this. I'm not entirely certain the source for it *is* open. Evidently it was part of the installer and was never opened up. I'm a little dismayed about this -- I never realized this to be the case, although admittedly there are distributions which make no use of sysidtool at all. I'm not sure where the sysidcfg code lives (Will have to have a rummage) but I've never liked the way any of it works and I'm sure I'm not alone. We (OpenIndiana) may want to adopt the approach OmniOS took which is to get rid of it and use something much simpler. If the OmniOS approach is sufficiently good enough for most people then we could just import it. I imagine adding compatibility with the sysidcfg file would be pretty trivial if anyone really cared about it. Alasdair ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] [developer] how to fix support for system_locale in sysidcfg for non global zone installation
Sysid was closed. It's replacement is open and in the slim install gate. -- Rich On Saturday, May 26, 2012 at 2:39 PM, Alasdair Lumsden wrote: On 26 May 2012, at 17:46, Garrett D'Amore wrote: sysidtool (where this lives) is not part of illumos-gate. Its a part of OpenIndiana. I'm having trouble locating the sources they used for this. I'm not entirely certain the source for it *is* open. Evidently it was part of the installer and was never opened up. I'm a little dismayed about this -- I never realized this to be the case, although admittedly there are distributions which make no use of sysidtool at all. I'm not sure where the sysidcfg code lives (Will have to have a rummage) but I've never liked the way any of it works and I'm sure I'm not alone. We (OpenIndiana) may want to adopt the approach OmniOS took which is to get rid of it and use something much simpler. If the OmniOS approach is sufficiently good enough for most people then we could just import it. I imagine adding compatibility with the sysidcfg file would be pretty trivial if anyone really cared about it. Alasdair ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
