From: Dan Shelton <dan.f.shelton@gmail.com>
To: Roland Mainz <roland.mainz@nrubsig.org>
Cc: ms-nfs41-client-devel@lists.sourceforge.net, cygwin@cygwin.com
Subject: Re: [Ms-nfs41-client-devel] WinSG Re: ANN: NFSv4.1 filesystem client Windows driver binaries for Windows 10/11 for testing, 2024-05-28 ...
Date: Thu, 6 Jun 2024 23:40:01 +0200 [thread overview]
Message-ID: <CAAvCNcCufaJ_9c3+n9BkHtSHCFu0eKuNc=irMgu+Qb6xxgFwMg@mail.gmail.com> (raw)
In-Reply-To: <CAKAoaQnHye9AA0ii1-bOvORCZg1Fup7FwTHZCMLKR-GFtJe6Ew@mail.gmail.com>
On Sat, 1 Jun 2024 at 14:50, Roland Mainz via Cygwin <cygwin@cygwin.com> wrote:
>
> On Wed, May 29, 2024 at 4:28 AM Dan Shelton <dan.f.shelton@gmail.com> wrote:
> >
> > On Tue, 28 May 2024 at 22:15, Cedric Blancher via Cygwin
> > <cygwin@cygwin.com> wrote:
> > >
> > > Good evening!
> > >
> > > For your consideration - we need FEEDBACK, please!
> > >
> > > New is support running it as service (sc start
> > > ms-nfs41-client-service), setgid()/newgrp support (with a new winsg
> > > utility to run Windows applications with different primary group),
> > > 32bit kernel support, ACL+UNC path (cd //host@port/path1/path2 work in
> > > bash and ksh93)+chgrp+nfs:// support, and the NFS server no longer
> > > needs the "insecure" export switch.
> >
> > The WinSG utility is actually cool, because it can be used like a
> > normal Windows utility, and brings support for using multiple groups
> > to native Windows.
> >
> > Just a couple of ideas:
> > - Native Windows doesn't have an easy way to list group memberships
> > for the current user, so a WinSG -l to list available groups would be
> > good
>
> Done, I used -L (instead of -l) to avoid colliding with other
> newgrp(1) implementations (see
> https://github.com/kofemann/ms-nfs41-client/commit/65cec8f29cda6b8f4a1446203f6ab1cb988496ad?diff=unified&w=1).
>
> But in general I think Linux, Solaris/Illumos and Cygwin should
> standatise sg(1) with features like "-c cmdline" (like $ bash -c
> cmdline #) and -L (list groups suitable for -g), and make "-g
> groupname" mandatory.
>
Cool.
Are you going to make new binaries soon?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
prev parent reply other threads:[~2024-06-06 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKAoaQm2yrdyvd-U1Q4GztqFuEVpit4epsSpBZRJxR92nn+Fug@mail.gmail.com>
2024-05-28 20:14 ` Fwd: [Ms-nfs41-client-devel] " Cedric Blancher
2024-05-29 2:28 ` WinSG " Dan Shelton
2024-05-29 13:36 ` Bill Stewart
2024-05-30 23:42 ` Dan Shelton
2024-05-31 21:16 ` Andrey Repin
2024-06-06 21:37 ` Dan Shelton
2024-06-01 12:50 ` [Ms-nfs41-client-devel] WinSG " Roland Mainz
2024-06-02 22:12 ` matthew patton
2024-06-06 21:40 ` Dan Shelton [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='CAAvCNcCufaJ_9c3+n9BkHtSHCFu0eKuNc=irMgu+Qb6xxgFwMg@mail.gmail.com' \
--to=dan.f.shelton@gmail.com \
--cc=cygwin@cygwin.com \
--cc=ms-nfs41-client-devel@lists.sourceforge.net \
--cc=roland.mainz@nrubsig.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).