Installing Solaris 8 as a second OS

I have Solaris 8 and want to install it on my pc I am already running windows 98se, I believe you have to partition the hard drive to run the 2 os. If any one could tell me how to partition my hard dirve and any tips for installation from there that would be great. If the there are any websites on this matter i would be grateful if you let me know.

Hey, goto http://math.uwb.edu.pl/~mariusz/dualboot/ and that will answer all your dual boot questions.

Similar Messages

Can I install solaris on a second hard drive?

I am completely new to Solaris. My computer runs Windows XP as its primary OS and I have a second (slave) hard drive that I would like to install Solaris 10 on. Does the installation DVD for x64 architecture automatically handle this kind of installation? Is this process possible? If it is, will I have to manually configure the BIOS to boot each OS every time I change my current OS, or will some sort of GUI dialogue come up? I would like information on this subject and if possible, step-by-step instructions.

Tottaly agree with the last post. Check if your hardware is in HCL, there is a free program you can download from Sun Download page, you burn it to CD and reboot, then it will provide you with all needed information. And if something is not in the list, you will get a hard time seting it up (there are a lot of unofficial drivers). So as an example: networkcard will be hard to install and set up. So check first.
As from my experiense conserning instalation, I would suggest to do so:
(in a way as the last post)
prepare a clean partition, or backup files on a HD. run the instalation, once you will reach the point when it will ask you how to install (Normal or Custom) choose custom, then it will go to several questions concerning where on a HD to install, thats where you can choose partitions and so on.
Just as a reminder: you dont need alot of space for Solaris to work properly, plus there not so much software which requires big amount of HD. So for OS and nice package for development you will probably need tops 10Gb.

Strange problems after installing Solaris 10 u6 on 64-bit PC

Hi all,
I have run into some very strange issues after installing Solaris 10 update 6 on my 64-bit PC (it's almost new). The problems are with graphical applications and desktop environments based on GTK (so it seems, at least).
I have installed Solaris normally, following most of the default options and choosing the "Entire Group" software packages installation. However, after the first login I've seen that:
1. No user creation process was offered to me and I had to login as root (I find it pretty strange)
2. After logging in as root into JDK system, my screen went blank for a couple of seconds and then the system threw me back to the login screen.
3. Logging into the old CDE environment was possible, but launching Firefox from there (using a command line terminal) wasn't. It gave me the following error message:
ld.so.1: firefox-bin: fatal: libmlib.so.2: open failed: no such file or directory
ld.so.1: firefox-bin: fatal: relocation error: file /usr/bin/firefox/firefox-bin: symbol gtk_init: referenced symbol not found.
It's very strange because GTK toolkit and JDK environment are supposed to be the core functionalities provided by Solaris. Does anyone have an idea what's going on?
My system sum-up:
CPU: Intel Core 2 Quand Q6600 @ 2.4 GHz
RAM: 2 Gb of DDR2 SDRAM
Motherboard: MSI MS-7529 (Intel G31 chipset)
Monitor: AOC LM725
Graphics card: NVIDIA GeForce 9400 GT
Hard disk: 2 Western Digital HDs (SATA) 320 Gb each,
1 Western Digital external USB HD MyBook Essential 2, 500 Gb
DVD drives: 2 LG DVD drives (SATA)
Network card: Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
I use my system in the following way:
On the first hard disk, I have a one-partition 32-bit Windows XP SP3 installation (ported from my old computer).
On the second hard disk, I have a functioning Fedora Core 9 installed on the first half of the disk's space (the installation is self-organized into several Linux partitions, e. g. /boot, /swap etc; I am a newbie so I don't know too much about Linux partitioning - only specified to Fedora how much space it could use for its volume group). I installed Solaris onto the second half of the second disk.
It has be noted that my USB external drive seemed to conflict with the network or graphics cards during the Fedora installation and caused it to hang sporadically, so I installed Fedora with this disk detached. I also detached it when I was installing Solaris, though it seems to have not influenced the problems I experienced. I also have attempted installing Solaris before I did so with Fedora, but had the same issues.

Well, it seems that the cause of the problem was that my DVD image was just corrupted - I didn't check it vs MD5 codes supplied by Sun assuming it went automatically OK. I downloaded the image again (this time it was OK), reinstalled the system and successfully logged into JDS. However, I am still puzzled why Solaris doesn't offer to create a default non-root user during the installation process.

