From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: compiling udev 141 on linux 2.4
Date: Thu, 23 Apr 2009 22:19:24 +0000 [thread overview]
Message-ID: <ac3eb2510904231519sec3906auc4d8d5dc2fea117c@mail.gmail.com> (raw)
In-Reply-To: <310ca25e50765edce514c2eaa65ea3ff@gzp>
On Fri, Apr 24, 2009 at 00:14, Gabor Z. Papp <gzp@papp.hu> wrote:
> * Kay Sievers <kay.sievers@vrfy.org>:
>
> | > Linux gzpLinux 2.4.37 #1 Tue Dec 2 19:24:20 CET 2008 i686 GNU/Linux
>
> | Oh, what do you want with udev in that environment, it depends on
> | sysfs and uevents wich are only in 2.6 kernels.
>
> Chicken and egg, you know...
You can run 2.6 without udev just fine, if you don't need to do fancy
stuff. Especially coming from 2.4, there should be no problem to run a
2.6 kernel with a static /dev and add udev later ...
Kay
next prev parent reply other threads:[~2009-04-23 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 21:27 compiling udev 141 on linux 2.4 Gabor Z. Papp
2009-04-23 22:10 ` Kay Sievers
2009-04-23 22:14 ` Gabor Z. Papp
2009-04-23 22:19 ` Kay Sievers [this message]
2009-04-29 18:39 ` Gabor Z. Papp
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=ac3eb2510904231519sec3906auc4d8d5dc2fea117c@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).