Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

ISO). Let me know if you > have some more specific questions, I'll be glad to help. > > -Max > > On Wed, Jul 13, 2016 at 6:52 AM, Glen Barber <g...@freebsd.org> wrote: > > > On Mon, Jul 11, 2016 at 05:23:32PM -0700, Maxim Sobolev wrote: > > > P.S. Just

Re: "make delete-old" failed: 11.0-ALPHA6 @r302388 -> stable/11 @r302412

On Fri, Jul 08, 2016 at 02:14:48PM -0700, Mark Millard wrote: > On Fri, Jul 08, 2016 at 09:23:43AM -0400, Michael Butler wrote: > Seems to be > a typo .. TARGET_CPUARCH should be TARGET_ARCH .. > > > > ${TARGET_CPUARCH} != "arm" apparently was an attempt to not explicitly test > for each

FreeBSD 11.0-BETA1 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first BETA build of the 11.0-BETA1 release cycle is now available. Installation images are available for: o 11.0-BETA1 amd64 GENERIC o 11.0-BETA1 i386 GENERIC o 11.0-BETA1 powerpc GENERIC o 11.0-BETA1 powerpc64 GENERIC64 o 11.0-BETA1 sparc64

HEADS-UP: OpenSSH DSA keys are deprecated in 12.0 and 11.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH, and will be deprecated effective 11.0-RELEASE (and preceeding RCs). Please see r303716 for details on the relevant commit, but upstream no longer considers them secure.

Re: HEADS-UP: OpenSSH DSA keys are deprecated in 12.0 and 11.0

On Fri, Aug 05, 2016 at 01:59:18AM +, Glen Barber wrote: > This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH, > and will be deprecated effective 11.0-RELEASE (and preceeding RCs). > Stupid editor mistake. OpenSSH DSA keys are deprecated upstream. Sorr

11.0-RELEASE schedule update

As those of you tracking our PR system are probably aware, re@ is aware of an issue related to ZFS and VFS that we feel is urgent enough to have fixed for 11.0-RELEASE. https://lists.freebsd.org/pipermail/freebsd-current/2016-August/062829.html As such, instead of branching releng/11.0 today and

Re: FreeBSD 11.0-BETA4 Now Available

On Mon, Aug 08, 2016 at 10:48:30AM +0200, Lars Engels wrote: > On Sat, Aug 06, 2016 at 09:05:26PM +0000, Glen Barber wrote: > > -BEGIN PGP SIGNED MESSAGE- > > > o The new system hardening options have been fixed to avoid overwriting > > other options sele

Re: FreeBSD 11.0-BETA4 Now Available

;> > >>>On Mon, Aug 08, 2016 at 02:44:05PM +, Glen Barber wrote: > >>>>On Mon, Aug 08, 2016 at 10:48:30AM +0200, Lars Engels wrote: > >>>>>On Sat, Aug 06, 2016 at 09:05:26PM +, Glen Barber wrote: > >>>>>>-BEGIN PGP SIGN

Re: FreeBSD 11.0-BETA4 Now Available

On Mon, Aug 08, 2016 at 11:22:27AM -0700, Nathan Whitehorn wrote: > > > On 08/08/16 10:56, Glen Barber wrote: > >On Mon, Aug 08, 2016 at 10:53:26AM -0700, Nathan Whitehorn wrote: > >> > >>On 08/08/16 10:43, Lars Engels wrote: > >>>On Mon, Aug 08

FreeBSD 11.0-BETA4 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The fourth BETA build of the 11.0-RELEASE release cycle is now available. Installation images are available for: o 11.0-BETA4 amd64 GENERIC o 11.0-BETA4 i386 GENERIC o 11.0-BETA4 powerpc GENERIC o 11.0-BETA4 powerpc64 GENERIC64 o 11.0-BETA4

Re: New FreeBSD snapshots available: head (20160701 r302303)

On Sat, Jul 02, 2016 at 09:26:14AM +0300, Ivan Klymenko wrote: > On Sat, 2 Jul 2016 06:19:58 + > Glen Barber <g...@freebsd.org> wrote: > ivan@nonamehost:/ % ftp > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/11.0-ALPHA6 Trying > 77.88.40.106:21 ... Connected to ftp.g

