Re: How do YOU stay up to date?
Roger 'Rocky' Vetterberg wrote: Drew Tomlinson wrote: Roger 'Rocky' Vetterberg told a big fish story including the following on 1/15/2004 2:34 AM: Duane Winner wrote: Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). If you have the resources, you should consider using a dedicated machine for compiling. With ~10 laptops, a bunch of workstations and about 20-25 servers running FreeBSD we use 2 dedicated machines that does nothing but download sources and compiles them. One is tracking 4.x-STABLE and the other 5.x-RELEASE. Anyone can nfs mount choosen directories from these machines and install the pre-compiled software. It works extremely well, once the users have learned the correct process. I've been contemplating this setup. I know I can use portupgrade to build packages and then just install packages on other machines but don't understand the details. Is it difficult to set up? Can you point me to a web tutorial? Thanks, Drew http://bsdvault.net/sections.php?op=viewarticle&artid=53 Its very basic, but it should get you started. Sorry, wrong link. Try this one instead: http://www.freebsddiary.org/makeworld-2boxes.php -- R ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
Drew Tomlinson wrote: Roger 'Rocky' Vetterberg told a big fish story including the following on 1/15/2004 2:34 AM: Duane Winner wrote: Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). If you have the resources, you should consider using a dedicated machine for compiling. With ~10 laptops, a bunch of workstations and about 20-25 servers running FreeBSD we use 2 dedicated machines that does nothing but download sources and compiles them. One is tracking 4.x-STABLE and the other 5.x-RELEASE. Anyone can nfs mount choosen directories from these machines and install the pre-compiled software. It works extremely well, once the users have learned the correct process. I've been contemplating this setup. I know I can use portupgrade to build packages and then just install packages on other machines but don't understand the details. Is it difficult to set up? Can you point me to a web tutorial? Thanks, Drew http://bsdvault.net/sections.php?op=viewarticle&artid=53 Its very basic, but it should get you started. -- R ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
Roger 'Rocky' Vetterberg told a big fish story including the following on 1/15/2004 2:34 AM: Duane Winner wrote: Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). If you have the resources, you should consider using a dedicated machine for compiling. With ~10 laptops, a bunch of workstations and about 20-25 servers running FreeBSD we use 2 dedicated machines that does nothing but download sources and compiles them. One is tracking 4.x-STABLE and the other 5.x-RELEASE. Anyone can nfs mount choosen directories from these machines and install the pre-compiled software. It works extremely well, once the users have learned the correct process. I've been contemplating this setup. I know I can use portupgrade to build packages and then just install packages on other machines but don't understand the details. Is it difficult to set up? Can you point me to a web tutorial? Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
From: "Roger 'Rocky' Vetterberg" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: freebsd-questions <[EMAIL PROTECTED]> Subject: Re: How do YOU stay up to date? Date: Thu, 15 Jan 2004 11:34:45 +0100 Duane Winner wrote: Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). If you have the resources, you should consider using a dedicated machine for compiling. With ~10 laptops, a bunch of workstations and about 20-25 servers running FreeBSD we use 2 dedicated machines that does nothing but download sources and compiles them. One is tracking 4.x-STABLE and the other 5.x-RELEASE. Anyone can nfs mount choosen directories from these machines and install the pre-compiled software. It works extremely well, once the users have learned the correct process. I'm doing something very similar with a dedicated server and for ports I do a daily upgrade with portupgrade -Rruap to upgrade and build a package that the users can then install because I have some very slow machines that would take days to build some of the larger ports and by just having the server's /usr/ports nfs mounted on their machines they can upgrade quickly by just using the -P option to portupgrade. I'm not sure if that is the best way to do it but it has worked well for me for sometime. Good luck, _ There are now three new levels of MSN Hotmail Extra Storage! Learn more. http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
Duane Winner wrote: Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). If you have the resources, you should consider using a dedicated machine for compiling. With ~10 laptops, a bunch of workstations and about 20-25 servers running FreeBSD we use 2 dedicated machines that does nothing but download sources and compiles them. One is tracking 4.x-STABLE and the other 5.x-RELEASE. Anyone can nfs mount choosen directories from these machines and install the pre-compiled software. It works extremely well, once the users have learned the correct process. -- R ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
On Wednesday 14 January 2004 11:36 pm, Duane Winner wrote: > Thanks for the reply, which was very helpful. > > Could you just clarify one thing for me? On your last point regarding > 'SECURITY - STABLE - CURRENT', my understanding up to now has been that > this applies to the FreeBSD 'src' tree only, but not to the ports > collection. Am I correct? > > If we are running 4.9-RELEASE, and cvsuping using 'RELENG_4_9', my > assumption is that we'll rarely have to do a 'buildworld' or recompile > the kernel, correct? It's not that you'll "have" to recompile less frequently; but when you **choose** to recompile, fewer changes will be made using RELENG_4_9 (SECURITY) than RELENG_4 (STABLE). > But ports don't fall under the same tracking mechanism, correct? > (I have a line 'ports-all tag=.' in my supfile because I read that there > are no release tags for ports). I think you're correct here; but you could choose not to cvsup the ports. > > I just want to make sure I understand all of this correctly. > > Thanks again, > Duane > > On Wed, 2004-01-14 at 23:27, Andrew L. Gould wrote: > > On Wednesday 14 January 2004 10:11 pm, Duane Winner wrote: > > > Hello all again, > > > > > > I'm finally getting my arms around FreeBSD and the updating processes > > > and tools. But I'm still trying to come up with good > > > habits/methods/instructions for updating routines for both myself and > > > my colleagues who also want to switch to FreeBSD. > > > > > > I now understand how to use cvsup to keep my src and ports tree > > > current. I know how to use pkg_add -r to install new sotware, or go > > > into /usr/ports/whatever to make install. I know how to do portupgrade > > > to upgrade my installed ports, how to pkg_version -v to see what's out > > > of date with my tree, and how to cronjob cvsup to keep my trees > > > current. (I still need to play more with make world and whatnot) > > > > > > But what do you all out there in BSD land do to stay current as a > > > practice? I'm looking at this on two fronts: FreeBSD on our laptops > > > (There will be at least 3 of us with T23's, and I also plan on > > > migrating most, if not all of my servers from Linux to FreeBSD). > > > > > > One thing that concerns me, at least on the laptops, is the amount of > > > time spent compiling new software as it is release, seeing as how we > > > will be running x, gnome and Yahweh knows what elseI've already > > > spent a great deal of time recompiling all this stuff to get current. > > > (granted, I'm still experimenting, blowing my machine away, starting > > > over, to both learn and write up instructions for the other guys, so > > > I'm repeating the pains). > > > > > > How is this going to affect us longterm with staying current if we are > > > constantly getting new source and having to recompile? One of my > > > colleagues has proposed just using packages as much as possible. But > > > although it seems simple enough to to go "pkg_add -r gnome2", what > > > about updating? I mean, after installing the package, "pkg_version -v" > > > many packages are listed as out of date with my current ports tree. So > > > how to update short of doing a "portupgrade -Pa" and waiting a few or > > > several hours? > > > > The existence of newer source code is not, in and of itself, > > justification for an upgrade. Each day brings new source code. It is up > > to the administrator to monitor new features, bug fixes and security > > issues to determine when an upgrade is warranted. > > > > Also, keep in mind: > > > > 1. "portupgrade -rR " will upgrade the specified port, its > > dependencies and any ports that depend upon the specified port. You > > don't have to update all ports at once to keep port dependencies in sync. > > > > 2. Packages installed with pkg_add, that have associated ports, can be > > upgraded using portupgrade. > > > > 3. Unless your use of computers demands cutting or bleeding edge code, > > tracking SECURITY may meet your needs as well or better than STABLE or > > CURRENT. > > > > Best regards, > > > > Andrew Gould > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
Thanks for the reply, which was very helpful. Could you just clarify one thing for me? On your last point regarding 'SECURITY - STABLE - CURRENT', my understanding up to now has been that this applies to the FreeBSD 'src' tree only, but not to the ports collection. Am I correct? If we are running 4.9-RELEASE, and cvsuping using 'RELENG_4_9', my assumption is that we'll rarely have to do a 'buildworld' or recompile the kernel, correct? But ports don't fall under the same tracking mechanism, correct? (I have a line 'ports-all tag=.' in my supfile because I read that there are no release tags for ports). I just want to make sure I understand all of this correctly. Thanks again, Duane On Wed, 2004-01-14 at 23:27, Andrew L. Gould wrote: > On Wednesday 14 January 2004 10:11 pm, Duane Winner wrote: > > Hello all again, > > > > I'm finally getting my arms around FreeBSD and the updating processes > > and tools. But I'm still trying to come up with good > > habits/methods/instructions for updating routines for both myself and my > > colleagues who also want to switch to FreeBSD. > > > > I now understand how to use cvsup to keep my src and ports tree current. > > I know how to use pkg_add -r to install new sotware, or go into > > /usr/ports/whatever to make install. I know how to do portupgrade to > > upgrade my installed ports, how to pkg_version -v to see what's out of > > date with my tree, and how to cronjob cvsup to keep my trees current. (I > > still need to play more with make world and whatnot) > > > > But what do you all out there in BSD land do to stay current as a > > practice? I'm looking at this on two fronts: FreeBSD on our laptops > > (There will be at least 3 of us with T23's, and I also plan on migrating > > most, if not all of my servers from Linux to FreeBSD). > > > > One thing that concerns me, at least on the laptops, is the amount of > > time spent compiling new software as it is release, seeing as how we > > will be running x, gnome and Yahweh knows what elseI've already > > spent a great deal of time recompiling all this stuff to get current. > > (granted, I'm still experimenting, blowing my machine away, starting > > over, to both learn and write up instructions for the other guys, so I'm > > repeating the pains). > > > > How is this going to affect us longterm with staying current if we are > > constantly getting new source and having to recompile? One of my > > colleagues has proposed just using packages as much as possible. But > > although it seems simple enough to to go "pkg_add -r gnome2", what about > > updating? I mean, after installing the package, "pkg_version -v" many > > packages are listed as out of date with my current ports tree. So how to > > update short of doing a "portupgrade -Pa" and waiting a few or several > > hours? > > > > The existence of newer source code is not, in and of itself, justification for > an upgrade. Each day brings new source code. It is up to the administrator > to monitor new features, bug fixes and security issues to determine when an > upgrade is warranted. > > Also, keep in mind: > > 1. "portupgrade -rR " will upgrade the specified port, its > dependencies and any ports that depend upon the specified port. You don't > have to update all ports at once to keep port dependencies in sync. > > 2. Packages installed with pkg_add, that have associated ports, can be > upgraded using portupgrade. > > 3. Unless your use of computers demands cutting or bleeding edge code, > tracking SECURITY may meet your needs as well or better than STABLE or > CURRENT. > > Best regards, > > Andrew Gould > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
On Wed, Jan 14, 2004 at 11:11:22PM -0500, Duane Winner wrote:
> I now understand how to use cvsup to keep my src and ports tree current.
> I know how to use pkg_add -r to install new sotware, or go into
> /usr/ports/whatever to make install. I know how to do portupgrade to
> upgrade my installed ports, how to pkg_version -v to see what's out of
> date with my tree, and how to cronjob cvsup to keep my trees current. (I
> still need to play more with make world and whatnot)
I think you've got the right tools, you jsut need to use them in
different ways.
> One thing that concerns me, at least on the laptops, is the amount of
> time spent compiling new software as it is release, seeing as how we
> will be running x, gnome and Yahweh knows what else
You have enough machines to justify using a build host: a single machine
that simply builds ports into packages (or compiles buildworld and
buildkernel into the /usr/obj directory). You can then do binary
installs off of the build host via NFS. It's a very handy architecture
because it allows you to do offload the work of building to a separate
server and roll out to other machines when it's convenient. It also
helps ensure that other machines stay uniform and allows new machines to
rolled out with little effort.
-T
--
"The most exhausting thing in life is being insincere."
- Anne Morrow Lindbergh {American Author}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do YOU stay up to date?
On Wednesday 14 January 2004 10:11 pm, Duane Winner wrote: > Hello all again, > > I'm finally getting my arms around FreeBSD and the updating processes > and tools. But I'm still trying to come up with good > habits/methods/instructions for updating routines for both myself and my > colleagues who also want to switch to FreeBSD. > > I now understand how to use cvsup to keep my src and ports tree current. > I know how to use pkg_add -r to install new sotware, or go into > /usr/ports/whatever to make install. I know how to do portupgrade to > upgrade my installed ports, how to pkg_version -v to see what's out of > date with my tree, and how to cronjob cvsup to keep my trees current. (I > still need to play more with make world and whatnot) > > But what do you all out there in BSD land do to stay current as a > practice? I'm looking at this on two fronts: FreeBSD on our laptops > (There will be at least 3 of us with T23's, and I also plan on migrating > most, if not all of my servers from Linux to FreeBSD). > > One thing that concerns me, at least on the laptops, is the amount of > time spent compiling new software as it is release, seeing as how we > will be running x, gnome and Yahweh knows what elseI've already > spent a great deal of time recompiling all this stuff to get current. > (granted, I'm still experimenting, blowing my machine away, starting > over, to both learn and write up instructions for the other guys, so I'm > repeating the pains). > > How is this going to affect us longterm with staying current if we are > constantly getting new source and having to recompile? One of my > colleagues has proposed just using packages as much as possible. But > although it seems simple enough to to go "pkg_add -r gnome2", what about > updating? I mean, after installing the package, "pkg_version -v" many > packages are listed as out of date with my current ports tree. So how to > update short of doing a "portupgrade -Pa" and waiting a few or several > hours? > The existence of newer source code is not, in and of itself, justification for an upgrade. Each day brings new source code. It is up to the administrator to monitor new features, bug fixes and security issues to determine when an upgrade is warranted. Also, keep in mind: 1. "portupgrade -rR " will upgrade the specified port, its dependencies and any ports that depend upon the specified port. You don't have to update all ports at once to keep port dependencies in sync. 2. Packages installed with pkg_add, that have associated ports, can be upgraded using portupgrade. 3. Unless your use of computers demands cutting or bleeding edge code, tracking SECURITY may meet your needs as well or better than STABLE or CURRENT. Best regards, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do YOU stay up to date?
Hello all again, I'm finally getting my arms around FreeBSD and the updating processes and tools. But I'm still trying to come up with good habits/methods/instructions for updating routines for both myself and my colleagues who also want to switch to FreeBSD. I now understand how to use cvsup to keep my src and ports tree current. I know how to use pkg_add -r to install new sotware, or go into /usr/ports/whatever to make install. I know how to do portupgrade to upgrade my installed ports, how to pkg_version -v to see what's out of date with my tree, and how to cronjob cvsup to keep my trees current. (I still need to play more with make world and whatnot) But what do you all out there in BSD land do to stay current as a practice? I'm looking at this on two fronts: FreeBSD on our laptops (There will be at least 3 of us with T23's, and I also plan on migrating most, if not all of my servers from Linux to FreeBSD). One thing that concerns me, at least on the laptops, is the amount of time spent compiling new software as it is release, seeing as how we will be running x, gnome and Yahweh knows what elseI've already spent a great deal of time recompiling all this stuff to get current. (granted, I'm still experimenting, blowing my machine away, starting over, to both learn and write up instructions for the other guys, so I'm repeating the pains). How is this going to affect us longterm with staying current if we are constantly getting new source and having to recompile? One of my colleagues has proposed just using packages as much as possible. But although it seems simple enough to to go "pkg_add -r gnome2", what about updating? I mean, after installing the package, "pkg_version -v" many packages are listed as out of date with my current ports tree. So how to update short of doing a "portupgrade -Pa" and waiting a few or several hours? As far as the servers go, I'm almost certain that I'll be standardizing on 4.9-RELEASE, with minimal software, so I'm not so concerned here since the security/bug fixes seem far and few between for this release. I'm just looking for advice. If the long way is the only way, fine. I need to start writing up some standards and procedures so we can move on. But if there are more efficient methods, or methods to make things easier on everybody else, or some technique I'm just plain missing, I'm all ears. Thanks for any info, guidance or virtual asskicking you can provide me. And sorry my post is so long. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
