Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

he end of my first upgrade since the >> transition to git: >> >> cd /usr/src/freebsd-current && make installworld && etcupdate >> >> 𠄴– concluded with a successful installworld, then a few lines about >> scanning an

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, Jan 2, 2021 at 8:43 AM Graham Perrin wrote: > On 02/01/2021 08:47, Herbert J. Skuhra wrote: > > >> < > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html> > >> still describes use of `svnlite` (not `git` or `got`) and, I guess, > >> might continue to do so for some

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, Jan 2, 2021 at 1:31 AM Graham Perrin wrote: > On 01/01/2021 19:24, Herbert J. Skuhra wrote: > > > On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote: > >> At what should have been the end of my first upgrade since the > >> transition to git: > &g

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, 02 Jan 2021 17:18:10 +0100, Graham Perrin wrote: > > Sorry for the mis-formatting and lost line breaks in my previous > e-mail. Blame Thunderbird. > > As reference: > > > > /usr/src > > > BSD, third-party, and/or local source f

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

Sorry for the mis-formatting and lost line breaks in my previous e-mail. Blame Thunderbird. As reference: /usr/src > BSD, third-party, and/or local source files ___ freebsd-current@freebsd.

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, Jan 02, 2021 at 03:43:04PM +, Graham Perrin wrote: > ... > >> In this context, is `cd /usr/src` still true? > > If you clone the repository to /usr/src instead of e.g. > > /usr/src/freebsd-current. > > Thanks again. > > I imagine that use cases will _eventually_ include trios of direc

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On 02/01/2021 08:47, Herbert J. Skuhra wrote: still describes use of `svnlite` (not `git` or `got`) and, I guess, might continue to do so for some time. In this context, is `cd /usr/src` still true? If you clone the re

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, 02 Jan 2021 09:47:07 +0100 "Herbert J. Skuhra" wrote: > On Sat, 02 Jan 2021 09:31:36 +0100, Graham Perrin wrote: > > > > With the transition to Git > > > > == > > > > If it's true that /usr/src is _no longe

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, 02 Jan 2021 09:31:36 +0100, Graham Perrin wrote: > > With the transition to Git > > == > > If it's true that /usr/src is _no longer_ a predictable path to the > source files, then is it still appropriate for users' fortune

etcupdate, svnlite, documentation etc. following the transition of source to Git

On 01/01/2021 19:24, Herbert J. Skuhra wrote: On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote: At what should have been the end of my first upgrade since the transition to git: cd /usr/src/freebsd-current && make installworld && etcupdate 𠄴– concluded with a success

Re: Panic @r305116 in transition to multi-user mode

On Wed, Aug 31, 2016 at 02:30:23PM +0200, Mateusz Guzik wrote: > ... > > db> dump > > Dumping 1299 out of 32687 > > MB:..2%..12%..21%..31%..41%..51%..61%..71%..81%..92% > > Dump complete > > db> > > > > This is most likely r305091 which I reverted in r305124, i.e. just > upgrade and see if it h

Re: Panic @r305116 in transition to multi-user mode

On Wed, Aug 31, 2016 at 05:09:56AM -0700, David Wolfskill wrote: > This was well into the transition from single- to multi-user mode, > so the following information is a re-creation after I rebooted to > single-user mode (verbosely), ran "fsck -p", then "exit" -- copy

Panic @r305116 in transition to multi-user mode

This was well into the transition from single- to multi-user mode, so the following information is a re-creation after I rebooted to single-user mode (verbosely), ran "fsck -p", then "exit" -- copy/pasted from serial console: # exit Setting hostuuid: 80f1e964-dc63-0010-89d5-0

Re: 11.0 -r301900 and cross builds: the transition from not using WITH_META_MODE=yes to using it still seems to require cleanworld between

