所以在一个非常好的主机上有一个传统的CentOS 6.x VPS模板，这个模板被一个100MB / boot分区“卡住”了。 不幸的是，自从4年前产生以来，我们的一台服务器就属于这个类别。 为了获得更多空间的新包/模板，不可能增加/ boot的大小。 切换区域将是一个相当的任务，因为将有新的知识产权和其他模式重新做，所以我们正在寻找替代品。
我们在该服务器上使用CloudLinux，因此内核可能比正常的要大一些。 无论哪种方式，我们被迫将活动内核减less到1，这困扰我，但这是所有可以适应/启动。 问题在于缺less可用于安装新版本内核的空间。
内核debugging*包似乎比标准内核大。 删除它们是否安全？ 如果有一个标准内核的旧版本（潜在地）可用于启动，debugging内核是否对生产有用？
这是一个运行LAMP的多租户生产VPS（KVM）。 我们没有做太多的服务器端的CLI，它主要是ecom + webapps。 如果可以提供某种解决方法的话，它会有内核pipe理。
有了kernel-debug *，你的意思是kernel-debug和kernel-debuginfo，因为这两个软件包是有区别的
Kernel-debuginfo: Provides a executable image of the kernel with all the debug symbols Kernel-debug: Enables some debugging code but not have same debug symbols on it ### Excerpt from RedHat Doc ### The kernel-debug enables the following options on the kernel that are disabled on the default kernel: CONFIG_DEBUG_SLAB Makes kernel do limited verification on memory allocation as well as poisoning memory on free to catch use of freed memory. (performance impact mainly on kmalloc / mfree calls). CONFIG_DEBUG_MUTEXES Allows mutexes semantics violations to be detected and reported. CONFIG_DEBUG_RT_MUTEXES Allows rt mutex semantics violations and rt mutex related deadlocks (lockups) to be detected and reported automatically. CONFIG_DEBUG_RWSEMS Allows read-write semaphore semantics violations to be detected and reported. CONFIG_DEBUG_LOCK_ALLOC This feature will check whether any held lock (spinlock, rwlock, mutex or rwsem) is incorrectly freed by the kernel, via any of the memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), vfree(), etc), whether a live lock is incorrectly reinitialized via spin_lock_init(),mutex_init(),etc, or whether there is any lock held during task exit. CONFIG_PROVE_LOCKING This feature enables the kernel to prove that all locking that occurs in the kernel runtime is mathematically correct: that under no circumstance could an arbitrary (and not yet triggered) combination of observed locking sequences (on an arbitrary number of CPUs, running an arbitrary number of tasks and interrupt contexts) cause a deadlock. CONFIG_DEBUG_VM Turn on extended checks in the virtual memory system (performance impact). CONFIG_DEBUG_SPINLOCK Built SMP to catch missing spinlock initialization and certain other kinds of spinlock errors commonly made. This is best used in conjunction with the NMI watchdog so that spinlock deadlocks are also debuggable. CONFIG_DEBUG_SPINLOCK_SLEEP Various routines which may sleep will become very noisy if they are called with a spinlock held. CONFIG_LOCK_STAT Enables tracking lock contention points ( see /usr/share/doc/kernel-doc/Documentation/lockstat.txt ). CONFIG_XFS_DEBUG Enable XFS debugging features, including ASSERT checks, function wrappers around macros, and extra sanity-checking functions in various code paths (make a huge and slow code). 现在回到你的问题是否可以安全地删除这些？
这些软件包仅用于debugging目的，可能会导致性能下降。因此，它们可以安全地移除，只需要在debugging过程中安装。