now that kdump works without dumping core :), i've got a question...

why does kdump report a successful read like this?

...
 27049 cat      CALL  read(0,0xbfbfcb44,0x1000)
 27049 cat      GIO   fd 0 read 4088 bytes
 27049 cat      GIO   fd 0 read 8 bytes
 27049 cat      RET   read 4096/0x1000
...

specifically, why two instances of "gio" and then the return?  is it
that the kernel pushes ktrace info out to disk in increments of the
machine's page size?

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."