Thai font support on solaris 2.6 sun os 5.6 sparc for java application

how to install new fonts on solaris 2.6 sparc sun os 5.6. what are the necessary changes we have to make inorder to use new fonts in a java application. the requirement is to install thai language fonts that will be used by a java application to print online/batch job using text/postscript documents. advise on how to do it. kindly mail me at <[email protected]>
thanks in advanse

It is recommended for you to upgrade the JDK version to the J2SE 1.2.x versions which provides better support for the Thai fonts.
You can download the localised version of Thai JDK 1.2.x for Solaris from :
http://www.sun.com.sg/developers/thailand/index.html

Similar Messages

Does iBooks author and iBooks support thai fonts?

I ,live in Thailand,want to create books by using iBook author but from what i've know iBook only support one font for THAI language, is it true or not.
Also does iBooks author support modifed thai font from the internet?
Last one, can I use .ibooks for limited usage not for public?
Thank you for your answer

The iPad only has one Thai font, Thonburi, and you cannot embed other fonts using iBook Author. Here is some info about using other apps
http://www.pigsgourdsandwikis.com/2011/04/embedding-fonts-in-epub-ipad-iphone-an d.html

Are there some Font supporting all utf-16 code including all supplementary?

Are there some Font supporting all utf-16 code including all supplementary code?
In an application, I need to show some text encoded in utf-16, which is multilingual and
Have some of supplementary character, so want to know a font to show it correctly? While find nothing from the internet, so anybody can instruct me will be very appreciated！Looking forward to your response, thanks.
Message was edited by:
passenger2007

Probably not. you might find some fonts listed her that support what you are interested in.
http://www.google.com/search?q=font+that+supports+all+unicode+characters

How to check actual allocated and used memory for java process in solaris?

Hi,
I'm testing performance for java application on solaris 10. And I would like to know how to measure actual memory allocated and used for java process.
I'm setting -Xms512m -Xmx512m for my java process and I use prstat command to monitor it's memory. But I found that when I run prstat to check, in SIZE column is more than I setting (found 644).
So I'm don't know the actual memory that java process used. (In this case,is it mean the process use memory (644) more than setting (512)?)
Thank you.

With Xms/Xmx you specify the Java heap size. On top of that comes the permanent generation (default max size 64m) and the C part of the process (the JVM itself with all its libraries and data).
With "ps -e -o pid,vsz,rss,args" you get the virtual and set resident size of your processes.
Nick.

Supporting Environment for WebDynpro applications

Hi All
Please let me clarify my doughts...
1) In local machine where all webdynpro applications stored...I mean I wnat to know path.
2) who(Developer/Administrator) will deploy the webdynpro components and what is the process to deploy webdynpro components in to SAP Enterprise portal.
3) In support environment which tools willbe used to give support for applications, which are developed using webdynpor technology.
I mean how the tickets will be handled,,I worked for some days in java, where in that environment i have used remedy tool to get tickets from the clients.
4) In local environment how can we run and deploy webdynpro applications...
5) Can we use make utility for webdypro applications as we can use for java applications..
Thanks
Seshu..

