Solaris 8 on SS5

I currently run Solaris 2.5.1 on my SS5, does anyone think I will have problems running Solaris 8 on a SS5?
Thanks!
Matt

Matt,
Usually, Solaris 8 will run on the same system that runs Solaris 2.5.1. But you must have the appropriate Hard Drive space available and atleast 64mb of RAM.
Follow this link for more information:
http://www.sun.com/software/solaris/binaries/specs.html
Thanks,
Allen
Sun Developer Technical Support

Similar Messages

Sys-suspend fails on Solaris 9 with tape drive present

I ran across a post by T. Kloeber (http://forum.java.sun.com/thread.jspa?threadID=5109999&messageID=9374786) on the Sun developer forum on this.
I replaced my Solaris 7 SS5 with an Ultra 2 and installed Solaris 9 fresh. The external disks and tape drive are unchanged. The SS5 used to suspend properly about 95% of the time, but now the machine refuses to suspend with the tape drive connected. Log messages are:
Mar 21 16:20:13 madera cpr: [ID 535284 kern.notice] System is being suspended
Mar 21 16:20:24 madera cpr: [ID 122848 kern.warning] WARNING: Unable to suspend device st@4,0.
Mar 21 16:20:24 madera cpr: [ID 537702 kern.warning] WARNING: Device is busy or does not support suspend/resume.
Mar 21 16:20:30 madera cpr: [ID 457896 kern.notice] NOTICE: Suspend operation failed.
Mar 21 16:20:30 madera cpr: [ID 583038 kern.notice] System has been resumed.
and the system is not suspended. Is there anything i am missing on Solaris 9?
I am able to modunload the st driver, then when I attempt to suspend, the driver gets reloaded, and I get the failure above.
I ran across an E10000 service manual from 2.6 days that said that tape devices were not suspendable. They must have rethought that by Solaris 7. No idea why 9 should refuse this. I have the latest recommended patches.
TIA for any information!
TW

I ran across a post by T. Kloeber (http://forum.java.sun.com/thread.jspa?threadID=5109999&messageID=9374786) on the Sun developer forum on this.
I replaced my Solaris 7 SS5 with an Ultra 2 and installed Solaris 9 fresh. The external disks and tape drive are unchanged. The SS5 used to suspend properly about 95% of the time, but now the machine refuses to suspend with the tape drive connected. Log messages are:
Mar 21 16:20:13 madera cpr: [ID 535284 kern.notice] System is being suspended
Mar 21 16:20:24 madera cpr: [ID 122848 kern.warning] WARNING: Unable to suspend device st@4,0.
Mar 21 16:20:24 madera cpr: [ID 537702 kern.warning] WARNING: Device is busy or does not support suspend/resume.
Mar 21 16:20:30 madera cpr: [ID 457896 kern.notice] NOTICE: Suspend operation failed.
Mar 21 16:20:30 madera cpr: [ID 583038 kern.notice] System has been resumed.
and the system is not suspended. Is there anything i am missing on Solaris 9?
I am able to modunload the st driver, then when I attempt to suspend, the driver gets reloaded, and I get the failure above.
I ran across an E10000 service manual from 2.6 days that said that tape devices were not suspendable. They must have rethought that by Solaris 7. No idea why 9 should refuse this. I have the latest recommended patches.
TIA for any information!
TW

Solaris 8 Install on SS5

Hey there,
I just got the full version of Solaris 8. I am trying to install it on my SPARC 5. I am using a Sun Bootable CDROM drive, which works fine. It boots and asks me stuff about the swap and can it be written as the first partition, then i say yes. It seems to try to format it and then says format failed. What does this sound like? Bad HDD? Thanks for helping!
Matt

Matt,
It sounds like there could be problems with your Hard Drive. Try booting the system with a DOS Bootable floppy and running the format command manually:
format c:
Thanks & Revert back,
Allen
Sun Developer Support

Solaris 2.6 download cd

sorry for posting in this topic but I can't find other for my problem. I loast my installation cd's that came with my sparcstation ipx and sparcstation 5. the hard drives crashed on both of them first ipx and then ss5. on ipx I put a "new" hdd with debian and on ss5 I wantt to put solaris 2.6. I can't find it anywhere on sun site. I can put debian on ss5 but I want to stay with solaris.
Can anyone post a link or tell me from where to get it?

Solaris 2.6(SPARC) was never available as a download.
It was always a commercially produced media kit, of disks and books, that you needed to buy.
Downloadable CD images began with Solaris 8, if I recall correctly.
You will need to search other sources for what you need.
Perhaps an online auction site vould provide a used copy, such as Ebay ??

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

Logical interface in solaris 10

Hi there,
I need to configure logical interface in a solaris 10 3/05 server. After reading the Solaris 10 IP services manual, I am not quite sure what to do. All the examples and explanation are about using the new subcommand addif of ifconfig. It was not clear in the documentation if the setting logical interfaces via addif will persist across boot.
Can one still configure logical interface in Solaris 10 in a more traditional way like in Solaris 8? In an Solaris 8 server I will do the following.
Let's assume I want to configure in a solaris 8 server a logical interface named hme0:1 with IP address 192.168.20.28 with netmask 255.255.255.0 for hostname host001
# cat /etc/hostname.hme0:1
host001
^D
# echo "192.168.20.28 host001" >> /etc/inet/hosts
# echo "192.168.20.0 255.255.255.0" >> /etc/inet/netmasks
# reboot -- -r
Can one still do that in solaris 10 3/05 server?

Hi there,
I need to configure logical interface in a solaris 10
3/05 server. After reading the Solaris 10 IP services
manual, I am not quite sure what to do. All the
examples and explanation are about using the new
subcommand addif of ifconfig. It was not clear in the
documentation if the setting logical interfaces via
addif will persist across boot.No. No 'ifconfig' command is persistent.
Can one still configure logical interface in Solaris
10 in a more traditional way like in Solaris 8? In an
Solaris 8 server I will do the following.
Let's assume I want to configure in a solaris 8
server a logical interface named hme0:1 with IP
address 192.168.20.28 with netmask 255.255.255.0 for
hostname host001
# cat /etc/hostname.hme0:1
host001
^D
# echo "192.168.20.28 host001" >> /etc/inet/hosts
# echo "192.168.20.0 255.255.255.0" >>
/etc/inet/netmasks
# reboot -- -r
Can one still do that in solaris 10 3/05 server?Absolutely.
You don't need to reboot (you can run ifconfig for this boot and let the files do the work next time) and the -r doesn't do anything with interfaces (expecially virtual interfaces) anyway.
Darren

Installation problem on Solaris

I am trying to install sun one 7.0 on Solaris 8. The install is failing with this error:
ERROR - library load failed with following error: Can't load library: /opt/SUNWappserver7/lib/libinstallCore.so
INFO - End core server uninstallation
anyone know what causes this??
cheers

Looks like Solaris package installation failed and installer reverted to uninstallation sequence. For low level pkgadd log please check /var/sadm/install/logs/Sun_ONE_Application_Server_install.B<timestamp> file (timestamp is date and time of your installation attempt in mmddHHMM format).
Look for any errors in this file. Most likely thing that could have happened is that the installation of Java Help (SUNWjhrt) package failed because you didn't have existing package based J2SE installation on the system. If that's the case, workaround is to either preinstall package based J2SE installation or to selected option to install bundled J2SE that comes with application server.

Installation problem on Solaris 10

Dear All,
We are trying to install j2sdk 1.4.2_13 on solaris server zone. I have downloaded j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin
But when I try to execute this:
#./j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin
It gives me error: The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag
Tried with -console:
The wizard cannot continue because of the following error: Invalid command line option: console is not supported (10
01) (403)
WARNING: could not delete temporary file /tmp/ismp001/2599368
WARNING: could not delete temporary file /tmp/ismp001/6183226
WARNING: could not delete temporary file /tmp/ismp001/1222839
Then tried with -silent:
This time command just completed w/o any output at all.
Please suggest what can I do?
regards, Sean.

Dear Siddhesh,
Thanks for your reply.
I tried using X Manager GUI for my Solaris. But when I double click the j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin file to run it, it simply denies saying:
The filename "j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin" indicates that this file is of type "Unknown type". The contents of the file indicate that the file is of type "Shell script". If you open this file, the file might present a security risk to your system.
Do not open the file unless you created the file yourself, or received the file from a trusted source. To open the file, rename the file to the correct extension for "Shell script", then open the file normally. Alternatively, use the Open With menu to choose a specific application for the file.
Also /tmp has full authorizations:
drwxrwxrwt 7 root sys 557 Jun 24 08:34 tmp
I dont have Hummingbird for X11 forwarding with this client. Do I have any other option??
regards, Sean.

New to Solaris, Some Samba and NTFS issues.

Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/samba/log/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
passdb backend = smbpasswd
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/sfw/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/sfw/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Series]
comment = TV Series
path = /home/Kirby/Series
public = yes
only guest = yes
writable = yes
printable = no

875739 wrote:
Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.I never had a need for it but I think you'll have to compile fuse ntfs-3g manually.
http://web.archiveorange.com/archive/v/u46DbWSGcIzl7pexf4hQ
>
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.You don't need to use Samba in Solaris 11 Express.
http://download.oracle.com/docs/cd/E19963-01/html/821-1448/gaynd.html#gayne

Error while creating a Solaris Resource

I got the following error while creating the following solaris resource:
Test connection failed for resource(s):
Solaris: Script failed waiting for "ASSWORD:" in response "_,)#+(:" ==> com.waveset.util.WavesetException: Script processor timed out with nothing to read and the following unprocessed text: "_,)#+(:".\n
I have the sudo permissions for the following commands:
(ALL) NOPASSWD: /usr/bin/auths, /usr/sbin/groupadd, /usr/sbin/groupdel, /usr/sbin/groupmod, /usr/bin/last, /usr/bin/listusers, /usr/bin/logins, /usr/bin/passwd, /usr/bin/profiles, /usr/bin/roles, /usr/sbin/useradd, /usr/sbin/userdel, /usr/sbin/usermod, /usr/bin/ypmatch, /usr/bin/ypcat, /usr/bin/ypasswd, /usr/bin/awk, /usr/bin/cat, /usr/bin/chmod, /usr/bin/chown, /usr/bin/cp, /usr/bin/cut, /usr/bin/diff, /usr/bin/echo, /usr/bin/grep, /usr/bin/ls, /usr/bin/mv, /usr/bin/rm, /usr/bin/sleep, /usr/bin/sort, /usr/bin/tail, /usr/bin/touch, /usr/bin/which
Please let me know what could be the problem?

This doesn't look like a Sun Directory Server issue. You may want to post this to another forum.
Regards,
Ludovic.

Error ora-15081 (and several others) while creating a new db in Solaris

Hi all,
OS: Solaris 11
DB: 11.2.0.3.5 (2 node rac)
While creating a new db on a Solaris 11 env, via dbca, the following stack error appeared to me:
ORA-19624: operation failed, retry possible
ORA-19870: error while restoring backup piece path[...]
ORA-19504: failed to create file "+MYDG"
ORA-00372: file cannot be modified at this time
ORA-15196: invalid ASM block header [kfc.c:19572] [1] [257] [0 != 821602346]
ORA-15081: failed to submit an I/O operation to a disk
ORA-15066: offlining disk "dsk_0001" in group "MYDG" may result in data loss
ORA-06512: at SYS.X$DBMS_BACKUP_RESTORE, line5827The dbca (ran as oracle user) aborts at 15%.
There are a lot of errors in this stack, and i'm not pretty sure which error is the main cause of this issue, but I think it's the "ORA-15081: failed to submit an I/O operation to a disk" that is the bad guy here. I did some researches and found that some possible sollutions:
1) One said that this error might be caused by bad permissions on the raw devices used in the "MYDG" diskgroup (i'm using 6 devices with external redundancy), but my devices are all with the grid:asmadmin and 660 permissions
2) Another said that this might be a problem with the owner:group of the oracle binaries. In ny installation the oracle binaries ($ORACLE_HOME/bin) are with the oracle:oinstall. I thougth of addind the asmadmin group to the oracle user, but i'm not sure what are the implications of this change. What do you thing?
What am I doing wrong and how can i solve it?
Thanks in advance for your pacience and attention.

Here follows the output:
NAME                           MOUNT_S     HEADER_STATU MODE_ST STATE    GROUP_NUMBER PATH
DG02HML_0000                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                                  00500d0s0
DG02HML_0001                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                                  00502d0s0
DG02HML_0002                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                                 00504d0s0
DG02HML_0003                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                               00506d0s0
DG02HML_0004                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                                  00508d0s0
DG02HML_0005                   CACHED MEMBER       ONLINE NORMAL              3 /dev/rdsk/c0t60060E8005487F000000487F000                                                                                  0050Ad0s0

How to create HP LaserJet 2420 printer queue on Solaris 10

Hi Solaris Gurus,
I am having difficulty creating a printer queue for HP LaserJet 2420 on Solaris 10 (11/9) Sparc (Sun Fire T5220) server. A popular method used is with hppi (HP Jet Direct) tool but it does not have the exact printer driver and alternative printer drivers (e.g. HP LaserJet 4 / 4M, HP LaserJet 2000 series) resulted in only part of the text occupying the wrong side of an A5 page.
An alternative approach that has worked in the past for simple default paper tray 2 (single paper tray), with tray 1 reserved for manual feed. This method involves creating a working printer queue on a Windows workstation (XP) / server (2000) with the correct driver and having configured to support Unix printing to receive LPR request from Unix systems in general. A remote printer queue would then be defined on Solaris 10 system which points to the Windows system. However, the printing jobs kept going to tray 1 (top manual feed) even though the Windows printer queue was configured to go to tray 3 (bottom tray).
The earlier method would be simplest but needs the right driver (PDD) but I don’t know where to find it. The latter approach is also not working despite having got the right driver on Windows. A test page on the target Windows printer queue would print to tray 3 (bottom tray) of the printer correctly.
Printmgr does not work well with HP printers from experience. It is good for serial and local printers.
Your advice would be much appreciated.
Thanks,
Crystal

