InstallMultiplePackagesSolaris10Installing Go from source The Go Programming Language. Introduction. Go is an open source project, distributed under a. BSD style license. This document explains how to check out the sources. Most users dont need to do this, and will instead install. Getting Started. a much simpler process. If you want to help develop what goes into those precompiled. In Oracle Solaris 10, Oracle Solaris Zones technology gave you the ability to create different isolated environments to suit the needs of your particular applications. There are two official Go compiler tool chains. This document focuses on the gc Go. For information on how to work on gccgo, a more traditional. GCC back end, see. Setting up and using gccgo. The Go compilers support eight instruction sets. There are important differences in the quality of the compilers for the different. A mature implementation. Comparable to the amd. Install Go compiler binaries. The Go tool chain is written in Go. To build it, you need a Go compiler installed. The scripts that do the initial build of the tools. Hardening Solaris with Jass. By Sen Boran www. Solarishardening4. This article presents a concise stepbystep approach to securely. SAP BusinessObjects Data Services 4. Supported Platforms Solaris 64bit SAP COMMUNITY NETWORK SDN sdn. BPX bpx. sap. com BOC boc. UAC. Supports Linux, Free. BSD, Net. BSD, Open. BSD and Darwin binaries. Less widely used than the other ports. AArch. 64. Supports Linux and Darwin binaries. New in 1. 5 and not as well exercised as other ports. Power. PC big and little endian. Supports Linux binaries. New in 1. 5 and not as well exercised as other ports. MIPS big and little endian. Supports Linux binaries. New in 1. 8 and not as well exercised as other ports. MIPS big and little endian. Supports Linux binaries. New in 1. 6 and not as well exercised as other ports. IBM System z. Supports Linux binaries. New in 1. 7 and not as well exercised as other ports. Install Multiple Packages Solaris 10' title='Install Multiple Packages Solaris 10' />Except for things like low level operating system interface code, the run time. The compilers can target the Dragon. Fly BSD, Free. BSD, Linux, Net. BSD, Open. BSD. OS X Darwin, Plan 9, Solaris and Windows operating systems. XAMPP is an easy to install Apache distribution for Windows, Mac OS X, Linux and Solaris. The package includes the Apache web server, MySQL, PHP, Perl, a FTP server. The full set of supported combinations is listed in the discussion of. See the main installation page for the overall system requirements. The following additional constraints apply to systems that can be built only from source. For Linux on Power. PC 6. 4 bit, the minimum supported kernel version is 2. Go does not support Cent. OS 6 on these systems. Install Go compiler binaries. The Go tool chain is written in Go. To build it, you need a Go compiler installed. The scripts that do the initial build of the tools look for an existing Go tool. GOROOTBOOTSTRAP. If unset, the default value of GOROOTBOOTSTRAP. HOMEgo. 1. 4. There are many options for the bootstrap tool chain. After obtaining one, set GOROOTBOOTSTRAP to the. For example, GOROOTBOOTSTRAPbingo should be. To use a binary release as a bootstrap tool chain, see. Go distribution. To build a bootstrap tool chain from source, use. Go 1. 4 source code plus accumulated fixes. Go 1. 4 was the last distribution in which the tool chain was written in C. After unpacking the Go 1. Windows, make. bat. To cross compile a bootstrap tool chain from source, which is. Go 1. 4 did not target for. Go on a different system. When run as for example. GOOSlinux GOARCHppc. GOOSGOARCH. combination, leaving the resulting tree in. GOOS GOARCH bootstrap. That tree can be copied to a machine of the given target type. GOROOTBOOTSTRAP to bootstrap a local build. To use gccgo as the bootstrap toolchain, you need to arrange. GOROOTBOOTSTRAPbingo to be the go tool that comes. For example on Ubuntu Vivid. GOROOTBOOTSTRAPusr. Install Git, if needed. To perform the next step you must have Git installed. Check that you. have a git command before proceeding. If you do not have a working Git installation. Cheetah 3D Serial Mac more. Git downloads page. Optional Install a C compiler. To build a Go installation. Go. programs to import C libraries, a C compiler such as gcc. Do this using whatever. To build without cgo, set the environment variable. CGOENABLED0 before running all. Fetch the repository. Go will install to a directory named go. Change to the directory that will be its parent. Then clone the repository and check out the latest release tag. Where lt tag is the version string of the release. Optional Switch to the master branch. If you intend to modify the go source code, and. Otherwise, skip this step. To build the Go distribution, run. To build under Windows use all. If all goes well, it will finish by printing output like. ALL TESTS PASSED. Installed Go for linuxamd. Installed commands in homeyougobin. You need to add homeyougobin to your PATH. For more information about ways to control the build, see the discussion of. Go. which can take more time than simply building Go. If you do not want to run. Testing your installation. Check that Go is installed correctly by building a simple program. Create a file named hello. Printfhello, worldn. Then run it with the go tool. If you see the hello, world message then Go is installed correctly. Set up your work environment. Youre almost done. You just need to do a little more setup. How to Write Go Code. Learn how to set up and use the Go tools. The How to Write Go Code document. Go tools. The source code for several Go tools including godoc. To install all of them, run the goget command. Or if you just want to install a specific command godoc in this case. To install these tools, the goget command requires. Git be installed locally. You must also have a workspace GOPATH set up. How to Write Go Code for the details. Note The go command will install the godoc. GOROOTbin or GOBIN and the. GOROOTpkgtoolGOOSGOARCH. You can access the latter commands with. The usual community resources such as. Freenode IRC server. For those who wish to keep up to date. Go repository. Bugs can be reported using the Go issue tracker. Keeping up with releases. New releases are announced on the. Each announcement mentions the latest release tag, for instance. To update an existing tree to the latest release, you can run. Where lt tag is the version string of the release. Optional environment variables. The Go compilation environment can be customized by environment variables. None is required by the build, but you may wish to set some. The root of the Go tree, often HOMEgo. X. Its value is built into the tree when it is compiled, and. There is no need to set this unless you want to switch between multiple. The value assumed by installed binaries and scripts when. GOROOT is not set explicitly. It defaults to the value of GOROOT. If you want to build the Go tree in one location. GOROOTFINAL to the eventual location. GOOS and GOARCH. The name of the target operating system and compilation architecture. These default to the values of GOHOSTOS and. GOHOSTARCH respectively described below. Choices for GOOS are. Mac OS X 1. 0. 8 and above and i. OS, dragonfly, freebsd. Choices for GOARCH are. ARM, arm. 64 6. ARM. Power. PC 6. 4 bit, little endian, ppc. Power. PC 6. 4 bit, big endian. MIPS 6. 4 bit, little endian, and mips. MIPS 6. 4 bit, big endian. MIPS 3. 2 bit, little endian, and mips MIPS 3. The valid combinations of GOOS and GOARCH are. GOOSGOARCHandroidarmdarwin. GOHOSTOS and GOHOSTARCH. The name of the host operating system and compilation architecture. These default to the local systems operating system and. Valid choices are the same as for GOOS and. GOARCH, listed above. The specified values must be compatible with the local system. For example, you should not set GOHOSTARCH to. The location where Go binaries will be installed. The default is GOROOTbin. After installing, you will want to arrange to add this. PATH, so you can use the tools. If GOBIN is set, the go command. GO3. 86 for 3. 86 only, default is auto detected. This controls the code generated by gc to use either the 3. SSE2 instructions set to sse. GO3. 863. 87 use x. Pentium MMX or later. Mirroring Disks with Solstice Disk. Suite. Introduction. This paper will present a short introduction to mirroring two disks using. Solstice Disk. Suite. Although not as robust as Veritas Volume Manager. Vx. VM also distributed by Sun as the Sun Enterprise Volume. Manager SEVM, Disk. Suite is nonetheless still a popular choice for doing. This tutorial will be presented using an actual. Note that the following procedure is for Disk. Suite 4. 2, which runs on. Solaris 2. 6 and Solaris 7. This procedure will also work with Disk. Suite. 4. 2. 1, distributed with Solaris 8. Solstice Disk. Suite is now known as. Volume Manager in Solaris 9 and later. There are a few fundamental. The terms Disk. Suite and Solaris Volume Manager are both used in this. Where necessary, specific versions will be pointed out. The first step to setting up mirroring using Disk. Suite is to install. Disk. Suite packages and any necessary patches for systems prior to Solaris 9. SVM is part of the. Solaris 9. The latest recommended version of Disk. Suite is 4. 2 for systems running Solaris 2. Solaris. 7, and 4. Solaris 8. There are currently three packages and one patch necessary to install. Disk. Suite 4. 2. They are. SUNWmd RequiredSUNWmdg Optional GUISUNWmdn Optional SNMP log daemon1. The packages should be installed in the same order as listed above. Note. that a reboot is necessary after the install as new drivers will be. Solaris kernel. For Disk. Suite 4. 2. 1, install the following packages. SUNWmdu CommandsSUNWmdr DriversSUNWmdx 6. Bit DriversSUNWmdg Optional GUISUNWmdnr Optional log daemon configsSUNWmdnu Optional log daemon. For Solaris 2. 6 and 7, to make life easier, be sure to update your. PATH and MANPATH variables to add Disk. Suites. directories. Executables reside in usroptSUNWmdsbin and. SUNWmdman. In Solaris 8, Disk. Suite. files were moved to normal system locations usrsbin so. The Environment. In this example we will be mirroring two disks, both on the same. The first disk will be the primary disk and the second will. The disks are. Disk 1 c. Disk 2 c. 0t. 1d. The partitions on the disks are presented below. There are a few items of. Each disk is partitioned exactly the same. This is necessary to. Slice 2, commonly referred to as the. There are situations where slice 2 is used as a normal slice. The three unassigned partitions on each disk are configured to each be. MB. These 1. 0MB slices will hold the Disk. Suite State Database Replicas, or. More information on the state database replicas will. In Disk. Suite 4. In SVM, they occupy 8. MB. This can lead to many problems during an upgrade if the. The Database State Replicas. The database state replicas serve a very important function in. Disk. Suite. They are the repositories of information on the state and. A logical device created through. Disk. Suite is known as a metadevice. Having multiple replicas is critical. Disk. Suite. There must be a minimum of three replicas. Disk. Suite requires at least. Replicas should be spread across disks and controllers where. In a three drive configuration, at least one replica should be on each. In a two drive configuration, such as the one we present here, there. If there were only three. Disk. Suite to function and the system would panic. Here we will create our state replicas using. The a and f options used together create the. The a option attaches a new database. Initializing Submirrors. Each mirrored meta device contains two or more submirrors. The meta. device gets mounted by the operating system rather than the original. Below we will walk through the steps involved in creating. Here we create the two submirrors for the. The first two commands create the two submirrors. The f. option forces the creation of the submirror even though the specified. The second two options 1 1. In a mirroring situation, this should always be. Finally, we specify the logical device that we will be. After mirroring the root partition, we need to run the. This command will update the root entry in. Ommitting this step is one of. Disk. Suite. If. you do not run the metaroot command before you reboot, you. Next, we continue to create the submirrors and initial one way mirrors for. Updating etcvfstab. The etcvfstab file must be updated at this point to reflect. The partition will have already been. The entries in the file will look something like the following. Notice that the device paths for the disks have changed from the normal. The system can now be rebooted. When it comes back up it will be running. Use the df command to verify this. In the next step we will attach the second half of the mirrors and allow the two. Attaching the Mirrors. Now we must attach the second half of the mirrors. Once the mirrors are. The progress of the synchonization. To attach the. submirrors, issue the following commands. With an eye towards recovery in case of a future disaster it may be a. Open Boot PROM. OBP device alias to ease booting the system if the primary disk. In order to find the physical device path, simply do the. This should return something similar to the following. SUNW,fas3,8. 80. Using this information, create a device alias using an easy to remember. To create this alias, do the following. Open Boot PROM. ok nvalias altboot sbus3,0SUNW,fas3,8. For more information on creating OBP device aliases, refer to the. Tech. Note Modifying. CD ROM nvalias on an Ultra 1. IDE based System slacksite. It is now possible to boot off of the secondary device in case of failure. OBP. For more information on Disk. Suite, including configuring metatrans devices. Additional Solstice Disk. Suite Topics slacksite.