Skip to main content

Disclaimer

Disclaimer for solaris-ville

If you require any more information or have any questions about our site's disclaimer, please feel free to contact us by email at atul.khiste291@gmail.com

Disclaimers for solaris-ville

All the information on this website - https://solaris-support.blogspot.com - is published in good faith and for general information purpose only. solaris-ville does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this website (solaris-ville), is strictly at your own risk. solaris-ville will not be liable for any losses and/or damages in connection with the use of our website. Our Disclaimer was generated with the help of the Disclaimer Generator and the Disclaimer Generator.

From our website, you can visit other websites by following hyperlinks to such external sites. While we strive to provide only quality links to useful and ethical websites, we have no control over the content and nature of these sites. These links to other websites do not imply a recommendation for all the content found on these sites. Site owners and content may change without notice and may occur before we have the opportunity to remove a link which may have gone 'bad'.

Please be also aware that when you leave our website, other sites may have different privacy policies and terms which are beyond our control. Please be sure to check the Privacy Policies of these sites as well as their "Terms of Service" before engaging in any business or uploading any information.

Consent

By using our website, you hereby consent to our disclaimer and agree to its terms.

Update

Should we update, amend or make any changes to this document, those changes will be prominently posted here.

Comments

Popular posts from this blog

Setting up X11 Access to the Solaris GUI Gnome Desktop

How to   access the GUI desktop environment on a Solaris 11 SPARC server from Windows, MAC, Solaris or Linux desktop computer. As most of the time SPARC based servers are installed using the Oracle Solaris 11 Text  Installer (installing the solaris-large-server group of software packages), the desktop  environment is not installed (mostly to keep the system lightweight) . So the only option for connecting remotely to the server is with an SSH client and a command line interface  (Known as Terminal). Most widely used software to connect to a command line is Putty. For beginners , who haven’t worked on any unix/linux system , it takes time to adjust to the commands and syntax of terminals (The so called black screen).   Installation Overview To accomplish our task   we will   follow these three steps: 1. Install the Gnome desktop environment on our SPARC server. Note – If we use the text installation method, the Oracle Solaris Desktop package (solar...

AWK one liners [part one]

AWK was initially developed in 1977 by Alfred Aho , Peter J Wienberger  and Brian Kernighan. And hence the name(AWK) derived from  their respective initials. AWK was designed basically for text processing and used mostly for  extraction  a nd manipulation of data. For more info  :  visit here Lets start with the examples. 1. Print Specific Column from a file sample file created awk '{print $1 "   " $3}' abc.txt awk '{print $1 "   " $3}' abc.txt 2. Print all data from a table awk '{print $0}' abc.txt

Ldom Backup & Restore

1. Login to control Domain and list the current configuration file. bash-3.2# ldm list-spconfig basic_configuration new_configuration [current] 2.To take the complete LDOM configuration backup use below command. # ldm list-constraints -x >config.xml 3.You can also  take the configuration backup for specific LDOM # ldm list-constraints -x ldom_name > ldom_name.xml How to restore the system to factory default  1. Login to the control domain console and remove the spconfig profile. bash-3.2# ldm ls-spconfig basic_configuration new_configuration[current] bash-3.2# ldm  remove-spconfig new_configuration bash-3.2# ldm ls-spconfig basic_configuration [next poweron] 2.Power cycle the server to take the changes effect. bash-3.2# init 5 -> show /SYS   Properties:         type = Host System         ipmi_name = /SYS         keyswitch_state...