Just because you have a problem doesn't mean that the entire product is a
"bug ridden mess." There is little diffence between 6.0 and 6.1.
Please tone down your rhetoric.
To upgrade your packages simply boot into Linux, login as root, do an `init
1` to switch to single user mode, mount your redhat 6.1 cdrom, cd
/mnt/cdrom/RedHat/RPMS, and do a `rpm -Uvh --nodeps --force *.rpm. This will
upgrade all your packages.
Redhat 6.1 is nearly the same as Redhat 6.0, the only differences are about
fifty security patches. After you install you should goto
http://redhat.com/support and download and install the patches for redhat
6.1.
Have fun...
Jeremy Katz wrote:
> On Wed, 20 Oct 1999, Matt Nelson wrote:
>
> > The Red Hat 6.1 installer is a bug-ridden mess.
> >
> > This is an update to my original post to redhat-list regarding problems
> > with upgrading from Red Hat 6.0 to Red Hat 6.1.
> [some snipping]
> > It was suggested to me that the installer has problems with NTFS
> > partitions, and that I should change the ID of /dev/hda1 from 7 to 17,
> > do the upgrade, then switch it back to 7.
>
> Yes, there is a bug in the installer if you have an NTFS partition.
> This has been pretty well confirmed at this point.
>
> > Well, this morning I tried the workaround. here's what happened:
> >
> > Graphical Install: The system got past the "searching for existing
> > Red Hat installations" screen, but hung on
> > "Finding packages to upgrade".
> > Text Install: same thing.
> >
> > I switched to VC1, and saw some error messages:
> >
> > error opening security policy file
> > /usr/X11R6/lib/X11/xserver/SecurityPolicy
>
> This message is due to the fact that there is not a full install of
> XFree in order to conserve space in the image.
>
> > which was followed by a python traceback, the last entry of which was:
> >
> > /usr/lib/python1.5/site-packages/todo.py line 1155 in
> > upgradeFindPackages
> >
> > out of curiosity, i switched to VC2 to check what was mounted:
> >
> > bash# mount
> > /dev/root / ext2 rw 0 0
> > /proc /proc proc rw 0 0
> > /dev/pts /dev/pts devpts rw 0 0
> > /tmp/cdrom /mnt/source iso9660 ro 0 0
> > /tmp/hdb1 /mnt/sysimage/boot ext2 rw 0 0
> > /proc /mnt/sysimage/proc proc rw 0 0
> >
> > odd thing, my root partition isn't mounted anywhere; no wonder it
> > couldn't find any packages...
> >
> > By the way, will it give me a choice of which installation to upgrade?
> > I have two different Linux installations installed, one on /dev/hdb3 and
> > another on /dev/hdb4...
>
> It has asked me which installation I wanted to upgrade every time I've
> upgraded a machine with multiple installs on it. Which I've done quite
> a few times from the first beta onward. The strange thing from the
> listing of what you have mounted is it shows /boot as being mounted...
> if that's the correct partition for /boot there is no way the installer
> would have figured that out without looking at the /etc/fstab for the
> actual root of the system. I seem to remember that even on my laptop
> (which only has one distribution) it still asked if it had located the
> proper filesystem for /. I'm guessing that you hit next quickly without
> realizing it.
>
> Jeremy
>
> --
> Jeremy Katz http://linuxpower.org
> Personal: [EMAIL PROTECTED]
> School: [EMAIL PROTECTED]
>
> QOTD:
> CCI Power 6/40: one board, a megabyte of cache, and an attitude...
>
> --
> To unsubscribe:
> mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
