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 SUNOS
asupgrade
asupgrade(1m) Application Server Utility asupgrade(1m)
NAME
asupgrade - migrates the configuration of a previously installed Sun Java System Application Server
SYNOPSIS
asupgrade [-c | --console] [-V --version] [-h | --help]-s | -source applicationserver7.x_installation -t --target application-
server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p |
--capwdfile CA_password_filepath]
Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application
Server installation. If the domain contains information about a deployed application and the installed application components do not agree
with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime bina-
ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.
Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server install-
er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.
Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged
into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.
You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide the pass-
words for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys and certificates are con-
verted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
the items that could not be migrated.
OPTIONS
-c --console launches the upgrade command line utility.
-V--version displays the version of the UpgradeTool.
-h--help displays the arguments for launching the UpgradeTool.
-s--source identifies the installation directory for Sun Java System Application Server 7.
-t--target identifies the installation directory for Sun Java System Application Server 8.
-d--domain identifies the destination domain name for the migrated certificates.
-n--nsspwdfile identifies the path to the NSS password file.
-j--jkspwdfile identifies the path to the JKS password file.
-p--capwdfile identifies the path to the CA certificate password file.
EXAMPLES
Example 1: Using asupgrade
example% upgrade -s /home/sunas7 -t /home/sunas8
SEE ALSO
asmigrate(1M)
Sun Java System Application Server March 2004 asupgrade(1m)
