Discuss January 2014

discuss@lists.centos.org

194 participants
172 discussions

grub color on C6 (not)
by Ted Miller 08 Jan '14

08 Jan '14

I have tried more than half a dozen different combinations of the "color" command in my grub.conf file, and see nothing but black and white. Is there * a problem with the Centos grub command? * a problem with grub figuring out how to do color on my hardware? * a true-false day, when everything is either true or false, no in between grays, and no color? scratching my head, Ted Miller Elkhart, IN, USA

2 2

Odd problems with CR updates
by Scott Robbins 08 Jan '14

08 Jan '14

As I've seen no mention of this anywhere, I've got to assume it's just me. Doing some of the CR updates last night, google-chrome and firefox suddenly stopped working with https pages, including google itself. I was able to downgrade, but wasn't sure exactly what had caused the problem. Tonight, trying again, package by package, it seems that it's nss-softokn that's causing the problem. Has anyone run into something similar? For example, if I upgrade to the CR version, then open chromium and type a search phrase, I'll get message that this web page not available. Firefox is somewhat more informative, ---------- An error occurred during a connection to www.google.com. security library: invalid algorithm. (Error code: sec_error_invalid_algorithm) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. -------- This happens when I upgrade to nss-softokn.3.14.3-9.el6 When I downgrade to 3.14.3-3.el6_4 it's fine. Has anyone else run into this? -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

4 6

Re: [CentOS] [CentOS-announce] CentOS Project joins forces with Red Hat
by aly.khimji＠gmail.com 08 Jan '14

08 Jan '14

