StarOffice 8 install Solarisx86 with zones

I have tried several times to install startoffice on solaris 10 u1 x86 box with 4 zones. It would fail after several minutes complaining it couldn't get an admin lock on the zones. Several reboots and clearing the zones /tmp folder didn't make a difference.
I gave up on the install script and manually installed the packages using the -G option to just install it in the global zone.
I can start programs now using /opt/staroffice/program/scalc ..., they seem to work.
How to I get the links and document associations to point to staroffice 8 instead of staroffice 7?

Just run the .sh file and when the setup starts, klick cancel.
Then goto /var/tmp/unpack_staroffice/RPMS
Remove the RPMs you dont want to install and do
rpm -Uvh nodeps force staroffice-*.rpm
That's it you can run staroffice8

Similar Messages

Solaris Express Zone install error with SUNWiiimr and SUNWcnetr

Hi all,
I got these errors when installing a new zone on a Solaris Express 1/08 (5.11) on a x64 box:
Installation of these packages generated errors: SUNWiiimr
Installation of these packages generated warnings: SUNWcnetr
The zone creation log shows:
*** package -SUNWiiimr- failed to install with fatal errors:
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postin stall: /export/zones/newzone/root/lib/postrun: not found
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postinstall: /export/zones/newzone/root/lib/postrun: not found
pkgadd: ERROR: postinstall script did not complete successfully
Installation of -SUNWiiimr- on zone -newzone- failed.
*** package -SUNWcnetr- installed with warnings:
pkgadd: ERROR: unable to create package object -/export/zones/newzone/root/etc/dladm-.
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/aggregation.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/linkprop.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/secobj.conf- failed
owner name -dladm- not found in passwd table(s)
Installation of -SUNWcnetr- on zone -newzone- partially failed.
-newzone- was configured to be a whole root zone. Are there any ways to solve these installation errors?
Thanks in advance.

This problem seems some strange - this time with Solaris 10u4, from 10 containers installed on a brand new X2200 (2x cpu) only one do not output those errors, but just this one cannot install the dsee or proxy. This time the errors were from:
Installation of <SUNWxwplr> on zone <dsee-proxy> partially failed.
Installation of <SUNWdtdmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWmconr> on zone <dsee-proxy> partially failed.
Installation of <SUNWrmwbr> on zone <dsee-proxy> partially failed.
Installation of <SUNWlvmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWzebrar> on zone <dsee-proxy> partially failed.
So the machine was, too, just installed. After several hours, anoter atempt to install a zone, this time just this one, returned no errors - and the dsee installed without any complains. All configurations were for whole root zones. Used was Solaris 10u4 with the most recent patch cluster applied.

Problem with zone installation on solaris 08/07

Hello :)
I need some help
I install solaris 10 08/07 on my x2100 M2.Everything is ok.
Then I try to install non-global zone named web-zone with the following commands:
# mkdir /export/web-zone
# chmod 700 /export/web-zone
# zonecfg -z web-zone
web-zone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:web-zone> create
zonecfg:web-zone> set autoboot=true
zonecfg:web-zone> set zonepath=/export/web-zone
zonecfg:web-zone> add net
zonecfg:web-zone:net> set address=192.168.0.3
zonecfg:web-zone:net> set physical=bge1
zonecfg:web-zone:net> end
zonecfg:web-zone> info
zonepath: /export/web-zone
autoboot: true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address: 192.168.0.3
physical: bge1
zonecfg:web-zone> verify
zonecfg:web-zone> commit
zonecfg:web-zone> exit
# zoneadm -z web-zone verify
# zoneadm -z web-zone install
# zoneadm list -cv
# zoneadm -z web-zone boot
When I zlogin into zone configuration stack with:
Fatal internal error: prompt_error called before prompt_open!
The IP address previously set on the network interface
is no longer available. The system state is corrupted. System identification
can no longer continue.
Press Return to continue
And that�s it :)
On interface bge1 I have 2 ip addresses, one for management processor (192.168.0.254) and one for global zone (192.168.0.2)
The output from ifconfig �a is :
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
zone web-zone
inet 127.0.0.1 netmask ff000000
bge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255
ether 0:1b:24:5:4f:6f
bge1:1: flags=4001000842<BROADCAST,RUNNING,MULTICAST,IPv4,DUPLICATE> mtu 1500 index 2
zone web-zone
inet 192.168.0.3 netmask ffffff00 broadcast 192.168.0.255
Any Ideas ?? :)
Thaks
pp Sory for my baad english :)

