Sol 7 upgrade to Sol9

Anyone have any written guides to this process? Checklists?
And anyone else have any horror stories with wisdom included?
Anyone else done this successfully?
thanks ahead of time
David McCall
UNIX Administrator
AdvancedTelcomGroup
[email protected]

Fer1337,
> but I
> cant get any information to upgrade from ZAM 7 to 7.5.
>
how about the documentation? http://www.novell.com/documentation/...rade_guide.pdf
Shaun Pond

Similar Messages

Live Upgrade 2.0 (from Sol8 K23 to Sol9 K05

Installed LU 2.0 from solaris 9 CDs
Created a new BE (= copy of my Sol8 K23)
Start upgrade on my inactiive BE to Sol9
insert Solaris 9 CD 1of2
luupgrade -u -n <INACT_BE> -s /cdrom/sol_9_403_sparc/s0
--> runs fine
eject cdrom
insert Solaris 9 CD 2of2
luupgrade -i -n <INACT_BE> -s /cdrom/sol_9_405_sparc_2 -O '-nodisplay'
After a few questions, the upgrade starts,
it first upgrade Live Upgrade ok,
then it start upgrading Solaris,
it than fails .
I checked the logs on the <INACT_BE> and found in
/var/sadm/install/logs/Solaris_9_pacjages...
it failed on installing SUNWnsm (Netscape 7) because already installed !!
It is right that I had SUNWnsm on my Solaris 8 system!!
Why is this causing LU to fail ?
It should just skip that package and go to the next
For the sake of it I deinstalled netscape 7 of my <INACT_BE> using pkgrm -R
I then restarted the LU using CD 2of2 , now it goes further but fails on package SUNWjhrt (java) which also existed !!
Do I miss something or is LU just unusable ??Thanks

Fred,
I personally have never read that caveat, what is recommended is to always run the same version on components that use the same firmware bundle, in other words.... For a B series upgrade, you need the Infraestruture bundle (include firmware for Fabric Interconnects, IOMs and UCSM) and also need the Server bundle (which includes the firmware for the CIMC, BIOS and Adapter).
Bottom line, the recommendation is to run exactly the same version for components that use firmware that come from the same bundle BUT, UCSM 2.1 introduces an enhancement: "Mixed version support (for infra and server bundles firmware) " wich allows the combination of SOME infraestructure bundles with some server bundles.
http://www.cisco.com/en/US/docs/unified_computing/ucs/release/notes/UCS_28313.html#wp58530 << Look for
"Operational enhancements"
These are the posible configurations I am aware of:
2.1(1f) infrastructure and 2.0(5a)+ server firmware
2.1(2a) infrastructure and 2.1(1f)+ server firmware
I hope that helps.
Rate ALL helpful answers.
-Kenny

Upgrading Sol 10 u3 x86 -- Sol 10 u6 x86 without using LU/Live Upgrade ?

Hi all,
I've got a group of SunFire x4200 M2 hosts currently running Solaris 10 x86 u3, fully patched. They are using the internal LSI Logic SAS controller in a RAID1 config for the disk environment.
When they were originally installed, the thought of running up an SVM mirror wasn't on the cards for our SE who installed them - nor was the potential for using Live Upgrade.
It occurs to me, that whilst Sun will release and continue to release patches for u3, I need to actually migrate to u6 in order to get certain functionality (i.e - new ZFS genesis, iscsitadm/iscsiadm, root zpools). I don't believe this will be "patched in" later for older versions, will it?
How can I cleanly upgrade my hosts without losing any config data or information? Is it even possible? These are production hosts, so I want to do this in the safest way possible. Many have told me I can simply slip in the Sol 10 update 6 media - and boot from it, then find that it will detect the old OS, but I am a little skeptical.
If someone could point me in the right direction here, that would be appreciated!
Thanks.
z

The installer polls many different things on the existing installation. If any of them aren't exactly right, it won't offer the upgrade option, and it won't give you any hints about what tests didn't pass. (Did I find a root slice, is there a root filesystem on it? Does the /etc/vfstab on that partition make sense? Do I have the space in those filesystems to upgrade? ...)
The most common ones to fail have to do with disk layout. It's possible to move /var around, or have an extra partition mounted that the installer doesn't realize is irrelevant for the upgrade.
If that's not the problem, it's very difficult to pin down. At one level, most of the installer logic is just scripts that you could read to understand the logic, but it's difficult to tell which script is running when, so following the logic is not easy.
Darren

Upgrade from Sol 10 to 10 1/06

I have never checked this: when doing an upgrade (from Sol 10 to 10 1/06, in this case), is much extra disk space required beyond that needed for any new packages that are chosen for installation? I've got 2 4GB drives in my U60, with 161MB free on / (slice 0, 50% used) and 1.8GB free on /usr (different disk, 50% used). I can't afford to mess with the hardware just now, and also can't afford to have the OS screwed up by having the upgrade process go awry.
Also, is Web Start the only installation option now? I tried booting from the second CD but that did not work...these are not Sun-supplied CD's, but were burned by someone else; the Web Start install/upgrade seems to work fine, though, at least up to the point where I've selected to upgrade and customized the set of packages for install/upgrade (at which point I cancel, due to my question above).
Many thanks!

I have never checked this: when doing an upgrade
(from Sol 10 to 10 1/06, in this case), is much extra
disk space required beyond that needed for any new
packages that are chosen for installation? I've got 2
4GB drives in my U60, with 161MB free on / (slice 0,
50% used) and 1.8GB free on /usr (different disk, 50%
used). I can't afford to mess with the hardware just
now, and also can't afford to have the OS screwed up
by having the upgrade process go awry.
Also, is Web Start the only installation option now?
I tried booting from the second CD but that did not
work...these are not Sun-supplied CD's, but were
burned by someone else; the Web Start install/upgrade
seems to work fine, though, at least up to the point
where I've selected to upgrade and customized the set
of packages for install/upgrade (at which point I
cancel, due to my question above).
Many thanks!

SAP Sol Mgr 4.0 Upgrade to 7.0 Enterprise Edition

Hi,
I have installed SAP Sol Mgr 4.0 SR3. Now I want to upgrade to SOl Mgr 7.0 Enterprise Edition.
What are the steps I need to follow.
Regards,
B

Hi Neshimi,
Thanks for your reply. Points assigned.
I actually installed Sol Mgr 4.0 SR3. In your reply you mentioned it same as Sol Mgr 7.0 SR3.
Is the Sol Mgr 7.0 EHP1 same as Sol Mgr Enterprise Edition?
Please let me know the steps I need to follow to upgrade to Enterprise Edition. I understood your reply partly.
Please be more clear so that I can understand easily.
What are the patches or updates I need to download. How to Upgrade after I download the files.
The reason why I installed Sol Mgr 4.0 SR3 first is I have the license for it. Is the upgrade free for the next version?
Regards,
B
You can also install ETP as a add-on
check #1109650 and:
#1140258:
2. Prerequisites for the installation
You require SAP Solution Manager 7. 0 SP15 to SPS 17. With SPS 18 (identical to EHP 1) it is automatically activated. The steps described further down are not required.
3. Preparing for the installation
4. Executing the installation
Download the SAP Solution Manager Extension Add-on ST-ETP from SAP Service Marketplace. For details see note 1109650.
Install the Add-on in your Solution Manager
5. After the installation
To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
a) In the case of ST-400 SP15-SP17
To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
b) In the case of ST-400 SP18 or higher
The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
Please also note that your Solman 4.0 SR3 is similar to SolMan 7.0 SR3. The name has just changed in order to matchup with the Netweaver naming convention
Nesimi

