Re: [OpenIndiana-discuss] pkg and local zones
What speaks against Jim's original approach of using the '-R' option to pkg? I've used this with very reasonable success for quite a while now. That simply works for me. Cheers Stefan Von: Jim Klimov [jimkli...@cos.ru] Gesendet: Mittwoch, 19. Februar 2014 13:41 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] pkg and local zones On 2014-02-19 13:27, Peter Tribble wrote: However, every now and then I need to install some package into all zones. While I can parse the zoneadm list output and find zoneroots and ask pkg(5) to install into the altroots, Would running pkg via zlogin be better? It would be roughly equivalent in terms of command-line scripting, and would only influence the zones running at the moment. Also, such installation would rely on the package servers configured and available in the local zone (if any). Although pkg via zlogin has the benefit of instantly launching some SMF wrappers that the new package might provide, etc. So these are quite different methods... By the way, I saw that SVR4 pkgadd done into a local zone from the GZ (as an altroot) sometimes fails with an error related to the content of $ZONEROOT/etc/zones/index: the zone path there (/) is invalid in the GZ context. I have to script up commenting away this entry (or renaming the file) before pkgadd and returning it after. Would this be considered a bug worthy of mentioning in the issue tracker? (Now that some people seem offensive about others suggesting what people should do, I guess I should ask about every one of my crazy-or-not ideas and RFEs ;) ) it is a bit clunky, so I wonder if I missed some option to just have the pkg(5) program itself install the named package into all available local zones? If not, does this sound like a worthwhile RFE for those who can do and don't know what to do next? :^) When reimplementing zones for Tribblix (where I have both legacy whole/sparse zones and the ipkg-style independent zones) I steered away from the old SVR4 behaviour of controlling packages (after zone installation) from the global zone. It adds horrendous complexity to the packaging system. It's far better to loop over a list of zones and run the packaging commands in each zone than to do it from the global zone. (And that way you can manipulate an arbitrary subset of zones depending on need. Besides, combining simpler commands is the unix way.) You are probably right. Still, at the moment this requires me to type in the commands involved upon every case of a major (home-brewn) package upgrade, or distribute a script to manage the process, which is a bit inconvenient. I wonder if some automation for this belongs in the common illumos-gate (whether as part of pkgadd and pkg(5), or as a separate utility script)? Thanks, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg and local zones
On Thu, Feb 20, 2014 at 8:46 AM, Stefan Müller-Wilken stefan.mueller-wil...@acando.de wrote: What speaks against Jim's original approach of using the '-R' option to pkg? I've used this with very reasonable success for quite a while now. That simply works for me. I would expect it to mostly work most of the time, but it's not quite equivalent, nor is it guaranteed to work correctly under all circumstances, and it's not always safe.(Think, for example, of a situation in which the file system layout in the zone is constructed from mountpoints that don't have the same layout as viewed from the global zone. There was a time when the SVR4 packaging tools used to be able to work out how to put things in the right place for diskless client systems, but that just shows how fragile this could be.) Von: Jim Klimov [jimkli...@cos.ru] Gesendet: Mittwoch, 19. Februar 2014 13:41 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] pkg and local zones On 2014-02-19 13:27, Peter Tribble wrote: However, every now and then I need to install some package into all zones. While I can parse the zoneadm list output and find zoneroots and ask pkg(5) to install into the altroots, Would running pkg via zlogin be better? It would be roughly equivalent in terms of command-line scripting, and would only influence the zones running at the moment. Also, such installation would rely on the package servers configured and available in the local zone (if any). Although pkg via zlogin has the benefit of instantly launching some SMF wrappers that the new package might provide, etc. So these are quite different methods... By the way, I saw that SVR4 pkgadd done into a local zone from the GZ (as an altroot) sometimes fails with an error related to the content of $ZONEROOT/etc/zones/index: the zone path there (/) is invalid in the GZ context. I have to script up commenting away this entry (or renaming the file) before pkgadd and returning it after. Would this be considered a bug worthy of mentioning in the issue tracker? (Now that some people seem offensive about others suggesting what people should do, I guess I should ask about every one of my crazy-or-not ideas and RFEs ;) ) There's probably a good reason why the manpages for pkgadd and pkgrm explicitly tell you not to do this! -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI-151a9
On 19 February 2014 18:18, Tim Mooney tim.moo...@ndsu.edu wrote: In regard to: [OpenIndiana-discuss] OI-151a9, Marc Lobelle said (at 7:11pm...: I see that a new version 0I-151a9 is available, but the version to download at http://openindiana.org/download/ is still 151a8. Where can I find the ISO for 151a9 ? Is it smoother that 151a8 that had many small inconvenients (gnome unusual behaviours etc.). Check the archives for this list. Differences between 151a8 and 151a9 and some of the problems that people have run into have been discussed quite a bit in the past few weeks. My personal experience is that 151a9 is better than 151a8, especially from a JDS perspective, but there are plenty of people that haven't had the same experience. For my part I've found that a9 has problems running KVM with a Windows guest - it will usually boot, but will crash within a couple of minutes. Historically, updating KVM on OI has always been problematic - most versions have been broken in one way or another - so a9 isn't especially bad in that regard. With any luck I'll be able to just keep running the old version of system/qemu/kvm, rather than having to hold back from a9 altogether, but I won't be able to try that out for a few weeks. Other than that, everything appeared to look fine. I don't use any of the graphical packages that some people seem to have problems with though. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg and local zones
- Original Message - From: Peter Tribble peter.trib...@gmail.com To: Discussion list for OpenIndiana openindiana-discuss@openindiana.org Sent: Thursday, February 20, 2014 8:53:53 AM Subject: Re: [OpenIndiana-discuss] pkg and local zones On Thu, Feb 20, 2014 at 8:46 AM, Stefan Müller-Wilken stefan.mueller-wil...@acando.de wrote: What speaks against Jim's original approach of using the '-R' option to pkg? I've used this with very reasonable success for quite a while now. That simply works for me. I would expect it to mostly work most of the time, but it's not quite equivalent, nor is it guaranteed to work correctly under all circumstances, and it's not always safe.(Think, for example, of a situation in which the file system layout in the zone is constructed from mountpoints that don't have the same layout as viewed from the global zone. There was a time when the SVR4 packaging tools used to be able to work out how to put things in the right place for diskless client systems, but that just shows how fragile this could be.) Gotta second Peter's caution here. This is precisely the kind of inconsistency we've run into when using the -R option to pkg. I'm quite sure I _still_ don't understand it (and wait patiently for one of you to write the 'Definitive Guide' !! ) Meanwhile: Magical incantations, glue and duct tape. Lou Picciano Von: Jim Klimov [jimkli...@cos.ru] Gesendet: Mittwoch, 19. Februar 2014 13:41 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] pkg and local zones On 2014-02-19 13:27, Peter Tribble wrote: However, every now and then I need to install some package into all zones. While I can parse the zoneadm list output and find zoneroots and ask pkg(5) to install into the altroots, Would running pkg via zlogin be better? It would be roughly equivalent in terms of command-line scripting, and would only influence the zones running at the moment. Also, such installation would rely on the package servers configured and available in the local zone (if any). Although pkg via zlogin has the benefit of instantly launching some SMF wrappers that the new package might provide, etc. So these are quite different methods... By the way, I saw that SVR4 pkgadd done into a local zone from the GZ (as an altroot) sometimes fails with an error related to the content of $ZONEROOT/etc/zones/index: the zone path there (/) is invalid in the GZ context. I have to script up commenting away this entry (or renaming the file) before pkgadd and returning it after. Would this be considered a bug worthy of mentioning in the issue tracker? (Now that some people seem offensive about others suggesting what people should do, I guess I should ask about every one of my crazy-or-not ideas and RFEs ;) ) There's probably a good reason why the manpages for pkgadd and pkgrm explicitly tell you not to do this! -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
Seems like there is something with GNOME config files in user home folder, indeed. After touching GNOME so that it saves some config, the problem disappeared. (I have removed the Volume applet from the upper toolbar in production server, and after that upgrade went without problems; Seems like any change will do, Volume applet is not the culprit. Removed the whole bottom taskbar in vbox installation, and after that I was unable to reproduce the problem) Laurent Blume wrote: chances are it's something messed up in the ~/.gnome*/ directories. The easiest way to fix it is to remove them. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI-151a9
As far as I know, the 151a9 release has no ISO. It only may be upgraded from earlier release. Marc Lobelle wrote: I see that a new version 0I-151a9 is available, but the version to download athttp://openindiana.org/download/ is still 151a8. Where can I find the ISO for 151a9 ? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
Are you saying that after updating to a new OI151a9 BE, you removed the volume applet from the toolbar while logged in under an OI151a7 BE, and then you booted to OI151a9. Whereupon everything worked perfectly after logging in under OI151a9??? On 2014-02-20 19:32, Dmitry Kozhinov wrote: Seems like there is something with GNOME config files in user home folder, indeed. After touching GNOME so that it saves some config, the problem disappeared. (I have removed the Volume applet from the upper toolbar in production server, and after that upgrade went without problems; Seems like any change will do, Volume applet is not the culprit. Removed the whole bottom taskbar in vbox installation, and after that I was unable to reproduce the problem) Laurent Blume wrote: chances are it's something messed up in the ~/.gnome*/ directories. The easiest way to fix it is to remove them. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
Not exactly. I have removed the volume applet in 151a7 even before upgrading to 191a9. Not sure that this is why the upgrade went surprisingly well (on a production server). However when i tried to reproduce the problem in virtualbox, seemed like the following helped: - Updated to 151a9; Reproduced the problem somehow (reinstalled gvfs?); - Booted into 151a7 BE and deleted .gnome* folders in my home folder; - Booted into 151a9 successfully. Are you saying that after updating to a new OI151a9 BE, you removed the volume applet from the toolbar while logged in under an OI151a7 BE, and then you booted to OI151a9. Whereupon everything worked perfectly after logging in under OI151a9??? On 2014-02-20 19:32, Dmitry Kozhinov wrote: / Seems like there is something with GNOME config files in user home // folder, indeed. // After touching GNOME so that it saves some config, the problem // disappeared. // // (I have removed the Volume applet from the upper toolbar in production // server, and after that upgrade went without problems; Seems like any // change will do, Volume applet is not the culprit. // Removed the whole bottom taskbar in vbox installation, and after that // I was unable to reproduce the problem) // // Laurent Blume wrote: // chances are it's something messed up in the ~/.gnome*/ // directories. The easiest way to fix it is to remove them./ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
Hi Milan, Is this considered a next release preview? pkg set-publisher-ghttp://pkg.opensolaris.cz:1/ --search-before=openindiana.org jds.openindiana.org ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
Hi, On pá, 2014-02-21 at 02:12 +0600, Dmitry Kozhinov wrote: Hi Milan, Is this considered a next release preview? pkg set-publisher-ghttp://pkg.opensolaris.cz:1/ --search-before=openindiana.org jds.openindiana.org jds.o.o is testing repo of bits which will be included in the next OI release (a10 currently). I hope. Best regards, Milan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI-151a9
The ISO or USB build can be create from the archived oi_151a9 repository tarball. With some work, you can update using the OI-JDS a10beta packages from pkg.opensolaris.cz and add other software or device drivers. ~ Ken Mays Sent from Yahoo Mail on Android ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
