[I cut out the history to start clean.]
So 63a7e799b32c was already built and installed as of here, from what
I can tell. This example does not show the 1c090bf880bf -> 63a7e799b32c
transition, only after 63a7e799b32c is already built and installed.
So, up to this point:
buildworld 63a7e799b32
On Sun, Jan 28, 2024 at 05:13:24PM -0800, Mark Millard wrote:
> ...
> > As it happens, I rather fumble-fingered the (intended) reboot on the 2nd
> > laptop (and started another rebuild instead).
> >
> > And I do these within script(1), as it's handy to have a record.
> >
> > Note that this differ
On Jan 28, 2024, at 16:05, David Wolfskill wrote:
> On Sun, Jan 28, 2024 at 03:00:59PM -0800, Mark Millard wrote:
>> ...
>> To be clear, referencing details of your context:
>>
>> When you had the stable/14 machines at 1c090bf880bf:
>>
>> A) You built (META_MODE): 63a7e799b32c
>> B) You
On Sun, Jan 28, 2024 at 03:00:59PM -0800, Mark Millard wrote:
> ...
> To be clear, referencing details of your context:
>
> When you had the stable/14 machines at 1c090bf880bf:
>
> A) You built (META_MODE): 63a7e799b32c
> B) You installed: 63a7e799b32c
> C) You rebooted in
On Jan 28, 2024, at 14:34, Mark Millard wrote:
> [Note: your email is rejecting my E-mail:
> 554: 5.7.1 ]
>
> On Jan 28, 2024, at 14:06, David Wolfskill wrote:
>
>> On Sun, Jan 28, 2024 at 10:20:30AM -0800, Mark Millard wrote:
>>> ...
That said, one of the machines in question is my local
[Note: your email is rejecting my E-mail:
554: 5.7.1 ]
On Jan 28, 2024, at 14:06, David Wolfskill wrote:
> On Sun, Jan 28, 2024 at 10:20:30AM -0800, Mark Millard wrote:
>> ...
>>> That said, one of the machines in question is my local "build machine" --
>>> and for it, in addition to in-place so
On Sun, Jan 28, 2024 at 10:20:30AM -0800, Mark Millard wrote:
> ...
> > That said, one of the machines in question is my local "build machine" --
> > and for it, in addition to in-place source updates, I also do (weekly)
> > updates of my "production" machines (at home).
> >
> > And for that case,
On Jan 28, 2024, at 07:46, David Wolfskill wrote:
> On Sun, Jan 28, 2024 at 07:30:53AM -0800, Mark Millard wrote:
>> ...
>> The following two sequences are very different:
>>
>> make buildworld
>> make buildworld
>>
>> vs.
>>
>> make buildworld
>> make installworld
>> make buildworld
>>
>> Th
On Sun, Jan 28, 2024 at 07:30:53AM -0800, Mark Millard wrote:
> ...
> The following two sequences are very different:
>
> make buildworld
> make buildworld
>
> vs.
>
> make buildworld
> make installworld
> make buildworld
>
> The installworld can update a lot of non-source
> files that were use
David Wolfskill wrote on
Date: Sun, 28 Jan 2024 11:50:44 UTC :
> Context for this is in-place source-based updates using META_MODE, amd64
> arch.
> . . .
> But llvm is now being rebuilt.
>
> Why?
The following two sequences are very different:
make buildworld
make buildworld
vs.
make buildwo
Context for this is in-place source-based updates using META_MODE, amd64
arch.
In the specific case that catalyzed this note, the systems are running:
freebeast(14.0-S)[4] uname -aUK
FreeBSD freebeast.catwhisker.org 14.0-STABLE FreeBSD 14.0-STABLE #40
stable/14-n266551-63a7e799b32c: Sat Jan 27 1
11 matches
Mail list logo
