-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 16 Jan 2019 18:33:36 +0100
Tijl Coosemans schrieb:
> On Wed, 16 Jan 2019 15:23:40 +0100 "O. Hartmann"
> wrote:
> > We have an experimental IPV6 network and within this network, FreebSD
> > CURRENT
> > (r343087) is acting as a CUPS print s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275
Oleksandr Tymoshenko changed:
What|Removed |Added
CC||go...@freebsd.org
Hi!
> > > Well no longer needed as puc0 has found and allocated the
> > > device(s) which would of shown up had you done this before
> > > you fixed puc0 to find them.
> >
> > The problem is that the found 4 uarts are not 8 uarts, and they do not
> > seem to work (tested using kermit), either 8-(
> Hi!
>
> > Well no longer needed as puc0 has found and allocated the
> > device(s) which would of shown up had you done this before
> > you fixed puc0 to find them.
>
> The problem is that the found 4 uarts are not 8 uarts, and they do not
> seem to work (tested using kermit), either 8-(
But yo
On Mon, 2019-01-21 at 10:17 -0500, David Boyd wrote:
> On Mon, 2019-01-21 at 10:37 +0100, Trond Endrestøl wrote:
> > On Sun, 20 Jan 2019 13:09-0500, David Boyd wrote:
> >
> > > 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled.
> > >
> > > Running in VirtualBox 6.0.2.
> > >
> > > The
On Mon, 2019-01-21 at 10:37 +0100, Trond Endrestøl wrote:
> On Sun, 20 Jan 2019 13:09-0500, David Boyd wrote:
>
> > 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled.
> >
> > Running in VirtualBox 6.0.2.
> >
> > The identical configuration running 12.0-RELEASE-p2, 12.0-STABLE,
> > 11
On 21.01.2019 15:59, Toomas Soome wrote:
> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
loader.efi lives on ESP partition, do I understand it right? So, it
could not be damaged with "bad" upgrade?
>>>
>>> It could, unless the backup is created.
>> Does it l
> On 21 Jan 2019, at 14:45, Lev Serebryakov wrote:
>
> On 21.01.2019 15:39, Toomas Soome wrote:
>
Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
>>> loader.efi lives on ESP partition, do I understand it right? So, it
>>> could not be damaged with "bad" upgrade?
>>
On 21.01.2019 15:39, Toomas Soome wrote:
>>> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
>> loader.efi lives on ESP partition, do I understand it right? So, it
>> could not be damaged with "bad" upgrade?
>
> It could, unless the backup is created.
Does it live on code
> On 21 Jan 2019, at 14:15, Lev Serebryakov wrote:
>
> On 20.01.2019 20:05, Warner Losh wrote:
>
>> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
> loader.efi lives on ESP partition, do I understand it right? So, it
> could not be damaged with "bad" upgrade?
>
> --
On 20.01.2019 20:05, Warner Losh wrote:
> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
loader.efi lives on ESP partition, do I understand it right? So, it
could not be damaged with "bad" upgrade?
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signa
On 20.01.2019 21:09, David Boyd wrote:
> 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled.
>
> Running in VirtualBox 6.0.2.
>
> The identical configuration running 12.0-RELEASE-p2, 12.0-STABLE, 11.2-
> RELEASE-p8 and 11.2-STABLE do not exhibit this behavior.
>
> This (VM) is a test
On Sun, 20 Jan 2019 13:09-0500, David Boyd wrote:
> 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled.
>
> Running in VirtualBox 6.0.2.
>
> The identical configuration running 12.0-RELEASE-p2, 12.0-STABLE, 11.2-
> RELEASE-p8 and 11.2-STABLE do not exhibit this behavior.
>
> This (VM
Hi!
> >> > Well no longer needed as puc0 has found and allocated the
> >> > device(s) which would of shown up had you done this before
> >> > you fixed puc0 to find them.
> >> The problem is that the found 4 uarts are not 8 uarts, and they do not
> >> seem to work (tested using kermit), either 8-
14 matches
Mail list logo