SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm using slackware-10.2 with kernel 2.4.32 in combination with serveral removable devices: mp3-player, camera, external hard-disk,...
hotplug assigns these devices to /dev/sd[bcd]? according to the sequence of connection (which is variable, actually). Therefore it is not possible to define "fixed" mount points in /etc/fstab.
As far as I understand, with kernel 2.6 this problem is handled by udev.
Do you know a similar solution for kernel 2.4?
At the moment, I'm using hotplug as a black-box; can I configure hotplug to do that job for the above mentioned devices?
Or you can setup /etc/fstab with generic mount point names, and then either manually mount them or use the "System > Storage Media > Removable Device (sdx1)" choices from the KDE desktop. These are two mount points:
@all: basically, my system is running - I just want to optimize it....
@drkstr:
> What are you experiencing when you try to use udev?
$ head -n 9 /usr/doc/udev-064/README | tail -1
- You must be running a 2.6 version of the Linux kernel.
--> I didn't try....
@Chinaman:
- yes - this is an option - but still I would have to "think about" wich /dev/s?? I have to use, when I connect any devices.
Actually, I'm looking for something like
/dev/camera /mnt/camera vfat noauto,users,.....
where /dev/camera gets linked to /dev/s?? by any (hotplug?) automatism.
You don't have to think about anything if you're running KDE, just make yourself 4 mount points, plug in the device, and then use what I told you before. You click on the icon and it mounts.
Of course, udev is supposed to assign the same mount point to devices if you write udev rules properly. But udev is still a buggy issue, and only certain versions work with certain kernels. See the ChangeLog.txt of Slackware -current for more info.
You're only going to get the functionality you want with udev.
At the present time, that's going to require a lot of work on
your part, probably 'hit and miss' at that. Did you read?
Code:
mingdao@silas:~$ less /usr/doc/udev-071/README
udev - userspace device management
For more information see the files in the docs/ directory.
Important Note:
Integrating udev in the system is a whole lot of work, has complex dependencies
and differs a lot from distro to distro. All reasonable distros use udev these
days, the major ones make it mandatory and the system will not work without it.
The upstream udev project does not support or recomend to replace a distro's udev
installation with the upstream version. The installation of a unmodified upstream
version may render your system unusable! There is no "default" setup or a set
of "default" rules provided by the upstream udev version.
<snip>
And since I had enough trouble with udev just running,
without writing any udev rules, I'm not even sure if what you
are saying is possible. I think udev still uses device names,
but translates those into specific mount points.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.