Unlike Red Hat Enterprise Linux versions 2.1 and 3, there is no kernel-source package in the Red Hat Enterprise Linux 4 distribution. It was deemed redundant to provide a kernel-source package and a kernel .src.rpm package at the same time. Users that require access to the kernel sources can find them in the kernel.src.rpm file.
In Red Hat Enterprise Linux 4, The kernel-devel package includes the kernel headers files and you no longer require the kernel source package to build a third party kernel module. To install the kernel-devel package run the following command as root user in a terminal:
#up2date kernel-devel
A full source tree is not required in order to build modules against the current kernel you are using. You can simply point your Makefile to /lib/modules/`uname -r`/build. A more detailed explanation can also be found in the Release Notes. » Read more
John Halamka, CIO of Harvard Medical School and Beth Israel Deaconess Medical Center, was one of the keynote speakers at this summer’s Red Hat Summit. In this video, he explains how open source is critical to the healthcare industry and talks a little about his implanted RFID chip. Learn more about how Beth Israel saved $200,000 and reduced downtime to nearly zero.
Question: I got an error that stated: ‘error code 91: Red Hat software management exhausted’ what do I do?
Answer: This error is most commonly received when you are trying to use activation keys to connect a system profile to Red Hat Network (RHN) but you have exhausted all available management entitlements.
You would need to purchase additional Management level entitlements if you wish to continue using activation keys. Generally you will not get this error when using the up2date –register command unless you have previously created an activation key and designated it as the universal default key on your account. If you previously used an activation key flagged as the universal default, you would need to update the status on that Activation Key before you could create new profiles using the up2date –register command. » Read more
Guvnor is the business rules management system in Drools 5. When you deploy it out of the box, you get an unsecured web application that stores data in Jackrabbit’s embedded Derby database.
This two-part article explains how to tune Guvnor deployed on JBoss Application Server 4.2.3. (If you missed the first half of the series, catch up in our archives.)This means that we will use the container’s configuration files and security infrastructure. This installment covers enabling password validation based on an OpenLDAP server, moving from the default data repository, and enabling SSL for better security. » Read more
Yes, to achieve this, pass the shared disk with the w! option.
For example in /etc/xen/<config file for vm> do the following:
disk = [ "file:/var/lib/xen/images/hostOS.img,hda,w""file:/var/lib/xen/images/qdisk.img,sda,w!"
Make the setting, then boot up all nodes. Create qdisk fs, then check that all nodes can read the qdisk fs:
$ mkqdisk -L
Guvnor is the business rules management system in Drools 5. When you deploy it out of the box, you get an unsecured web application that stores data in Jackrabbit’s embedded Derby database.
The first half of this series explains how to tune Guvnor deployed on JBoss Application Server 4.2.3. This means that we will use the container’s configuration files and security infrastructure. We will cover enabling password validation based on an OpenLDAP server, moving from the default data repository, and enabling SSL for better security in part 2. » Read more
First, make sure that you have downloaded the correct files. For each distribution there are binary files and source files. To complete an installation the four binary files for a particular distribution are required.
Simply burning these files to CD as files will result in a single file being burnt to CD with a .iso extension. If this occurs your disks will not be bootable. The files available from Red Hat Network (RHN) are disk images and need to be burned to CD as an image.
Your burning software will extract the files from the .iso and burn them to CD. See your specific burning software documentation for more information on how to burn images to CD.
To check if you have burned each image correctly simply examine the contents of the CD. Instead of a single .iso file the disk should contain multiple files and directories.
We’ve had some URLs of interest just sitting around the editorial desk. Now it’s Friday and time to share with you:
