[zones-discuss] Error on zoneadm attach -u when going from b132 to b133

I upgraded my system from b132 to b133 this weekend and I got error messages when I ran attach -u to upgrade my zones. The second run of the install of updated packages fails. In the log I find: $ pfexec cat /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:50 CET] Log File: /var/

Re: [zones-discuss] Error on zoneadm attach -u when going from b132 to b133

On Mon, 22 Feb 2010 11:49:46 +0100, Paul van der Zwan wrote: > I upgraded my system from b132 to b133 this weekend and I got error messages > when I ran attach -u to upgrade my zones. > The second run of the install of updated packages fails. > In the log I find: > > $ pfexec cat /var/tmp/dns.a

Re: [zones-discuss] Error on zoneadm attach -u when going from b132 to b133

On 22 feb 2010, at 12:02, Frank Batschulat (Home) wrote: > On Mon, 22 Feb 2010 11:49:46 +0100, Paul van der Zwan > wrote: > >> I upgraded my system from b132 to b133 this weekend and I got error messages >> when I ran attach -u to upgrade my zones. >> The second run of the install of updated

Re: [zones-discuss] [osol-discuss] Error on zoneadm attach -u when going from b132 to b133

On 22 feb 2010, at 12:26, Alan Burlison wrote: > Paul van der Zwan wrote: > >> If I run attach -u a second time it attaches without doing anything, or >> giving an error. >> Are my zones OK or are they partly upgraded ? > > Sounds like an issue mentioned in the release notes: > > http://mail.

Re: [zones-discuss] [osol-discuss] Error on zoneadm attach -u when going from b132 to b133

you're lucky. It didn't work for me. I got caught in a catch 22 i'd do attach -u and it would fail, then i'd do attach (without -u) and it would tell me to do attach -u On Mon, Feb 22, 2010 at 8:51 AM, Paul van der Zwan wrote: > > On 22 feb 2010, at 12:26, Alan Burlison wrote: > > > Paul van de

[zones-discuss] minor code review for 6890415 & 6880288 (zoneadm.c, native brand)

May I have 2 code reviewers for the following minor changes for: PSARC/2010/008 Remove zoneadm install sub-option "-x nodataset" 6880288 retire zoneadm install -x nodataset option 6890415 zoneadm install fails but returns 0 http://cr.opensolaris.org/~batschul/nodataset/ thanks! frankB Notes: f

Re: [zones-discuss] minor code review for 6890415 & 6880288 (zoneadm.c, native brand)

On 02/22/10 09:40, Frank Batschulat (Home) wrote: May I have 2 code reviewers for the following minor changes for: PSARC/2010/008 Remove zoneadm install sub-option "-x nodataset" 6880288 retire zoneadm install -x nodataset option 6890415 zoneadm install fails but returns 0 http://cr.opensolaris

Re: [zones-discuss] minor code review for 6890415 & 6880288 (zoneadm.c, native brand)

On Mon 22 Feb 2010 at 10:52AM, Jerry Jelinek wrote: > On 02/22/10 09:40, Frank Batschulat (Home) wrote: > >May I have 2 code reviewers for the following minor changes for: > > > >PSARC/2010/008 Remove zoneadm install sub-option "-x nodataset" > >6880288 retire zoneadm install -x nodataset option >

Re: [zones-discuss] renaming zonepath

On 02/21/10 08:33 AM, Anil wrote: Never mind. I will not do this rename. It's not worth the trouble. r...@vps1:~# zoneadm -z note move /zones/note Moving across file systems; copying zonepath /zones/bugs...sh[1]: cd: /zones/bugs: [No such file or directory] zoneadm: zone 'note': 'copy' failed w

[zones-discuss] snv_132: rlogin, rsh, telnet in non-global zones

What is the correct way to enable rlogin, rsh and/or telnet in a non-global zone on an snv_132-based system? These services appear to be absent in non-global zones: # zlogin myzone # zonename myzone # svccfg list | grep network/shell # svccfg list | grep network/login # svccfg list | grep netwo

Re: [zones-discuss] snv_132: rlogin, rsh, telnet in non-global zones

Just to clarify, this question is specifically about ipkg zones (i.e., on an osol-b132 host). -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org