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: Sat, 05 Aug 2006 03:37:16 +0000	[thread overview]
Message-ID: <1154749036.8839.122.camel@piet2.bluelane.com> (raw)
In-Reply-To: <1154678172.8839.84.camel@piet2.bluelane.com>

On Fri, 2006-08-04 at 17:13 -0700, Dan Nicholson wrote:

Hi Dan:

> On 8/4/06, Piet Delaney <piet@bluelane.com> wrote:
> > On Fri, 2006-08-04 at 08:12 -0700, Dan Nicholson wrote:
> > >
> > > 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
> >
> > 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.
> 
> By permissions I assume you mean the rules files.

Well..., yes. It seems between 030 and 056 the permissions directory
support was dropped yet lots of examples existed and it appears to
parse it in the log so it's hidden in the noise that the changing
of permissions is now done in the rules files. Even the udev 
Change log doesn't indicate this.


>                                                  The udev rules have
> jumped around a bit. They've only come under version control in the
> past few months. Here's the rules and bootscripts from 6.1.1, which
> used udev-056 and linux-2.6.12.
> 
> http://downloads.linuxfromscratch.org/udev-config-4.rules
> http://downloads.linuxfromscratch.org/lfs-bootscripts-3.2.1.tar.bz2

Thanks. I've been using the udev-config-4.rules and it bring us closer
to our previous permissions. It seems there was yet another undocumented
change. The config files:

	# default_mode - set the default mode for all nodes that have no
	#                explicit match in the permissions file
	default_mode="0600"

is no longer supported. The Change log only indicates it's being
supported way back when udev started to exist. So many permissions
with your LFS udev-config-4.rules still leave difference from our
previous environment. Many appear to be a consistent difference between
default permissions. Many of our files have permissions 600 and are
now coming up 660. I think this is likely because default_mode="0600"
is now ignored in the config file.

Might be best to try two versions of udev-config-4.rules, one with the
way they exist in the 6.1.1 release and another that beings us closer
to the permissions we are using from 6.1 (or earlier).

Any thoughts on that. You may be in a great position to know which
environment be best. Using the stock udev-config-4.rules from 6.1.1
would likely make future migration to 6.2 easier. Modifying the
udev-config-4.rules to give the same permissions we use now with
6.1 would likely minimize risk of our appliance behavior changing.

I haven't seen anything in your /lfs-bootscripts-3.2.1.tar that
changes files modes in /dev.

-piet
	
> 
> I think you can also safely update to udev-071 with the same setup.
> Read the NEWS and README in udev. It's noted when things become
> incompatible such as kernel version needed, or a tool going away, like
> udevstart.
> 
> --
> 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-05  3:37 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
2006-08-05  0:13 ` Dan Nicholson
2006-08-05  3:37 ` Piet Delaney [this message]
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=1154749036.8839.122.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).