Re: Applying local patches after updating FreeBSD source

2012-01-24 Thread Maxim Khitrov
On Mon, Jan 23, 2012 at 2:13 PM, Maxim Khitrov m...@mxcrypt.com wrote: On Mon, Jan 23, 2012 at 1:25 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make

Re: Applying local patches after updating FreeBSD source

2012-01-24 Thread Conrad J. Sabatier
On Mon, 23 Jan 2012 14:13:49 -0500 Maxim Khitrov m...@mxcrypt.com wrote: On Mon, Jan 23, 2012 at 1:25 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make

Applying local patches after updating FreeBSD source

2012-01-23 Thread Maxim Khitrov
Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will be automatically applied whenever that port is built. Is there equivalent functionality for building FreeBSD world and kernel? When

Re: Applying local patches after updating FreeBSD source

2012-01-23 Thread Matthew Seaman
On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will be automatically applied whenever that port is built. Is there equivalent

Re: Applying local patches after updating FreeBSD source

2012-01-23 Thread Maxim Khitrov
On Mon, Jan 23, 2012 at 1:25 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will

Updating FreeBSD

2012-01-11 Thread Артем Каялайнен
Hello, I'm trying to update my FreeBSD install on two servers. They are mostly identical. So, I've builded world and kernel on first srv, updated it, without any problems. Then exported /usr/src and /usr/obj by NFS to another machine, then installed kernel, but can't install world. It says:

Re: Updating FreeBSD

2012-01-11 Thread Volodymyr Kostyrko
Артем Каялайнен wrote: I don't have any options in make.conf on first machine, nor on second machine. I've googled a little and found, that _p is profiling library and it can be ignored with -DNO_PROFILE option. But in this case, How about compairing /etc/src.conf? -- Sphinx of black quartz

Re: Updating FreeBSD

2012-01-11 Thread Артем Каялайнен
2012/1/11 Volodymyr Kostyrko c.kw...@gmail.com: How about compairing /etc/src.conf? Wow, you are 100% right. My bad. Thanks. --- With Best Regards / Ystävällisin terveisin Artem Kajalainen ___ freebsd-questions@freebsd.org mailing list

Re: Is CTM still being offered for updating FreeBSD?

2011-02-26 Thread Chris Rees
On 25 February 2011 23:42, Eitan Adler li...@eitanadler.com wrote:   Why is this question even arising? Surely there are other problems that need to be addressed much more than the ending of a useful, uncontroversial service by someone who is not familiar with it? I am familiar with it. I

Is CTM still being offered for updating FreeBSD?

2011-02-25 Thread Eitan Adler
) Is it still being offered and supported as a method of updating FreeBSD systems? 2) If not can the section in the handbook be removed? I have attached a patch which removes references to CTM from the handbook. Should it be applied? 3) Probably the most controversial question - but I'll ask

Re: Is CTM still being offered for updating FreeBSD?

2011-02-25 Thread b. f.
So I have a few questions: 1) Is it still being offered and supported as a method of updating FreeBSD systems? As of today, yes -- I have recent deltas in my mailbox. But you could easily check by subscribing, and looking at: http://ftp.freebsd.org/pub/FreeBSD/CTM where the deltas are still

Re: Is CTM still being offered for updating FreeBSD?

2011-02-25 Thread Eitan Adler
 Why is this question even arising? Surely there are other problems that need to be addressed much more than the ending of a useful, uncontroversial service by someone who is not familiar with it? I am familiar with it. I just happened to notice that the mailing lists were empty and therefore

Clarification on updating FreeBSD through csup

2007-09-17 Thread Rakhesh Sasidharan
Hi there! Just seeking a clarification on keeping FreeBSD up-to-date through csup. I am on FreeBSD 6.2 and want to keep up-to-date for security patches etc. I understand I can use csup to follow the RELENG_62 branch. After the sources are downloaded, do I have to follow all the steps

Re: Clarification on updating FreeBSD through csup

2007-09-17 Thread Daniel Bye
On Mon, Sep 17, 2007 at 09:24:26PM +0400, Rakhesh Sasidharan wrote: Hi there! Just seeking a clarification on keeping FreeBSD up-to-date through csup. I am on FreeBSD 6.2 and want to keep up-to-date for security patches etc. I understand I can use csup to follow the RELENG_62 branch.

Re: Clarification on updating FreeBSD through csup

2007-09-17 Thread Rakhesh Sasidharan
Daniel Bye wrote: On Mon, Sep 17, 2007 at 09:24:26PM +0400, Rakhesh Sasidharan wrote: I understand I can use csup to follow the RELENG_62 branch. After the sources are downloaded, do I have to follow all the steps outlined in this

Re: Problem updating Freebsd ver 6.2

2007-05-12 Thread Erik Norgaard
Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). Up to know, I

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread Gerard Seibert
On Fri, 11 May 2007 01:45:47 -0500 WizLayer [EMAIL PROTECTED] wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread Simon Castillo
Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Gerard Seibert [EMAIL PROTECTED] escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread WizLayer
On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Gerard Seibert [EMAIL PROTECTED]

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread youshi10
On Fri, 11 May 2007, Simon Castillo wrote: Hi Garret: Freebsd ver 6.2 Samba: from ver 3.0.23 to 3.0.24 gdm: From ver 2.16 to 2.18 Thanks Simon Garrett Cooper [EMAIL PROTECTED] escribió: Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread Gerard Seibert
On Fri, 11 May 2007 11:23:11 -0500 (CDT) Simon Castillo [EMAIL PROTECTED] wrote: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Assuming your ports tree is up to date, try running: pkgdb -Ffv

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread Simon Castillo
Hi WizLayer: Nope, no particular reason to use portmanager. I guess I'll one more that suffer a bad experience. I don't see any other solution than re-install every thing again. Thanks Simon WizLayer [EMAIL PROTECTED] escribió: On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Hi

