On Fri, Mar 04, 2005 at 02:31:06PM +1100, Paul Hampson wrote:
> On Fri, Mar 04, 2005 at 12:18:14AM +0100, Bernd Eckenfels wrote:
> > In article <[EMAIL PROTECTED]> you wrote:
> > > If so... then it's flat-out not available on the set of systems in
> > > question
> 
> > Hm? it is on all my  systems:
> 
> > # cat /proc/cmdline
> > auto BOOT_IMAGE=v2.6.8.1 ro root=811
> 
> Can we assume your systems are all Linux-based Debian? I expect
> neither of the BSD-type Debian ports has anything in /proc that's
> not a pid or self... I have a sneaking suspicion that the Hurd-
> based Debian port is like that too, but I've never booted Hurd.

As noted to a couple of people in private, this is specifically the case.
On NetBSD, /proc is solely process info (and is, in fact, entirely optional
right now, if recommended). Stuff found in /proc/sys is found with sysctl,
but there isn't really any preservation of information about the kernel
startup that I know of; I can't speak for Hurd ports.

> I'm not gonna speculate on the win32-based port that may or may
> not actually have come into existance, but I strongly doubt it
> has (would have) a /proc on the grounds that the win32 kernel
> doesn't actually have a / to mount things under...

Can't comment on this.

> And given that even Linux itself is looking to migrate non-PID
> things from /proc to /sys where sensible, I wouldn't rely on
> things like /proc/cmdline to be around come Linux 2.8.

We can only hope (though cmdline stuff is still, in some sense, proc
related... /proc/kernel?)
-- 
Joel Aelwyn <[EMAIL PROTECTED]>                                       ,''`.
                                                                     : :' :
                                                                     `. `'
                                                                       `-

Attachment: signature.asc
Description: Digital signature

Reply via email to