Re: Weekday missing in date(1) output

On Mon, Jul 04, 2016 at 03:12:19AM +, Glen Barber wrote: > On Sun, Jul 03, 2016 at 10:17:54PM +0200, Thomas Eberhardt wrote: > > % uname -a > > FreeBSD clarence.ocp.lan 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302324: Sun > > Jul 3 21:27:41 CEST 2016 > > tho...@cl

Re: Weekday missing in date(1) output

On Sun, Jul 03, 2016 at 10:17:54PM +0200, Thomas Eberhardt wrote: > % uname -a > FreeBSD clarence.ocp.lan 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302324: Sun Jul > 3 21:27:41 CEST 2016 > tho...@clarence.ocp.lan:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 > % env LANG=en_US.UTF-8 date > Sunday,

Re: ISO image: where is the CLANG compiler?

On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote: > On Thu, 19 Jan 2017 06:58:16 +0100 > Matthias Apitz wrote: > > > El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude > > escribió: > > > > > On 2017-01-18 14:37, O. Hartmann wrote: > > > > Am

Re: ISO image: where is the CLANG compiler?

On Thu, Jan 19, 2017 at 08:50:34PM +0100, Andreas Nilsson wrote: > On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber <g...@freebsd.org> wrote: > > I do want to weigh in here and inform I am actively watching this > > thread. clang(1) is not in disc1.iso or bootonly.iso because

Re: ISO image: where is the CLANG compiler?

On Thu, Jan 19, 2017 at 07:10:00PM +, Glen Barber wrote: > On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote: > > On Thu, 19 Jan 2017 06:58:16 +0100 > > Matthias Apitz <g...@unixarea.de> wrote: > > > > > El día Wednesday, January 18, 201

Delay with 11.0-RC2 builds

Two issues have been brought to our attention, and as a result, 11.0-RC2 builds will be delayed a day or two while these are investigated. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211926 An update will be sent if the delay is

Re: make universe and /etc/src.conf

On Mon, Aug 22, 2016 at 08:47:06AM -0700, Bryan Drewery wrote: > On 8/22/2016 8:27 AM, Glen Barber wrote: > > On Mon, Aug 22, 2016 at 10:24:25AM -0500, Eric van Gyzen wrote: > >> I just tried a "make universe", and all the kernels failed because they > >> co

Re: make universe and /etc/src.conf

On Mon, Aug 22, 2016 at 10:24:25AM -0500, Eric van Gyzen wrote: > I just tried a "make universe", and all the kernels failed because they > couldn't > find the config files. I had forgotten that I have this in /etc/src.conf: > > KERNCONF=NUMA > KERNCONFDIR=/etc > > Since "make

FreeBSD 11.0-RC2 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The second RC build of the 11.0-RELEASE release cycle is now available. Installation images are available for: o 11.0-RC2 amd64 GENERIC o 11.0-RC2 i386 GENERIC o 11.0-RC2 powerpc GENERIC o 11.0-RC2 powerpc64 GENERIC64 o 11.0-RC2 sparc64 GENERIC o

Re: FreeBSD 11.0-RC2 Now Available

On Thu, Aug 25, 2016 at 03:14:20AM +, Glen Barber wrote: > [...] > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64 and i386 > systems running earlier FreeBSD releases. Systems running earlier > FreeBSD releases can

Re: FreeBSD 11.0-RC2 Now Available

On Thu, Aug 25, 2016 at 08:29:11AM +0200, Jochen Neumeister wrote: > On 25.08.2016 06:53, Glen Barber wrote: > > On Thu, Aug 25, 2016 at 03:14:20AM +0000, Glen Barber wrote: > >> [...] > >> === Upgrading === > >> > >> The freebsd-update(8) utili

Re: FreeBSD 11.0-RC2 Now Available

