Re: OpenBSD site

2018-10-27 Thread ivpgbe
Knowing OpenBSD philosophy, you should probably NOT expect a CMS :).

But you don't need to guess when you can check for yourself - all the sources 
are available for an anonymous CVS as described in [1].

You can easily have an up-to-date local copy on your machine by first reading 
manual pages on cvs(1), httpd(8) and httpd.conf(5) and then doing something 
like (as root):

# mkdir -p /var/www/htdocs/openbsd
# cd /var/www/htdocs/openbsd
# cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs checkout -P www

and adding the following section to /etc/httpd.conf:

server "openbsd-doc" {
listen on * port 81
root "/htdocs/openbsd/www"
}

and enabling httpd:

# rcctl enable httpd

After that, navigate to http://localhost:81 and enjoy browsing an offline copy 
of OpenBSD website.

[1] https://www.openbsd.org/anoncvs.html
 

On Sat, Oct 27, 2018, at 4:24 AM, Janne Johansson wrote:
> Manual edits, no hurry to jump on this weeks fashionable web
> framework, testing with lynx goes a long way to keep it simple and
> readable.
> 
> Den lör 27 okt. 2018 kl 11:14 skrev misc nick :
> >
> > I was wondering how you maintain and update such high quality content in 
> > OpenBSD's site.
> > Do you manually edit html files, use a cms, or something else? I am asking 
> > to shamelessly
> > copy your best practices. ;-)
> >
> > Thanks,
> > Nick
> >
> 
> 
> -- 
> May the most significant bit of your life be positive.
> 



Re: OpenBSD site

2018-10-27 Thread ivpgbe
On Sat, Oct 27, 2018, at 12:16 PM, Solène Rapenne wrote:
> Le 2018-10-27 21:06, ivp...@eml.cc a écrit :
> > After that, navigate to http://localhost:81 and enjoy browsing an
> > offline copy of OpenBSD website.
> > 
> > [1] https://www.openbsd.org/anoncvs.html
> > 
> 
> you don't even need to setup a http server to browse the pages :)

You are right, of course - but that would require giving your browser access to 
that part of the file system. I'm  running Chromium with --enable-unveil, 
that's why I prefer the approach above.



Fixing sluggish performance on Thinkpad X1 Carbon 6th gen with proper BIOS settings

2018-10-28 Thread ivpgbe
Hello,

several people reported about various problems with Lenovo Thinkpad X1 Carbon 
6th gen (X1C6), when performance become sluggish and fan goes wild. [1] [2] [3]

I had similar problem (system OK, become sluggish with high CPU utilization 
after sleep/wake), but was able to completely and reliably fix it by updating 
to latest Lenovo BIOS (2018-09-17, version 1.31), and setting the following 
settings in the BIOS:

* UEFI Secure Boot: Off
* Power -> Sleep State: Linux
* Startup -> UEFI/Legacy Boot: UEFI Only
* Startup -> CSM Support: Yes
* Config -> Thunderbolt(TM) 3 -> Thunderbolt BIOS Assist Mode: Enable
* Config -> Thunderbolt(TM) 3 -> Wake by Thunderbolt(TM) 3: Disable

It's the Thunderbolt BIOS Assist Mode: Enable that finally solved my problem. 
(In the BIOS itself, it recommends to set this option to Enable for Linux 
systems). Everything is perfect now with my system.

I'm running -current:

thor$ dmesg | grep OpenBSD   
OpenBSD 6.4-current (GENERIC.MP) #391: Thu Oct 25 15:27:35 MDT 2018

I'm happy to assist other OpenBSD users or developers if you need help further 
investigating this issue. I have described my adventure, along with dmesg and 
other details, here [4]. My dmesg is below.

[1] https://www.youtube.com/watch?v=lb7mDXHGDFk
[2] https://marc.info/?l=openbsd-bugs&m=154070079630478
[3] https://marc.info/?l=openbsd-bugs&m=153770491811274&w=2
[4] 
https://www.reddit.com/r/openbsd/comments/9q8atz/thinkpad_x1c6_heats_up_dramatically_drops/

