From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bringing up NFS server on 64 bits
Date: Mon, 13 Jan 2014 09:24:00 -0000 [thread overview]
Message-ID: <20140113092359.GA19104@calimero.vinschen.de> (raw)
In-Reply-To: <002701cf1023$0e4b0110$2ae10330$%fedin@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Jan 13 09:48, Pavel Fedin wrote:
> Hello!
>
> > Not necessarily. If the package is in a good shape, has no known
> > security issues, and works fine with the latest Cygwin, you're good.
> > Other than that, just keep an eye on the Cygwin ML if somebody reported
> > a problem with your packages and see if you can lend a hand, maybe.
>
> This doesn't sound too bad.
>
> > This is a generic problem. Maintaining packages does not actually cost
> > a lot of time, unless you're trying to stick to the bleeding edge or
> > try to maintain too many packages. But people still shy away from that
> > without even trying. That's pretty disappointing.
>
> Ok, i will try to.
Thanks!
> So far:
> Packages to update: rpcgen, nfs-server
> New package: rpcbind
>
> Is rpcgen maintained or not ?
Marco answered that.
> And, nobody has answered the question. Who are original authors of this NFS server ?
SUN Microsystems, AFAIK.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-01-13 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:36 Pavel Fedin
2014-01-10 13:52 ` Corinna Vinschen
2014-01-10 14:29 ` Pavel Fedin
2014-01-10 15:07 ` Corinna Vinschen
2014-01-13 5:48 ` Pavel Fedin
2014-01-13 6:29 ` marco atzeri
[not found] ` <003101cf1031$c11cb640$435622c0$%fedin@samsung.com>
2014-01-13 8:11 ` marco atzeri
2014-01-13 9:24 ` Corinna Vinschen [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=20140113092359.GA19104@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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).