linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vassilis Virvilis <vasvir@iit.demokritos.gr>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev vs. devfs
Date: Thu, 16 Jun 2005 17:10:11 +0000	[thread overview]
Message-ID: <42B1B273.30302@iit.demokritos.gr> (raw)
In-Reply-To: <BAY19-F8BE196D4CCF42A9E246A6B9F50@phx.gbl>

Pelle Svensson wrote:
> 
> Hi,
> 
[snip]
> Can't somebody tell me what I need to get udev up and running from scratch.
> 
> I'm building a ARM system with 2.6 kernel from scratch so I only need the
> most basic stuff to get a 'dev' list.
> 

Halo,

I don't if it will help you but it mostly works for my setup so you may give it a try.

Assuming you are booting correctly and
0) you have the latest kernel >= 2.6.11.rc4 and the latest udev (git versions)
1) you have mount your root partition
2) you have mount /proc /sys

in your init
1) run start_udev (it is distributed with udev sources)
2) later run coldplug
---- coldplug -----
#!/bin/sh

BUSSES="pci usb";

for bus in $BUSSES; do
   for DEV in /sys/bus/$bus/devices/*; do
      echo -n "Checking bus $bus device $DEV...";
      if [ -L "$DEV" -a -f $DEV/modalias ]; then
         echo "modprobing";
         modprobe `cat $DEV/modalias`;
      else
         echo "no";
      fi
   done;
done;
---------------

and of course have a hotplug handy in /sbin/hotplug
----------- /sbin/hotplug ------------
#!/bin/sh

#echo "*** hotplug 'subsystem=$1' 'MODALIAS=$MODALIAS' 'DEVPATH=$DEVPATH' ***" > /dev/kmsg;
if [ -n "$MODALIAS" -a ! -L /sys/$DEVPATH/driver ]; then
    echo "*** hotplug 'subsystem=$1' 'MODALIAS=$MODALIAS' 'DEVPATH=$DEVPATH' ***" > /dev/kmsg;
    modprobe -v $MODALIAS > /dev/kmsg;
fi

if [ -n "$DEVPATH" -a -d "/sys" ]; then
    #echo "udevsend $1 -------------" > /dev/kmsg;
    /sbin/udevsend $1;
fi

if everything goes out well you can comment out the /dev/kmesg redirection.
Oh and in my /dev I have already /dev/kmsg /dev/null /dev/console.

I am sure somebody will popup with a better script/procedure or something
but anyway here are my 2dr.

.bill


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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

  reply	other threads:[~2005-06-16 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 15:07 udev vs. devfs Pelle Svensson
2005-06-16 17:10 ` Vassilis Virvilis [this message]
2005-06-16 18:37 ` Greg KH
2005-06-16 19:29 ` David Brownell
2005-06-17 12:42 ` Pelle Svensson
2005-06-17 12:58 ` Kay Sievers
2005-06-17 13:15 ` Pelle Svensson
2005-06-17 16:05 ` Greg KH
2005-06-17 19:21 ` David Brownell
2005-06-17 19:26 ` David Brownell
2005-06-20 12:52 ` Pelle Svensson
2005-06-23 16:59 ` Vassilis Virvilis
2005-06-28 11:24 ` Vassilis Virvilis

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=42B1B273.30302@iit.demokritos.gr \
    --to=vasvir@iit.demokritos.gr \
    --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).