vi-curious Gary J Little's Weblog

Mounting an iPod on Solaris

This worked for me.... I'm using Solaris 11 / Nevada built from build 36

# uname -a
SunOS dhcp-egmp02-36-140 5.11 snv_36 i86pc i386 i86pc

I plug in my Ipod to the usb port (I've not tried it on Firewire) of my laptop. I type devfsadm at the root prompt

# devfsadm
# 

I then use rmformat -l to see if the device is recognised

# rmformat -l
Looking for devices...
     1. Volmgt Node: /vol/dev/aliases/cdrom0
        Logical Node: /dev/rdsk/c1t0d0s2
        Physical Node: /pci@0,0/pci-ide@1f,1/ide@1/sd@0,0
        Connected Device: TOSHIBA  DVD-ROM SD-C2612 1F27
        Device Type: DVD Reader
        Bus: IDE
        Size: 
        Label: 
        Access permissions: 
     2. Logical Node: /dev/rdsk/c5t0d0s2
        Physical Node: /pci@0,0/pci10cf,11ab@1d,7/storage@1/disk@0,0
        Connected Device: Apple    iPod             1.53
        Device Type: Removable
        Bus: USB
        Size: 19.1 GB
        Label: 
        Access permissions: Medium is not write protected.
     3. Logical Node: /dev/rdsk/c5t0d0p0
        Physical Node: /pci@0,0/pci10cf,11ab@1d,7/storage@1/disk@0,0
        Connected Device: Apple    iPod             1.53
        Device Type: Removable
        Bus: USB
        Size: 19.1 GB
        Label: 
        Access permissions: Medium is not write protected.

Now, since the Ipod is formatted as PCFS I need to do the following magic command.

# mount -F pcfs /dev/dsk/c5t0d0p0:c /a

I can now see the iPod disk

# cd /a
# ls
Calendars     Contacts      iPod_Control  Notes

And I can make a file

# timex mkfile 100m ipod-disk1-100m

real     1:15.47
user        0.01
sys         5.64

# ls -l
total 204832
drwxrwxrwx   1 root     root        4096 Jan  1  1970 Calendars
drwxrwxrwx   1 root     root        4096 Jan  1  1970 Contacts
-rwxrwxrwx   1 root     root     104857600 Mar 31 11:53 ipod-disk1-100m
drwxrwxrwx   1 root     root        4096 Jan  1  1970 iPod_Control
drwxrwxrwx   1 root     root        4096 Jan  1  1970 Notes
# 

Cool!

( Mar 31 2006, 11:54:38 AM BST ) Permalink Comments [3]

Persistent Resource Controls in S10

In a previous blog entry, I used prctl to change a resource limit on a project wide basis. It turns out that this is only temporary - and will be overwritten on reboot. For persistant resource changes it seems we still need to use the projmod command (or edit the /etc/project file by hand). Initially, my project file looks like this:-

bash-3.00# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
user.oracle:11::::

Which means that my shared memory limit will be reset on reboot, which is not what we want. To make the change permanent, we use the projmod command like so.

#  projmod -s -K "project.max-shm-memory=(priv,4gb,deny)" user.oracle    
# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
user.oracle:11::::project.max-shm-memory=(priv,4294967296,deny)

# bc
4*1024*1024*1024
4294967296

If you want to edit the /etc/project by hand, you'll need to enter just a decimal number. It won't accept 4gb (at least not on my system,i tried). The changes are only seen on reboot. To change dynamically, use

prctl -n project.max-shm-memory -r -v 4gb -i project user.oracle

Then you will see the results immediately. When issuing the prctl command (above) at least one process e.g. a shell needs to be running in the project user.oracle (the simplest way to do this is to simply login to the machine as oracle in another terminal) ( Mar 28 2006, 03:49:09 PM BST ) Permalink Comments [0]