Installing disksuite 4.2.1

Hello,
I am about to install Disksuite 4.2.1 on top of Solaris 8.
I have FINALLY located some pkgs for this on the Solaris 8 Software CD disk2. I have found the following pkgs on this cd in /cdrom/sol_8_1000_sparc_2/Solaris_8/EA/products/DiskSuite_4.2.1/sparc/Packages -
SUNWmdg
SUNWmdja
SUNWmdnr
SUNWmdnu
SUNWmdr
SUNWmdu
SUNWmdx
Going on some notes I have, I am also supposed to have in the same directory, and supposed to install the following -
SUNWlvma
SUNWlvmg
SUNWlvmr
But I can't see these pkgs in this dir. Do these also need to be installed ??
Thx
Trev

Forget it.
Don't think I need these pkgs. Have installed all others and will see how I go.
Cheers

Similar Messages

Disksuite 4.2.1 wont install via jumpstart on Solaris 8 2/04

Trying to install Disksuite on a Sun Solaris 8 image. The install works on Fujitsu hardware with an even older (2/02) Solaris 8 image for Fujitsu hardware, but for some reason its not working for a Sun V120 with Sun's 2/04 solaris 8 release.
Here's the output from my finish script to install the packages. All other packages install just fine.
==============================================================================
ACI-secure.driver: Finish script: install-disksuite.fin
==============================================================================
Installing DiskSuite
Installing DiskSuite from /a//tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
==============================================================================
Installing Package: SUNWmdr
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdr> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Drivers
(sparc) 4.2.1,REV=1999.12.03.10.00
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdr/install/checkinstall
: /tmp/sh141750: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdr> failed.
No changes were made to the system.
==============================================================================
Installing Package: SUNWmdx
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdx> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Drivers(64-bit)
(sparc) 4.2.1,REV=1999.11.04.18.29
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdx/install/checkinstall
: /tmp/sh142020: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdx> failed.
No changes were made to the system.
==============================================================================
Installing Package: SUNWmdu
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdu> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Commands
(sparc) 4.2.1,REV=1999.11.04.18.29
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdu/install/checkinstall
: /tmp/sh142290: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdu> failed.
No changes were made to the system.

/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdr/install/checkinstall
: /tmp/sh141750: cannot create
pkgadd: ERROR: checkinstall script did not complete successfullyCheckinstall errors usually suggest that the package cannot be read by the user nobody.
The FAQ mentions this with respect to patches, but it can affect packages as well:
http://www.science.uva.nl/pub/solaris/solaris2.html#q5.59
5.59) Patch installation often fails with "checkinstall" errors.
Darren

DiskSuite disk manager

Hello!
I'm up and running Solaris8 on a dual P3-550 iWill mobo.
I've got gnomev1.4 running and netscape 6.
I have a second drive that I disconnected for safety when I installed Solaris. (It is a ufs drive with files already on it.) I reconnected the cabling, and ran devsadm -v.
I was not having any luck with the mount command, so I ran
"metatool &" as root and the Disksuite software loads. I hit the "DiskView" button, and my controller and the 2 Hard drives show up. But the drop-down menu ("Tools") for filemanager and diskmanager says "need to install DiskSuite SysAdmin SUNWadm". So, I installed all the SUNWadm* packages from cd 1. No luck / same message.
(Both disks show in the graphical window, and the sizes and slices are all correct. )
Is this DiskSuite supposed to be functional as supplied with the media install kit? Where is this SUNWadm package?
Bottom line, I want to access the second disk "as is", without formatting,etc! (As I said, it was formatted ufs via a previous Solaris8 install, and I have lots of good stuff on it).

Wouldn't you know it: I succeeded with the mount command just now.
I can access all the files on the second drive.
Still, the graphical DiskSuite is something I'd like to have running!
Help!

VxVM v3.5, unencapsulation and no rootdg

