Bits on Bytes bits on iphone, programming, and all things tech

Run the following in Terminal, just fill in your company name:

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

I often disable the GUI login on my Solaris machines for simplicity, so they just sit at the console login prompt. This presents a problem because by default Solaris sends logs to the console via /dev/sysmsg. This means that system errors, kernel and authentication notices are right out there for the world to see. So I like to redirect these logs to a more secure location (and keep my console nice and pretty).

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.

So if you didn’t quite understand that subject it means this post is about the ACL (access control list) I am using on my CIFS (common internet file system) shared ZFS (zetta file system). I’m fairly new to ACLs myself but Ben Rockwood wrote an extremely helpful post about them, so go check it out!

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: Read the rest of this entry »

Disable

# /usr/dt/bin/dtconfig -d

Enable

# /usr/dt/bin/dtconfig -e

“To create an ISO image in OS X, use Disk Utility to burn a new image choosing CD/DVD Master as the Image Format. That creates an image with the cdr extension. Just rename the cdr file extension to iso and there you have it!”

“If you already have a DMG and want to convert it to an ISO, you can use hdiutil to do so:”

$ hdiutil convert discimage.dmg -format UDTO -o output.iso

Found it here.

First map the .iso file to a device:

# lofiadm -a /path/to/image.iso /dev/lofi/1

Note: You can mount more images by incrementing the lofi device number (/dev/lofi/2).

Now just mount it like a file system:

# mount -o ro -F hsfs /dev/lofi/1 /mnt/image

The ISO file should now be mounted at /mnt/image

Spent forever looking for this:

# /var/sadm/prod/entsys/SUNWentsys4/uninstall