2009/12/8 Alex Huth :
> * Matthew Seaman schrieb:
>> Alex Huth wrote:
>>
>> Yes. If you want to track one of the development branches (HEAD, RELENG_N)
>> then you have to update sources by csup(1) or various other mechanisms and
>> then compile your kernel+world yourself.
>>
>> Alternatively you c
* Matthew Seaman schrieb:
> Alex Huth wrote:
>
> Yes. If you want to track one of the development branches (HEAD, RELENG_N)
> then you have to update sources by csup(1) or various other mechanisms and
> then compile your kernel+world yourself.
>
> Alternatively you can track release branches (RE
Alex Huth wrote:
> * Matthew Seaman schrieb:
>>> Next question is if i don't get updates with freebsd-update when i have
>>> a stable version? I have the problem with two machines (6.3 and 6.4). On
>>> both
>>> i do not get the public key because it is not available on the remote
>>> server.
>>>
* Matthew Seaman schrieb:
> > Next question is if i don't get updates with freebsd-update when i have
> > a stable version? I have the problem with two machines (6.3 and 6.4). On
> > both
> > i do not get the public key because it is not available on the remote
> > server.
> > I have test it with
Alex Huth wrote:
> Hello!
>
> Maybe i haven't understand the process of updating not really. I thought when
> i use Releng_6 in the stable_supfile i get the latest version of 6.x = 6.4.
> But after the process of make buildworld and so on, it is still 6.3. Do i have
> to use Releng_6_4 even when i
Hello!
Maybe i haven't understand the process of updating not really. I thought when
i use Releng_6 in the stable_supfile i get the latest version of 6.x = 6.4.
But after the process of make buildworld and so on, it is still 6.3. Do i have
to use Releng_6_4 even when i do not get the patches then?
