here's the current situation if anyone wants to suggest tests. i have my two gateway MX7120s installed with fedora 11 alpha -- one with i386, the other with x86_64 -- virtually identically (about 1550 packages on each).
the first difference is that, at the end of the install, when i rebooted, the i386 install rebooted cleanly while the x86_64 install flashed a screenful of kernel diagnostics on its way down, but it still booted cleanly coming back up again. not sure what that was all about.
at this point, before i do *anything*, should i take note of the current setup in any way? suggestions? my first step would be to update the yum/rpm packages but, to do that, i would first update "fontpackages-filesystem" since its original packaging conflicted with "rpm-build" which i installed, so my proposed first step would be:
# yum update fontpackages-filesystem # yum update rpm* # yum update yum
does that make sense? but even before i do that, i'm still open to what i should record in terms of current config.
thoughts?
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA ========================================================================
On 3/5/2009 7:55 AM, Robert P. J. Day wrote:
here's the current situation if anyone wants to suggest tests. i have my two gateway MX7120s installed with fedora 11 alpha -- one with i386, the other with x86_64 -- virtually identically (about 1550 packages on each).
the first difference is that, at the end of the install, when i rebooted, the i386 install rebooted cleanly while the x86_64 install flashed a screenful of kernel diagnostics on its way down, but it still booted cleanly coming back up again. not sure what that was all about.
at this point, before i do *anything*, should i take note of the current setup in any way? suggestions? my first step would be to update the yum/rpm packages but, to do that, i would first update "fontpackages-filesystem" since its original packaging conflicted with "rpm-build" which i installed, so my proposed first step would be:
# yum update fontpackages-filesystem # yum update rpm* # yum update yum
does that make sense? but even before i do that, i'm still open to what i should record in terms of current config.
thoughts?
Do I understand correctly that these are *not* updated to current Rawhide yet?
If so you would probably need to do the x86 and x86_64 updates in small stages. Rawhide x86 was rebuild from i386 to i586 recently so I would think that most, if not *all*, of the packages installed would be an 'update' on the x86 install.
That would hold true for the x86_64 install too for the x86 packages installed there.
Good luck.
On Thu, 5 Mar 2009, David wrote:
On 3/5/2009 7:55 AM, Robert P. J. Day wrote:
here's the current situation if anyone wants to suggest tests. i have my two gateway MX7120s installed with fedora 11 alpha -- one with i386, the other with x86_64 -- virtually identically (about 1550 packages on each).
the first difference is that, at the end of the install, when i rebooted, the i386 install rebooted cleanly while the x86_64 install flashed a screenful of kernel diagnostics on its way down, but it still booted cleanly coming back up again. not sure what that was all about.
at this point, before i do *anything*, should i take note of the current setup in any way? suggestions? my first step would be to update the yum/rpm packages but, to do that, i would first update "fontpackages-filesystem" since its original packaging conflicted with "rpm-build" which i installed, so my proposed first step would be:
# yum update fontpackages-filesystem # yum update rpm* # yum update yum
does that make sense? but even before i do that, i'm still open to what i should record in terms of current config.
thoughts?
Do I understand correctly that these are *not* updated to current Rawhide yet?
you understand that correctly -- they are fresh off the original DVDs.
If so you would probably need to do the x86 and x86_64 updates in small stages. Rawhide x86 was rebuild from i386 to i586 recently so I would think that most, if not *all*, of the packages installed would be an 'update' on the x86 install.
That would hold true for the x86_64 install too for the x86 packages installed there.
and yet, that was one of the issues -- whether (after upgrading the fundamental yum and rpm* packages), i should simply be able to type "yum update" and go drink beer. some people claimed that they had done exactly that -- my experience was otherwise.
so what's the story here? are you saying that that should *not* be expected to succeed? if not, that's pretty important information.
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA ========================================================================
On 3/5/2009 11:32 AM, Robert P. J. Day wrote:
On Thu, 5 Mar 2009, David wrote:
On 3/5/2009 7:55 AM, Robert P. J. Day wrote:
here's the current situation if anyone wants to suggest tests. i have my two gateway MX7120s installed with fedora 11 alpha -- one with i386, the other with x86_64 -- virtually identically (about 1550 packages on each). the first difference is that, at the end of the install, when i rebooted, the i386 install rebooted cleanly while the x86_64 install flashed a screenful of kernel diagnostics on its way down, but it still booted cleanly coming back up again. not sure what that was all about. at this point, before i do *anything*, should i take note of the current setup in any way? suggestions? my first step would be to update the yum/rpm packages but, to do that, i would first update "fontpackages-filesystem" since its original packaging conflicted with "rpm-build" which i installed, so my proposed first step would be: # yum update fontpackages-filesystem # yum update rpm* # yum update yum does that make sense? but even before i do that, i'm still open to what i should record in terms of current config. thoughts?
Do I understand correctly that these are *not* updated to current Rawhide yet?
you understand that correctly -- they are fresh off the original DVDs.
If so you would probably need to do the x86 and x86_64 updates in small stages. Rawhide x86 was rebuild from i386 to i586 recently so I would think that most, if not *all*, of the packages installed would be an 'update' on the x86 install.
That would hold true for the x86_64 install too for the x86 packages installed there.
and yet, that was one of the issues -- whether (after upgrading the fundamental yum and rpm* packages), i should simply be able to type "yum update" and go drink beer. some people claimed that they had done exactly that -- my experience was otherwise.
so what's the story here? are you saying that that should *not* be expected to succeed? if not, that's pretty important information.
Actually it should succeed but I don't think I would "go drink beer". I might *stay* and drink beer though. 8-)
The way the update works is that *all*, you said 1500, packages would be downloaded, then installed, and then the cleanup would begin. That would take a lot of disk space with the potential to fail at any stage.
For the 64bit you would get *all* of the i386 now i586 packages install and all of the 64bit packages that have changed. And Rawhide changes a lot every day.
Someone posted a script a while back, might have been here, that was supposed to help someone with a disk space problem by doing the update a little at a time. IIRC it was for a release upgrade but I don't see why it would not work here.
Disclaimer here: I have not used this. :-)
---------------------------------------------------------------------
#! /bin/bash
yum -q check-update > /root/check-update for i in `awk '{print $1}' < /root/check-update` do yum -y update $i yum clean all done rm /root/check-update
---------------------------------------------------------------------
And I would do this in level 3 and not in the GUI level 5. Less things to go wrong that way.
You do know how to get to level three?
On Thu, 5 Mar 2009, David wrote:
The way the update works is that *all*, you said 1500, packages would be downloaded, then installed, and then the cleanup would begin. That would take a lot of disk space with the potential to fail at any stage.
that's probably why, after updating *only* rpm* and yum, the first thing i did was install the downloadonly plugin, then "yum update --downloadonly", wait ... wait ... wait ... then burn all those packages to DVD before going any further. just to save time the next time.
oh, and i set "keepcache=1". just playing it safe.
For the 64bit you would get *all* of the i386 now i586 packages install and all of the 64bit packages that have changed. And Rawhide changes a lot every day.
i understand that. it still brings us back to the same issue -- should i *expect* "yum update" to just work, even with rawhide? as in, should i expect it not to totally hose my system to the point where i have to re-install from scratch?
Someone posted a script a while back, might have been here, that was supposed to help someone with a disk space problem by doing the update a little at a time. IIRC it was for a release upgrade but I don't see why it would not work here.
i have buckets of disk space -- i accepted the default disk partitioning so i have one honking big root filesystem (>80G). disk space is not an issue.
And I would do this in level 3 and not in the GUI level 5. Less things to go wrong that way.
You do know how to get to level three?
yes, dear ... i've done it a time or two in my day. :-)
rday --
p.s. still waiting for suggestions as to what to do first if anyone wants to see the current state of the systems before i bork them totally. or i'll just start things rolling and you'll hear the angry shrieking at some point later this afternoon.
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA ========================================================================
On 3/5/2009 12:25 PM, Robert P. J. Day wrote:
On Thu, 5 Mar 2009, David wrote:
The way the update works is that *all*, you said 1500, packages would be downloaded, then installed, and then the cleanup would begin. That would take a lot of disk space with the potential to fail at any stage.
that's probably why, after updating *only* rpm* and yum, the first thing i did was install the downloadonly plugin, then "yum update --downloadonly", wait ... wait ... wait ... then burn all those packages to DVD before going any further. just to save time the next time.
oh, and i set "keepcache=1". just playing it safe.
A good idea there. That will avoid most of the 'downloading again' should things go south. An 'update' in a few days would only be recent changes. It is not uncommon for there to be 50, or so, packages a day. It all depends on how much of what you have installed.
For the 64bit you would get *all* of the i386 now i586 packages install and all of the 64bit packages that have changed. And Rawhide changes a lot every day.
i understand that. it still brings us back to the same issue -- should i *expect* "yum update" to just work, even with rawhide? as in, should i expect it not to totally hose my system to the point where i have to re-install from scratch?
I would. I have, as a time with nothing to do thing, installed a release. Updated it to current. And then 'changed' it to Rawhide and updated it then. And I had not problems.
Someone posted a script a while back, might have been here, that was supposed to help someone with a disk space problem by doing the update a little at a time. IIRC it was for a release upgrade but I don't see why it would not work here.
i have buckets of disk space -- i accepted the default disk partitioning so i have one honking big root filesystem (>80G). disk space is not an issue.
You had said 'laptop' and they are noted to not have large harddrives. It sounds as if you will not have that problem.
And I would do this in level 3 and not in the GUI level 5. Less things to go wrong that way.
You do know how to get to level three?
yes, dear ... i've done it a time or two in my day. :-)
Sorry. Did not mean to be condescending. ;-) I have seen many 'experts' that only thought that they were experts. Many who were great with a GUI to look at and lost at the CLI. There was a thread a while back that had a 'many years of experience' guy that could not maintain his network because he could not log into the GUI as root. He could have. If he had that much experience. :-)
rday
p.s. still waiting for suggestions as to what to do first if anyone wants to see the current state of the systems before i bork them totally. or i'll just start things rolling and you'll hear the angry shrieking at some point later this afternoon.
I don't know about the bork part. I really do believe that most 'problems' are self inflicted. Third party site packages is a big one. Odd hardware is another big one. By 'odd' I mean not well supported.
Good luck.