[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: [rhn-users] Remote (telnet) kernel updates possible?
- From: "DB" <rhn-list catalpaweb com>
- To: <rhn-users redhat com>
- Subject: RE: [rhn-users] Remote (telnet) kernel updates possible?
- Date: Tue, 29 Apr 2003 15:04:59 -0400
Thanks Erik,
DB
-----Original Message-----
From: rhn-users-admin redhat com [mailto:rhn-users-admin redhat com]On
Behalf Of Erik McCormick
Sent: Tuesday, April 29, 2003 2:14 PM
To: rhn-users redhat com
Subject: RE: [rhn-users] Remote (telnet) kernel updates possible?
That IP address isn't really relevant to anything. It just updates a
field in the RHN database. I can't actually see a way to edit that on
RHN. I suppose you could rerun the registration process and edit it at
that point. Either way it shouldn't affect your updates.
-----Original Message-----
From: rhn-users-admin redhat com [mailto:rhn-users-admin redhat com] On
Behalf Of DB
Sent: Tuesday, April 29, 2003 1:54 PM
To: rhn-users redhat com
Subject: RE: [rhn-users] Remote (telnet) kernel updates possible?
Thanks Erik,
that brings me to another question - I think I may have messed up the
up2date command - "up2date --register". I'm not sure but I think
up2date
was already set up properly but then I ran "up2date --register" again
yesterday, up2date showed my local IP 127.0.0.0 not my actual IP of the
server - WAN connection. But two weeks ago over 20 packages were
updated
via up2date OK according to rhn site - a linux guru did it for me.
How can I check to see if up2date is set up correctly prior to
attempting an
update more updates?
Thanks for all this great advice guys, this is my first time updating
anything on my OS and want to make sure I'm doing it correctly - the
server
has been live for a while.
DB
-----Original Message-----
From: rhn-users-admin redhat com [mailto:rhn-users-admin redhat com]On
Behalf Of Erik McCormick
Sent: Tuesday, April 29, 2003 1:18 PM
To: rhn-users redhat com
Subject: RE: [rhn-users] Remote (telnet) kernel updates possible?
A few other points here:
>From my understanding of the way RHN works, when you select to apply an
update on the web site, it's simply telling RHN to apply that update the
next time the machine checks in. This would require you to be running
the RHN daemon on your server. But really it's the same thing as
running up2date. If you run up2date manually from the command line, it
will allow you to do the update right away and watch its progress. Both
processes will download the RPM, install the package on your system, and
update the RHN database to reflect that you've installed it.
Updating the kernel should not effect any of the software you mentioned
below. I can't say it WON'T because there are very few sure things in
life, but it really shouldn't. The kinds of things that will break when
you update a Kernel are any modules that you've installed manually by
building them against Kernel source (eg. Network drivers, Sound drivers,
etc). As long as you're within the same major release version (ie.
2.4.x in this case), all of your software should continue to function
normally.
-Erik
-----Original Message-----
From: rhn-users-admin redhat com [mailto:rhn-users-admin redhat com] On
Behalf Of Ed Greshko greshko com
Sent: Tuesday, April 29, 2003 12:52 PM
To: rhn-users redhat com
Subject: RE: [rhn-users] Remote (telnet) kernel updates possible?
On Tue, 29 Apr 2003, DB wrote:
> I'm running qmail and e-commerce software, stats software, etc on
server.
> I'm wondering if by updating the kernel if this would break any
dependencies
> of my installed software. How would I find out prior to?
>
> I guess I should contact all of my software vendors first? Or is the
only
> way to find out, hold breath and click "Apply Errata"?
As was previously mentioned by another kind soul.....
The update of the kernel does not remove the previous kernel. You have
to
manually issue the "rpm" command to remove an old kernel.
If you update and have problems you simply boot the previous kernel.
You
don't even need to remove the new one. Just edit your grub
configuration
to boot the older kernel by default.
Ed
--
SARS - The only virus not spread by Outlook
http://www.shorewall.net/ for all your firewall needs
_______________________________________________
rhn-users mailing list
rhn-users redhat com
https://listman.redhat.com/mailman/listinfo/rhn-users
_______________________________________________
rhn-users mailing list
rhn-users redhat com
https://listman.redhat.com/mailman/listinfo/rhn-users
_______________________________________________
rhn-users mailing list
rhn-users redhat com
https://listman.redhat.com/mailman/listinfo/rhn-users
_______________________________________________
rhn-users mailing list
rhn-users redhat com
https://listman.redhat.com/mailman/listinfo/rhn-users
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]