On Mon, Aug 20, 2018 at 05:48:04AM -0700, Cy Schubert wrote:
> Make sure the archs are the same. Make sure the src and obj pathnames
> on both servers are exactly the same. Make sure /usr/src (or wherever
> you put it) is the same, it too needs to be rsynced.
>
> The tiniest differences will
In message <20180820062511.yaa2rimgmwpv3hxx@kazhap>, Dhananjay Balan
writes:
> On Sat, Aug 18, 2018 at 04:36:15PM -0700, Cy Schubert wrote:
> > You can use NFS or rsync. Make sure the src and obj path names are
> > exactly the same on all thes servers. I used to use NFS until a year or
> > two
On Sat, Aug 18, 2018 at 04:36:15PM -0700, Cy Schubert wrote:
> You can use NFS or rsync. Make sure the src and obj path names are
> exactly the same on all thes servers. I used to use NFS until a year or
> two ago when I started using different patches on different machines.
> On occasion I've
On 19/8/18 5:31 pm, Matthew Seaman wrote:
> On 19/08/2018 01:55, Shane Ambler wrote:
>>> I run 12-CURRENT on few machines, some more powerful that other (all
>>> of them x86_64, march varies).
>
>> You can use freebsd-update by setting up your own update server
>>
On Sun, Aug 19, 2018 at 6:30 PM O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Sun, 19 Aug 2018 00:34:20 +0200
> Dhananjay Balan schrieb:
>
> > Hi,
> >
> > I run 12-CURRENT on few machines, some more powerful that other (all
> > of them x86_64, march varies).
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sun, 19 Aug 2018 00:34:20 +0200
Dhananjay Balan schrieb:
> Hi,
>
> I run 12-CURRENT on few machines, some more powerful that other (all
> of them x86_64, march varies).
>
> Is there is a way to avoid building CURRENT on all machines? Rather
Dhananjay Balan wrote on 2018/08/19 00:34:
Hi,
I run 12-CURRENT on few machines, some more powerful that other (all
of them x86_64, march varies).
Is there is a way to avoid building CURRENT on all machines? Rather
than building everywhere, can I just build it on the big server that I
have and
On 19/08/2018 01:55, Shane Ambler wrote:
>> I run 12-CURRENT on few machines, some more powerful that other (all
>> of them x86_64, march varies).
> You can use freebsd-update by setting up your own update server
> https://www.freebsd.org/doc/en/articles/freebsd-update-server
freebsd-upgrade(8)
On 19/8/18 8:04 am, Dhananjay Balan wrote:
> Hi,
>
> I run 12-CURRENT on few machines, some more powerful that other (all
> of them x86_64, march varies).
>
> Is there is a way to avoid building CURRENT on all machines? Rather
> than building everywhere, can I just build it on the big server
On Sat, Aug 18, 2018 at 5:34 PM, Dhananjay Balan wrote:
> Hi,
>
> I run 12-CURRENT on few machines, some more powerful that other (all
> of them x86_64, march varies).
>
> Is there is a way to avoid building CURRENT on all machines? Rather
> than building everywhere, can I just build it on the
On Sun, Aug 19, 2018 at 12:34:20AM +0200, Dhananjay Balan wrote:
> Hi,
>
> I run 12-CURRENT on few machines, some more powerful that other (all
> of them x86_64, march varies).
>
> Is there is a way to avoid building CURRENT on all machines? Rather
> than building everywhere, can I just build
In message <20180818223420.rjisst4vuxzxbcrl@kazhap>, Dhananjay Balan
writes:
> Hi,
>
> I run 12-CURRENT on few machines, some more powerful that other (all
> of them x86_64, march varies).
>
> Is there is a way to avoid building CURRENT on all machines? Rather
> than building everywhere, can I
Hi,
I run 12-CURRENT on few machines, some more powerful that other (all
of them x86_64, march varies).
Is there is a way to avoid building CURRENT on all machines? Rather
than building everywhere, can I just build it on the big server that I
have and copy and update my laptop?
-
Dhananjay
13 matches
Mail list logo