OpenBSD 6.4-current (GENERIC.MP) #391: Thu Oct 25 15:27:35 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16912433152 (16128MB)
avail mem = 16390590464 (15631MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x4f057000 (63 entries)
bios0: vendor LENOVO version "N23ET56W (1.31 )" date 09/17/2018
bios0: LENOVO 20KHCTO1WW
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT 
SSDT BOOT BATB SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR NHLT 
ASF! FPDT UEFI
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4) 
RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) 
PXSX(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1393.14 MHz, 06-8e-0a
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 23MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1138.49 MHz, 06-8e-0a
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 950.25 MHz, 06-8e-0a
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 897.90 MHz, 06-8e-0a
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RD

Re: Fixing sluggish performance on Thinkpad X1 Carbon 6th gen with proper BIOS settings

2018-10-28 Thread ivpgbe
Hi Robert,

I'm certainly not trolling (although I'm not sure what would be a protocol to 
prove it, other than posting a video that shows all mentioned BIOS settings and 
than a successful boot), and I'm sure you are not trolling either, as I can see 
a number of postings to this mailing list and your first one is from 10 years 
ago. [1] A never considered a threat model where a malicious user posts 
knowingly bad BIOS settings to brick other users machines, thank you for being 
vigilant. If anyone else thinks that posting a video with my BIOS settings and 
a successful boot would be useful, I'm happy to do that.

In addition to double-checking my settings, I also looked at 4 links you've 
provided (I don't read German and can't check the last one).

The first one is a very similar machine (the difference, from what I 
understand, is that all Yoga's have a multi-touch screen), but the post is from 
7/13, and whatever the issue they encountered, I'm using a later BIOS (version 
1.31 from 9/15).

The second one is posted on 9/15, but the author and few others with similar 
problems have P52, which is a different machine - dual graphics with NVIDIA 
chip and a different CPUs - either i8750H or i8850H 6-core processors, while I 
have a i8550U. However, what is similar, is that enabling the BIOS Assist Mode 
does indeed require a 15-sec or so reboot, as the author describes, and that 
seemed to be a step that bricked their machine.

The third author also has a different machine (P1, also with NVIDIA graphics), 
and they refer to BIOS version 1.12 from 10/12 release - again, a different 
BIOS. They also post a solution for their problem [2], however it requires 
extracting firmware and flushing it to EEPROM, so you better know what you are 
doing.

The fourth author has a P72 (also a machine with NVIDIA graphics), and they did 
say they changed something in BIOS although they never specify what exactly.

Thanks!

[1] https://marc.info/?l=openbsd-misc&m=128033208924257&w=2
[2] 
https://www.reddit.com/r/thinkpad/comments/9rnimi/ladies_and_gentlemen_i_present_to_you_the/

