"sticky-address" seems to work with "source-hash".
But the manual page looks like:
round-robin [sticky-address]
The round-robin option...
source-hash [key]
The source-hash option...
This misleads people think source-hash doesn't work with
sticky-address.
ok?
Index:
Dear Ingo,
On 4/23/19 9:30 PM, Ingo Schwarze wrote:
>>> Index: rcsfile.5
> [...]
>>> +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>>> +.\"
>
>> Nitpick: The other man pages in the usr.bin/rcs/ tree do not have a
>> trailing .\" -- except for rcs(1).
>> You may wish to make
Hi all,
I have one question about *relayd*.
FILE: /usr.sbin/relayd/check_script.c
In function 'script_sig_alarm(int sig)':
** A function parameter ( sig ) is not used in the body of the
function.
** I think, that If the argument is needed for type
compatibility or
Hi,
with below diff the usb serial adapter built into the SRX 300 attaches
to uslcom and can be used.
uslcom0 at uhub1 port 1 configuration 1 interface 0 "Silicon Labs Juniper
Networks BX Series System Console" rev 1.10/1.01 addr 10
OK?
Remi
Index: usbdevs
Bryan Steele wrote:
> > I just got through building a new desktop machine and thought I'd
> > install OpenBSD -current on it. The install kernel booted quite fast,
> > but now that I have the real kernel there, it takes approximately 5
> > minutes to boot. The vast majority of the time is spent
Tobias Stoeckmann wrote:
> On Mon, Apr 22, 2019 at 01:24:13PM -0400, Ted Unangst wrote:
> > ah, good catch. I don't think it's wrong (until it overflows) but needs to
> > be
> > fixed. Needs some more review then. Thanks.
>
> I have added following changes:
>
> - converted 0u to 0 as bluhm
Ricardo Mestre(ser...@helheim.mooo.com) on 2019.04.23 00:42:46 +0100:
> Hi,
>
> I had a patch with pledge(2) for quite a while ago, but my setup is too simple
> and cannot test it enough so at least we can have restricted read access to
> the
> fs in relayd(8)'s main process through unveil(2).
Hi Fabio,
Fabio Scotoni wrote on Tue, Apr 23, 2019 at 07:46:31PM +0200:
> On 4/23/19 7:15 PM, Ingo Schwarze wrote:
>> Is it correct that you wrote all the text in the file?
>> If so, your name needs to be there.
> It is indeed correct that I wrote all the text in the file (except, by
>
> Date: Mon, 15 Apr 2019 08:55:10 +0200
> From: Patrick Wildt
>
> Hi,
>
> with kettenis' change from 2015(?) we can configure a ppb(4)'s bus
> information. Unfortunately the hotplug fixup code runs before that
> change has a chance, and it will program a single bus (with no amount
> of
Fabio Scotoni wrote:
> > According to the Berne Convention, even though you cannot give away
> > the moral rights that constitute the core of Copyright, you can give
> > away the economic rights arising from a Work. Some publishers of
> > software (for example the FSF) ask for that. But in
On 4/23/19 7:15 PM, Ingo Schwarze wrote:
>>> At the top of the file, a Copyright notice and license is missing.
>>> Please conisder using /usr/share/misc/license.template with the
>>> comment markers changed to .\" .
>
>> I intentionally skipped on adding the copyright notice and license
>>
> Date: Tue, 23 Apr 2019 18:50:50 +0200
> From: Denis Fondras
>
> Noticed by visa@
I don't think HOSTORY should describe the history of the man page
itself, but rather the history of the functionality it describes.
Since openprom(4) has been there from the start for OpenBSD/arm64, the
HISTORY
Hi Fabio,
i applied a very small number of minor tweaks and plan to commit
the patch below tomorrow based on OK jmc@ deraadt@ millert@,
unless i hear objections.
Fabio Scotoni wrote on Tue, Apr 23, 2019 at 05:19:48PM +0200:
> I've adjusted the updated man page (inline) .Dt and .Nm to match
Noticed by visa@
Index: man4.arm64/Makefile
===
RCS file: /cvs/src/share/man/man4/man4.arm64/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- man4.arm64/Makefile 2 Apr 2019 19:41:53 - 1.6
+++
On 21/04/19(Sun) 16:45, Martin Pieuchot wrote:
> Diff below removes the KERNEL_LOCK() from bridge(4)'s output fast-path.
>
> To do so, it redefines the ifp <-> bridge relationship. Currently every
> interface in a bridge(4) contains a pointer to that bridge's port. This
> relationship is
On Tue, 23 Apr 2019 14:52:09 +0200, Ingo Schwarze wrote:
> That wouldn't be me. Either way, an additional OK to import would be
> appreciated.
I like this too. OK millert@ for importing it.
- todd
Dear Ingo,
Thank you for your insightful suggestions,
which I've incorporated.
On 4/23/19 2:52 PM, Ingo Schwarze wrote:
> I think the source should go to /usr/src/usr.bin/rcs/rcs.5
> and it should be installed to /usr/share/man/man5/rcs.5.
I've adjusted the updated man page (inline) .Dt and .Nm
On Tue, Apr 23, 2019 at 02:52:09PM +0200, Ingo Schwarze wrote:
>
> That wouldn't be me. Either way, an additional OK to import would be
> appreciated.
>
> Yours,
> Ingo
>
if you feel it would be useful, go ahead.
jmc
Hi Fabio,
Fabio Scotoni wrote on Tue, Apr 23, 2019 at 01:45:22PM +0200:
> While familiarizing myself with OpenRCS,
> I noticed that there's no rcsfile(5).
> This may be handy for people whose RCS file got corrupted for whatever
> reasons.
> Other *NIXes that ship SCCS tend to have a sccsfile(4),
On Tue, 23 Apr 2019 11:55:01 +0200 Matthieu Herrb wrote:
> If you are actually running X, ...
Not on the old "S3 Trio3D AGP" Pentium II 350MHz machines Matthieu,
(these are used as small servers, some with VGA glass tube screens).
> This is an Intel chipset supported by the current DRM
While familiarizing myself with OpenRCS,
I noticed that there's no rcsfile(5).
This may be handy for people whose RCS file got corrupted for whatever
reasons.
Other *NIXes that ship SCCS tend to have a sccsfile(4),
so I figured it could be worthwhile to have something of that nature for
OpenRCS.
> On 22 Apr 2019, at 5:45 am, Martin Pieuchot wrote:
>
> Diff below removes the KERNEL_LOCK() from bridge(4)'s output fast-path.
>
> To do so, it redefines the ifp <-> bridge relationship. Currently every
> interface in a bridge(4) contains a pointer to that bridge's port. This
>
On Tue, Apr 23, 2019 at 10:28:18AM +0100, Craig Skinner wrote:
> On Mon, 22 Apr 2019 18:47:23 +0200 Matthieu Herrb wrote:
> > If you're still using a machine with a graphics card supported by one
> > of these, please speak up, otherwise they are going to be removed:
>
> Is this a valid way to
On Mon, 22 Apr 2019 18:47:23 +0200 Matthieu Herrb wrote:
> If you're still using a machine with a graphics card supported by one
> of these, please speak up, otherwise they are going to be removed:
Is this a valid way to find out Matthieu?
$ grep -i -e vga -e video /var/run/dmesg.boot
vga1 at
24 matches
Mail list logo
