Articles: Customizing Rails Applications on Mac OS X Leopard


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Articles: Customizing Rails Applications on Mac OS X Leopard
# 1  
Old 06-14-2008
Articles: Customizing Rails Applications on Mac OS X Leopard

Learn how to enhance your Rails application with views and web forms, AJAX, and iPhone support.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. OS X (Apple)

Use a Serial Console with Mac OS X Leopard

I'm trying to use an old Commodore 128D as a terminal to access OS X's shell via a serial port. I've used 'screen' and 'zterm' to ensure the two machines are successfully interfaced. Instructions for opening up the serial console on other Unix-y operating systems don't work with OS X Leopard. ... (3 Replies)
Discussion started by: joecassara
3 Replies

2. OS X (Apple)

loading MAC X 5.0(leopard) on a X86 laptop

I want to install MAC X 5.x on my T60 Lenova laptop. I have the Original Mac X 5.0 installation media. I tried to install it on a blank hard disk in my laptop but it doesn't work. On the internet I found sites that offer torrent downloads but I can't use torrent downloads on my laptop. (Corp... (1 Reply)
Discussion started by: mndavies
1 Replies

3. Shell Programming and Scripting

mac backup script in leopard

Hi all I had a nice simple backup script on my mac running Tiger. I used an Automator 'Run Shell Script' command that loaded psync and backed up one directory on an external drive to a directory on another external drive. This was the command /usr/local/bin/runpsync 0 0 0... (1 Reply)
Discussion started by: Billy T
1 Replies
Login or Register to Ask a Question
CPMAC(1)						    BSD General Commands Manual 						  CPMAC(1)

NAME
/usr/bin/CpMac -- copy files preserving metadata and forks SYNOPSIS
/usr/bin/CpMac [-rp] [-mac] source target /usr/bin/CpMac [-rp] [-mac] source ... directory DESCRIPTION
In its first form, the /usr/bin/CpMac utility copies the contents of the file named by the source operand to the destination path named by the target operand. This form is assumed when the last operand does not name an already existing directory. In its second form, /usr/bin/CpMac copies each file named by a source operand to a destination directory named by the directory operand. The destination path for each operand is the pathname produced by the concatenation of the last operand, a slash, and the final pathname compo- nent of the named file. The following options are available: -r If source designates a directory, /usr/bin/CpMac copies the directory and the entire subtree connected at that point. This option also causes symbolic links to be copied, rather than indirected through, and for /usr/bin/CpMac to create special files rather than copying them as normal files. Created directories have the same mode as the corresponding source directory, unmodified by the process' umask. -p Causes /usr/bin/CpMac to preserve in the copy as many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions. -mac Allows use of HFS-style paths for both source and target. Path elements must be separated by colons, and the path must begin with a volume name or a colon (to designate current directory). NOTES
The /usr/bin/CpMac command does not support the same options as the POSIX cp command, and is much less flexible in its operands. It cannot be used as a direct substitute for cp in scripts. As of Mac OS X 10.4, the cp command preserves metadata and resource forks of files on Extended HFS volumes, so it can be used in place of CpMac. The /usr/bin/CpMac command will be deprecated in future versions of Mac OS X. SEE ALSO
cp(1) MvMac(1) Mac OS X April 12, 2004 Mac OS X