From: Frank Neuber <neuber@convergence.de>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Milind <dmilind@india.hp.com>,
linux-kernel@vger.kernel.org, blore-linux@yahoogroups.com
Subject: Re: Info about /dev/kmem required
Date: Mon, 20 Aug 2001 20:21:08 +0200 [thread overview]
Message-ID: <20010820202108.A7121@jupiter> (raw)
In-Reply-To: <3B7D232B.FEA189AD@india.hp.com> <20010817175739.I19385@arthur.ubicom.tudelft.nl>
In-Reply-To: <20010817175739.I19385@arthur.ubicom.tudelft.nl>
On Fri, Aug 17, 2001 at 05:57:39PM -0400, Erik Mouw wrote:
> On Fri, Aug 17, 2001 at 07:29:08PM +0530, Milind wrote:
> > I wanted some info about ' /dev/kmem ' file with respect to following
> >
> > 1) What this file contains?
>
> >From Documentation/devices.txt:
>
> 1 char Memory devices
> 1 = /dev/mem Physical memory access
> 2 = /dev/kmem Kernel virtual memory access
>
> > 2) Who writes into this file?
>
> Normally nobody does, though it can be used to patch up a running
> system (in theory).
>
> > Reply at the earliest.
>
> I'm sorry, we're not a helpdesk.
I think You can use /dev/kmem as an corefile for gdb. So it is possible to debug
the linux kernel (of course read only :-)).
Frank
--
Dipl.-Ing. Elektrotechnik convergence integrated media gmbh / HW
Frank Neuber Rosenthalerstr.51 / 10178 Berlin
Email: neuber@convergence.de Phone: +49(0)30-72 62 06 50
WWW: www.convergence.de Fax: +49(0)30-72 62 06 55
next prev parent reply other threads:[~2001-08-20 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 13:59 Info about /dev/kmem required Milind
2001-08-17 21:57 ` Erik Mouw
2001-08-20 18:21 ` Frank Neuber [this message]
2001-08-21 12:39 ` Erik Mouw
2001-08-21 12:35 ` Frank Neuber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010820202108.A7121@jupiter \
--to=neuber@convergence.de \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=blore-linux@yahoogroups.com \
--cc=dmilind@india.hp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.