How to stop Dolphin from mounting unwanted volume on Slackware 14.2
by will_kranz from LinuxQuestions.org on (#5H1VM)
I am just setting up a new system with Win10 and Linux Slackware 14.2.
I have a very similar system I have been using successfully for 3 years. Both came with a Win10 hard disk pre-configured. In new system I added a 2nd 500Gb disk with a large NTFS data partition, linux swap, and a linux root partition where I installed the Linux OS. Took me a while to identify the problem but the 3 new partitions are mounted from the new disk on /dev/sdb, the Windows disk is /dev/sda. I mount the desired partitions with /etc/fstab which included the main Windows partition as /Windows on /dev/sda2, the new NTFS data partition as /Archive on /dev/sdb1, linux swap as /dev/sdb2, and linux /root as /dev/sdb3. All is well, and I think I am home free. But it turns out that if I run the Dolphin file manager it auto mounts /dev/sda1 as another volume with the name /Archive which really confuses things. This 2nd /Archive, /dev/sda1, is the Win10 boot partition and I really don't want to be copying my data files there. I have no idea why or where behavior this comes from and I'd like to stop it. If I use Konquorer instead of Dolphin the problem never occurs. I have one other system with Win10 and Slackware Linux 14.2, and several with WinXP and linux configured like this. None have this auto mount problem with Dolphin. Anyone have suggestions?
My apology if this ends up a duplicate, I tried to post yesterday and it never appeared.
I have a very similar system I have been using successfully for 3 years. Both came with a Win10 hard disk pre-configured. In new system I added a 2nd 500Gb disk with a large NTFS data partition, linux swap, and a linux root partition where I installed the Linux OS. Took me a while to identify the problem but the 3 new partitions are mounted from the new disk on /dev/sdb, the Windows disk is /dev/sda. I mount the desired partitions with /etc/fstab which included the main Windows partition as /Windows on /dev/sda2, the new NTFS data partition as /Archive on /dev/sdb1, linux swap as /dev/sdb2, and linux /root as /dev/sdb3. All is well, and I think I am home free. But it turns out that if I run the Dolphin file manager it auto mounts /dev/sda1 as another volume with the name /Archive which really confuses things. This 2nd /Archive, /dev/sda1, is the Win10 boot partition and I really don't want to be copying my data files there. I have no idea why or where behavior this comes from and I'd like to stop it. If I use Konquorer instead of Dolphin the problem never occurs. I have one other system with Win10 and Slackware Linux 14.2, and several with WinXP and linux configured like this. None have this auto mount problem with Dolphin. Anyone have suggestions?
My apology if this ends up a duplicate, I tried to post yesterday and it never appeared.