How to Install Solaris for Intel so that it boots off from a boot floppy?

Hi all,
Sorry to bother you with this one (I went through all documentations/manuals and could not find straight answers to following
specific questions):
I have one hard drive with 1st partition used by Windows XP and a second partition that's a blank FAT 32 (using Partition Magic)
I want to use for Solaris for Intel.
My very specific questions:
(1)That blank Fat32 partition: can I run the Solaris install over it ..or should I absolutely make sure that it's a blank UFS formatted
partition? I am asking you that because all manuals (except one) pretend that I can run my Solaris install on a blank Fat partition...
but I believe that documentation at multiboot.solaris-x86.org stresses that if the partition is not a blank UFS one, it wont install Solaris
(2)As you already know, some Oses like Linux or FreeBSD can be installed on a partition and be booted off a boot floppy.
So without that boot floppy, no trace of the OS. How can I do that with Solaris for Intel. I want my Solaris to boot off a boot floppy only.
BTW, I currently have Solaris 7 for Intel.
Thanks for the answers.

(1)That blank Fat32 partition: can I run the Solaris install over it ..or should I absolutely make sure that it's a blank UFS formatted You can install Solaris to that blank FAT32 drive but Solaris WILL convert it to UFS BEFORE doing the install. In other words, after the install it will be UFS and not FAT32 anymore.
So without that boot floppy, no trace of the OS. How can I do that with Solaris for Intel. I want my Solaris to boot off a boot floppy only.Not that I know of. Some people have reported booting Solaris off of a USB drive though.
alan

Installing Solaris as a guest OS on VirtualBox-1.6.0

I am using VirtualBox-1.6.0 as my VM on an AMD ATHLON 1800+ with 1GB RAM running Fedora 9 (uname -r = 2.6.25.3-18.fc9.i686). My first attempt to install Solaris was with Solaris10 11/06, while the second attempt was with Solaris10 05/08.
Solaris10 11/06: 1. Default screen resolution created a window too long with the bottom off screen.
Is there a recommended resolution when the host screen resolution is 1440x900?
2. Guest Additions failed to install properly
What is the appropriate method for installing the Guest Additions for Solaris?
Solaris10 05/08: 1. Install hangs when installing as a networked system at system 77% initialized prior to the actual install.
2. Install hangs when installing as a non-networked system when system is at 100% complete and about to reboot. I manually powered off the VM
unmounted the DVD image and then restarted the VM. When it rebooted, it complained that there wasn't a system on the hard drive.
In both installs, I went with the default config of the VM (512MB RAM, 8MB Video RAM, creating a dynamic virtual disk starting at 20GB limit), and the install media were iso's, 11/06 5 CD iso files and 05/08 1 DVD iso file.
TIA
Scott
Edited by: Bad2theBone on May 30, 2008 10:37 AM

Just redid the install of Solaris10 11/06 and this time I was able to change the size of the window so that it is within my desktop. I am running 32 bit apps as my AMD processor is only 32 bit, also I originally went with the CDE desktop and later switched to JDE. I was also able to install the Guest Additions for Solaris this time without any errors using pkgadd from the cli. I haven't retried the 05/08 version yet, but will post when I do. One thing in common with 11/06 and OpenSolaris.200805 is that the audio on my system does not work on either VM VBox 1.6.0. It reports that it cannot find any compatible device. It also complains about the UART device, although I don't have Serial Ports enabled. Also does anyone know how to tell VBoxSvr what host name to use with each VM?
Fri. 27 June 2008
I was able to install Solaris10u5 (05/2008) on VMware Server using 684MB of RAM and 20GB HDD. I did not have the tools addition for Solaris, I'm not even sure if there is such an animal, so I had to "Scroll the desktop" to maneuver around. I then tried it again on VirtualBox 1.6.2, got through the initial install setting RAM to 684MB, default Video no Serial ports or USB, although parts were painfully slow. I was not able to do the first reboot, it just sat there saying that it was doing system initialization and the indicator just kept on going back and forth. After about 20 min. I shutoff the VM giving up. Also I still can't get sound to work on either the older Solaris10 or OpenSolaris. In OpenSolaris the DDU indicates that 2 drivers are missing;
Audio; Intel 82801AA AC'97 Audio Controller
Other; ACPI AC Device
Anyone know if and when VBox or OpenSolaris will have these drivers?
Edited by: Bad2theBone on Jun 27, 2008 8:45 PM

