From: Amit Gud <gud@ksu.edu>
To: Neil Brown <neilb@suse.de>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>,
Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH 01/11] nfs-utils: mount: non-nfs mount options
Date: Thu, 22 Mar 2007 16:23:34 -0500 [thread overview]
Message-ID: <4602F3D6.4090803@ksu.edu> (raw)
In-Reply-To: <17917.52788.9258.451246@notabene.brown>
Neil Brown wrote:
> On Friday March 16, SteveD@redhat.com wrote:
>>> and possible some other things that I didn't notice. As this is a
>>> setuid program, I really want to be able to review changes in
>>> isolation please.
>> Ok... I broke the original patch up into 3 separate ones.
>> Pleas see attachments...
>
> Thanks. I've applied the last.
> I'd really like to understand the ln/cp issue before applying. And
> I'm not quite ready to turn on setuid yet. Maybe when I do that,
> testing will show something.
>
I was not able to retain the setuid bit with ln, so I copied the files
over with -p option.
AG
--
May the source be with you.
http://www.cis.ksu.edu/~gud
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-03-22 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 11:17 [PATCH 01/11] nfs-utils: mount: non-nfs mount options Steve Dickson
2007-02-27 6:04 ` Neil Brown
2007-03-16 15:25 ` Steve Dickson
2007-03-18 23:41 ` Neil Brown
2007-03-22 21:23 ` Amit Gud [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=4602F3D6.4090803@ksu.edu \
--to=gud@ksu.edu \
--cc=SteveD@redhat.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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.