public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: Upgrading from RH 7.1 to 7.2
Date: Mon, 10 Dec 2001 14:00:21 -0600	[thread overview]
Message-ID: <3.0.6.32.20011210140021.008e6e20@mail.doorpi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0112100901130.2139-100000@rh.health.gov.za>

Well, don't have a network yet, but maybe some day I can get this machine
on one. 
At 09:05 AM 12/10/01 +0500, you wrote:
>Hi,
>There is a program called up-to-date or uptodate i am not sure.
>I think you need to be registered at redhat to use it.
>There is also a program rpmfind which possibly could identify all packages
>that need upgrading and then download them.
>I would rather try and get hold (by downloading?) the iso images of the 
>two
>cds you will need for the upgrade and get them written onto cds.
>If you have a network at your disposal, you can put these iso images on
>another box and upgrade over the network.
>hth
>Willem
>
>On Thu, 6 Dec 2001, Brent Harding wrote:
>
>> It'd be cool to use ext3, is there a way to upgrade by modem?
>> At 08:48 AM 12/6/01 +0500, you wrote:
>> >Hello,
>> >The config files should be automatically saved in *.rpmsave files by the
>> >upgrading process.  
>> >The main difference between rh-7.1 and 7.2 is the introduction of the ext3
>> >jurnalling file system.
>> >One should considder if it would be werth upgrading
>> >if there are a lot of custom configuration that has been done on 7.1.
>> >Ext3 has more overhead than ext2, but it has the ability to do something
>> >like point-in-time recovery.
>> >
>> >I have done the upgrade on my box to try and get my onboard sound to work
>> >with viavoice.  My lynx.cfg was lost in etc, but my .pinerc in
>> >my home directory was kept.
>> >hth
>> >Willem 
>> >On Wed, 5 Dec 2001, Nicolas Pitre wrote:
>> >
>> >> On Wed, 5 Dec 2001, John J. Boyer wrote:
>> >> 
>> >> > Hello,
>> >> > How do I upgrade from Redhat 7.1 to 7.2 without losing my
configuration
>> >> > files or my brltty driver?
>> >> 
>> >> Performing an "upgrade" with the Red HAT 7.2 disk should preserve
most of 
>> >> your customisations.  To what degree is this reliable I can't tell.
>> >> 
>> >> 
>> >> Nicolas
>> >> 
>> >> 
>> >> 
>> >> _______________________________________________
>> >> Blinux-list mailing list
>> >> Blinux-list@redhat.com
>> >> https://listman.redhat.com/mailman/listinfo/blinux-list
>> >> 
>> >
>> >
>> >
>> >_______________________________________________
>> >Blinux-list mailing list
>> >Blinux-list@redhat.com
>> >https://listman.redhat.com/mailman/listinfo/blinux-list
>> >
>> >
>> 
>> 
>> 
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>> 
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>




  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John J. Boyer
 ` Nicolas Pitre
   ` Willem van der Walt<vdwaltw@health.gov.za>
     ` Brent Harding
       ` Willem van der Walt<vdwaltw@health.gov.za>
         ` Brent Harding [this message]
 ` Janina Sajka
 ` Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.6.32.20011210140021.008e6e20@mail.doorpi.net \
    --to=bharding@doorpi.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).