Re: Help with the NET_LOCK()

2017-01-26 Thread RD Thrush
On 01/25/17 01:32, Martin Pieuchot wrote: > I just enabled the NET_LOCK() again and I'm looking for test reports. > Please go build a kernel from sources or wait for the next snapshot, > run it and report back. > > If you're looking for some small coding tasks related to the NET_LOCK() > just do:

Re: Help with the NET_LOCK()

2017-01-26 Thread RD Thrush
On 01/25/17 01:32, Martin Pieuchot wrote: > I just enabled the NET_LOCK() again and I'm looking for test reports. > Please go build a kernel from sources or wait for the next snapshot, > run it and report back. > > If you're looking for some small coding tasks related to the NET_LOCK() > just do:

Re: Allow install from https server w/ self signed cert

2017-01-10 Thread RD Thrush
On 01/06/17 06:28, Stuart Henderson wrote: > Related to this (and particularly thinking about autoinstalls), > would it make sense to allow explicit protocols in the hostname? > > some.host -> https with http fallback > http://some.host/ -> http only > https://some.host/ -> https only, no

Re: Allow install from https server w/ self signed cert

2017-01-07 Thread RD Thrush
On 01/07/17 16:13, Bob Beck wrote: > > On Fri, Jan 06, 2017 at 10:48:37AM -0500, RD Thrush wrote: >> On 01/06/17 06:28, Stuart Henderson wrote: >>> Related to this (and particularly thinking about autoinstalls), >>> would it make sense to allow expl

Re: Allow install from https server w/ self signed cert

2017-01-06 Thread RD Thrush
On 01/06/17 06:28, Stuart Henderson wrote: > Related to this (and particularly thinking about autoinstalls), > would it make sense to allow explicit protocols in the hostname? > > some.host -> https with http fallback > http://some.host/ -> http only > https://some.host/ -> https only, no

Allow install from https server w/ self signed cert

2017-01-05 Thread RD Thrush
Rather than add load to the OpenBSD snapshot servers, for years I download a snapshot to a local netgear nas server. With the recent https changes, I'm no longer able to install from that server. I've appended a console log of a failed install attempt. Per src/distrib/miniroot/install.sub

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 19:37, Edgar Pettijohn wrote: >> On May 13, 2016, at 4:16 PM, RD Thrush <openbsd-t...@thrush.com> wrote: >> >> On 05/13/16 11:07, Theo de Raadt wrote: >>>> Since the anti-ROP mechanism in libc [2] was added in late April, -current >>>

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 23:34, Theo de Raadt wrote: >> The report is fairly easy to reproduce. Make the /usr filesystem >> read-only in /etc/fstab, go to single user mode and exit back to >> multi-user. I've appended a transcript. > > This does not matter. It is your configuration. It is not the default.

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 19:40, Chris Cappuccio wrote: > RD Thrush [openbsd-t...@thrush.com] wrote: >> On 05/13/16 11:07, Theo de Raadt wrote: >>>> Since the anti-ROP mechanism in libc [2] was added in late April, -current >>>> with read-only /usr produces something li

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/14/16 04:34, Craig Skinner wrote: > Hi RD/all, > > On 2016-05-13 Fri 17:16 PM |, RD Thrush wrote: >> >> # cp -p /etc/fstab /etc/fstab.orig >> # sed -e 's,/usr ffs rw,/usr ffs ro,' /etc/fstab >> # shutdown -f now >> Shutdown NOW! >> shutdown: [p

Re: Is loss of read-only /usr permanent?

2016-05-13 Thread RD Thrush
On 05/13/16 11:07, Theo de Raadt wrote: >> Since the anti-ROP mechanism in libc [2] was added in late April, -current >> with read-only /usr produces something like the following message: >> re-ordering libraries:install: /usr/lib/INS@OPOjn7ck17: Read-only file system > > Look, your statement is

sysmerge w/ local sets

2014-08-28 Thread RD Thrush
sysmerge hangs while fetching the SHA256.sig file when working with local sets, ie.: #export SM_PATH=/nas2/public/OpenBSD/snapshots/amd64 #cd $SM_PATH #ls -l SHA256.sig xetc56.tgz -rw-r--r-- 1 rd rd 1977 Aug 26 23:39 SHA256.sig -rw-r--r-- 1 rd rd 69066 Aug 6 16:10 xetc56.tgz #sysmerge -bd

Re: Fix of sysctl.c rev. 1.191 related bug and unbreak diskless(8)