Hello
I would appreciate some help please.
Using VxVM & VxFS v3.5 on Solaris 9.
The root disks were encapsulated with two extra volumes on non root disks.
There are two data volumes within the cdrdg disk group.
I have unencapsulated the root disk and re-booted with the view to:
1. install Disksuite/SVM
2. Deport the data diskgroup located on data disks
3. Remove Veritas VxVM & VxFS v3.5
4. Install Veritas VxVM & VxFS v4.1
5. Import the data diskgroup.
However, on booting after unencapsulating the root disks I get the following errors:
Starting VxVM restore daemon...
VxVM starting in boot mode...
Sep 5 08:37:28 vxvm:vxconfigd: enable failed: Error in disk group configuration copies
Sep 5 08:37:28 vxvm:vxconfigd: No valid disk found containing disk group; transactions are disabled.
Sep 5 08:37:28 vxvm:vxconfigd: Rootdg cannot be imported during boot
VxVM general startup...
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
No valid disk found containing disk group; transactions are disabled.
vxvm: Vold is not enabled for transactions
No volumes started
vxvm:vxrecover: ERROR: IPC failure: Configuration daemon is not accessible
Starting VxVM Diskgroup Configuration Log Daemon...
I think that this is due to there now not being a rootdg disk group.
The contents of /etc/vfstab are:
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/md/dsk/d1 - - swap - no -
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no logging
/dev/md/dsk/d3 /dev/md/rdsk/d3 /var ufs 1 no logging
swap - /tmp tmpfs - yes size=512m
#/dev/vx/dsk/cdrdg/cdrt01vol /dev/vx/rdsk/cdrdg/cdrt01vol /cdrt vxfs 1 yes log
#/dev/vx/dsk/cdrdg/cdrc01vol /dev/vx/rdsk/cdrdg/cdrc01vol /cdrc vxfs 1 yes log
Does anyone have any idea what I can do?
I have removed the two Veritas file systems out of /etc/vfstab and the system boots OK but
I can nolonger mount the Veritas volumes.
I have now added DiskSuite/SVM to the root disks and mirrored.
I have not touched the slices 3 & 4, just added a slice 7 from unused disk space.
Should I add the DiskSuite root disks to rootdg, mount the veritas file systems, deport them,
remove Veritas v3.5 and then install V4.1 and import the disk group.
or
just continue with the removal of v3.5 and import the disk group when v4.1 is installed.
Many thanks.

Starting VxVM restore daemon...
VxVM starting in boot mode...
Sep 5 08:37:28 vxvm:vxconfigd: enable failed: Error
in disk group configuration copies
Sep 5 08:37:28 vxvm:vxconfigd: No valid disk found
containing disk group; transactions are disabled.
Sep 5 08:37:28 vxvm:vxconfigd: Rootdg cannot be
imported during boot
VxVM general startup...
vxvm:vxconfigd: ERROR: enable failed: Error in disk
group configuration copies
No valid disk found containing disk group;
transactions are disabled.
vxvm: Vold is not enabled for transactions
No volumes started
vxvm:vxrecover: ERROR: IPC failure: Configuration
daemon is not accessible
Starting VxVM Diskgroup Configuration Log Daemon...
think that this is due to there now not being a
rootdg disk group.Yes.
The contents of /etc/vfstab are:
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/md/dsk/d1 - - swap - no
md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no
logging
md/dsk/d3 /dev/md/rdsk/d3 /var ufs 1 no
logging
- /tmp tmpfs - yes size=512m
ev/vx/dsk/cdrdg/cdrt01vol
/dev/vx/rdsk/cdrdg/cdrt01vol /cdrt vxfs 1 yes log
/dev/vx/dsk/cdrdg/cdrc01vol
/dev/vx/rdsk/cdrdg/cdrc01vol /cdrc vxfs 1 yes log
Does anyone have any idea what I can do?You could create a new rootdg, or you could ignore it. I'd probably ignore it.
I have removed the two Veritas file systems out of
/etc/vfstab and the system boots OK but
I can nolonger mount the Veritas volumes.Correct. VxVM 3.x (and lower) requires a 'rootdg' group be present.
have now added DiskSuite/SVM to the root disks and
mirrored.
have not touched the slices 3 & 4, just added a
slice 7 from unused disk space.
Should I add the DiskSuite root disks to rootdg,
mount the veritas file systems, deport them,
remove Veritas v3.5 and then install V4.1 and import
the disk group.That would work.
or
just continue with the removal of v3.5 and import the
disk group when v4.1 is installed.That would work as well.
Darren

New install of solaris 10 and I cannot see the other 5 harddrives

I am a bit rusty on solaris but here is the issue and exscuse my clulessness. Just installed 10 on an e450. At the ok prompt you can query the hardware and the hard drives are there. From the OS level, they do not appear. In the solaris console I can only see the hard drive the OS is on. Question is simple; how do you make the OS see the other hard drives. Linux I use disk druid. In 8 I used disksuite, but it has been about six years since I have messed with it.

It sounds like all that was done during the installation as to set up one disk for the OS install and the remaining drive were not selected and partitioned.
Run format and see if the disks show up. If they are there, then they likely need partitioning and file systems added with newfs command. Last thing is to make sure they get mounted by adding entries in /etc/vfstab.
If you want to do volumes go to docs.sun.com and dowload the Sun Volume Manager documentation under Solaris 10.
Regards

Error in installing packages during jumpstart

