Re: Supermount

2002-04-15 Thread David Odin
On Mon, Apr 15, 2002 at 07:17:38PM +1000, David Findlay wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Is there a particular reason why Supermount couldn't be included in the 
> debian unstable kernels as an option? It works brilliantly on Mandrake, and 
> makes things much easier to use. Thanks,
> 
  Please, no!

  Supermount has a lots of problems if you're not alone on your system,
and most of its features can be done with the more robust automount.

   DindinX

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Supermount

2002-04-15 Thread David Odin
On Mon, Apr 15, 2002 at 07:38:26PM +1000, David Findlay wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Mon, 15 Apr 2002 19:25, David Odin wrote:
> > On Mon, Apr 15, 2002 at 07:17:38PM +1000, David Findlay wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > Is there a particular reason why Supermount couldn't be included in the
> > > debian unstable kernels as an option? It works brilliantly on Mandrake,
> > > and makes things much easier to use. Thanks,
> >
> >   Please, no!
> >
> >   Supermount has a lots of problems if you're not alone on your system,
> > and most of its features can be done with the more robust automount.
> 
> Why can't it be included *ONLY AS AN OPTION*?

  Because I don't want debian developper to spend time on this crap, and
even more on explaining the user why this doesn't work as expected.

Supermount is a very bad hack, and as the problem of letting a user
'lock' a removable medium, if it is "superunmounted" when still in use.

> automount is totally insufficient compared to the supermount patch.
> Or is there some other patch that has equal functionality for mounting
> removable media immediately when it is put in and then umounting it
> when ejected? Thanks,
> 
  Automount will mount the medium as soon as you access it. I fail to see
any use of mounting a medium when it is put, and before it is accessed.
The medium will be unmounted after a 'user defined' time. I've chosen 5
seconds, so at most, I'll have to wait 5 seconds between the last time I
access the medium and the moment I want to eject the medium.

  The way of acting is the same as supermount, but it won't let you do
stupid thing such as ejecting a medium in use.

DindinX

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Supermount

2002-04-15 Thread David Odin
On Mon, Apr 15, 2002 at 07:54:48PM +0200, Tomas Pospisek's Mailing Lists wrote:
> On Mon, 15 Apr 2002, Joseph Carter wrote:
> 
> > On Mon, Apr 15, 2002 at 12:06:23PM +0200, David Odin wrote:
> 
> > >   The way of acting is the same as supermount, but it won't let you do
> > > stupid thing such as ejecting a medium in use.
> 
> Depending on what "use" means it's not the user that is stupid, but the
> implementation. I know from experience that it is impossible to emulate
> windows removable media behaveour which is a PITA. For "normal" people
> it's the led that's the indicator of "in use", which is IMHO not that
> stupid. Stupid is that the whole chain of tools expects media to be
> unmounted and if you don't do it that favor as a not-so-experienced user
> will most probably *will* have to pull the plug to get that "*&/%"*/&% CD
> out of the drive.
> *t
> 
  Well, the main problem I have with supermount and not have with
automount is the following:
  I'm a CS teacher, and the linux distribution in the computer room is
mandrake. And, very often, a student use supermount to mount a floppy,
do some stuff, but manage to log off with the floppy still mounted.
Then, the next student using the same computer cannot use the floppy,
since it is still mounted. Only root can unmount then, and that's very
boring.

   DindinX

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Supermount

2002-04-15 Thread David Odin
On Mon, Apr 15, 2002 at 05:12:26PM -0400, Sean Middleditch wrote:
> On Mon, 2002-04-15 at 16:54, David Odin wrote:
> >   Well, the main problem I have with supermount and not have with
> > automount is the following:
> >   I'm a CS teacher, and the linux distribution in the computer room is
> > mandrake. And, very often, a student use supermount to mount a floppy,
> > do some stuff, but manage to log off with the floppy still mounted.
> > Then, the next student using the same computer cannot use the floppy,
> > since it is still mounted. Only root can unmount then, and that's very
> > boring.
> 
> Why is the floppy being mounted/unmounted at all?

  This is the point: the floppy is mounted by supermount, and never
  unmounted!

> If you hav supermount, the point is quite simply that you do not have to
> mount/unmount once the device is mounted; you are mounting the device
> itself, not the medium.
> 
> If you don't want supermount in Mandrake, just remove the supermount
> settings from /etc/fstab, unload the kernel module, and no student
> should be able to mount w/ supermount anymore.
> 
  I don't have a Mandrake at home, thanks.
  In the computer classroom, I have the root passwd (I'm a teacher, not
the admin), so i cannot edit /etc/fstab or whatever, and anyway, most of
my student are unable to mount anything "by hand". Imho, the way to go
is to use automount there.

DindinX

-- 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]