Date: Wed, 4 Nov 1998 21:57:28 +0000 From: Ben Smithurst <ben@scientia.demon.co.uk> To: Keith Woodman <keith@lightningweb.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: -current vs. -RELEASE Message-ID: <19981104215728.A3748@scientia.demon.co.uk> In-Reply-To: <Pine.BSF.3.96.981104130720.7155A-100000@nefertiti.lightningweb.com> References: <Pine.BSF.3.96.981104130720.7155A-100000@nefertiti.lightningweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Keith Woodman wrote: > 1) What are the differences between. -current -stable -RELEASE ?? -current is the latest, greatest and most likely to break (where most likely is still very unlikely, ime). -stable has bug fixes applied after they've been well tested in -current. -releases are made every now and again. I use -current, and it suits me fine. If you need your system to be _very_ stable, use -stable (like the name says). This is all as I understand it, anyway. > 2) Since I am running a server with 2.2.5 -RELEASE, does this needed patch > apply to me? No, the message says it only affects 3.0 and -current before it was fixed. I assume therefore that 2.2.5 is unnaffected. > 3) How do I implement the patch? patch ip_input.c patch_source ???? No. $ cd /usr/src/sys/netinet $ patch -p0 < where-you-saved-the-patch-file (the /usr/src/sys/netinet came from the RCS file: line in the patch, and -p0 means remove all directory components from the filename which it will patch. Note that you don't need to specify the file you are patching since the patch program will determine that from the patch file. Read the patch man page for more details.) -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key 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?19981104215728.A3748>