From: Pavel Machek <pavel@ucw.cz>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
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, ivo.g.dimitrov.75@gmail.com,
Greg KH <greg@kroah.com>
Subject: Re: Getting new udev to run with 2.6.28
Date: Sat, 10 Jan 2015 23:49:02 +0100 [thread overview]
Message-ID: <20150110224902.GA25534@amd> (raw)
In-Reply-To: <20150110211805.GZ22149@ZenIV.linux.org.uk>
On Sat 2015-01-10 21:18:05, Al Viro wrote:
> On Sat, Jan 10, 2015 at 09:13:35PM +0200, Aaro Koskinen wrote:
> > Hi,
> >
> > On Sat, Jan 10, 2015 at 06:39:20PM +0100, Pavel Machek wrote:
> > > N900 has real problems on 3.19, and 2.6.28 should be very well
> > > debugged version. Getting it to compile on recent distribution was
> > > fun, but I succeeded. Unfortunately, Debian 7's udev does not work
> > > with 2.6.28...
> >
> > I guess you will have many other issues too if you want to run
> > such combination (legacy kernel + modern userspace). E.g. current glibc
> > requires >= 2.6.32.
>
> How current is current and just what does it require in 2.6.32?
Debian 7 seems to contain
root@n900:~# ls /lib/arm-linux-gnueabi/libc
libc-2.13.so
. And that one seems to be happy with 2.6.28. Its just udev that is
the problem.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-01-10 22:49 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
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 [this message]
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=20150110224902.GA25534@amd \
--to=pavel@ucw.cz \
--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=sre@debian.org \
--cc=sre@ring0.de \
--cc=viro@ZenIV.linux.org.uk \
/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