Re: Problem updating Freebsd ver 6.2

2007-05-11 Thread WizLayer
On Friday 11 May 2007 04:00:15 pm you wrote: WizLayer [EMAIL PROTECTED] escribió: On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Gerard Seibert escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I could be wrong as I haven't used portmanager in a while (and

Problem updating Freebsd ver 6.2

2007-05-10 Thread Simon Castillo
Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). After the update, I starting having

Re: Problem updating Freebsd ver 6.2

2007-05-10 Thread WizLayer
On Thursday 10 May 2007 11:24:31 pm Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after

Re: Updating freebsd without cvsup

2005-09-20 Thread vittorio
Alle 18:27, venerdì 16 settembre 2005, Ashley Moran ha scritto: Vittorio wrote: Thanks. I've just compiled the portsnap sources and put the following in /usr/local/etc/portsnap.conf: # Defaults: WORKDIR=/usr/local/portsnap PORTSDIR=/usr/ports

Re: Updating freebsd without cvsup

2005-09-20 Thread Kevin Kinsey
vittorio wrote: Well, after thourough examination and a word with the network administrator I learnt that my FreeBSD 5.4 client cannot resolve the name (and the IP too) of portsnap.daemonology.net because it is behind a firewall and a proxy (which -by the way - I had already defined via

Updating freebsd without cvsup

2005-09-16 Thread Vittorio
At office I have a freebsd 5.4 server to run postgresql. I'd like to update the ports in it from time to time but cvsup doesn't seem to work behind our proxy. In fact, in make.conf I have the following two lines: FETCH_ENV = HTTP_PROXY=http://user:[EMAIL PROTECTED]:8080 FETCH_ENV =

Re: Updating freebsd without cvsup

2005-09-16 Thread Kris Kennaway
On Fri, Sep 16, 2005 at 03:38:42PM +0100, Vittorio wrote: At office I have a freebsd 5.4 server to run postgresql. I'd like to update the ports in it from time to time but cvsup doesn't seem to work behind our proxy. In fact, in make.conf I have the following two lines: FETCH_ENV =

Re: Updating freebsd without cvsup

2005-09-16 Thread Ashley Moran
Vittorio wrote: Is there another alternative way of defining the proxy OR any other way of getting a new source three to be copied to the server, e.g., by means of a cd burnt at home? Have you considered using the sysutils/portsnap port? It's what I use to keep my servers up-to-date.

Re: Re: Updating freebsd without cvsup

2005-09-16 Thread Vittorio
Fetching public key... failed. What's wrong with the original key in the portsnap.conf.sample file? Thanks again Vittorio Messaggio originale Da: [EMAIL PROTECTED] Data: 16-set-2005 5.14 PM A: Vittorio[EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Ogg: Re: Updating freebsd

Re: Updating freebsd without cvsup

2005-09-16 Thread Colin Percival
Vittorio wrote: # Defaults: WORKDIR=/usr/local/portsnap PORTSDIR=/usr/ports KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 URL=http://portsnap.daemonology.net # portsnap fetch Fetching public key... failed. What's wrong with the original key in the

Re: Updating freebsd without cvsup

2005-09-16 Thread Ashley Moran
Vittorio wrote: Thanks. I've just compiled the portsnap sources and put the following in /usr/local/etc/portsnap.conf: # Defaults: WORKDIR=/usr/local/portsnap PORTSDIR=/usr/ports KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 URL=http://portsnap.daemonology.net BUT

Re: Updating freebsd without cvsup

2005-09-16 Thread vittorio
Alle 18:21, venerdì 16 settembre 2005, Colin Percival ha scritto: Vittorio wrote: # Defaults: WORKDIR=/usr/local/portsnap PORTSDIR=/usr/ports KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 URL=http://portsnap.daemonology.net # portsnap fetch Fetching

Re: Updating freebsd without cvsup

2005-09-16 Thread Giorgos Keramidas
On 2005-09-16 21:49, vittorio [EMAIL PROTECTED] wrote: Alle 18:21, venerd?? 16 settembre 2005, Colin Percival ha scritto: That key is correct. Try running portsnap --debug fetch to work out what the problem is. Here it is : vicbsd# portsnap --debug fetch Fetching public key... fetch:

Re: Updating FreeBSD

2005-03-21 Thread Andreas Davour
On Mon, 21 Mar 2005, Christopher San Diego wrote: I'm a confused newbie whose been (re)installing FreeBSD 5.3 Release for the past week or two. I've read the handbook and various other documents concerning updating FreeBSD only to learn that -STABLE and -CURRENT are both development branches. Take

Updating FreeBSD

2005-03-20 Thread Christopher San Diego
I'm a confused newbie whose been (re)installing FreeBSD 5.3 Release for the past week or two. I've read the handbook and various other documents concerning updating FreeBSD only to learn that -STABLE and -CURRENT are both development branches. I've decided to stick with -RELEASE. Given