On Mon, 11 Feb 2019 08:13:16 +0300
Kihaguru Gathura wrote:
> Hi,
>
> Any ideas on how to fix the missing libraries,
>
> www# pkg_add -v mini_sendmail-chroot
> Update candidates: quirks-3.91 -> quirks-3.91
> quirks-3.91 signed on 2019-02-10T22:07:56Z
> Can't install mini_sendmail-chroot-1.3.9
Hi,
Any ideas on how to fix the missing libraries,
www# pkg_add -v mini_sendmail-chroot
Update candidates: quirks-3.91 -> quirks-3.91
quirks-3.91 signed on 2019-02-10T22:07:56Z
Can't install mini_sendmail-chroot-1.3.9 because of libraries
|library c.95.0 not found
| /usr/lib/libc.so.92.6
Hi Adam,
It sounds like you're on an ISP with very similar requirements to me. The exec
summary of what my ISP wants is pppoe on vlan2, with the vlan priority forced
to a single value.
Our (OpenBSD's) understanding of the priority field in VLAN headers is that it
uses 802.1p for the fields
On Sun, Feb 10, 2019 at 11:16:03PM +0100, Erling Westenvik wrote:
> Hi,
> After upgrading to todays snapshot (February 10th) I experience some rather
> ugly shadow artifacts and color distortions when using compton(1) under
> cwm(1).
> It may perhaps best be described by linking to an issue
Hi,
After upgrading to todays snapshot (February 10th) I experience some rather
ugly shadow artifacts and color distortions when using compton(1) under cwm(1).
It may perhaps best be described by linking to an issue report from April 2018
at github:
https://github.com/chjj/compton/issues/487
and
> On Feb 10, 2019, at 12:13 PM, Nick Holland
> wrote:
>
> Most likely, you are going to start by panicking about Meltdown and
> Spectre. Then you are going to go load up your system with poorly
> written software which is far more likely to be the REAL cause of a breach.
>
> OpenBSD
On 2/10/19 8:41 AM, Mihai Popescu wrote:
> Hello all,
>
> I usually take my computers for OpenBSD from used/refurbished market
> since they are much cheaper and I don't need edge hardware. Lately,
> AMD processors platforms are not so easy to find ( I prefer a
> combination of cpu + video + brand
Am Sonntag, Februar 10, 2019 14:19 CET, Stefan Sperling
schrieb:
> On Sun, Feb 10, 2019 at 11:50:35AM +0100, Sebastian Reitenbach wrote:
> > The non-working one shows up as AR7015 in Windows, but I don't see a AR7015
> > chipset
> > mentioned in athn(4), therefore I wanted to verify, if that
> On Feb 10, 2019, at 7:41 AM, Mihai Popescu wrote:
>
> How did you folks with Intel based production systems mitigated this?
>
> Thank you.
At this point hyper threading is no-op on my Dell system.
Hoping to clarify if meltdown effects Bigtable?
Also what is the status of "no root unix”.
>Hello all,
>
>I usually take my computers for OpenBSD from used/refurbished market
>since they are much cheaper and I don't need edge hardware. Lately,
>AMD processors platforms are not so easy to find ( I prefer a
>combination of cpu + video + brand name).
>I have a much bigger offer from Intel
Hello all,
I usually take my computers for OpenBSD from used/refurbished market
since they are much cheaper and I don't need edge hardware. Lately,
AMD processors platforms are not so easy to find ( I prefer a
combination of cpu + video + brand name).
I have a much bigger offer from Intel side.
On Sun, Feb 10, 2019 at 11:50:35AM +0100, Sebastian Reitenbach wrote:
> The non-working one shows up as AR7015 in Windows, but I don't see a AR7015
> chipset
> mentioned in athn(4), therefore I wanted to verify, if that particular
> chipset is actually
> supported by our athn(4) at all?
Indeed,
On 2/10/19 4:51 PM, Adam Evans wrote:
> When I do a 'route show' with PPPoE established it hangs with no output,
> disabling PPPoE 'route show' displays output.
Maybe this goes without saying, but you probably should be using 'route
-n show' (or 'netstat -nr') to avoid getting stuck on DNS
Hi Stefan,
Am Sonntag, Februar 10, 2019 11:06 CET, Stefan Sperling
schrieb:
> On Sat, Feb 09, 2019 at 06:56:45PM +0100, Sebastian Reitenbach wrote:
> > Hi,
> >
> > got a cheap TP-Link TL-WN821N, which shows up as Atheros AR7015 under
> > Windows 10.
> >
> > athn0 at uhub3 port 3 configuration
On Sat, Feb 09, 2019 at 06:56:45PM +0100, Sebastian Reitenbach wrote:
> Hi,
>
> got a cheap TP-Link TL-WN821N, which shows up as Atheros AR7015 under Windows
> 10.
>
> athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev
> 2.00/2.02 addr 5
> athn0: failed loadfirmware of
15 matches
Mail list logo
