Alexander E. Patrakov wrote these words on 12/10/05 02:15 CST: > Sorry. My fault. That's because I restarted the HAL daemon many times > investigating how to add the proper "iocharset" option to the > autocreated fstab entries.
Well, I would like to continue this thread until it is determined that we either will or will not use a patched util-linux. As far as the HAL daemon and the managed keyword, I forgot to mention that there is one bit of behavior that is probably wrong in the BLFS setup of not using the managed keyword in the auto-fstab entries. I've noticed that for *non-removable* devices (a floppy and a cd-recorder/player on my system) when the HAL daemon starts for the first time, appropriate entries are created in the fstab file and the corresponding mount points in /media are created. But the first time only. After this, even if the HAL daemon is shut down and restarted, the fstab file and mount points remain unchanged. My understanding in reading the HAL documentation is that when the daemon is started, the fstab and mount points are updated, and when the daemon is stopped, the fstab entries and mount points should be removed. But I don't see this. I only see the fstab entries and mount points created the first time the daemon starts and never again. The entries/mount points are *not* removed, nor are more created when the daemon is restarted. I don't think this is proper behavior and *do* attribute this to not having the managed keyword in the fstab entry. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 02:41:00 up 76 days, 12:05, 3 users, load average: 0.00, 0.02, 0.28 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