That is amazing news, I hope this proves to be a great relationship. Congratulations, looking forward to the future. Aly Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Karanbir Singh <kbsingh(a)centos.org> Sender: centos-announce-bounces(a)centos.org Date: Tue, 07 Jan 2014 21:09:27 To: CentOS Announcements List<centos-announce(a)centos.org> Reply-To: centos(a)centos.org Subject: [CentOS-announce] CentOS Project joins forces with Red Hat -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With great excitement I'd like to announce that we are joining the Red Hat family. The CentOS Project ( http://www.centos.org ) is joining forces with Red Hat. Working as part of the Open Source and Standards team ( http://community.redhat.com/ ) to foster rapid innovation beyond the platform into the next generation of emerging technologies. Working alongside the Fedora and RHEL ecosystems, we hope to further expand on the community offerings by providing a platform that is easily consumed, by other projects to promote their code while we maintain the established base. We are also launching the new CentOS.org website ( http://www.centos.org ). - ------------- The new initiative is going to be overseen by the new CentOS Governing Board. The initial Board comprises of the existing CentOS Core team members : - - Ralph Angenent - - Tru Hyunh - - Johnny Hughes JR - - Jim Perrin - - Karanbir Singh and also sees new members: - - Fabian Arrotin, who comes to the board nominated from the community - - Carl Trieloff, Karsten Wade, and Mike McLean join us, nominated by Red Hat. Please join me in welcoming the new members to the Board. The key operating points of the Board are going to be: Public, Open, and Inclusive. You can find more information about the governance model, the board, and the operating policies we are proposing at http://www.centos.org/about/governance/ Furthermore, some of the existing CentOS Core members are moving to take up roles at Red Hat, as a part of their sponsorship of the CentOS Project, allowing these people to work on the Project as their primary job function. This includes Johnny Hughes Jr, Jim Perrin, Fabian Arrotin, and myself. We will be working with and operating out of the Red Hat Open Source and Standards team in the CTO's Office. - ------------- Some of the things that are not changing: - - The CentOS Linux platform isn't changing. The process and methods built up around the platform however are going to become more open, more inclusive and transparent. - - The sponsor driven content network that has been central to the success of the CentOS efforts over the years stays intact. - - The bugs, issues, and incident handling process stays as it has been with more opportunities for community members to get involved at various stages of the process. - - The Red Hat Enterprise Linux to CentOS firewall will also remain. Members and contributors to the CentOS efforts are still isolated from the RHEL Groups inside Red Hat, with the only interface being srpm / source path tracking, no sooner than is considered released. In summary: we retain an upstream. Feel free to reach out if you have specific concerns about how this change impacts your CentOS story. URLs mentioned at the bottom of this email should be a good starting point. - ------------- Some of the key things that are changing: - - Some of us now work for Red Hat, but not RHEL. This should not have any impact to our ability to do what we have done in the past, it should facilitate a more rapid pace of development and evolution for our work on the community platform. - - Red Hat is offering to sponsor some of the buildsystem and initial content delivery resources - how we are able to consume these and when we are able to make use of this is to be decided. - - Sources that we consume, in the platform, in the addons, or the parallel stacks such as Xen4CentOS will become easier to consume with a git.centos.org being setup, with the scripts and rpm metadata needed to create binaries being published there. The Board also aims to put together a plan to allow groups to come together within the CentOS ecosystem as a Special Interest Group (SIG) and build CentOS Variants on our resources, as officially endorsed. You can read about the proposal at http://www.centos.org/variants/ - - Because we are now able to work with the Red Hat legal teams, some of the contraints that resulted in efforts like CentOS-QA being behind closed doors, now go away and we hope to have the entire build, test, and delivery chain open to anyone who wishes to come and join the effort. The changes we make are going to be community inclusive, and promoted, proposed, formalised, and actioned in an open community centric manner on the centos-devel mailing list. And I highly encourage everyone to come along and participate. - ------------- Contacting us works best via the established community mechanisms. - - Real time chats via IRC ( http://wiki.centos.org/irc ) ; To keep conversation sanity intact, I recommend using the #centos-devel channel to discuss project related activity while #centos is best used for end user conversations. - - The Mailing lists are a great way to interface with the developers, contributors and the community at large ( http://lists.centos.org ). As with IRC, we recommend using the centos-devel list to talk about project related issues while the general centos list is best used for end user conversations. - - The CentOS Forums are another great way to engage in conversation with other users ( http://www.centos.org/forums ), if you prefer that mechanism. All the above mentioned venues are public and open to the community, should you wish to discuss something privately, you can email us at centosdev(a)centos.org. Press requests should be sent to press(a)centos.org. Please note that it will take us much longer to reply to private requests as compared to content on the public venues. - ------------- In the coming days we are going to create opportunities for people to come and get involved in more face to face interactions. Starting with a regular scheduled office-hours format hangouts ( http://wiki.centos.org/OfficeHours ) that start early next week. We are trying to split the sessions into two different timezones so as to maximise the number of people who are able to join. The sessions will run live, with #centos-devel on irc.freenode.net being used for conversations alongside. We are also running a CentOS Dojo on the 31st Jan 2014 at Belgium ( http://wiki.centos.org/Events/Dojo/Brussels2014 ); The event will run two tracks, with lots of opportunities for social interaction between the talks; followed by CentOS in the Clouds Hack sessions. We are limited in the number of people we can accomodate, so I encourage everyone to register early. - ------------- I want to take this opportunity to thank all the sponsors, the contributors and the CentOS team members for all their help over the years, the project is built completely upon those contributions - and I look forward to seeing even more involvement from everyone as we move forward. - ------------- A Request: We are still sorting out content in various places and it might take a day or two to get everything in place. In the mean time if you find something stale and perhaps misleading in the new context ( or the old one! ) please drop in on #centos-devel at irc.centos.org and let us know. - ------------- Some URLS: - - http://www.centos.org/ The CentOS Project - - http://wiki.centos.org/ CentOS Community wiki - - http://community.redhat.com/ RedHat OSAS - - http://www.redhat.com/about/news/press-archive/2014/1/red-hat-and-centos-jo… - - Red Hat Press Release - - http://community.redhat.com/centos-faq - Red Hat FAQ's about the initiative - - http://wiki.centos.org/FAQ - CentOS FAQ's about the initiative Enjoy! and regards, Karanbir Singh and everyone from the CentOS team, - -- Karanbir Singh, Project Chair, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLMbQcACgkQMA29nj4Tz1sTnQCgj2fYxYpTjA0KwH7TpCWjE4gg w2cAniQWb/nh6Zn/8daSQ3EAfLIzGNKg =KJOk -----END PGP SIGNATURE----- _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce

1 0

Re: [CentOS] [CentOS-announce] CentOS Project joins forces with Red Hat
by David Hrbáč 07 Jan '14

07 Jan '14

Dne 7.1.2014 22:09, Karanbir Singh napsal(a): > With great excitement I'd like to announce that we are joining the Red > Hat family. The CentOS Project ( http://www.centos.org ) is joining > forces with Red Hat. Working as part of the Open Source and Standards > team ( http://community.redhat.com/ ) to foster rapid innovation > beyond the platform into the next generation of emerging technologies. > Working alongside the Fedora and RHEL ecosystems, we hope to further > expand on the community offerings by providing a platform that is > easily consumed, by other projects to promote their code while we > maintain the established base. Something I have dreamt of. Good news. Congratulations. Regards, David Hrbáč

