howto:solaris:install
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
howto:solaris:install [2012/01/18 12:15] n3mmr |
howto:solaris:install [2013/01/10 17:35] (current) zip |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | The below procedure installs | + | ====== How to install |
| - | It will likely work just as well, with possibly minor details changed, on Solaris | + | |
| + | === Note that, Solaris or OpenIndiana or any other Solaris descendant, is NOT Linux === | ||
| + | <fc # | ||
| + | Most of the visible differences occur in admin software, but a few quirks exist in userland, too. | ||
| + | And the package system is aggressively different. | ||
| + | Still, most any Java library is likely to run w/o any problem, and most Linux software | ||
| + | can be automatically transformed to run in Solaris descendants. | ||
| + | And, given its heritage, Solaris makes for very good and reliable servers. //</ | ||
| + | |||
| + | The below procedure installs serviio as a service under SMF in Openindiana v 151a and later. | ||
| + | It will likely work just as well, with possibly minor details changed, on Solaris 10 or 11, Nexenta and OpenSolaris b134 (possibly earlier versions too). | ||
| - | First, make sure you have the appropriate supporting SW installed: | + | The serviio console should normally be started from a separate copy of serviio, given the below setup. |
| + | In most useful cases, this is anyway the case, since you want serviio running on a server machine, and you run the console from another machine, say your laptop. | ||
| + | **First, make sure you have the appropriate supporting SW installed: | ||
| ffmpeg 0.9.1 with rtmp-support, | ffmpeg 0.9.1 with rtmp-support, | ||
| http:// | http:// | ||
| - | from where you can install using the IPS installer, pkg, of your openindiana | + | from where you can install using the IPS installer, pkg, of your OpenIndiana |
| - | Then get the linux tar distro, and extract | + | **Get the distro and install |
| - | Now test it by running it manually: | + | Download the serviio linux tar distro, and extract |
| - | prompt> | + | Create a group " |
| + | |||
| + | **//<fc #0000FF>prompt> | ||
| + | |||
| + | and a user " | ||
| + | |||
| + | **//<fc # | ||
| + | |||
| + | On my system, 103 was free in both cases, and one might as well use the same number for both. | ||
| + | |||
| + | Now, make sure the / | ||
| + | **//<fc # | ||
| + | prompt> cd /usr/local; chown -R serviio: | ||
| + | //** | ||
| + | |||
| + | Now test it by running it manually, as user serviio: | ||
| + | |||
| + | <fc # | ||
| + | **//<fc # | ||
| + | </ | ||
| + | **//<fc #0000FF> | ||
| prompt> ./ | prompt> ./ | ||
| - | prompt> ./ | + | </ |
| + | **//<fc # | ||
| + | prompt> ./ | ||
| Enter the correct address to bind to explicitly on the Status panel, and save. | Enter the correct address to bind to explicitly on the Status panel, and save. | ||
| Line 27: | Line 60: | ||
| Make sure serviio is stopped! | Make sure serviio is stopped! | ||
| - | Now create | + | **Lastly, define |
| - | + | ||
| - | prompt> groupadd -g 103 serviio | + | |
| - | + | ||
| - | and a user " | + | |
| - | + | ||
| - | prompt> useradd -u 103 -g 103 -d / | + | |
| - | + | ||
| - | On my system, 103 was free in both cases, and one might as well use the same number for both. | + | |
| - | + | ||
| - | Now, make sure the / | + | |
| - | + | ||
| - | prompt> cd /usr/local; chown -R serviio: | + | |
| - | + | ||
| Save the xml text found at the end of this page in a file " | Save the xml text found at the end of this page in a file " | ||
| - | + | **// | |
| - | prompt> pfexec svccfg validate ~serviio/ | + | <fc #0000FF>prompt> pfexec svccfg validate ~serviio/ |
| - | prompt> pfexec svccfg import ~serviio/ | + | </ |
| + | **//<fc #0000FF> | ||
| + | prompt> pfexec svccfg import ~serviio/ | ||
| This creates a new service svc:/ | This creates a new service svc:/ | ||
| Line 51: | Line 72: | ||
| Next enable the service, so that it will start up whenever the machine is booted, and will be restarted if it gets shot down by mistake. | Next enable the service, so that it will start up whenever the machine is booted, and will be restarted if it gets shot down by mistake. | ||
| - | prompt> svcadm enable serviio | + | **//<fc #0000FF>prompt> |
| + | </ | ||
| - | and as you can see, one needs not use the full fmri, as long as you use enough of the name to make it unique. | + | You can look at the serviio service by doing |
| + | ** | ||
| + | //<fc # | ||
| + | and as you can see, you need not use the full fmri, as long as you use enough of the name to make it unique. | ||
| + | As a final check, just in case, look at / | ||
| + | This might be wrong if you had an earlier copy running as some user other than serviio, or you did the manual test above not as user serviio. | ||
| + | |||
| + | < | ||
| ---------serviio.xml file contents------------ | ---------serviio.xml file contents------------ | ||
| + | |||
| <?xml version=" | <?xml version=" | ||
| < | < | ||
| Line 76: | Line 106: | ||
| < | < | ||
| </ | </ | ||
| - | |||
| - | |||
| - | | ||
| - | | ||
| - | | ||
| | | ||
| < | < | ||
| Line 86: | Line 111: | ||
| </ | </ | ||
| - | < | + | < |
| < | < | ||
| Line 92: | Line 117: | ||
| < | < | ||
| <propval name=" | <propval name=" | ||
| - | | ||
| - | | ||
| <propval name=" | <propval name=" | ||
| </ | </ | ||
| Line 100: | Line 123: | ||
| | | ||
| </ | </ | ||
| - | | ||
| | | ||
| < | < | ||
| Line 116: | Line 138: | ||
| </ | </ | ||
| -------end of serviio.xml contents--------------- | -------end of serviio.xml contents--------------- | ||
| + | </ | ||
howto/solaris/install.1326888938.txt.gz · Last modified: 2012/01/18 12:15 by n3mmr
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
