Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 9 Oct 2001 11:21:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 9 Oct 2001 11:21:28 -0400 Received: from hermes.toad.net ([162.33.130.251]:12705 "EHLO hermes.toad.net") by vger.kernel.org with ESMTP id ; Tue, 9 Oct 2001 11:21:15 -0400 Subject: Re: sysctl interface to bootflags? From: Thomas Hood To: Dave Jones Cc: linux-kernel@vger.kernel.org In-Reply-To: In-Reply-To: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 09 Oct 2001 11:21:14 -0400 Message-Id: <1002640876.1103.21.camel@thanatos> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi. I looked at your code and I saw that it depended on ACPI. Since ACPI doesn't work on my machine, I thought I should look for another solution. However, Alan now tells me that what I want to do can already be done via /dev/nvram. Thanks to both of you. Thomas On Tue, 2001-10-09 at 10:15, Dave Jones wrote: > On 9 Oct 2001, Thomas Hood wrote: > > > Would it be a good idea to do this using the sysctl infrastructure? > > If so, can someone please suggest an appropriate pathname for > > the flag files? How about "/proc/sys/BIOS/bootflags/diagnostics" > > and "/proc/sys/BIOS/bootflags/PnP-OS" ? > > If this is a bad idea, someone please stop me before I waste my > > time implementing it. > > Last week, I pointed you at http://www.codemonkey.org.uk/sbf.c > Can you give a reason why this needs to be done in kernel space ? > > regards, > > Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/