Hi
Thank you for replay
This is happened exactly when I zlogin for first time to complete installation.
The installation procedure flow flawless.I set terminal type 13 (dt terminal) and everything is OK, but when I try to setup hostname I�ve got this error.
I try this with 3 different zones on this machine with same result
I have old x86 machines with solaris 11/06 zones installed , everything works fine (1 year uptime)
This is not the first zone in my life :)
Best Regards
DJ JAM

Deferred patching broken for machines with zones

For a while I've noticed that Ive had trouble patching a couple of machines.
I've managed to determine the significant characteristic identifying them.
All the machines with a non global zone have the problem.
To confirm, I added a test zone to a machine that was fine. And it immediately it developed the problem.
Anyway, the symptom is that no deferred patches will install.
So patches delayed by a "smpatch update" till the reboot fail to install.
The sunucLog displays the following error
Sep 17 10:30:05 webdb1 123186-03 [notice] Status Install Begin 123186-03
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Validating patches...
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Loading patches installed on the system...
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Loading patches requested to install.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Checking patches that you specified for installation.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] svcadm: Instance "svc:/system/filesystem/local:default" has been disabled by another entity.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] ERROR: Enabling filesystem/local service failed.
Sep 17 10:30:05 webdb1 123186-03 [ALERT] Status Install End 123186-03 Install Update installation failed
Anyone got any workarounds for this problem.
Is it a known issue.
Or should I log a support request.

Any progress on this? Its been 2 months. And sun has managed to put out an entire new update to Solaris.
And a 119254-59 has been released. But neither includes a fix for this issue as far as I can tell...
Its now basically impossible to patch machines with zones up to the latest kernel 137137-09 since that has a dependency on 119254-58.
And machines with zones can't be patched if a version higher than 119254-53 is installed....

Cloning Solaris 10 with zones

What is the best method to use when cloning a Solaris machine with zones, to ensure all software is included and can be easily installed
on new hardware?
Thank you!

If you use UFS, then ufsdump/ufsrestore
If you use ZFS, then zfs send/zfs receive
But, if you are using hardware or software RAID, you can also try to move one disk to an another machine.
You can see with these simple examples, that you have several methods and it depends how you configured your machine, Solaris and the zones. And finally, it depends too what is the source machine and what is the target machine, and how they are configured.

Live Upgrade with Zones - still not working ?

Hi Guys,
I'm trying to do LiveUpdate from Solaris update 3 to update 4 with non-global zone installed. It's driving me crazy now.
I did everything as described in documentation, installed SUNWlucfg and supposedly updated SUNWluu and SUNWlur (supposedly because they are exactly the same as were in update 3) both from packages and with script from update 4 DVD, installed all patches mentioned in 72099, but lucreate process still complains about missing patches and I've checked if they're installed five times. They are. It doesn't even allow to create second BE. Once I detached Zone - everything went smooth, but I had an impression that Live Upgrade with Zones will work in Update 4.
It did create second BE before SUNWlucfg was installed, but failed on update stage with exactly the same message - install patches according to 72099. After installation of SUNWlucfg Live Upgrade process fails instantly, that's a real progress, must admit.
Is it still "mission impossible" to Live Upgrade with non-global zones installed ? Or am I missed something ?
Any ideas or success stories are greatly appreciated. Thanks.

