defaults write com.apple.Xcode PBXCustomTemplateMacroDefinitions '{ORGANIZATIONNAME = "Some Company Name"; }'

Well, maybe not directly but either way the problem has been fixed! As you can see in the picture on the right, the Gmail navigation column (including the labels) was increased by 23 pixels!

So thanks Google.

I’ve been able to successfully do this in a native iPhone app but the method still needs refinement. I’m posting this to see if anybody else is doing this or knows of a better method. If anyone else is interested I’d be glad to share code, just let me know.

security = user
passdb backend = tdbsam

That will let you use the Solaris user accounts for samba access. Next set up a share that you’d like to test with. Here’s a simple one I used:

[htdocs]
path = /opt/coolstack/apache2/htdocs
valid users = cjs00c
public = no
writable = yes

Start up the samba service with svcadm enable samba. Now we need to add a user/pass to the samba user database: smbpasswd -a cjs00c. You should be able to connect to your new samba share now.

Just for fun, the samba password database file is located at /etc/sfw/private/passdb.tdb. If you’d like to check it for users you can use:
tdbtool /etc/sfw/private/passdb.tdb
tdb> info
3 records totalling 224 bytes
tdb> dump

key 12 bytes
USER_cjs00c
data 213 bytes
[a whole bunch of encoded data here]

key 13 bytes
INFO/version
data 4 bytes
[000] 03 00 00 00 …

key 13 bytes
RID_000004b0
data 7 bytes
[000] 63 6A 73 30 30 63 00 cjs00c
tdb>

The config file is /etc/syslog.conf. Comment out the line:

*.err;kern.notice;auth.notice                  /dev/sysmsg

by putting a # in front of it, or point to a new file location.

You should notice that most of these messages are being captured by the line below it as well and are being sent to /var/adm/messages. That’s a good place for these logs so leave that. However, it’s not capturing the auth.notice messages. Look a bit further down the file and you’ll see an ‘auth.notice’ line that’s commented out. Uncomment that line (make sure loghost is set in /etc/hosts) and your auth messages should be sent to /var/log/authlog. Which is a much nicer location than the console don’t you think?

User errors are defined further down the file and it also has an entry for logging user errors to /dev/sysmsg so you can comment that out as well if desired.

At the next menu choose ‘Solaris Interactive Text’ either desktop or console. I chose #4, the console session because it loads faster.

The installer asks you a few network and configuration questions first. For simplicity I’ll just list my summary:

Networked: Yes
Use DHCP: No
Host name: gibbs
IP address: 150.252.xxx.xxx
System part of a subnet: Yes
Netmask: 255.255.xxx.xxx
Enable IPv6: No
Default Route: Specify one
Router IP Address: 150.252.xxx.xxx
Configure Kerberos Security: No
Name service: DNS
Domain name: acu.edu
Server address(es): 150.252.xxx.xxx
150.252.xxx.xxx
Search domain(s): acu.edu
NFSv4 Domain Name: << Value to be derived dynamically >>
Time zone: Central Time
(US/Central)
Date and time: 2008-11-03 14:14:00

After entering the root password the screen goes blank for a few seconds, some scripts start executing, then the installation screen comes back.

1. Select the “Standard” installation
2. Automatically eject CD/DVD
3. Auto Reboot
4. Accept the license agreement
5. Select any extra regional support
6. Select POSIX C (C)
7. Select None for Web Start products
8. Select ZFS for the filesystem
9. Select Entire Distribution
10. Select disk to install on

Configure the ZFS settings. I changed the swap size to 2G and left everything else default.

ZFS Pool Name: rpool
ZFS Root Dataset Name: s10x_u6wos07b
ZFS Pool Size (in MB): 39214
Size of Swap Area (in MB): 2048
Size of Dump Area (in MB): 1024
Keep / and /var combined

Add remote mounts if you have any and begin installation!

So to configure the zone you need to log into the zone’s ‘console’ after booting it for the first time.

# zlogin -C myzone

If you don’t see anything hit enter. You should be presented with a terminal choice. After that it should be pretty standard system configuration questions.

Alternatively, this can be automated by creating a sysidcfg file and placing it in /etc

On to the subject of this post - If you share a ZFS filesystem with CIFS and create new entries from a windows computer (as one might do for a home file server), the resulting entries have zero permissions. For example, this is the ls -l result of a directory and a text file created from a windows system:

d---------+  2 peemus   staff          2 Jul 20 20:50 blee
----------+  1 peemus   staff          0 Jul 20 20:50 bloo.txt

Notice the +. It signifies that the entry has extended attributes (see Ben’s post), these are the attributes inherited from some Microsoft leprechaun on the windows machine - instead of inheriting the attributes of the parent entry. This is most annoying if you like to browse your data from the server side, as well as from the windows side. So to fix this, I created a custom ACL that when applied to the root shared directory will force child entries to inherit the correct permissions. So the example entries would now look like:

drwxr-xr-x+  2 peemus   staff          2 Jul 20 20:58 blee
-rw-r--r--+  1 peemus   staff          0 Jul 20 20:58 bloo.txt

To make this happen just use chmod like so (and of course with -R if you want it to recursively apply the ACL):

chmod A=\
owner@:w:d:allow,\
owner@:w:f:allow,\
everyone@:rxpdDaARWcCos:d:allow,\
everyone@:rpdDaARWcCos:f:allow \
mySharedDir/

Of course you can change the permissions to be whatever you want.

It gets better! OpenSolaris will even help protect your system by creating an entirely new boot environment and upgrading that. So if something were to not go as expected you could always boot back into your original environment.

The following instructions were not written by me, I got them from the indiana-discuss mailing list in the build 93 announcement by David Comay. I have copied it here for reference.

General instructions on updating to the latest OpenSolaris development build
=======================================================================
1) Before using the "image-update" subcommand, it is recommended that
the latest available version of the IPS software be installed for your
current boot environment

       $ BUILD=`uname -v | sed s/snv_//`
       $ pfexec pkg refresh
       $ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
       $ pfexec pkg install entire@0.5.11-0.$BUILD

2) Before proceeding to the next step, verify your OpenSolaris build
number

       $ echo $BUILD

3) If you are running build 93 or greater, you can use "image-update"
directly as follows

       $ pfexec pkg image-update

4) If you are using a build prior to 93, it is recommended one apply
the update directly to an alternate boot environment.  First, display
the list of the existing BEs on the system

       $ beadm list
       BE            Active Active on Mountpoint     Space
       Name                 reboot                   Used
       ----          ------ --------- ----------     -----
       opensolaris   no     no        -              33.92M
       opensolaris-1 yes    yes       -              17.06M

Next, choose the name of a new BE - if the most recent created BE is of
the form "opensolaris-" where  is an integer, then a suitable
choice for the new BE is "opensolaris-".  In the above example,
the new BE would be "opensolaris-2".

Then, execute the following sequence to create, mount, update and
activate the new BE

       $ pfexec beadm create opensolaris-
       $ pfexec beadm mount opensolaris- /mnt
       $ pfexec pkg -R /mnt image-update
       $ pfexec beadm activate opensolaris-

5) If you are running build 86, one additional work-around is
required.

               >>>>>>>>>> IMPORTANT <<<<<<<<<<

Due to changes in the GRUB boot system, one must manually update the
Master Boot Record (MBR) to include these latest changes.  Failure to
follow these instructions when updating from 2008.05 (build 86) to a
later build will result in a system that does not boot by default and
instead the original boot environment must be manually selected.

Update the GRUB configuration on your ZFS boot device(s) using

       $ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt

When you're ready to boot into the updated boot environment, you can
reboot(1M) or init(1M) as usual.