Date: Thu, 17 Jul 2008 22:43:16 +0300 From: Manolis Kiagias <sonic2000gr@gmail.com> To: Jonah Sinowitz <jgsinowitz@gmail.com> Cc: "freebsd-doc@freebsd.org" <freebsd-doc@freebsd.org>, Tim Kellers <kellers@njit.edu> Subject: Re: Chapter 23 Message-ID: <487FA0D4.60405@gmail.com> In-Reply-To: <eb1e531d0807171222y11af328cx9a4b76f36b3f6c6b@mail.gmail.com> References: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com> <487F9926.2020703@gmail.com> <eb1e531d0807171222y11af328cx9a4b76f36b3f6c6b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonah Sinowitz wrote: > Dear Manolis, > > Thanks for the quick response. > > In the introductory course I took, we did *exactly *as you said: we > downloaded the release CD and then worked through the equivalent of > the first few chapters of the Handbook. We then moved very very > quickly to the "Common Tasks" section of the Handbook, "Chapter 8", > and configured the kernel. > After this experience, my thought was -- /if /"Configuring the FreeBSD > Kernel" is a common task, so are many of those tasks listed in "The > Cutting Edge". > > Does this make sense? > > Best, > Jonah Well, it depends on the audience. Many people choose to stay with -RELEASE (especially on servers), others run -STABLE on their desktops or when -RELEASE has a problem with their hardware. People who are actively developing (low level) stuff usually run CURRENT. I certainly know of people who compile CURRENT daily... Creating a custom kernel is a relatively easy task, once you grasp the basics, but compiling the rest of the system is something that a lot of people may never need. Enthusiasts will do it anyway, just to learn how :) I suggest you give -STABLE a try if you are so inclined, it is a good learning experience.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?487FA0D4.60405>