lkcd
[Top] [All Lists]

RE: Current snapshot

To: "'Matt D. Robinson'" <yakker@xxxxxxxxxxxxxx>, "Schaal, Richard" <richard.schaal@xxxxxxxxx>
Subject: RE: Current snapshot
From: "Schaal, Richard" <richard.schaal@xxxxxxxxx>
Date: Mon, 17 Sep 2001 08:46:24 -0700
Cc: "'lkcd@xxxxxxxxxxx'" <lkcd@xxxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
My mistake.  I was having problems realizing that the configuration got
split between the /sbin/lkcd script and the
/etc/syconfig/dump script and having the script refer to /dev/vmdump
confused me further.  It appears to be working ok now that I have the
configuration corrected.  I think the biggest problem I had was to point
/dev/dump at the target drive for the dump rather than as the access method
to the dump driver.

Thanks!

Richard



-----Original Message-----
From: Matt D. Robinson [mailto:yakker@xxxxxxxxxxxxxx]
Sent: Friday, September 14, 2001 7:02 PM
To: Schaal, Richard
Cc: 'lkcd@xxxxxxxxxxx'
Subject: Re: Current snapshot


"Schaal, Richard" wrote:
> 
> Hi Matt,
> I have retrieved the current CVS image and as you had previously
suggested,
> applied the files in the
> 2.4 tree to a linux-2.4.8 kernel.  I hate to be a whiner, but it didn't
> build...  mostly in the dump_gzip.c
> file - a few include files weren't as well as a missing "=" sign in the
> initialization of the dump_compress_t structure.

I know that dump_gzip.c doesn't work yet, but it wasn't
intended to be part of the main patch as of yet.  I have to convert over
a new zlib.h, which isn't done yet.  All the rest of the files work, right?
I know that you don't have to turn on DUMP_COMPRESS_GZIP for now.

> I did get the code to compile eventually, but am now wondering whether you
> can make my life easier by obsoleting some files.
> 
>         2.4/driver/block/vmdump.c       appears to be obsolete.
>         lkcdutils/scripts/sbin.vmdump           ditto
>         lkcdutils/scripts/sysconfig.vmdump      ditto

Sure, I can do that this evening.  Should be easy enough.  It's
about time that all the vmdump.c files get moved.

> There seems to be some sort of disconnect in the new startup scripts as
> well.  In the previous version, the
> dump parameters were squirted into the dump driver through the /proc
> interface.  Now, lkcd_config is failing
> an IOCTL on the dump device.

What's the failure?  The new /sbin/lkcd (no longer /sbin/vmdump) should
use /dev/dump (which /sbin/lkcd creates) to run the ioctl.  Again, the
modules have to be installed, etc.  Do you have dump built directly
into the kernel, or is it a module?

> Please set me on the true path to enlightenment, happiness and dumping.

Let me know if this works for you.  I'll be around all night.  I'm
working on the RPM build for 'lkcdutils'.

--Matt

> Many thanks,
> 
> Richard
> 
> --
> Richard.Schaal@xxxxxxxxx                  Intel Corporation
> Ph: (408)765-1579                         Richard Schaal
>                                           Mail Stop SC12-308
>                                           3600 Juliette Lane
> "I can type faster than I think!"         Santa Clara, CA 95052

<Prev in Thread] Current Thread [Next in Thread>