The machine I am installing via jumpstart is on a terminal server and I am connected to ttya. I am seeing these errors in the log:
## Executing postinstall script.
pkgadd: ERROR: freopen(/dev/tty, "a", stdout) failed, errno=6
pkgadd: ERROR: postinstall script did not complete successfully
and I am told the installation failed with an error code of 1 which, according to the pkgadd man page it a fatal error.
When I do a pkginfo -l on the package it appears that the package is there. Is this something to worry about?
If it means anything, this is the java 1.4.2_02 packages.
Kent

You might want to redirect stdout & stderr to /dev/null while installing packages via run-scripts (I'm assuming that 's the case).
So, when you're doing the pkgadd, do it like this:
echo y|pkgadd -a ${MD_PRODUCT}/admin -d `pwd` SUNWmdr > /dev/null 2>&1
Here I'm trying to install a disksuite pkg as a post-install and it givees me the same error messages that you get if I don't redirect 2>&1 to /dev/null
HTH

How to backout a Recommended Patch cluster deployment in Solstice disksuite

Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Installing GCC

Hello...
I got the blw error every time I try to install gcc package:
#pkgadd -d gcc-2.95.3-sol7-sparc-local
The following packages are available:
1 SMCgcc gcc
(sparc) 2.95.3
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1
Processing package instance <SMCgcc> from </gcc-2.95.3-sol7-sparc-local>
gcc
(sparc) 2.95.3
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/cc1obj", errno
28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/cc1plus", errn
o 28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/chillrt0.o", e
rrno 28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/collect2", err
no 28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/cpp0", errno 2
8, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/crtbegin.o", e
rrno 28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/f771", errno 2
8, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/gmon.o", errno
28, No space left on device
cpio: Cannot write "reloc/lib/gcc-lib/sparc-sun-solaris2.7/2.95.3/include/assert
.h", errno 28, No space left on device
cpio: Cannot write "
pkgadd: ERROR: attempt to process datastream failed
- process </usr/bin/cpio -icdumD -C 512> failed, exit code 95
pkgadd: ERROR: unable to unpack datastream
Installation of <SMCgcc> failed (internal error).
No changes were made to the system.
Can u pls advise how I can over come this problem? I alrady tried to install "gcc-3.0.3-sol7-sparc-local" but still the same.
Thanx
Rabea

Hi
You cannot dynamically resize filesystems unless you have some disc managagement software
running ( eg Solstice Disksuite, Veritas Volume Manager ).
If you do not have disk management software, you will probably have to dump all the filesystems
to tape or another server using something like ufsdump, repartition your disk and then restore the
filesystems back.
You can find good FAQs on Disk Suite or Veritas at docs.sun.com.

DiskSuite and Live Upgrade 2.0

I have two Solaris 7 boxes running DiskSuite to mirror the O/S disk onto another drive.
I need to upgrade to Solaris 8. In the past I have used Live Upgrade to do so, when I have enough free disk space to partition an existing disk or to use a unused disk for the Solaris 8 system files.
In this case, I do not have sufficient free space on the boot disk. So, what is the best approach? It seems that I would have to:
1. unmirror the file system
2. install Solaris 8 onto the old mirror drive using LU 2.0
3. make the old mirror drive the boot drive
4. re-establish mirroring, being sure that it goes the right way from the Solaris 8 disk to the old boot disk
Comments, suggestions?

