On Sat, Aug 05, 2000 at 07:30:34AM +0800, John Summerfield wrote:
mkkickstart is for cloning the same release; it does not cope well with
upgrades where packages get renamed, split up differently or otherwise
reoganised.
Exactly. Thats what rpm is for.
IMHO, implementing much more flexible
On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
On Sat, Aug 05, 2000 at 07:30:34AM +0800, John Summerfield wrote:
mkkickstart is for cloning the same release; it does not cope well with
upgrades where packages get renamed, split up differently or otherwise
reoganised.
Exactly. Thats what
Hoi Pekka,
I should have phrased my point better. Thanks for point that out. To make it
short (more elaboration below):
Instead of hard-coding the information about package replacements and
package importance into an update-tool, it could be put into the package
header and rpm should be able to
On Sat, Aug 05, 2000 at 04:49:49PM +0300, Pekka Savola wrote:
Instead of hard-coding the information about package replacements and
package importance into an update-tool, it could be put into the package
header and rpm should be able to read and *use* that information for the
"Freshen"
On Sat, Aug 05, 2000 at 09:50:21AM -0400, Trond Eivind Glomsrød wrote:
Package: samba-common
Depends: some-package (=3D 1.2.3) || some-other-package (=3D 4.5.6)
Replaces: samba
You could do that by having a virtual package provided by multiple
packages (e.g. MTA)
I think that
On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
But thats exactly the other way 'round! *You* have to know that OpenSSH is
the new ssh software and then rpm will do the right thing. However, what I
would to like to see in rpm is something like "here are your pakets, update
as much as you can" and
On Fri, 4 Aug 2000, Pekka Savola wrote:
On Thu, 3 Aug 2000, Jag wrote:
You can do this with kickstart. On all your machines install the initrd
and vmlinux from the net boot disk, add a lilo entry for reinstall that
uses them and include an
On Fri, 04 Aug 2000, Ulrich Kiermayr wrote:
Hmm, would be usable but I think of two things:
1. It would be cute to have a script line mkkickstart which generates the
config for an Upgrade (easy i think)
2. One might have to make sure if there is enough disk-space for the
upgrade,
On Fri, 4 Aug 2000, Pekka Savola wrote:
Hmm, would be usable but I think of two things:
1. It would be cute to have a script line mkkickstart which generates the
config for an Upgrade (easy i think)
mkkickstart is for cloning the same release; it does not cope well with
upgrades
It is certainly possible, but you'd have to skip the kernel
upgrades, and be very careful. init will get upgraded on disk,
but the running one in memory will be older. This should only be
attempted in single user mode because the C libaries will get
updated as well as all critical
On Wed, 2 Aug 2000, J Kinsley wrote:
However, I did not use any
'automagic' means to do this. I upgraded each individual package
manually using Midnight Commander (MC). It took most of an evening
to install the packages and retweak all the configs,
On Wed, 2 Aug 2000, Ulrich Kiermayr
On Wed, 2 Aug 2000, Ulrich Kiermayr wrote:
Hello!
A Question: is it possible to do an upgrade (e.g. 6.1 - 6.2) while the
system is up and running.
I could do an rpm -F /mnt/cdrom/RedHat/RPM/*, but this might break some
dependencies (of packages which got split up for example)
It is
On Wed, 2 Aug 2000, Nitebirdz wrote:
I've done it in a couple of cases, but I suppose it is wise to actually
take the server out of production, perform the upgrade, make sure
everything works fine and then put it back in production. Nevertheless,
in those cases where I had to do it, I didn't
On Thu, 03 Aug 2000, Pekka Savola wrote:
On Wed, 2 Aug 2000, Nitebirdz wrote:
I think Red Hat Linux definitely needs some tools to upgrade a live
system. The main reason for this is that you can do it remotely. I can't
see anything more annoying than having to walk through every Linux
On Thu, 3 Aug 2000, Pekka Savola wrote:
Just my 0.02$;
I think Red Hat Linux definitely needs some tools to upgrade a live
system. The main reason for this is that you can do it remotely. I can't
see anything more annoying than having to walk through every Linux
workstation / server
On Thu, 3 Aug 2000, Jag wrote:
On Thu, 03 Aug 2000, Pekka Savola wrote:
On Wed, 2 Aug 2000, Nitebirdz wrote:
I think Red Hat Linux definitely needs some tools to upgrade a live
system. The main reason for this is that you can do it remotely. I can't
see anything more annoying
On Thu, 3 Aug 2000, Jag wrote:
You can do this with kickstart. On all your machines install the initrd
and vmlinux from the net boot disk, add a lilo entry for reinstall that
uses them and include an
append="ks=nfs:nfs.server.domainname:/path/to/kickstartsconfigs" line
for that entry. Then
On Wed, 2 Aug 2000, Ulrich Kiermayr wrote:
Date: Wed, 2 Aug 2000 11:02:25 +0200 (CEST)
From: Ulrich Kiermayr [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Upgrade distribution while system is running
Hello!
A Question: is it possible to do an upgrade (e.g. 6.1 - 6.2) while the
system is up
On Wed, 2 Aug 2000, J Kinsley wrote:
Date: Wed, 2 Aug 2000 18:07:21 -0400 (EDT)
From: J Kinsley [EMAIL PROTECTED]
To: Ulrich Kiermayr [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Upgrade distribution while system is running
I upgraded from RedHat 4.? to 5.0 on a live system and only
Hello!
A Question: is it possible to do an upgrade (e.g. 6.1 - 6.2) while the
system is up and running.
I could do an rpm -F /mnt/cdrom/RedHat/RPM/*, but this might break some
dependencies (of packages which got split up for example)
It is because i want to reduce downtimes due to upgrades
20 matches
Mail list logo
