Comments on: How to create a RAM disk with the contents of a disk image preloaded http://boredzo.org/blog/archives/2008-01-11/how-to-create-a-ram-disk-with-the-contents-of-a-disk-image-preloaded The personal weblog of Peter Hosey. Fri, 05 Dec 2008 14:05:15 +0000 http://wordpress.org/?v=2.6.5 By: Peter Hosey http://boredzo.org/blog/archives/2008-01-11/how-to-create-a-ram-disk-with-the-contents-of-a-disk-image-preloaded#comment-155538 Peter Hosey Sat, 12 Jan 2008 10:10:11 +0000 http://boredzo.org/blog/archives/2008-01-11/how-to-create-a-ram-disk-with-the-contents-of-another-image-preloaded#comment-155538 Jon H: Good point. Fixed. Thanks. Jon H: Good point. Fixed. Thanks.

]]> By: Jon H http://boredzo.org/blog/archives/2008-01-11/how-to-create-a-ram-disk-with-the-contents-of-a-disk-image-preloaded#comment-155490 Jon H Sat, 12 Jan 2008 06:07:48 +0000 http://boredzo.org/blog/archives/2008-01-11/how-to-create-a-ram-disk-with-the-contents-of-another-image-preloaded#comment-155490 "The safest way is copy and paste." Actually the safest way is probably to copy, paste into an editor, build and check the command there, then copy it and paste it into Terminal. I've occasionally had a copy/paste go wrong when I accidentally include a CR or LF or something, resulting in Terminal acting as if I'd hit Return. If that happened preceded by a bad selection and copy, you could end up pasting a wrong drive identifier and kicking off the copy. "The safest way is copy and paste."

Actually the safest way is probably to copy, paste into an editor, build and check the command there, then copy it and paste it into Terminal.

I've occasionally had a copy/paste go wrong when I accidentally include a CR or LF or something, resulting in Terminal acting as if I'd hit Return. If that happened preceded by a bad selection and copy, you could end up pasting a wrong drive identifier and kicking off the copy.

]]>