From: "Willem van der Walt<vdwaltw@health.gov.za>" <vdwaltw@health.gov.za>
To: <blinux-list@redhat.com>
Cc: "John J. Boyer" <director@chpi.org>
Subject: Re: Upgrading from RH 7.1 to 7.2
Date: Thu, 6 Dec 2001 08:48:19 +0500 (GMT-5) [thread overview]
Message-ID: <Pine.LNX.4.33.0112060838310.24859-100000@rh.health.gov.za> (raw)
In-Reply-To: <Pine.LNX.4.33.0112051531460.32505-100000@xanadu.home>
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
>
next prev parent 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> [this message]
` Brent Harding
` Willem van der Walt<vdwaltw@health.gov.za>
` Brent Harding
` 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=Pine.LNX.4.33.0112060838310.24859-100000@rh.health.gov.za \
--to=vdwaltw@health.gov.za \
--cc=blinux-list@redhat.com \
--cc=director@chpi.org \
/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).