On 30 May 2014 03:10, "Michael Biebl" <<a href="mailto:mbiebl@gmail.com">mbiebl@gmail.com</a>> wrote: > > 2014-05-30 3:55 GMT+02:00 Greg KH <<a href="mailto:gregkh@linuxfoundation.org">gregkh@linuxfoundation.org</a>>: > > On Fri, May 30, 2014 at 03:40:52AM +0200, Zbigniew Jędrzejewski-Szmek wrote: > >> On Thu, May 29, 2014 at 08:54:22PM -0400, Cristian Rodríguez wrote: > >> > As discussed ad-nauseum previously, it is the kernel's task > >> > to load firmware, not udev's. > >> I think this patch is a bad idea - it makes things harder for people > >> who, for whatever reason, good or bad, run older kernels. At the same > >> time, our maintenance burden is pretty much zero. > > > > What kernel version are you thinking still needs this, that would ever > > want to have a new version of systemd on it? > > Debian Wheezy does ship with 3.2 and we do provide backports of newer > systemd versions of it. > It also simplifies dist-upgrades if one can still boot with the old > kernel in case the new one fails to boot for whatever reason. > > So +1 for keeping it. > As Zbiginiew said, the maintenance cost is basically zero. While it is not very important that this patch gets applied now, as a general rule it seems extremely unlikely that we will keep being able to boot on such old kernels going forward. Maybe it would be best to find some alternative way to achieve your features sooner rather than later? You could for instance use the double reboot mechanism to upgrade from really old kernels and some sort of double buffering or snapshots to support rollback. Running new user space on ancient kernels seems like it would just cause more work at little to no gain... Just my two cents, Tom