Re: Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

On 4/17/21 12:52 PM, Graham Perrin wrote: 2) line 2274 etcupdate -p I get: > No previous tree to compare against, a sane comparison is not possible. Hmm, how did you initially install this machine? Release images should generally i

Re: Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

On 4/18/21 1:48 AM, driesm.michi...@gmail.com wrote: If etcupdate -p fails before make installworld, then should the subsequent etcupdate be with or without option -B ? -p and -B are not related. -p deals with changes needed for a correct run of installworld (see above). -B uses a freshly bui

Re: Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

On 18/04/2021 09:48, driesm.michi...@gmail.com wrote: 1) lines 2273 and 2275 With ZFS in the mix, /usr/src is present but empty (the file system is not mounted). See [3] a bit lower in the file at 2341. … comes down to "service zfs sta

RE: Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

> -Original Message- > From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of Graham Perrin > Sent: Saturday, 17 April 2021 21:52 > To: freebsd-current > Subject: Review D28062 of /usr/src/UPDATING with regard to upgrading > FreeBSD and inconsist

Review D28062 of /usr/src/UPDATING with regard to upgrading FreeBSD and inconsistency with the FreeBSD Handbook

1) lines 2273 and 2275 With ZFS in the mix, /usr/src is present but empty (the file system is not mounted). If single user mode is recommended, then why is this not in the FreeBSD Handbook?

Re: head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

On 2018-Aug-26, at 12:35 PM, Dag-Erling Smørgrav wrote: > Mark Millard writes: >> But when I look at [...] the installed build(7) for head -r338319 I do >> not find any references to LOADER_DEFAULT_INTERP . > > It was added to build(7) in r338043: Thanks for the notes. Sure enough I see it in

Re: head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

Mark Millard writes: > But when I look at [...] the installed build(7) for head -r338319 I do > not find any references to LOADER_DEFAULT_INTERP . It was added to build(7) in r338043: LOADER_DEFAULT_INTERP Defines what interpreter the default loader program will

head's /usr/src/UPDATING vs. "LOADER_DEFAULT_INTERP, documented in build(7)": not documented yet

Quoting UPDATING for head: 20180818: The default interpreter has been switched from 4th to Lua. LOADER_DEFAULT_INTERP, documented in build(7), will override the default interpreter. If you have custom FORTH code you will need to set LOADER_DEFAULT_INTERP=4th (valid

Re: Typo in /usr/src/UPDATING

On 12 May 2013 12:01, Rainer Hurling wrote: > I am not a native speaker, but isn't there a typo in /usr/src/UPDATING > entry from 20130121? > > --- UPDATING.orig 2013-05-09 09:46:55.0 +0200 > +++ UPDATING2013-05-12 17:58:20.0 +0200 > @@ -108,7 +10

Typo in /usr/src/UPDATING

I am not a native speaker, but isn't there a typo in /usr/src/UPDATING entry from 20130121? --- UPDATING.orig 2013-05-09 09:46:55.0 +0200 +++ UPDATING2013-05-12 17:58:20.0 +0200 @@ -108,7 +108,7 @@ Due to the use of the new -l option to install(1) during

Re: performance / /usr/src/UPDATING

> Date: Mon, 24 Feb 2003 13:12:51 +0100 > From: Christoph Kukulies <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > In /usr/src/UPDATING I read that -current is always compiled withlots of debugging > flags on etc. > > Can this be switched off with a singl

Re: performance / /usr/src/UPDATING

Christoph Kukulies <[EMAIL PROTECTED]> writes: > In /usr/src/UPDATING I read that -current is always compiled > withlots of debugging flags on etc. > > Can this be switched off with a single switch in the Makefile? Not a single switch, but there isn't a whole lot to do. M

Re: performance / /usr/src/UPDATING

kuku> Can this be switched off with a single switch in the Makefile? No, or you misunderstand what FreeBSD-current is. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

performance / /usr/src/UPDATING

In /usr/src/UPDATING I read that -current is always compiled withlots of debugging flags on etc. Can this be switched off with a single switch in the Makefile? -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-cu

Re: GCC 3.2.1-pre and /usr/src/UPDATING

I just updated it for gcc 3.2. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: GCC 3.2.1-pre and /usr/src/UPDATING

* De: Garance A Drosihn <[EMAIL PROTECTED]> [ Data: 2002-09-02 ] [ Subjecte: Re: GCC 3.2.1-pre and /usr/src/UPDATING ] > Someone needs to update /usr/src/UPDATING then, so people will > find out about this need to recompile their C++ world. Who is > it that updates UPDA

Re: GCC 3.2.1-pre and /usr/src/UPDATING

2 is not binary >= compatible with 3.1. > >Most excellent! Thanks! Someone needs to update /usr/src/UPDATING then, so people will find out about this need to recompile their C++ world. Who is it that updates UPDATING these days? Thanks for getting this update done, btw. I was starting to wor

/usr/src/UPDATING

Hi Warner, Can you add a remark about the devfs and vinum conflict to UPDATING ? I had serious problems today, because I have been bitten by this conflict. Devfs is now in GENERIC-KERNEL in CURRENT, and if you upgrade and have vinum set up on on /usr, you cannot mount it - no way. mkdir: /dev/

Re: /usr/src/UPDATING question

On Wed, Apr 14, 1999 at 05:37:37PM -0700, David O'Brien wrote: > Some have gotten -aout to work. When was your last CVSup and non-a.out > `make world' ? Yesterday around 9pm MEST. -- Jos Backus _/ _/_/_/"Reliability means never _/

Re: /usr/src/UPDATING question

>: If it's true that cc -aout is broken (.section in an a.out .o file? Hm.), how >: can one rebuild things like XFree86 a.out libraries, when make world fails? > >What it means is that cc -aout has been broken since the conversion to >egcs, and now it is supposedly working. Known breakage includes

Re: /usr/src/UPDATING question

> - I don't understand the wording of the most recent paragraph: > > Note cc -aout has been broken since the conversion to egcs. If > you have rebuilt things like XFree86 a.out libraries, you should > rebuild them again or things (including netscape) will not work. Some h

Re: /usr/src/UPDATING question

On Wed, Apr 14, 1999 at 03:57:32PM -0600, Warner Losh wrote: > What it means is that cc -aout has been broken since the conversion to > egcs, and now it is supposedly working. I see ``supposedly'' sounds about right :) > Don't know about building an aout world. According to my system, no... I w

Re: /usr/src/UPDATING question

In message <19990414234749.a42...@hal.mpn.cp.philips.com> Jos Backus writes: : - I don't understand the wording of the most recent paragraph: : : Note cc -aout has been broken since the conversion to egcs. If : you have rebuilt things like XFree86 a.out libraries, you should :

/usr/src/UPDATING question

While doing a ``make -DWANT_AOUT world'' I'm seeing the following: ===> libgcc_r c++ -O -pipe -march=pentium -I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -D_PTHREADS -I/usr/src/gnu/lib/libgcc_r/../../.