From: Terje Kvernes <terjekv@math.uio.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Red Hat upgrade over existing LVM
Date: Sat Apr 6 23:13:02 2002 [thread overview]
Message-ID: <wxxelhs3xar.fsf@nommo.uio.no> (raw)
In-Reply-To: <3CAFCEBB.7860B8E4@vtc.edu.hk>
Nick Urbanik <nicku@vtc.edu.hk> writes:
> Terje Kvernes wrote:
>
> > that's one way, the easier way is to either use apt
>
> Does apt work with Red Hat in a usable way? I tried it a long time
> ago, and deleted it.
sort of, just mask out ximian-packages and other stuff you can't
make dependencies for. otherwise it supposedly works well. I have
to admit to using red-carpet mostly myself.
> > or red-carpet to upgrade your distro. with red-carpet, fiddle
> > with /etc/redhat-release, apt has dist-upgrade, I think. I've
> > upgraded two machines from 7.0 -> 7.2 with red-carpet, but I'd
> > advice you to set off a day with this, even if you get the rpms
> > from somewhere besides ximian.
> >
> > I did it as follows: grab the rpms from RH7.2, with the updates,
> > from a local mirror, and dump them to /var/cache/redcarpet, then
> > fiddle with /etc/redhat-release (feel free to install the rpm
> > "redhat-release"), then run red-carpet. things will break and
> > fail now and then, fiddle.
>
> I have used rpmfind --autoupgrade to upgrade from 7.1 to 7.2, and
> that required not a huge amount of manual intervention, but more
> than I want.
hm, haven't tried that.
> I tried using rpmfind to upgrade this machine from 7.2 to 7.2.93,
> but it changed my /lib/ld-linux.so and everything ground to a halt.
ouch. someone[tm] didn't think when they handed you the rpms.
> I had to reboot with init=/sbin/sash to fix it. Now I have created
> a directory /static, containing lots of statically compiled tools,
> including the LVM tools.
I've by habit compiled all the tools statically for a long while
now.
> We really need a rescue disk that supports LVM, RAID, reiserfs and
> ext3. Anyone seen such a beast, or do I have to make it myself?
Gentoo's default kernel supports this, as well as XFS, out of the
box.
> > these days I have a RH7.2-box that has an uptime of about 240
> > days. :)
>
> So you are not yet running a recent kernel?
correct. but only me and my girlfriend can log into it, so
security-wise it doesn't really matter. although I do miss certain
parts of 2.4.18 these days. :)
oh, and yes, the box runs 0.9.1_beta7. which has worked flawlessly
as long as I've kept _far_ away from known bugs. :)
--
Terje
next prev parent reply other threads:[~2002-04-06 23:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 1:08 [linux-lvm] Red Hat upgrade over existing LVM Nick Urbanik
2002-04-06 2:28 ` Terje Kvernes
2002-04-06 15:30 ` Steve Wray
2002-04-06 21:26 ` Terje Kvernes
2002-04-08 2:54 ` Remco Post
2002-04-06 22:47 ` Nick Urbanik
2002-04-06 23:45 ` Steve Wray
2002-04-08 4:04 ` Eduard Bloch
2002-04-06 22:44 ` Nick Urbanik
2002-04-06 23:13 ` Terje Kvernes [this message]
2002-04-07 5:28 ` Luca Berra
2002-04-08 2:07 ` Dirk Heinrichs
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=wxxelhs3xar.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--cc=linux-lvm@sistina.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