From: Thomas Hood <jdthood@mail.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysctl interface to bootflags?
Date: 09 Oct 2001 11:21:14 -0400 [thread overview]
Message-ID: <1002640876.1103.21.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.30.0110091613490.32557-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0110091613490.32557-100000@Appserv.suse.de>
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.
next prev parent reply other threads:[~2001-10-09 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 14:01 sysctl interface to bootflags? Thomas Hood
2001-10-09 14:15 ` Dave Jones
2001-10-09 15:21 ` Thomas Hood [this message]
2001-10-09 15:34 ` Dave Jones
2001-10-09 15:50 ` Thomas Hood
2001-10-09 15:52 ` Dave Jones
2001-10-09 15:56 ` Thomas Hood
2001-10-09 16:53 ` Dave Jones
2001-10-09 14:18 ` Alan Cox
2001-10-09 15:35 ` Thomas Hood
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 22:48 Thomas Hood
2001-10-10 14:05 ` Dave Jones
2001-10-09 3:29 Thomas Hood
2001-10-09 2:56 Thomas Hood
2001-10-10 6:46 ` Dave Jones
2001-10-10 12:37 ` Thomas Hood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1002640876.1103.21.camel@thanatos \
--to=jdthood@mail.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox