linux-kernel - Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060731051547.GB29058@kroah.com>
Date:	Sun, 30 Jul 2006 22:15:47 -0700
From:	Greg KH <greg@...ah.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	ajwade@...001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com,
	laurent.riffard@...e.fr, andrew.j.wade@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

On Sun, Jul 30, 2006 at 09:50:25PM -0700, Andrew Morton wrote:
> On Sun, 30 Jul 2006 21:35:42 -0700
> Greg KH <greg@...ah.com> wrote:
> 
> > Remember, FC3 is now in Legacy support mode, not something the mainline
> > kernel should have to worry about.
> 
> It's not specifically related to FC3.  It's udev - we've broken _any_
> distribution which uses a two-year-old udev.  In fact we're proposing
> breaking any distro which has an older-than-ten-month udev.  That's really
> bad.

Why?  What do you propose we do then?  Wait a year?  Two years?  I've
already stated that I'm going to wait 3 more months in order to be able
to fix up the currently supported distros to handle the changes needed.
I'll even dig up RC4 to get that working, as it shouldn't be that hard
to do so.  What more can I do?

> It's worse on FC3 because there is, as far as I can tell, no rpm or srpm
> which can be used to unbreak it.  And pointing at Documentation/Changes
> doesn't alter that, does it?

No, but it does show that you are running on an unsupported distro.  Why
should the kernel developers have to support this?  When is the cut-off
date?

> Personally, there's no way I'm upgrading this box because I _want_ to run
> old distros to catch things like this.  So I'll hack it around to work
> somehow.  I can do that, because I'm a developer. 

And that's the only group of people who would try to do this.
Seriously, I don't see the complaint here.  It's an unsupported distro
by the very makers of that distro.  How long should the community have
to care about a distro after the creators of it have abandonded it?

> Are we going to stop doing this soon?

Not if we want to keep on making things better.  The real reason I made
these changes is to get power management working better.  We need to get
the devices into the proper place in the sysfs tree in order to handle
suspend/resume for classes of devices properly.  That's what Linus's
patch did, and now I'm moving the devices to allow it to really happen.

thanks,

greg k-h
-
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/