Re: buildworld errors at outset on fresh svn checkout

2016-10-07 Thread Kevin Oberman 
On Thu, Oct 6, 2016 at 10:16 PM, Scott Bennett  wrote:

>  I'm running into a problem in updating my 10-STABLE system from
> source.
> A "make buildworld" quits immediately.  I tried a fresh svn checkout for
> base/stable/10 and then tried to run buildworld again, but got the same
> error.
> I've been scratching my head over this for hours, but must be missing
> something
> simple.
>  I have ccache installed and have been using it for a fairly long time
> now.
> My /etc/src.conf contains just two lines:
>
> PORTS_MODULES=multimedia/cuse4bsd-kmod sysutils/pefs-kmod #
> emulators/virtualbox-ose-kmod
> WITH_LLDB=yes
>
> My /etc/make.conf is rather longer, so I'll append it following .sig below.
>
>  Here's what happens.
>
> Script started on Thu Oct  6 23:31:47 2016
> hellas# cd /usr/src
> hellas# nice make buildworld
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1113: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1122: if-less endif
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1144: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1161: if-less endif
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1183: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1190: if-less endif
> bmake: fatal errors encountered -- cannot continue
> *** Error code 1
>
> Stop.
> make: stopped in /usr/src
> hellas# exit
> exit
>
> Script done on Thu Oct  6 23:37:00 2016
>
>  This just started happening after my machine had been down for a
> couple
> of days after a hang that damaged stuff in /usr/home.  I had already
> restored
> /usr/local from backups before narrowing down the weird behavior I was
> seeing
> in wmaker to /usr/home corruption.  So /usr/home has now been restored to
> good condition, too, but perhaps I need to restore something else as well.
> This mess was part of my justification to myself for the fresh checkout of
> /usr/src, but that doesn't seem to have made any difference in the
> buildworld
> failure.
>  If anyone else can see what's wrong and clue me in, I'd be grateful.
> I'm subscribed to the digest for this list, so please Cc: me directly, so
> I'll get replies right away.
> Thanks in advance!
>
>
>   Scott Bennett, Comm. ASMELG, CFIAG
>

Could something else have gotten corrupted?