Problems with Smart Wireless Headset Pro after upgrading my Xperia Sola to ICS

Just want to let the community, and Sony, know that since I "upgraded" my Xperia Sola to ICS, the Text to Speech on my Smart Wireless Headset Pro is not functioning. It used to work just fine when I had Gingerbread on my phone, but when I upgraded to ICS, the Text to Speech voice is not output on the headset, but on the phone, on the call speaker... Hope this bug gets fixed soon.
Maybe someone already knows of a solution?
Thanks in advance.

There is a new update available for the Smart Wireless headset pro, MW1 (0.1.C.0.3).
Which software version are you running your MW1 on?
If you don't have the latest I suggest that you use SUS to update your software.
http://www.sonymobile.com/gb/tools/update-service/
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

Sol 9 x86 EA now = full version upgrade later?

Hi,
Can anyone confirm that the $20 Solaris 9 intel purchase now, will entitle the buyer to upgrades/patches/etc once Sol 9 moves out of Early Access?
This afternoon somebody mentioned this to me, but I would like a second (weightier) opinion.
In short, if I purchase Sol 9 for $20 now, and the production version comes out next week/month/year, will I have to pay for that too (as if i hadn't purchased this one) or will there be some upgrade-path-type of option.
Thanks,
Vafa.

This is probably the "pci function #5" problem for SIS chipsets.
Apparently you can work around the problem by creating a custom
DCA floppy diskette and installing/replacing a fixed ata.bef file on
that floppy:
http://groups.yahoo.com/group/solarisonintel/message/45595
http://groups.yahoo.com/group/solarisonintel/message/45366

Error messages after upgrading kernel (devfs to udev) [SOL]

when installing the new kernel i got a message to change my menu.lst so it changed "/dev/discs/disc0/part3" to "/dev/hda3" (and nothing else) cause of udev instead of devfs.
after rebooting i get few error messages:
[after network start]
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
etho0: unknwon interface: No such device

kjs wrote:I'm also having an issue after upgrading neither eth0 nor eth1 are showing up in /dev .... I think it's due to the switch from devfs to udev...
for the record - network interfaces never show up in /dev - they're not normal devices
edit: I guess I should provide some help...
ifconfig and "ifconfig -a" will list network devices (also in /proc/net somewhere). If you do not have a network device that means that your module is not properly loaded for that device.
This should have nothing to do with a devfs/udev switch and everything to do with a kernel upgrade.
Just for some more info, can you please report the output of:
· lsmod
· uname -r
· ls /lib/modules
· ifconfig -a

Panic after upgrade sol 8 - sol 10

Hello I make upgrade from solaris 8 to solaris 10 on one of my domain on E6900
after success upgrade and reboot i have that:
module /platform/SUNW,Sun-Fire/kernel/sparcv9/unix: text at [0x1000000, 0x10a2a15] data at 0x1800000
module /platform/sun4u/kernel/sparcv9/genunix: text at [0x10a2a18, 0x1263667] data at 0x18d9b40
module /platform/SUNW,Sun-Fire/kernel/misc/sparcv9/platmod: text at [0x1263668, 0x12673ff] data at 0x192ff00
module /platform/SUNW,Sun-Fire/kernel/cpu/sparcv9/SUNW,UltraSPARC-IV: text at [0x1267400, 0x127a2c7] data at 0x1930cc0
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Ethernet address = 0:3:ba:7:83:c5
mem = 16777216K (0x400000000)
avail mem = 16766476288
root nexus = Sun Fire E6900
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
ssm0 at root: SSM Node 0
ssm0 is /ssm@0,0
pci108e,80022 at ssm0: Node 0 Safari id 31 0xff00000
pcisch2 is /ssm@0,0/pci@1f,700000
PCI-device: pci@2, pci_pci1
pci_pci1 is /ssm@0,0/pci@1f,700000/pci@2
/ssm@0,0/pci@1f,700000/pci@2/scsi@2,1 (glm3):
glm3 supports power management.
/ssm@0,0/pci@1f,700000/pci@2/scsi@2,1 (glm3):
Rev. 7 Symbios 53c896 found.
PCI-device: scsi@2,1, glm3
glm3 is /ssm@0,0/pci@1f,700000/pci@2/scsi@2,1
sd45 at glm3: target 0 lun 0
sd45 is /ssm@0,0/pci@1f,700000/pci@2/scsi@2,1/sd@0,0
root on /ssm@0,0/pci@1f,700000/pci@2/scsi@2,1/disk@0,0:a fstype ufs
pci108e,80021 at ssm0: Node 0 Safari id 30 0xf600000
pcisch1 is /ssm@0,0/pci@1e,600000
PCI-device: pci@1, pci_pci0
pci_pci0 is /ssm@0,0/pci@1e,600000/pci@1
/ssm@0,0/pci@1e,600000/pci@1/scsi@2 (glm0):
glm0 supports power management.
/ssm@0,0/pci@1e,600000/pci@1/scsi@2 (glm0):
Rev. 7 Symbios 53c896 found.
PCI-device: scsi@2, glm0
glm0 is /ssm@0,0/pci@1e,600000/pci@1/scsi@2
/ssm@0,0/pci@1e,600000/pci@1/scsi@2,1 (glm1):
glm1 supports power management.
/ssm@0,0/pci@1e,600000/pci@1/scsi@2,1 (glm1):
Rev. 7 Symbios 53c896 found.
PCI-device: scsi@2,1, glm1
glm1 is /ssm@0,0/pci@1e,600000/pci@1/scsi@2,1
/ssm@0,0/pci@1f,700000/pci@2/scsi@2 (glm2):
glm2 supports power management.
/ssm@0,0/pci@1f,700000/pci@2/scsi@2 (glm2):
Rev. 7 Symbios 53c896 found.
PCI-device: scsi@2, glm2
glm2 is /ssm@0,0/pci@1f,700000/pci@2/scsi@2
sd15 at glm1: target 0 lun 0
sd15 is /ssm@0,0/pci@1e,600000/pci@1/scsi@2,1/sd@0,0
sd51 at glm3: target 6 lun 0
sd51 is /ssm@0,0/pci@1f,700000/pci@2/scsi@2,1/sd@6,0
sd21 at glm1: target 6 lun 0
sd21 is /ssm@0,0/pci@1e,600000/pci@1/scsi@2,1/sd@6,0
PCI-device: SUNW,qlc@2, qlc0
qlc0 is /ssm@0,0/pci@1e,600000/SUNW,qlc@2
PCI-device: SUNW,qlc@1, qlc1
qlc1 is /ssm@0,0/pci@1f,700000/SUNW,qlc@1
fp0 is /ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0
fp1 is /ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0
iscsi0 at root
iscsi0 is /iscsi
ssd47 at fp0: name w5006016a306025e6,0, bus address 15800
ssd47 is /ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016a306025e6,0
ssd55 at fp1: name w5006016b306025e6,0, bus address 15000
ssd55 is /ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016b306025e6,0
/ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016a306025e6,0 (ssd47) online
/ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016b306025e6,0 (ssd55) online
ssd43 at fp0: name w50060163306025e6,0, bus address 15000
ssd43 is /ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w50060163306025e6,0
ssd51 at fp1: name w50060162306025e6,0, bus address 15800
ssd51 is /ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w50060162306025e6,0
/ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w50060162306025e6,0 (ssd51) online
/ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w50060163306025e6,0 (ssd43) online
ssd39 at fp1: name w5006048449af09f7,0, bus address 12800
ssd39 is /ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w5006048449af09f7,0
ssd19 at fp0: name w5006048449af09f8,0, bus address 12800
ssd19 is /ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006048449af09f8,0
WARNING: /ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w5006048449af09f7,0 (ssd39):
Corrupt label; wrong magic number
WARNING: /ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006048449af09f8,0 (ssd19):
Corrupt label; wrong magic number
/ssm@0,0/pci@1e,600000/SUNW,qlc@2/fp@0,0/ssd@w5006048449af09f8,0 (ssd19) online
/ssm@0,0/pci@1f,700000/SUNW,qlc@1/fp@0,0/ssd@w5006048449af09f7,0 (ssd39) online
pseudo-device: emcp23
emcp23 is /pseudo/emcp@23
panic[cpu12]/thread=180e000: BAD TRAP: type=31 rp=180a090 addr=1000000a8 mmu_fsr=0
: trap type = 0x31
addr=0x1000000a8
pid=0, pc=0x1049bf0, sp=0x1809931, tstate=0x480001601, context=0x0
g1-g7: 1, 1, 1, 1066bc0, 1833c00, 10, 180e000
0000000001809db0 unix:die+9c (31, 180a090, 1000000a8, 0, 1809e70, d45a60a8)
%l0-3: 0000000000001fff 0000000000000031 0000000001000000 0000000000002000
%l4-7: 0000000000100000 0000000001887d40 0000000000000000 000000000109c400
0000000001809e90 unix:trap+9e0 (180a090, 0, 1fff, 5, 100000000, 1)
%l0-3: 0000000000000000 0000000001887d40 0000000000000031 0000000000001c00
%l4-7: 0000000000000000 0000000000000001 ffffffffffffe000 0000000000000005
0000000001809fe0 unix:ktl0+48 (300004488a8, 100000000, 1, 183e400, 0, 1835400)
%l0-3: 0000000000000002 0000000000001400 0000000480001601 000000000101c178
%l4-7: 0000000000000001 0000000000000001 0000000000000000 000000000180a090
000000000180a130 unix:mutex_vector_enter+364 (18b1178, 1, 300004488a8, 100000000, 0, 0)
%l0-3: 0000000001933788 000000000180c2e0 0000000000000000 0000000000000000
%l4-7: 0000000100000000 0000000000000000 00000000018357f8 00000000018357f0
000000000180a1e0 emcp:PowerInitOpenCnt+54 (76, 18b1000, 4bb, 6af, 1f4, 1932880)
%l0-3: 00000300004488a8 0000000000000076 0000000000000b10 0000030000446000
%l4-7: 00000000010bc2f8 00000000000006af 3ffffffffffffae8 00000000010bc000
000000000180a340 emcp:_init+4574 (0, 19c64d0, 300007bfd60, 660504, 0, 1)
%l0-3: 0000000000000076 0000000001958df0 00000000013941d0 0000000000000224
%l4-7: 00000300007bfe08 00000000019c64e0 0000000000000000 000000000120b630
000000000180a400 emcpioc:_init+68 (0, 0, 0, 0, 1262800, 13ff560)
%l0-3: 0000000000000000 0000000000000004 0000000000000000 0000000001936a90
%l4-7: 0000000000000001 0000000000000000 0000000001939518 0000000000000000
000000000180a4c0 genunix:modinstall+cc (0, 300014a72d0, 0, 18e7a30, 80000000, 13ff3b8)
%l0-3: 0000000000000000 0000060021a0448d 0000000000000000 0000000001936800
%l4-7: 0000000000000000 0000000020000000 00000000018e7800 0000060021892c36
000000000180a580 genunix:mod_hold_installed_mod+9c (60021a04488, 0, 0, 180a6ec, 1, 300014a72d0)
%l0-3: 0000000000000004 0000000000000003 0000000000000000 00000000000007c0
%l4-7: 0000030000059000 00000000018e09f0 0000000000000000 0000000001939400
000000000180a630 genunix:modrload+100 (19742d0, 1939400, 0, 180c000, 16, 4)
%l0-3: 000000000000000d 0000000000000000 0000060021a04488 00000000019742d8
%l4-7: 000000000180c2f8 0000000000000038 0000000000000037 00000000fffd9c00
000000000180a6f0 emcp:_init+33f0 (6002183ec90, 0, 0, 0, 0, 0)
%l0-3: 0000060021892c2f 0000060021892b90 0000000000000001 00000000019742d0
%l4-7: 00000000019742d8 000000000180a800 000000000000000e 000000000180adf
I have no idea what is wrong. Can anybody help me ? Thank you.

Did you upgrade the version of powerpath to a release supported on Solaris 10?

Sol man upgrade!

Dear All,
Could you please guide me in upgrading solution manager from 4.0 SR2(Patch level 11) to Solman 7 EHP1...
Can i upgrade it through EHPi or i have to deploy patches first through (SPAM/SAINT)
Any prompt help related to this is appreciated......
Regards,
Sohal....

Hi Harvinder,
In order to upgrade solman to EHP1. You cannot use EHPI installer. You have to do this via SAINT/JSPM.
Also, check 1169247, 822380
Also, link https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065932
Thanks
Sunny

Upgrade (Sol 7- Sol 8) and auto_layout

I'm attempting to upgrade from Solaris 7 - Solaris 8 using the cd #1 installation procedure. My /usr filesystem is already pretty full on the Solaris 7 machine. After starting the upgrade process, it reports that i'm roughly 140 mb short in /usr. I used the auto_layout process to free up some space. However, it seems as if the upgrade process wants to store 7.5 GB of data before it can resize.
Is there a way to circumvent this? This is my first upgrade and I'm pretty new to Solaris systems management.
Many Thanks......

What type of netra did you load Solaris 7 on?
netra T1 (AC200)?
netra T1 (100/105)?
Chris

Upgrading from Sol 10 to Sol 10?

Some things on my system got screwed up due to lack of disk space (ie - can't get X to start anymore). Can I just reinstall it and choose the "Upgrade" option, then use smpatch to get it up to date again?
TIA :)

It should work :-) You might get problems if some of the packages on CD/jumpstart are older than the ones on your system, but i think it should work.
It might be safer to do a upgrade to a new HW release, but the next one isn't out yet ..
//Magnus