On Sun, Oct 28, 2018, at 4:47 AM, Robert wrote:
> WARNING:
> 
> I do not know if the orginal author is serious, or if he is trolling.
> 
> But there are known issues with the stated Thunderbolt setting in BIOS
> that can brick your Thinkpad beyond repair (or BIOS reset).
> 
> See here:
> https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/Thinkpad-X1-Yoga-3rd-Gen-Stuck-at-Black-Screen-After-Enabling/td-p/4106952/page/3
> https://forums.lenovo.com/t5/ThinkPad-P-and-W-Series-Mobile/Lenovo-P52-bricked-by-selecting-BIOS-thunderbolt-support-for/td-p/4207538
> https://www.reddit.com/r/thinkpad/comments/9qmqd2/thinkpad_p1_serious_issue_with_bricked_bios/
> https://www.reddit.com/r/thinkpad/comments/9nb3zo/new_thinkpad_p72_biosuefi_corrupted_just_black/
> 
> (german)
> https://www.notebookcheck.com/Lenovo-Einige-aktuelle-ThinkPads-koennen-scheinbar-durch-eine-UEFI-Einstellung-zerstoert-werden.346101.0.html
> 
> /Robert
> 
> 
> On Sun, 28 Oct 2018 00:50:03 -0700
> ivp...@eml.cc wrote:
> 
> > Hello,
> > 
> > several people reported about various problems with Lenovo Thinkpad X1 
> > Carbon 6th gen (X1C6), when performance become sluggish and fan goes wild. 
> > [1] [2] [3]
> > 
> > I had similar problem (system OK, become sluggish with high CPU utilization 
> > after sleep/wake), but was able to completely and reliably fix it by 
> > updating to latest Lenovo BIOS (2018-09-17, version 1.31), and setting the 
> > following settings in the BIOS:
> > 
> > * UEFI Secure Boot: Off
> > * Power -> Sleep State: Linux
> > * Startup -> UEFI/Legacy Boot: UEFI Only
> > * Startup -> CSM Support: Yes
> > * Config -> Thunderbolt(TM) 3 -> Thunderbolt BIOS Assist Mode: Enable
> > * Config -> Thunderbolt(TM) 3 -> Wake by Thunderbolt(TM) 3: Disable
> > 
> > It's the Thunderbolt BIOS Assist Mode: Enable that finally solved my 
> > problem. (In the BIOS itself, it recommends to set this option to Enable 
> > for Linux systems). Everything is perfect now with my system.
> > 
> > I'm running -current:
> > 
> > thor$ dmesg | grep OpenBSD   
> > OpenBSD 6.4-current (GENERIC.MP) #391: Thu Oct 25 15:27:35 MDT 2018
> > 
> > I'm happy to assist other OpenBSD users or developers if you need help 
> > further investigating this issue. I have described my adventure, along with 
> > dmesg and other details, here [4]. My dmesg is below.
> > 
> > [1] https://www.youtube.com/watch?v=lb7mDXHGDFk
> > [2] https://marc.info/?l=openbsd-bugs&m=154070079630478
> > [3] https://marc.info/?l=openbsd-bugs&m=153770491811274&w=2
> > [4] 
> > https://www.reddit.com/r/openbsd/comments/9q8atz/thinkpad_x1c6_heats_up_dramatically_drops/
> > 
> > OpenBSD 6.4-current (GENERIC.MP) #391: Thu Oct 25 15:27:35 MDT 2018
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 16912433152 (16128MB)
> > avail mem = 16390590464 (15631MB)
> > mpath0 at root
> > scsibus0 at mpath0

mail doesn't read mail from /var/mail/root

2018-11-07 Thread ivpgbe
Hello,

I must be missing something obvious, but since installing 6.4-current (on a few 
versions in a row), I can't get mail to read /var/mail/root.

After logging in, I see:

>---<
OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4

[... skipped ...]

You have mail.
thor# mail
No mail for root
thor# mail -f /var/mail/root
Mail version 8.1.2 01/15/2001.  Type ? for help.
"/var/mail/root": 0 messages
thor# ls -l /var/mail/root
-rw---  1 root  wheel   3.9K Oct 20 00:37 /var/mail/root
thor# head /var/mail/root
>From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00 MDT 2018
Return-Path: root
Date: Nov 1 06:30:00 MDT 2018
From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
To: root
Subject: Welcome to OpenBSD 6.4!

This message attempts to describe the most basic initial questions that a
system administrator of an OpenBSD box might have.  You are urged to save
this message for later reference.
>--<

I also remember that I had this problem since the first time I installed 
6.4-current on my new laptop.

I do receive local mail (e.g., from crontab) for a non-priveleged user created 
during setup.

Any ideas of what might be going on?

Best,
ivpgbe



Re: mail doesn't read mail from /var/mail/root

