On 28/06/2014 15:05, Dale wrote: > Neil Bothwick wrote: >> On Sat, 28 Jun 2014 06:55:28 -0500, Dale wrote: >> >>> It was more Murphy's law I was worried about. ;-) >> Hasn't that been deprecated in favour of Dale's Law? >> >> > > If it hasn't, maybe it should. It's strange tho, I have good luck with > a lot of things, even computer hardware really, but messing with some > new software generally leads to trouble. Hal was the first really bad > thing. There was some other thing that popped up that I can't recall > and recently the init thingy kept me from booting. I then booted the > init thingy off here. I just keep a up to date Kubuntu disk laying > around. ;-) New software just doesn't like me or my rig much. Older > stuff seems to work fine. It's the things that seem to be new that > really crawl under my skin. It seems they always bite me even when it > works for most everyone else. That was pretty much the case with hal. > It just would not work on my rig. I give the dev credit tho, he > realized it was a mess and started over from scratch. At least he > realized the boo boo. > > On this old drive. I got my data copied over and tested the stuffin out > of the new drive and then tested it a few more times. Looks good for > the new drive. I'm doing a dd on the old drive now and I plan to let it > at least get to where that bad spot is. I figure if I let dd do its > thing on the whole drive, that should get it, unless I lose power or > something and have to stop it. After that, I'm going to put a file > system on it and fill it up and test it and see what it says then. > Maybe it will fix itself and I can at least use it as a occasional > backup or something. I dunno. > > I noticed when I copied the data over that some files had a line of > question marks in the name. Since a question mark is a wild card, I > can't find them now. How does one search for a file name that has a > wild card in it?
escape the character with a \ But that's not your main problem. You got those filenames because the source disk somehow has a problem and the names couldn't be read properly. So junk was used instead. Reasons vary, but the basics never change: there is a problem with your source disk and now you need to go find what that problem is. -- Alan McKinnon alan.mckin...@gmail.com
