8 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
2. Solaris
Hi Guys,
I am getting into patching activity now a days.
I had already done kernel upgrade through LU.
My doubt is if i had to install 3 patches to get my system to current available patch level, can i directly patch one by one on an inactive LU and once done i can activate it later on
or... (3 Replies)
Discussion started by: Rockyc3400
3 Replies
3. Hardware
Hi,
I would like to ask related to video graphics driver specifically the AMD (radeon HD 7000 series) or had someone with the same experience or problem that im currently experiencing and willing to share some info. I understand that the kernel is self contain it will not affect the installed... (3 Replies)
Discussion started by: jao_madn
3 Replies
4. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
5. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
6. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
7. Red Hat
Hello,
How to upgrade kernel from 2.4 to 2.6. Currently i am using rhel3 i want to upgrade it to 2.6
Please provide me the steps.
Prashant (1 Reply)
Discussion started by: prashant_ohol
1 Replies
8. UNIX for Dummies Questions & Answers
Hi everyone,
I am trying to have a second kernel in my Red hat 2.4.18.
I downloaded the 2.4.9 version and did all the extract and stuff. when I run the command make bzImage I get the following error:
devlist.h:6931: __devices_b1b3 causes a section type conflict
> devlist.h:6934:... (1 Reply)
Discussion started by: bashirpopal
1 Replies
LEARN ABOUT CENTOS
redhat-upgrade-tool-cli
REDHAT-UPGRADE-TOOL(8) redhat-upgrade-tool User Manual REDHAT-UPGRADE-TOOL(8)
NAME
redhat-upgrade-tool - Red Hat Upgrade tool
SYNOPSIS
redhat-upgrade-tool [OPTIONS] SOURCE
DESCRIPTION
redhat-upgrade-tool is the Red Hat Upgrade tool.
The redhat-upgrade-tool client runs on the system to be upgraded. It determines what packages are needed for upgrade and gathers them from
the source(s) given. It also fetches and sets up the boot images needed to run the upgrade and sets up the system to perform the upgrade at
next boot.
The actual upgrade takes place when the system is rebooted, using the boot images set up by redhat-upgrade-tool. The upgrade initrd starts
the existing system (mostly) as normal, lets it mount all the local filesystems, then starts the upgrade.
When the upgrade finishes, it reboots the system into the newly-upgraded OS.
OPTIONS
Optional arguments
-h, --help
Show a help message and exit.
-v, --verbose
Print more info.
-d, --debug
Print lots of debugging info.
--debuglog DEBUGLOG
Write debugging output to the given file. Defaults to /var/log/redhat-upgrade-tool.log.
--reboot
Automatically reboot to start the upgrade when ready.
SOURCE
These options tell redhat-upgrade-tool where to look for the packages and boot images needed to run the upgrade. At least one of these
options is required.
--device [DEV]
Device or mountpoint of mounted install media. If DEV is omitted, redhat-upgrade-tool will scan all currently-mounted removable devices
(USB disks, optical media, etc.)
--iso ISO
Installation image file.
--network VERSION
Online repos matching VERSION (a number or "rawhide")
Multiple sources may be used, if desired.
Additional options for --network
--enablerepo REPOID
Enable one or more repos (wildcards allowed).
--disablerepo REPOID
Disable one or more repos (wildcards allowed).
--addrepo REPOID=[@]URL
Add the repo at URL. Prefix URL with @ to indicate that the URL is a mirrorlist.
--instrepo REPOID
Get upgrader boot images from the repo named REPOID. The repo must contain a valid .treeinfo file which points to the location of
usable kernel and upgrade images.
Cleanup commands
--resetbootloader
Remove any modifications made to bootloader configuration.
--clean
Clean up everything written by redhat-upgrade-tool.
EXAMPLES
redhat-upgrade-tool --network 7.0 --instrepo <repo URL>
Upgrade to RHEL 7.0 by downloading all needed packages and data from the specified repository.
redhat-upgrade-tool --device --network 7.0
Upgrade to RHEL 7.0 using install media mounted somewhere on the system, fetching updates from the network if needed.
EXIT STATUS
0
Success.
1
Cancelled by user, failure writing files to disk, or other unknown error
2
Failed to download/copy files from the given SOURCE
3
RPM upgrade transaction test failed
BUGS
The --iso image must be on a filesystem listed in /etc/fstab.
AUTHORS
Will Woods <wwoods@redhat.com>
redhat-upgrade-tool 11/08/2013 REDHAT-UPGRADE-TOOL(8)
