From: "Lott, Christopher M" <clott-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Ubuntu SecurityFlags at boot
Date: Tue, 02 Oct 2012 01:24:57 -0400 [thread overview]
Message-ID: <506A7AA9.2090606@appcomsci.com> (raw)
In-Reply-To: <20121001214848.45781bb3-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
Thank you so much for explaining what should have been utterly obvious.
It worked perfectly when I did this:
% sudo -i
# echo 0x30030 > /proc/fs/cifs/SecurityFlags
# mount -t cifs //myoldtiredserver/lott /mnt
I'm still getting used to using echo for communicating with a kernel
module but that's just gonna take time :)
On 10/01/2012 09:48 PM, Jeff Layton wrote:
> The sudo in the above command just covers the echo command. The shell
> redirection (and hence the write to SecurityFlags) is done as the
> original user, which is why you're getting EACCES. You probably want
> to do something like this to ensure that the shell redirection is done
> as root as well:
>
> $ sudo sh -c "echo 0x30030 > /proc/fs/cifs/SecurityFlags"
>
next prev parent reply other threads:[~2012-10-02 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 22:23 Ubuntu SecurityFlags at boot Lott, Christopher M
[not found] ` <506A17EB.2050908-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
2012-10-02 1:48 ` Jeff Layton
[not found] ` <20121001214848.45781bb3-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-10-02 5:24 ` Lott, Christopher M [this message]
[not found] ` <506A7AA9.2090606-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
2012-10-02 11:19 ` Jeff Layton
[not found] <S1753625Ab2HELY7/20120805112459Z+242@vger.kernel.org>
[not found] ` <S1753625Ab2HELY7/20120805112459Z+242-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
2012-08-05 11:31 ` blueduck-GANU6spQydw
[not found] ` <484724139.8236317.1344166282900.JavaMail.root-TwAYtqM7ZI5mpWzFTGZ+Dhh1pbbyJDp15NbjCUgZEJk@public.gmane.org>
2012-08-05 15:29 ` Steve French
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=506A7AA9.2090606@appcomsci.com \
--to=clott-as7a0gipye2tg0buxcxiua@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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