Jonathan, just wanted to report the patch worked. The card is up and
running. Many thanks.
On Fri, Jul 16, 2021 at 10:03:47PM -0400, Adam Stouffer wrote:
> On Fri, Jul 16, 2021 at 6:47 PM Jonathan Matthew wrote:
> >
> >
> > I think the problem here is that we don't check if msi is enabled
> > before deciding we can use msix. Can you try this diff out?
> > I wrote this after seeing a si
On Sat, Jul 17, 2021 at 11:20 AM Theo de Raadt wrote:
>
> Instead, we are focusing on 99% of the use cases.
I hardly think that wanting to override your ISP's name servers is
outside of the 99% use cases. Of course it wouldn't be the first time
I am wrong.
> You might want to look into using unw
On 2021-07-17, Sonic wrote:
> Ah yes, my bad, had a line without the parens around the dhcp
> interface reference.
> This issue is resolved.
> Oddly enough it never affected many previous snapshots which used
> dhcpcd in place of dhcpleased.
OpenBSD never had dhcpcd in base, if you had configured
Philip Guenther schrieb am Samstag, 17. Juli 2021 um 11:09:
> On Fri, Jul 16, 2021 at 11:49 PM podolica wrote:
>
>> On my OpenBSD installation (6.9) one of the log files created by login(1)
>> seems to be a binary file:
>> $ less /var/log/failedlogin
>> "failedlogin" may be a binary file. See it
Sonic wrote:
> On Fri, Jul 16, 2021 at 10:35 PM Theo de Raadt wrote:
> > We are moving from a model where dhclient on 1 interface believes it is
> > MASTER of /etc/resolv.conf and a bunch of system aspects, and the
> > userbase is familiar with a pile of hacky control knobs in
> > dhclient.conf.
On Fri, Jul 16, 2021 at 10:35 PM Theo de Raadt wrote:
> We are moving from a model where dhclient on 1 interface believes it is
> MASTER of /etc/resolv.conf and a bunch of system aspects, and the
> userbase is familiar with a pile of hacky control knobs in
> dhclient.conf.
>
> Towards a model wher
Hi,
podolica wrote on Sat, Jul 17, 2021 at 12:36:05PM +:
> Philip Guenther schrieb am 17. Juli 2021 um 11:09:
>> That file is specific to the 'login' command, specifically the
>> source file /usr/src/usr.bin/login/failedlogin.c and consists of
>> an array of the 'badlogin' structure specifie
On Fri, Jul 16, 2021 at 6:47 PM Jonathan Matthew wrote:
>
>
> I think the problem here is that we don't check if msi is enabled
> before deciding we can use msix. Can you try this diff out?
> I wrote this after seeing a similar report somewhere, but I can't find
> it now.
>
> Index: pci.c
> =
Hi all,
On my OpenBSD installation (6.9) one of the log files created by login(1)
seems to be a binary file:
$ less /var/log/failedlogin
"failedlogin" may be a binary file. See it anyway?
The hexdump of it is:
openbsd# hexdump -C failedlogin
00 00 00 00 00 00 00 00 00 00 00 00
Theo de Raadt writes:
> Sonic wrote:
>
> > Having some issues after a sysupgrade to the latest snapshot (of this
> > writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
> >
> > Seems the base change to dhcpleased/resolvd has presented some issues.
>
> This is intentional.
>
> We are moving from a m
On Fri, Jul 16, 2021 at 11:49 PM podolica wrote:
> On my OpenBSD installation (6.9) one of the log files created by login(1)
> seems to be a binary file:
> $ less /var/log/failedlogin
> "failedlogin" may be a binary file. See it anyway?
>
...
> What can I learn from this logfile?
> A lot
On 2021-07-17, Kent Watsen wrote:
> Thanks Theo!
>
>
>> It seems you copied libjq and libonig into usr/local/lib in the chroot.
>> By default, ld.so only looks for shared objects in /usr/lib, so it can't
>> find them.
>>
>> # env LD_LIBRARY_PATH=/usr/lib:/usr/local/lib chroot /var/www
>> /usr/lo
13 matches
Mail list logo