SysAdmin Blog, TechTips and Reviews
Optimized Open Source Software Stack (Cool Stack) 1.3.1 Final Release…
Will be installing Ruby on Rails using Cool Stack… this is the first of sets of post.. Now downloading the packages from Sun.com
Optimized Open Source Software Stack (Cool Stack) for the Sun Solaris Operating System(TM). Cool Stack is a collection of some of the most commonly used open source applications optimized for the Sun Solaris OS. By using these binaries you will enjoy the best levels of performance from your system, while also reducing your time-to-service.
Instructions: Select the files you want, then click the “Download Selected with Sun Download Manager” (SDM) button below to automatically install and use SDM (learn more). Alternately, click directly on file names to download with your browser. (Use of SDM is recommended but not required.)
Once you have a non-global zone installed or running on a Solaris 10 installation, it is often useful to connect to the console of the zone. This provides the same control over the zone as connecting to the console of a physical server running Solaris.
To connect to the console of a Solaris 10 zone called testzone, use the following command as root or the equivalent on the global zone:
zlogin -C testzone
The -C option specifies a console login. The console login will persist when the zone is rebooted.
To exit zlogin, use the escape sequence ~. on a new line (the tilde must follow a carriage return, not any other character). If this escape character is inappropriate (because you are connected using software like tip that also uses this escape sequence), you can specify a different escape character on the command line. For example, to use the @ symbol, use:
zlogin -C -e @ testzone
In this case, to exit the zlogin console session, type @. on a new line
Just a note of reference, if you are using tip and forget to change the escape character above. you can do the following to get out
~~.
This will force it to disconnect the local zlogin instead of the tip…
—-
However, let’s go deeper….
If you logged into a container’s console (via chs000xx —> ILOM —> then to a serial console)..
#. – will exit to ILOM (but once you logged in again.. you’re in container’s console)
~. – will exit to chs000xx (but once you logged in again.. you’re in container’s console)
~~. – WILL EXIT from the Container!!
It’s a like an hierarchy thingy..
(first part was taken from a website… later part was from me.. of course if you didn’t read all of it, you wont see this note.. 
)
http://sysadmindayph.com/
Another quikie copy/paste kind of thingy…
You may set your search path automatically each time you log in, by placing the appropriate “set path” command in your “.login” file.
(To learn more about the .login file, type “help dotlogin”.) Here is a sample of a command line that you might put in your .login file to set a non-standard search path:
set path = ( $path /usr/ucb /bin /usr/bin /usr/new .)
I am subscribe to the official Sun Microsystem newsletter and I got this one directly from my inbox that I want to share to every Solaris SysAdmin out there:
This How-To Guide instructs users, system administrators, and developers unfamiliar with Solaris 10 OS on consolidating applications onto a single server using Solaris Containers technology. The guide starts with a brief overview of Solaris Containers and follows with an example of using Solaris Containers to consolidate two Web server applications and an email server application onto a single server. Users are guided step-by-step through the consolidation process, with code examples and illustrations.
After using this guide, a user should be able to create Solaris Containers by:
* Creating a resource pool
* Defining Solaris Zones
* Assigning CPU usage with the Fair Share Scheduler (FSS)
* Installing and booting a zone
* Configuring access to raw devices from the zone
Here’s what we did today on one of our Solaris box that is worth mentioning on this cool super system administrator’s blog ‘o mine! (Don’t you find it cool that SysAds are so funny?!)
Anyhoo, today we re-jumpstarted a laboratory box because the ‘owner’ of it wants it back. Since we pretty much messed it up, I have to jumpstarted a fresh copy.
After installing returned the original /etc/shadow and /etc/passwd back from backup (had a backup file on the laptop).. but unfortunately, the /etc/shadow file is ‘null’.
Restoring File From UFSdump Backup
Here’s the procedure in restoring a particular file from ufs dump backup… Of course if you’re restoring from ufs backup you probably made a ufs backup in the first place, right? Right!
In this example, the files backup.examples and junk are restored from the pubs directory: