On Fri, 6 Aug 1999, Matt Stegman wrote:
> On Fri, 6 Aug 1999, Ramon Gandia wrote:
>
> > /proc does NOT exist in your hard disk, although the directory
> > exists in your hard disk. This is easier to grasp if you
> > do not think "directory" but think "mount point".
>
> You might say that /proc contains a "virtual filesystem." Take a look at
> the fstab entry for /proc and /dev/pts.
>
> > Basically, /proc is a window into your computer setup. All the
> > info in there is in RAM. You can change it there, but at the
> > next reboot it is gone. It is best if you do not write to it,
> > although some hackers do this to make some on-the-fly changes.
> > If you do so, your computer could crash or could get annoyed
> > and format your hard drive and those connected to it via the
> > internet.
>
> Yah- I wouldn't touch /proc with a 50-foot pole for a million dollars.
> Very dangerous stuff there. Although you're welcome to read it with
> impunity: you probably can't damage anything just by looking at it.
Touch it all you want to, but be damned sure what your fondleing when your
doing your fondleing, you'll find comments in the kernel source.
/usr/src/linux/drivers/net/ne* is the code for the NIC's
> > Another analogy is that this is Linux's "registry".
>
> I diagree. I presume you're making the analogy to thw Windows registry?
> Windows' registry contains configuration info for applications (software
> configuration). I don't think there's a single byte of info about hardware
> configuration- which is what /proc is all about. /proc also contains info
> on running processes. Again, nothing like this is in the Windows
> registry.
Actualy it is theres more hardware stuff there then sticks to shake at,
its not near as flexable however :)
> If you're interested in IRQs and IO addresses, try `cat /proc/interrupts`
> and `cat /proc/ioports`. This might be what you're looking for.
>
> -Matt Stegman
> <[EMAIL PROTECTED]>
>
>
