On Sat, Oct 20, 2018 at 09:38:00AM -0700, Tracy Bales wrote:
> My AMD FX-8300 CPU runs bsd.rd with no issues...I can complete the
> installation process. However, when the machine reboots and after it
> pauses for BOOT 3.34 and then loads either bsd.mp or bsd.sp it reboots as
> soon as the first l
>Synopsis: iked(8) producing bad-ip-version 7 error with vxlan(4)
traffic
>Category: system
>Environment:
System : OpenBSD 6.4
Details : OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23
MDT 2018
dera...@amd64.openbsd.org:
/usr/src/sys/ar
It seems that libjpeg causes an issue in OpenBSD6.4 (32 and 64bit).
Downloading or compiling the graphical links browser will not allow jpeg
images to be displayed.
Philip Guenther wrote:
> On Mon, 22 Oct 2018, Larry Gadallah wrote:
> > Thanks Phillip. This system probably does have 64KB blocks, as the
> > root FS is ~460 Gb in size.
Such a filesystem size will be ffs2, which means it uses
sys/lib/libsa/ufs2.c support, which looks like it allocates 64K * 5
On Mon, 22 Oct 2018, Larry Gadallah wrote:
> Thanks Phillip. This system probably does have 64KB blocks, as the
> root FS is ~460 Gb in size.
Is there a website or something out there recommending this sort of setup?
Wondering where this bad idea is coming from.
> 2. Shouldn't the docs indicat
Larry Gadallah wrote:
> Thanks Phillip. This system probably does have 64KB blocks, as the
> root FS is ~460 Gb in size. This leads to a couple of questions:
Why is your root filesystem this big?
You manually chose that.
Why did you avoid the default partition scheme which installs multiple
pa
Thanks Phillip. This system probably does have 64KB blocks, as the
root FS is ~460 Gb in size. This leads to a couple of questions:
1. Is there a way to instruct the installer to install an EFI bootloader?
2. Shouldn't the docs indicate somewhere that if you deviate from the
recommended partitioni
On Mon, Oct 22, 2018 at 09:01:21AM +0200, Martijn van Duren wrote:
> I found another bug while testing ldap(1) to M$ AD.
> Attributes like objectGUID are encoded as OCTET STRING, but are binary
> data, which are not UTF-8 strings.
> When looking at RFC4511 I found the following:
> 4.1.5. Attribute
I found another bug while testing ldap(1) to M$ AD.
Attributes like objectGUID are encoded as OCTET STRING, but are binary
data, which are not UTF-8 strings.
When looking at RFC4511 I found the following:
4.1.5. Attribute Value
A field of type AttributeValue is an OCTET STRING containing an