> ls -i /bin/[
65795 /bin/[
> ls -i /bin/test
65795 /bin/test

The values (inode) will not match these, but must be identical.

'[' needs to be a hard link to test. I'm suspicious that something happened
to this link. If this is the case, other corruption may have occurred, but,
if you can re-create the hardlink (ln /bin/test /bin/[) and successfully
make buildworld  and make buildkernel, it's likely that you can reinstall
the system and the system will be fine. Of course, things could be damaged
in the installed ports, too.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Your buildworld system is pulling userland libraries/headers

2016-10-07 Thread Nathan Lay 
Hello once again FreeBSD-stable,
While upgrading from FreeBSD 10-STABLE and later updating my FreeBSD
11-STABLE system, I noticed that your build system is pulling headers and
libraries from the userland rather than the /usr/src tree. This can't
possibly be intended. I kind of figured with recent news of delayed
released you might have realized this. After all, _FOR EXAMPLE_ (may not
reflect reality), who wants to accidentally include userland's older
version of OpenSSL headers and link with userland's older version of
OpenSSL?

I can cope with this by manually copying headers from /usr/src/sys/sys and
/usr/src/include to their appropriate locations and/or installing the newer
library manually and then restarting the build. But others may not be so
familiar with FreeBSD. And I did manage to get FreeBSD 11-STABLE up and
running just fine eventually.

But just a few days ago, I updated SVN to rebuild world and kernel
following the news of your delayed release and found libprocstat failing to
compile. And it failed to compile because it was including
/usr/include/ufs/ufs/extattr.h instead of
/usr/src/sys/sys/ufs/ufs/extattr.h. This is very disturbing to me. During
the FreeBSD 10 updating phase, I saw way more examples of this with even
unresolved reference errors during linking since the build system was
trying to link with userland's FreeBSD 10 libraries! I can think of two
recurring examples: devctl and procstat.

I also noticed your build system liked to now put modules in /boot/modules.
I was hacking if_ath and none of my changes were working. Well, it was
because kldload was loading the unchanged one in /boot/kernel rather than
the one now being installed in /boot/modules. That's a really nasty
surprise. I probably spent a couple hours figuring that out :)

Best regards,
Nathan Lay

P.S. FreeBSD 11 is running great! Great job!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Marcelo Gondim 

Em 06/10/2016 17:18, Glen Barber escreveu:

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 your patience in waiting for 11.0-RELEASE.

Glen
On behalf of:   re@

Great job Glen. The important to a sysadmin is an increasingly stable 
system. When he is ready, it will be ready.


Thanks!  :)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Bruce A. Mah 
If memory serves me right, Cassiano Peixoto wrote:
> Looks we have some import issues to be fixed before 11-RELEASE. I have
> another one that nobody cares:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
> and
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413
> 
> It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
> crash.
> 
> IMHO would be better to release a stable product instead of keep the
> schedule.

There's always "just one more bug".  If the FreeBSD Project waited until
the code was bug-free there'd be no releases at all.

It's the Release Engineering team's job to make the call on which bugs
are worth holding up a release for and which aren't, when workarounds
are acceptable and when they need to try to pursuade a developer to
diagnose and implement a real fix, etc.  They need to use their
judgement about a number of factors such as severity, number of users
impacted, availability of developers, and so on.  The schedule is also a
factor, but it's never just for the sake of adhering to the schedule.

Bruce
(Ex-RE team member)

> On Fri, Oct 7, 2016 at 8:32 AM, Alexander Shitov  wrote:
> 
>> Op 06/10/2016 om 22:18 schreef Glen Barber:
>>> 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 your patience in waiting for 11.0-RELEASE.
>>>
>>> Glen > On behalf of: re@ >
>>
>> Is fix for Hyper-V bug "virtual disk being detached from the bus"
>> (https://reviews.freebsd.org/D7693)  included in final build?
>> PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721
>>
>> It will be big disappointment if 11.0-RELEASE will became incompatible
>> with Hyper-V.
>>
>> ---
>> Best Regards,
>> Alexander
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 




signature.asc
Description: OpenPGP digital signature

11.0-RELEASE and mbuf-related trace

2016-10-07 Thread Slawa Olhovchenkov 
Has anybody comment on this?
During debug tcp-related freeze I am collect starnge mbuf-related
freeze (this is like recursive lock to UMA Slabs keg) and trace:

last pid: 49575;  load averages:  2.00,  2.05,  3.75up 1+01:12:08  22:13:42
853 processes: 15 running, 769 sleeping, 35 waiting, 34 lock
CPU 0:   0.0% user,  0.0% nice,  0.0% system,  100% interrupt,  0.0% idle
CPU 1:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 2:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 3:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 4:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 5:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 6:   0.0% user,  0.0% nice,  0.4% system,  0.0% interrupt, 99.6% idle
CPU 7:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 8:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 9:   0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
CPU 10:  0.0% user,  0.0% nice,  0.4% system,  0.0% interrupt, 99.6% idle
CPU 11:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 8659M Active, 8385M Inact, 107G Wired, 1325M Free
ARC: 99G Total, 88G MFU, 10G MRU, 32K Anon, 167M Header, 529M Other
Swap: 32G Total, 32G Free

# procstat -k -k 1046
  PIDTID COMM TDNAME   KSTACK
 1046 100686 nginx-mi_switch+0xd2 
critical_exit+0x7e lapic_handle_timer+0xb1 Xtimerint+0x8c 
__mtx_lock_sleep+0x168 zone_fetch_slab+0x47 zone_import+0x52 
zone_alloc_item+0x36 keg_alloc_slab+0x63 keg_fetch_slab+0x16e 
zone_fetch_slab+0x6e zone_import+0x52 uma_zalloc_arg+0x36e m_getm2+0x14f 
m_uiotombuf+0x64 sosend_generic+0x356 soo_write+0x42 dofilewrite+0x87

Some info below posible incorectly decoded.

(kgdb) thread 809
[Switching to thread 809 (Thread 100686)]
(kgdb) bt
#0  sched_switch (td=0xf8014485f500, newtd=0xf8011422b000, 
flags=) at /usr/src/sys/kern/sched_ule.c:1973
#1  0x804a8d92 in mi_switch (flags=, newtd=0x0) at 
/usr/src/sys/kern/kern_synch.c:455
#2  0x804a6bee in critical_exit () at 
/usr/src/sys/kern/kern_switch.c:218
#3  0x80771701 in lapic_handle_timer (frame=0xfe2021699340) at 
/usr/src/sys/x86/x86/local_apic.c:1184
#4  
#5  0x804de424 in lock_delay (la=) at 
/usr/src/sys/kern/subr_lock.c:127
#6  0x80484dc8 in __mtx_lock_sleep (c=, 
tid=18446735283061126400, opts=, file=, 
line=) at /usr/src/sys/kern/kern_mutex.c:514
#7  0x806a4257 in zone_fetch_slab (zone=0xf8207ffe6000, 
keg=0xf8207ffe7180, flags=1) at /usr/src/sys/vm/uma_core.c:2371
#8  0x806a4312 in zone_import (zone=, bucket=, max=, flags=) at 
/usr/src/sys/vm/uma_core.c:2501
#9  0x806a0986 in zone_alloc_item (zone=0xf8207ffe6000, udata=0x0, 
flags=1) at /usr/src/sys/vm/uma_core.c:2591
#10 0x806a2463 in keg_alloc_slab (keg=0xf8010f9ecd80, 
zone=0xf80114236000, wait=1) at /usr/src/sys/vm/uma_core.c:964
#11 0x806a48ce in keg_fetch_slab (keg=, zone=, flags=) at /usr/src/sys/vm/uma_core.c:2343
#12 0x806a427e in zone_fetch_slab (zone=, keg=, flags=) at /usr/src/sys/vm/uma_core.c:2375
#13 0x806a4312 in zone_import (zone=, bucket=, max=, flags=) at 
/usr/src/sys/vm/uma_core.c:2501
#14 0x806a147e in zone_alloc_bucket (flags=2, zone=, 
udata=) at /usr/src/sys/vm/uma_core.c:2531
#15 uma_zalloc_arg (zone=, udata=0xf8105a700300, flags=2) at 
/usr/src/sys/vm/uma_core.c:2257
#16 0x8048231f in m_getjcl (how=2, type=1, flags=, 
size=4096) at /usr/src/sys/kern/kern_mbuf.c:829
#17 m_getm2 (m=, len=, how=, 
type=, flags=) at 
/usr/src/sys/kern/kern_mbuf.c:861
#18 0x80516044 in m_uiotombuf (uio=0xf818dcfbaec0, how=60, 
len=, align=0, flags=0) at /usr/src/sys/kern/uipc_mbuf.c:1535
#19 0x8051ce56 in sosend_generic (so=, addr=0x0, 
uio=, top=, control=, 
flags=, td=) at 
/usr/src/sys/kern/uipc_socket.c:1332
#20 0x804fd872 in soo_write (fp=, 
uio=0xf818dcfbaec0, active_cred=, flags=, 
td=) at /usr/src/sys/kern/sys_socket.c:146
#21 0x804f5c97 in fo_write (fp=, uio=0xf818dcfbaec0, 
active_cred=0xc0, flags=0, td=) at /usr/src/sys/sys/file.h:311
#22 dofilewrite (td=0xf8014485f500, fd=1531, fp=0xf80ac09fa960, 
auio=0xf818dcfbaec0, offset=, flags=0) at 
/usr/src/sys/kern/sys_generic.c:590
#23 0x804f5978 in kern_writev (td=0xf8014485f500, fd=1531, 
auio=0xf818dcfbaec0) at /usr/src/sys/kern/sys_generic.c:506
#24 0x804f5be6 in sys_writev (td=0xf8014485f500, 
uap=0xfe2021699a40) at /usr/src/sys/kern/sys_generic.c:491
#25 0x806e4051 in syscallenter (td=0xf8014485f500, sa=) at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:135
#26 amd64_syscall (td=0xf8014485f500, traced=0) at 
/usr/src/sys/amd64/amd64/trap.c:942

