Iinitial automounting by lenny/kde very slow after each X/kde-session start.
Hello debian-kde list,
This problem occurs since a few months with KDE, but NOT with GNOME.
The system is debian/lenny on a dual core Intel PC where we normally use KDE.
Inserting a usbstick for the FIRST TIME after logging in to KDE via kdm or gdm
results
in a delay of about TEN minutes before the kde-mount-screen appears!
Then everything works OK. All next inserts work normal.
The devices are always directly created upon insertion (here /dev/sdb1),
and pmount can be used directly. There never is any warning or error to be
found.
Please find below some debugging information, where the most informative is
that the
10 minute delay seems to start AFTER a "hal-probe-storage", see hald logging
info below.
Can anyone point me in a direction? I would be most grateful.
I already tried the debian-user list, but to no avail.
Here OUTPUT from hald from /var/log/daemon.log:
===
.
Aug 19 13:13:44 wingtip84 hald[5386]: 13:13:44.224 [I] blockdev.c:1622:
hald-probe-storage --only-check-for-media returned 0 (exit_type=0)
Aug 19 13:22:39 wingtip84 hald[5386]: 13:22:39.186 [I] hald_dbus.c:5127: OK for
method 'Mount' with signature 'ssas' on interface
'org.freedesktop.Hal.Device.Volume' for
UDI '/org/freedesktop/Hal/devices/volume_uuid_76DE_0888' and execpath
'hal-storage-mount'
.
==
Note the 10 minute delay between the hald-probe-storage and the "OK for method
'Mount'.
Here output from lshal --monitor
Start monitoring devicelist:
-
10:35:40.519: usb_device_781_7108_00046315 added
10:35:40.552: usb_device_781_7108_00046315_usbraw added
10:35:40.573: usb_device_781_7108_00046315_if0 added
10:35:40.577: usb_device_781_7108_00046315_if0_scsi_host added
10:35:45.552: usb_device_781_7108_00046315_if0_scsi_host_0 added
10:35:45.553:
usb_device_781_7108_00046315_if0_scsi_host_0_scsi_device_lun0 added
10:35:45.566:
usb_device_781_7108_00046315_if0_scsi_host_0_scsi_device_lun0_scsi_generic
added
10:35:46.947: volume_uuid_76DE_0888 added
10:35:47.140: storage_serial_SanDisk_Cruzer_Titanium_00046315_0_0
added
10:35:47.140: storage_serial_SanDisk_Cruzer_Titanium_00046315_0_0
property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'}
(new)
+++ here the 10 minute wait.
10:47:43.754: volume_uuid_76DE_0888 property volume.mount_point = '/media/disk'
10:47:43.755: volume_uuid_76DE_0888 property volume.is_mounted = true
Here OUTPUT from hald in nodeamon and verbose mode (different attempt):
===
! full path is '/usr/lib/hal/hald-probe-volume', program_dir is '/usr/lib/hal'
pid 5476: rc=0 signaled=0: /usr/lib/hal/hald-probe-volume
Run started hald-probe-storage (1) (0)
! full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal'
woohoo
pid 5485: rc=0 signaled=0: /usr/lib/hal/hald-probe-storage
+++ here the 10 minute wait.
Run started hal-storage-mount (0) (1)
! full path is '/usr/lib/hal/hal-storage-mount', program_dir is '/usr/lib/hal'
5657: XYA attempting to get lock on /media/.hal-mtab-lock
5657: XYA got lock on /media/.hal-mtab-lock
device = /dev/sdb1
invoked by uid = 502
invoked by system bus connection = :1.36
label '' uuid '76DE-0888'
Looking at /etc/fstab entry '/dev/sda7'
/etc/fstab: device /dev/sda7 -> /dev/sda7
===
Can anyone point me in the right direction?
Again note that there NEVER is any warning or error to be found.
How could the 10 minute delay be triggered?
Is it an udev-rule problem?
(at some point I had package dmsetup (devicemapper setup) installed and after
fiddling with its udev-rules it seemed to work (once).
Now dmsetup is not installed anymore)
Thanks in advance.
Sietse Achterop
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Kde devices's automounting on desktop
Null Pointer wrote: > On Friday 28 October 2005 08:24, Derek Broughton wrote: > >> Martin Steigerwald wrote: >> > KDE 3.4 ... does not automount, but it puts an icon (or >> > more when there are several partitions on the medium) that >> > you can click to mount it. >> >> I don't think that's _quite_ right. aiui, if you create the >> correct hal .fdi files, you can specify that the device be >> automounted. Gnome seems to have better support for that >> end of things. > > With only some parts of 3.4 installed, I restarted KDE and got > the 3.4 login screen. I logged in, opened Konq, clicked on > storage media, and then plugged in a SanDisk flash drive. Its > icon immediately appeared, correctly labeled. When I clicked > on the drive's icon, it mounted and Konq correctly displayed > the contents. Files opened properly, etc. > > The context menu for the icon lists 'mount' and 'safely > remove.' It does not have 'unmount' as an option -- even when > the device is mounted. The icon properly indicates if the > device is mounted or not. "Safely remove' seems to have > replaced 'unmount' for removeable media. > > It seems to work just as Martin indicated -- and was the > primary reason I chose to get the 3.4 from Sid. Exactly - why I said not "quite" right. That's the way everything works by default, and is definitely good enough for me. > While it may be possible to script things so that the device is > mounted automatically when it is plugged in, I see that as an > unnecessary risk for removeable media, at least for my current > applications. I prefer it to mount when I click on the icon, > so I'm happy with what I am finding in 3 he;. It's not a matter of scripting, but of setting attributes for specific devices & media. You could, for instance (I think) make your CD player only automount CDs with specific volume labels - way too much work to do by hand, but some helper program might take advantage of it. For instance, your audio player might have a record of all the CDs you've played, and add their labels into hal's database so that whenever you reinsert a CD from your audio collection it is automatically played. I don't see automounting a USB memory stick to be an unnecessary risk, and I've seen enough users demanding it and then writing their own .fdi's so that their sticks do automount. It's "unmounting" that's the problem :-) -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kde devices's automounting on desktop
On Friday 28 October 2005 08:24, Derek Broughton wrote: > Martin Steigerwald wrote: > > KDE 3.4 ... does not automount, but it puts an icon (or > > more when there are several partitions on the medium) that > > you can click to mount it. > > I don't think that's _quite_ right. aiui, if you create the > correct hal .fdi files, you can specify that the device be > automounted. Gnome seems to have better support for that > end of things. -- > derek As I write this I am upgrading a notebook to KDE 3.4. Before the upgrade, the notebook had a new net install of Debian/Testing -- using the Sarge net installer, RC3 -- not exactly up to date, but it worked with a few kinks. With only some parts of 3.4 installed, I restarted KDE and got the 3.4 login screen. I logged in, opened Konq, clicked on storage media, and then plugged in a SanDisk flash drive. Its icon immediately appeared, correctly labeled. When I clicked on the drive's icon, it mounted and Konq correctly displayed the contents. Files opened properly, etc. The context menu for the icon lists 'mount' and 'safely remove.' It does not have 'unmount' as an option -- even when the device is mounted. The icon properly indicates if the device is mounted or not. "Safely remove' seems to have replaced 'unmount' for removeable media. It seems to work just as Martin indicated -- and was the primary reason I chose to get the 3.4 from Sid. While it may be possible to script things so that the device is mounted automatically when it is plugged in, I see that as an unnecessary risk for removeable media, at least for my current applications. I prefer it to mount when I click on the icon, so I'm happy with what I am finding in 3.4. N.P. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kde devices's automounting on desktop
Martin Steigerwald wrote: > KDE 3.4 ... does not automount, but it puts an icon (or more when > there are several partitions on the medium) that you can click to mount > it. I don't think that's _quite_ right. aiui, if you create the correct hal .fdi files, you can specify that the device be automounted. Gnome seems to have better support for that end of things. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kde devices's automounting on desktop
Am Samstag 22 Oktober 2005 13:13 schrieb João Silva: > Hi, > does anybody knows if exists any aplication > that automatically mounts devices on desktop > like gnome do? Hello João, KDE 3.4 has inbuilt functionality for this using the media:// kio slave, hal, udev and D-BUS. Either just use the media:// kio slave or configure the desktop which device symbols it should display (context menu from desktop, "Behaviour/Device symbols" or something like that, have it in german here). It does not automount, but it puts an icon (or more when there are several partitions on the medium) that you can click to mount it. KDE 3.5 adds to that that it pops up a window when you insert a medium. For KDE 3.3 you can use usbmount and hook in a script that puts an icon on the desktop. I have made one that I can send to you. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
Re: Kde devices's automounting on desktop
Well, thanks for your fast awsers. I had configured autofs. Maybe i will make some work on it for debian. My question was, the automounting without the locking of the device. I already done this with autofs. I know that kunbutu's kde already do that, with an adaption of gnomevfs.On 10/23/05, Huston <[EMAIL PROTECTED]> wrote: I know if you go to the control center, desktop and behavior there is a tabfor device icons, and I can make my hard drives and network drives show upmounted on the desktop.- Original Message - From: "Theo Schmidt" <[EMAIL PROTECTED]>To: "João Silva" <[EMAIL PROTECTED]>Cc: < debian-kde@lists.debian.org>Sent: Sunday, October 23, 2005 3:51 AMSubject: Re: Kde devices's automounting on desktop> João Silva schrieb:>> does anybody knows if exists any aplication >> that automatically mounts devices on desktop>> like gnome do?>> There was extensive discussion on this list about this; you may find it in> the archives. The conclusion was yes, KDE can do this, as you will find > out if you try out Kubuntu and plug in a USB storage device. As for> getting Debian to do this: there was no real consensus what is exactly> needed and what isn't: there seem to be several competing systems and no > agreement on this list which is best.>> Theo Schmidt>>> --> To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact> [EMAIL PROTECTED]>>>--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Cumprimentos,João Carlos Galaio da Silva
Re: Kde devices's automounting on desktop
I know if you go to the control center, desktop and behavior there is a tab for device icons, and I can make my hard drives and network drives show up mounted on the desktop. - Original Message - From: "Theo Schmidt" <[EMAIL PROTECTED]> To: "João Silva" <[EMAIL PROTECTED]> Cc: Sent: Sunday, October 23, 2005 3:51 AM Subject: Re: Kde devices's automounting on desktop João Silva schrieb: does anybody knows if exists any aplication that automatically mounts devices on desktop like gnome do? There was extensive discussion on this list about this; you may find it in the archives. The conclusion was yes, KDE can do this, as you will find out if you try out Kubuntu and plug in a USB storage device. As for getting Debian to do this: there was no real consensus what is exactly needed and what isn't: there seem to be several competing systems and no agreement on this list which is best. Theo Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kde devices's automounting on desktop
João Silva schrieb: does anybody knows if exists any aplication that automatically mounts devices on desktop like gnome do? There was extensive discussion on this list about this; you may find it in the archives. The conclusion was yes, KDE can do this, as you will find out if you try out Kubuntu and plug in a USB storage device. As for getting Debian to do this: there was no real consensus what is exactly needed and what isn't: there seem to be several competing systems and no agreement on this list which is best. Theo Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kde devices's automounting on desktop
Le Samedi 22 Octobre 2005 13:13, João Silva a écrit : > Hi, > does anybody knows if exists any aplication > that automatically mounts devices on desktop > like gnome do? > > Greetings, > João Silva > > -- > Cumprimentos, > João Carlos Galaio da Silva Add device icons on your desktop, or add the applet in kicker bar. It will not mount it automatically, but it shows the icons when you plug the device (if you use udev+hal), and when you click on this icon, to open a window, it mounts it for you (you need pmount for that) In kde 3.5, kde will ask you what you want to do with the device (play a dvd, play cd audio, write data, mount the device, or so ...) I guees there are other solutions, but it is the one I choose since it's well integrated in kde, and not too intrusive/heavy. ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kde devices's automounting on desktop
Hi, does anybody knows if exists any aplication that automatically mounts devices on desktop like gnome do? Greetings, João Silva-- Cumprimentos,João Carlos Galaio da Silva
Automounting....
Hi! KDE mounts removable devices using pmount. Unfortunately, I can't find an option to disable mounting devices without the "sync" option. Is it possible to specify this somewhere? With this option enabled write access is too slow and may damage flash devices... regards, Jörg -- Hi! I'm a .signature virus! Copy me into your signature to help me spread!.-. PGP Key: send mail with subject 'SEND PGP-KEY' PGP Key-ID: FD 4E 21 1Doo| PGP Fingerprint: 388A872AFC5649D3 BCEC65778BE0C605 _ // /`'\ I am Ohm of Borg. Resistance is voltage divided by current. \X/ (\_;/) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
Theo Schmidt wrote: > Derek Broughton schrieb: >> Bellegarde Cedric wrote: >>> Roman Kreisel wrote: > ... >>>>And no, afaik, hotplug is _not_ obsolete. > ... >>>hotplug is obsolete, udev is now the good way to do (and not hal): > > Oh great, even the experts disagree... Oooh, I hope he's not talking about me... :-) > I gleaned my clip on "obsolete > hotplug" from an article about SuSE 10.0 in LinuxUser (German magazine). > > ... >>>udev, in mandriva(2006), now do hotplug job. >>> >> >> I can't see how. Hotplug inserts the modules required by a device - I >> see >> nothing in udev that's going to do that. hal is a _very_ good way to >> enable automounting (amongst other things) - it doesn't mount anything, >> but then neither does udev. > > hal seems to depend on udev, but I still havn't got a clue what all > these components *really* do. I think we're all just fumbling in the dark these days, as there isn't enough documentation around. I have a pretty good clue about hotplug - and the simplest explanation is that it notes the insertion of hotpluggable hardware (generally PC-card and USB) and installs the appropriate modules to support it (running custom scripts if necessary). I've got less knowledge of udev, but it builds the /dev database and makes all the necessary nodes with appropriate permissions and synonyms. I don't have a clue what HAL & DBUS do, but if they aren't integral to both of these yet, they will be. They are integral to pmount - which is the (an?) other part of the story. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
On Monday 26 September 2005 19:11, Bellegarde Cedric wrote: > On Monday 26 September 2005 10:30, Roman Kreisel wrote: > > And no, afaik, hotplug is _not_ obsolete. > > hotplug is obsolete, udev is now the good way to do(and not hal): > >Thanks to the replacement of hotplug with udev functions, > >all machines now boot faster. > > udev, in mandriva(2006), now do hotplug job. What?! udev depends on hotplug! It depends on it to create the device nodes! It won't work without it! Could we get en udev/hotplug/hal maintainer in to settle this please. Anders -- - Debian/Unstable - KDE 3.4.2 - KMail 1.8.2 - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
Derek Broughton schrieb: Bellegarde Cedric wrote: Roman Kreisel wrote: ... And no, afaik, hotplug is _not_ obsolete. ... hotplug is obsolete, udev is now the good way to do (and not hal): Oh great, even the experts disagree... I gleaned my clip on "obsolete hotplug" from an article about SuSE 10.0 in LinuxUser (German magazine). ... udev, in mandriva(2006), now do hotplug job. I can't see how. Hotplug inserts the modules required by a device - I see nothing in udev that's going to do that. hal is a _very_ good way to enable automounting (amongst other things) - it doesn't mount anything, but then neither does udev. hal seems to depend on udev, but I still havn't got a clue what all these components *really* do. Theo Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
Bellegarde Cedric wrote: > On Monday 26 September 2005 10:30, Roman Kreisel wrote: >> And no, afaik, hotplug is _not_ obsolete. > > hotplug is obsolete, udev is now the good way to do(and not hal): > >>Thanks to the replacement of hotplug with udev functions, >>all machines now boot faster. > > udev, in mandriva(2006), now do hotplug job. > I can't see how. Hotplug inserts the modules required by a device - I see nothing in udev that's going to do that. hal is a _very_ good way to enable automounting (amongst other things) - it doesn't mount anything, but then neither does udev. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
On Monday 26 September 2005 19:11, Bellegarde Cedric wrote: > On Monday 26 September 2005 10:30, Roman Kreisel wrote: > > And no, afaik, hotplug is _not_ obsolete. > > hotplug is obsolete, udev is now the good way to do(and not hal): http://packages.debian.org/unstable/admin/udev : " It responds to /sbin/hotplug device events ..." So apparently hotplug is not obsolete (yet) ? Serge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automounting experiments
On Monday 26 September 2005 10:30, Roman Kreisel wrote: > And no, afaik, hotplug is _not_ obsolete. hotplug is obsolete, udev is now the good way to do(and not hal): >Thanks to the replacement of hotplug with udev functions, >all machines now boot faster. udev, in mandriva(2006), now do hotplug job. Cédric
Re: Automounting experiments
On Monday 26 September 2005 10:43, EmIscA wrote: > Could you post somewhere that scripts? > Thanks Here you are: http://www2.fht-esslingen.de/~rokrit01/files/automount-scripts/ Short Installation-Howto: - Copy those scripts to a location in your $PATH, preferably /usr/local/bin and make them executable - Run the mediahandling.py (as non-root, inside X11), read the error-message (which will likely appear) and solve the dependencies. You'll have to install several python-*-packages. Additionaly you need HAL and pmount installed and working. - Once everything works and mediahandly.py doesn't stop with an error, insert media and watch it beeing mounted. Remember, that it does NOT handle umounting! Therefore you might want to use usbumount.py - Fine-tuning: - Put a link to mediahandling.py in your $KDEDIR/Autostart - edit $HOME/.injectrc Regards Roman -- Why do geeks get Halloween and Christmas confused? Because 31 oct == 25 dec -- seen on the net pgpxU6HWnl4iD.pgp Description: PGP signature
Re: Automounting experiments
Could you post somewhere that scripts?
Thanks
Roman Kreisel ha scritto:
On Monday 26 September 2005 08:07, Theo Schmidt wrote:
John O'Hagan schrieb:
There seem to be (say) three generations of USB mounting systems:
1) The good old way: USB partitions showed up in /proc somewhere, e.g.
/proc/partitions and one had to write an entry line in /etc/fstab and
then mount manually as root or create a desktop icon which mounts and
opens the device in konqueror. Problem: the partition labels change with
different devices, so you need to either do a bit of detective work
occasionally or maintain a whole zoo of /etc/fstab entries. (Completely
manual mounting without going through /etc/fstab often doesn't work
because often the file system type is unknown. In this case the only
thing I have found which will even find the partition is QTparted, a
super partitioning tool which is unfortunately incomplete and buggy and
no longer maintained or even part of Debian, as far as I can tell.)
If you want to have specific devices shown as specific nodes in /dev, you can
use hotplug and define some rules. And no, afaik, hotplug is _not_ obsolete.
2) The semiautomatic way: detective work as above in 1), then use pmount
/dev/sd. Device will show up in /media/sd and even on the
desktop if you have "show devices" activated in KDE. Problem: needs a
modern kernel.
Correct, but to get new features (and unfortunately auto-mounting of
usb-devices is relatively new to most linux-distributions, including debian)
you need to use new software. In that case an up2date kernel. (Although even
2.6.8 from Sarge would suffice)
3) The modern way: device icon appears automatically (unmounted) on
desktop. Clicking mounts it in Konqueror. Right-clicking allows safe
removal. Problem: requires modern kernel and lots of other things. Only
few distributions (e.g. Kunbuntu) seem to have gotten this right,
certainly not Sarge.
You're right. KDE starting from 3.4.0 supports this, but it didn't make it
into sarge. Although it's just your 2) + a nice GUI to handle it. It has some
points i dislike:
a) no automounting, you still need to mount the device. Fine if you're using
only kde-apps, but annoying for those who want to store a file from
OpenOffice, Mozilla or whatever on the USB-Device. They've to open the
directory in Konqueror, first.
b) mountpoints are related to the devicenode, not to the label of the
partition (like gnome-volume-manager and pmount-hal do)
I note that even 3) isn't true automounting, so maybe there is a 4).
Yes there is.
The IMHO optimal solution is to combine hal (for detecting new attached
devices), pmount (for auto-mounting without being root) and a nice
userspace-programm like GVM which starts the right program for the right
medium (xine for VCD, Konqueror for Data-CD, USB-Stick, USB- or
Firewire-Harddrive). Right now, gnome-volume-manager does this job quite
nice. Unfortunately, g-v-m has nautilus hardcoded as filemanager, which makes
it a suboptimal choice for KDE-Users.
I wrote my own scripts (python) which do at least the auto-mounting thing
using pmount-hal. If you're interested, inform me. Although you should know
that i don't continue development of them nor are they really finished. But
they "just work".
Regards
Roman
Re: Automounting experiments
On Monday 26 September 2005 08:07, Theo Schmidt wrote: > John O'Hagan schrieb: > There seem to be (say) three generations of USB mounting systems: > > 1) The good old way: USB partitions showed up in /proc somewhere, e.g. > /proc/partitions and one had to write an entry line in /etc/fstab and > then mount manually as root or create a desktop icon which mounts and > opens the device in konqueror. Problem: the partition labels change with > different devices, so you need to either do a bit of detective work > occasionally or maintain a whole zoo of /etc/fstab entries. (Completely > manual mounting without going through /etc/fstab often doesn't work > because often the file system type is unknown. In this case the only > thing I have found which will even find the partition is QTparted, a > super partitioning tool which is unfortunately incomplete and buggy and > no longer maintained or even part of Debian, as far as I can tell.) If you want to have specific devices shown as specific nodes in /dev, you can use hotplug and define some rules. And no, afaik, hotplug is _not_ obsolete. > 2) The semiautomatic way: detective work as above in 1), then use pmount > /dev/sd. Device will show up in /media/sd and even on the > desktop if you have "show devices" activated in KDE. Problem: needs a > modern kernel. Correct, but to get new features (and unfortunately auto-mounting of usb-devices is relatively new to most linux-distributions, including debian) you need to use new software. In that case an up2date kernel. (Although even 2.6.8 from Sarge would suffice) > 3) The modern way: device icon appears automatically (unmounted) on > desktop. Clicking mounts it in Konqueror. Right-clicking allows safe > removal. Problem: requires modern kernel and lots of other things. Only > few distributions (e.g. Kunbuntu) seem to have gotten this right, > certainly not Sarge. You're right. KDE starting from 3.4.0 supports this, but it didn't make it into sarge. Although it's just your 2) + a nice GUI to handle it. It has some points i dislike: a) no automounting, you still need to mount the device. Fine if you're using only kde-apps, but annoying for those who want to store a file from OpenOffice, Mozilla or whatever on the USB-Device. They've to open the directory in Konqueror, first. b) mountpoints are related to the devicenode, not to the label of the partition (like gnome-volume-manager and pmount-hal do) > I note that even 3) isn't true automounting, so maybe there is a 4). Yes there is. The IMHO optimal solution is to combine hal (for detecting new attached devices), pmount (for auto-mounting without being root) and a nice userspace-programm like GVM which starts the right program for the right medium (xine for VCD, Konqueror for Data-CD, USB-Stick, USB- or Firewire-Harddrive). Right now, gnome-volume-manager does this job quite nice. Unfortunately, g-v-m has nautilus hardcoded as filemanager, which makes it a suboptimal choice for KDE-Users. I wrote my own scripts (python) which do at least the auto-mounting thing using pmount-hal. If you're interested, inform me. Although you should know that i don't continue development of them nor are they really finished. But they "just work". Regards Roman -- If only you and dead people can read hex, how many people can read hex? pgpNgcadN6d2L.pgp Description: PGP signature
Re: Automounting experiments
John O'Hagan schrieb: ... Then I upgraded udev and hal, and suddenly pmount needed to be called manually. ... Which raised the question, how was it working in KDE without g-v-m,... If someone could figure out what those changes were, and how to make them (optionally) permanent, KDE's device automounting would be improved. Any thoughts? I think USB mounting is one of the greatest quagmires Linux has to offer; I don't know how much of this is due to - or on the other hand corrigible by - KDE. The mounting of USB-devices seems to involve too many competing systems and I havn't found a document which describes which methods are compatible and which are obsolete. E.g. I just read in LinuxUser that with hal, hotplug is no longer required. Yet Kubuntu, the only distribution I have tried which really works regarding with USB semi-automounting, still has hotplug. hotplug, automount, pmount, udev, hal and many more: this is a real mess only comprehensible to people who live and breathe Linux. Users who simply want to read and write their data are put off. I have spent hours trying to sort these out and many kind people on this list have given useful advice. I had to install a new kernel to even use pmount, which killed my sound and I havn't been able to get this back even with the help of experts on the debian-kernel list and have gone back to my old kernel. There seem to be (say) three generations of USB mounting systems: 1) The good old way: USB partitions showed up in /proc somewhere, e.g. /proc/partitions and one had to write an entry line in /etc/fstab and then mount manually as root or create a desktop icon which mounts and opens the device in konqueror. Problem: the partition labels change with different devices, so you need to either do a bit of detective work occasionally or maintain a whole zoo of /etc/fstab entries. (Completely manual mounting without going through /etc/fstab often doesn't work because often the file system type is unknown. In this case the only thing I have found which will even find the partition is QTparted, a super partitioning tool which is unfortunately incomplete and buggy and no longer maintained or even part of Debian, as far as I can tell.) 2) The semiautomatic way: detective work as above in 1), then use pmount /dev/sd. Device will show up in /media/sd and even on the desktop if you have "show devices" activated in KDE. Problem: needs a modern kernel. 3) The modern way: device icon appears automatically (unmounted) on desktop. Clicking mounts it in Konqueror. Right-clicking allows safe removal. Problem: requires modern kernel and lots of other things. Only few distributions (e.g. Kunbuntu) seem to have gotten this right, certainly not Sarge. I note that even 3) isn't true automounting, so maybe there is a 4). My personal solution is to forget about USB-mounting in my Debian system and to use a Kubuntu Live-CD whenever I need to use USB. Theo Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Automounting experiments
Hi all, There's been a lot of discussion on this list about automounting of removable devices. I thought this might be interesting: A while back I discovered pmount, and along with hal and udev on a 2.6.11 kernel, it worked as expected: plug in, icon appears, already mounted, no fstab entry required. (This is on KDE 3.3.2) Then I upgraded udev and hal, and suddenly pmount needed to be called manually. I emailed Martin Pitt, the author of pmount, and he explained how it is supposed to work: >...hotplug invokes hal, hal adds the new device to the db and sends out >notifications, gnome-volume-manager picks it up and calls >pmount-hal to actually mount the device >[...] >However, g-v-m is certainly not the intended solution for KDE... Which raised the question, how was it working in KDE without g-v-m, and why did it stop on upgrade of hal and udev? And which KDE part is supposed to listen to HAL events and call pmount-hal? Anyway, I installed gnome-volume-manager, added it to KDE Autostart and it ran in the background (its behaviour can be configured by running gnome-volume-properties), automounting nicely. On a recent upgrade to etch, I tried uninstalling g-v-m, and now found that the automounting was again working without it. Next upgrade of hal and udev, it stopped again; installed g-v-m, it worked, uninstalled it again, it kept working...I think you're beginning to see the pattern. It seems that installing g-v-m (without necessarily keeping it) does something to the system to enable hal to talk to pmount, and that upgrading certain programs overwrites those changes. If someone could figure out what those changes were, and how to make them (optionally) permanent, KDE's device automounting would be improved. Any thoughts? John O'Hagan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