On Thu, Aug 25, 2016 at 08:43:18AM +0200, Jochen Neumeister wrote: > On 25.08.2016 08:32, Glen Barber wrote: > > On Thu, Aug 25, 2016 at 08:29:11AM +0200, Jochen Neumeister wrote: > >> On 25.08.2016 06:53, Glen Barber wrote: > >>> On Thu, Aug 25, 2016 at 03:14

11.0-RELEASE status update

As some of you may be aware, a few last-minute showstoppers appeared since 11.0-RC1 (and before RC1). One of the showstoppers has been fixed in 12-CURRENT, and merged to stable/11 and releng/11.0 that affected booting from large volumes: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139

Re: 11.0-RELEASE status update

On Fri, Sep 02, 2016 at 12:13:51AM +0300, Slawa Olhovchenkov wrote: > Do you planed to fix issuse with missied and delete libmap32.conf? > Is there a PR about this? This issue does not sound familiar, so I am not sure it is (or was) on our radar. Glen signature.asc Description: PGP

Re: 11.0-RC2 suspend/resume on thinkpad x201 kills poweroff

On Thu, Sep 08, 2016 at 12:48:28AM +0200, Philip Homburg wrote: > Hi, > > I found out that playing with suspend/resume (using acpiconf -s 3) on a > thinkpad x201 running 11.0-RC2 changes something in CMOS that prevents > poweroff from working. > > I managed to trigger the problem om two x201

Re: 11.0-RC2 suspend/resume on thinkpad x201 kills poweroff

On Thu, Sep 08, 2016 at 11:32:24PM +0200, Philip Homburg wrote: > The main culprit seems to be putting 'hw.acpi.reset_video=1' in > /boot/loader.conf > Yes, I have seen this cause problems on some (not all) hardware. > this causes resume to hang half way through. I managed to trigger > CMOS

11.0-RELEASE status update

There is one issue that was brought to our attention, which we are waiting for feedback before classifying as an EN candidate. Once we receive feedback, the 11.0-RELEASE schedule should be updated to reflect reality. At present, I am hopeful 11.0-RC3 builds should start 9/14/2016 at 00:00 UTC

Re: should aarch64 cross-build work at amd64?

On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > 24.09.2016 00:44, Boris Samorodov пишет: > > 24.09.2016 00:39, Glen Barber пишет: > >> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > >>> make[1]: /poudriere/jails/HEAD-aarch64/

Re: should aarch64 cross-build work at amd64?

On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: > In-tree binutils does not support the aarch64 architecture. Install the > aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. These lines are

Re: should aarch64 cross-build work at amd64?

On Sat, Sep 24, 2016 at 01:56:54AM +0300, Boris Samorodov wrote: > 24.09.2016 01:19, Glen Barber пишет: > > On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > >> 24.09.2016 00:44, Boris Samorodov пишет: > >>> 24.09.2016 00:39, Glen Barber пишет: > &

Re: 11.0-RELEASE Status Update

On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote: > On 6 October 2016 at 13:18, Glen Barber <g...@freebsd.org> wrote: > > the final release announcement is planned for Monday, October 10. > > suggestion: > update the schedule > https://www.freebsd.org/r

11.0-RELEASE Status Update

As many of you are aware, 11.0-RELEASE needed to be rebuilt to address several issues that were discovered after the release was built. Extra caution is being taken in testing the rebuilt releases, so at present, the final release announcement is planned for Monday, October 10. Thank you for

Re: 11.0-RELEASE-RC3

On Fri, Sep 16, 2016 at 03:10:48PM -0500, Antonio Olivares wrote: > There are new releases for RC3 I am running RC3 and want to update to > RC3 and I get errors retrieving new release. > > See attached file. > > Is there a way to update to RC3? > Do I build from source? > > Best Regards, > >

FreeBSD 11.0-RC3 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third RC build of the 11.0-RELEASE release cycle is now available. Installation images are available for: o 11.0-RC3 amd64 GENERIC o 11.0-RC3 i386 GENERIC o 11.0-RC3 powerpc GENERIC o 11.0-RC3 powerpc64 GENERIC64 o 11.0-RC3 sparc64 GENERIC o