1 0

Simple question on USB flash drive naming
by James B. Byrne 07 Jan '14

07 Jan '14

I have a USB key that when inserted into a port on my CentOS-6.5 system maounts as this: /dev/sdb1 /media/22d773e3-8502-4196-b45f-388380dcee48 ext2 rw,nosuid,nodev,uhelper=udisks 0 0 What is the mechanism to give this thing a more human usable mount name / volume name? Mounting this USB key with what I guess is a UUID in place of a name was not always the case. My sense is that the change in behaviour started when I moved the system from CentOS-5.7 to 6.0 but I cannot be sure that this is actually the case. The key has not changed since 2006 (CentOS-4) but the name that CentOS assigns to its mount point has. It used to be something like "kingston_blahblah" I looked at /dev/disk/ on the host and noted that the by-label sub-directory is gone. Is this something that should be there and is not or has CentOS-6 gotten rid of it? TIA -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS] Can we trust RedHat encryption tools?
by James B. Byrne 07 Jan '14

07 Jan '14

On Mon, January 6, 2014 16:51, m.roth(a)5-cent.us wrote: > > Looks like it's rtrying to install it, not just build it. In the first > example, you're trying to replace the existing /usr/bin/strip, which only > root can do. Are you doing make, or make install? > I started out by using the openssl.spec file for openssl-1.0.1f directly from openssl.org. The contents of that file are provided at http://git.openssl.org/gitweb/?p=openssl.git;a=blob_plain;f=openssl.spec;hb…. What I then do download the source from openssl.org and put that into ~/rpmbuild/SOURCES and extract it. I then copy ~/rpmbuild/SOURCES/openssl-1.0.1f/openssl.spec into ~/rpmbuild/SPECS and run the following commands: mock --buildsrpm --sources=./rpmbuild/SOURCES --spec=./rpmbuild/SPECS/openssl.spec mock --no-clean --rebuild --root=default /var/lib/mock/epel-6-x86_64/result/openssl-1.0.1f-1.src.rpm This gives the error reported above. I realize that this is a naive approach but I after looking at the Redhat openssl.spec file I thought it best to start with the base files provided by the origin and work out any build problems one by one making the absolute minimum number of changes possible. The nearest equivalent Redhat openssl.spec file that I found is that used by Fedora 20 for openssl-1.0.1e and its contents are displayed here: http://pkgs.fedoraproject.org/cgit/openssl.git/tree/openssl.spec?h=f20 >From what I have read elsewhere, Fedora/Redhat openssl begins with a set of modified source files. The spec file additionally applies about 43 patch files of which 27 alter the functionality of the package. It is not within my ability to determine what effect of the modifications to the source and these additional patches have on the integrity of the openssl provided with RHEL. Is there any third party in our community which does? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

Disappearing directory
by Ken Smith 07 Jan '14

07 Jan '14

Hi All and happy new year, Via a cron job a USB disk is mounted on a Centos 6.4 machine for backup and dismounted after. I've noticed this failing. See below, the backup directory that was in /mnt had disappeared, so creating it again as follows... # cd /mnt # mkdir backup # mount /dev/sdb1 /mnt/backup/ # ls backup # cd backup/ # ls boot.tar.gz etc etc.tar.gz home home.tar.gz ident.txt lost+found named.tar.gz root.tar.gz usr.tar.gz var var.tar.gz # cd .. # ls backup # umount /dev/sdb1 # ls # cat /etc/redhat-release CentOS release 6.4 (Final) After the umount the directory vanishes. What gives or have I lost the plot in 2014. (This works as I'd expect on an old fc14 system I have) :-) Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

7 15

CentOS-announce Digest, Vol 107, Issue 3
by centos-announce-request＠centos.org 07 Jan '14

07 Jan '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2014:0005 CentOS 6 sssd Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 6 Jan 2014 16:08:49 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0005 CentOS 6 sssd Update To: centos-announce(a)centos.org Message-ID: <20140106160849.GA10654(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0005 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0005.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0d31e0bfd94af81305f8e620a2c859c141d63ee6e7e1695da18ce9ff32b1d8ad libipa_hbac-1.9.2-129.el6_5.4.i686.rpm bd616a723787d89ad2832219915964b1cbb5c45251e013323a17572d18279a7d libipa_hbac-devel-1.9.2-129.el6_5.4.i686.rpm 89ef63c0d8b7d94d53ae76130d82624de337b1b17124abd44f3e5c8dfe8fe442 libipa_hbac-python-1.9.2-129.el6_5.4.i686.rpm d029a76709875099b811c8b788ca761a4851fed24a3e6cd8ac8301aeeebfe50e libsss_autofs-1.9.2-129.el6_5.4.i686.rpm ca729ea089821db0a6e31fae61ef8af691ee44b1c1dd3b7cab3706561ac5de8f libsss_idmap-1.9.2-129.el6_5.4.i686.rpm 570b574f6edd9bc3aeead48a3c8c3dda1425a97c5b53b429c8e99d83236b706b libsss_idmap-devel-1.9.2-129.el6_5.4.i686.rpm c4c441c07b31ffb3515725e08bfdb42bb0bf6a40731b21a8ccf737918765c0d1 libsss_sudo-1.9.2-129.el6_5.4.i686.rpm fab7bb18cf94a75dc2ae89444cd26f593871ff74e0ee7d48d46666703121f3d3 libsss_sudo-devel-1.9.2-129.el6_5.4.i686.rpm 036a42feb61a07ae20a44ba2119f59f7208acdcb4a3f2c99578ae6fb8e950806 sssd-1.9.2-129.el6_5.4.i686.rpm 63b9d09340e4c54efec67109d168de2ec1c489e9f08e5eb0887cc155977c4406 sssd-client-1.9.2-129.el6_5.4.i686.rpm 82673b1596a9ac0dddcbbc09398607d20a2d852e65d37dc8294260d82d2ef485 sssd-tools-1.9.2-129.el6_5.4.i686.rpm x86_64: 0d31e0bfd94af81305f8e620a2c859c141d63ee6e7e1695da18ce9ff32b1d8ad libipa_hbac-1.9.2-129.el6_5.4.i686.rpm ac4561121f9aaf41acae676fbb33cff958afb8c071a43274b7970df0c056191f libipa_hbac-1.9.2-129.el6_5.4.x86_64.rpm bd616a723787d89ad2832219915964b1cbb5c45251e013323a17572d18279a7d libipa_hbac-devel-1.9.2-129.el6_5.4.i686.rpm 2a53eda1460fdf2cc9df81487c05c45c876d70fa104ee88833a40864bff84bd6 libipa_hbac-devel-1.9.2-129.el6_5.4.x86_64.rpm 09f2329cf4a85ce0ed1e2e5d57df1548b592143cc914d56996abf704ba34044b libipa_hbac-python-1.9.2-129.el6_5.4.x86_64.rpm 73eaff3cccaa30f13cf431c1b5b19461e9e2c931ea85e2a00fe73d5c2109104f libsss_autofs-1.9.2-129.el6_5.4.x86_64.rpm ca729ea089821db0a6e31fae61ef8af691ee44b1c1dd3b7cab3706561ac5de8f libsss_idmap-1.9.2-129.el6_5.4.i686.rpm a7ba5cea05f9519f873bd08bdb478aad7f79156f8db26a7aceaf264ce90593e9 libsss_idmap-1.9.2-129.el6_5.4.x86_64.rpm 570b574f6edd9bc3aeead48a3c8c3dda1425a97c5b53b429c8e99d83236b706b libsss_idmap-devel-1.9.2-129.el6_5.4.i686.rpm f9346e709519c0bcb049d0f9d1cbe95692864bb8f114a96b1913f0763bf94dad libsss_idmap-devel-1.9.2-129.el6_5.4.x86_64.rpm 3ccbe1d1f618371ed1a71dc08fa30b5a997c0fcc119704202a901e5fd7cc9520 libsss_sudo-1.9.2-129.el6_5.4.x86_64.rpm fab7bb18cf94a75dc2ae89444cd26f593871ff74e0ee7d48d46666703121f3d3 libsss_sudo-devel-1.9.2-129.el6_5.4.i686.rpm 9a72bb6896d6052055cecf2206d0cdd49bd7ef672040f2154da662402d34082d libsss_sudo-devel-1.9.2-129.el6_5.4.x86_64.rpm 6afd1e8393d11c7f977b715a49935db27868dc9375c614872d65d4084e9e5d36 sssd-1.9.2-129.el6_5.4.x86_64.rpm 63b9d09340e4c54efec67109d168de2ec1c489e9f08e5eb0887cc155977c4406 sssd-client-1.9.2-129.el6_5.4.i686.rpm 218cbec8a327d7077713b545d95738f962d2fec46d11a6ee415b9858cd01012b sssd-client-1.9.2-129.el6_5.4.x86_64.rpm c7e5f0ab55282731cf7a4d0b316cec008135772a6b9eae5fc0c74f2f7bb9d81b sssd-tools-1.9.2-129.el6_5.4.x86_64.rpm Source: ccda87b7a3678c790b5802581d057d16f76ac908c1d317e55bb61b5730c892e3 sssd-1.9.2-129.el6_5.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 107, Issue 3 ***********************************************

