YASUOKA Masahiko wrote:
> Hello,
>
> On Wed, 7 Aug 2019 21:41:17 -0500
> Scott Cheloha wrote:
> > Drop config(8) support for getting/setting the kernel timezone.
>
> I'm using this. Is there any alternative or discussion?
>
> I think PCs are still shipped with their firmware configured to
Hello,
On Wed, 7 Aug 2019 21:41:17 -0500
Scott Cheloha wrote:
> Drop config(8) support for getting/setting the kernel timezone.
I'm using this. Is there any alternative or discussion?
I think PCs are still shipped with their firmware configured to the
local time.
> ok?
>
> Index: cmd.c
>
On Thu, Aug 08, 2019 at 11:06:30PM +0100, Stuart Henderson wrote:
> On 2019/08/08 15:42, Claudio Jeker wrote:
> > I need to be able to control the bind address for openrsync connections.
> > This implements this but it only works for connections to an rsync daemon.
> > For rsync over ssh you need
On 2019/08/08 15:42, Claudio Jeker wrote:
> I need to be able to control the bind address for openrsync connections.
> This implements this but it only works for connections to an rsync daemon.
> For rsync over ssh you need to use -e 'ssh -b address' instead.
Works as expected for IPv4. For IPv6
On Thu, Aug 08, 2019 at 01:40:06PM +0200, Claudio Jeker wrote:
> Just use O_CLOEXEC or SOCK_CLOEXEC on everything. There is no reason to
> keep any kind of file descriptor over an exec call. At least this way
> I'm sure that no fds will leak into the childs.
>
> OK?
OK bluhm@
> Index: carp.c
>
Hi,
I'm trying to improve Pinebook experience on OpenBSD. I added a few more
sensors to axppmic 803.
I have two boards I tested this patch on:
- Pinebook: axppmic0 at sxirsb0 addr 0x3a3: AXP803
$ sysctl hw.sensors.axppmic0
hw.sensors.axppmic0.temp0=42.55 degC
hw.sensors.axppmic0.volt0=3.85 VDC
OK kn
I need to be able to control the bind address for openrsync connections.
This implements this but it only works for connections to an rsync daemon.
For rsync over ssh you need to use -e 'ssh -b address' instead.
--
:wq Claudio
Index: extern.h
On Thu, Aug 08, 2019 at 11:48:08AM +0200, Claudio Jeker wrote:
> With the introduction of re-exec of the childs the config parsing happened
> after bgpd demonized. This is super annoying and therefor this diff
> changes that. It will make bgpd fail on startup if there is an issue with
> the config
Hi,
The change below adds ic type 13 as an elantech v4 device and causes
the touchpad in a thinkpad x380 yoga to work as described in wsmouse(4).
Two finger scrolling works and the three mouse button areas are defined
as described. Before the touchpad and trackpoint were attached as a
single
Just use O_CLOEXEC or SOCK_CLOEXEC on everything. There is no reason to
keep any kind of file descriptor over an exec call. At least this way
I'm sure that no fds will leak into the childs.
OK?
--
:wq Claudio
? obj
Index: carp.c
Hi,
With the introduction of re-exec of the childs the config parsing happened
after bgpd demonized. This is super annoying and therefor this diff
changes that. It will make bgpd fail on startup if there is an issue with
the config file. I could not move the control socket setup before
12 matches
Mail list logo