On Wed, 31 Jan 2018 17:05:57 -0500
Bryan Steele wrote:
> On Wed, Jan 31, 2018 at 10:41:48PM +0100, Christian Weisgerber wrote:
>> Alexei Malinin:
>>
>> > If the base system supported multi-booting in MBR would the community be
>> > interested in it?
>>
>> It should be easy to adapt FreeBSD's boo
On Thu, 01 Feb 2018 01:55:18 +0200, Kapetanakis Giannis wrote:
> On 01/02/18 00:06, Todd C. Miller wrote:
> >
> > Shouldn't this be:
> >
> > # Log everything coming from host bastion to a separate file
> > ++bastion /var/log/bastion
> > *.*
> > +*
>
> how
On 01/02/18 00:06, Todd C. Miller wrote:
Shouldn't this be:
# Log everything coming from host bastion to a separate file
++bastion /var/log/bastion
*.*
+*
how about
# Log everything coming from host bastion to a separate file
++bastion
On Wed, 31 Jan 2018 20:44:10 +0100, Landry Breuil wrote:
> the default etc/syslog.conf has a commented out example for by-prog
> logging, but nothing for by-host logging. I fighted a bit with it; so
> why not providing an example in the EXAMPLES section of the manpage ?
I recently did the same so
On Wed, Jan 31, 2018 at 10:41:48PM +0100, Christian Weisgerber wrote:
> Alexei Malinin:
>
> > If the base system supported multi-booting in MBR would the community be
> > interested in it?
>
> It should be easy to adapt FreeBSD's boot0. I don't remember any
> demand for it, and now MBR is on its
Alexei Malinin:
> If the base system supported multi-booting in MBR would the community be
> interested in it?
It should be easy to adapt FreeBSD's boot0. I don't remember any
demand for it, and now MBR is on its way out...
https://svnweb.freebsd.org/base/head/stand/i386/boot0/boot0.S
boot0 +
On Wed, Jan 31, 2018 at 07:51:08PM +0100, Jeremie Courreges-Anglas wrote:
> On Wed, Jan 31 2018, Patrick Wildt wrote:
> > On Wed, Jan 31, 2018 at 09:46:52AM -0800, Mike Larkin wrote:
> >> On Wed, Jan 31, 2018 at 05:12:03PM +0100, Patrick Wildt wrote:
> >> > Hi,
> >> >
> >> > this diff allows us t
Hi,
the default etc/syslog.conf has a commented out example for by-prog
logging, but nothing for by-host logging. I fighted a bit with it; so
why not providing an example in the EXAMPLES section of the manpage ?
Landry
Index: syslog.conf.5
On 31 January 2018 at 16:21, Martin Pieuchot wrote:
> Thanks for all the feedbacks I received. Diff below addresses multiple
> points after discussion with dlg@ and martijn@:
>
> - Stop using the word 'group' which confuse people. Instead talk of
> 'protected domain'. Interfaces that are
On [31/01/18] [01:53P], Kevin Lo wrote:
; On Wed, Jan 31, 2018 at 01:25:10PM +0100, Stefan Sperling wrote:
; >
; > If iwn(4) is in associated state (status: active), and I run:
; >
; > ifconfig iwn0 scan
; >
; > it loses link (status: no network) and never comes back while the
; > LED keeps
On Wed, Jan 31 2018, Patrick Wildt wrote:
> On Wed, Jan 31, 2018 at 09:46:52AM -0800, Mike Larkin wrote:
>> On Wed, Jan 31, 2018 at 05:12:03PM +0100, Patrick Wildt wrote:
>> > Hi,
>> >
>> > this diff allows us to load the Intel microcode much earlier. So far
>> > we load it after the CPUs have i
On Wed, Jan 31, 2018 at 09:46:52AM -0800, Mike Larkin wrote:
> On Wed, Jan 31, 2018 at 05:12:03PM +0100, Patrick Wildt wrote:
> > Hi,
> >
> > this diff allows us to load the Intel microcode much earlier. So far
> > we load it after the CPUs have identified and then have to update the
> > CPU flag
On Wed, Jan 31, 2018 at 05:12:03PM +0100, Patrick Wildt wrote:
> Hi,
>
> this diff allows us to load the Intel microcode much earlier. So far
> we load it after the CPUs have identified and then have to update the
> CPU flags afterwards. This is not good since we have to assume that
> those upda
On 22/01/18(Mon) 16:23, Martin Pieuchot wrote:
> Diff below adds a new feature to bridge(4), similar to Cisco's Protected
> Port but with more possibilities.
>
> The idea is to prevent traffic to flow between some members of a bridge(4).
> For example:
> - you want to prevent some of your server
Hello.
If the base system supported multi-booting in MBR would the community be
interested in it?
--
Alexei Malinin
Hi,
this diff allows us to load the Intel microcode much earlier. So far
we load it after the CPUs have identified and then have to update the
CPU flags afterwards. This is not good since we have to assume that
those updates can remove and add instructions and other features. We
need to load it
On Wed, Jan 31, 2018 at 04:20:39PM +0100, Mark Kettenis wrote:
> Shouldn't these new entries be _VHT_ instead of _HT_?
Yes, they should. Thanks for checking!
It seems I'm a rather sloppy copy/paste editor today.
Index: if_media.h
===
> Date: Wed, 31 Jan 2018 14:59:24 +0100
> From: Stefan Sperling
>
> On Wed, Jan 31, 2018 at 02:49:38PM +0100, Stefan Sperling wrote:
> > bwfm(4) will do 11ac (Very High Throughput), so add media types for it.
> >
> > ok?
>
> phessler points out that I botched the IFM_IEEE80211_11AC macro.
>
>
On Wed, Jan 31, 2018 at 02:49:38PM +0100, Stefan Sperling wrote:
> bwfm(4) will do 11ac (Very High Throughput), so add media types for it.
>
> ok?
phessler points out that I botched the IFM_IEEE80211_11AC macro.
Fixed:
Index: if_media.h
==
On Wed, Jan 31, 2018 at 01:25:10PM +0100, Stefan Sperling wrote:
>
> If iwn(4) is in associated state (status: active), and I run:
>
> ifconfig iwn0 scan
>
> it loses link (status: no network) and never comes back while the
> LED keeps blinking. I need to run 'ifconfig iwn0 down' to recove
bwfm(4) will do 11ac (Very High Throughput), so add media types for it.
ok?
Index: if_media.h
===
RCS file: /cvs/src/sys/net/if_media.h,v
retrieving revision 1.40
diff -u -p -r1.40 if_media.h
--- if_media.h 15 Nov 2017 01:11:45 -000
On Mon, Jan 29, 2018 at 01:02:41PM +0100, Martin Pieuchot wrote:
> ...instead of incrementing f_count directly, ok?
OK bluhm@
> Index: nfs/nfs_syscalls.c
> ===
> RCS file: /cvs/src/sys/nfs/nfs_syscalls.c,v
> retrieving revision 1.111
If iwn(4) is in associated state (status: active), and I run:
ifconfig iwn0 scan
it loses link (status: no network) and never comes back while the
LED keeps blinking. I need to run 'ifconfig iwn0 down' to recover.
What happens is the driver goes to SCAN state and sends a scan
command to
On Wed, Jan 24, 2018 at 06:42:42PM +0100, Stefan Sperling wrote:
> I just observed iwn(4) firmware reporting a missed beacon event
> during a background scan:
>
> Jan 24 18:24:50 laptop /bsd: iwn0: begin background scan
> Jan 24 18:24:57 laptop /bsd: iwn0: sending probe_req to xx:xx:xx:xx:xx:xx on
24 matches
Mail list logo