I upgraded from u3 to u5.
The upgrade went fine, the zones boot up but there are problems.
sshd doesn't work
svsc -vx prints out this.
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Fri Apr 18 09:54:33 2008
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: man -M /usr/share/man -s 1M gssd
Impact: 8 dependent services are not running:
svc:/network/nfs/client:default
svc:/system/filesystem/autofs:default
svc:/system/system-log:default
svc:/milestone/multi-user:default
svc:/system/webconsole:console
svc:/milestone/multi-user-server:default
svc:/network/smtp:sendmail
svc:/network/ssh:default
svc:/network/inetd:default (inetd)
State: maintenance since Fri Apr 18 09:54:41 2008
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/share/man -s 1M inetd
See: /var/svc/log/network-inetd:default.log
Impact: This service is not running.
It seems as thought the container is not upgraded.
more /etc/release in the container shows this
Solaris 10 11/06 s10s_u3wos_10 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 14 November 2006
How do I get it to fix the inetd service?

Kernel Patching with zones

I have a T2000 installed with the Solaris 10 1/06 release with several zones created on it. 4 zones are "sparse" root, and one (zone-5) is a "whole root" zone.
In order to apply and certify (internally) the latest sendmail patch, Solaris 10 needs a later kernel patch than I had installed (this is a subject for another discussion...). So I downloaded the latest patch cluster (4/6 Recommended cluster) to apply it.
I shut down the non-global zones, and took the machine to single user mode, and installed the cluster. It seemed to go in fine, except for the following error:
Zone zone-5
Rejected patches:
122856-01
Patches that passed the dependency check:
None.
Fatal failure occurred - impossible to install any patches.
zone-5: For patch 122856-01, required patch 118822-30 does not exist.
Fatal failure occurred - impossible to install any patches.Now, 118822-30 is a kernel patch series that is prerequisite for the latest kernel patch (118833-03). Zone-5 is my only whole-root zone. I then looked at the patch cluster log, and discovered that a handful of patches (including 118822-30) had also failed:
titan15n> grep failed /var/sadm/install_data/Solaris_10_Recommended_Patch_Cluster_log
Pkgadd failed. See /var/tmp/119254-19.log.6615 for details
Pkgadd failed. See /var/tmp/118712-09.log.9307 for details
Pkgadd failed. See /var/tmp/119578-18.log.15160 for details
Pkgadd failed. See /var/tmp/121308-03.log.18339 for details
Pkgadd failed. See /var/tmp/119689-07.log.22068 for details
Pkgadd failed. See /var/tmp/118822-30.log.9404 for details
Pkgadd failed. See /var/tmp/119059-11.log.29911 for details
Pkgadd failed. See /var/tmp/119596-03.log.4724 for details
Pkgadd failed. See /var/tmp/119985-02.log.8349 for details
Pkgadd failed. See /var/tmp/122032-02.log.13334 for details
Pkgadd failed. See /var/tmp/118918-14.log.27743 for detailsLooking at any of these logs (in the non-global zone-5's /var/tmp directory shows failures like the following snippet:
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/cheetahregs.h6HaG8w>: (30) Read-only file sy
stem
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/clock.h7HaG8w>: (30) Read-only file system
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/dvma.h8HaG8w>: (30) Read-only file systemQuestion(s):
Why would there be read-only file systems where tmp files are getting written? Possibly a timing issue?
Is there a "best practice" on applying patch clusters, and specifically, the kernel patch? Did I make a mistake in taking the zones down first? It seems like the zones were being booted up as the patches were getting applied, but I may be misinterpreting the output.
Even though the patches failed to apply to zone-5, the uname -a output in the zone show the latest kernel patch, but does NOT show 118822-30 (118822-25 is what showrev -p in the non-global zone-5 shows -- which is the level I was at before attempting to patch).
Any solutions?
Thanks.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
CHK include/linux/version.h

Anyway to force patch install on a zone that's already installed in global?

Global zone has 142909-17 installed:
<pre>user@global:~$ showrev -p | grep "Patch: 142909-17"
Patch: 142909-17 Obsoletes: 118814-01, 120038-01, 120816-01, 121128-01, 121394-03, 122085-01, 123194-01, 123271-01, 123332-02, 123334-05, 125022-01, 125108-02, 125174-02, 125200-01, 125201-01, 125808-01, 125896-03, 126308-01, 126428-01, 127723-01, 127759-03, 127762-01, 127882-03, 128032-01, 128324-02, 128346-01, 136891-02, 137017-03, 137028-01, 137123-03, 137133-01, 137291-01, 138046-02, 138081-01, 138098-01, 138112-01, 138116-01, 138118-01, 138120-01, 138157-01, 138169-01, 138223-03, 138263-03, 138283-05, 138318-03, 138324-03, 138375-01, 138381-01, 138411-01, 138627-07, 138644-01, 138764-02, 138848-02, 138858-01, 138870-01, 138872-02, 138874-05, 139390-01, 139468-01, 139487-01, 139503-01, 139504-01, 139508-01, 139509-02, 139514-01, 139553-01, 139568-01, 139935-01, 139941-01, 139943-01, 139945-03, 139946-01, 139948-01, 139949-01, 139958-01, 139970-01, 139971-01, 139975-03, 139983-04, 140003-03, 140078-01, 140144-01, 140146-01, 140151-02, 140157-03, 140165-01, 140167-01, 140169-01, 140175-01, 140192-01, 140386-04, 140391-03, 140395-01, 140397-11, 140401-01, 140413-01, 140557-01, 140559-01, 140562-02, 140681-02, 140788-01, 140917-02, 141012-01, 141022-02, 141026-14, 141030-10, 141034-02, 141054-01, 141536-01, 141542-01, 141544-01, 141550-02, 141562-02, 141723-02, 141740-01, 141773-01, 141780-01, 141899-03, 141906-01, 141914-02, 141922-02, 142005-01, 142055-03, 142236-02, 142242-05, 142245-02, 142247-01, 142249-01, 142257-05, 142259-07, 142263-01, 142290-01, 142330-01, 142346-02, 142390-03, 142436-08, 142481-01, 142528-01, 142539-01, 142541-01, 142675-01, 142900-15, 143051-01, 143052-02, 143054-01, 143117-01, 143119-02, 143120-03, 143122-02, 143125-02, 143128-05, 143131-08, 143135-03, 143137-04, 143350-05, 143352-01, 143354-03, 143356-01, 143357-05, 143359-02, 143360-01, 143515-01, 143519-01, 143521-02, 143523-04, 143528-01, 143556-04, 143558-01, 143565-01, 143569-04, 143574-01, 143576-03, 143583-02, 143585-01, 143586-02, 143590-01, 143595-01, 143597-02, 143603-01, 143605-01, 143607-01, 143611-01, 143613-01, 143623-01, 143895-01, 143897-03, 143899-01, 143903-01, 143905-01, 143907-01, 143909-06, 143911-01, 143920-02, 143927-02, 143933-01, 143935-01, 143943-01, 144015-01, 144017-01, 144019-01, 144021-01, 144023-01, 144043-01, 144045-02, 144049-01, 144051-03, 144056-01, 144110-01, 144182-01, 144258-01, 144369-01, 144373-01, 144389-01, 144453-01, 144494-01, 144511-01, 144624-01, 144761-01, 145024-01, 145049-01, 145051-01, 145102-01, 145103-01 Requires: 118731-01, 118833-36, 118918-24, 119042-09, 119578-30, 120011-14, 120900-04, 121133-02, 121901-01, 126540-02, 126897-02, 127127-11, 127755-01, 137137-09, 139555-08, 141444-09, 142911-01, 142933-02 Incompatibles: Packages: SUNWixgb, SUNWcsr, SUNWdmgtu, SUNW1394, SUNWcsl, SUNWdtrc, SUNWefcl, SUNWcpc, SUNWcti2, SUNWckr, SUNWfmdr, SUNWcsu, SUNWdrcr, SUNWftdur, SUNWcpcu, FJSVmdb, SUNWarcr, FJSVmdbr, SUNWhea, SUNWib, SUNWkvm, SUNWdcar, SUNWcslr, SUNWfmd, SUNWhermon, SUNWaccu, SUNWfruip, SUNWmdb, FJSVcpcu, SUNWesu, SUNWluxl, SUNWipoib, SUNWdhcsu, FJSVpiclu, SUNWmdbr, FJSVfmd, SUNWcsd, SUNWmdr, SUNWefc, SUNWcpr, FJSVhea, SUNWippcore, SUNWcry, SUNWarc, SUNWcakr, SUNWdrr, SUNWintgige
user@global:~$ more /etc/release
Solaris 10 8/07 s10s_u4wos_12b SPARC
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
user@global:~$</pre>
Sparse-root zone does not show it being installed:
<pre>user@global:~$ sudo zlogin zone1 showrev -p | grep "Patch: 142909-17"
user@global:~$ sudo zlogin zone1 cat /etc/release
Solaris 10 8/07 s10s_u4wos_12b SPARC
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
user@global:~$</pre>
Not sure how it happened. Original admin is no longer with the company. My guess it was installed with a -G in the global zone? Is there some magic that will apply the patch to the zone w/o backing out and reinstall in global zone? The install of 144500-11 is bombing out because zone does not think patch is installed:
<pre>Patches that passed the dependency check:
144500-19
Fatal failure occurred - impossible to install any patches.
SUNWlu-zone1: For patch 144500-19, required patch 142909-17 does not exist.
SUNWlu-zone2: For patch 144500-19, required patch 142909-17 does not exist.
SUNWlu-zone3: For patch 144500-19, required patch 142909-17 does not exist.
SUNWlu-zone4: For patch 144500-19, required patch 142909-17 does not exist.
Fatal failure occurred - impossible to install any patches.
Failed (exit code 1)</pre>
Not real interested in installing 144500-19 with -G but if that's the last resort then...

Patch can be installed in local zone individually. But, 142909-% is kernel patch which you might have read in the read-me. Analyze before you take any action. Also, there are some special install instructions at the end of the read me of 142909, check it.

High available address with zone cluster

Hi,
I run through Sun documentation, and didn't fully understand, how should I ensure the high availability of an IP address "inside" Solaris zone cluster.
I installed a new zone cluster with the following configuration:
zonename: proxy
zonepath: /proxy_zone
autoboot: true
brand: cluster
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
enable_priv_net: true
net:
     address: 193.219.80.85
     physical: auto
sysid:
     root_password: ********************
     name_service: NONE
     nfs4_domain: dynamic
     security_policy: NONE
     system_locale: C
     terminal: ansi
node:
     physical-host: cluster1
     hostname: proxy_cl1
     net:
          address: 193.219.80.92/27
          physical: vnet0
          defrouter: 193.219.80.65
node:
     physical-host: cluster2
     hostname: proxy_cl2
     net:
          address: 193.219.80.94/27
          physical: vnet0
          defrouter: 193.219.80.65
clzc:proxy>
clzc:proxy>
After installation, I've tried to configure a new resource group with a logicalhostname resource in it inside the zone cluster:
/usr/cluster/bin/clresourcegroup create -n proxy_cl1,proxy_cl2 sharedip
and got the following error:
clresourcegroup: (C145848) proxy_cl1: Invalid node
Is there any other way to make an IP address inside a "proxy" zone cluster high available?
Thanks.

I have rapid spanning tree enabled on both switches.
The problem is that I have to disabled spanning tree on the link connecting the two switches together. If not the inter switch link will be blocked the moment I fail over the network bond because it probably thinks there is a redundant path. Is there some other way to prevent the inter switch link from blocking?
If not, how can I disable spanning tree on the aggregated link? So far I only managed to do this on a normal link, but cannot do it on an aggregated link.

Firefox 5 will not start with Zone Alarm Ver 10.0.240.000

Firefox updated yesterday and now it will no longer start, it looks like the probem may be with Zone Alarm Forcefield. Does anyone have any ideas how to get Firefox 5 to tun under Zone Alarm Extreme Security? Thanks

Hi,
I'm running Win7 x64 with ZoneAlarm Extreme Security 10.0.241.000
I had the same problem with Firefox 4. After turning off ForceField Toolbar, it started working fine.
Then I updated to Firefox 5 and it wouldn't start, instead it was showing an error message from ZA...
I searched mozilla support and followed the instructions here: http://kb.mozillazine.org/Browser_will_not_start_up
on the topic"Firefox does not start after updating with ZoneAlarm ForceField enabled".
The correct instructions for this ZA version should be: "'''Internet '''-> '''Web Security '''-> '''Settings''', and click '''Clear Virtual Data'''"
After that I could open Firefox again! Then I realized it was still version 4...
I installed the update, and everything went smooth. Checked again if Forcefield toolbar was inactive (it was) and opened a few pages, closed Firefox and opened again. After a while it wouldn't open...
AGAIN the "Clear Virtual Data" did the trick...
This time I clicked on '''Settings '''(next to "Clear Virtual Data") -> '''Advanced Settings''', and turned off "'''Enable Virtualization'''".
Until ZA get a fix for this, either we turn it off or clear virtual data every few moves...
Working fine.
Best regards

Upgrading Solaris with Zones

I have just found the following statement in the Solaris 10 Install Guide, section "Upgrade Limitations":
"If you have configured Solaris Zones on your system, you are not able to upgrade until you have unconfigured and uninstalled your non-global zones"
I have a serious problem with this limitation. It seems to be impossible to upgrade a Solaris 10 system with zones configured. I would have to shut down and uninstall my zones and applications to upgrade the OS.
There's not even a way to move the affected zones to another system to keep the application running if the host with the global zone needs maintenance due to OS upgrade, HW maintenance or if simply has too many zones configured on it and all resources are exhausted.
With these limitations I don't see much reasonable use for zones. In particular, once a zone and an application is set up on a physical box with a particular OS release I am stuck with it for all times.
How are you going to solve these problems. And when? What are zones good for in the current implementation? I am still waiting for convincing arguments to use zones ...

I guess I'll state for the record, lest anyone should be confused by my last post, that LiveUpgrade doesn't allow upgrade anymore. I guess I got away with it before LU was upgraded to restrict such activity.
ERROR: Unable to upgrade boot environment <Solaris10-B58>.
INFORMATION: Boot environment <Solaris10-B58> has one or more non-global
zones installed. This version of Live Upgrade cannot upgrade a boot
Guess I'd better figure out how to backup my zones so I clean remove them. A simple tar will probly do the trick for now.
benr.

IP/Interface setup with zones

Moin!
Am trying to configure my first server with zones and am new to it so please forgive me if I aske dumb questions.
I wanted to use zones to protect my machine setup from possible intrusions from the internet. So I wanted to create a global zone that is only connected to a backend network (10.x.x.x.) over say hme0 and then a zone that has access to hme1 which is connected to public internet.
However as it is only possible to configure routes from the global zone I have to give that interface (hme1) an address in the global zone also as I have to configure different default routes. This however exposes the global zone to the internet.
Is there anything I missed that makes it possible to achive this (without fireing up ipfilter)?
TIA and so long
-Ralf Weber

You should be able to add the default routes with configuring a global zone address on hme1. However, you need to boot the zone before you install the routes. For security, you should also:
- enable strict destination multihoming:
# ndd -set /dev/ip ip_strict_dst_multihoming 1- add reject routes to block the zone from accessing the global zone (see older posts on this forum)
Blaise

I am trying to install Appletv with an iPad2 and cannot get Homesharing to work

I am trying to install Appletv with an iPad2 and cannot get Homesharing to work

Homesharing only works with computers. If your using an ipad you want to use Airplay instead.
http://support.apple.com/kb/ht4437?viewlocale=de_de&locale=de_de

If I do a clean install on my MacBook Pro will I be able to re-install apps (FCP, Aperture, MS Office etc.) from a Time Machine backup, or will I need the original install DVDs with authorization codes?

I have two questions...
1) If I do a clean install on my MacBook Pro will I be able to re-install apps (FCP, Aperture, MS Office etc.) from a Time Machine backup, or will I need the original install DVDs with authorization codes? (because I don't have them)
2) Has anyone ever seen anything like this before on their computers?
The Apple Genius' were stumped by my laptop issues and said they'd never seen anything like it before and recommended I did a clean install. Below you can see my trash bin, and if you look at the "Empty" button it reads "N201" and then there's the "N39" to the left of it. You can also see these numbers over by the folder area--"SD5, SD6, SD7." But that's not all...
When I right click on items I see the numbers again. Instead of "Open with" I get "N152" and there's an "N35" and "LB1" towards the bottom.
I have no idea what's going on so I'm just going to do a clean install on my machine but I don't want to lose my apps. I don't have the original install DVDs for them anymore. If you have any suggestions please let me know. Thanks!

