mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Mathewson <joe@mathewson.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Jeremy White <jwhite@codeweavers.com>
Subject: Re: isofs unhide option:  troubles with Wine
Date: Sat, 25 May 2002 15:01:42 +0100	[thread overview]
Message-ID: <TiM$20020525030142$2365@deschutes.mathewson.int> (raw)
In-Reply-To: <1022334596.1262.6.camel@jwhiteh>

In message "Re: isofs unhide option:  troubles with Wine", <Jeremy White>
wrote:

> > >     1.  Invert the logic of the option, make it 'hide' instead
> > >         of unhide, and so unhide is the default.
> >
> > how about:
> >
> > /dev/hdb /cdrom iso9660 defaults,ro,unhide,user 0 2
> >
> > in your /etc/fstab. This would allow users to mount and unmount CDs.
> > It also changes the default to unhide.
>
> Yes, that is what we have to do now.  So, when our product is
> installed, a user is presented with a confusing, and highly technical
> question, the gist of which is:  please give us your root password
> so we can do something you don't understand.  It's okay, trust us,
> really...<grin>
>
> Further, I would argue that if you accept that unhide is a
> reasonable default for me to force into the fstab, then
> it is a reasonable default for the kernel to have.

Is this not an issue that could be put to RedHat/Mandrake/SuSE/Turbo/etc to
include the above fstab in their standard install.  If the user is going to have
to upgrade their kernel to get this default, they will understand fstab.  If
they do not understand fstab, they are going to upgrade their kernel by
upgrading their distro anyway.  So why not push for this option in the default
fstab of popular distros?

Joe.

  reply	other threads:[~2002-05-25 14:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-25  4:30 Jeremy White
2002-05-25 13:46 ` Olaf Dietsche
2002-05-25 13:49   ` Jeremy White
2002-05-25 14:01     ` Joseph Mathewson [this message]
2002-05-25 14:23       ` Jeremy White
2002-06-10  3:12       ` Francois Gouget
2002-06-10 11:52         ` Thunder from the hill
2002-06-10 12:38           ` Guest section DW
2002-05-25 15:50     ` Alan Cox
2002-06-03 17:05       ` Jeremy White
2002-06-03 18:06         ` Thunder from the hill
2002-06-03 18:40           ` H. Peter Anvin
2002-06-03 19:40             ` Thunder from the hill
2002-06-03 19:43               ` H. Peter Anvin
2002-06-04  0:23         ` Alan Cox
2002-06-19  2:36           ` Jeremy White
2002-05-25 14:18 ` Ruth Ivimey-Cook
2002-05-25 14:25   ` Jeremy White
2002-05-25 19:31   ` H. Peter Anvin
2002-05-25 19:40 ` Linus Torvalds
2002-05-25 20:31   ` H. Peter Anvin
2002-05-25 21:20     ` Lionel Bouton
2002-05-25 21:51       ` H. Peter Anvin
2002-05-25 21:07 ` Lionel Bouton
2002-05-25 17:04 Andries.Brouwer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='TiM$20020525030142$2365@deschutes.mathewson.int' \
    --to=joe@mathewson.co.uk \
    --cc=joe.mathewson@btinternet.com \
    --cc=jwhite@codeweavers.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®