Resource Conflict Warning (ACPI/NON-ACPI devices) while installing solaris

Hi,
I am trying to install Solaris 8 on my system.
Intel Celeron 1.7 Ghz
128 MB RAM
Gigabyte 8LD 533K Motherboard with Intel Chipset.
While installing, the second installation screen titled "Bus
Enumeration" gives the following warning.
Warning: Resource Conflict:
ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown)
NON-ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown,
which are different from the ones shown under the ACPI device list)
I ignored the message and pressed F2 key as suggested.
The next screen "Solaris Boot" comes and after choosing the CD (as
the target from which the OS is to be installed), The next screen
comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. No matter which option I choose, the
system shows 2-3 messages, and even before I can read them, the
system reboots. Thus I am unable to install Solaris.
I searched on Google and as one person had suggested tried tweaking
the BIOS. (Disable APM etc). But it did not work, because I don't
have an option that specifically gives the Disable/Enable option for
APM. I get the Advanced Power Management screen, but it shows some
different options.
I spoke about this problem with a friend who has some experience on
Solaris and he put the CD Drive and the Hard Disk on two different
buses, but it didn't help. I still get the same message.
I would be very grateful if someone could suggest a method so I can
install Solaris.
Regards,
pmu

The next screen comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. At this screen, type
b kadb -v
instead of choosing 1) or 2). Now you should be able to read the error messages from the kernel that
prevent booting into Solaris.

Installing Solaris 9 on 1850r w/SmartArray 221

I am in the midst of attempting to install Solaris 9 x-86 on a Compaq Proliant 1850r with a SmartArray 221 RAID controller. As Compaq has not released any drivers for Solaris 9 for intel, I was forced to try to use the Solaris 8 SmartArray driver for the 221 controller. The install program accepts the Solaris 8 221 driver during the first part of the install. It finds the array, and begins copying files to it. However at the end of the GUI portion of the install, after it has successfully written to the drives, the setup program opens a window prompting me to re- insert the driver diskette. When I put in the disk containing the smartii driver which setup recognized, and successfully used to write to the disks earlier in the install, I get a message informing me that the smartii driver is not located on the disk. I have repeated the procees, re-downloaded the driver disk, also tried with the solaris 7 x-86 driver all with the same result. Has anyone found a way to make this work? Please post any solutions to this issue. Thanks

I had exactly the same problem trying to install Solaris 9 x86 onto a Compaq ML530 with a SmartArray 431 controller.
The problem is that Compaq haven't updated the drivers for Solaris 9. So, for the driver to work on the Solaris 9 install you will have to make some changes to the DU diskette.
The reason that the installer cannot find the driver on the diskette the second tome around, is that it is looking for the 2.9 version of the driver and not the 2.8 version of the driver that is on the diskette.
What you have to do is to rename the a: \DU\sol_28 directory on the diskette, to a:\DU\sol_29
Next you have to edit the a:\DU\release.def file and change the number 28 in that file to the number 29
Having done these two things, the installer should now accept the Driver on the diskette and you should be able to complete the installation successfully.

Installing Solaris 8 CD 2/2.

I am successful in creating and installing the "Solaris 8 Jumpstart CD" 1of 2. However, I am unable to install CD 2of 2 from the console. When I run the "installer" command under /cdrom/sol_8_202_sparc_2, I get the install GUI and the program goes for "LIVE UPGRADE" rather than installing Solaris OE 2/2. Is there a way to install the second CD after installing the "Custom Jumpstart CD".

The Solaris 8 2/02 CD 2 of 2 Product Installer has changed from previous Solaris 8 updates where the installer was located in /cdrom/sol_8_1001_sparc_2 (/cdrom/cdrom0 under vold control). There is an installer still located in this directory, however this is the Live Upgrade installer.
The new location of the Solaris CD2 Product Installer (solaris2) is located in /cdrom/sol_8_202_sparc_2/Solaris_8/Tools/Installers (/cdrom/cdrom0/Solaris_8/Tools/Installers).
This change is documented in the Solaris 8 2/02 Installation Release Notes p/n 816-2413-10 and on AnswerBook in the "Solaris 8 2/02 Update Collection" under "Solaris 8 (SPARC Platform Edition) 2/02 Release Notes" under the title "Solaris 8 Software 2 of 2 Installation Program Does Not Automatically Start When Using Custom JumpStart or re-preinstall (4556860)"
This problem is not an issue when installing interactivly from CD-ROM (boot cdrom), but when invoking Custom JumpStart from CD-ROM (boot cdrom - install).
Execute the installer as follows:
# cd /cdrom/cdrom0/Solaris_8/Tools/Installers
# ./solaris2
Regards,
Chris

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)>

