Issues with preupgrade F15B?

2011-05-11 Thread Philip A. Prindeville
I'm seeing the following after trying to update an fc14.x86_64 platform (updated) to Lovelock (F15B) with preupgrade: Booting 'Upgrade to Fedora 15 (Lovelock)' kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=da026107-5d0c-4c77-9fa4-502576c05cdd:/upgrade/ks.cfg

Re: Issues with preupgrade F15B?

2011-05-12 Thread Philip A. Prindeville
On 05/12/2011 09:01 AM, Nathanael D. Noblet wrote: > On 05/12/2011 12:20 AM, Philip A. Prindeville wrote: >> I'm seeing the following after trying to update an fc14.x86_64 platform >> (updated) to Lovelock (F15B) with preupgrade: >> >>Booting 'Upgrade

Re: Issues with preupgrade F15B?

2011-05-12 Thread Philip A. Prindeville
On 05/12/2011 11:49 AM, Philip A. Prindeville wrote: > On 05/12/2011 09:01 AM, Nathanael D. Noblet wrote: >> On 05/12/2011 12:20 AM, Philip A. Prindeville wrote: >>> I'm seeing the following after trying to update an fc14.x86_64 platform >>> (updated) to

Re: Issues with preupgrade F15B?

2011-05-13 Thread Philip A. Prindeville
On 05/13/2011 12:44 AM, Frank Murphy wrote: > On 13/05/11 05:24, Philip A. Prindeville wrote: > >> I'm not seeing any interest in resolving this, so I'm going to go ahead with >> a yum update instead. >> >> Too bad, the problem was 100% reproducible, so

Re: And logging issues following F15B upgrade

2011-05-14 Thread Philip A. Prindeville
On 05/14/2011 12:09 AM, Philip Prindeville wrote: > It's also not clear why logging goes to the console for mail services: > > [ 109.727642] imaps[1921]: accepted connection > [ 109.732264] master[2201]: about to exec /usr/lib/cyrus-imapd/imapd > [ 109.743816] imaps[2201]: executed > [ 109.7472

Glitch in "Upgrading from EOL Fedora using yum"

2013-05-13 Thread Philip A. Prindeville
I was reading the document: http://fedoraproject.org/wiki/Upgrading_from_EOL_Fedora_using_yum#Fedora_16_-.3E_Fedora_17 and got to the section: If you have /var on a separate partition, you will have to manually convert "/var/run" and "/var/lock" to a symbolic link. # mv -f /var

Re: Glitch in "Upgrading from EOL Fedora using yum"

2013-05-13 Thread Philip A. Prindeville
And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: > > May

Re: Glitch in "Upgrading from EOL Fedora using yum"

2013-05-20 Thread Philip A. Prindeville
And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: > > Mayb