Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Each kernel image will take several mb's *at most*, usually it will be around 2,5-5mb for a 2.6.x kernel. 2.4 kernels are smaller though most distros don't use them any longer. If you also store the system.map files that will add around 1.5mb for each kernel you install.
So, 100mb is plenty if you are careful enough (or your package manager) to uninstall those kernels that you will no longer use. When updating a kernel it's always a good idea to keep at least another one that you know is working, just in case that the new kernel doesn't boot for some reason. Some people use different kernels for different purposes as well (real time stuff, experimental patchsets, testing, etc).
Wait, what do you think RAID 6 has to do with the size of your /boot partition?
And thanks a lot, jerk. I was in the middle of a thread when that happened. :/
Re-reading this thread has me making a few clairifications.
To start with, I was setting up new RAID volumes on the on the server, wanted to keep the OS on it's own. My question was in relation to the volume that would be used to boot the OS; for the OS and core server software. This volume is 100GB and I left the remaining space of the array not initialized (for now). I was figuring that the WebServer and DB's would be installed in the Uninitialized space when I get there.
When I installed RHEL 5.3 Server, the boot partition on the first volume (VolumeGroup00) was left at the default 101MB, the rest is where I installed and patched the OS.
Does this make more sense now? Am I heading the right direction with the configuration?
*gently clicks "Submit Reply" in hopes of not bringing down the forum again*
Last edited by cyninger; 08-13-2009 at 03:21 PM.
Reason: specified "Server" for the RHEL
All sounds good to me; was just wondering what you meant by that since RAID operates totally underneath the filesystem. 101 MB should be fine; my /boot's 200 MB but only using 22 MB right now. Assuming Red Hat has the same stuff as Fedora (reasonable), it'll automatically trim you to the current and past two package management-installed kernels, so it should never get anywhere near capacity.