# vmstat -M /var/crash/vmcore.1 -z| grep -i mbuf
mbuf_packet:256,

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Glen Barber 
On Fri, Oct 07, 2016 at 10:52:37AM +0200, Johan Hendriks wrote:
> Op 06/10/2016 om 22:18 schreef Glen Barber:
> > 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 your patience in waiting for 11.0-RELEASE.
> >
> >
> Is the aws bug included in the final build? It would be nice if it is
> included and not being an Eratta. I think a lot of people are going to
> update there servers, and then read the announcement.
> Just like they install the RELEASE even if there is no official release
> post about the release.
> 

No, the problem was discovered far too late.  It will be noted in the
errata document and the announcement for people to wait until the EN for
this.

Glen



signature.asc
Description: PGP signature

Re: 11.0-RELEASE Status Update

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

I thought I did, but it looks like a local network hiccup caused the
commit to fail.

Fixing.  Thanks.

Glen



signature.asc
Description: PGP signature

Re: 11.0-RELEASE Status Update

2016-10-07 Thread jungle Boogie 
On 6 October 2016 at 13:18, Glen Barber  wrote:
> the final release announcement is planned for Monday, October 10.

suggestion:
update the schedule
https://www.freebsd.org/releases/11.0R/schedule.html



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

The best tool for automation marketing

2016-10-07 Thread iMarketing Center 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Cassiano Peixoto 
Looks we have some import issues to be fixed before 11-RELEASE. I have
another one that nobody cares:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413

It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
crash.

IMHO would be better to release a stable product instead of keep the
schedule.


On Fri, Oct 7, 2016 at 8:32 AM, Alexander Shitov  wrote:

