From: Al Viro <viro@ZenIV.linux.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Pavel Machek <pavel@ucw.cz>,
pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
khilman@kernel.org, aaro.koskinen@iki.fi,
ivo.g.dimitrov.75@gmail.com
Subject: Re: Getting new udev to run with 2.6.28
Date: Sat, 10 Jan 2015 21:18:58 +0000 [thread overview]
Message-ID: <20150110211857.GA22149@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150110181710.GA8884@kroah.com>
On Sat, Jan 10, 2015 at 10:17:10AM -0800, Greg KH wrote:
> > > Yes, 3.18, please use that instead.
> >
> > Can't, sorry. My goal is to get 3.18/3.19 working, but I really need
> > working kernel to debug userland (and then use that userland to debug kernel).
> >
> > > Seriously, lots of things have changed, if you want to run a "new"
> > > version of udev with an old kernel, try eudev, they have been attempting
> > > to keep "legacy" support around in it, don't know how well it has been
> > > working though, you really are on your own.
> >
> > I was hoping someone has devtmpfs patches I could just apply over
> > 2.6.28 and get a working system?
>
> If you want such a crazy thing, you have all of the source to do it
> yourself, good luck.
... and this, boys and girls, is why quite a few of us have loathed udev
way before it got merged into even nastier shitpile. Still do, for that
matter.
next prev parent reply other threads:[~2015-01-10 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 17:39 Getting new udev to run with 2.6.28 Pavel Machek
2015-01-10 18:05 ` Greg KH
2015-01-10 18:09 ` Pavel Machek
2015-01-10 18:17 ` Greg KH
2015-01-10 21:18 ` Al Viro [this message]
2015-01-10 22:25 ` Martin Steigerwald
2015-01-10 23:06 ` Al Viro
2015-01-11 9:04 ` Martin Steigerwald
2015-01-11 10:12 ` Pavel Machek
2015-01-11 10:43 ` Richard Weinberger
2015-01-10 19:54 ` Sven Joachim
2015-01-10 19:13 ` Aaro Koskinen
2015-01-10 21:18 ` Al Viro
2015-01-10 22:49 ` Pavel Machek
2015-01-10 22:59 ` Aaro Koskinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150110211857.GA22149@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=aaro.koskinen@iki.fi \
--cc=greg@kroah.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@debian.org \
--cc=sre@ring0.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox