CentOS

Not yet. Once I have the video file and have split it up into the separate presentations I will upload it to the CentOS youtube channel.

That could indeed be an issue with the system-auth pam file. If you're not able to get into the system remotely, then you would need to be able to connect to rescue mode somehow (remote KVM etc).

The authconfig command is not your problem. The system will still honor older md5 style passwords, however any NEW password will be created with sha512 encryption. This is handled via the beginning strings of the password in /etc/shadow. You'll either see a $1$ for md5 passwords, or a $6$ for the sh...

I went ahead and added my $0.02 to the bug report, but I'll add it here also. This is hitting a yum edge case, and highlights some of the differences between 'yum upgrade' and 'yum install' or yum update. The exactarch=1 default setting in /etc/yum.conf is what's causing yum to (rightfully) ignore t...

[quote]
AlanJBartlett wrote:
Thanks for those words of wisdom and spotting the bit I missed [b]Jim[/b].

[ot]Did you get a new broom at Christmas? :-P [/ot][/quote]

I'm all stocked up on brooms now. I've moved on to mops

I <3 mop!

This one is pretty clearly an sqlite issue. It's almost certainly due to having a newer version of sqlite interacting with the query structure or other bits. The notable entries in the error which show this are here -> TypeError: Can not create packages table: near "release": syntax error Mostly tha...

There's really no point to having this much swap, unless you're running something like oracle. If you're using that much swap space, you need to upgrade your hardware.

The old mantra of swap = 2x RAM stops applying after you hit 1G of ram or so.

I was trying to be polite. Mostly, you're doing something incorrectly and since I'm not watching over your shoulder, I don't know what. It's not a problem of software or servers. There's something that you're doing which isn't right. Or you possibly have a corrupt cookie store for bugs.centos.org.

Browser/User error. Just because it doesn't work for you, doesn't mean it's down. We have systems in place which watch our servers to notify us of problems and outages.

As a bit of etiquette, filing the SAME bug repeatedly is bad form. Doing what you're doing will just anger/irritate developers who need to be spending time on things other than closing duplicate bug reports.