Re: List of Servers for FreeBSD and Ports Updates...
> 1-Port directory update through portsnap > 2-FreeBSD src update through CTM > 3-Port updates through distfiles and/or packages > > I think 1- and 2- are quite straightforward. To allow 1- I need to white > list the whole content of http://portsnap.freebsd.org/ . To allow 2- I need > to white list the content of ftp://ftp.freebsd.org/pub/FreeBSD/CTM/ . That > should be sufficient, right? Yoy can receive all of src*, ports, cvs by ctm You can receive ctm by mail, all from @freebsd.org mail lists Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Required HTTP/FTP Servers for FreeBSD and Ports Updates?
Hi, I am working on a network which uses a http/ftp proxy that prompts by default for user permission before downloading any file. In order to be able to keep my system up-to-date (FreeBSD and ports), I have to white list the FreeBSD servers and directories that need to be accessible, because otherwise I can only download files through a web browser, which is obviously extremely painful. Also only the HTTP and FTP protocols are allowed on my network, so CVSUP is not allowed. So my current plan is to update FreeBSD using the following tools: 1-Port directory update through portsnap 2-FreeBSD src update through CTM 3-Port updates through distfiles and/or packages I think 1- and 2- are quite straightforward. To allow 1- I need to white list the whole content of http://portsnap.freebsd.org/ . To allow 2- I need to white list the content of ftp://ftp.freebsd.org/pub/FreeBSD/CTM/ . That should be sufficient, right? The main issue I have though is with 3-. MASTER_SITE_BACKUP and MASTER_SITE_OVERRIDE variables are no longer recognized in /etc/make.conf, right? How can I force FreeBSD to pull distfiles and packages from ftp://ftp.freebsd.org/pub/FreeBSD/ports ? Also what is the difference between ftp://ftp.freebsd.org/pub/FreeBSD/distfiles and ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles ? I guess one of the directories is aliased to point to the other, right? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
List of Servers for FreeBSD and Ports Updates...
Hi, I am working on a network which uses a http/ftp proxy that prompts by default for user permission before downloading any file. In order to be able to keep my system up-to-date (FreeBSD and ports), I have to white list the FreeBSD servers and directories that need to be accessible, because otherwise I can only download files through a web browser, which is obviously extremely painful. Also only the HTTP and FTP protocols are allowed on my network, so CVSUP is not allowed. So my current plan is to update FreeBSD using the following tools: 1-Port directory update through portsnap 2-FreeBSD src update through CTM 3-Port updates through distfiles and/or packages I think 1- and 2- are quite straightforward. To allow 1- I need to white list the whole content of http://portsnap.freebsd.org/ . To allow 2- I need to white list the content of ftp://ftp.freebsd.org/pub/FreeBSD/CTM/ . That should be sufficient, right? The main issue I have though is with 3-. MASTER_SITE_BACKUP and MASTER_SITE_OVERRIDE variables are no longer recognized in /etc/make.conf, right? How can I force FreeBSD to pull distfiles and packages from ftp://ftp.freebsd.org/pub/FreeBSD/ports ? Also what is the difference between ftp://ftp.freebsd.org/pub/FreeBSD/distfiles and ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles ? I guess one of the directories is aliased to point to the other, right? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Sat, 7 Nov 2009 10:57:54 -0600, Adam Vande More wrote: > There are three basic branches, CURRENT STABLE RELEASE > > You want release. You shouldn't run anything else unless you're willing and > able to help with testing, debugging, and development. That's a quite generic answer, but basically I agree. On a production system, in most cases RELEASE is the branch you want to follow, beginning from X.Y-RELEASE and then tacking the security updates X.Y-RELEASE-pZ. The tool freebsd-update is very good for this task, especially when you're not running a custom kernel. STABLE is a good solution when you want to use a stable system, but are interested in additions between the releases. Things that are tested and found working are present in STABLE and will often appear in the upcoming RELEASE. CURRENT is interesting for you - as Adam said - for testing and development, and if you are intendedly interested in "bleeding edge" software. Note that it can happen that a CURRENT system of today won't build, but will tomorrow. It's the development branch. In any case: You should re-install or re-compile ALL of your applications when you perform the step to a new release (e. g. 7.2 -> 8.0). You can install the 7-compat port to avoid this (downward compatibility libraries). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
andrew clarke writes: > > Don't bother with any of that. Just use portsnap. It's also part of > > base, and was written by the same person that wrote freebsd-update. > > It's lovely and much faster, although some people may argue with me on > > that. > > > For your system, use freebsd-update. > > Seconded. Portsnap and freebsd-update are a cinch to use. As for freebsd-update: It has limitations; /inter alia/ see the DESCRIPTION section of the man page. If that's something one can live with, use it. If it's not, then the OP really needs to get familiar with the update-from-source method as described in the Handbook. It's scary at first (actually, it's still a teeny bit scary after ten years). but it helps one understand what goes into making a working system ... which is a really good thing if something does manage to go Horribly Wrong(tm). Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Sat 2009-11-07 19:19:52 UTC-0800, Randi Harper (ra...@freebsd.org) wrote: > Don't bother with any of that. Just use portsnap. It's also part of > base, and was written by the same person that wrote freebsd-update. > It's lovely and much faster, although some people may argue with me on > that. > For your system, use freebsd-update. Seconded. Portsnap and freebsd-update are a cinch to use. > For your ports tree, use portsnap. For installed ports, use > portupgrade or portmanager. I'm more fond of portmanager, but it seems > portupgrade has many more users. Both portupgrade and portmanager are > available in the ports tree, not base. I use portmaster and find it easy to use. Not familiar with portmanager. /usr/ports/UPDATING will often provide portmaster commands where necessary and these can useful for upgrading some ports. Maybe it's easy to translate those commands to their equivalent portmanager commands. Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Fri, Nov 6, 2009 at 9:31 AM, Roger wrote: > > My second concerned is the ports. In the file "ports-supfile" there is > one option, "*default release=cvs tag=.". > I believe this specifies which cvs tag to use when pulling files from > the ports. At one point I had "*default release=cvs > tag=RELEASE_7_2_0". > When I pulled the ports using the "RELEASE_7_2_0" tag and tried to > build "portsupgrade" the installation failed because the ruby version > that was going to be installed I believe had a security problem. (I > love the fact that I was stopped from installing software that is > KNOWN to be vulnerable). > I figured that maybe I needed to get the latest version. So I went > ahead and changed the cvs tag to "." (which I believe means the head > version). > Don't bother with any of that. Just use portsnap. It's also part of base, and was written by the same person that wrote freebsd-update. It's lovely and much faster, although some people may argue with me on that. I updated the ports and then tried the installation again, this time > the installation went further but failed again due to the fact that > my libtool (I can't remember the exact name) was older than what the > installation required. So that threw me off. > I believe that libtool is part of the base system and not the ports, > correct? > So that made me think that maybe because of using the latest version > of the ports I can build certain ports if my base is not > concurrent (in terms of what the ports requires and what my system > offers) with the port system. > So my question is this, if my FreeBSD release is 7.2-RELEASE-p4 which > tag should I set for the ports system? > Should I put the tag "RELEASE_7_2_0" and then wait for a security fix > of the particular port (ruby) and then proceed to install? > What is the recommended approach if your aim is to have your system up > to date and stable? > For your system, use freebsd-update. For your ports tree, use portsnap. For installed ports, use portupgrade or portmanager. I'm more fond of portmanager, but it seems portupgrade has many more users. Both portupgrade and portmanager are available in the ports tree, not base. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Sat, Nov 7, 2009 at 3:20 PM, Frank Shute wrote: > You mentioned lsof but there is a utility in base which you probably > don't know about called fstat(1), which does a lot of what lsof does. > Thank you for the tip. I will definitely look into it. > IIRC, the sources for 7.2 should be on the CD (run sysinstall(8) after > sticking the CD in). That will save you from downloading all the > sources. > > Then update the sources with csup(1) using the correct tag: RELENG_7_2 > > There's a supfile, /usr/share/examples/cvsup/standard-supfile, which > you can change the default host and cvs tag of and it should work. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html > > goes into the details. > > > Regards, > > -- > > Frank > > Contact info: http://www.shute.org.uk/misc/contact.html > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Sat, Nov 07, 2009 at 11:39:41AM -0500, Roger wrote: > > Hello all, > > I have another concept that I'm confused about, the source distribution. > Some ports, like "lsof" require the existence of /usr/src. > What I don't understand is which version to use to keep synchronized > with the production release. > When the installed was performed the release was 7.2 but after doing > "freebsd-update" the release is now > 7.2-p4. According to the documentation, I can track CURRENT, STABLE plus > other. > Which one is the recommended one for a production server. I have not > build that many > packages that need the sources present so now would be a good time to > find out which one > I should use. > > Thank you for your time and patience, > > -r You mentioned lsof but there is a utility in base which you probably don't know about called fstat(1), which does a lot of what lsof does. IIRC, the sources for 7.2 should be on the CD (run sysinstall(8) after sticking the CD in). That will save you from downloading all the sources. Then update the sources with csup(1) using the correct tag: RELENG_7_2 There's a supfile, /usr/share/examples/cvsup/standard-supfile, which you can change the default host and cvs tag of and it should work. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html goes into the details. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
Roger wrote: > Hello all, > > I have another concept that I'm confused about, the source distribution. > Some ports, like "lsof" require the existence of /usr/src. > What I don't understand is which version to use to keep synchronized > with the production release. > When the installed was performed the release was 7.2 but after doing > "freebsd-update" the release is now > 7.2-p4. A RELEASE such as 7.2 has a maintenance period during which the security team will apply security patches to the OS. Only the patches are applied, the rest of the bulk of /usr/src is untouched. This is what the -p4 means. The security support period for different releases can be located on the web site. Some releases are designated "extended support", while others have shorter time frames. > According to the documentation, I can track CURRENT, STABLE plus > other. Which one is the recommended one for a production server. I have > not build that many > packages that need the sources present so now would be a good time to > find out which one > I should use. > I don't use the binary freebsd-update myself, but still use the old csup the source in /usr/src and the make buildworld/buildkernel/install dance. So I tend to think in terms of CVS tags. The tag RELENG_7_2_0_RELEASE would fetch the original release bits that never change. The tag RELENG_7_2 would fetch the /usr/src that has the security patches applied. The -p4 you observed means that freebsd-update used binaries built with security patches applied. If there exists any question as to whether your /usr/src is in sync you can simply csup your source with the RELENG_7_2 tag in the supfile. There is also another way to patch, and that is to apply patches manually. Let's say, for example, the built in bind had a file or two that got patched. You could rebuild just this one thing and after installing the bits simply restart the daemon. Sometimes this is preferred when one needs to prevent a security hole but doesn't want to reboot a server. A downside is when you do this it does not register the "-p4" like you noticed. For a production server I feel it is best to use production release. IMHO there is one possible cause to consider STABLE for a production server and that is if there is new code "Merged From Current" that addresses and corrects a very specific problem. Let's say you have a particular NIC in your server that is exhibiting an exact same (and reproducible) condition as described in a bug report. If code which fixes this exact problem becomes available it will be written in CURRENT, and after some testing if deemed to be of sufficient quality it will be merged back to STABLE. Upgrading to STABLE will then pull in this fix. IMHO I wouldn't normally consider this unless there is an exact match between problem and fix. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Sat, Nov 7, 2009 at 10:39 AM, Roger wrote: > Hello all, > > I have another concept that I'm confused about, the source distribution. > Some ports, like "lsof" require the existence of /usr/src. > What I don't understand is which version to use to keep synchronized > with the production release. > When the installed was performed the release was 7.2 but after doing > "freebsd-update" the release is now > 7.2-p4. According to the documentation, I can track CURRENT, STABLE plus > other. > Which one is the recommended one for a production server. I have not > build that many > packages that need the sources present so now would be a good time to > find out which one > I should use. > > Thank you for your time and patience, > > There are three basic branches, CURRENT STABLE RELEASE You want release. You shouldn't run anything else unless you're willing and able to help with testing, debugging, and development. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
Hello all, I have another concept that I'm confused about, the source distribution. Some ports, like "lsof" require the existence of /usr/src. What I don't understand is which version to use to keep synchronized with the production release. When the installed was performed the release was 7.2 but after doing "freebsd-update" the release is now 7.2-p4. According to the documentation, I can track CURRENT, STABLE plus other. Which one is the recommended one for a production server. I have not build that many packages that need the sources present so now would be a good time to find out which one I should use. Thank you for your time and patience, -r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ports updates
[CC'ing freebsd-questions@ again] Chad Perrin <[EMAIL PROTECTED]> wrote: > On Wed, May 16, 2007 at 11:06:20AM +0200, Fabian Keil wrote: > > "Paul V. Belyakov" <[EMAIL PROTECTED]> wrote: > > > > > Why ports updates recently occur so seldom? > > > > Because of the ongoing tests for the xorg 7.2 integration. > > Any idea whether this will make the r300 driver available through the > ports tree? I'm not involved in the xorg integration and don't know which drivers will eventually be ported, however r300 doesn't show up in: grep r300 /usr/ports/x11-drivers/*/pkg-plist so my assumption is that it wont be available right away. Fabian signature.asc Description: PGP signature
Re: ports updates
Le 16/05/2007 à 18:45:21+1000, Paul Fraser a écrit > On 5/16/07, Paul V. Belyakov <[EMAIL PROTECTED]> wrote: > > > >Why ports updates recently occur so seldom? > > > > The ports tree is currently frozen for the merge of a new Xorg release. > Things should return to normal shortly. Don't known if this switch is with many pain or not but lots of thanks for those guys to do this big work. Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Mer 16 mai 2007 15:45:50 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports updates
Paul Fraser writes: > > Why ports updates recently occur so seldom? > > The ports tree is currently frozen for the merge of a new Xorg > release. Things should return to normal shortly. Probably not, in the statistical sense. :-) Not only will there be the X upgrade, for all that affects, but the backlog of other ports comparable to a major version change, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports updates
On 5/16/07, Paul V. Belyakov <[EMAIL PROTECTED]> wrote: Why ports updates recently occur so seldom? The ports tree is currently frozen for the merge of a new Xorg release. Things should return to normal shortly. -- Regards, Paul Fraser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports updates
"Paul V. Belyakov" <[EMAIL PROTECTED]> wrote: > Why ports updates recently occur so seldom? Because of the ongoing tests for the xorg 7.2 integration. For details see: http://wiki.freebsd.org/ModularXorg or the ports@ archive. Fabian signature.asc Description: PGP signature
ports updates
Why ports updates recently occur so seldom? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports updates
jxz wrote: Hello! I'm considering upgrading from Linux to FreeBSD in my home machine. I have some doubts concerning the ports collection: Nice participle (gerund?) in that first sentence :-) I would use the 4.8-RELEASE branch. The ports are stalled (just security upgrades) or they continue to be updated with new versions of the softwares? What are the updates policies of the ports collections on the other branches, where do I found more about it? TIA. The ports tree is the ports tree there's no branch. It's tagged -CURRENT in the CVS system, so if you're running -STABLE, for example, you'd have to have seperate supfiles for source and ports (but it's no problem, ready to configure examples are all in /usr/share/examples/cvsup/). My advice would be to install what you want from ports, cvsup the new tree periodically (say monthly or so) and use 'portupgrade' (from the ports tree) to keep the ports up to date. Dru Lavigne has a great article on portupgrade at onlamp.com: http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html I'd also advise that if you do go this route, start portupgrade within a couple of months after you move to FBSD. I waited over a year for one server, and it took a while to get that one straightened out when I finally got around to 'portupgrade' on it. :-( Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports updates
On Sat, Oct 18, 2003 at 02:46:02PM -0200, jxz wrote: > I'm considering upgrading from Linux to FreeBSD in my home machine. I > have some doubts concerning the ports collection: > > I would use the 4.8-RELEASE branch. The ports are stalled (just > security upgrades) or they continue to be updated with new versions of > the softwares? > > What are the updates policies of the ports collections on the other > branches, where do I found more about it? ports do not have any special relation to any particular branch of the OS. There's just ports, which gets continually updated with maybe the occasional hiatus right before new releases when a set of packages is produced to go onto the release CDs Don't confuse ports; which is a framework of makefiles and other supporting material that makes it trivially easy to download source, compile and install any software; with packages; which are the compiled output of ports gathered together in a handy-to-install tar-ball. As complete a set of packages as possible is produced to go with each OS release, and if there's time available on the package building cluster, updated packages will be produced when possible. Given the parallel release tracks of 4.x and 5.x at the moment, there hasn't been much time to produce as many package updates as usual. The typical way of using ports is described very well in a series of onlamp articles by Dru Lavigne: http://www.oreillynet.com/pub/a/bsd/2003/08/07/FreeBSD_Basics.html http://www.oreillynet.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html http://www.oreillynet.com/pub/a/bsd/2003/09/18/FreeBSD_Basics.html but the canonical instructions are at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP http://www.freebsd.org/ports/index.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: ports updates
On Sat, 18 Oct 2003 14:46:02 -0200 jxz <[EMAIL PROTECTED]> wrote: > The ports are stalled (just> security upgrades) or they continue to be > updated with new versions of the softwares? Ports always give you the latest software for your FreeBSD box. You need to cvsup them regularly, but that's all. After that you run the everything you'll ever want to run from ports ;) -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ports updates
Hello! I'm considering upgrading from Linux to FreeBSD in my home machine. I have some doubts concerning the ports collection: I would use the 4.8-RELEASE branch. The ports are stalled (just security upgrades) or they continue to be updated with new versions of the softwares? What are the updates policies of the ports collections on the other branches, where do I found more about it? TIA. -- [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
