From: "Johannes C. Schulz" <enzephalon76@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: netdev@vger.kernel.org
Subject: Re: bring back IPX and NCPFS, please!
Date: Fri, 9 Nov 2018 18:30:14 +0100 [thread overview]
Message-ID: <CAFfL_ozyvDbOL0Z-E6nLkhVF3oDQHFqAHVe1SvuUk2=kHHre7w@mail.gmail.com> (raw)
In-Reply-To: <20181109160903.GA1277@1wt.eu>
Hello Willy, hello Stephen
Thankyou for your reply.
But I'm not able to maintain or code these modules. I'm just a bloody
user/webdev. It would be really nice if these modules will find a good
maintainer!
Best regards
Johannes
Am Fr., 9. Nov. 2018 um 17:09 Uhr schrieb Willy Tarreau <w@1wt.eu>:
>
> On Fri, Nov 09, 2018 at 02:23:27PM +0100, Johannes C. Schulz wrote:
> > Hello all!
> >
> > I like to please you to bring back IPX and NCPFS modules to the kernel.
> > Whyever my admins using Novell-shares on our network which I'm not be
> > able to use anymore - I'm forced to use cifs instead (and the admins
> > will kill the cifs-shares in some time), because my kernel (4.18) does
> > not have support for ncpfs anymore.
> > Maybe we at my work are not enough people that just for us this
> > modules will come back, but maybe out there are other people.
> > Thank you.
>
> Well, like any code, it requires time and skills. If nobody with the
> required skills is available for this anymore, there's no way you'll
> get a feature back. However you could always step up to maintain it
> yourself if you have the time and are willing to develop your own
> skills at it. It's how maintainers change over time for certain parts
> of the system, so you have an opportunity here.
>
> Just my two cents,
> Willy
--
Viele Grüße
Johannes C. Schulz
„Programmer - n. [proh-gram-er] an organism that turns caffeine and
pizza into software“
next prev parent reply other threads:[~2018-11-10 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 13:23 bring back IPX and NCPFS, please! Johannes C. Schulz
2018-11-09 16:01 ` Stephen Hemminger
2018-11-09 16:09 ` Willy Tarreau
2018-11-09 17:30 ` Johannes C. Schulz [this message]
2018-11-09 18:20 ` Willy Tarreau
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='CAFfL_ozyvDbOL0Z-E6nLkhVF3oDQHFqAHVe1SvuUk2=kHHre7w@mail.gmail.com' \
--to=enzephalon76@googlemail.com \
--cc=netdev@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 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 NNTP newsgroup(s).