Forgot to mention kernel update
Kernel version 2.6.16.9, so I will supply its config file here config-2.6.16.9.txt. Same procedure as before.
Good luck.
Kernel version 2.6.16.9, so I will supply its config file here config-2.6.16.9.txt. Same procedure as before.
Good luck.
Powered by YARPP.
This post is for the users of the great dm-multipath system in Linux, who encounter a major availability problem when attempting a resize of mpath devices (and their partitions), and find themselves scheduling a reboot. This documented is based on a document created by IBM called “Hot Resize Multipath Storage Volume on Linux with SVC”,…
Update to 0.2. Links remain the same. At the moment I cannot host many versions (it’s mostly uncomfortable), but this might change in the future. I have created a GUI cables installer and configurator for L2TP on Linux. I have noticed that there is no GUI solution, so, after this has been brought up, I…
Doesn’t work. It will work fine up to the step where you actually try to active one of the VMware virtual machines. And then your kernel will panic. Works fine without Xen kernel (but without Xen, of course). Pity. Was tested on Centos5.1 64bit. Related posts: A note about VMware-Server machine security VMware experiance –…
This is a rather common knowledge now that on RHEL4 you need to state inside /etc/modprobe.conf the following line, when you want more than one bonding interfaces: options bonding max_bonds=2 Then you attempt to use a trick to address different bonding devices with their name (aka, bond0 and bond1, and maybe bond2, etc), using an…
I got the following error message when attempting to upgrade RPM packages: Oracle Linux 8 introduced a bug with a package called rpm-plugin-selinux (details: rpm-plugin-selinux-4.14.3-28.0.1.el8_9) which prevents RPM packages from being installed correctly, either by dnf/yum or manually. The solution, as shown in this Oracle community forum is to downgrade the package rpm-plugin-selinux like that:…
I’ve had a belief for quite a while now that Linux, unlike other types of systems, was unable to produce any I/O SNMP information. I only recently found out that it was partially true – all production-level distros, such as RedHat (and Centos, for that matter) were unable to produce any output for any SNMP…