All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Issa <frechdesign@gmail.com>
Cc: autofs@linux.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [autofs] Autofs SMBFS no write in files
Date: Thu, 06 Jan 2011 22:04:53 +0800	[thread overview]
Message-ID: <1294322693.2852.2.camel@perseus> (raw)
In-Reply-To: <4D1A31B2.4000103@gmail.Com>

On Tue, 2010-12-28 at 19:51 +0100, Issa wrote:
> Hello,
> 
> 
> Autofs accés smbfs impossible d'écrire sur le disque ?
> Autofs smbfs no writing ?

A bit off topic but is there some reason you need to use smbfs.
It's deprecated and I expect it will go away some time soon.
You should try using CIFS if you have a reasonably recent (or even not
so recent should be ok) kernel.

> 
> Im usint autofs with ubuntu 10.10
> Im using autofs like this
> 
> 
> sudo nano /etc/auto.master
> 
> 
> +auto.master
> /mnt/smb       /etc/auto.auto   --timeout=60 --ghost
> et le fichier sudo nano /etc/auto.auto
> 
> 
> #directory name         option for mount                                                  device to mount
> win1            -fstype=smbfs,rw,credentials=/etc/smb.auth         ://win1/docs/
> Authentication files :
> sudo nano /etc/smb.auth
> 
> 
> username=users1
> password=motDePasse
> domain=windowsDomaine
> 
> now with this i can access only in read
> /mnt/smb/win1
> 
> My question how add acess to write ?
> 
> 
> because i can write for the moment.
> 
> 
> thanks
> 
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs


      reply	other threads:[~2011-01-06 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 23:02 [PATCH][RFC] autofs4: Do not potentially dereference null pointer returned by fget() in autofs_dev_ioctl_setpipefd() Jesper Juhl
2010-12-15  3:03 ` [autofs] " Ian Kent
2010-12-17 12:07   ` Jesper Juhl
2010-12-28 18:51     ` Autofs SMBFS no write in files Issa
2011-01-06 14:04       ` Ian Kent [this message]

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=1294322693.2852.2.camel@perseus \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=frechdesign@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.