> Op 06/10/2016 om 22:18 schreef Glen Barber:
> > 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 your patience in waiting for 11.0-RELEASE.
> >
> > Glen > On behalf of: re@ >
>
> Is fix for Hyper-V bug "virtual disk being detached from the bus"
> (https://reviews.freebsd.org/D7693)  included in final build?
> PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721
>
> It will be big disappointment if 11.0-RELEASE will became incompatible
> with Hyper-V.
>
> ---
> Best Regards,
> Alexander
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Reproducible panic - Going nowhere without my init!

2016-10-07 Thread Konstantin Belousov 
On Fri, Oct 07, 2016 at 08:32:24AM +1000, Andy Farkas wrote:
> With your latest patch applied, I ran through my procedure more
> than a dozen times and no panics!
> 
> Any explanation why sleep(STALL_TIMEOUT) as apposed to a
> bunch of sleep(1)'s tickles the panic?
What happened was sleep() got interrupted by a signal.

Normally reboot(8) stops init with SIGTSTP, then kill processes, then
calls reboot(2). reboot(8) does not and cannot get acknowledges for the
receipts of the signals by signalled processes, which indeed may result
in the sleep interruption if other signal is delivered to init before
SIGTSTP.

Patch does not add 'just bunch of sleeps'. The code in the patch ensures
that _exit() is called not earlier than STALL_TIMEOUT from the moment
of detection of the shell exit, by reissuing sleep(). I changed the
argument to 1 second to avoid situation where we e.g. sleep for 15 secs,
get interrupt and then sleep for whole 30 secs.  The overtime with
sleep(1) is limited to 1 second.

> 
> Also, it is definitely not sleeping for 30 seconds. I guess some
> event interrupts the sleep loop?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 stuck on high network load

2016-10-07 Thread Slawa Olhovchenkov 
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote:

>  Thanks again to Slawa, for his numerous debug reports and always
> questioning my explanations.  His last question directly led to this
> finding.  He is testing a quick workaround patch to check if there is more.

Thanks very match! You was very helpful, explaining detail of FreeBSD
TCP code and gave a lot of work to this issuse, I'm appreciate all
your help!
Thanks again!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.0-RELEASE Status Update

2016-10-07 Thread Alexander Shitov 
Op 06/10/2016 om 22:18 schreef Glen Barber:
> 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 your patience in waiting for 11.0-RELEASE.
>
> Glen > On behalf of: re@ >

Is fix for Hyper-V bug "virtual disk being detached from the bus"
(https://reviews.freebsd.org/D7693)  included in final build?
PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721

It will be big disappointment if 11.0-RELEASE will became incompatible
with Hyper-V.

---
Best Regards,
Alexander
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

O Presente que o seu filho merece está aqui!

2016-10-07 Thread Netself 

   
   Caso no esteja visualizando corretamente esta 
mensagem, acesse aqui.













A Odontopediatria  a especialidade que cuida da 
sade bucal do seu filho desde a amamentao. Com um plano 
Dental Kids, voc conta com os melhores especialistas da rea e uma 
cobertura perfeita para o seu filho sorrir desde os primeiros meses de vida.


Conhea nossos benefcios:


 Rede diferenciada de especialistas em 
Odontopediatria;

 Programas peridicos de preveno e 
promoo da sade bucal para crianas;

 Sem limite de utilizao;

 Aprovaoonlinedos tratamentos 
cobertos;

 Clnicas de urgncia 24h;

 Carteirinha virtual;

 Carncia de apenas 24h para pagamentos no 
carto de crdito ou boleto anual;

 Aditivo SOS Dental  atendimento domiciliar em 
casos de urgncias*.






















Contratao totalmenteonline. Mais facilidade 
para voc.


  simples e rpido. Toda a compra  
realizada em apenas 3 passos;

 Ao optar pelo pagamento no carto de crdito, 
voc ganha desconto de 15% e carncia de 24h para todos os 
procedimentos cobertos;

 Parcelamento em 1, 2, 3, 4, 6 ou 12 vezes, sem juros, 
nos cartes Visa ou MasterCard;

 Burocracia zero  voc no precisa 
enviar nenhum documento para a Amil Dental no ato da contratao***.









CONSULTE SEU CORRETOR

Re: 11.0-RELEASE Status Update

2016-10-07 Thread Johan Hendriks 


Op 06/10/2016 om 22:18 schreef Glen Barber:
> 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 your patience in waiting for 11.0-RELEASE.
>
> Glen
> On behalf of: re@
>
Is the aws bug included in the final build? It would be nice if it is
included and not being an Eratta. I think a lot of people are going to
update there servers, and then read the announcement.
Just like they install the RELEASE even if there is no official release
post about the release.

regards,
Johan
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"