Path: ...!2.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!news.eyrie.org!.POSTED!not-for-mail
From: Russ Allbery <eagle@eyrie.org>
Newsgroups: news.software.nntp
Subject: Re: INN 2.x FAQ
Date: Sun, 24 Mar 2024 10:11:14 -0700
Organization: The Eyrie
Message-ID: <87il1bimh9.fsf@hope.eyrie.org>
References: <FAQ-faq-1711004462$20714@hope.eyrie.org>
	<v8m00jt7fb5tkncmd5aehstvlspd2dhr0j@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: hope.eyrie.org;
	logging-data="2845"; mail-complaints-to="news@eyrie.org"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:BfyRBPKrhz6XIU8RmoxgIBuoV+c=
Bytes: 1803
Lines: 21

"floffy@gallaxial.com" <floffy@gallaxial.com> writes:

> Does have a fork for windows , i am very not good in linux ....

People have gotten INN working with Cygwin in the past, but it's been
quite a while and it probably doesn't work any more.  INN is very heavily
POSIX-based and would require substantial amounts of care and feeding to
get it to work on Windows, and my experience in the past with keeping such
a port of UNIX software working over time has not been positive.  It tends
to be very intrusive in the source code.

The more interesting question now is whether INN would work on the Windows
Subsystem for Linux (WSL).  That's much more likely, since WSL is
essentially a virtual Ubuntu system.  This may still be too Linux-y for
your needs, but it would be much more likely to work than trying to run
INN as a native Windows application.

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>

          Please post questions rather than mailing me directly.
     <https://www.eyrie.org/~eagle/faqs/questions.html> explains why.