From owner-freebsd-bugs Mon Oct 9 09:23:44 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15259 for bugs-outgoing; Mon, 9 Oct 1995 09:23:44 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15254 for ; Mon, 9 Oct 1995 09:23:42 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA08502; Mon, 9 Oct 1995 12:23:34 -0400 Date: Mon, 9 Oct 1995 12:23:34 -0400 From: "Garrett A. Wollman" Message-Id: <9510091623.AA08502@halloran-eldar.lcs.mit.edu> To: Lyndon Nerenberg VE7TCP Cc: freebsd-bugs@freefall.freebsd.org Subject: getbootfile() In-Reply-To: <199510080229.TAA20131@multivac.orthanc.com> References: <199510080229.TAA20131@multivac.orthanc.com> Sender: owner-bugs@FreeBSD.org Precedence: bulk < said: > FreeBSD I can't see how it would be generally useful. Not having > copies of the relevent POSIX standards at hand I'm curious as to > how this information can be obtained portably (if at all). POSIX does not make any guarantees that there even is such a thing as a file that has the kernel in it. POSIX doesn't even guarantee that there is a `kernel' at all. > Is this > routine being standardized at all? No. Any code that attempts to play around with the kernel's namelist is by definiton unportable. If anybody else wants to follow my lead, they are welcome to do so. > It seems that sysctl(3) is a > more logical place for this information to be obtained. You are certainly welcome to retrieve the kern.bootfile MIB varaible if you so desire. You will probably find that only FreeBSD supports this as well. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant