|
|
Typo?
The hint suggests this: % sudo cp -Rp /Previous\ System/Previous\ System 1/System/ Library/SyncServices/PalmBladeConduit.bundle /System/Library/ SyncServices/PalmBladeConduit.bundle</code> That "</code>" at the end looks like a typo to me. Should the line be like this instead? % sudo cp -Rp /Previous\ System/Previous\ System 1/System/ Library/SyncServices/PalmBladeConduit.bundle /System/Library/ SyncServices/PalmBladeConduit.bundle And while we're at it, we can clean up the linebreaks for easier copy & paste action with a well placed backslash: % sudo cp -Rp \ /Previous\ System/Previous\ System 1\ /System/Library/SyncServices/PalmBladeConduit.bundle \ /System/Library/SyncServices/PalmBladeConduit.bundle Does it look better / more accurate this way? The line-break as given here should, hopefully, make it much clearer what is being done by that line -- the /System/Library[...]Palm[...]bundle file is being copied out of the previous system directory (which, incidently, could have different names on different systems, depending on whether people have done other upgrades in the past) into the current /System directory tree. Whitespace almost always makes it easier to see what's going on... :-) ---
Typo?
Doh! The backslashes were in when I previewed it. This CMS takes HTML, chews it through a blender, and spits out something unrecognizeable, eh? Let me try that end code block again: % sudo cp -Rp \ /Previous\ System/Previous\ System 1\ /System/Library/SyncServices/PalmBladeConduit.bundle \ /System/Library/SyncServices/PalmBladeConduit.bundle If that gets mangled again, I'm putting a backslash character at the end of each of the first three lines, but not the last line. The first line has a space between the '-Rp' and the backslash (probably works either way, but clearer with the space), the second line does not have a space after the '1' and its backslash, and the third line does have a space after '.bundle' and before its backslash. The spacing is significiant, particualrly in the second line, because you're forcing the shell to insert a linebreak & yet to ignore it, and I think the behavior of any whitespace before the backslash is undefined (i.e. it might be taken literally, and you'll get an error about a missing file). Of course, if the slashes are all visible this time, then the previous disclaimer can be safely ignored :-) ---
Typo?
When doing code in postings, I always COPY my whole message, hit the Preview button and if it looks good, PASTE back in what was written before the Preview. Then I post that. I find that on many sites the Preview step mangles things. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|