From: Matthew Percival <matthew@capgo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug only coldplugs...
Date: Tue, 04 Apr 2006 02:51:20 +0000 [thread overview]
Message-ID: <1144119080.8872.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1143760894.8931.14.camel@localhost.localdomain>
G'Day,
With the help of an off-the-list reply from Dan Nicholson, I have been
able to get udev going. I have put the contents of his reply at the end
of this message, so should anyone else have the same problem as I did,
and they search this list, they can get a solution.
I am just having a small issue now, in regard to the rules files. For
whatever reason, it seems as if the rules files are ignored: I took the
base Debian files, removed things that I did not need, changed the
permissions, added some symlinks, and set it up to mount the USB flash
memory sticks (which was the original purpose of my question). The
trouble is, none of my changes are being seen in the system, even after
a reboot; indeed, I found that completely removing /etc/udev/rules.d/
has no effect on what I see in /dev/! Each file ends in .rules, and it
readable to all.
Just as an aside, the way I understand things is that udev works out
what the system has available, and uses the rules to work out how to
present them to the user (in very simple terms), but can I write rules
to say `yeah, I have this, but I do not use it, so just ignore it'?
-- Matthew
On Mon, 2006-04-03 at 16:06 -0700, Dan Nicholson wrote:
> Hi Matthew,
>
> I saw your post on linux-hotplug-devel about setting up udev on a
> homebrewed system. I'm not subscribe there, so I apologize for
> sending this off-list.
>
> Anyway, my system uses the Linux From Scratch recipe which is pretty
> minimal for a base. There are people tackling the newer udev issue
> right now. This is not an advertisement for that project, but just an
> offering of one possible solution.
>
> There are two books you might be interested in. The first is the
> standard native build. Here's the one using newer udev and kernel:
>
> http://www.linuxfromscratch.org/lfs/view/udev_update/
>
> The other one is cross-compiled and handles a few arches. udev
> shouldn't matter much on the arch, I don't think, so you could pick
> any of them.
>
> http://www.linuxfromscratch.org/lfs/view/cross-lfs/
>
> Both are udev only, no hotplug. The important parts are the udev
> build (obviously), the udev rules and the bootscripts. The
> implementations are slightly different for stupid reasons that aren't
> worth getting into.
>
> Since I'm more familiar with the native build, here are the relevant
> sections from that book.
>
> Udev rules (these are much simpler than any you will find at a distro,
> although I make no promises that they will recognize all the devices
> for your system):
>
> http://downloads.linuxfromscratch.org/udev-config-6.rules
>
> Bootscripts (The important one is in init.d/udev; beware that another
> set of bootscripts may come very shortly as people experiment with the
> udevtrigger program in newer udev. You rightly noticed that udevstart
> is not installed. This is because it's use is discouraged. The udev
> bootscript is one implementation to manually populate /dev at
> coldplug.)
>
> http://www.linuxfromscratch.org/~dj/bootscripts/lfs-bootscripts-udev_update-20060402.tar.bz2
>
> The udev build:
>
> http://www.linuxfromscratch.org/lfs/view/udev_update/chapter06/udev.html
>
> A description of the whole situation:
>
> http://www.linuxfromscratch.org/lfs/view/udev_update/chapter07/udev.html
>
> Good luck.
>
> --
> Dan
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-04-04 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 23:21 Hotplug only coldplugs Matthew Percival
2006-03-31 17:16 ` Greg KH
2006-04-03 6:16 ` Matthew Percival
2006-04-04 2:51 ` Matthew Percival [this message]
2006-04-06 6:33 ` Matthew Percival
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=1144119080.8872.17.camel@localhost.localdomain \
--to=matthew@capgo.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).