lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTik1G3E6RP8cEK2JoPcqZp0Q16nK9F-4tAtXWnPk@mail.gmail.com>
Date:	Thu, 15 Jul 2010 15:00:31 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <axboe@...nel.dk>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	alsa-devel@...a-project.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-scsi@...r.kernel.org, Takashi Iwai <tiwai@...e.de>,
	Greg KH <greg@...ah.com>, Kay Sievers <kay.sievers@...y.org>,
	linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>,
	"James E.J. Bottomley" <James.Bottomley@...e.de>,
	Alan Stern <stern@...land.harvard.edu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Ingo Molnar <mingo@...e.hu>, Tejun Heo <tj@...nel.org>,
	Alexey Kuznetsov <kuznet@....inr.ac.ru>,
	Stephen Hemminger <shemminger@...tta.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [alsa-devel] [PATCH] driver core: remove CONFIG_SYSFS_DEPRECATED

On Thu, Jul 15, 2010 at 2:14 PM, Greg KH <gregkh@...e.de> wrote:
> On Thu, Jul 15, 2010 at 10:24:18AM +1000, Dave Airlie wrote:
>> On Thu, Jul 15, 2010 at 9:38 AM, Andrew Morton
>> <akpm@...ux-foundation.org> wrote:
>> > On Fri, 9 Jul 2010 11:54:50 -0700
>> > Greg Kroah-Hartman <gregkh@...e.de> wrote:
>> >
>> >> This is no longer needed by any userspace tools, so it's safe to
>> >> remove.
>>
>> Also still used for booting mainline kernels on RHEL5 userspaces.
>
> Really?  I thought that was fixed a long time ago.  What kernel was
> RHEL5 originally based on?
>
> And note that no RHEL5 user is going to be using a .36 kernel on their
> system, that's a completely unsupported and unadvised situation.  Heck,
> I'd be amazed if a .34 kernel.org kernel boots on the thing, does it?
>

I think some people do it internally, last time I did it was to test
something I was backporting, so you want to make sure the upstream
version boots and the backported version also boots on the same
hw/userspace.

original kernel was 2.6.18.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