Re: Ports upgrade within Jail
The only common between the jail and the hosted system are the kernel and its drivers. You may use entirely different ports in the base system and into the jailed enviroment. So you may keep your jailed ports up to date without any concern as long as they do not conflict with the base system drivers and etc. Regards, Ivailo Tanusheff Deputy Head of IT Department ProCredit Bank (Bulgaria) AD Druckbar [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07.08.2008 13:15 To freebsd-questions@freebsd.org cc Subject Ports upgrade within Jail Hello List, i have a jail hosted on a 6-2 RELEASE machine i don't have access to. As i don't have access, i can't upgrade the base system. But i would like to keep the ports i use up to date. Will i encounter problems if i just upgrade my ports using portsnap and portmaster? or will those tools be aware of the version my base system is and only use ports that are made for this version? -- Thank you manuel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade question
On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm a newbie running 6.1 stable and I have what may be several simple questions: What exactly is happening when I run make index make readmes after I upgrade my ports tree? Why aren't the indexes and readmes made when we run cvsup ports You don't need to run make index... just cd into /usr/ports and type Better yet, don't screw with cvsup. Portsnap is standard equipment in 6.x. It's much faster, uses less bandwidth, and is even less load on the update server. And it does the indexes automatically. Just man portsnap or search the archives. -Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade question
On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm a newbie running 6.1 stable and I have what may be several simple questions: What exactly is happening when I run make index make readmes after I upgrade my ports tree? Why aren't the indexes and readmes made when we run cvsup ports-supfile? Finally, why does it take so long to make what appear (to me) to be fairly small files? Thanks. You don't need to run make index... just cd into /usr/ports and type 'make fetchindex' after every cvsup session. You don't need to run make readmes too, these are just html pages with all the ports listed on them... see here for an example: http://www.freebsd.org/ports/ -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade question
On 6/10/06, Nikolas Britton [EMAIL PROTECTED] wrote: On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm a newbie running 6.1 stable and I have what may be several simple questions: What exactly is happening when I run make index make readmes after I upgrade my ports tree? Why aren't the indexes and readmes made when we run cvsup ports-supfile? Finally, why does it take so long to make what appear (to me) to be fairly small files? Thanks. You don't need to run make index... just cd into /usr/ports and type 'make fetchindex' after every cvsup session. You don't need to run make readmes too, these are just html pages with all the ports listed on them... see here for an example: http://www.freebsd.org/ports/ err... that link/example should be something more like this one: http://www.freebsd.org/cgi/ports.cgi?query=stuffstype=allsektion=all -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports upgrade policy
Mike Loiterman wrote: This is my supfile: *default host=cvsup1.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6_0 *default delete use-rel-suffix src-all *default tag=. ports-all doc-all I have been using it like this for years, obviously changing to the latest release tag. I haven't had problem and I'm not having problems, but my question is this: Is it advisable to sync my source to RELEASE, but to CURRENT for ports? Typically, I upgade my ports a few days after they get updated so I'm always running the latest version, but would it be better to sync both ports and source to RELEASE? Hi Mike, It would be nice I guess if ports were tagged like src but they are not. Basically HEAD is all there is vis-a-vis tags. You can specify a specific date however. Duane Obviously, it depends, somewhat, on personal choice, but in terms of stablity and correctness which is better? -- Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: [EMAIL PROTECTED] PGP Key: 0xD1B9D18E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports upgrade policy
On Tue, Mar 14, 2006 at 04:18:13AM -0400, Duane Whitty wrote: Mike Loiterman wrote: This is my supfile: *default host=cvsup1.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6_0 *default delete use-rel-suffix src-all *default tag=. ports-all doc-all I have been using it like this for years, obviously changing to the latest release tag. I haven't had problem and I'm not having problems, but my question is this: Is it advisable to sync my source to RELEASE, but to CURRENT for ports? Typically, I upgade my ports a few days after they get updated so I'm always running the latest version, but would it be better to sync both ports and source to RELEASE? Hi Mike, It would be nice I guess if ports were tagged like src but they are not. Basically HEAD is all there is vis-a-vis tags. You can specify a specific date however. Ports *are* tagged for each release, but they are not branched. Duane Obviously, it depends, somewhat, on personal choice, but in terms of stablity and correctness which is better? -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Ports upgrade policy
Erik Trulsson mailto:[EMAIL PROTECTED] wrote: On Tue, Mar 14, 2006 at 04:18:13AM -0400, Duane Whitty wrote: Mike Loiterman wrote: This is my supfile: *default host=cvsup1.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6_0 *default delete use-rel-suffix src-all *default tag=. ports-all doc-all I have been using it like this for years, obviously changing to the latest release tag. I haven't had problem and I'm not having problems, but my question is this: Is it advisable to sync my source to RELEASE, but to CURRENT for ports? Typically, I upgade my ports a few days after they get updated so I'm always running the latest version, but would it be better to sync both ports and source to RELEASE? Hi Mike, It would be nice I guess if ports were tagged like src but they are not. Basically HEAD is all there is vis-a-vis tags. You can specify a specific date however. Ports *are* tagged for each release, but they are not branched. Yes, I know, which is why I asked the question...which is better? -- Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: [EMAIL PROTECTED] PGP Key: 0xD1B9D18E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports upgrade policy
On 3/14/06, Mike Loiterman [EMAIL PROTECTED] wrote: Erik Trulsson mailto:[EMAIL PROTECTED] wrote: On Tue, Mar 14, 2006 at 04:18:13AM -0400, Duane Whitty wrote: Mike Loiterman wrote: Is it advisable to sync my source to RELEASE, but to CURRENT for ports? Typically, I upgade my ports a few days after they get updated so I'm always running the latest version, but would it be better to sync both ports and source to RELEASE? It would be nice I guess if ports were tagged like src but they are not. Basically HEAD is all there is vis-a-vis tags. You can specify a specific date however. Ports *are* tagged for each release, but they are not branched. Yes, I know, which is why I asked the question...which is better? As I understand it, release tagsare static. If you specify a release tag, you get the ports as they were at the time of that release. Ports don't branch with releases, so if you want updated ports, you use tag=. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Ports upgrade policy
On Tue, 14 Mar 2006 08:35:46 -0600, Mike Loiterman [EMAIL PROTECTED] said: Erik Trulsson mailto:[EMAIL PROTECTED] wrote: [snip] Is it advisable to sync my source to RELEASE, but to CURRENT for ports? Typically, I upgade my ports a few days after they get updated so I'm always running the latest version, but would it be better to sync both ports and source to RELEASE? [snip] Ports *are* tagged for each release, but they are not branched. Yes, I know, which is why I asked the question...which is better? Considerations I can think of - (1) Advantage of using -HEAD (-CURRENT): Updates to ports may include security fixes. (2) Disadvantage of using -HEAD (-CURRENT): It is possible, though perhaps not likely, that an updated port would require something your -RELEASE base system lacked. Jud ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade question
On Mon, May 03, 2004 at 02:25:18PM +0300, alexander botov wrote: I'm sure that this is a trivial question to ask . I'm considering source and ports tree upgarde from 5.2_REL to 5.2.1_REL . I've never did cvs before (usually i back up , format + binary install and restore ) . I've read the article from the handbook and everything is pretty much explained there . My question is when i install the new distro how should i upgrade the ports tree after syncing it from cvs ? Are there any guidelines , tips or tricks ? I've heard about portupgrade port . Is this the right tool for bringing my ports up to date ? Your help will be greatly appreciated and I hope will save me hours of hesitation and headache :-) You've pretty much got the right idea. portupgrade(1) is the tool to use. However, you should read /usr/ports/UPDATING carefully -- apart from anything else, if you're upgrading from the ports tree as it was at the time of 5.2-RELEASE you'll have a tricky ruby(1) version bump to deal with (ruby is the language portupgrade is written in) as well as major updates for some large software collections like Gnome and KDE. Note that the ports collection is developed pretty much independently from the base system, and reflects the completely independent development of software by any number of completely different projects. There's no particular requirement to only upgrade your ports concurrently with upgrading your system. In fact, it's probably better to upgrade ports slightly more frequently (or perhaps even a lot more frequently) than the base system. 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 upgrade error?
On Friday 16 April 2004 08:11 am, Marwan Sultan wrote: Hello everyone, Im on FreeBSD 5.1-Release, CVsup, portupgrade are installed. I want to upgrade my ports tree, so I did whats on the Handbook. I'v copied and edit the file - ports-supfile. I ran the command cvsup -g -L 2 /path/to/ports-supfile And it gave me the following error: Parsing supfile /usr/home/deadline/things/ports-supfile Release not specified for collection host=cvsup1.freebsd.org I tired to change the mirror site, Also i tried to uncomment one of the packages, and I tired to add ports-all to end of the entries, but all gave the same error, any ideas? tips? please. This is my ports-supfile entries: host=cvsup1.freebsd.org *default host=cvsup1.freebsd.org You only need the one with the *default on it. It is complaining about the first one. Kent *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all PS: This command will run as a background proccess? if i disconnect from internet and I connect again later (Dialup) it will resume the updating? or i have to download it one time? -- Marwan Sultan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade error?
On Fri, 2004-04-16 at 15:11, Marwan Sultan wrote: Hello everyone, PS: This command will run as a background proccess? if i disconnect from internet and I connect again later (Dialup) it will resume the updating? I think it will time out and exit the process eventually, so you would have to restart the cvsup. You could script that, but be careful as noted below. or i have to download it one time? No, it is mostly a linear process. Whatever is updated by the time you disconnect will still be updated. Then when you restart the cvsup, you wont have to redo that part. There is some overhead searching through parts that don't need to be updated, so don't do it every 5minutes, but its not huge overhead. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade error?
Thank you Tim, Thank you Kent, This fixed the problem. On Fri, 16 Apr 2004 07:14:28 -0700, Kent Stewart wrote You only need the one with the *default on it. It is complaining about the first one. Kent *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade w/out internet connection
On Monday 22 September 2003 08:44 am, Brian Henning wrote: Greetings: Can i perform a ports upgrade to a computer that has no internet connection by ftping the file /pub/FreeBSD/ports/ports/ports.tar.gz and replacing the /usr/ports/ directory with the uncompressed version of this file? please let me know your opinion to solve my problem. It is only the beginning. You also have to download the distfiles for each of the ports that you want to update. You could also download the packages and bypass building the ports. I don't think the packages will be as uptodate as the port structure that you would download. They require hours to build. Where as, the port structure can be tarballed fairly quickly every day. Kent thanks, brian -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports upgrade
On Fri, Dec 20, 2002 at 18:11:11 +0200, [EMAIL PROTECTED] wrote:
Hello!
If I cvsup'd ports what will I need in order to make my new ports to work? I mean I
should make a buildworld?
no you wont
just installs portupgrade (ports/sysutils/portupgrade), and then run
portupgrade -R your_port_name
--
char*p=char*p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
-- Anonymous
msg12690/pgp0.pgp
Description: PGP signature
Re: ports upgrade
On Fri, 20 Dec 2002 18:11:11 +0200, [EMAIL PROTECTED] wrote: Hello! If I cvsup'd ports what will I need in order to make my new ports to work? I mean I should make a buildworld? Thanks! You will often be able to build most or all of your new ports without building the world, because cvsup-ing has updated the ports skeletons. However, occasionally an updated port will depend on something in your system having been updated, so building world would be necessary to avoid breakage. Therefore, unless building the world would be a problem (takes too long, don't want to take the machine offline, etc.), doing so avoids any potential difficulty. -- Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
