Sponsored Content
Operating Systems Solaris OpenSolaris instead Sun Solaris Post 302373655 by jlliagre on Saturday 21st of November 2009 09:21:26 AM
Old 11-21-2009
Install that script somewhere and run it once at login. The latter can easily be automatized. eg: add the script at the end of a custom Xstartup:

Code:
mkdir /etc/dt/config
cp Xstartup /etc/dt/config
vi /etc/dt/config/Xstartup
... # <- append slovenianKeyboard.sh content at the end of the script

 

3 More Discussions You Might Find Interesting

1. High Performance Computing

Solaris 10 and OpenSolaris : Web Based Management tools and Sun Cluster installation

Gurus, I have several questions : 1. Does Solaris 10/OpenSolaris has some kind of web based management tools ? Currently I am using WebMin. It worked fine, however I am very curious to use the tools provided by Sun Microsystem. Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies

2. Solaris

Installing OpenSolaris on Sun v120

I have come into my possesion a v120 server at work that was decommisioned from another project. I don't have the Solaris Installation CD nor do I have root or any user credentials on this server. My goal was to install OpenSolaris on this server and use it as a playground for learning UNIX... (6 Replies)
Discussion started by: stringzz
6 Replies

3. Solaris

Sun Studio 11 in OpenSolaris

Install Sun Studio 11 on OpenSolaris 2009.06 When run IDE - system return error: touch: cannot change times on /export/home/iktomy/.sunstudio/11-SunOS-i386/system/dontshowisw: Permission denied /opt/SUNWspro/prod/scripts/jdk_chooser: line 131: cat: command not found... (0 Replies)
Discussion started by: Iktomy
0 Replies
MAKESH(1)						      General Commands Manual							 MAKESH(1)

NAME
makeSH - a .SH script maker SYNOPSIS
makeSH files DESCRIPTION
MakeSH examines one or more scripts and produces a .SH file that, when run under sh, will produce the original script. The .SH script so produced has two sections containing code destined for the output. The first section has variable substitutions performed on it (taking values from config.sh), while the second section does not. MakeSH does not know which variables you want to have substituted, so it puts the whole script into the second section. It's up to you to insert any variable substitutions in the first section for any values you want from config.sh. You should run makeSH from within your top-level directory and use the relative path to the file as an argument, so that the "Extracting ..." line printed while running the produced .SH file later on will give that same path. AUTHOR
Larry Wall <lwall@netlabs.com> SEE ALSO
pat(1), metaconfig(1), makedist(1). BUGS
It could assume that variables from metaconfig's Glossary need to be initialized in the first section, but I'm too lazy to make it do that. LOCAL MAKESH(1)
All times are GMT -4. The time now is 06:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy