Re: less(1): `!' command

On Sat, 16 Dec 2017 21:52:44 +, Theo de Raadt wrote: > > On Sat, 16 Dec 2017 19:39:27 +, Theo de Raadt wrote: > > > > On Sat, 16 Dec 2017 18:13:16 +, Jiri B wrote: > > > > > On Sat, Dec 16, 2017 at 04:55:44PM +, kshe wrote: > > > > > > Hi, > > > > > > > > > > > > Would a patch to

arm64 wsdisplay options

Pretty much a no-brainer. The raw keyboard stuff is necessary for running X, and we have VT support in simplefb(4) so let's enable it. ok? Index: arch/arm64/conf/GENERIC === RCS file: /cvs/src/sys/arch/arm64/conf/GENERIC,v

Memory attributes for simplefb userland mappings

Running X on my Orange Pi PC2 results in some interesting artifacts that are clearly cache-related. That made me realize that we're mapping the framebuffer as device memory in our kernel and as normal WB-cachable memory in X. That is a seriously bad idea. The diff below switches the userland

Re: mg: have Insert key toggle overwrite mode by default

Committed, thanks. On 12/17/17 05:11, Florian Obser wrote: OK On Sat, Dec 16, 2017 at 10:06:59PM +, Lari Rasku wrote: There's a fairly strong convention among text editors that the Insert key should toggle overwrite mode. This is admittedly far more common among GUI editors, but could mg

one XXX in ksh(1)

Hello, In my understanding the reason why texec had to be static was because the struct member ioact was never initialised. The call tree is execute() -> comexec() -> exchild() -> execute() and a fork happens in exchild(). The second execute() dereferences t->ioact on line 115 which causes SEGV.

Another regulator framework improvement

Diff below allows enabling of more complex regulators. The "fixed" regulator support is split off in its own function. We now respect the "regulator-allways-on" property by leaving the regulator alone, assuming it is already turned on. ok? Index: dev/ofw/ofw_regulator.c

Re: ypldap patch 5: fix aldap_close

2017-12-17 6:35 GMT+03:00 Jonathan Matthew : > On Sat, Dec 16, 2017 at 08:38:59PM +0300, Vadim Zhukov wrote: >> 2017-12-06 19:12 GMT+03:00 Vadim Zhukov : >> >> The aldap_close() return value is never checked, and I do not see >> >> any good reason to do that.

csh dounsetenv()

Hello, The free() at the top of dounsetenv() in csh(1) isn't needed because name is always freed before returning at bottom of function. Also, name itself is never returned so it doesn't need to be static. ./csh setenv HEY YU unsetenv HEY printenv I ran the above and it seems to work the same

Re: mg: have Insert key toggle overwrite mode by default

OK On Sat, Dec 16, 2017 at 10:06:59PM +, Lari Rasku wrote: > There's a fairly strong convention among text editors that the Insert > key should toggle overwrite mode. This is admittedly far more common > among GUI editors, but could mg adopt it as a default anyway? > > diff --git

efiboot: boot i386 kernel (part 1)

Hi, I had been looking into booting a 32-bit kernel with efiboot and the first thing I stumbled upon is that when we jump back into 32-bit mode we don't disable the Long Mode Extension. Thus when the i386 kernel turns on paging, LME goes active as well and "weird things happen". Not sure this

Re: efiboot: boot i386 kernel (part 1)

On Sun, Dec 17, 2017 at 08:34:52PM +0100, Patrick Wildt wrote: > Hi, > > I had been looking into booting a 32-bit kernel with efiboot and the > first thing I stumbled upon is that when we jump back into 32-bit mode > we don't disable the Long Mode Extension. Thus when the i386 kernel > turns on

Re: efiboot: boot i386 kernel (part 1)

On Sun, Dec 17, 2017 at 12:17:26PM -0800, Mike Larkin wrote: > On Sun, Dec 17, 2017 at 08:34:52PM +0100, Patrick Wildt wrote: > > Hi, > > > > I had been looking into booting a 32-bit kernel with efiboot and the > > first thing I stumbled upon is that when we jump back into 32-bit mode > > we