I recently built a system (specs below) and installed this card (MSI GF4 Ti4200 VTD8X MS8894, 128MB DDR), and when I try to use Live Update 2 (version 3.33.000, from the CD that came with the card), I get the same message:
"Warning!!! Your Display Card does not support MSI Live Update 2 function. Note: MSI Live Update 2 supports the Display Cards of MSI only."
I'm using the drivers/BIOS that came on the CD: Driver version 6.13.10.4107, BIOS version 4.28.20.05.11. I see on the nVidia site that they have the 4109 drivers out now, should I try those? ?(
I have also made sure to do the suggested modifications to IE (and I don't have PC-cillin installed):
"Note: In order to operate this application properly, please note the following suggests.
-Set the IE security setting 'Download signed ActiveX controls' to [Enable] or [Prompt]. (System default is [Prompt]).
-Disable 'WebTrap' of PC-cillin(R) or any web based anti-virus application when executing MSITM Live Update 2TM.
-Update Microsoft® Windows® Installer"
I downloaded a newer version of LIveUpdate (3.35.000), and installed it (after completely uninstalling the old version), and got the same results. Nothing on my system is currently overclocked.
Help!
System specs:
-Soyo SY-KT400 DRAGON Ultra (Platinum Edition) with latest BIOS & Chipset Drivers
-AMD Athlon XP Thoroughbred 2100+
-MSI GF4 Ti4200 VTD8X (MS-8894)
-WD Caviar Special Edition 80 GB HDD, 8 MB Cache
-512 MB Crucial PC2700 DDR (one stick, in DIMM #1)
-TDK 40/12/48 CD R/RW
-Daewoo 905DF Dynaflat 19" Monitor
-Windows XP Home Edition, SP1/all other updates current
-On-Board CMedia 6-channel audio
-On-Board VIA 10/100 Ethernet
-Altec-Lansing ATP3 Speakers

Upgrade solaris 8 to solaris 10 with DiskSuite

Hello
After years of not using Solaris I find I have to upgrade a Sun V240 from Solaris 8 to Solaris 10. My concern is that the disks are managed by DiskSuite. Do I have to back DiskSuite out before I do the upgrade and upgrade just on the underlying disks? Or is Solaris clever enough to not have to do this now?
I have looked around but would just like a definative answer from someone on here.
Many Thanks
Darren.

Hi,
You can use a IEAK 10 to deploy the installation of IE 10, build your own package, you can add any additional installations or updates you may want to tack onto your Internet Explorer 10 instal.
This is the download link
Internet Explorer Administration Kit 10
http://www.microsoft.com/en-in/download/details.aspx?id=36807
Detailed instructions are listed in the following link
Utility Spotlight: Build your own Internet Explorer 10 installation
http://technet.microsoft.com/en-us/magazine/dn133229.aspx
Yolanda Zhu
TechNet Community Support

After installing 137137-09 patch OK in global zone, bad in non global zone

Hi all,
scratching my head with this one.
Installed 137137-09 fine on Sun Fire V210. Machine has one non global zone running a proxy server (nothing very exciting there!). non global zone has a local filesystem attached, but don't think this is the issue (on my test V210 I created the same sort of filesystem and was unable to replicate the problem :( ).
So 137137-09 is fine in the global zone (I had the non global zone halted when patch installed) it is also installed in the non global zone (ie, when zone boots it says it's at rev 137137-09 via uname) in the patch log in the non global zone I get this:
PKG=SUNWust2.v
Original package not installed.
pkgadd: ERROR: ERROR: unable to get zone brand: zonecfg_get_brand: No such zone configured
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
/usr/local/zones/cotchin/lu/dev/.SUNW_patches_1000109009-1847556-000000d3e42faa84/137137-09/FJSVcpcu/install/checkinstall: /usr/local/zones/cotchin/lu/dev/.SUNW_patches_1000109009-1847556-000000d3e42faa84/137137-09/FJSVcpcu/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.
I'm not sure if the branding error is causing the checkinstall postpatch script error or if they are not related. There doesn't seem to be any obvious permissions problems that I can find. I have checked that all the pkg and patch patches are up to date on the system. Searching on the brand error gives me a link to a problem with 127127-11, but that was installed on the system before the local zone was created and all the other seemingly appropriate patches (eg: 119254) are all up to date or at a higher revision than recommended.
I see the same problem on a M5000 which has two non global zones on it.
Both machines had the Solaris 10 50/08 update bundle applied when it came out,a nd have had recommended patch sets applied at regular intervals since.
This issue only came to light when trying the latest bundles with 138888-01/02 in it, and those fail to install on the global zones because the non global zone install dies claiming 137137-09 is not installed (which is plainly wrong).
I've tried to recreate this on a test server but unfortunately everything works as it should, even though the test server has a similar history in terms of patches and original setup to the others.
I'm planning to try to detatch the non global zone and try an attach -u to see if it will update the patches properly, but I'm not holding out much hope on that one (I need to wait for a mainteiance window when I can take the zone down in a couple of days).
Any ideas?

Well, I am following up to my own post it seems I have determined what is causing the problem, or at least situations where the problem can be reproduced which I have been able to do on my test system.
It seems that if the zone container's zonepath is in /usr (eg: /usr/zones, /usr/local/zones, or some other path under /usr) the patchadd of 137137-09 will fail with the log similar to posted above, and this will stop further kernel patches (eg: 138888-02) being added.
The test system had everything patched to current and searching the web I can't find any other instances of this being an issue, but I have reproduced this problem on my test machine (which worked OK because it's test zones were in a filesystem mounted as /zones). When I used zoneadd -z <zonename> move to a zone in /usr/local and applied 137137-09 the same problem came up.
Not sure what is causing this issue.. I imagine it might have to do with some sort of confusion with the patch utilities and the read-only loopback filesystems in the sparse root zone but I can't bs sure.
Maybe someone at sun will see this and figure out what the deal is :)
When I moved my test zone back to /zones the patch applied perfectly so it's definitely having it in /usr or /usr/local (I tried both locations, even though they are seperate ufs filesystems on my test server).
Oh I am running DiskSuite to mirror filesystems on my V210's which may or may not have anything to do with it.
Hope this helps someone in the future at least!

Trying to install solaris 10 on sun file v210

Rebooting with command: boot net - install nowin
Boot device: /pci@1f,700000/network@2 File and args: - install nowin
1000 Mbps FDX Link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 1000 Mbps FDX Link up
Requesting Internet address for 0:3:ba:60:36:d
I am trying to install solaris 10 (sparc) on a sun fire v210 and I get kernel dump and
the following crash messages:
Any suggestion would be very welcome indeed as this the first of 250 systems...
Lydia
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Cannot find /system/contract
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Cannot mount /proc
WARNING: file system 'mntfs' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: Cannot find /etc/svc/volatile
WARNING: Cannot find /system/object
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Failed to process interrupt for ali1535d+-power0 due to down-rev nexus driver isa0
WARNING: power_attach: failed to add high-level interrupt handler.
WARNING: power button driver failed to install
WARNING: Failed to process interrupt for rmc_comm0 due to down-rev nexus driver isa0
WARNING: rmc_comm failed to install
WARNING: Could not install rmclomv driver
WARNING: Failed to process interrupt for pcf85840 due to down-rev nexus driver isa0
WARNING: i2c_0 failed to retrieve iblock cookie. Operating in POLL MODE only
fs/sockfs:sock_getfasync() not defined properly
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetpeername'
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetsockname'
WARNING: mod_load: cannot load module 'c2audit'
WARNING: c2audit: unable to resolve dependency, module 'fs/sockfs' not found
misc/consconfig:consconfig_get_usb_kb_path() not defined properly
panic[cpu1]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/consconfig
000000000180b890 genunix:mod_hold_stub+1f0 (0, 185f800, 18ac878, 60000c44fb0, 1817328, 0)
%l0-3: 0000000001843ac8 000006000136e000 0000000001811cf8 0000000000000000
%l4-7: 0000000000000000 0000000000000064 0000000000000064 0000000000000001
000000000180b940 unix:stubs_common_code+30 (21dead78c0, 960010, 53555554, 0, 31f400, 0)
%l0-3: 000000000180b209 000000000180b2e1 000000123e000000 0000000000000001
%l4-7: 0000000000000000 0000000001817338 0000000000000000 0000060000c1abc0
000000000180ba10 genunix:main+134 (18accd0, 18a8800, 18364c0, 1861400, 183b400, 1814000)
%l0-3: 0000000070002000 0000000000000001 0000000000000000 0000000000000002
%l4-7: 00000000018afef8 00000000018afc00 00000000018acce0 00000000018acc00

I am using jet to do the jumpstart and the config file for jet is list below.
The install server is solaris 10 sparc
SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500
The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded
the latest recommended patchset which should bring me to 118855-36 plus the latest
minor kernel patches.
nereid-root (482)>cat m1001
# Client template file
# Client: m1001 (derived from quintor.js)
# Created: Wed Mar 8 14:38:51 GMT 2006
# This file was automatically generated using 'make_template'
# Product: base_config
# Synopsys: Basic host information
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# i86pc : Intel X86
# Ethernet can be obtained from the 'banner' command at OBP
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
base_config_ClientArch="sun4u"
base_config_ClientEther=00:03:ba:60:36:0d
base_config_ClientOS="sol10_u3"
# Client allocation
# The mechanism used to build this client; by default, the options listed
# in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
# if this particular client needs to do something different.
base_config_client_allocation="newboot"
# products is the set of products to install after base_config; this
# should be updated automatically by make_template, so you
# will only need to change it, if you wish to omit certain
# modules when testing/debugging.
base_config_products=" custom"
# JumpStart sysidcfg information
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
# terminal: terminal type (vt100/vt220/sun etc)
# security_policy: Kerberos policy (Solaris 8 +)
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
# default_route: Solaris 9 allows a default route to be set
# (ignored on all other versions of Solaris, less than 9)
base_config_sysidcfg_nameservice=NONE
base_config_sysidcfg_network_interface=PRIMARY
base_config_sysidcfg_ip_address=172.17.3.1
base_config_sysidcfg_netmask=255.255.0.0
base_config_sysidcfg_root_password="xxxxxxxxxxxx"
base_config_sysidcfg_system_locale="en_GB.ISO8859-15"
base_config_sysidcfg_timeserver=
base_config_sysidcfg_timezone="GB"
base_config_sysidcfg_terminal=vt100
base_config_sysidcfg_security_policy=NONE
base_config_sysidcfg_protocol_ipv6=no
base_config_sysidcfg_default_route=
# X86, X64 specific settings. If this is an x86 client, then you may need
# to configure these settings. They are ignored for SPARC builds.
# base_config_x86_nowin:
# This stops Solaris from trying to run windows during the install.
# the default value is yes.
# base_config_x86_console:
# Set the console to the correct tty port. This is used for doing installs
# via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
# and v65x use ttyb. NOTE: you only need to set this if you are NOT going
# to connect a keyboard and monitor to the client.
# base_config_disable_acpi:
# Disable ACPI - sometimes disabling ACPI makes the install go
# better due to how the interrupts are handled. Non-Null disables ACPI.
# base_config_x86_safetoreboot:
# The Solaris installer can't control the BIOS, therefore does not
# know if its safe to reboot the client as it may simply jumpstart
# again. If your PXE boot is a one time option, and the next reboot
# will attempt to boot from disk, then you probably want to set this
# option to "yes". Otherwise, leave it as it is so that it won't reboot
# and therefore allow you to manually change your BIOS to boot from disk.
base_config_x86_nowin=""
base_config_x86_console=""
base_config_x86_disable_acpi=""
base_config_x86_safetoreboot=""
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory, otherwise
# fill in the other details below to get toolkit to create one for you.
base_config_profile=""
# JumpStart profile information
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
# partition sizes:
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
# / s0
# swap s1
# /var s5
# /usr s6
# /opt s7
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
base_config_profile_cluster=SUNWCall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=""
base_config_profile_root=8192
base_config_profile_swap=4096
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
# If you are not using VxVM, then you can use s3 and s4 for whatever you wish!
base_config_profile_s3_mtpt=""
base_config_profile_s3_size=""
base_config_profile_s4_mtpt=""
base_config_profile_s4_size=""
base_config_profile_s5_mtpt=""
base_config_profile_s5_size=""
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""
# If you are using DiskSuite, the default behaviour is to use slice 7 as a
# location for metastate databases. If you are using DiskSuites default config,
# please avoid using s7 for data!
base_config_profile_s7_mtpt="/export/disk/1"
base_config_profile_s7_size="free"
# You can specify additional disks to use/configure here
# additional_disks is a space separated list of c?t?d? type disk names
# For each disk listed in additional_disks, a pair of variables of the form
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
# should be defined for each slice required on the disk.
# N.B. DO NOT SET THE BOOT DISK UP HERE !
base_config_profile_additional_disks=""
base_config_profile_disk_c0t3d0s0_mtpt=""
base_config_profile_disk_c0t0d0s0_size=
# Additional locales/geos e.g. N_Europe, C_Europe
base_config_profile_add_locales=""
base_config_profile_del_locales=""
base_config_profile_add_geos=""
base_config_profile_del_geos=""
# UFS Logging
# Solaris 7 and above support UFS+, which allows for a logging filesystem
# under UFS. If you want to use this feature on any of the UFS mount points,
# please specify the mount points here, as a space seperated list, or enter
# the keyword "all" to enable logging on all UFS filesystems.
# Solaris 9 09/04 enables logging by default. You can also specify mountpoints
# preceded by a - sign to say that you DON'T want logging enabled on that
# filesystem, or you can use the keyword "none" to say you don't want any
# ufs logging turned on at all.
# N.B. root (/) can be included in the list, and is included by default if
# using either the "all" or "none" keyword.
# Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
# valid.
# e.g. base_config_ufs_logging_filesys="all" : log all filesystems
# base_config_ufs_logging_filesys="none" : log no filesystems
# base_config_ufs_logging_filesys="-/ /var -/usr" : log /var, but not / and /usr.
base_config_ufs_logging_filesys="all"
# Packages to add to/remove from the selected cluster
# Use this to populate the profile with package <pkg> <add|delete> entries
base_config_profile_add_packages=""
base_config_profile_del_packages="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"
# Clusters to add to/remove
# Use this to populate the profile with cluster <cluster> <add|delete> entries
base_config_profile_add_clusters=""
base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"
# Remote file systems (NFS)
# Specify these as space seperated list of pairs as follows, using ? as
# the seperator (as : has special meanings with nfs!)
# e.g. to mount 1.1.1.1:/fs on /fs you would create the entry
# base_config_nfs_mounts="fs?1.1.1.1:/fs"
base_config_nfs_mounts=""
# Host information
# This section defines most things network related etc.
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
# nodename: the value for /etc/nodename if it's not the default
# hostname
# defaultrouter: the value for /etc/defaultrouter.
# notrouter: if this is set, the file /etc/notrouter will be created
# dns_domain: domain entry for /etc/resolv.conf
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
# dns_searchpath: list of entries to go in the search line
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# of DNS until later on.
base_config_nodename=""
base_config_defaultrouter=""
base_config_notrouter=""
base_config_dns_domain=""
base_config_dns_nameservers=""
base_config_dns_searchpath=""
base_config_dns_disableforbuild="yes"
# NTP configuration
# Specify a list of names or ip addresses for the NTP servers. The first
# one will be given a 'prefer' tag. This section will only place lines
# of the form: server <ipaddress/name> [prefer]
# into the /etc/inet/ntp.conf file. If you require more control of ntp,
# please use the custom module to deploy your own custom ntp.conf file.
# N.B. If you do use names, they must be resolvable in your name service.
base_config_ntp_servers=""
# Network Interface information
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
# Logical interfaces should be defined using _'s rather
# than :'s.
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
# For example:
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
base_config_networkifs="beg1"
base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"
# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""
# IP Multipathing (Solaris 8+)
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
# netgroup: ipmp interface group name
# e.g. database-net
# ipmp mode: s = standby (failover only)
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
# l = load spreading / active-active
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
# test1: ipmp test address1
# test2: ipmp test address2
# N.B. these addresses must not be used or
# placed in the hosts file
# mask: netmask for ipmp pair
# hostname: unique hostname for logical ip
# log-ip: logical ip address for first i/f of pair
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
# hostname2: unique hostname for logical ip
# log-ip2: logical ip address for second i/f
# of pair
# Example:
# base_config_ipmp_networkifs="qfe0_qfe1"
# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""
# Misc options
# this section is a catchall for other options not included above
# update_terminal: if set, put the sysidcfg terminal type into inittab
# enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
# dumpadm_minfree: set a limit so that crash dumps don't fill up the
# dump filesystem. See dumpadm(1M) -m option for
# possible values.
# noautoshutdown: if set to any value, disable power management
# enable_rootlogin: if set to any value, enable network root login
# from both telnet/rsh and ssh
# enable_rootftp: if set to any value, enable root ftp access
# shutup_sendmail: if set, create an alias hostname. to shut up sendmail
# poweroff_afterbuild: if set, shut the machine down once it has been built
# base_config_dedicated_dump_device:
# if set, dumpadm will configure the partition as a
# Dedicated Dump Device. See dumpadm(1M) for supported
# Operating Environments.
# (Device path e.g. /dev/dsk/c?t?d?s?)
# N.B. This partition is for the SOLE use of the crashdump utility !
# enable_altbreak: if set, enable alternate break sequence
# disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
# usually just tries to rarp ip addresses for additional
# interfaces and takes ages on machines with lots
# of unused network adapters.
base_config_update_terminal="yes"
base_config_enable_savecore="yes"
base_config_dumpadm_minfree="20000k"
base_config_noautoshutdown="pm_disabled"
base_config_enable_rootlogin="yes"
base_config_enable_rootftp=""
base_config_shutup_sendmail=""
base_config_poweroff_afterbuild=""
base_config_dedicated_dump_device=""
base_config_enable_altbreak=""
base_config_disable_sysid_probe="yes"
# NFSv4
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
base_config_nfsv4_domain=""
# N.B. Unless you need to point this client at alternate media for patches
# and packages that is not held on this server, please skip this section!
# productdir is where to find the products. This should be an NFS style
# path, i.e. 192.168.1.1:/export/install but if the server
# is the JumpStart server, then it should just be specified
# as a normal path.
# patchdir is where to find the patches. Same format as productdir.
# Leaving the following blank means they will be populated using jumpstart.conf
# and the JumpStart servers ip address. This is the default behaviour
# and should only be changed if your patch/package repository is not held
# on this server.
base_config_productdir=""
base_config_patchdir=""
# Last one - mainly for developing JumpStart scripts!
# If you set this, the rc3.d/S99jumpstart script will be disabled
# (set to rc3.d/s99jumpstart) every time it is processed - this allows you
# to run it by hand and invoke each reboot step
base_config_debug_jumpstart_postinstall=""
# Product: Custom
# Synopsis: The custom product can install packages and patches that
# would not otherwise be included by the standard
# installation products.
# Which additional packages are to be installed
# (by default, these get added during the main Solaris installation phase)
# O.S. Specific versions:
# as a side effect, if a directory exists under the package dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main package directory
# i.e /export/install/pkgs/custom/sparc/5.8 takes preference over
# /export/install/pkgs/custom/sparc for a Solaris 8 box
# Package Response files:
# If a custom package needs a response file, create a directory called
# /opt/jet/Clients/<clientname>/responses
# and put the response file in to it, named the same as the package.
# i.e. for a package called Fred, on client1, use pkgask to create
# pkgask -r /opt/jet/Clients/client1/responses/Fred Fred
# (Space seperated list of packages)
custom_packages=""
# Custom packages at subsequent boots
custom_packages_1=""
custom_packages_n=""
# Which additional patches are to be installed
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of patches)
custom_patches=""
# Custom patches at subsequent boots
custom_patches_1=""
custom_patches_n=""
# Custom patch sets... create a directory in the patch directory named after
# the set, and put a patch_order file in it, along with the patches...
# (Space seperated list of patch set names)
# N.B. as a side effect, if a directory exists under the patch set dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main patchset directory
# i.e /export/install/patches/patchset/5.8 takes preference over
# /export/install/patches/patchset
custom_patchsets=""
# Custom patchsets at subsequent boots
custom_patchsets_1=""
custom_patchsets_n=""
# Search paths
# The files and scripts sections below will look for source files relative
# to the Clients/<clientname> directory. If you wish to look in other places
# for files, please fill out the search path option below. Items in the
# search path are relative to the Clients/<clientname> directory, since the
# client has no knowledge of the filesystem layout of the server
# e.g. for a client 'fred', the default location for all custom files/scripts
# is /opt/jet/Clients/fred
# if the search path was set to "../common" then the installation routines
# would look first in Clients/fred then
# Clients/fred/../common (or Clients/common in this case)
# Search path is a space separated list of places to search
# THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!
custom_search_path="../common.files"
# Files to be copied to the client. The filenames must be of the form
# filename1:a:filename2
# Where filename1 is the name of the source file in the
# /opt/jet/Clients/<clientname> directory
# filename2 is the full path of the file on the installed client
# and the middle option is whether to a - append, or o - overwrite the file
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of tuples)
# N.B. Please see section above regarding where to place the source files
# N.B. (2):
# appending to /etc/hosts is a special case; instead of just appending
# the file, the module will do an 'intelligent merge' of the new hosts
# file with the existing one.
# custom_files="hosts:a:/etc/hosts"
#custom_files="system:a:/etc/system"
custom_files=""
custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"
# Custom files at subsequent boots
custom_files_n=""
# Scripts to be run on the client at the end of the build
# The scripts must be placed in the directory
# /opt/jet/Clients/<clientname>
# and will be copied to the client.
# Note: we don't allow you to run custom scripts during the Jumpstart
# phase because its kinda dangerous.
# If you need to do this, the best way is to create
# your own custom module to do this.
# Custom scripts at subsequent boots
custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"
custom_scripts_n=""
# Special JumpStart 'Begin' phase scripts
# If you need to run scripts in the 'begin' phase of the JumpStart, you
# can supply them here. Please note, that in the 'begin' phase, the
# new OS has not been installed and the majority of the OS running will
# be read-only from the JumpStart server.
custom_scripts_b=""
nereid-root (483)>