Re: Delay with 11.0-RC2 builds

On Thu, Aug 18, 2016 at 11:30:24PM +, Glen Barber wrote: > Two issues have been brought to our attention, and as a result, 11.0-RC2 > builds will be delayed a day or two while these are investigated. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872 > https://b

[HEADS-UP] 11.0-RELEASE status update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear FreeBSD Community: Although the FreeBSD 11.0-RELEASE has not yet been officially announced, many have found images on the Project FTP mirrors. However, please be aware the final 11.0-RELEASE will be rebuilt and republished on the Project

[REVISED] [HEADS-UP] 11.0-RELEASE status update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear FreeBSD Community: [Corrected the date.] Although the FreeBSD 11.0-RELEASE has not yet been officially announced, many have found images on the Project FTP mirrors. However, please be aware the final 11.0-RELEASE will be rebuilt and

Re: should aarch64 cross-build work at amd64?

On Tue, Sep 27, 2016 at 09:46:29PM -0600, Ross Alexander wrote: > On Fri, 23 Sep 2016 22:19:15 +, Glenn Barber wrote: > > >On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > >> 24.09.2016 00:44, Boris Samorodov ?: > >> > 24.09.2016 00:39,

Re: status of and/or url to check base packages repo somewhere?

On Sun, Jun 25, 2017 at 10:30:53PM -0700, Jeffrey Bouquet wrote: > As the Subject: is there a canonical url to check, and a procedure in place > yet, to, > for instance, if one cannot buildworld on 12.0-CURRENT, to access the package > .txz or > whatever and 'pkg fetch ... pkg add ...'

Re: base packages, ino64 and upgrade

On Wed, May 24, 2017 at 03:47:47PM +0300, Boris Samorodov wrote: > Hi All, > > Does anyone know the procedure to upgrade for those using base packages? > 'pkg install FreeBSD-kernel-generic' (or whatever your kernel package is called), reboot, 'pkg upgrade'. Glen signature.asc Description:

Re: The futur of the roff toolchain

On Sun, May 21, 2017 at 02:57:33PM +0200, Baptiste Daroussin wrote: > No the problem left is documentations available in share/doc. > > I would like to push them elsewhere. Those documents are mostly useful for > historical reason (hence we want to keep them) but not really for daily use of >

HEADS-UP: release-releated documentation moving from base to doc repository

Hi, I have expressed my intent to move the release-related documents from the src tree to the doc tree in the past. This has been met with some resistance, but I think this change is far overdue at this point. The primary motivation behind this change is that if there is an error in

Re: VM images for 12.0-CURRENT showing checksum failed messages

On Wed, Oct 18, 2017 at 09:28:40AM -0700, John Baldwin wrote: > On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > > On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > > > On Tuesday, October 17, 2017 11:57:44 AM David Boyd wrote: > > > >

Re: VM images for 12.0-CURRENT showing checksum failed messages

On Wed, Oct 18, 2017 at 04:40:22PM +, Glen Barber wrote: > On Wed, Oct 18, 2017 at 09:28:40AM -0700, John Baldwin wrote: > > On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > > > On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > > > > O

Re: VM images for 12.0-CURRENT showing checksum failed messages

On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > On Tuesday, October 17, 2017 11:57:44 AM David Boyd wrote: > > The FreeBSD-12.0-CURRENT-amd64-20171012-r324542.vmdk image displays > > many checksum failed messages when booted. (see attachment). > > > > I think this started about

Re: Head build unsafe for /etc today

On Thu, Nov 02, 2017 at 07:23:27PM -0700, Steve Kargl wrote: > On Thu, Nov 02, 2017 at 07:08:50PM -0700, Bryan Drewery wrote: > > > On Nov 2, 2017, at 18:49, Steve Kargl > > > wrote: > > > You're making changes to the build infrastructure and you're > > > not

Re: make ftp failing

On Tue, Nov 07, 2017 at 11:39:01AM +, Roger Pau Monné wrote: > Hello, > > Since the end of last week `make -C release ftp` has been failing for > me, giving the following output (trimmed for convenience): > [...] > /usr/bin/ld: cannot find -lvers > cc: error: linker command failed with exit

