This is the mail archive of the
mailing list for the Cygwin project.
Re: [ITP] tftp-hpa 5.0
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 15 Nov 2010 15:26:39 +0100
- Subject: Re: [ITP] tftp-hpa 5.0
- References: <4CA42DB5.email@example.com> <4CA4406D.firstname.lastname@example.org> <4CA5F18E.email@example.com> <4CA6029A.firstname.lastname@example.org> <4CA98F44.email@example.com> <4CA9F1B4.firstname.lastname@example.org> <4CA9FE05.email@example.com> <4CB4A904.firstname.lastname@example.org> <4CDD621C.email@example.com> <4CDE1676.firstname.lastname@example.org>
- Reply-to: cygwin-apps at cygwin dot com
On Nov 12 23:39, Charles Wilson wrote:
> On 11/12/2010 10:49 AM, Gernot Hillier wrote:
> > On 12.10.2010 20:29, Charles Wilson wrote:
> >> Here's my revised version of your package:
> >> http://cygwin.cwilson.fastmail.fm/tftp-5.0-1-src.tar.bz2
> >> http://cygwin.cwilson.fastmail.fm/tftp-5.0-1.tar.bz2
> >> http://cygwin.cwilson.fastmail.fm/tftp-server-5.0-1.tar.bz2
> > Phew, 4 weeks passed by. Sorry for the long delay.
> 'Sokay. I've been busy, too.
> > But finally, I managed to test your binary packages - they look rather
> > nice to me. Account creation and service activation (--standalone)
> > worked quite nicely.
> > The only strange thing I stumbled over was that my Windows XP 64bit was
> > classified as NT 5.2 by uname, so that the additional account magic was
> > triggered. But that's likely another story - and it worked perfectly,
> > only the messages were a bit confusing.
> Well, it appears you are correct:
> Geez, Microsoft sux.
> However, I *wonder* if XP64 is more like NTServer2003, than it is like
The 64 bit kernel was developed after the XP 5.1 kernel. The resulting
64 bit-clean 5.2 kernel was then used for XP 64, 2K3 32 and 64 bit. The
numbering makes a lot of sense, given the history. And so, obviously,
XP 64 shares the new behaviour in some respect(*) with 2K3.
(*) The SYSTEM user restriction when starting a service is just one
difference. There are more. For instance, the new SO_REUSEADDR
socket binding behaviour, or the fact that \Device\PhysicalMemory is
not accessible from user space anymore.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com