Hey Seshu
1>By default it'll be in
C:Documents and Settings<user>.dtc
2>FYI we dont deploy applications in EP, we deploy in the J2ee engine and portal just a component on top of the java engine.
An Administrator can deploy the applications developed.
or anyone can deploy applications knowing the SDM password
3> am not clear on wat tickets u spekin
4>you need to deploy once in the server and then run the application throught he url generated after deploying.
5>need more clarity..
[Still More Details|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/29fd0ec7-0301-0010-359f-9f50928528db]
regards
Harish
`

Does Photoshop CS3 Extended support Thai fonts?

I am translating some short text in Photoshop to several Asian languages. I noticed just with the Thai language, that I get a series of X's with boxes instead of Thai characters. The characters are fine in other applications, including Flash CS3. Other than taking a screenshot in another app and pasting into Photoshop, does anyone know of a workaround? Should I install a particular Thai font that is supported by Photoshop? I am running Photoshop CS3 Extended on Windows XP. Thanks for any help.

So in my search, the only thing I found was a utility downloadable at CNET http://download.cnet.com/ASK-Square-Free-Version/3000-2316_4-10855142.html
"ASK Square works efficiently with well-known graphic software such as Adobe Photoshop 7, CS, CS2, CS3 and CS4. It enables users to use of all Thai characters. Users can type all Thai characters, even troublesome characters like. This software also corrects excessively high vowels while typing or after typing just by only one click. Further more it can transform illegible font to normal font that happens when changes a texts font, to a readable normal font. If users copy texts from external application such as word processing or spreadsheet software and paste those texts into their graphic software, ASK Square software can correct the wrong-encoded texts automatically.
ASK Square is flexible. It enable user to type Thai non-unicode font on Adobe Photoshop. Version 1.5.0.10 supports Adobe Photoshop CS4."
Funny thing is you can tell their sales pitch was loosely translated. I gave it a try anyway. The instruction PDF was in Thai, their website was in Thai. But I felt brave anyway, seeing as I googled this application title and didn't see anything negative written about it. Then I go to the application icon in the system tray. As you can see from my screenshot, it ain't exactly user-friendly.
Bottom line... it didn't work. Anyone out there have a solution? I've searched everywhere... Am I the only one with this problem?

Generating GUIDs, RPC DCE support on Solaris

Hallo!
I want to build a C/C++-Class which generates "Global Unique Identifiers" on Solaris and on WinNt.
On WinNt I can use RPC DCE for this.
Questions:
(1) How to genereate an Global Unique Identifier on Solaris?
(2) Is there and RPC DCE support on Solaris?
Thanks,
Alois Blaimer
[email protected]

It is recommended for you to upgrade the JDK version to the J2SE 1.2.x versions which provides better support for the Thai fonts.
You can download the localised version of Thai JDK 1.2.x for Solaris from :
http://www.sun.com.sg/developers/thailand/index.html

Installation of Solaris 10 on SUN Sparc M4000

Hi
I am trying to install Solaris 10 on SUN SPARC M4000.
Here is the error I have:
+Enter filename [kernel/sparcv9/unix]: /platform/sun4v/kernel/sparcv9/unix+
+Enter default directory for modules [platform/sun4v/kernel /kernel /usr/kernel]:+
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
Program terminated
It seems that version of Solaris I trying to install is not support by the Hardware, when I use another Solaris 10 DVD, it works...
But the problem is that I need to install this Solaris version because others softwares are depending on that.
If someone knows how to make this installation possible, it will be very helpfull.
Thanks in advance.
BR
Racine

Minimum Supported
Solaris[tm] Operating Environment Versions for the M4000 are as follows
OpenSolaris 2009.06
SPARC64 VI:
10 - 11/06 (U3) plus required patches (minimum)
10 - 08/07 (U4) (recommended)
SPARC64 VII:
10 - 08/07 (U4) plus required patches (minimum)
10 - 5/08 (U5) (recommended)
A full matrix for the M4000 which details the minimum patch requirements to support the h/w is available from https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1145383.1

JNI FC1063 HBA support on solaris 10

Hi ,
I have upgraded Solaris 9 to Solaris 10 using Live upgrade.Server is SUN fire V880 and the HBA is JNI FC1063.
After upgrading ,I am not able to see the FC LUNS .
Does The JNI Fc1063 HBA has support on Solaris 10.
Thanks

I would beg to differ on this response. This is not a service call and the storage vendor is not responsible for making decisions on what the customer is allowed or not allowed to use.
EG, I have a Sun StorEdge 9990 (actually a HDS USP 1100 and not the 9990 Lightning series which is on the web site) and I made the call to put the Fibre Channel HBA's of my choice into my systems and I also chose the Cisco 9509 switches. Both HDS and Cisco put out documentation regarding compatibility of the HBA's.
So, I would suggest RPS check out the Brocade website or sales people and ask them if they recommend anything.
http://www.brocade.com/products/pdf/Fabric_Aware_Compatibility_Matrix-060521.pdf
states that the option X6768A is supported for Solaris 10.
Sun 9980 will work on most of the HBA's available in the system handbook.
The could be either the rebadged Qlobic or JNI HBA's. You could even use Emulux if you are that way inclined.
My systems are full of dual channel HBA's such as SG-XPCI2FC-QF2.
You should also be aware that the 1280 has only one 66 MHz PCI slot. You can upgrade the I/O boat to all 66 MHz slots if you are after good throughput. The upgrade will also give the opportunity to use the 4 Gb HBA if you can find a system to use them on.
Stephen

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

Level of ACPI support with Solaris 10?

What is the current level of ACPI support with Solaris 10 x86? I have been searching forums and Sun documentation and I have not found an official answer to this question from Sun. I have seen posts in which people state what they "think" they know or they know how something worked with "their" system but nothing official from Sun. I assume there is some support for ACPI because the eeprom command can be used with the acpi-user-options. Can I just enable ACPI support on my motherboard and let Solaris 10 Update 3 do the rest? Thanks for the help?

I found this site that seams to answer this question.
http://blogs.oracle.com/jsavit/entry/ours_goes_to_11_features

USB Video Class Driver on Solaris 10 and Sun Ray

Hello,
Is it posible to use the USB Video Class Driver (usbvc) on Solaris 10 and Sun Ray?
How can I do that?
Thank you very much.

It's not possible. The Video Class requires isochronous operation on USB and Sun Ray does not support isochronous mode.
Even if Sun Ray did support isochronous mode, the libusb library (which is what third-party applications use to interact with USB devices attached to Sun Ray) does not support isochronous transfers. The hard part is the Sun Ray itself. When that gets resolved it probably won't be very hard to add isoc support into libusb.

Thai fonts in FM8

Can anyone please tell me how to fix this problem? I created a manual in Thai (BrowalliaUPC font) in FM7. When I open it in FM8, it turns to gibberish, no matter what Thai font I use. Does FM8 not support Thai fonts? I no longer have FM7 on my computer, and need to update this manual.

Without having used Thai fonts, I think:
When you moved to FM 8, you also moved to a Unicode environment; the documents you created in 7 were not Unicode, so the manner in which you insert characters probably changed. I recall seeing other problems with people who had to switch environments, but I'm unsure if there's an easy solution.
Based on Microsoft's www site for BrowalliaUPC, it also looks as if there are two versions of the font in the field, and they seem to have different levels of Unicode support. If you're using the 2.2 version of the font, you may want to get the version 5 shipped with Vista and 7 to get the expanded support.
To see if there's also something going on with the operating system / environment, I'd suggest creating a new FM 8 fle and seeing if you can insert content with the Thai font... or if that's also twisted.

OpenInstaller is only supported on Solaris 9 or later error

I was trying to install java 1.6 version on an Solaris machine During install it failed with the following error message "openInstaller is only supported on Solaris 9 or later" since the Solaris version on this machine is 5.8
As per the sun download page, it was mentioned like supported version is Solaris 8,9 and 10.
http://www.java.com/en/download/help/5000010600.xml
My Solaris machine version is 5.8
./java_ee_sdk-6u1-jdk-solaris-sparc.sh
extracted: install/metadata/view/jwsdp_5.png
extracted: install/metadata/view/jwsdp_6.png
extracted: install/metadata/view/jwsdp_7.png
extracted: install/metadata/view/updatetool.xml
openInstaller is only supported on Solaris 9 or later
Could you please let me know what is the issue and how to resolve this issue.
Thanks,
Ricks

bumping this up in hopes of an answer....
it appears that the jar installer works fine, the problem is with .bin installers only.....
in install docs found proposed solution of "use df compatible with used posix" - that must be a joke, right ??
we're supposed to replace df that comes with OS with some version that works with posix used by the installer ?? Really ?@?@?

[bug report] 1.0.3 firmware wipes out Thai font Display

I got 4th Gen iPod nano, with a fair Thai font display from 1.0 to 1.0.2
but after I tried to update a new firmware to 1.0.3 last night, it wipes away Thai font Display. All song and artist names in Thai are all gone and I have no choice but clean restore again to 1.0.3
The song and artist names are working after I freshly have a clean restore but, then, after try adding more songs, the Thai text display ability is all gone again.
Now I climb down and let it back downgrading to 1.0.2
Please let me know if this issue could be passed to iPod fireware development team
Thank you

Thanks, Whisp.
As Tom said, there is no menu languages option for Thai, but the iPod will do support Thai Display.
and it is now not working on 1.0.3
More info, I have discussed with other users in Thai forum, they also have the same problem just like me. They can solve this by reset the iPod, however, the bug will repeat every time if they add songs into iPod.
I'm not too sure this bug effects the other foreign language display so.

Thai font support on solaris 2.6 sun os 5.6 sparc for java application

Similar Messages

Maybe you are looking for