Re: casper issues with pkgbase

On Wed, Nov 08, 2017 at 06:43:44AM +0800, Ben Woods wrote: > Hi everyone, > > I recently upgraded my FreeBSD 12-current machine which uses pkgbase from > r324720 to r325426, and it looks like an error has been introduced in the > naming of base packages for casper. > > Without having looked into

Re: [RFC] Deprecation and removal of the drm2 driver

On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > >Also as the Moore's law curve flattens expect the life of these > > > >older, but not so old, machines to live quiet some time. I > > > >believe we are

Re: [RFC] Deprecation and removal of the drm2 driver

On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > >Also as the Moore's law curve flattens expect the life of these > >older, but not so old, machines to live quiet some time. I > >believe we are talking sandy bridge and earlier? If that is > >corret Sandy bridge is still a very

Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver)

On Wed, May 30, 2018 at 08:29:57AM -0700, Rodney W. Grimes wrote: > > On 25 May 2018 at 04:51, Philip Homburg wrote: > > > > > > I have bad news and some good news. > > > > > > The bad news is that with this image the USB stick doesn't get recognized > > > as > > > a boot device. Same as with

Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

Hi, Could folks please help boot-test the most recent 12.0-CURRENT amd64 memstick images on various hardware? Note, this is not a request to install 12.0-CURRENT, only a boot-test with various system knobs tweaked. The most recent images are available at:

Re: VM images for 12.0-CURRENT showing checksum failed messages

On Wed, Oct 18, 2017 at 09:49:16AM -0700, John Baldwin wrote: > On Wednesday, October 18, 2017 04:40:22 PM Glen Barber wrote: > > On Wed, Oct 18, 2017 at 09:28:40AM -0700, John Baldwin wrote: > > > On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > > > >

Re: VM images for 12.0-CURRENT showing checksum failed messages

On Thu, Oct 19, 2017 at 01:39:11PM +, Glen Barber wrote: > On Wed, Oct 18, 2017 at 09:49:16AM -0700, John Baldwin wrote: > > On Wednesday, October 18, 2017 04:40:22 PM Glen Barber wrote: > > > First, mdconfig(8) is used to create a md(4)-backed disk, onto which > > >

Re: can't make installworld

On Wed, Aug 01, 2018 at 10:29:18AM -0400, AN wrote: > FreeBSD BSD12 12.0-CURRENT FreeBSD 12.0-CURRENT #16 r335386: Tue Jun > 19 19:57:51 EDT 2018 > root@BSD12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 > > # cat /etc/master.passwd | grep ntp > ntpd:*:123:123::0:0:NTP

[REVISED] Update to 12.0-RELEASE schedule

The 12.0-RELEASE schedule will slip while last-minute work-in-progress continues to be completed before branching stable/12. At present, the project branch used to update OpenSSL to version 1.1.1 is expected to be ready to merge to head at some point early next week. As such, to err on the side

[REVISED UPDATE] Update to 12.0-RELEASE schedule

The 12.0-RELEASE schedule will slip while last-minute work-in-progress is finalized before branching stable/12. At present, the project branch used to update OpenSSL to version 1.1.1 is expected to be ready to merge to head at some point early this week. As such, to err on the side of caution,

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

On Thu, Oct 11, 2018 at 09:05:52AM +0200, Raúl wrote: > Maybe related to recent Glen's Heads-UP? > > https://lists.freebsd.org/pipermail/freebsd-current/2018-October/071581.html > No, this is different, and more recent than the heads-up. I now see failures on powerpc, powerpc64, powerpcspe,

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

On Thu, Oct 11, 2018 at 03:38:47PM -0500, Justin Hibbits wrote: > On Thu, 11 Oct 2018 19:07:45 + > Glen Barber wrote: > > > On Thu, Oct 11, 2018 at 09:05:52AM +0200, Raúl wrote: > > > Maybe related to recent Glen's Heads-UP? > > > > > > https://l

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

