linux-kernel - Re: Which kernel.org WWW is the master server?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 26 Aug 2010 08:36:55 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	piotr@...owicz.com
Cc:	Arnd Hannemann <hannemann@...s.rwth-aachen.de>,
	Jiri Kosina <jkosina@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Which kernel.org WWW is the master server?

On Thu, 26 Aug 2010 17:20:13 +0200 Piotr Hosowicz wrote:

> On 26.08.2010 17:10, Arnd Hannemann wrote:
> > Am 26.08.2010 15:37, schrieb Jiri Kosina:
> >> On Thu, 19 Aug 2010, Piotr Hosowicz wrote:
> >>
> >>
> >>> I wrote a simple python script that tells me that a new kernel version
> >>> appeared. The problem is that it is based exactly on this what appears on the
> >>> webpage so sometimes it resolves the server IP that the version has changed,
> >>> despite the fact that it is not true. Which server is the master server?
> >>>
> >> I guess that simply running
> >>
> >> 	finger @kernel.org
> >>
> >> will give you exactly the information you are looking for which much less
> >> pain of connecting to www server, parsing html, etc.
> >>
> >
> > Not sure if this is still accurate:
> >
> >> Aug 21, 2003: Please don't use *finger.kernel.org* for any sort of
> >> automatic monitoring. The number of automatic bots hitting this port
> >> is causing the finger daemon to shut down more often than not. The
> >> same information is available from
> >> http://www.kernel.org/kdist/finger_banner
> >> <http://kernel.org/kdist/finger_banner>.
> 
> Moreover it is written as the above.

I have a script that reads finger_banner then adds mmotm & its base kernel tree,
& linux-next & its base kernel tree to the finger_banner.  (It was written
before finger_banner included linux-next info.)

Output today is:

The latest linux-next version of the Linux kernel is:         next-20100826
The latest snapshot 2.6 version of the Linux kernel is:       2.6.36-rc2-git4
The latest mainline 2.6 version of the Linux kernel is:       2.6.36-rc2
The latest stable 2.6.35 version of the Linux kernel is:      2.6.35.3  
The latest stable 2.6.34 version of the Linux kernel is:      2.6.34.5  
The latest stable 2.6.33 version of the Linux kernel is:      2.6.33.7  
The latest stable 2.6.32 version of the Linux kernel is:      2.6.32.20 
The latest stable 2.6.31 version of the Linux kernel is:      2.6.31.14 
The latest stable 2.6.27 version of the Linux kernel is:      2.6.27.52 
mmotm-2010-0811-1610 ... applies to: 2.6.35
next-20100826 ... applies to: v2.6.36-rc2

http://www.xenotime.net/linux/scripts/kcurrent

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/