New v240, can't install or upgrade Sol 10

I've got two new SunFire v240 servers. They came running solari 10 03/05. OBP 4.18.10. I need to upgrade to at least update 2. The installer aborts every time.
I've tried installing via "boot net" or "boot cdrom" without sucess, both update 2 and update 3. After the initial round of questions about identifying the system, the installer just quits. I get a message that says I can run the script "Install_Solaris" if I want to restart the install process, but it still fails. Install log message says, "searching ctd0xxx for an upgradeable Solaris image".
This problem just feels like a newbie issue. If we just knew what setting to set, it would let us continue with the install. Any ideas?

Are you using media provided by Sun (manufactured commercially),
or are you using media that you created yourself onto blank disks ?
If these are "home made" disks, how did you create them?

Trying to set up AV server on mini late 2012. Will upgrade to Yosemite tomorrow. Home Internewt is ATT Sierra mobile hotspot only. So I think I need a wifi router that will tether the hotspot as sole internet source. Recommendation for system set

My system: Mac Mini late 2012 w/ 1 TB disk and *GB memory (for AV server), iPad air 2 w/ 64 GB, iPad, iPad 2, iPhone 6, iPhone 4, Macbook running Yosemite, older Macboo w/ 2GB memory & 160 GB hard drive, 1 TB back up drive, WiFi Printer
Internet: Wireless hotspot ATT 4G LTE limited to 5 GB/mo (no cable or DSL available. Router to be determined
AV equip: Vizio smart TV (WiFi capable & network cable), high end analog audio, DAC, Samsung TV/display w/ HDMI.
Looking for a router recommendation that will utilize my ATT device and stream music (and of course less demanding DATA)
What is/are recommended connection(s) between devices? Hardwire Mini to main TV w/ HDMI, network or USB? Help?

Another way to set things up, use an Apple Airport Extreme Basestation.
My system setup has a cable modem directly connected to the AEBS.
The AEBS is then setup to do all of the network management, I use
both hardwired and WiFi access via the AEBS. It also has a USB port
that you can use for attaching HDDs for common data access and even
Time Machine backups.
FWIW, here's my system:
2011 MiniServer used as HTPC - hardwired ethernet to AEBS
2010 Mini used as server - hardwired ethernet to AEBS
(these are hardwired simply because of proximity to AEBS but could be WIFi connected)
Late 2013 27" iMac workstation- hardwired or WIFi depending on needs
Early 2011 Macbook Pro - WiFi connected
iPhone 5S - WiFi connected as needed
The 2010 Mini Server I use as my "iTunes hub" set up with Home Sharing and
by running Server on it, have Apple download caching of both Mac and iOS
apps, Time Machine backups and general backups for various content from
the different computers.

Risks involved while upgrading to Sol 10 from Sol8.

Hi,
I want to port my existing software from Solaris 8 to Solaris 10.
So, I want to know the risks involved on the basis of :
1. System Call prototype changes.
2. Path to executables.
3. output file path changes.
Please let me know other risks and concerns.
thanks in advance!
Regards,
Manabendra

I want to port my existing software from Solaris 8 to
Solaris 10.
So, I want to know the risks involved on the basis of
1. System Call prototype changes.User code doesn't normally do direct system calls,
but use libc instead.
But I doubt that any system calls have changed.
There may be some new ones, though.
2. Path to executables.Shouldn't have changed.
3. output file path changes.This would depend on your application,
I would think.
Please let me know other risks and concerns.Many Solaris 8 applications will just run on Solaris 10.
Checkout:
http://developers.sun.com/solaris/articles/appcert.html
When building on Solaris 10,
there could be some differences
in the header files, like /usr/include/sys/*,
that you might run into.
Also, some of the new functions/interfaces
in the #include files in /usr/include might clash with
names in your source files.
I don't have a list of the differences
or remember seeing one.
Peter.

Sol 7 upgrade to Sol9

Similar Messages

Maybe you are looking for