This diff allows a single space for sentence delimitation.
ok/comments/objections? The default of a double space is left as is.
mark
Index: def.h
===
RCS file: /cvs/src/usr.bin/mg/def.h,v
retrieving revision 1.154
diff -u -p -u -p
On Tue, Apr 12, 2016 at 05:03:39PM +0200, Mark Kettenis wrote:
> > On Fri, Apr 08, 2016 at 12:16:03PM +, Visa Hankala wrote:
> > > Every now and then I see "spurious interrupt 34" messages on octeon
> > > serial console. The root cause seems to be in comstart() which enables
> > > the TX
On Tue, Apr 12, 2016 at 07:14:16PM +0200, Ingo Schwarze wrote:
> [moved to tech@, source-changes is not ideal for discussions]
>
> Marc Espie wrote on Tue, Apr 12, 2016 at 03:44:34PM +0200:
> > On Tue, Apr 12, 2016 at 11:24:40PM +1000, Jonathan Gray wrote:
> >> On Tue, Apr 12, 2016 at 02:36:09PM
On Tue, Apr 12, 2016 at 19:14 +0200, Ingo Schwarze wrote:
> [moved to tech@, source-changes is not ideal for discussions]
>
> Marc Espie wrote on Tue, Apr 12, 2016 at 03:44:34PM +0200:
> > On Tue, Apr 12, 2016 at 11:24:40PM +1000, Jonathan Gray wrote:
> >> On Tue, Apr 12, 2016 at 02:36:09PM
On Mon, 11 Apr 2016 14:47:20 -0400, Rob Pierce wrote:
> Running pstat with either [-M core] or [-N system] along with the -T option
> results in a segmentation fault. Make sure kvm access is initialized prior
> to running kvm_read() when -T is specified.
>
> This issue appears to have been
[moved to tech@, source-changes is not ideal for discussions]
Marc Espie wrote on Tue, Apr 12, 2016 at 03:44:34PM +0200:
> On Tue, Apr 12, 2016 at 11:24:40PM +1000, Jonathan Gray wrote:
>> On Tue, Apr 12, 2016 at 02:36:09PM +0200, Marc Espie wrote:
>>> On Tue, Apr 12, 2016 at 08:18:33PM +1000,
Hi Mark,
Mark Lumsden wrote on Tue, Apr 12, 2016 at 06:47:40PM +:
> This diff allows a single space for sentence delimitation.
> ok/comments/objections?
No objection, but a comment. Note that *using* the option is
destructive. Once you have replaced double spaces at the ends
of sentences
Marc Espie wrote:
> Parentheses are okay in urls, so I see no reason why:
>
> man.openbsd.org/carp(4)
>
> shouldn't work.
There are an astounding number of text to html URL parsers/highlighters that
cannot quite handle parentheses. That's not our problem, but instead of trying
to boil the
Hi Mike,
Mike Belopuhov wrote on Tue, Apr 12, 2016 at 08:41:16PM +0200:
> why is 3p still on the "sections" list in the fs_search?
> Just a lookup optimization?
No. The purpose of the function fs_search() is not optimization,
but fallback. If the requested manual is found in a database, that
Hardcoding stuff makes no sense.
There are enough variations out there.
Default + config probably.
As far as putting links in the faq, does it make sense to let man resolve
stuff instead of providing the redirection link directly ?
Actually, I think that in this day and age, the query? syntax
Hi,
Ted Unangst wrote on Tue, Apr 12, 2016 at 03:37:42PM -0400:
> Marc Espie wrote:
>> I think that in this day and age, the query? syntax is cumbersome
I fully agree, the query syntax is obsolete for deep linking.
It is supported for the HTML form frontend and for backward
compatibility only.
On Tue, Apr 12, 2016 at 09:50:44PM +0200, Ingo Schwarze wrote:
> Exactly what i did. It already works. Try it.
Ah, but the .Xr inside the renderer html still use the old ?query syntax,
so it is not exactly obvious this is going to work!
On Wed, Apr 06, 2016 at 12:15 +0200, Mike Belopuhov wrote:
> Hi,
>
> The EBUSY hack that I'm removing imposes an order on the ifconfig
> commands issued against the pppoe interface used to configure the
> sppp layer below. Right now ifconfig will fail with "device busy"
> after the
Hi Ingo,
On Tue, Apr 12, 2016 at 08:39:07PM +0200, Ingo Schwarze wrote:
> Hi Mark,
>
> Mark Lumsden wrote on Tue, Apr 12, 2016 at 06:47:40PM +:
>
> > This diff allows a single space for sentence delimitation.
> > ok/comments/objections?
>
> No objection, but a comment. Note that *using*
Hoist sysct and kvm calls, and pledge stdio, rpath, vminfo.
Rob
Index: pstat.c
===
RCS file: /cvs/src/usr.sbin/pstat/pstat.c,v
retrieving revision 1.102
diff -u -p -r1.102 pstat.c
--- pstat.c 12 Apr 2016 16:53:42 -
On Tue, Apr 12, 2016 at 03:37:42PM -0400, Ted Unangst wrote:
> Marc Espie wrote:
> > Parentheses are okay in urls, so I see no reason why:
> >
> > man.openbsd.org/carp(4)
> >
> > shouldn't work.
>
> There are an astounding number of text to html URL parsers/highlighters that
> cannot quite
Hi Mike,
Mike Belopuhov wrote on Tue, Apr 12, 2016 at 08:01:23PM +0200:
> IMO it's a very bad idea to hardcode "3p/" like that.
> Aren't there packages using other funny section names?
Packages are in a different manual tree /usr/local/man/, which gets
lower priority than /usr/share/man/ in the
On Tue, Apr 12, 2016 at 20:27 +0200, Ingo Schwarze wrote:
> Hi Mike,
>
> Mike Belopuhov wrote on Tue, Apr 12, 2016 at 08:01:23PM +0200:
>
> > IMO it's a very bad idea to hardcode "3p/" like that.
> > Aren't there packages using other funny section names?
>
> Packages are in a different manual
On 12 April 2016 at 21:49, Theo Buehler wrote:
> On Tue, Apr 12, 2016 at 03:37:42PM -0400, Ted Unangst wrote:
>> Marc Espie wrote:
>> > Parentheses are okay in urls, so I see no reason why:
>> >
>> > man.openbsd.org/carp(4)
>> >
>> > shouldn't work.
>>
>> There are an
On 12 April 2016 at 22:25, Rob Pierce wrote:
> Hoist sysct and kvm calls, and pledge stdio, rpath, vminfo.
>
> Rob
>
Please make sure that "pstat -d" still works. It's about the most useful
thing it can do.
Did you bring this up to Pascal Dornier ? I think he would rather fix
the eeprom...
This is specific to the hardware layout, the eeprom is the right place,
not the driver!
On the other hand, I think the CSR_WRITE_1 is perfectly clear
Stuart Henderson [s...@spacehopper.org] wrote:
> The
The re(4) variant on the PC Engines APU1, RTL8111E, has a flexible LED
configuration. The nic's default config seems to be intended for
controlling 3 LEDs (or one single-colour and a bi-colour LED with
different colours to indicate link speed) however the ethernet ports
on the APU1 only have two
Can you try the diff below? I'd like to know what is happening.
Index: efiboot.c
===
RCS file: /cvs/src/sys/arch/amd64/stand/efiboot/efiboot.c,v
retrieving revision 1.11
diff -u -p -r1.11 efiboot.c
--- efiboot.c 4 Feb 2016
On 2016/04/12 14:31, Chris Cappuccio wrote:
> Did you bring this up to Pascal Dornier ? I think he would rather fix
> the eeprom...
No, but it came up a few times on the forums and, assuming he's logging
in as "support" there, he knows about it:
Hi,
Thank you for your report.
The diff seems to make sense for the issue. I'll fix it on the CVS soon.
On Mon, 11 Apr 2016 21:26:37 +0200
"Vegar Linge Haaland" wrote:
> Hi! I am hitting an issue in efiboot on my HP Stream 13. Patch below. Sorry
> if this is the wrong list.
On Tue, Apr 12, 2016 at 06:24:10AM +, Miod Vallat wrote:
> > wskbd_enable (calls pckbd_enable) does not appear to be called from
> > wskbd_activate, perhaps just calling wskbd_enable from there would be
> > better? (as a matter of fact, wskbd_activate doesn't really do much at
> > all except
On 12/04/16(Tue) 17:16, Jonathan Gray wrote:
> On Thu, Apr 07, 2016 at 04:45:43PM +0200, Martin Pieuchot wrote:
> > On 07/04/16(Thu) 22:29, Jonathan Gray wrote:
> > > On Thu, Apr 07, 2016 at 01:47:13PM +0200, Martin Pieuchot wrote:
> > > > If we need a random value to fake an Ethernet address,
As reported by jsg@ the wifi stack should use if_start() just like the
rest of the kernel. One of the patterns can even be converted to
if_enqueue().
Tested with:
iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34
ok?
Index: net80211/ieee80211_input.c
> wskbd_enable (calls pckbd_enable) does not appear to be called from
> wskbd_activate, perhaps just calling wskbd_enable from there would be
> better? (as a matter of fact, wskbd_activate doesn't really do much at
> all except set sc_dying=1, and I'm not sure where that gets reset.)
Nooo!
On Thu, Apr 07, 2016 at 04:45:43PM +0200, Martin Pieuchot wrote:
> On 07/04/16(Thu) 22:29, Jonathan Gray wrote:
> > On Thu, Apr 07, 2016 at 01:47:13PM +0200, Martin Pieuchot wrote:
> > > If we need a random value to fake an Ethernet address, let's use
> > > arc4random(9).
> > >
> > > ok?
> >
> >
> I think the best idea is to proceed with the diff as posted, with
> the added check to make sure the keyboard is enabled, and to always
> call config_activate_children on all paths through pckbd_activate?
>
> In other words, no changes to wskbd_enable or wskbd_activate.
>
> Sound right?
I
On Tue, Apr 12, 2016 at 09:38:53AM +0200, Martin Pieuchot wrote:
> On 12/04/16(Tue) 17:16, Jonathan Gray wrote:
> > On Thu, Apr 07, 2016 at 04:45:43PM +0200, Martin Pieuchot wrote:
> > > On 07/04/16(Thu) 22:29, Jonathan Gray wrote:
> > > > On Thu, Apr 07, 2016 at 01:47:13PM +0200, Martin Pieuchot
On Tue, Apr 12, 2016 at 08:34:08AM +0200, Martin Pieuchot wrote:
> As reported by jsg@ the wifi stack should use if_start() just like the
> rest of the kernel. One of the patterns can even be converted to
> if_enqueue().
Note that if_enqueue() checks for a bridge port and, if present, sends
On 12 April 2016 at 08:34, Martin Pieuchot wrote:
> As reported by jsg@ the wifi stack should use if_start() just like the
> rest of the kernel. One of the patterns can even be converted to
> if_enqueue().
>
> Tested with:
> iwn0 at pci2 dev 0 function 0 "Intel Centrino
On 2016/04/12 08:32, sven falempin wrote:
> still advocating for a structured output of system commands like ifconfig
> -json,
freebsd is > that way ;-)
Relying on the "scopeid" field is not a viable long-term solution. I'm
spending too much time these days trying to figure out which interface
correspond to which index.
Here's a difference in output, then the diff itself. ok?
@@ -1,31 +1,29 @@
lo0: flags=8049
On 12/04/16(Tue) 12:34, Stefan Sperling wrote:
> On Tue, Apr 12, 2016 at 08:34:08AM +0200, Martin Pieuchot wrote:
> > As reported by jsg@ the wifi stack should use if_start() just like the
> > rest of the kernel. One of the patterns can even be converted to
> > if_enqueue().
>
> Note that
On 2016/04/12 14:18, Claudio Jeker wrote:
> On Tue, Apr 12, 2016 at 01:47:53PM +0200, Stefan Sperling wrote:
> > On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson wrote:
> > > On 2016/04/12 13:00, Martin Pieuchot wrote:
> > > > Relying on the "scopeid" field is not a viable long-term
On Tue, Apr 12, 2016 at 8:18 AM, Claudio Jeker
wrote:
> On Tue, Apr 12, 2016 at 01:47:53PM +0200, Stefan Sperling wrote:
> > On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson wrote:
> > > On 2016/04/12 13:00, Martin Pieuchot wrote:
> > > > Relying on the
On Fri, Apr 08, 2016 at 12:16:03PM +, Visa Hankala wrote:
> Every now and then I see "spurious interrupt 34" messages on octeon
> serial console. The root cause seems to be in comstart() which enables
> the TX holding register empty interrupt before writing data to the TX
> register. If the
On 2016/04/12 13:00, Martin Pieuchot wrote:
> Relying on the "scopeid" field is not a viable long-term solution. I'm
> spending too much time these days trying to figure out which interface
> correspond to which index.
>
> Here's a difference in output, then the diff itself. ok?
>
> @@ -1,31
On 2016/04/12 13:10, Martin Pieuchot wrote:
> On 12/04/16(Tue) 12:34, Stefan Sperling wrote:
> > On Tue, Apr 12, 2016 at 08:34:08AM +0200, Martin Pieuchot wrote:
> > > As reported by jsg@ the wifi stack should use if_start() just like the
> > > rest of the kernel. One of the patterns can even be
On Tue, Apr 12, 2016 at 01:10:33PM +0200, Martin Pieuchot wrote:
> What's the use case of bridging wireless interfaces. Does that work?
You can have an AP which bridges wifi clients into a LAN:
wifi-client ))) athn0(AP)-bridge0-em0 -> LAN
Now wifi-client and the LAN can talk on layer 2. I use
On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson wrote:
> On 2016/04/12 13:00, Martin Pieuchot wrote:
> > Relying on the "scopeid" field is not a viable long-term solution. I'm
> > spending too much time these days trying to figure out which interface
> > correspond to which index.
> >
On Tue, Apr 12, 2016 at 01:47:53PM +0200, Stefan Sperling wrote:
> On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson wrote:
> > On 2016/04/12 13:00, Martin Pieuchot wrote:
> > > Relying on the "scopeid" field is not a viable long-term solution. I'm
> > > spending too much time these days
On 12/04/16(Tue) 14:03, Stuart Henderson wrote:
> On 2016/04/12 14:18, Claudio Jeker wrote:
> > On Tue, Apr 12, 2016 at 01:47:53PM +0200, Stefan Sperling wrote:
> > > On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson wrote:
> > > > On 2016/04/12 13:00, Martin Pieuchot wrote:
> > > > >
On 26 March 2016 at 16:25, Mike Belopuhov wrote:
> On Fri, Mar 25, 2016 at 22:43 +0100, Mark Kettenis wrote:
>> > From: Mike Belopuhov
>> > Date: Thu, 24 Mar 2016 21:33:25 +0100
>> >
>> > On 24 March 2016 at 20:53, Mark Kettenis
On 12 April 2016 at 15:12, Visa Hankala wrote:
> On Fri, Apr 08, 2016 at 12:16:03PM +, Visa Hankala wrote:
>> Every now and then I see "spurious interrupt 34" messages on octeon
>> serial console. The root cause seems to be in comstart() which enables
>> the TX holding
On 12/04/16(Tue) 15:31, Mike Belopuhov wrote:
> On 12 April 2016 at 15:12, Visa Hankala wrote:
> > On Fri, Apr 08, 2016 at 12:16:03PM +, Visa Hankala wrote:
> >> Every now and then I see "spurious interrupt 34" messages on octeon
> >> serial console. The root cause seems to
On 2016-04-12, Martin Pieuchot wrote:
> Relying on the "scopeid" field is not a viable long-term solution. I'm
> spending too much time these days trying to figure out which interface
> correspond to which index.
What's the general use case for this? I mean apart from
> Date: Tue, 12 Apr 2016 13:12:42 +
> From: Visa Hankala
>
> On Fri, Apr 08, 2016 at 12:16:03PM +, Visa Hankala wrote:
> > Every now and then I see "spurious interrupt 34" messages on octeon
> > serial console. The root cause seems to be in comstart() which enables
> >
On 12/04/16(Tue) 14:43, Christian Weisgerber wrote:
> On 2016-04-12, Martin Pieuchot wrote:
>
> > Relying on the "scopeid" field is not a viable long-term solution. I'm
> > spending too much time these days trying to figure out which interface
> > correspond to which index.
>
Christian Weisgerber(na...@mips.inka.de) on 2016.04.12 14:43:50 +:
> On 2016-04-12, Martin Pieuchot wrote:
>
> > Relying on the "scopeid" field is not a viable long-term solution. I'm
> > spending too much time these days trying to figure out which interface
> > correspond
Hi tech@
Based on recommendation from ratchov@ to put his advice for recording
an audio output monitor in the FAQ as 13.5:
[http://marc.info/?m=146039522014603]
Proposing the diffs to FAQ 13 here, and the FAQ index below [1]. Hope
this goes mangle-free by the mail client, ready to resend if
Martin Pieuchot(m...@openbsd.org) on 2016.04.12 16:25:36 +0200:
> On 12/04/16(Tue) 14:03, Stuart Henderson wrote:
> > On 2016/04/12 14:18, Claudio Jeker wrote:
> > > On Tue, Apr 12, 2016 at 01:47:53PM +0200, Stefan Sperling wrote:
> > > > On Tue, Apr 12, 2016 at 12:27:10PM +0100, Stuart Henderson
Hi Sebastien,
Sebastien Marie wrote on Tue, Apr 12, 2016 at 05:09:45PM +0200:
> "mcast" promise isn't documented (used in eigrpd, ldpd, ospfd, and
> route6d).
>
> This promise allows only some options with getsockopt(2)/setsockopt(2):
>
> - IPV6_MULTICAST_IF : Get or set the interface from
56 matches
Mail list logo