Re: /etc/rc: fsck -y

On 2018/01/18 13:30, Artturi Alm wrote: > On Thu, Jan 18, 2018 at 12:13:54PM +0100, Otto Moerbeek wrote: > > On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote: > > > > > Hi, > > > > > > i think i've never answered "n" to fsck, so to me the lack of -y does > > > mean unnecessary

Re: /etc/rc: fsck -y

Hi All, For what its worth.. if they are devices that are regularly rebooted without proper shutdown,( you may be better off avoiding the situation where FSCK has to run) I have found As Otto has pointed out fsck and all the way doesn't work so well in some cases. The most risk adverse way I

umidi: not all Yamaha products are MIDI devices

The umidi driver tries to attach midi devices to any usb device with the Yamaha vendor-id; this is not correct and prevents non-midi Yamaha device to attach (ex. usb audio devices). ok? Index: umidi_quirks.c === RCS file:

Re: httpd: mess with PATH_INFO (again)

On Thu, Jan 18, 2018 at 10:18:29AM +, Stuart Henderson wrote: > I think it should skip redirecting for "". You can't actually issue an > HTTP request for http://example.com (without the trailing slash). > True, but shouldn't a "GET /" have PATH_INFO set to "/", just like "GET /foo" results in

switch armv7 to clang

I think we are ready to switch. The procedure is the same as with previous switches. Apply the diff below, run make install in /usr/src/share/mk, and create the following hard links: # ln -f /usr/bin/clang /usr/bin/cc # ln -f /usr/bin/clang++ /usr/bin/c++ # ln -f /usr/bin/clang-cpp

Re: switch armv7 to clang

On 2018 Jan 18 (Thu) at 19:08:17 +0100 (+0100), Mark Kettenis wrote: :I think we are ready to switch. The procedure is the same as with :previous switches. Here is the corresponding ports diff: Index: infrastructure/mk/arch-defines.mk

Re: switch armv7 to clang

On Thu, Jan 18 2018, Peter Hessler wrote: > On 2018 Jan 18 (Thu) at 19:08:17 +0100 (+0100), Mark Kettenis wrote: > :I think we are ready to switch. The procedure is the same as with > :previous switches. > > Here is the corresponding ports diff: Here's an additional hunk

Re: malloc.c: correlation between random choices

On Thu, Jan 18, 2018 at 12:05:48PM +0100, Otto Moerbeek wrote: > On Thu, Jan 18, 2018 at 10:48:09AM +, kshe wrote: > > > On Thu, 18 Jan 2018 08:54:21 +, Otto Moerbeek wrote: > > > Looking back the rotor thing is ill-convceived indeed. I'm now > > > testing the diff below. I still re-use

Re: /etc/rc: fsck -y

On Thu, Jan 18, 2018 at 12:22:21PM +, Stuart Henderson wrote: > A flag (fsck_flags) would be a better idea than a file, and more > flexible (users with many disks and low RAM could use the same > mechanism to force "-l 1" for example). fsck_flags would be an idea. I prefer not to bring local

VMD: vioscsi - fix large iso support

Howdy. Attached is a patch to fix handling images > 4GB support in Linux. I confused image size vs blocks to determine when to send UINT32_MAX and trigger a READ_CAPACITY_16. Identified by mlarkin@ Comments? Ok? +--+ Carlos Index: vioscsi.c

Re: request for testing: malloc bitmap scanning

On Sat, Jan 13, 2018 at 03:36:33PM +0100, Otto Moerbeek wrote: > On Sat, Jan 13, 2018 at 11:14:27AM +0100, Otto Moerbeek wrote: > > > On Sat, Jan 13, 2018 at 09:39:35AM +0100, Otto Moerbeek wrote: > > > > > Hi, > > > > > > This diff is based upon kshe's diff, but there's one differene: I am >

Re: malloc.c: correlation between random choices

On Wed, Jan 17, 2018 at 06:25:03PM +0100, Otto Moerbeek wrote: > On Wed, Jan 17, 2018 at 01:59:21PM +, kshe wrote: > > > Hi, > > > > In malloc_bytes(), the choice of the chunk_info list to use is > > correlated with that of the offset at which the search for a free chunk > > begins, because

Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Hi All, >From time to time I receive Kernel Panic on OpenBSD 6.2 amd64 when run0 driver for RT3070 based device is attached to the Lenovo X220 laptop during boot. It appears just after file system is mounted. Next boot I receive that file system was not properly unmounted. But after FS checking

Explicitly check PF_TRANS_RULESET

The pf(4) DIOCX{BEGIN,COMMIT,ROLLBACK} calls support two ruleset types: PF_TRANS_RULESET and PF_TRANS_TABLE. However, their switch statements in pf_ioctl.c only check for PF_TRANS_TABLE and do not check PF_TRANS_RULESET at all. This diff adds explicit checks for PF_TRANS_RULESET to those switch

Zap PF_TRANS_ALTQ

Nothing uses PF_TRANS_ALTQ anymore, so zap it. ok? Index: pfvar.h === RCS file: /cvs/src/sys/net/pfvar.h,v retrieving revision 1.470 diff -u -p -r1.470 pfvar.h --- pfvar.h 29 Dec 2017 17:05:25 - 1.470 +++ pfvar.h

Re: /etc/rc: fsck -y

On Thu, Jan 18, 2018 at 12:13:54PM +0100, Otto Moerbeek wrote: > On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote: > > > Hi, > > > > i think i've never answered "n" to fsck, so to me the lack of -y does > > mean unnecessary work/boards/VMs left waiting for the F.. > > > > i would use

Re: switch armv7 to clang

On 2018/01/18 21:03, Jeremie Courreges-Anglas wrote: > +_SYSTEM_VERSION-arm = 1 Hooray for _SYSTEM_VERSION!

Re: httpd: mess with PATH_INFO (again)

On 2018/01/18 08:25, Henrik Friedrichsen wrote: > Hello, > > I am running Flask apps with uWSGI as a middleware, communicating with > httpd via FastCGI sockets. > > Ever since OpenBSD 6.1 I started running into problems with all of my > Flask apps. They would get caught in a redirect loop for

Re: malloc.c: correlation between random choices

On Thu, 18 Jan 2018 08:54:21 +, Otto Moerbeek wrote: > Looking back the rotor thing is ill-convceived indeed. I'm now > testing the diff below. I still re-use r, because I really think a > little bit of correlation does not hurt here. Actually, I think it does hurt, because it introduces a

Re: malloc.c: correlation between random choices

On Thu, Jan 18, 2018 at 10:48:09AM +, kshe wrote: > On Thu, 18 Jan 2018 08:54:21 +, Otto Moerbeek wrote: > > Looking back the rotor thing is ill-convceived indeed. I'm now > > testing the diff below. I still re-use r, because I really think a > > little bit of correlation does not hurt

Re: /etc/rc: fsck -y

On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote: > Hi, > > i think i've never answered "n" to fsck, so to me the lack of -y does > mean unnecessary work/boards/VMs left waiting for the F.. > > i would use something like this if it was there: > > diff --git a/etc/rc b/etc/rc > index

/etc/rc: fsck -y

Hi, i think i've never answered "n" to fsck, so to me the lack of -y does mean unnecessary work/boards/VMs left waiting for the F.. i would use something like this if it was there: diff --git a/etc/rc b/etc/rc index c88e13ce7ab..e3a269be818 100644 --- a/etc/rc +++ b/etc/rc @@ -349,7 +349,11 @@