1 0

nfs client kerberos cache
by Darod Zyree 06 Jan '14

06 Jan '14

Greetings, Not sure if this is the correct mail list. I have the following test environment set up: - 1x ipa master = ipa1.example.com - 1x nfs server = nfs1.example.com - 1x nfs client = nfsclient1.example.com NFS version 4 is used and the appropriate Kerberos principal has been created in IPA: [root@nfs1 ~]# ipa service-show nfs/nfs1.example.com(a)EXAMPLE.COM Principal: nfs/nfs1.example.com(a)EXAMPLE.COM Keytab: True Managed by: nfs1.example.com Mounting using krb5p works: [root@nfsclient1 ~]# mount -v -t nfs -o sec=krb5p nfs1.example.com:/exports/homes/ /mnt mount.nfs: timeout set for Mon Jan 6 21:25:56 2014 mount.nfs: trying text-based options 'sec=krb5p,vers=4,addr=192.168.12.172,clientaddr=192.168.12.173' nfs1.example.com:/exports/homes/ on /mnt type nfs (rw,sec=krb5p) rpcgssd created the Kerberos cache file as indicated in /var/log/messages: rpc.gssd[2473]: INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_EXAMPLE.COM' are good until 1389125973 So far so good, but then: 1) I unmount everything from nfs1, remove the nfs1.example.host, its DNS record(s) and service principcals. 2) I redeploy the nfs1.example.com and re-create the nfs/nfs1.example.com(a)EXAMPLE.COM principal 3) I try to mount the same NFS share from nfs1 on nfsclient1 I get an error: mount.nfs: trying text-based options 'sec=krb5p,vers=4,addr=192.168.12.172,clientaddr=192.168.12.173' mount.nfs: mount(2): Operation not permitted Now I'm not an IPA or Kerberos expert but I am guessing that this happens because the nfsclient1 still has, and uses, the /tmp/krb5cc_machine_EXAMPLE.COM cache file? This file would have the “old” Kerberos credentials?... On the NFS server in /var/log/messages this error message is displayed: "rpc.svcgssd[5983]: ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more information) - Wrong principal in request" On the NFS client in /var/log/messages these messages are displayed: "creating context with server nfs(a)nfs1.example.com" "WARNING: Failed to create machine krb5 context with credentials cache FILE:/tmp/krb5cc_machine_EXAMPLE.COM for server nfs1.example.com" "WARNING: Machine cache is prematurely expired or corrupted trying to recreate cache for server nfs1.example.com" Restarting the rpcgssd daemon works, this action removes the /tmp/krb5cc_machine_EXAMPLE.COM file and upon a mount command it is recreated. However restarting the rpcgssd daemon on all NFS clients every time an NFS server is redeployed doesn't feel right. Anyone perhaps have an idea on what I might be doing wrong? Or is this by design?

1 0

Re: [CentOS] I want to ask about some Kernel level operations.
by Eliezer Croitoru 05 Jan '14

05 Jan '14

Hey, I am still not sure if it's Harald or Reindl as first name. Now for the matter in hands: I am building the software mostly manually if I can! The problem is that most software developers tend to build their software in a very good way. The kernel developers for example of a remarkable software is a very strict environment. If I cannot build the kernel as root user it is better to not build it at all from my aspect. The RPMBUILD tools and other automation tools is suppose to help distributing and test the code. Once it has passed these tests why would I need to build them as a non-root user? We all humans and we do tend to maybe miss here and there something but don't let these MOCKs and RPMbuilds to just *vaporise* the basic efforts which the developers invested. I would say something like that: Building as root user\s level is not recommended due to couple incidents in the past. All The Bests, Eliezer On 05/01/14 17:16, Reindl Harald wrote: > DO NOT BUILD AS ROOT AND USE MOCK/RPMBUILD > > what is your problem as you statet even in the original post > that you know that it is not recommended to build as root > but you insist in doing so? > > *what* do you want to achieve with this thread? >

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2014