Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: How to make gnus store received mail in the directory /mnt/windows?
Date: Mon, 15 Aug 2005 22:00:19 +0200	[thread overview]
Message-ID: <87hddr6kdo.fsf@koldfront.dk> (raw)
In-Reply-To: <ILA3ZQ$246B66A748A438EBD2EDCF097C0BF499@libero.it>

On Mon, 15 Aug 2005 21:40:38 +0200, romeomedina\@libero\.it wrote:

> What's it, a guessing game?

No. It is helping you to learn to find the information yourself.

> I read all through the fstab manual,

You did? Okay, that is all I can ask.

In the line in your fstab, do you see where all the other options are,
with commas between them? The part that says:
"umask=0,iocharset=iso8859-15,codepage=850"?

Try adding ",uid=501,gid=501" to those. Leaving you with a line like
this in your fstab:

# 1        2           3    4(!)
/dev/hda1 /mnt/windows vfat umask=0,iocharset=iso8859-15,codepage=850,uid=501,gid=501 0 0

> and also the mount options for fat, and neither there nor there it
> is said what the right place should be for the uid and gid options.

In the middle of the fstab man-page it says:

 "The fourth field, (fs_mntops), describes the mount options associated
  with the filesystem.

  It is formatted as a comma separated list of options. It contains at
  least the type of mount plus any additional options appropriate to
  the filesystem type. For documentation on the available options for
  non- nfs file systems, see mount(8). For documentation on all
  nfs-specific options have a look at nfs(5). Common for all types of
  file system are the options ``noauto'' (do not mount when "mount -a"
  is given, e.g., at boot time), ``user'' (allow a user to mount), and
  ``owner'' (allow device owner to mount), and ``comment'' (e.g., for
  use by fstab-main- taining programs). The ``owner'' and ``comment''
  options are Linux- specific. For more details, see mount(8)."


  Best regards,

-- 
 "Remember, Robert, in life anything can happen."             Adam Sjøgren
                                                         asjo@koldfront.dk




  parent reply	other threads:[~2005-08-15 20:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 19:40 romeomedina
2005-08-15 19:57 ` Derrell.Lipman
2005-08-15 20:02   ` Adam Sjøgren
2005-08-15 21:47   ` Rodolfo Medina
2005-08-15 22:18     ` Rodolfo Medina
2005-08-15 20:00 ` Adam Sjøgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-15 22:21 romeomedina
2005-08-16 21:05 ` Rodolfo Medina
2005-08-15 22:06 romeomedina
2005-08-15 18:25 romeomedina
2005-08-15 18:40 ` Adam Sjøgren
2005-08-15 19:48   ` Rodolfo Medina
2005-08-15 16:08 romeomedina
2005-08-15 16:35 ` David S. Goldberg
2005-08-15 18:39   ` Rodolfo Medina
2005-08-15 14:58 romeomedina
2005-08-15  8:57 romeomedina
2005-08-14 22:33 Rodolfo Medina
2005-08-15  3:11 ` Henrik Enberg
2005-08-15  3:25   ` Dave Goldberg
2005-08-15  9:00     ` Rodolfo Medina
2005-08-15  9:36       ` Adam Sjøgren
2005-08-15 15:19         ` Rodolfo Medina
2005-08-15  3:18 ` Dave Goldberg

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=87hddr6kdo.fsf@koldfront.dk \
    --to=asjo@koldfront.dk \
    /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;
as well as URLs for NNTP newsgroup(s).