On Sat, Jul 02, 2005 at 11:09:06AM +0200, Eric Valette wrote:
> Willy Tarreau wrote:
> > Well, although I've never used udev because I've been using sort of an
> > equivalent called "preinit" for 4 years now, I don't totally agree with
> > you about the firmware upgrade : when you package your systems to allow
> > the customer to perform "firmware" upgrades, your image is already very
> > specific to a hardware model, and I don't see why you would need to
> > create /dev entries independantly from the kernel or rootfs.
>
> I beg to disagree. More and more devices have generic connectivity plug
> (USB, 1394, ...) and you may update your firmware because you support a
> new device connected to this plug that is not a generic device (specific
> driver needed) but you may also have provisionned generic devices
> drivers for the plug and want devices created only when device is
> plugged (usb mass storage comes in mind). If I make a static /dev
> provision for a USB disk how many useless partition will I need to
> create,
They cost almost nothing, and in all cases, far less than the required code
to autodetect them. You just need to create /dev/sda{,0-15} for an USB disk,
and you may need to to this for sdb and/or sdc if you plan to support multiple
USB storage devices simultaneously plugged. And if your embedded system already
carries SCSI disks (which is very rare, except for example external arrays),
then you're in trouble already. Maybe sysfs can help you, I don't know.
> and how will I mount the correct number of partition without
> hotplug like feature and analysing by hand the partition table?
"analysing by hand" is a bit excessive. I don't think the difference between
for part in /dev/sda*; do
mkdir -p /mnt/${part#/dev/}
mount $part /mnt/${part#/dev/}
done
and :
while read maj min blo part; do
case $part in sda[1-9]*)
mkdir -p /mnt/$part
mount /dev/$part /mnt/$part
esac
done </proc/partitions
is so important.
Now I agree that devfs might have made it easier to find the sd* devices
associated to the usb-storage device, but it is totally independant on
your problem of creating lots of /dev entries in advance.
Regards,
Willy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|