2018-11-08 Thread ivpgbe
On Thu, Nov 8, 2018, at 6:03 AM, TronDD wrote:
> On November 8, 2018 1:39:13 AM CST, ivp...@eml.cc wrote:
> >Hello,
> >
> >I must be missing something obvious, but since installing 6.4-current
> >(on a few versions in a row), I can't get mail to read /var/mail/root.
> >
> >After logging in, I see:
> >
> >>---<
> >OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4
> >
> >[... skipped ...]
> >
> >You have mail.
> >thor# mail
> >No mail for root
> >thor# mail -f /var/mail/root
> >Mail version 8.1.2 01/15/2001.  Type ? for help.
> >"/var/mail/root": 0 messages
> >thor# ls -l /var/mail/root
> >-rw---  1 root  wheel   3.9K Oct 20 00:37 /var/mail/root
> >thor# head /var/mail/root
> >From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00 MDT 2018
> >Return-Path: root
> >Date: Nov 1 06:30:00 MDT 2018
> >From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
> >To: root
> >Subject: Welcome to OpenBSD 6.4!
> >
> >This message attempts to describe the most basic initial questions that
> >a
> >system administrator of an OpenBSD box might have.  You are urged to
> >save
> >this message for later reference.
> >>--<
> >
> >I also remember that I had this problem since the first time I
> >installed 6.4-current on my new laptop.
> >
> >I do receive local mail (e.g., from crontab) for a non-priveleged user
> >created during setup.
> >
> >Any ideas of what might be going on?
> >
> >Best,
> >ivpgbe
> 
> It's because the Welcome email that gets sent to root and the user 
> created during install is dated in the future.  It has the initial 
> planned release date of Nov. 1st.  Mail(1) can't seem to see into the 
> future.

