When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
I am using CentOS 5.2 with GRUB booting a software RAID configuration. The first disk is md0 and is mirrored across sda1 and sdb1.I manually re-installed grub using grub-install and the machine will no longer boot off of the HD. The grub menu comes up, I can select my kernel the machine then jumps to loading the initrd and hangs.It will go no further. I have a live DVD that can boot from the HD. If I use that to first boot from the DVD, then specifiy the HD, it shows the same grub menu and then the machine boots fine w/o the initrd hang.I have tried re-installing grub but not been able to get the machine to work again w/o the DVD.
I've had a Centos 5.3 zimbra mailserver set up for about 3 months now.Every 7-10 days or so, the system will do a kernel panic and I've been putting off its resolution due to other matters.I'm now ready to look into it but I have two issues :
1) No logs.
So far, I've manually rebooted when a kernel panic occured and could look at the panic printout and write down relevant info. But since I wanted more info than I had written down, I went hunting in the logs for the kernel panic event (one happened earlier today) but, to my surprise, I noticed the system doesn't log the kernel panic at all. Kdump is currently disabled as I'd like to keep all available memory available to the system but I was under the impression it would log the kernel panic message regardless but would simply leave out more advanced diagnostic information.How would I make sure the kernel panic is logged so I can have more info about it ?
2) The actual panic.Here's a snippet of what's appearing when the kernel panics :
I've also seen f793bee4 instead of the highlighted part above but everything else is always the same from the times I've seen (as I haven't always had the chance to be around when a panic occured).I'm looking further into it at this point but early research seem to indicate this could be a memory issue. I'll run memtest next weekend to check that out (since I don't want to take the system offline for any length of time during office hours) but people here might have other theories based on what I've put up so far. The system has all of the latest patches and updates and is running only what I need as far as software goes (zimbra server + prerequisites, x + GNOME (not loaded on startup), firefox and vnc for windows RDP access). My system also uses a software RAID1 array (boot = md0 and / = md2 with swap files not being mirrored as there's no need to).
PS : In order to further troublehsoot by myself before posting here, I've tried to enable kdump to see if kdump is the culprit for the missing logs but I'm also having an issue with it. I'm getting a "No kdump initial ramdisk found" and "mkdumprd: failed to make kdump initrd" messages at startup. I'm thinking this might be because of my raid array ? I've found an old bug report regarding one of those error messages on centos 5.2 but it was supposedly fixed in the 30 version by RH and I'm using the latest one (56).
now i want to remove to due to upgrade the system using the latest centos system, but now i cant remove it, try to format my desktop also cannot. when im entering the bios its show GNU GRUB. im also need to install xp for my new study project..
I don't want to disable it... I want to completely remove it, so it doesn't sneak back later. I don't see a yum --removerepo and Googling leads to instructions to disable.
I have done an initial CentOS install. I've now found out that the driver that I want to install (nVidia for GPU support) will not support the Xen feature that I installed. I'd like to avoid having to re-install completely. Is there a way to remove the Xen support that is documented somewhere?
If I do a fresh 'netinst' of CentOS 5.4 x64 on a server, what is the correct way to verify that no 32-bit packages were installed or mixed in with x64? Also can someone tell me if it is safe to remove those 32-bit RPM packages? I searched the Wiki for 'Post Install Tips' and could not find anything there or on Google.
I am using CentOS 5.5. After upgrading i have at present 4 kernels in the menu.lst.If i try to remove any kernel, 2.6.18-194.3.1.el5.i686 via Package Manager, i am told that i am removing critical software for system functionality etc. How delete older kernels?
I have installed CentOS 5.2 and tried to click on the application => add/remove software
I get some error saying Unable to retrieve software information.
Cannot retrieve repository metadata (repomd.xml) for repositoryc5-media.
What I did wat disable the repository manager and unchecked c5-media.
This is the only one I can see at the repository manager screen.
Then I restarted application => add/remove software
The screen came out.
But I am expecting a similar screen as CentOS 3 or 4 which display the package management by group of Desktop, Application, Servers, Development, System.
From here I could know what I have installed and what I have not.
I am currently running the xen (64 bit) kernel, but want to move to the non xen kernel(64 bit) while retaining my carefully crafted system. I tried this once before by unticking the "virtualisation" and it removed the xen kernel, leaving me with nothing to boot from.
I'm installing CentOS from the netinstall in Virtualbox now. I was about to post a different thread because Anaconda kept crashing on me. Whenever I would try to uncheck Gnome, clicking next would always fail. I really don't want Gnome, but I need to get the VM installed, so I just accepted the default software selection. (It's not an iso problem either because I originally tried the DVD as well.)I've been using Linux for several years, but I need to use a GUI-less server. I found some instructions on how to disable X by entering runlevel 3, but that's not what I want to do. Is there a meta-package that I can remove "yum remove" and it will remove all the GUI dependencies, or perhaps something like "yum groupremove"?
The reason I want to delete the LUKS password is simply that I do not want to have to put it in for each server just to get the system to boot. I am planning to cluster the servers as well and like I said before I don't want to put the password in each time since they won't be running all the time.
I installed Xen package on a CentOS 5.3 x86_64. After a reboot I found the virbr0 bridge configured by default. I guess that "virbr0" is the name used conventionally by Red Hat to indicate the first bridge. In other Xen installations usually it would have named "xenbr0". I did not find in which configuration or script file it was created. How is it possible to remove that "virbr0" bridge?
What is 'java-1.4.2-gcj-compact package' Is this a JDK or just JRE?
I want to remove 'java-1.4.2-gcj-compact' package and install sun's JDK1.6. But lots of other packages depends on 'java-1.4.2-gcj-compact'. How should I go ahead.
I'm using x86_64 CentOS 5.4. There are some 32bit applications on my system. Does these applications work on 64bit platform. If not, how can I remove these applications without harming my system.
I'm running CentOS 5.4 in combination with DirectAdmin, and I'm wondering: Is it safe to remove /media and /opt directory?Because those directories /media and /opt are empty.
Running # lsmod | grep -e " 0 " | wc on one of my servers running CentOS 5.5 (64 bits) reports me 32 unused modules, I mean, modules with 0 references. Am I wrong interpreting these results? If I'm not, how can I automatically clean those unused modules (i.e not manually running modprobe -r ). Some years ago there used to be a daemon called kerneld who was in charge of that task, right? What's CentOS new equivalent?
I'm trying to do a disk upgrade on some servers. They are using LVM with DRBD on top and each LVM volume contains a Xen image. I have already created identical volumes on another volume group, copied the data and pointed DRBD to the new source (Which seems to have worked).
What I am unsure of is how to safely remove the disks. The disks are an Areca Raid 1 array and support hotswap. Can I just pull them out of the machine or is some sort of command needed to tell LVM or the kernel to disconnect from the physical array device? Is removing the raid array from the Areca management GUI first a good idea?
I heard somewhere that by creating custom initrd image and default compiled kernel image, we can do PXE linux installation. can anyone please guide me 'what content will be placed inside initrd?'I know the process of creating custom initrd file .
I would like to remove openldap from my Centos home-server..
Centos offers me:
Quote:
Removing: openldap i386 2.3.43-12.el5_5.2 installed 592 k openldap x86_64 2.3.43-12.el5_5.2 installed 598 k
[Code]...
..obviously I'll not remove openldap by this operation.. but my question is: there is another way to remove a single package with yum without "consequences"?
from [URL] How to remove them completely? The ipw2200 driver complains that it could not agree with certain symbols in ieee80211 module. Before taking another route, I would like to know how to completely remove the files installed by these driver packages.
How to remove package with his configuration files. rpm -e doesnt delete any configuration files, is there any similar command to debians apt-get --purge ?