On 6/15/16 1:36 AM, Mark Millard wrote: > On 2016-Jun-14, at 11:00 PM, Mark Millard wrote: > >> [The following is after having updated and booted the host amd64 environment >> to -r301900. The activity reported on is cross building targeting a rpi2 >> (armv7-a/cortex-a7). It is trying to go fro

Re: 11.0 -r301900 and cross builds: the transition from not using WITH_META_MODE=yes to using it still seems to require cleanworld between

On 2016-Jun-14, at 11:00 PM, Mark Millard wrote: > [The following is after having updated and booted the host amd64 environment > to -r301900. The activity reported on is cross building targeting a rpi2 > (armv7-a/cortex-a7). It is trying to go from not haivng used > WITH_META_MODE=yes last ti

11.0 -r301900 and cross builds: the transition from not using WITH_META_MODE=yes to using it still seems to require cleanworld between

[The following is after having updated and booted the host amd64 environment to -r301900. The activity reported on is cross building targeting a rpi2 (armv7-a/cortex-a7). It is trying to go from not haivng used WITH_META_MODE=yes last time I cross built to now using WITH_META_MODE=yes this time.

Re: Unclean shutdown for r273852 -> r273899 transition

Am Fri, 31 Oct 2014 06:59:12 -0700 David Wolfskill schrieb: > I thought it a bit odd when I rebooted after the "make installworld" > completed and found that fsck(8) was checking teh file systems on my > laptop. > > When it also happened for my build machine, I suspected it might not > merely be

Unclean shutdown for r273852 -> r273899 transition

I thought it a bit odd when I rebooted after the "make installworld" completed and found that fsck(8) was checking teh file systems on my laptop. When it also happened for my build machine, I suspected it might not merely be a one-off oddity... and I was able to make use of the serial console on t

Re: panic during transition to multi-user mode @r249303 [i386]

On Tue, Apr 09, 2013 at 08:59:39PM +0300, Konstantin Belousov wrote: > ... > This is hopefully fixed by r249314. After hand-applying that change, re-building & re-installing the kernel on my build machine, it is able to make the transition to multi-user mode without issue. Now running

Re: panic during transition to multi-user mode @r249303 [i386]

At 10:59 AM 4/9/2013, Konstantin Belousov wrote: >This is hopefully fixed by r249314. > Yes r249314 works fine Thanks || n...@pozo.com || || || -- This message has been scanned for viruses

Re: panic during transition to multi-user mode @r249303 [i386]

On Tue, Apr 09, 2013 at 10:26:53AM -0700, Manfred Antar wrote: > > > More info > Break to debugger starts here: > > add net default: gateway 192.168.0.1 > add net :::0.0.0.0: gateway ::1 > add net ::0.0.0.0: gateway ::1 > add net fe80::: gateway ::1 > add net ff02::: gateway ::1 > Waiting fo

Re: panic during transition to multi-user mode @r249303 [i386]

More info Break to debugger starts here: add net default: gateway 192.168.0.1 add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 Waiting for bge0 to have link. Waiting for 192.168.0.1 to respond to ICMP Fatal trap 12: page

Re: panic during transition to multi-user mode @r249303 [i386]

At 09:21 AM 4/9/2013, David Wolfskill wrote: >I saw this first on my laptop; backtrace mentioned something about >iwn(4), so after I saved the crash dump, I flippe dthe wireless switch >off and tried again... and got a different (but undoubtedly related) >panic, which I also saved. > >Then, after m

panic during transition to multi-user mode @r249303 [i386]

I saw this first on my laptop; backtrace mentioned something about iwn(4), so after I saved the crash dump, I flippe dthe wireless switch off and tried again... and got a different (but undoubtedly related) panic, which I also saved. Then, after my build machine finished, that also got a panic (us

Re: SMP deadlock during multi-user mode transition after r204866

On Thu, Mar 11, 2010 at 09:04:40AM -0800, David Wolfskill wrote: > My build machine (dmesg attached) is a dual CPU, single-core box; my > laptop is a single CPU, single-core box. I track head on each daily; > while the build machine has been locking up during the transition to > mul

SMP deadlock during multi-user mode transition after r204866

My build machine (dmesg attached) is a dual CPU, single-core box; my laptop is a single CPU, single-core box. I track head on each daily; while the build machine has been locking up during the transition to multi-user mode since Tuesday (when I had built CURRENT at r204909; previous was r204866

HEADSUP: locale renaming transition period is finished

Finally deprecated locale names generating and corresponding support code are removed today as promised years ago. Check your LANG variable confirm naming convention documented in the handbook. This change is not for MFC. ___ [EMAIL PROTECTED] mailing lis

Re: transition...

it > will be almost a year before we reach this point) > > 4.x-RELEASE (Currently in the middle) > > 5.0-CURRENT (The new branch (HEAD) for current) Yep. But why call them "stable", "current", etc. Just call the FreeBSD3, FreeBSD4, FreeBSD5 and alias the e

transition...

Well, Here we are again. Another branch off the FreeBSD code and the mailing lists are going to be confusing. CURRENT is starting to see posts of the 5.0 code and STABLE is starting to see things of 4.0. I read CURRENT and STABLE at the moment because I have myservers on 3.x and my laptop runnin

Re: Transition to 4.0

According to Jeroen Ruigrok/Asmodai: > my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel) > as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now. Same here with an SMP kernel. FreeBSD tara 4.0-CURRENT FreeBSD 4.0-CURRENT #9: Sun Jan 24 18:54:47 CE

Re: Transition to 4.0

Jeroen Ruigrok/Asmodai wrote: > Just a general note to Matt, Mark and a couple of other commiters: > > my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel) > as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now. > > Hope this is some good

Transition to 4.0

Just a general note to Matt, Mark and a couple of other commiters: my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel) as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now. Hope this is some good info after all the breakages =) --- Jeroen Ruigrok van der