|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] RAM Block Device
|
- From: TuskenTower <tuskentower@gmail.com>
- To: "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
- Subject: Re: [PLUG] RAM Block Device
- Date: Thu, 21 Jun 2007 11:22:43 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Gacyzd9vAnoB3q+X0PxK/oSJZewTdROspG0NDuyS92vFGDO+vpfVk0jxnFFF6/tcvn66lBSbqbE/M1fJ9poDc+RDhFtprniFmkPNKsuqMJHFpYq0L7zqyRIhfYki9ysce5IH/GAJi8wQd2DcRHyWmcW3YAGn+ck52/pVd+EAykI=
- Reply-to: Philadelphia Linux User's Group Discussion List <plug@lists.phillylinux.org>
- Sender: plug-bounces@lists.phillylinux.org
Jon,
LOL, its not a problem. I happened to remember people whining about
this a while back, so I knew Google had to have my answer. Do post
back when you find out what can be done to get /dev/mem and /dev/kmem
information.
thanks,
Amul
On 6/21/07, Jon Nelson <lists@linuxnotes.net> wrote:
Amul,
Thanks for the help. I also Googled my question before posting on the
list, but your Google-fu is obviously much better.
Jon
On Thu, 2007-06-21 at 09:46 -0400, TuskenTower wrote:
> Jon,
> There's a technote on this very subject.
> http://developer.apple.com/documentation/Darwin/Conceptual/KernelProgramming/security/chapter_3_section_7.html
>
> Here's a trick for 10.4
> http://www.clusterresources.com/pipermail/torquedev/2006-December/000395.html
>
> BTW, I Googled your question. :)
> http://www.google.com/search?q=Intel+Macs+%2Fdev%2Fmem+and+%2Fdev%
> 2Fkmem&ie=utf-8&oe=utf-8&aq=t&rls=org.debian:en-US:unofficial&client=iceweasel-a
>
> Amul
>
> On 6/21/07, Jon Nelson <lists@linuxnotes.net> wrote:
> > Hi All,
> >
> > On PPC based Macs you could capture the contents of RAM with:
> >
> > $ dd if=/dev/mem of=/home/me/mem.bin bs=1024
> >
> > Now with the Intel Macs /dev/mem and /dev/kmem are no longer there.
> > Does anyone know how to track down which block device is associated
> with
> > RAM?
> >
> > TIA,
> >
> > Jon
> >
> >
> ___________________________________________________________________________
> > Philadelphia Linux Users Group --
> http://www.phillylinux.org
> > Announcements -
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > General Discussion --
> http://lists.phillylinux.org/mailman/listinfo/plug
> >
> ___________________________________________________________________________
> Philadelphia Linux Users Group --
> http://www.phillylinux.org
> Announcements -
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion --
> http://lists.phillylinux.org/mailman/listinfo/plug
>
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|