Hi Giogio, and welcome to the HP Forums.
I am sorry to be the bearer of this news, but do the age of the printer, it is not supported by Mac OS X 10.9. I am including a list below of the supported printers from Apple:
OS X: Printer and scanner software available for download.
For more information, I would recommend contacting the Apple Support Communities.
Thank you for posting on the HP Forums.
Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
Jamieson
I work on behalf of HP
"Remember, I'm pulling for you, we're all in this together!" - Red Green.

PMTU discovery in IPv6 based on IPV6_RECVPATHMTU in Solaris 10

Our application works with raw sockets and needs to discover PMTU of IPv6 paths.
According to the RFC-3542 (http://tools.ietf.org/html/rfc3542, section 11) the socket option IPV6_RECVPATHMTU allows applications to know about the change of path MTU by receipt of new ancillary data item (IPV6_PATHMTU) which is delivered to recvmsg() without any actual data. Following construction should be used to enable this option:
int on = 1;
setsockopt(fd, IPPROTO_IPV6, IPV6_RECVPATHMTU, &on, sizeof(on));In the online Sun documentation I found that this socket option is supported since Solaris 10 (http://docs.sun.com/app/docs/doc/816-5177/ip6-7p).
However, in our test this socket option appears to be not working. After decrease of the PMTU via ifconfig and sending a big enough packet an ICMP (Packet Too Big) is received but there is no event with ancillary data item on the socket.
One peculiarity that may be essential is that our application binds to a specific port in a raw socket (i.e. to IP address : port pair).
Does anyone have information if the IPV6_RECVPATHMTU socket option is really supported in Solaris 10?
Probably, ICMP should be off to be able to receive this event with ancillary data on the socket?
Will appreciate any ideas how to make it working.
Thanks in advance,
Mike.

Hi,
I have a Sunfire V100 - and have the exact same problem. The settings are correct; I have configure dual-NIC cards many times in the past - but this issue is simply eluding me. I can swap in a Linux machine in router / ip forwarding mode and there are no problems, but when I put back in the Sunfire I encounter the same issues you have.
In effect, packets from the LAN arrive at the NIC on the Solaris machine, but then don't get forwarded to the other NIC's gateway. I'm at a loss, but I have seen this problem pop-up (without answer) a half-dozen times in this forum alone, and multiple times on different support sites. Did you (or anyone) ever come across a solution for this? Is this not some easily overlooked yet possibly cryptic flag or variable that I've missed? Anyone?

Solaris: OC4J: 9.0.2.0.0 or 9.0.3.0.0

I'm a bit puzzled as to versioning of oc4j running applications created with Jdeveloper RC2 / BI Beans RC2 .
I downloaded a file called oc4j_extended.zip (of 25. March).
I would have thought this to be the latest distro of oc4j.
When I invoke the oc4j.jar, I receive a message like this:
"Oracle9iAS (9.0.2.0.0) Containers for J2EE initialized"
I see other people are running version 9.0.3.0.0, and most Jdeveloper references are for this version as well.
Is there a later version (for Solaris) that I need to download/install?
If so, where can it be found?
Or am I fine running with the one I have?
(Reason for asking is that I am running into problems that could possibly be related to versioning.)
Jens

Thanks for quick response, I am located in Norway, 6 hours in front of the US, so days can easily be "wasted" waiting for you guys. Maybe we'll manage to squeeze in 2 answers today ;-)
Here are the answers to your question:
myhost% java -version -jar oc4j.jar
java version "1.3.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
myhost% java -jar oc4j.jar -version
Oracle9iAS (9.0.2.0.0) Containers for J2EE
myhost% java -jar ./oc4j.jar -version
Oracle9iAS (9.0.2.0.0) Containers for J2EE
This is a bit complicated, but here's a quick resume of what I did:
* Install Oracle 9.0.1.0.0, including the http-server.
* Patch to 9.0.1.2.0
* download oc4j_extended, unzip to a new $ORACLE_HOME/oc4j
* Source the following file:
myhost% more java131.sh
setenv PATH /usr/j2se/bin:/u01/app/oracle/product/901/bin:/bin:/usr/bin:/usr/cc
/bin:/etc:/opt/bin:/usr/ucb:.:/usr/openwin/bin:/usr/openwin/lib
setenv CLASS_PATH /usr/j2se/lib:/u01/app/oracle/jre/1.1.8/lib:/u01/app/oracle/p
oduct/901/jlib:/u01/app/oracle/product/901/wmt/jlib
setenv CLASSPATH /usr/j2se/lib:/u01/app/oracle/jre/1.1.8/lib:/u01/app/oracle/pr
duct/901/jlib:/u01/app/oracle/product/901/wmt/jlib
alias java="/usr/j2se/bin/java"
myhost%
* Check that the right java verson is running:
myhost% which java
/usr/j2se/bin/java
myhost%
* start the oc4j server with :
java -Xmx256m -Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB -Dorg.omg.COR
BA.ORBSingletonClass=com.inprise.vbroker.orb.ORB -jar oc4j.jar
And it reports back v. 9.0.2.0.0
So what am I doing wrong?
Any input will be appreciated.
Jens

Install of 9201 on Solaris 9

I am getting this same error on install of 9201 on Solaris 9 ; ld is core dumping - I have all of the required packages so I can't figure out why linking is failing, can anybody please give me a fix?!!?
Calling action unixActions2.2.0.6.0 make
installMakePath = /usr/ccs/bin/make
installMakeFileName = /opt/oracle/product/plsql/lib/ins_plsql.mk
installTarget = install
undoMakeFileName =
installArguments = ORACLE_HOME=/opt/oracle/product,
/opt/oracle/product/install/make.log
undoTarget =
Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target install of makefile /opt/oracle/product/plsql/lib/ins_plsql.mk
Exception Severity: 1
*** Cancel Dialog: ***
User selected: Stop installation of all products.
Error in invoking target install of makefile /opt/oracle/product/plsql/lib/ins_plsql.mk

Hello,
a) Please crosscheck your environment variables and make sure you have access to all binaries/executables.
Ex: make etc.
b) Make sure you OS is patches as per oracle requirements.
<<Message>>
Error in invoking target install of makefile /opt/oracle/product/plsql/lib/ins_plsql.mk
Indicates that you may not have access to execute make utility.
-Sri

Solaris 8 on SS5

Similar Messages

Maybe you are looking for