On 1/11/07, Karl Cunningham <[EMAIL PROTECTED]> wrote:
On 1/11/2007 9:34 AM, Carl Lowenstein wrote:
> On 1/10/07, Karl Cunningham <[EMAIL PROTECTED]> wrote:
>> Michael O'Keefe wrote:
>> >> Before I asked I tried the following in my home directory, containing
>> >> a bunch of normal stuff.
>> >> $ find . -type f | xargs gzip -q - | wc -c
>> >>
>> >> After a time and a lot of crunching it returned 60. Obviously wrong,
>> >> given:
>> >
>> > Where's your -c/--stdout so it can feed 'wc -c' ?
>>
>> Yes, you're right.
>>
>> OK, I've learned my lesson: don't try this with one's home directory!
>> This was a bad idea. Now *many* files in my home directory have been
>> gzipped, and the original is gone. Couldn't ssh to the box any more
>> since everything in ~/.ssh was gzipped. Ugh! Now trying to fix things
>> up...
>>
>
> I'm afraid you dug yourself into a hole, aided and abetted by bunches
> of advice that didn't see that "-c" was missing from the command
> line. Fortunately, gzip is reasonably conservative and keeps file
> names, dates, and permissions. So "all you need to do" is something
> like:
> $ find . -name \*.gz -xargs gunzip
>
> But of course from some place where you can get your hands on the machine.
Hi Carl,
Logged in at the console and straightened out my ~/.ssh directory, then
was able to ssh in as usual. I started to what you suggested thinking it
would be simple, but there were things like foo.tar.gz that where then
ungzipped where they should have been left alone. A restore of my home
directory from backup took care of the problem.
Moral of the story: mess with a small, insignificant directory first.
And a backup... don't foobar $HOME without it!
And don't turn off warning messages (-q). They might give you a clue
as to what is happening before it is too late.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
