From: Craig on
On 05/21/2010 08:14 PM, �Q� wrote:
> In<news:85ok12FoueU1(a)mid.individual.net>,
> Mark Warner<mhwarner.inhibitions(a)gmail.com> wrote:
>
>> This stuff has become so "seemless" that the distinction between
>> mounted and unmounted is kind of blurred anymore. Heck, the first
>> time I ran it, I opened up the file manager and didn't see them
>> anywhere, so I manually created a mount point under /mnt and stuck
>> 'em there. Didn't realize it would do it automagically with the
>> pointy clickity GUI desktop thingy until I revisted it last night.
>
> With a livecd, I don't care, but it's annoying with a new install. I
> need each USB drive and stick to have the same mountpoint every time
> it's mounted. So with a new install, I have to write a udev rule for
> each device, recheck the volume labels, create mount points that match
> those volume labels, and match them up in fstab. (Can't mount from the
> command line without fstab and can't mount consistently in KDE unless
> the mountpoints match the labels.)
>
> While they were making things "seemless" it would be nice if they'd
> tossed in some GUI for pairing drives with mountpoints.

Whoa... GUI's aside: Don't HAL Unique Device Identifiers or Unique unit
ID (UUID) solve this? You know, the string in the fstab like

> UUID=15f2abe8-94a6-4b52-bde6-f2191d7ed111

Or is this some other issue?

--
-Craig
From: Mark Warner on
Craig wrote:
> On 05/21/2010 08:14 PM, »Q« wrote:
>> In<news:85ok12FoueU1(a)mid.individual.net>,
>> Mark Warner<mhwarner.inhibitions(a)gmail.com> wrote:
>>
>>> This stuff has become so "seemless" that the distinction between
>>> mounted and unmounted is kind of blurred anymore. Heck, the first
>>> time I ran it, I opened up the file manager and didn't see them
>>> anywhere, so I manually created a mount point under /mnt and stuck
>>> 'em there. Didn't realize it would do it automagically with the
>>> pointy clickity GUI desktop thingy until I revisted it last night.
>>
>> With a livecd, I don't care, but it's annoying with a new install. I
>> need each USB drive and stick to have the same mountpoint every time
>> it's mounted. So with a new install, I have to write a udev rule for
>> each device, recheck the volume labels, create mount points that match
>> those volume labels, and match them up in fstab. (Can't mount from the
>> command line without fstab and can't mount consistently in KDE unless
>> the mountpoints match the labels.)
>>
>> While they were making things "seemless" it would be nice if they'd
>> tossed in some GUI for pairing drives with mountpoints.
>
> Whoa... GUI's aside: Don't HAL Unique Device Identifiers or Unique unit
> ID (UUID) solve this? You know, the string in the fstab like
>
>> UUID=15f2abe8-94a6-4b52-bde6-f2191d7ed111
>
> Or is this some other issue?

It's probably an issue with those bizzarro distros he uses. I mean,
c'mon. Gentoo??? Arch??? FFS...

--
Mark Warner
MEPIS Linux
Registered Linux User #415318
...lose .inhibitions when replying

From: Craig on
On 05/22/2010 09:36 AM, Mark Warner wrote:

> It's probably an issue with those bizzarro distros he uses. I mean,
> c'mon. Gentoo??? Arch??? FFS...

You know what they say.

> Gentoo: Almost as good as BSD

;-)
--
-Craig
From: za kAT on
On Sat, 22 May 2010 10:25:35 -0700, Craig wrote:

> On 05/22/2010 09:36 AM, Mark Warner wrote:
>
>> It's probably an issue with those bizzarro distros he uses. I mean,
>> c'mon. Gentoo??? Arch??? FFS...
>
> You know what they say.
>
>> Gentoo: Almost as good as BSD
>
> ;-)

<VVBG>

Just practicing. thank you for luving me.
--
zakAT(a)pooh.the.cat - www.zakATsKopterChat.com
From: »Q« on
In <news:ht83u4$b4r$1(a)news.eternal-september.org>,
Craig <netburgher(a)REMOVEgmail.com> wrote:

> On 05/21/2010 08:14 PM, »Q« wrote:
> > In<news:85ok12FoueU1(a)mid.individual.net>,
> > Mark Warner<mhwarner.inhibitions(a)gmail.com> wrote:
> >
> >> This stuff has become so "seemless" that the distinction between
> >> mounted and unmounted is kind of blurred anymore. Heck, the first
> >> time I ran it, I opened up the file manager and didn't see them
> >> anywhere, so I manually created a mount point under /mnt and stuck
> >> 'em there. Didn't realize it would do it automagically with the
> >> pointy clickity GUI desktop thingy until I revisted it last night.
> >
> > With a livecd, I don't care, but it's annoying with a new install.
> > I need each USB drive and stick to have the same mountpoint every
> > time it's mounted. So with a new install, I have to write a udev
> > rule for each device, recheck the volume labels, create mount
> > points that match those volume labels, and match them up in fstab.
> > (Can't mount from the command line without fstab and can't mount
> > consistently in KDE unless the mountpoints match the labels.)
> >
> > While they were making things "seemless" it would be nice if they'd
> > tossed in some GUI for pairing drives with mountpoints.
>
> Whoa... GUI's aside: Don't HAL Unique Device Identifiers or Unique
> unit ID (UUID) solve this? You know, the string in the fstab like
>
> > UUID=15f2abe8-94a6-4b52-bde6-f2191d7ed111
>
> Or is this some other issue?

That would probably solve at least part of it, but I've kept and
tweaked my approach as new KDE versions screwed with it. Next time a
new KDE breaks things, maybe I'll try the hal stuff.

The real problem is that KDE only wants to use a mountpoint that
matches the partition's volume label. If such a mountpoint doesn't
exist, KDE will create it. I'm not sure if KDE will even consult
fstab; people who don't (u)mount from the cli don't need to bother
with fstab entries for some time now.