Lot of troubles (impossible) installing Solaris 10 on VMware Workstation 6

Hi, i'm experiencing troubles trying to install Solaris 10 x_86 (the last release) on VMware Workstation 6.
During the creation of the virtual machine I selected Solaris 64bit (I'm running an Intel Core2Duo CPU), selected the first ISO image and boot up the virtual machine. The installation of the first cd went just fine.
During the installation of the second cd, at a certain percent (sometimes ~50%, or later) the virtual machine reboots: I select the first choice on grub menu, but Solaris tolds me that something about the root repository (I don't remember well) is out of sync, and suggest me to reboot in failsafe mode and repair it; I did it and reboot...Doing this way I installed the second cd, but for the third (it happened the same -reboot- problem) it didn't work:
after fixed the repository in failsafe mode, and after reboot it doesn't start the installer, and shows this message:
http://img469.imageshack.us/my.php?image=solarishangsoi3.png
Please help me! I don't really know where/what I'm doing wrong...
Thanks really a lot for any help.
Regards
Gabriele

Simply Great, I had to Reboot the OS and I went to Failsafe mode where it went to single user mode and ask to update boot_archive, that worked.
When i Shutdown and Rebooted the System i could see system booting nicely and then it gave me bunch of Errors.
I think i will go and Do a Fresh Install again :(

Unable to install Solaris 10 for intel on IDE hard disk?

I was trying to install solaris on an 80 GB IDE HDD with
AMD 32 bit ,XP2000 cpu, 1024 MB RAM using a DVD rom
drive with the first/second solaris os install CD.
BUT after 2nd CD , i got the message 'Short Read/Read Error'
after the GRUB boot loader screen.
Repeated after formatting disk using Red Hat linux (linux installed successfully on same disk/machine without problems) but even then
when i retried installing solaris 10, it failed with same error.
Same set of CDs installed successfully on intel xeon server with
1 GB RAM, 32 GB SCSI HDD.
Does solaris install on IDE hard disks on intel 32 bit PCs?
pl help/

Sometimes it's possible to use drivers for older Solaris x86 systems
to install the latest Solaris x86 release.
http://h18023.www1.hp.com/support/files/server/us/family/model/2543.html?submit.y=0&submit.x=0&lang=en&cc=us
To do that, you have to modify HP's ITU floppy. For Solaris 10 x86,
rename the DU/sol_2X directory on HP's floppy to DU/sol_210 .
See also:
http://forum.sun.com/thread.jspa?threadID=22200&messageID=68765

Hard disk problem after installing Solaris 10 u5 on a Sun Ultra 24

Hi.
After receiving a new Sun Ultra 24, shipped with Solaris 10 u4, the first thing I did was installing Solaris 10 u5. X wouldn't start but that was not a big problem and installed it in text mode. Installation went fine but, when the system starts, a single beep is heard and after some seconds some warning message appear on the console, before the "Hostname: ..." message, informing that some read operation on my hard disk had timed out and were aborted. The system then starts up normally. The only other anomaly is that the diagnostic partition in unbootable.
I ran the hard disk tests from the tools and drivers CDs and all of the tests were passed. Solaris 10 u4 was working normally so I'm wondering if this may be a bug.
Thanks for your help,
Enrico.

Thanks anyway, I discovered what the problem was: a bug in Solaris 10 u5:
http://opensolaris.org/jive/thread.jspa?threadID=58768&tstart=75
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6536722
Thanks,
Enrico

How install Solaris 2.5.1 and Windows Together

Hi, We�ve a registered copy of Solaris 2.5.1 and we can�t install solaris and windows in the same Hard disk.
I�ve been trying since two weeks. I can�t found a document that help me with this task.
Please, help me with the directions to do that or try to indicate me an internet link to read it.
Thanks a lot.

OK, this is that I did.
1. With solaris 2.5.1. boot disk install solaris from CDROM
2. I do the partition in hard disk, the disk has 3 GB, and make a 940 MB partition for solaris and the rest for Windows
3. I install solaris in stangalong mode
4. When I finished solaris installation, it ask me wich partition are going to use to boot de machine.
5. I format a WINDOWS disk partition to install it.
6. I transfered the system to the windows partition
7. Reboot the machine and the solaris still ask me by wich O/S are going to use to boot.
8. Then, install Windows 95 B version, and when rebbot the machine, the boot manager of salaris dissaper.
9. With FDISK of windows and put the second partition (solaris) as active, and nothing happens.
Note: I`m using the solaris partition as second one, i mean that the main partition is Windows (is exactly that I did have it).

Help me in Installing Solaris Express, Developer Edition X 86

Hi,
Help me in installing Solaris Express, Developer Edition
When i am trying to install Solaris, system hangs and the moniter is switcher off when the system goes in GUI mode.
i have intel 945GTP mother board with as on board Intel Graphics Media Accelerator Drives , Chipset -> Intle 945G , 160 SATA Hard Disk, 1 GB DDR2 Ram , P4 3.Ghz Processer , on board Intel PRO/100 VE Network Card.
Please,Help me.
Thanking you,
P.Sathish Kumar

Hello,
first of all: Try to run the HCTS (Hardware
Compatibility Test Suite) first, it's available
here:
http://www.sun.com/bigadmin/hcl/hcts/device_detect.htm
l
This you can run from Windows, and it will list all
hardware that has drivers, and all those, that do not
have drivers (including some public domain drivers).
After that, you have the possibility to install
Solaris WITHOUT a GUI, use one of the two "terminal"
modes. The first Is still a GUI, as it only starts X
and opens a terminal, in which then the installer
runs. The second does NOT start X, but runs the
installer on the console. Try this one, and once you
get through that, you can afterwards figure out the
settings of the Xserver.Hi ,
i have installed the solaris using console.
Still GUI is not starting, the moniter is switched off when GUI gets started
I used Hardware Compatibility Test Suite, its say that system is supported
by Solaris.
Should i have change BIOS setting to stated the system
Bye
P.Sathish Kumar

Help me in installing Solaris Express, Developer Edition X86

Hi,
Help me in installing Solaris Express, Developer Edition
When i am trying to install Solaris, system hangs and the moniter is switcher off when the system goes in GUI mode.
i have intel 945GTP mother board with as on board Intel Graphics Media Accelerator Drives , Chipset -> Intle 945G , 160 SATA Hard Disk, 1 GB DDR2 Ram , P4 3.Ghz Processer , on board Intel PRO/100 VE Network Card.
Please,Help me.
Thanking you,
P.Sathish Kumar

Hello,
first of all: Try to run the HCTS (Hardware
Compatibility Test Suite) first, it's available
here:
http://www.sun.com/bigadmin/hcl/hcts/device_detect.htm
l
This you can run from Windows, and it will list all
hardware that has drivers, and all those, that do not
have drivers (including some public domain drivers).
After that, you have the possibility to install
Solaris WITHOUT a GUI, use one of the two "terminal"
modes. The first Is still a GUI, as it only starts X
and opens a terminal, in which then the installer
runs. The second does NOT start X, but runs the
installer on the console. Try this one, and once you
get through that, you can afterwards figure out the
settings of the Xserver.Hi ,
i have installed the solaris using console.
Still GUI is not starting, the moniter is switched off when GUI gets started
I used Hardware Compatibility Test Suite, its say that system is supported
by Solaris.
Should i have change BIOS setting to stated the system
Bye
P.Sathish Kumar

How to install Solaris 8 as the third OS?

Hi all
I'll appreciate anyone who could guide me how to install Solaris 8 in my PC which runs on an Intel Pentium III
Currently, I've installed Windows 2000 on the first partition, Red Hat 7.2 on the second partition. Only the first partition is primary, the second is logical partition. However, I don't use LILO as the boot manager. I use Window's boot manager instead.[I modified the boot.ini a little bit]
Now, I want to install Solaris 8 which can be installed on a Intel processor, on the third partition. However, I heard that it's very difficult to install Solaris so that I really need your advices from all of you. Thanks a million!
Best regards,

Hi,
I am also dealing with the same. For these three to sit, in your case, create a partition from fdisk of Linux which can be identified by solaris8. Then when you startoff installing solaris8, the OS should be in a position to capture that partion. If that won't happen, using Solaris8 fdisk is very dangerous. You can not preserve your old data. Try this way.

Installing Solaris 8 as a second OS

Similar Messages

Maybe you are looking for