From: Alex Smith <alex@alex-smith.me.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev on real Linux from scratch
Date: Sun, 06 May 2007 19:23:55 +0000 [thread overview]
Message-ID: <463E2B4B.2010302@alex-smith.me.uk> (raw)
In-Reply-To: <x63b2av12d@gzp>
Gabor Z. Papp wrote:
> * Alex Smith <alex@alex-smith.me.uk>:
>
> | IMO it would be wiser to use udevtrigger and udevsettle here rather
> | than udevstart because AFAIK udevstart is deprecated and will be
> | removed soon.
>
> Thanks, replaced, works fine, except I'm getting 2 errors that was
> hidden before the change. udevd complaining about these lines stolen
> from slackware config:
>
> ACTION="add", DEVPATH="/devices/*", ENV{PHYSDEVBUS}="?*", WAIT_FOR_SYSFS="bus"
>
> # permissions for IDE CD devices (without symbolic link creation)
> BUS="ide", KERNEL="*[!0-9]", ENV{PHYSDEVDRIVER}="ide-cdrom", NAME="%k", GROUP="disk", MODE="0660"
>
> # permissions for IDE floppy devices
> BUS="ide", KERNEL="*[!0-9]", ENV{PHYSDEVDRIVER}="ide-floppy*", NAME="%k", GROUP="disk", MODE="0660"
>
> Saying something like PHYSDEV* deprecated and will be removed?
Yes, you'll need to replace these sometime. I'm not sure what you should
replace them with though.
>
> | that udevd needs and does not create. This is what I do on
> | Frugalware:
>
> [...]
>
> Thank you Alex.
>
> Two questions left, mounting tmpfs on /dev is ok, or should I use ramdisk?
> No need to set (limit) the size of /dev?
mount -n -t ramfs none /dev
I use ramfs ^^
>
> Another error I'm getting from udevd:
>
> "the kernel does not support inotify, udevd can't monitor configuration file changes"
Just rebuild your kernel with inotify support - it's under the File
systems menu in menuconfig IIRC.
--
Alex Smith
Frugalware Linux developer - http://www.frugalware.org
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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:[~2007-05-06 19:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 7:55 udev on real Linux from scratch Gabor Z. Papp
2007-05-06 8:34 ` Alex Smith
2007-05-06 11:57 ` Bryan Kadzban
2007-05-06 15:39 ` Gabor Z. Papp
2007-05-06 19:23 ` Alex Smith [this message]
2007-05-07 1:48 ` Bryan Kadzban
2007-05-07 7:34 ` Gabor Z. Papp
2007-05-07 8:11 ` Alex Smith
2007-05-07 12:26 ` Gabor Z. Papp
2007-05-07 12:39 ` Gabor Z. Papp
2007-05-07 15:00 ` Dan Nicholson
2007-05-07 16:30 ` Leisner, Martin
2007-05-07 17:28 ` Alex Smith
2007-06-03 19:22 ` DervishD
2007-06-04 6:47 ` Alexander E. Patrakov
2007-06-04 8:21 ` DervishD
2007-06-05 18:54 ` Matthew Burgess
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=463E2B4B.2010302@alex-smith.me.uk \
--to=alex@alex-smith.me.uk \
--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).