On 16 May 2006, at 12:30, Neil Bothwick wrote:
...
I thought that under udev, the kernel was supposed to be quite clever
about recognising devices. Do I need to emerge coldplug, or is there
anything else I can do to help things along?
If I boot from a LiveCD or Knoppix these are always very good about
finding all the devices in the system and making a mount point for
them - are there any utilities for my installed Gentoo system that
will do similar.
Udev should recognise the drive and create a device node...
Having spent the last hour tinkering, it seems to do so only after
I've emerged & started coldplug. Is there anything else I should be
doing to get udev working, or should it "just work" with current
kernels.
... but creating mount points is not udev's job.
Yes, I'm not quite so fussed about that, as long as I can find the
drive in /dev/sda
What I'm having problems with right now is allowing users to write to
the external drive.
Is this something as simple as `chmod 777 /mnt/sda1 && chgrp users /
mnt/sda1`?
I'm afraid I'm more used to using Linux on servers, and I don't
recall encountering this issue.
I know I can change permissions in /etc/fstab, but I don't know yet
whether I want to add this device to there (even with the "noauto"
option) as it won't always be connected.
You need a device manager for that. If
you use KDE, especially 3.5, it should handle it for you, provided you
have the hal USE flag set. With other WMs, use ivman.
Thanks! I'll take a look at ivman - I want to get KDE installed on
this machine eventually, but I really want something that'll also
work when I'm not booting to X. Are there any downsides to using
`ivman` with USE=-hal KDE? I guess drives mounted by ivman might not
appear on KDE desktops, so I might be better emerging both ivman
_and_ USE=hal KDE but putting them in different runlevels?
...I use this
rule in /etc/udev/rules.d/10-udev.rules, but you'll need to change the
model_id value, unless you have the same enclosure as me.
BUS=="ieee1394", KERNEL=="sd?1", SYSFS{model_id}=="0x008034",
NAME:="fwdisk", SYMLINK="%k"
Running coldplug seems to have placed the drive at /dev/sda, which
I'm perfectly happy with.
Thanks for your time,
Stroller.
--
[email protected] mailing list