Solstice DiskSuite in Solaris 8

Hi all,
I was told that DiskSuite is included in Solaris 8, does anybody know where can I find the installation files???
Is there a wizard or something like that???
Do I need a special CD???
I have installed it from the Easy Access Server CD but I don't know how to do it from the files included in Solaris 8 Media
Thanks in advance...
Marissa

had the same prob myself...
cd /cdrom/cdrom0/Solaris_8/EA/products/DiskSuite_4.2.1/sparc

DiskSuite or Veritas Volume Manager

With regards to Solaris 8,
I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

Hi,
You've already got volume manager, so why not use it? If you install ODS as well as VXVM, you're just complicating the setup of the machine.
You've got veritas already installed, just use this!

Does Solaris 8 come with Disksuite? If so where is it?

We have recently purchased a Netra T1 which comes with Solaris 8
pre-installed (and no CD Roms). I want to be able to configure the 6 SCSI
drives that we have with this machine as a single device - and I believe that
the tool I need for this is called 'DiskSuite'.
However I can't find any of the disksuite commands on our machine, and
it doesn't look like it is installed.
Can anybody tell me:
- Is Disksuite the tool that I need to join multiple disks together into
a single Raid5 device?
- If so, is it supplied with Solaris 8
- And if so, where can I get hold of it?
Many thanks,
Chris Allen
[email protected]

you can download the software 2 of 2 cd, which has the Disksuite 4.2.1 software on it, from:
http://wwws.sun.com/software/solaris/binaries/get.html
The documentation for the disksuite package can be found at docs.sun.com
ct

Installing disksuite 4.2.1

Similar Messages

Maybe you are looking for