linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piet Delaney <piet@bluelane.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev on Fedore 5 - Gentoo script not very helpfull in LFS
Date: Fri, 04 Aug 2006 23:55:59 +0000	[thread overview]
Message-ID: <1154735759.8839.102.camel@piet2.bluelane.com> (raw)
In-Reply-To: <1154678172.8839.84.camel@piet2.bluelane.com>

On Fri, 2006-08-04 at 08:12 -0700, Dan Nicholson wrote:
> On 8/4/06, Piet Delaney <piet@bluelane.com> wrote:
> >
> > I'm starting to lean towards just waiting till we have Linux From
> > Scratch (LFS) 6.2 working and then switching to the new event mechanism.
> > It's about to be released and supported the new 2.6.16 kernel and the
> > new udev-096. Perhaps I can extract 6.2 udev scripts part of
> > 6.2 without too much work and supports pre 2.6.16 kernels; I suspect
> > not.
> 
> 6.2 is out now. Here's the book and the bootscripts directly.
> 
> http://www.linuxfromscratch.org/lfs/view/stable/
> http://wiki.linuxfromscratch.org/lfs/browser/tags/6.2/bootscripts/lfs/init.d/udev?revw62
> http://wiki.linuxfromscratch.org/lfs/browser/tags/6.2/bootscripts/lfs/init.d/udev_retry?revw62
> 
> They are installed as S10udev and S45udev_retry. No attempt at
> backwards compatibility with earlier kernels or udev is attempted.
> We're assuming you followed the LFS book and are using the packages
> mentioned there. I believe it would work with kernels back to 2.6.15,
> but I don't know.

Hi Dan:

I'm Having better luck with udev-056, MUCH faster with 2.6.13 kernel
than udev-030. Majors and Minors are identical. Permissions are
derived from the Original udev permissions and likely the original 
LFS permissions. 

Is it difficult to get the original LFS permissions for various releases
easily? For now I'll just use our existing LFS permissions from way
back in 6.1 (or perhaps even earlier). I tried browsing the src and
using wiki.linuxfromscratch.org but didn't easily find it.

-piet

> 
> --
> Dan
-- 
Piet Delaney
BlueLane Teck
W: (408) 200-5256; piet@bluelane.com
H: (408) 243-8872; piet@piet.net



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-08-04 23:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  7:56 udev on Fedore 5 - Gentoo script not very helpfull in LFS Piet Delaney
2006-08-04 15:12 ` Dan Nicholson
2006-08-04 16:48 ` Greg KH
2006-08-04 23:55 ` Piet Delaney [this message]
2006-08-05  0:13 ` Dan Nicholson
2006-08-05  3:37 ` Piet Delaney
2006-08-05 19:22 ` Dan Nicholson

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=1154735759.8839.102.camel@piet2.bluelane.com \
    --to=piet@bluelane.com \
    --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).