2013-07-15 Thread RD Thrush
On 07/14/13 23:50, Philip Guenther wrote: On Sun, Jul 14, 2013 at 12:54 AM, Rafael Neves rafaelne...@gmail.com wrote: The patch below fixes a bug on sysctl(8) introduced by revision 1.191 of sysctl.c. After rev1.191, `sysctl vfs' mangles information about filesystems (mounted instances of ffs

Re: Fix of sysctl.c rev. 1.191 related bug and unbreak diskless(8)

2013-07-14 Thread RD Thrush
Your patch applies correctly. 5sysctl kern.version kern.version=OpenBSD 5.4-beta (GENERIC.MP) #27: Fri Jul 12 10:35:54 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP 6mount /dev/sd0a on / type ffs (local, softdep) mfs:26558 on /tmp type mfs (asynchronous, local,

Re: 5.3 -current installation problem

2013-04-04 Thread RD Thrush
On 04/03/13 09:08, Stuart Henderson wrote: moving this to tech@ - original message with dmesg is at http://marc.info/?l=openbsd-miscm=136498447228598w=2 - summary: asus P8H77-M, intel 7 series chipset, Intel HD Graphics 3000 running i386 or amd64, fails during boot with recent kernels unless

Re: 5.3 -current installation problem

2013-04-03 Thread RD Thrush
On 04/03/13 09:52, Mark Kettenis wrote: Date: Wed, 3 Apr 2013 14:08:20 +0100 From: Stuart Henderson s...@spacehopper.org moving this to tech@ - original message with dmesg is at http://marc.info/?l=openbsd-miscm=136498447228598w=2 - summary: asus P8H77-M, intel 7 series chipset, Intel HD

Xorg triggers panic w/ Intel HD4000 graphics

2013-02-06 Thread RD Thrush
Using startx as root w/ no Xorg.conf causes -current to panic when using the i7-3770 integrated graphics adapter. I built a debug kernel and sent a sendbug report[1] on Sunday. I've appended a (serial console) excerpt from that report. The panic is easily reproducible. Is this a known

Re: Xorg triggers panic w/ Intel HD4000 graphics

2013-02-06 Thread RD Thrush
On 02/06/13 09:52, Mark Kettenis wrote: Date: Wed, 06 Feb 2013 06:39:48 -0500 From: RD Thrush r...@thrush.com Using startx as root w/ no Xorg.conf causes -current to panic when using the i7-3770 integrated graphics adapter. I built a debug kernel and sent a sendbug report[1] on Sunday

Re: UQ_BAD_HID

2012-08-12 Thread RD Thrush
On 08/10/12 08:13, Stuart Henderson wrote: On 2012/08/10 13:46, Martin Pieuchot wrote: I'm also in favor of removing quirks however I would suggest to remove them on a case-by-case basis until libusb have full support for communicating with any usb device (hopefully in this release cycle).

Re: diff: fix waiting problem on AMD Hudson's AHCI (Re: AMD APU report)

2012-04-12 Thread RD Thrush
On 04/12/12 09:40, SASANO Takayoshi wrote: Hello, I have a system with an asrock a75m-itx motherboard and an amd a6-3500 processor. I notice there is a 40 second delay after the 'ahci0 at pci0 dev 17 ...' line. I have IBM's ThinkPad Edge E525, AMD A8-3500M based machine. And I checked

AMD APU report

2012-04-03 Thread RD Thrush
I have a system with an asrock a75m-itx motherboard and an amd a6-3500 processor. I notice there is a 40 second delay after the 'ahci0 at pci0 dev 17 ...' line. I also notice there are two 'not configured' items and 4 'unknown product' items. It appears that I have selected a combination

Re: ddb symbol derefence error, test, ok?

2011-05-18 Thread RD Thrush
On 05/18/11 18:32, Ariane van der Steldt wrote: It turns out that on sparc64, doing something like show map /f *kernel_map in ddb, makes you crash with a nullpointer exception. Diff below makes sure we read all bytes of the pointer. The int in the original code also explains why amd64

Shuttle XPC SK21 hangs unless acpimadt is disabled

2010-08-06 Thread RD Thrush
This problem first occurred between the Dec 15, 2008 and the Jan 16, 2009 amd64 snapshots. Bug reports kernel/6138 and kernel/6164 have been submitted. The problem still remains, ie. both RAMDISK_CD and GENERIC hang unless acpimadt is disabled. With acpimadt disabled, the system runs ok. Both

Re: infrastructure/build/out-of-date unusable with '@option always-update'

2010-01-27 Thread RD Thrush
Matthias Kilian wrote: On Mon, Jan 25, 2010 at 10:44:26AM -0500, RD Thrush wrote: ${PORTSDIR}/infrastructure/build/out-of-date generates unusable data for a port with a packing list containing '@option always-update'. The following patch fixes the problem (which appears to be fallout from

infrastructure/build/out-of-date unusable with '@option always-update'

2010-01-25 Thread RD Thrush
${PORTSDIR}/infrastructure/build/out-of-date generates unusable data for a port with a packing list containing '@option always-update'. The following patch fixes the problem (which appears to be fallout from the recent pkg_add improvements): Index: out-of-date