John Baldwin writes:
> -[8] In order to have a kernel that can run the 4.x binaries needed to
> -do an installworld, you must include the COMPAT_FREEBSD4 option in
> -your kernel. Failure to do so may leave you with a system that is
> -hard to boot to recover. A similar kern
On Wed, Jan 2, 2019, 1:42 PM John Baldwin On 12/31/18 12:08 PM, Warner Losh wrote:
> > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone >
> >> Does this mean that it's currently impossible to build a world with
> >> debug symbols?
> >>
> >
> > Yes. Clang is simply too big until 64 bit offset support goes
On 1/2/19 1:31 PM, Robert Huff wrote:
>
> John Baldwin writes:
>
>> >> [8] In order to have a kernel that can run the 4.x binaries
>> >> needed to do an installworld, you must include the
>> >> COMPAT_FREEBSD4 option in your kernel. [...]
>>
>> > No, COMPAT_FREEBSD4 is not needed. Maybe CO
John Baldwin writes:
> >> [8] In order to have a kernel that can run the 4.x binaries
> >> needed to do an installworld, you must include the
> >> COMPAT_FREEBSD4 option in your kernel. [...]
>
> > No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed.
>
> Yes, that te
On 1/2/19 12:02 PM, Kurt Jaeger wrote:
> Hi!
>
>> FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64
>>
>> to CURRENT (as of last midnight.
>> Does this, in src/UPDATING:
>>
>> [8] In order to have a kernel that can run the 4.x binaries
>> needed to do an insta
On 12/31/18 12:08 PM, Warner Losh wrote:
> On Mon, Dec 31, 2018, 1:36 PM Ryan Stone
>> Does this mean that it's currently impossible to build a world with
>> debug symbols?
>>
>
> Yes. Clang is simply too big until 64 bit offset support goes in.
We actually build clang (and llvm) with stripped
Hi!
> FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64
>
> to CURRENT (as of last midnight.
> Does this, in src/UPDATING:
>
> [8] In order to have a kernel that can run the 4.x binaries
> needed to do an installworld, you must include the
> COMPAT
I'm updating a machine from:
FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64
to CURRENT (as of last midnight.
Does this, in src/UPDATING:
[8] In order to have a kernel that can run the 4.x binaries
needed to do an installworld, you mu
On 1/2/19 4:57 PM, Hans Petter Selasky wrote:
On 1/2/19 4:47 PM, Matthias Apitz wrote:
After card removal and insert devd(8) starts a new pcsd:
Does pcsd install this devd(8) rule? I thought pcsd would no longer need
to be restarted. >
Let's move this thread freebsd-usb only.
Have a look h
On 1/2/19 4:47 PM, Matthias Apitz wrote:
After card removal and insert devd(8) starts a new pcsd:
Does pcsd install this devd(8) rule? I thought pcsd would no longer
need to be restarted.
--HPS
___
freebsd-current@freebsd.org mailing list
https://l
El día miércoles, enero 02, 2019 a las 12:37:37p. m. +0100, Hans Petter Selasky
escribió:
> > Nothing. Only on boot it sees the card:
>
> And you are using the latest version of pcsd ?
Yes. Compiled with all ports from December 23.
>
> > Jan 2 11:25:39 c720-r342378 kernel: ugen0.1: <0x8086 X
On 1/2/19 11:48 AM, Matthias Apitz wrote:
El día miércoles, enero 02, 2019 a las 09:44:06a. m. +0100, Hans Petter Selasky
escribió:
On 1/1/19 2:51 PM, Matthias Apitz wrote:
Now with r342378, it works only after boot but not after withdraw/re-insert
anymore. To separate the problem from GnuPG
On 2/01/2019 4:56 pm, Matthew Macy wrote:
I just updated world/kernel/ports to today's HEAD and packages and
pkg "upgraded" chrome to be broken in this way. This isn't an isolated
issue.
On Tue, Jan 1, 2019 at 9:55 PM Matthew Macy wrote:
I just updated world/kernel/ports to today's HEAD and
I just updated world/kernel/ports to today's HEAD and packages and
pkg "upgraded" chrome to be broken in this way. This isn't an isolated
issue.
On Tue, Jan 1, 2019 at 9:53 PM Matthias Apitz wrote:
>
> El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert
> escribió:
>
> > I
El día miércoles, enero 02, 2019 a las 09:44:06a. m. +0100, Hans Petter Selasky
escribió:
> On 1/1/19 2:51 PM, Matthias Apitz wrote:
> > Now with r342378, it works only after boot but not after withdraw/re-insert
> > anymore. To separate the problem from GnuPG and it's software stack, I have
> >
On 1/1/19 2:51 PM, Matthias Apitz wrote:
Now with r342378, it works only after boot but not after withdraw/re-insert
anymore. To separate the problem from GnuPG and it's software stack, I have
here some
small tests with usbconfig(8). First usbconfig reads fine the bus, but then
it takes 3-5 minu
16 matches
Mail list logo