Re: Let init know user wants to shutdown

From: John Fremlin <chief@bandits.org>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'John Fremlin'" <chief@bandits.org>,
	"'Pavel Machek'" <pavel@suse.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	"Acpi-linux (E-mail)" <acpi@phobos.fachschaften.tu-muenchen.de>
Subject: Re: Let init know user wants to shutdown
Date: 11 Apr 2001 19:29:05 +0100	[thread overview]
Message-ID: <m2d7aj9tou.fsf@boreas.yi.org.> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E8905DE822@orsmsx35.jf.intel.com>
In-Reply-To: "Grover, Andrew"'s message of "Wed, 11 Apr 2001 10:06:52 -0700"

"Grover, Andrew" <andrew.grover@intel.com> writes:

[...]

> > > > +		printk ("acpi: Power button pressed!\n");
> > 
> > [...]
> > 
> > > > +		printk("acpi: Sleep button pressed!\n");
> > 
> > Do you think you could keep the above part of the patch? It would be
> > nice to know how much of ACPI was actually working ;-)

> I'm hesitant to do this, since 1) You can put those printk's in
> yourself to find out if your particular system is working and 2) You
> can just cat /proc/sys/event, hit a button, and you should see
> output if it works.

Hmm. Pavel Machek could hardly be described as a newbie at hacking
stuff, and yet he says, "I hunted bug for few hours, thinking that
kernel does not get the event at all."

The printks are certainly clearer than cat'ing some binary garbage to
the console and will help out the casual user who doesn't want to
recompile kernel and reboot just to discover that the damn thing
doesn't work.

[...]

-- 

	http://www.penguinpowered.com/~vii