Re: [osol-code] Why "savecore -L" doesn't work for me?

# savecore -v -L savecore: dedicated dump device required The error message is exact and complete... ___ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Re: [osol-code] Why "savecore -L" doesn't work for me?

Stephen Hahn wrote: * Oliver Yang <[EMAIL PROTECTED]> [2006-07-24 22:38]: Hi All, When I try to savecore on a running system, we found it doesn't work on my machine: # dumpadm Dump content: kernel pages Dump device: /dev/dsk/c0d0s1 (swap) Savecore directory: /var/crash/palace Sa

Re: [osol-code] Why "savecore -L" doesn't work for me?

* Oliver Yang <[EMAIL PROTECTED]> [2006-07-24 22:38]: > Hi All, > > When I try to savecore on a running system, we found it doesn't work on > my machine: > > # dumpadm > Dump content: kernel pages > Dump device: /dev/dsk/c0d0s1 (swap) > Savecore directory: /var/crash/palace > Savecor

[osol-code] Why "savecore -L" doesn't work for me?

Hi All, When I try to savecore on a running system, we found it doesn't work on my machine: # dumpadm Dump content: kernel pages Dump device: /dev/dsk/c0d0s1 (swap) Savecore directory: /var/crash/palace Savecore enabled: yes # savecore -v -L savecore: dedicated dump device require

Re: [osol-code] ioctls & MULTI_DATA_MODEL

Amit Mitkar wrote: hi, I have a 64 bit driver with an ioctl entry point that can be called from 32 bit apps. From the various docs available it seems that I need to use the _MULTI_DATA_MODEL macro in my code to copy the ioctl arg appropriately depending upon what kind of app calls it.

[osol-code] ioctls & MULTI_DATA_MODEL

hi, I have a 64 bit driver with an ioctl entry point that can be called from 32 bit apps. From the various docs available it seems that I need to use the _MULTI_DATA_MODEL macro in my code to copy the ioctl arg appropriately depending upon what kind of app calls it. The ioctls to t