On Thu, Oct 11, 2018 at 10:32:34PM +, Glen Barber wrote: > I still see a failure with this applied. > > ===> lib/libldns (obj,all,install) > /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: cannot find -lssl > --- libprivateldns.so.5.full --- > *** [libprivateldns.so

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

On Thu, Oct 11, 2018 at 10:55:46PM +, Glen Barber wrote: > On Thu, Oct 11, 2018 at 10:32:34PM +0000, Glen Barber wrote: > > I still see a failure with this applied. > > > > ===> lib/libldns (obj,all,install) > > /usr/obj/usr/src/powerpc.powerpc/tmp

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

On Thu, Oct 11, 2018 at 04:44:10PM -0500, Justin Hibbits wrote: > On Thu, 11 Oct 2018 17:32:21 -0400 > Jung-uk Kim wrote: > > > On 18. 10. 11., Justin Hibbits wrote: > > > On Thu, 11 Oct 2018 19:07:45 + > > > Glen Barber wrote: > > > > > &

FreeBSD 12.0-BETA2 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The second BETA build of the 12.0-RELEASE release cycle is now available. Please see the "SPECIAL NOTE" below regarding upgrading from FreeBSD 10.x and 11.x for important information regarding geli(4)-backed filesystems. Also note, pkg(8) builds

Re: FreeBSD 12.0-BETA2 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 One minor correction: On Sat, Oct 27, 2018 at 05:03:48PM +, Glen Barber wrote: > === SPECIAL NOTE === > This only affects systems that employ geli(4)-backed encrypted > filesystems and currently running 11.x or 10.x. Upgrades from >

Re: HEADS-UP: OpenSSL 1.1.1 in 12.0

On Sat, Oct 27, 2018 at 06:14:39PM +0200, David Marec wrote: > On 09/10/2018 23:34, Glen Barber wrote: > > OpenSSL has been updated to version 1.1.1 as of r339270. > > > > It is important to rebuild third-party packages before running: > > > > # make -C /usr/s

FreeBSD 12.0-BETA3 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third BETA build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-BETA3 amd64 GENERIC o 12.0-BETA3 i386 GENERIC o 12.0-BETA3 powerpc GENERIC o 12.0-BETA3 powerpc64 GENERIC64 o 12.0-BETA3 sparc64

FreeBSD 12.0-BETA1 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first BETA build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-BETA1 amd64 GENERIC o 12.0-BETA1 i386 GENERIC o 12.0-BETA1 powerpc GENERIC o 12.0-BETA1 powerpc64 GENERIC64 o 12.0-BETA1

FreeBSD 12.0-BETA4 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The fourth BETA build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-BETA4 amd64 GENERIC o 12.0-BETA4 i386 GENERIC o 12.0-BETA4 powerpc GENERIC o 12.0-BETA4 powerpc64 GENERIC64 o 12.0-BETA4

Update to 12.0-RELEASE schedule

The 12.0-RELEASE schedule has been updated, adding BETA4 to the schedule in order to provide additional testing for changes that fix a boot time issue, in addition to allowing more time for packages for arm and arm64 to finish building, before branching releng/12.0 and starting the RC phase of

Re: HEADS-UP: OpenSSL 1.1.1 in 12.0

On Wed, Oct 10, 2018 at 08:35:28PM -0400, Ed Maste wrote: > On Wed, 10 Oct 2018 at 18:11, O. Hartmann wrote: > > > > security/libssh > > This one is open as PR 228895. > I don't need to be personally CC'd on every port that fails to build. I'm keeping an eye on them. I do not need the extra

Re: Not sure if this is an important bug...

On Mon, Oct 08, 2018 at 07:12:59PM +, Poul-Henning Kamp wrote: > I tried running 12.0-BETA8 under bhyve on a Phenom-II+11.2 box and > it explodes because of an unemulated instruction: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232081 > > I have no idea what importance this has

Re: FreeBSD 12 Alpha8 install try to fetch at a wrong location

On Mon, Oct 08, 2018 at 08:45:35PM +0200, David Marec wrote: > Hi > > The FreeBSD 12 image installer that one can download at > https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/12.0/ > doesn't not fetch txz files from a correct location. > > By the fact, the installer try to fetch files

HEADS-UP: OpenSSL 1.1.1 in 12.0

OpenSSL has been updated to version 1.1.1 as of r339270. It is important to rebuild third-party packages before running: # make -C /usr/src delete-old && make -C /usr/src delete-old-libs Thank you for your patience while this work was in progress, and thank you to all involved for their hard

Update to 12.0-RELEASE schedule

The 12.0-RELEASE schedule will slip while we wait for some last-minute work-in-progress to be completed before branching stable/12. The most notable work-in-progress is upgrading the in-tree OpenSSL to version 1.1.1, to avoid being stuck with an outdated OpenSSL when 1.0.x reaches end of life on

FreeBSD 12.0-RC3 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third RC build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-RC3 amd64 GENERIC o 12.0-RC3 i386 GENERIC o 12.0-RC3 powerpc GENERIC o 12.0-RC3 powerpc64 GENERIC64 o 12.0-RC3 powerpcspe

FreeBSD 12.0-RC2 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The second RC build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-RC2 amd64 GENERIC o 12.0-RC2 i386 GENERIC o 12.0-RC2 powerpc GENERIC o 12.0-RC2 powerpc64 GENERIC64 o 12.0-RC2 powerpcspe

[UPDATE] Re: FreeBSD 12.0-RC2 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The freebsd-update(8) binary upgrade patches are now available for 12.0-RC2. The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as

Re: FreeBSD 12.0-RC2 Now Available

On Sun, Nov 25, 2018 at 06:56:29PM +0200, Sami Halabi wrote: > HI, > I went over the release notes and honestly I don't see what 12 brings new.. > I remember older versions were big change each in different aspect.. So > what is 12-Rel unique aspect VS 11 let's say? > The release notes are in

FreeBSD 12.0-RC1 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first RC build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-RC1 amd64 GENERIC o 12.0-RC1 i386 GENERIC o 12.0-RC1 powerpc GENERIC o 12.0-RC1 powerpc64 GENERIC64 o 12.0-RC1 powerpcspe

Re: SVN r346316 breaks build

On Wed, Apr 17, 2019 at 08:45:57PM -0400, Ed Maste wrote: > On Wed, 17 Apr 2019 at 17:31, Michael Butler > wrote: > > > > There seems to be a missing include here? > > > > ===> usr.bin/strings (obj,all,install) > > Building > > /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/strings/strings.o

Statement regarding employment change and roles in the Project

Dear FreeBSD community: As I have a highly-visible role within the community, I want to share some news. I have decided the time has come to move on from my role with the FreeBSD Foundation, this Friday being my last day. I have accepted a position within a prominent company that uses and

Re: New vm-image size is much smaller than previos

On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote: > > > On May 3, 2019, at 9:57 AM, Alan Somers wrote: > > > > See r346959. Before first boot, you should expand the image up to > > whatever size you want. growfs(8) will automatically expand the file > > system. > > -Alan > > > >

Re: FreeBSD Friday

On Fri, Nov 22, 2019 at 08:56:22PM +0100, Robert wrote: > Thank you. > Seems better to wait for 12-STABLE to be updated... Do you know how often > snapshots are built? Once a week. Glen signature.asc Description: PGP signature

Re: breakage at usr.sbin/jail/Makefile

On Wed, Nov 20, 2019 at 07:57:57PM -0800, Pete Wright wrote: > Hello, > looks like some of the recent commits to usr.sbin/jail/Makefile has broken > CURRENT.  I am getting this error when attempting a buildworld: > > ===> usr.sbin/jail (cleandir) > make[4]:

Re: breakage at usr.sbin/jail/Makefile

On Wed, Nov 20, 2019 at 08:18:52PM -0800, Pete Wright wrote: > > > On 11/20/19 8:13 PM, Glen Barber wrote: > > On Wed, Nov 20, 2019 at 07:57:57PM -0800, Pete Wright wrote: > > > Hello, > > > looks like some of the recent commits to usr.sbin/jail/Makefile has br

emulators/qemu-user-static linker error on 13-CURRENT r358890

13-CURRENT aarch64 GENERIC builds failed this week due to the dependent port emulators/qemu-user-static failing to build, which is used by the targets that create the cloud provider images (EC2, GCE, etc.). The error output from the port build is: ===> Configuring for

New FreeBSD snapshots available: main (20200903 c122cf32f2a)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 New FreeBSD development branch installation ISOs and virtual machine disk images have been uploaded to the FreeBSD Project mirrors. NOTE: These are the first snapshots built from the FreeBSD Git sources. Also note: The armv6 and armv7 builds

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > Hello, > > On Thu, 3 Sep 2020 15:02:45 + > Glen Barber wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > New FreeBSD development branch installation ISO

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > On Thu, 3 Sep 2020 16:00:51 + > Glen Barber wrote: > > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > > > > > Hello, > > > > > > On Thu,

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote: > On Thu, 10 Sep 2020 16:36:44 + > Glen Barber wrote: > > > On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > > > On Thu, 3 Sep 2020 16:00:51 + > > > Glen Barber wrote: &g

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 04:53:30PM +, Glen Barber wrote: > On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote: > > Which port commit and which board ? There haven't been a commit in the > > u-boot ports or rpi-firmware this a month now so I fails to understand &

Re: documentation on release build process change (svn -> git)?

On Fri, Aug 28, 2020 at 01:32:06PM -0400, Michael Butler wrote: > Is there any documentation around the changes to the release build > system from SVN to GIT? > > I currently keep a mirrored SVN repo and the revised release scripts > seem not to have that as a build option. Can I still use this

Re: documentation on release build process change (svn -> git)?

On Fri, Aug 28, 2020 at 05:43:07PM +, Glen Barber wrote: > On Fri, Aug 28, 2020 at 01:32:06PM -0400, Michael Butler wrote: > > Is there any documentation around the changes to the release build > > system from SVN to GIT? > > > > I currently keep a mirrored SVN r

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 11:34:15AM -0400, Michael Butler wrote: > On 8/29/20 11:14 AM, Glen Barber wrote: > > NOPORTS=yes is the problem, and I forgot to address it before merging > > the project branch back. Please try with r364956. > > Trying now but, in the interim, I n

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 03:51:23PM +, Glen Barber wrote: > On Sat, Aug 29, 2020 at 11:34:15AM -0400, Michael Butler wrote: > > On 8/29/20 11:14 AM, Glen Barber wrote: > > > NOPORTS=yes is the problem, and I forgot to address it before merging > > > the proje

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 10:30:24AM -0400, Michael Butler wrote: > On 8/28/20 1:44 PM, Glen Barber wrote: > > > Note, not entirely tested, however, since future snapshots and 13.0 will > > be exclusively built from the git sources. > > When building with .. > > ## S

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 04:38:05PM -0400, Michael Butler wrote: > On 8/29/20 12:04 PM, Glen Barber wrote: > > On Sat, Aug 29, 2020 at 03:51:23PM +0000, Glen Barber wrote: > >> I added a way to update an existing tree in r364959. I have only done > >> very trivial test

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 05:21:16PM -0400, Michael Butler wrote: > On 8/29/20 5:17 PM, Glen Barber wrote: > > On Sat, Aug 29, 2020 at 04:38:05PM -0400, Michael Butler wrote: > >> The build-from-existing mode fails with .. > >> > >> imb@vm01:/usr/src/release>

Re: documentation on release build process change (svn -> git)?

On Sat, Aug 29, 2020 at 09:40:17PM +, Glen Barber wrote: > On Sat, Aug 29, 2020 at 09:30:02PM +0000, Glen Barber wrote: > > On Sat, Aug 29, 2020 at 05:21:16PM -0400, Michael Butler wrote: > > > On 8/29/20 5:17 PM, Glen Barber wrote: > > > > On Sat, Aug 29, 202

<    1   2   3   4   5   6   >