From owner-freebsd-bugs  Sat Oct  7 19:29:47 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id TAA11245
          for bugs-outgoing; Sat, 7 Oct 1995 19:29:47 -0700
Received: from multivac.orthanc.com (root@multivac.orthanc.com [204.244.20.2])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA11240
          for <freebsd-bugs@freefall.freebsd.org>; Sat, 7 Oct 1995 19:29:44 -0700
Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7/8.7) with SMTP id TAA20131 for <freebsd-bugs@freefall.freebsd.org>; Sat, 7 Oct 1995 19:29:36 -0700 (PDT)
Message-Id: <199510080229.TAA20131@multivac.orthanc.com>
X-Authentication-Warning: multivac.orthanc.com: Host lyndon@localhost didn't use HELO protocol
From: Lyndon Nerenberg VE7TCP <lyndon@orthanc.com>
To: freebsd-bugs@freefall.freebsd.org
Subject: getbootfile()
X-Attribution: VE7TCP
Date: Sat, 07 Oct 1995 19:29:35 -0700
Sender: owner-bugs@FreeBSD.org
Precedence: bulk

Further to the rwhod multicast submission I sent in the other day,
I've been looking at getbootfile() a bit more closely. I'm curious
(concerned) about the portability of using this. Being specific to
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). Is this
routine being standardized at all? It seems that sysctl(3) is a
more logical place for this information to be obtained.

On a related note, the 2.0.5 getbootfile(3) man page references
sysctl(2). This should be sysctl(3).

--lyndon