Date: Wed, 29 Oct 2008 19:28:21 +0000 From: pwn <pwnedomina@gmail.com> To: Jerry McAllister <jerrymc@msu.edu> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd installation order Message-ID: <4908B955.4050409@gmail.com> In-Reply-To: <20081029190834.GC8360@gizmo.acns.msu.edu> References: <4908687B.7020105@gmail.com> <20081029165518.GB7985@gizmo.acns.msu.edu> <4908A3B1.4070309@gmail.com> <20081029181149.GB8360@gizmo.acns.msu.edu> <4908ADD4.90000@gmail.com> <20081029190834.GC8360@gizmo.acns.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Jerry McAllister escreveu: > On Wed, Oct 29, 2008 at 06:39:16PM +0000, pwn wrote: > > >> Jerry McAllister escreveu: >> >>> On Wed, Oct 29, 2008 at 05:56:01PM +0000, pwn wrote: >>> >>> >>> >>>> Jerry McAllister escreveu: >>>> >>>> >>>>> On Wed, Oct 29, 2008 at 01:43:23PM +0000, pwn wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> immediately after the installation of FreeBSD what steps should be >>>>>> performed by order >>>>>> 1 - Configuring the FreeBSD Kernel >>>>>> 2 - The Cutting Edge >>>>>> 3 - Updating FreeBSD >>>>>> >>>>>> Is this the proper order? >>>>>> >>>>>> >>>>>> >>>>> I would say, first update FreeBSD src and rebuild. >>>>> Then update the ports tree >>>>> Then, if you must, configure a custom kernel - or if >>>>> nothing is critical, just skip that. >>>>> >>>>> Then, install what ports you want and start running. >>>>> >>>>> As for cutting edge, do you mean tracking CURRENT? >>>>> If so, if you are using it to get in on FreeBSD development, then >>>>> do that now and daily. If it is a server for something, then don't >>>>> do that. Just periodically or if some important patch comes put, pull >>>>> in the latest security fixes with update. >>>>> >>>>> >>>>> ////jerry >>>>> >>>>> >>>>> >>>> just to clarify >>>> >>>> I would say, first update FreeBSD src and rebuild. Then update the ports >>>> tree >>>> Re:both this task can be done using csup or cvsup and using the samples >>>> provided in /usr/share/examples/cvsup/ >>>> >>>> >>> Yup. That is what I use. >>> >>> >>> >>>> Then, if you must, configure a custom kernel >>>> Re:(taking a look on hardware and editing generic for example) >>>> >>>> >>> Unless you are running something where absolute maximum performance >>> is critical, don't bother removing things from the kernel. Just >>> limit customizing to adding those things you need that are not >>> in by default - some drivers, maybe. >>> >>> >>> >>>> As for cutting edge, do you mean tracking CURRENT? >>>> Re:yes, but i dont want get in on FreeBSD dev team, so i guess STABLE is >>>> enought. >>>> >>>> >>>> >>> So, yup. You seem to have it. >>> >>> ////jerry >>> >>> >> on this page >> http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html >> it says: >> Tip: By default, when you build a custom kernel, all kernel modules will >> be rebuilt as well. If you want to update a kernel faster or to build >> only custom modules, you should edit /etc/make.conf before starting to >> build the kernel: >> > > It would take more time to edit /etc/make.conf than you would > save in the kernel build. If you are doing lots of kernel > builds while doing development, maybe then this would be worthwhile, > but kernel builds do not take enough time on modern machines to > bother speeding them up trivial amounts. Basically, this is > saying you can fix things up so that it only builds those modules > that you are changing when you do a rebuild and skips the others. > > This is not relevant to general system performance, just kernel > builds. > > ////jerry > i got it =), although, imho kernel builds always affect system performance.(maybe not in general) i was just asking myself a away for simplify at extreme this tasks that sometime can take many time, i guess after configure FreeBSD on a machine i should copy some configuration files like, /etc/make.conf and a custom kernel in attempt to avoid repetitive tasks. > >> isnt enought editing the configuration file? part of the devices listed >> there use modules that do not interest me which can i delete or comment, >> why the use of /etc/make.conf ? >> also, its possible to automate all this pos-installation tasks in order >> to get things running fast and optimized? (i know /etc/make.conf can be >> used for this) but there are other methods that require spendless time? >> >> >>> >>> >>>> >>>> >>>>> >>>>> >>>>>> there is some set of rules to be followed post-installation? >>>>>> since, i do not find any reference mentioning the order that should be >>>>>> followed immediately after installation i would like to be informed if >>>>>> possible what will be the proper order to facilitate the maintenance of >>>>>> the operating system and the installation of new applications without >>>>>> conflicts or problems with ports. >>>>>> thank you. >>>>>> >>>>>> _______________________________________________ >>>>>> freebsd-questions@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-questions-unsubscribe@freebsd.org" >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>> >>> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4908B955.4050409>