media:/ shows unnecessary media
Rajeev J Sebastian
rajeev_jsv at dinamis.com
Sun May 29 10:17:00 CDT 2005
On Sunday 29 May 2005 8:50 am, Giuseppe Bilotta wrote:
> Plus, pmount complains
> about hdas not being removable media, so one of the big issues here is
> that pmount will *not* work with hard disks. Maybe it will if they are
> recognized via the hotplug/udev interface, but I don't know.
Ok good (!!). fstab-sync/pmount doesnt work. No problem.
> > Yeah that is a problem :) Obviosly, we shouldn't allow that, but I havent
> > checked. But I also think
>
> Therefore you are ;)
:) .. what I meant was, the partition-id disambiguates. Plus, if a user tries
to set a label to an entry in media:/ which is the same as another, media:/
complains. So that takes care of the manual case.
>
> >>> 2) else if the user has already changed the name to something more
> >>> appropriate in media:/, it sets that as the label in media :/
> >>
> >> Is this necessary? :)
> >
> > Yep its necessary, otherwise, we might overwrite the label set by the
> > user.
>
> Just skip that partition? :)
yeah, same as re-setting it :) but your method is good since we have better
performance. thanks :)
>
> > If someone can give me a printout/screenshot of hal-device-manager
> > showing the Advanced properties of a USB stick, I can make sure that such
> > disks are labelled accordingly.
>
> I will try and do it later today.
Thanks
> > Well, as long as you have the dependencies (python2.4-dbus,
> > python2.4-dcop and python2.4) then it should run (you need to modify the
> > /etc/defaults/hal as well so that we can retrieve partition type info
> > from HAL).
>
> Hm. Hope Kubuntu live has those deps :)
I had to manually install dcop package.
> But it should only happen if it wasn't configured already ...
> otherwise just a popup notice to let the user know the device has been
> (re)added.
Yep, exactly.
> > perhaps, it is also a start to a kubuntu specific device-manager ?
>
> That's an interesting idea. Are there Kubuntu-specific feature that
> allow that, or can the scripts and all be passed upstream with little
> change?
Yeah why not. What I meant by kubuntu-specific, is that it should fit the
vision of kubuntu (and maybe debian), than anything else in particular. But,
I see nothing stopping it from going upstream (if upstream was KDE-Debian).
In particular, I would like to have something like the "Send to Ubuntu" button
that hal-device-manager has: to submit hardware profile to some online
service (or via email, snail mail, whatever) for analysis purposes.
My plan is this:
1) expand the script to make it a sort of service
2) have plugins to do stuff when conditions occur.
The more I look at it, it seems very much like ivman. However, ivman uses
pmount. I will write my own fstab-sync-ing system, unless it is not
advisable.
Any opinions on this ?
Rajeev J Sebastian
More information about the kubuntu-devel
mailing list