On 10 Jan 2018, at 18:53, Baptiste Daroussin wrote:
>
> I need to figure out a mechanism to make this simpler to handle to upgrade of
> base system while keeping this safety belt for users.
>
> Any idea is welcome
I believe the apt approach to this is to have a different verb (distupgrade vs
u
On Wed, 2018-01-10 at 19:53 +0100, Baptiste Daroussin wrote:
> On Wed, Jan 10, 2018 at 09:29:04PM +0300, Boris Samorodov wrote:
> >
> > Hi All,
> >
> > I use self built base packages. Seems that I have a problem with pkg.
> > Today I've got this:
> > ===
> > % sudo pkg update -f
> > Updating Free
On Thu, Jan 11, 2018 at 08:57:34AM -0700, Ian Lepore wrote:
> On Wed, 2018-01-10 at 19:53 +0100, Baptiste Daroussin wrote:
> > On Wed, Jan 10, 2018 at 09:29:04PM +0300, Boris Samorodov wrote:
> > >
> > > Hi All,
> > >
> > > I use self built base packages. Seems that I have a problem with pkg.
> >
https://reviews.freebsd.org/D13832 <--- test this update
I'd like to get some feedback from AMD cpu users on this update. I've
restructured and undone a few things that may have been keeping folks
using this port from getting their runtime cpu microcode updates.
After installing the port, grab
Dear FreeBSD Community,
This is the last call for submissions for the 2017Q4 FreeBSD Quarterly
Status Update. The deadline for submissions is January 14, 2018,
for work done in October through December.
Status report submissions do not need to be very long. They may be
about anything happening
On 2018-Jan-6, at 2:02 PM, Mark Millard wrote:
> On 2018-Jan-4, at 7:32 PM, Mark Millard wrote:
>
>> Darren Reed darrenr at freebsd.org wrote on
>> Thu Jan 4 11:56:29 UTC 2018 :
>>
>>> Most people are only talking about meltdown which doesn't hit AMD.
>>> spectre impacts *both* Intel and AMD.
When building just checked out sources of Revision: 327866 and try to
buildworld with
WITH_LLD_IS_LD and/(or not) set
WITH_LLD_BOOTSTRAP
AND with make -j X, X>1,
the build process fails on several CURRENT systems right now with musterious
errors regarding crt1.o missing or not linkable:
[...]