Good catch - that explains why I would not see it after the install. But today 
is Nov 8 (as confirmed by date(1), and it still doesn't see it, even after I 
touch(1) the file. Should I report it as a bug? 

The mismatch between Nov 1 and the actual release is probably another bug. 
Should I report as well?

Thanks!



Re: mail doesn't read mail from /var/mail/root

2018-11-08 Thread ivpgbe
I also tested on 6.4-release, and can confirm the same behavior.

On Thu, Nov 8, 2018, at 7:13 AM, ivp...@eml.cc wrote:
> On Thu, Nov 8, 2018, at 6:03 AM, TronDD wrote:
> > On November 8, 2018 1:39:13 AM CST, ivp...@eml.cc wrote:
> > >Hello,
> > >
> > >I must be missing something obvious, but since installing 6.4-current
> > >(on a few versions in a row), I can't get mail to read /var/mail/root.
> > >
> > >After logging in, I see:
> > >
> > >>---<
> > >OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4
> > >
> > >[... skipped ...]
> > >
> > >You have mail.
> > >thor# mail
> > >No mail for root
> > >thor# mail -f /var/mail/root
> > >Mail version 8.1.2 01/15/2001.  Type ? for help.
> > >"/var/mail/root": 0 messages
> > >thor# ls -l /var/mail/root
> > >-rw---  1 root  wheel   3.9K Oct 20 00:37 /var/mail/root
> > >thor# head /var/mail/root
> > >From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00 MDT 2018
> > >Return-Path: root
> > >Date: Nov 1 06:30:00 MDT 2018
> > >From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
> > >To: root
> > >Subject: Welcome to OpenBSD 6.4!
> > >
> > >This message attempts to describe the most basic initial questions that
> > >a
> > >system administrator of an OpenBSD box might have.  You are urged to
> > >save
> > >this message for later reference.
> > >>--<
> > >
> > >I also remember that I had this problem since the first time I
> > >installed 6.4-current on my new laptop.
> > >
> > >I do receive local mail (e.g., from crontab) for a non-priveleged user
> > >created during setup.
> > >
> > >Any ideas of what might be going on?
> > >
> > >Best,
> > >ivpgbe
> > 
> > It's because the Welcome email that gets sent to root and the user 
> > created during install is dated in the future.  It has the initial 
> > planned release date of Nov. 1st.  Mail(1) can't seem to see into the 
> > future.
> 
> Good catch - that explains why I would not see it after the install. But 
> today is Nov 8 (as confirmed by date(1), and it still doesn't see it, 
> even after I touch(1) the file. Should I report it as a bug? 
> 
> The mismatch between Nov 1 and the actual release is probably another 
> bug. Should I report as well?
> 
> Thanks!



Re: mail doesn't read mail from /var/mail/root

2018-11-08 Thread ivpgbe
Yes, and I didn't change any defaults:

# set | grep MAIL
MAIL=/var/mail/root
MAILCHECK=600

On Thu, Nov 8, 2018, at 7:23 AM, Otto Moerbeek wrote:
> On Thu, Nov 08, 2018 at 07:18:57AM -0800, ivp...@eml.cc wrote:
> 
> > I also tested on 6.4-release, and can confirm the same behavior.
> 
> Is you MAIL environment var set? 
> 
>   -Otto
> 
> > 
> > On Thu, Nov 8, 2018, at 7:13 AM, ivp...@eml.cc wrote:
> > > On Thu, Nov 8, 2018, at 6:03 AM, TronDD wrote:
> > > > On November 8, 2018 1:39:13 AM CST, ivp...@eml.cc wrote:
> > > > >Hello,
> > > > >
> > > > >I must be missing something obvious, but since installing 6.4-current
> > > > >(on a few versions in a row), I can't get mail to read /var/mail/root.
> > > > >
> > > > >After logging in, I see:
> > > > >
> > > > >>---<
> > > > >OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4
> > > > >
> > > > >[... skipped ...]
> > > > >
> > > > >You have mail.
> > > > >thor# mail
> > > > >No mail for root
> > > > >thor# mail -f /var/mail/root
> > > > >Mail version 8.1.2 01/15/2001.  Type ? for help.
> > > > >"/var/mail/root": 0 messages
> > > > >thor# ls -l /var/mail/root
> > > > >-rw---  1 root  wheel   3.9K Oct 20 00:37 /var/mail/root
> > > > >thor# head /var/mail/root
> > > > >From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00 MDT 2018
> > > > >Return-Path: root
> > > > >Date: Nov 1 06:30:00 MDT 2018
> > > > >From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
> > > > >To: root
> > > > >Subject: Welcome to OpenBSD 6.4!
> > > > >
> > > > >This message attempts to describe the most basic initial questions that
> > > > >a
> > > > >system administrator of an OpenBSD box might have.  You are urged to
> > > > >save
> > > > >this message for later reference.
> > > > >>--<
> > > > >
> > > > >I also remember that I had this problem since the first time I
> > > > >installed 6.4-current on my new laptop.
> > > > >
> > > > >I do receive local mail (e.g., from crontab) for a non-priveleged user
> > > > >created during setup.
> > > > >
> > > > >Any ideas of what might be going on?
> > > > >
> > > > >Best,
> > > > >ivpgbe
> > > > 
> > > > It's because the Welcome email that gets sent to root and the user 
> > > > created during install is dated in the future.  It has the initial 
> > > > planned release date of Nov. 1st.  Mail(1) can't seem to see into the 
> > > > future.
> > > 
> > > Good catch - that explains why I would not see it after the install. But 
> > > today is Nov 8 (as confirmed by date(1), and it still doesn't see it, 
> > > even after I touch(1) the file. Should I report it as a bug? 
> > > 
> > > The mismatch between Nov 1 and the actual release is probably another 
> > > bug. Should I report as well?
> > > 
> > > Thanks!
> > 



Re: mail doesn't read mail from /var/mail/root

2018-11-08 Thread ivpgbe
And regardless, /usr/src/usr.bin/mail/main.c:95 unsets MAIL environment 
variable when an '-u' flag is present, and the problem I'm reporting persists 
even when I run

mail -u root

as root.

On Thu, Nov 8, 2018, at 7:29 AM, ivp...@eml.cc wrote:
> Yes, and I didn't change any defaults:
> 
> # set | grep MAIL
> MAIL=/var/mail/root
> MAILCHECK=600
> 
> On Thu, Nov 8, 2018, at 7:23 AM, Otto Moerbeek wrote:
> > On Thu, Nov 08, 2018 at 07:18:57AM -0800, ivp...@eml.cc wrote:
> > 
> > > I also tested on 6.4-release, and can confirm the same behavior.
> > 
> > Is you MAIL environment var set? 
> > 
> > -Otto
> > 
> > > 
> > > On Thu, Nov 8, 2018, at 7:13 AM, ivp...@eml.cc wrote:
> > > > On Thu, Nov 8, 2018, at 6:03 AM, TronDD wrote:
> > > > > On November 8, 2018 1:39:13 AM CST, ivp...@eml.cc wrote:
> > > > > >Hello,
> > > > > >
> > > > > >I must be missing something obvious, but since installing 6.4-current
> > > > > >(on a few versions in a row), I can't get mail to read 
> > > > > >/var/mail/root.
> > > > > >
> > > > > >After logging in, I see:
> > > > > >
> > > > > >>---<
> > > > > >OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4
> > > > > >
> > > > > >[... skipped ...]
> > > > > >
> > > > > >You have mail.
> > > > > >thor# mail
> > > > > >No mail for root
> > > > > >thor# mail -f /var/mail/root
> > > > > >Mail version 8.1.2 01/15/2001.  Type ? for help.
> > > > > >"/var/mail/root": 0 messages
> > > > > >thor# ls -l /var/mail/root
> > > > > >-rw---  1 root  wheel   3.9K Oct 20 00:37 /var/mail/root
> > > > > >thor# head /var/mail/root
> > > > > >From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00 MDT 2018
> > > > > >Return-Path: root
> > > > > >Date: Nov 1 06:30:00 MDT 2018
> > > > > >From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
> > > > > >To: root
> > > > > >Subject: Welcome to OpenBSD 6.4!
> > > > > >
> > > > > >This message attempts to describe the most basic initial questions 
> > > > > >that
> > > > > >a
> > > > > >system administrator of an OpenBSD box might have.  You are urged to
> > > > > >save
> > > > > >this message for later reference.
> > > > > >>--<
> > > > > >
> > > > > >I also remember that I had this problem since the first time I
> > > > > >installed 6.4-current on my new laptop.
> > > > > >
> > > > > >I do receive local mail (e.g., from crontab) for a non-priveleged 
> > > > > >user
> > > > > >created during setup.
> > > > > >
> > > > > >Any ideas of what might be going on?
> > > > > >
> > > > > >Best,
> > > > > >ivpgbe
> > > > > 
> > > > > It's because the Welcome email that gets sent to root and the user 
> > > > > created during install is dated in the future.  It has the initial 
> > > > > planned release date of Nov. 1st.  Mail(1) can't seem to see into the 
> > > > > future.
> > > > 
> > > > Good catch - that explains why I would not see it after the install. 
> > > > But 
> > > > today is Nov 8 (as confirmed by date(1), and it still doesn't see it, 
> > > > even after I touch(1) the file. Should I report it as a bug? 
> > > > 
> > > > The mismatch between Nov 1 and the actual release is probably another 
> > > > bug. Should I report as well?
> > > > 
> > > > Thanks!
> > > 



Re: mail doesn't read mail from /var/mail/root

2018-11-08 Thread ivpgbe
Mystery solved! The very first line is missing a space between ‘Nov’
and ‘1’ (should be two spaces). After adding it back, mail can now
parse the file.
(Also, Nov 1 is Thu, not Sun, but that wouldn’t have prevented mail from
parsing the file).
I will send a patch to tech@ adding that space back  - it would be cool
to make a contribution of a single character ;).

On Thu, Nov 8, 2018, at 7:32 AM, ivp...@eml.cc wrote:
> And regardless, /usr/src/usr.bin/mail/main.c:95 unsets MAIL
> environment> variable when an '-u' flag is present, and the problem I'm 
> reporting
> persists even when I run
>
> mail -u root
>
> as root.
>
> On Thu, Nov 8, 2018, at 7:29 AM, ivp...@eml.cc wrote:
> > Yes, and I didn't change any defaults:
> >
> > # set | grep MAIL
> > MAIL=/var/mail/root
> > MAILCHECK=600
> >
> > On Thu, Nov 8, 2018, at 7:23 AM, Otto Moerbeek wrote:
> > > On Thu, Nov 08, 2018 at 07:18:57AM -0800, ivp...@eml.cc wrote:
> > >
> > > > I also tested on 6.4-release, and can confirm the same behavior.> > >
> > > Is you MAIL environment var set?
> > >
> > >  -Otto
> > >
> > > >
> > > > On Thu, Nov 8, 2018, at 7:13 AM, ivp...@eml.cc wrote:
> > > > > On Thu, Nov 8, 2018, at 6:03 AM, TronDD wrote:
> > > > > > On November 8, 2018 1:39:13 AM CST, ivp...@eml.cc wrote:
> > > > > > >Hello,
> > > > > > >
> > > > > > >I must be missing something obvious, but since installing
> > > > > > >6.4-current> > > > > > >(on a few versions in a row), I can't get 
> > > > > > >mail to read
> > > > > > >/var/mail/root.> > > > > > >
> > > > > > >After logging in, I see:
> > > > > > >
> > > > > > >>---<
> > > > > > >OpenBSD 6.4-current (GENERIC.MP) #425: Sun Nov 4
> > > > > > >
> > > > > > >[... skipped ...]
> > > > > > >
> > > > > > >You have mail.
> > > > > > >thor# mail
> > > > > > >No mail for root
> > > > > > >thor# mail -f /var/mail/root
> > > > > > >Mail version 8.1.2 01/15/2001.  Type ? for help.
> > > > > > >"/var/mail/root": 0 messages
> > > > > > >thor# ls -l /var/mail/root
> > > > > > >-rw---  1 root  wheel   3.9K Oct 20 00:37
> > > > > > >/var/mail/root> > > > > > >thor# head /var/mail/root
> > > > > > >From dera...@do-not-reply.openbsd.org Sun Nov 1 06:30:00
> > > > > > >MDT 2018> > > > > > >Return-Path: root
> > > > > > >Date: Nov 1 06:30:00 MDT 2018
> > > > > > >From: dera...@do-not-reply.openbsd.org (Theo de Raadt)
> > > > > > >To: root
> > > > > > >Subject: Welcome to OpenBSD 6.4!
> > > > > > >
> > > > > > >This message attempts to describe the most basic initial
> > > > > > >questions that> > > > > > >a
> > > > > > >system administrator of an OpenBSD box might have.  You are
> > > > > > >urged to> > > > > > >save
> > > > > > >this message for later reference.
> > > > > > >>--<
> > > > > > >
> > > > > > >I also remember that I had this problem since the first
> > > > > > >time I> > > > > > >installed 6.4-current on my new laptop.
> > > > > > >
> > > > > > >I do receive local mail (e.g., from crontab) for a non-
> > > > > > >priveleged user> > > > > > >created during setup.
> > > > > > >
> > > > > > >Any ideas of what might be going on?
> > > > > > >
> > > > > > >Best,
> > > > > > >ivpgbe
> > > > > >
> > > > > > It's because the Welcome email that gets sent to root and
> > > > > > the user> > > > > > created during install is dated in the future.  
> > > > > > It has the
> > > > > > initial> > > > > > planned release date of Nov. 1st.  Mail(1) can't 
> > > > > > seem to see
> > > > > > into the> > > > > > future.
> > > > >
> > > > > Good catch - that explains why I would not see it after the
> > > > > install. But> > > > > today is Nov 8 (as confirmed by date(1), and it 
> > > > > still doesn't
> > > > > see it,> > > > > even after I touch(1) the file. Should I report it 
> > > > > as a bug?
> > > > >
> > > > > The mismatch between Nov 1 and the actual release is probably
> > > > > another> > > > > bug. Should I report as well?
> > > > >
> > > > > Thanks!
> > > >
>



Re: XORG Doesnt start after syspatch

2018-11-21 Thread ivpgbe
If you are using startx, it won't work anymore after 001 security fix. Please 
switch to using xenodm(1).

There were a couple of discussions on this list about this, you can search 
archives for more details.

On Wed, Nov 21, 2018, at 4:12 PM, Manuel Solis wrote:
> Hello Misc.
> 
> I have installed 64 in a macbook and it works great and out of the box,
> however i notice that after i run syspatch and reboot, xorg doesn´t start
> at all.
> 
> I have done several tries like install64 - syspatch - error ; install64
> -fw_update -syspatch - error;
> 
> May i missing some sysctl trick ?
> 
> Thank you all.
> 
> Manuel
> 
> ===
> === Xorg.0.log after syspatch with Xorg not working ===
> ===
> [39.473]
> X.Org X Server 1.19.6
> Release Date: 2017-12-20
> [39.536] X Protocol Version 11, Revision 0
> [39.562] Build Operating System: OpenBSD 6.4 amd64
> [39.570] Current Operating System: OpenBSD mac.book 6.4 GENERIC.MP#364
> amd64
> [39.579] Build Date: 25 October 2018  11:39:05PM
> [39.588]
> [39.596] Current version of pixman: 0.34.0
> [39.605] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [39.605] Markers: (--) probed, (**) from config file, (==) default
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [39.639] (==) Log file: "/home/msolis/.local/share/xorg/Xorg.0.log",
> Time: Wed Nov 21 17:44:59 2018
> [39.649] (==) Using system config directory
> "/usr/X11R6/share/X11/xorg.conf.d"
> [39.650] (==) No Layout section.  Using the first Screen section.
> [39.650] (==) No screen section available. Using defaults.
> [39.650] (**) |-->Screen "Default Screen Section" (0)
> [39.650] (**) |   |-->Monitor ""
> [39.650] (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> [39.650] (==) Automatically adding devices
> [39.650] (==) Automatically enabling devices
> [39.650] (==) Not automatically adding GPU devices
> [39.650] (==) Max clients allowed: 256, resource mask: 0x1f
> [39.654] (==) FontPath set to:
> /usr/X11R6/lib/X11/fonts/misc/,
> /usr/X11R6/lib/X11/fonts/TTF/,
> /usr/X11R6/lib/X11/fonts/OTF/,
> /usr/X11R6/lib/X11/fonts/Type1/,
> /usr/X11R6/lib/X11/fonts/100dpi/,
> /usr/X11R6/lib/X11/fonts/75dpi/
> [39.654] (==) ModulePath set to "/usr/X11R6/lib/modules"
> [39.654] (II) The server relies on wscons to provide the list of input
> devices.
> If no devices become available, reconfigure wscons or disable
> AutoAddDevices.
> [39.654] (II) Loader magic: 0x2de2fe71000
> [39.654] (II) Module ABI versions:
> [39.654] X.Org ANSI C Emulation: 0.4
> [39.654] X.Org Video Driver: 23.0
> [39.654] X.Org XInput driver : 24.1
> [39.654] X.Org Server Extension : 10.0
> [39.654] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Permission denied)
> Check that you have set 'machdep.allowaperture=1'
> in /etc/sysctl.conf and reboot your machine
> refer to xf86(4) for details
> [39.654] linear framebuffer access unavailable
> [39.654] (II) LoadModule: "glx"
> [39.656] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
> [39.663] (II) Module glx: vendor="X.Org Foundation"
> [39.663] compiled for 1.19.6, module version = 1.0.0
> [39.663] ABI class: X.Org Server Extension, version 10.0
> [39.663] (==) Assigned the driver to the xf86ConfigLayout
> [39.663] (EE) No drivers available.
> [39.663] (EE)
> Fatal server error:
> [39.671] (EE) no screens found(EE)
> [39.680] (EE)
> Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>  for help.
> [39.688] (EE) Please also check the log file at
> "/home/msolis/.local/share/xorg/Xorg.0.log" for additional information.
> [39.697] (EE)
> [39.706] (EE) Server terminated with error (1). Closing log file.
> 
> ==
> ===working Xorg.0.log just after new installation =
> ==
> [50.434] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Operation not permitted)
> Check that you have set 'machdep.allowaperture=1'
> in /etc/sysctl.conf and reboot your machine
> refer to xf86(4) for details
> [50.434] linear framebuffer access unavailable
> [50.457] (--) Using wscons driver on /dev/ttyC4
> [50.471]
> X.Org X Server 1.19.6
> Release Date: 2017-12-20
> [50.471] X Protocol Version 11, Revision 0
> [50.471] Build Operating System: OpenBSD 6.4 amd64
> [50.472] Current Operating System: OpenBSD mac.my.doma

Re: Search OpenBSD mailing list archives?

2018-12-12 Thread ivpgbe
Marc.info


On Wed, Dec 12, 2018, at 5:56 PM, Paul Swanson wrote:
> Hi,
>
> Is there a facility for searching the mailing list archives?
>
> I can't seem to find one.
>
> Cheers,
>
> Paul Swanson