You don't lose them. You can always redownload them from the app store after you log back in with your Apple ID.
"Buy, download, and even redownload.
You can install apps on every Mac you use and even download them again. This is especially convenient when you buy a new Mac and want to load it with apps you already own."

MAC PRO (Early 2008) RAID CARD ISSUE - SYSTEM FREEZEHello (hopefully someone can shed some light on my issue) I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i m

Hello (hopefully someone can shed some light on my issue)
I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i made a regular drive)
a while ago i had to replace the RAID card battery, so i did this, over a year later the same thing happened again, but as previous just left it and the system seemed fine for ages, until last night i was working in PHOTOSHOP and everything just froze and the screen kind of appeared GREEN, could not do a single thing. So restarted the mac, this time grey screen for ages and a message appeared, (macs version of blue screen) (see attached).
I restarted the machine and this time a flashing question mark folder!
could not do a thing.
so i found my copy of snow leopard and got the computer to run this and at least launch the DISK UTILITY and (Interestingly in the drop down menu RAID UTILITY was also in the menu) but it did not matter which utility i used the (RAID or DISK) neither could see any of drives, just the dvd drive.
so looked around on you tube and various forums and discovered if i take out the RAID CARD and re-plug the main lead from the RAID card back in to the LOGIC BOARD I would be reverting the MAC to a normal regular non-RAID computer.
After performing this HARDWARE task and inserting all three HDD, and running the DISK utility from the drop down menu via the SNOW LEOPARD disc.
(interestingly since the RAID card had been removed the RAID UTILITY from the drop down menu no longer appeared). running disk utility I can now only see the regular (spare) hdd and DVD Drive, but the two RAID HDD , again, still do not show up DISK UTILITY?
O.K. so i could chuck out the RAID card (AND RAID HDD) and just go with a regular set-up, and run a back restore from Time Machine on a NEW hdd purchased.
but what is wrong with the RAID, is the card at fault or are both HDD used for the RAID knackered? can i perform any tests, to see whats what?
thanks for your help in advanced.

