Date: Fri, 2 Aug 2002 10:29:43 -0600 (CST) From: Ryan Thompson <ryan@sasknow.com> To: soheil h <soheil_h_y@hotmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: MAKING KERNEL ( emergency ) Message-ID: <20020802101340.N47960-100000@ren.sasknow.com> In-Reply-To: <F168x4FR0rmTIVvLVKi00008cc1@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
soheil h wrote to ryan@sasknow.com: > Hi list > as Ryan said i do a fresh compile and make no change to GENERIC conf. file > and the sources it takes errors ( syntax error , assembler error ,...) like > that i send before > how can i download the source code of FreeBSD4.4 release > help me > thanx Many prefer cvsup for this. (/usr/ports/net/cvsup, or cvsup-without-gui). See http://www.freebsd.org/handbook/cvsup.html To get 4.4 sources, use the RELENG_4_4 tag. Your supfile may look something like this: *default tag=RELENG_4_4 *default host=cvsup.freebsd.org *default prefix=/usr *default base=/usr/local/etc/cvsup *default release=cvs delete use-rel-suffix src-all src-crypto src-contrib Actually, this will also get you security fixes applied later to the 4.4-RELEASE tree, so it's probably a good thing to do. Read /usr/src/UPDATING (after the cvsup) for details and possible pitfalls. Using the RELENG_4_4_0_RELEASE tag would get you *only* 4.4-RELEASE, and not the subsequent critical fixes, if you need the exact release sources for some reason. Alternatively, if you have 4.4 CD-ROMs (or the ability to FTP), you can install the kernel source distribution from the original media using /stand/sysinstall, which should return your source tree to more or less its original state. Following the upgrade of your sources, leave the GENERIC kernel config as-is, and try to rebuild it: > >rm -Rf /usr/src/sys/compile/GENERIC > >cd /usr/src/sys/i386/conf > >config GENERIC > >cd ../../compile/GENERIC > >make depend > >make > >make install > > > >If that doesn't work, there is likely something wrong in your source > >tree. Do a fresh cvsup of the system sources and try again. > > > >Since you're also adding your own code to the kernel, do so carefully. > >A how-to on kernel hacking would be a bit much for this message :-), > >but basically, change as little as possible (meaning, start with a > >fresh kernel that you have successfully compiled without any changes), > >and make sure you can still compile at each step. Be prepared to roll > >back your last set of changes in the event something blows up. Yes, > >this takes time. Yes, it takes a lot *less* time than trying to insert > >hundreds of lines at once. :-) -- Ryan Thompson <ryan@sasknow.com> SaskNow Technologies - http://www.sasknow.com 901 1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020802101340.N47960-100000>