NOTE: an early draft of this question was sent somehow, ignore it
I have has miserable luck with fedup, is there a better way, anything? I really don't want to leave this machine down for days, and the 18->19 on a test machine took about 36 hours to complete, and another 3-4 to redo all the scripts from the ones on other machines which all use ethN to meaningless interface names. In 18 I just changed a single script to use (or not use) biosnames, and all was well, but on my test conversion to 19 that doesn't work, or the file was rewritten, and I finally used the name which changes every time the machine gets shuffled a bit.
Is there a better way than fedup, and why is it so slow?
On 11/22/2013 7:05 PM, Bill Davidsen wrote:
NOTE: an early draft of this question was sent somehow, ignore it
I have has miserable luck with fedup, is there a better way, anything? I really don't want to leave this machine down for days, and the 18->19 on a test machine took about 36 hours to complete, and another 3-4 to redo all the scripts from the ones on other machines which all use ethN to meaningless interface names. In 18 I just changed a single script to use (or not use) biosnames, and all was well, but on my test conversion to 19 that doesn't work, or the file was rewritten, and I finally used the name which changes every time the machine gets shuffled a bit.
Is there a better way than fedup, and why is it so slow?
My experience with Fedup is that it works. As long as you don't have some really 'strange', 3rd party, packages installed, that replace standard Fedora packages, and do not have any 'strange' repos enabled.
David wrote:
On 11/22/2013 7:05 PM, Bill Davidsen wrote:
NOTE: an early draft of this question was sent somehow, ignore it
I have has miserable luck with fedup, is there a better way, anything? I really don't want to leave this machine down for days, and the 18->19 on a test machine took about 36 hours to complete, and another 3-4 to redo all the scripts from the ones on other machines which all use ethN to meaningless interface names. In 18 I just changed a single script to use (or not use) biosnames, and all was well, but on my test conversion to 19 that doesn't work, or the file was rewritten, and I finally used the name which changes every time the machine gets shuffled a bit.
Is there a better way than fedup, and why is it so slow?
My experience with Fedup is that it works. As long as you don't have some really 'strange', 3rd party, packages installed, that replace standard Fedora packages, and do not have any 'strange' repos enabled.
Work it did, but it took about a day and a half to work, have no idea what it was doing. That's on a modest machine I know i7-950 quad, 32GB RAM, root on 128GB SSD (Intel, I think). I was hoping to have it sooner than that.
Strange repos, like rpmfusion so graphics work or adobe because people have things in flash (work things) I have to see. I do have those. Maybe that's the issue, if I didn't need to USE the system, I could do without them :-( Thanks for the warning, maybe I can disable, upgrade, then put in the needed things from single user mode.
Hi
On Fri, Nov 22, 2013 at 7:42 PM, Bill Davidsen wrote:
Work it did, but it took about a day and a half to work, have no idea what it was doing. That's on a modest machine I know i7-950 quad, 32GB RAM, root on 128GB SSD (Intel, I think). I was hoping to have it sooner than that.
Took about an hour on i3 on SSD with 4 GB of RAM. So not sure what is going on with your system.
Strange repos, like rpmfusion so graphics work or adobe because people have things in flash (work things) I have to see. I do have those. Maybe that's the issue, if I didn't need to USE the system, I could do without them :-( Thanks for the warning, maybe I can disable, upgrade, then put in the needed things from single user mode.
That wouldn't be needed since the repos get updated automatically
Rahul
On Fri, Nov 22, 2013 at 07:05:17PM -0500, Bill Davidsen wrote:
Is there a better way than fedup, and why is it so slow?
The last few upgrades, I went by the yum method. Despite all the warnings on the wiki, this seems to be the smoothest of all upgrade methods I have tried since F10.
Hope this helps,
Suvayu Ali wrote:
On Fri, Nov 22, 2013 at 07:05:17PM -0500, Bill Davidsen wrote:
Is there a better way than fedup, and why is it so slow?
The last few upgrades, I went by the yum method. Despite all the warnings on the wiki, this seems to be the smoothest of all upgrade methods I have tried since F10.
Hope this helps,
Appreciated! Having just wasted a lot of time with fedup, it may, I'll go check the wiki in the morning. On the first try I started with about 2G free, and got this:
18-fedup-64:root> time fedup --iso /mnt/10space/Downloads/ISO/Fedora/Fedora- 19/Fedora-19-x86_64-DVD/Fedora-19-x86_64-DVD.iso setting up repos... getting boot images... setting up update... finding updates 100% [=========================================================================] testing upgrade transaction rpm transaction 100% [=========================================================================]
Upgrade test failed with the following problems: insufficient disk space need 395M free on / (447M free) fedup ERROR: Upgrade test failed. rpm transaction 100% [=========================================================================]
real 1m35.615s user 0m17.963s sys 0m3.339s 18-fedup-64:root>
Which wasn't obvious, since the error message appears to say I have more than I need.
So I cleared more space and tried again, which ran to completion and told me to reboot. There was about a GB of stuff in the /var/tmp/fedora-upgrade tree, which was encouraging. I did the reboot, and the default boot option was Fedora upgrade, which started, put up a screen with a crawling white line, and when done booted back into Fedora18. Checking /boot there are no Fedora19 images, and /var/tmp/fedora-upgrade is now empty of all the stuff it had there before the reboot. Nothing is changed as far as I can see. I got this behavior with both a network upgrade and upgrade from an iso image with no visible network activity.
I'm very ready to try the yum method, since fedup is no more functional for me than ever, less actually, since it did eventually complete the last time I updated these machines.