hello people, the issue was in fact the GRAPHICS card nothing to do with the HDD or RAID system ( although this did cause issues with the RAID system it basically lost its way) below is my replay to another similar problem some one else had!
working in photoshop and then everything stopped working and the lot froze! only option was to force shutdown (via button).
and try to restart, hoping all was fine, this was not the case :-(
I had the added issue of the RAID card system, that i have, this was confused to say the lease and would not behave or work, causing the start up to hang.
so i thought the HDD must be bust and the root cause. ( but soon learnt it was not the cause )
...bought a new HDD removed the RAID card and replugged the cable from RAID card into LOGIC board, ( making the computer act like any normal non-RAID system). I managed to install the OSX, using the snow leopard disk way. once the mac was running, i started to notice the screen would flicker and started to see 'artefacts'. so i started to reveal my symptoms to the web and forums and soon discovered that my graphics card could be the issue all along?.
(nvidia geforce 8800gt 2x dvi).
I read up on that a fix, could be either A. reply the thermal paste, as the card could be over heating or B. stick the card in the oven trick.
Tried option A. first and nothing still issues, so last night took the plunge carried out option B. and ta da it worked! i even managed to run
from my new HDD my lasted install OS X, absolutely fine. I then thought, maybe i could repair my RAID so replugged all the HARDWARD back in and
carried out a disk repair and disk permissions on drives( took a small amount of time), via the SNOW LEOPARD disc - (Disk utilities) and this worked and now have my system working as it was just over 6 days ago.
what was the cost to get this? bought a new hdd so 40.00gbp and thermal paste and cleaner kit ( your still need to do this ) search video card trick on you tube.
and renew thermal paste, approx 15.00gbp, technically i don't need the new HDD, but it was all part of the trial and error way i went. ( i do have extra storage as a result!)"

StarOffice 8 install Solarisx86 with zones

Similar Messages

Maybe you are looking for