This post is password protected. To view it please enter your password below:

Password:

I’m the only user on the network, which is entirely behind a hardware-firewall. For now, I’ve been erring on the side of overly-permissible file-premissions, and still can’t access my own data.

The fileserver (Shangri-La or 192.168.28.29) has a static-IP, as no real local DNS is configured. I have the same username and password on all my machines.

Current Client Access

- Currently I can’t seem to automount the ZFS filesystems at all.
- If I use the GUI “Connect To Server” on OpenSolaris or Linux I can connect to a specific ZFS fileshare
- However If I connect to a top-level one, I get ‘permission-denied’ when trying to traverse into a lower one.
- I have to connect-to them all separately or simply connect-to the bottom leaves of the tree.

OpenSolaris Client now can browse all the filesystems individually, from gnome using eg: (smb://shangrila/dpool_import_cairo/)

I’ve followed numerous guides, and leafed through the ZFS and CIFS admin books. But still have no sane/consistent way to access the data from my Opensolaris client, let alone the suse one. Haven’t even tried Windows yet.

Server Side Config Files

~/bin/aclres.exe
With my limited knowledge of ACL permissions, I wrote this primitive brute-force script to set the permissions on the files I wanted to share.

#!/bin/bash

## Defaults
chmod -R A-    *
chmod -R 755    *
chown -R johnSmith *
chgrp -R staff *

## Files
chmod -R A=everyone@:rwxpaRcs:allow    *
chmod -R A+everyone@:AWCo:deny    *

chmod -R A+group@:rwxpd:allow    *
chmod -R A+group@::deny     *

chmod -R A+owner@:rwxpdDAWCo:allow    *
chmod -R A+owner@::deny    *

## Directories
chmod -Rf A=everyone@:rwxpaRcs:fd:allow    *
chmod -Rf A+everyone@:AWCo:fd:deny    *

chmod -Rf A+group@:rwxpd:fd:allow    *
chmod -Rf A+group@::fd:deny     *

chmod -Rf A+owner@:rwxpdDAWCo:fd:allow    *
chmod -Rf A+owner@::fd:deny    *

ZFS Layout

johnSmith@shangrila:~$ zfs list |grep  dpool
dpool                                  174G  54.5G  25.5K  /dpool
dpool/data                              62K  54.5G    22K  /dpool/data
dpool/data/davinci                      20K  54.5G    20K  /dpool/data/davinci
dpool/data/firefly                      20K  54.5G    20K  /dpool/data/firefly
dpool/dev                             16.3G  54.5G    22K  /dpool/dev
dpool/dev/magento                       20K  54.5G    20K  /dpool/dev/magento
dpool/dev/torque                      16.3G  54.5G  16.3G  /dpool/dev/torque
dpool/import                           114G  54.5G    23K  /dpool/import
dpool/import/athenaHome               57.5G  54.5G  57.1G  /dpool/import/athenaHome
dpool/import/aura                       20K  54.5G    20K  /dpool/import/aura
dpool/import/cairo                    56.1G  54.5G  39.1G  /dpool/import/cairo
dpool/media                           44.0G  54.5G    24K  /dpool/media
dpool/media/amadeus                   22.2G  54.5G  22.2G  /dpool/media/amadeus
dpool/media/holly                     21.8G  54.5G  21.8G  /dpool/media/holly
dpool/media/import                      20K  54.5G    20K  /dpool/media/import

Client Side Config Files

/etc/auto_master

+auto_master
/net		-hosts		-nosuid,nobrowse
/home		auto_home	-nobrowse
#/dpool   auto_smb   -nobrowse
/-       auto_direct

/etc/auto_direct

/dpool                -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool
/dpool/data           -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/data
/dpool/data/davinci   -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/data/davinci
/dpool/data/firefly   -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/data/firefly
/dpool/dev            -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/dev
/dpool/dev/magento    -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/dev_magneto
/dpool/dev/torque     -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/dev_torque
/dpool/import         -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/import
/dpool/import/athenaHome -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/import/athenaHome
/dpool/import/aura    -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/import/aura
/dpool/import/cairo   -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/import/cairo
/dpool/media          -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/media
/dpool/media/amadeus  -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/media/amadeus
/dpool/media_/holly   -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/media/holly
/dpool/media/import   -fstype=smbfs, dirperms=0700, uid=johnSmith //192.168.28.29/dpool/media/import

/etc/auto_smb

dpool                -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool
dpool_data           -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/data
dpool_data_davinci   -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/data/davinci
dpool_data_firefly   -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/data/firefly
dpool_dev            -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/dev
dpool_dev_magento    -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/dev_magneto
dpool_dev_torque     -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/dev_torque
dpool_import         -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/import
dpool_import_athenaHome -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/import/athenaHome
dpool_import_aura    -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/import/aura
dpool_import_cairo   -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/import/cairo
dpool_media          -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/media
dpool_media_amadeus  -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/media/amadeus
dpool_media__holly   -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/media/holly
dpool_media_import   -fstype=smbfs ://johnSmith:password@192.168.28.29/dpool/media/import

Attempting to Automount from OpenSolaris Client

johnSmith@athena: 502# automount -v
automount: hierarchical mountpoint: /dpool and /dpool/data
automount: hierarchical mountpoint: /dpool and /dpool/data/davinci
automount: hierarchical mountpoint: /dpool and /dpool/data/firefly
automount: hierarchical mountpoint: /dpool and /dpool/dev
automount: hierarchical mountpoint: /dpool and /dpool/dev/magento
automount: hierarchical mountpoint: /dpool and /dpool/dev/torque
automount: hierarchical mountpoint: /dpool and /dpool/import
automount: hierarchical mountpoint: /dpool and /dpool/import/athenaHome
automount: hierarchical mountpoint: /dpool and /dpool/import/aura
automount: hierarchical mountpoint: /dpool and /dpool/import/cairo
automount: hierarchical mountpoint: /dpool and /dpool/media
automount: hierarchical mountpoint: /dpool and /dpool/media/amadeus
automount: hierarchical mountpoint: /dpool and /dpool/media_/holly
automount: hierarchical mountpoint: /dpool and /dpool/media/import
automount: /dpool mounted
automount: no unmounts
johnSmith@athena: 503# ls /dpool
/dpool: Permission denied
johnSmith@athena: 504#

Magento is a newish shopping cart platform that is pretty slick, engineered, and rather complex to pickup.You can auto-install extension components for your Magento store from MagentoConnect which it turns out is built on top of the PEAR package-managing system. From the website you can browse for an extension, get an “activation key”, and use your store’s admin-gui to install a module.

• Make sure you’ve got a full backup or proper version-control of your stores source-code and mods.
• Make SURE you BACKUP YOUR DATABASE …

(I recently did a “live upgrade” of the ‘core’ platform, on a test-site and it corrupted my DB … )

PHP

You will need the “php” command in your $PATH.

• On a linux system you can usually discover it by calling:$ whereis php
• On OpenSolaris-2009.06 I found the webstack PHP in: /usr/php/5.2/bin/php

In either case we want to make this generically-accessible to our users, by adding a simple symbolic link from /usr/bin which IS in your $PATH to the actual php binary. If you can find the PEAR and want to add a similar link, do so as shown, but this is optional.:
$ cd /usr/bin
$ ln -s /usr/php/5.2/bin/php php
$ ln -s /usr/php/5.2/bin/pear pear

PEAR

Magento has a very broad file-structure, and modules put files in several locations. As a developer I wanted to lookat an existing extension similar to one I’m developing, without hunting for bits and pieces or blowing up my dev-environment on a failed install. While the MagentoConnect webpage fails to offer us a simple “Download” button, hope is not lost, as we can simply use PEAR from the command line.

If your machine has PHP installed (required in your $PATH for this exercise) it probably also has  PEAR, however we will want to use the PEAR installation provided WITH Magento.


// Setup Magento PEAR
$ cd ~/public_html/magento/
$ ./pear mage-setup
$ ./pear -V
$ ./pear list-channels

// Download a Package
$ ./pear download connect.magentocommerce.com/community/ModuleFooBar

// Install a Package
$ ./pear install connect.magentocommerce.com/community/ModuleFooBar

Download a Package

The PEAR “download” command does what it says and simply downloads a *.tar to your current directory. This is exactly what I required, now I have the files to move where I wish and examine at my leisure, if I had leisure…

Install a Package

The PEAR “install” command also does what it says, and goes stright to work attempting to install the package. This is (appears to be) essentially the same as grabbing the key-code from the web, and installing from your Magento AdminPanel GUI.

Note: You do not need to “download” a package before installing it as the PEAR “install” command is smart enough to do all the work for you.

ModuleFooBar

When you find a component ont he MagentoConnect site and click “Get Extension Key”, it gives you a string like “magento-community/ModuleFooBarr” to supply to the AdminPanel GUI. If your using PEAR, you still need to click this link and the final part “ModuleFooBar” is your package name. The first part of the path-name, you must discard in favor of PEAR channel-syntax.

Good Luck

1. Change your MySQL ROOT password!
   $ /usr/mysql/5.1/bin/mysqladmin -u root password {{'NewPassword'}}
$ mysql -u root -p

2. Install phpMyAdmin
   $ pfexec pkg set-authority -O http://pkg.opensolaris.org/webstack Webstack
$ pfexec pkg refresh
$ pfexec pkg install pkg://webstack/phpmyadmin
$ man phpmyadmin
$ /usr/bin/phpmyadmin_evaluation_init


Final Configuration of phpMyAdmin:

1. As root:
   # vi /etc/phpmyadmin/config.inc.php
/blowfish_secret
2. In the empty ‘ ‘ after the = type any random string under 46 chars. Doesn’t matter what (AFAIK) and you won’t be asked again (AFAIK).
3. :wq

Point your webbrowser at http://127.0.0.1/phpmyadmin/ and you should be ready to rock & roll. If you have any trouble go back to the origianl Maintainer’s Blogpost and also read the MAN pages more carefully.

You should also familiarize yourself with Sun’s: Web Stack Getting Started Guide

Good Luck!

Setting up your printer in OpenSolaris can be a trick, if your drivers aren’t yet included.

1. The place to start is in: System | Administration | Print Manager
2. Click “Add Printer” button and get to work
3. If your printer isn’t available try getting a driver from one of these places:
   • http://www.linuxfoundation.org/en/OpenPrinting
   • http://www.cups.org/index.php
4. You need to get a valid *.ppd or *.ppd.gz file for your printer.
5. Close the Print Manager GUI for now.
6. As ROOT type:
# ppdmgr -a path_to_.ppd -w
# ppdmgr -u
7. Reopen the Print Manager GUI and you should be able to find your driver.
8. Best of luck, that should make your printer happy!

Remove the Banner

To remove the ‘banner page’ that prints every time is easy:

1. Click: System | Administration | Solaris LP Print Manager
2. I just click ‘cancel’ on the first dialog box that pops up…
3. Select your printer and click: Printer | Modify Printer Properties
4. Under “Banner” select: Never Print Baner
5. ‘Apply’, ‘Ok’, Good-2-Go.

Default to Letter-Size

How? (possibly feature not implemented yet)

Print Source Code with: printcpp

Here’s an awesome hack handed down from my former Professor and UNIX Zen-Master. This simple alias prints nicely formatted plain-text files from the command-line with normal ‘C/C++ style’ source-code syntax-highlighting. It’s also great for printing any text file in a hurry.

The first one is ‘portrait’ mode and the second is ‘landscape’ mode. You may have to tweak a little if your porting to a different UNIX/LINUX system, but I’ve always gotten it to work!

1. See my prior post about installing more IPS repos!
2. From IPS, select the ‘SunFreeware’ repo, possibly marked ‘Companion’ or ‘SFW’
3. Grab the GNU “Enscrip”‘ package.
4. Add some code to your .bashrc or .bash_aliases:
   
alias printcpp='enscript -M Letter -G -i 2 -f Courier8 -Ecpp -P myPrinterName'
alias printcpp2='enscript -M Letter -r -G -i 2 -f Courier8 -Ecpp -P myPrinterName'

5. Pay-attention and be sure to substitute YOUR printer name for “myPrinterName”.
6. $ source ~/.bashrc

What is spec-files-extra? SFE is a repository of RPM-like spec files for building Solaris SVr4 packages from various Open Source modules. ~ The SFE Site

And if you follow the installation instructions closely-enough, without getting too bogged down in the details, you can probably be up and running SFE Enabled faster than I can write this blog. However those instructions are slightly dated, and even as a Sophomore to the OSol world, I hit a few bumps along the way, so here’s the short-list to get you going quickly!

JDS -> OSD

As it happens I started following the original instruction-set, returned a few hours later and someone had done a bit of “Find & Replace” re-branding; just to mess with my head I believe… So – just to clear up some confusion:

• JDS-CBE - (Java Desktop Source – Common Build Environment (?))
• OSD-CBE- (OpenSolaris Desktop – Common Build Environment(?))

Old Name, New Name, respectively.

Currently, they are the same thing and you will need the underlying “CBE” portion of them, even if you don’t intend to do further OSol Desktop Development. Careful not to follow the original instruction sheets blindly though, or your in for a world of trouble – instead, keep reading here!

Installing the Common Build Environment (CBE)

Reference Links

All of the information on this page was pulled-from and relates back to the following links. Hopefully, however, this blogpost will save you from dredging through them for the insight you need. Hopefully…

Useful Links (for now)

1. Spec File Extra - Main Site
2. JDS / OSD / CBE Installation Guide
3. OSD Download Center on Sun
4. SFE Index on SourceForge

Less Relevant Extra’s

1. OSD Source Code Tour
2. JDS / OSD Source Location
3. pkgbuild Home on SourceForge
   

(Do Not) Build CBE from Source

(Rant: Feel free to skip to next section!)
Given my Sun AMD_X64 system, I was unusually motivated to build something from source. Unfortunately, after a great effort it was not to be. After downloading jds-cbe-1.6.2-src.tar, one should be able to run the cbe-install script and things will be happy.

The CBE appeared to build and install the first several tools correctly including v.1.9 and v.1.10 of AutoMake (or was it AutoConf ?), disregarding that they both already exist. When the script got to building: libtool-1.5.22 it demanded AutoMake-1.9a and some other weird tool (also v.1.9.a). If I went to the directory under $HOME/PACKAGES, found libtool-1.5.22 I could “configure, make, make install” just fine. However, the “cbe-install” script was still not happy and would never complete. No luck with the jds-cbe-1.6.2-src.tar either…

Install From Binaries

1. (As stated elsewhere) “You don’t need root access for installing the CBE or building GNOME, but the build-user needs to have the ‘Software Installation’ profile for installing the packages that the CBE creates,”… Of course, giving yourself said permissions may require ROOT access (on a one-time basis). That said, from the desktop:

   - Click: System | Administration | Users & Groups
   - Select your userName and click: Properties
   - Click the 'User Profiles' Tab and check 'Software Installation'
   - Click 'OK' (twice).

2. Install SunStudio Express from the IPS package manager. Building SFE packages requires a compiler and now’s a good time to grab it.

   - Select the 'OpenSolaris.org' repository
   - Select 'All Categories'
   - Search for: studio
   - Check and Install: sunstudioexpress
   - Search for: sfwhea
   - Check and Install: SUNWsfwhea

3. Visit the OSD Download Center (Link #3) and grab the: jds-cbe-1.6.2-i386.tar.bz2 binary package.
   Warning: The _src_ does NOT build cleanly on OSol 2009.06, so for now don’t even waste your time!
4. athena: 453$ bunzip2 jds-cbe-1.6.2-i386.tar.bz2
athena: 454$ tar -xvf jds-cbe-1.6.2-i386.tar
athena: 456$ cd jds-cbe-1.6.2
athena: 459$ ./cbe-install
5. Follow the scripts instructions, mostly you want the defaults.
   • Specifically confirm your compiler is: /usr/bin/cc
   • The install script will complain, as your compiler is NEWER than the script, and doesn’t provide the expected version-output. This is OK!
6. Now you need to download the SFE Spec-Files, which as I understand it, are essentially header-files of meta-data for each SFE package. Thus when you tell the system to install one it has all the install info it needs on hand.
   
athena: 460$ cd ~
athena: 461$ svn co https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk SFE
7. At this point you will want to add to your ~/.bashrc file:

   PATH=$PATH:/opt/jdsbld/bin          # JDS-CBE   - packages we installed

8. Now source the ~/.bashrc, and then run the env.sh in the /opt/jdsbld/bin …
   athena: 466$ source ~/.bashrc
athena: 467$ . /opt/jdsbld/bin/env.sh

Congratulations! At this point you have installed the CBE, downloaded the SFE spec files from subversion, and configured your environment to start building SFE spec-file packages! Every time you want to install SFE packages you should run the second console line from ‘step 8′ above, and of course running the first line “source ~/.bashrc” will always revert you to your normal working shell-environment.

Installing a SFE Package


athena: 468$ . /opt/jdsbld/bin/env.sh
athena: 468$ pkgtool build --download SFEfoo.spec


Or, while not bullet-proof, you can often use the dependency-checking option.

pkgtool build --download SFEfoo.spec --autodeps


Other Approaches

Unknown to me, there was already a well written article to this effect. If you found my post unclear or unhelpful you may have better luck reading this: pkgbuild on OpenSolaris

As a final and entirely different method you may want to search for the sfe-bootstrap-latest script. Supposedly it is an all inclusive script to get you running. I believe it was originally published in THIS forum thread: sfe-bootstrap-latest script

If you’ve just installed OpenSolaris 2009.06 the only IPS repository on your list will be the default ‘OpenSolaris’ one. There are however, a few other reputable 3rd-party repositories who provide Solaris software packages which all new users should be familiar with!

Many of these have been around for some time, and have some intricate build/install infrastructures, which once configured, allow you to easily install packages on older versions of Solaris. With the new IPS system, hopefully those days will soon be a hazy memory. However, thse repositories are huge and they have only just begun porting their software-packages to OpenSolaris, and to IPS.

• Sun Extras – Not really sure what is ‘extra about these but they are separate from the primary repository. To add this IPS repo you will have to follow the (easy) instructions on this page to add it along with the secure SUN encryption keys.
  • IPS Extras Repository
• BlastWave – A popular 3rd party repository for solaris install packages.
  • Blastwave
• SunFreeware – “Celebrating 15 Years as the #1 Site for Free Software Packages for Solaris.” They have many additional software packages ready to install into Solaris.
  • SunFreeWare.com
  • SFW at OpenSolaris.org
• Solaris WebStack -Includes special extras for the Solaris AMP Webstack, including phpMyAdmin.
  • Webstack on OpenSolaris.org
  • Maintainer’s Blog

Installing the IPS Repos

• Blastwave
• SunFreeWare
• WebStack


$ pfexec pkg set-authority -O http://blastwave.network.com:10000/ Blastwave
$ pfexec pkg set-authority -O http://pkg.sunfreeware.com:9000/ SunFreeware
$ pfexec pkg set-authority -O http://pkg.opensolaris.org/webstack Webstack