From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: facorread@gmail.com
Subject: Re: 2.6.22-rc2 and libata/shutdown
In-Reply-To: <xs4all.4655FDEA.30209@gmail.com>
References: <xs4all.20070524102122.GA8652@localhost.localdomain>
Organization: 
Cc: linux-kernel@vger.kernel.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Message-Id: <E1HrLmU-0003XG-OM@n2o.xs4all.nl>
Date: Fri, 25 May 2007 00:27:38 +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1320
Lines: 35

In article <xs4all.4655FDEA.30209@gmail.com> you write:
>Hello Damien, people...
>
>Damien Wyart wrote:
>> Hello,
>> 
>> After trying 2.6.22-rc2, I noticed the warning message from libata about
>> upgrading shutdown(8). First, I have two SATA disks, and get the warning for
>> only one of them. Second, I double-checked the source of shutdown for my
>> distro (Debian unstable), and do not see anything related to issueing
>> STANDBYNOW.
>
>The warning is pretty important, and you can check it at
>
>http://linux-ata.org/shutdown.html
>
>I have been checking the sysvinit sources and I cannot see the portions
>on scanning SCSI or SATA
>disks. I only see the IDE scanning and standby-related code at
>src/hddown.c. Does anybody know
>how in the world are the SATA disks put to sleep in userspace?

Standard sysvinit doesn't do this, but many distributions have
patched it so that it does.

Debian has patched it as well; if you unpack the debian
sources you won't see it right away though. The extra patches
are applied by the build process, patches are under debian/

Mike.
-
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/