Hello
I was considering submitting a patch to rearrange some USB devices in the
GENERIC kernel config. I wanted to get some feedback / comments before I
submit a PR.
What I was going to propose is moving rum(4), ural(4), uath(4) and zyd(4) into
a separate USB section, similar to 'USB
FYI,
after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
samba33 programmes did abort() immediately after start. The
solution was to use
CONFIGURE_ARGS+= --disable-pie
-Andre
--
BSD, from the people who brought you TCP/IP.
___
Matt Dawson wrote:
Odd little issue just cropped up on my lappie running 8.0-RC1 amd64. On 7.2
the ral(4) wireless NIC (2560 1st gen mini-PCI) gave me the Japanese
regulatory domain allocations (2.412GHz to 2.477GHz, 14 channels) on
802.11g. I understand a lot has changed with 802.11 on 8, but
On Sat, 3 Oct 2009 14:42 -, Andre.Albsmeier wrote:
FYI,
after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
samba33 programmes did abort() immediately after start. The
solution was to use
CONFIGURE_ARGS+= --disable-pie
-Andre
To add an additional note samba33 even
On Sat, 03-Oct-2009 at 16:27:32 -0400, jhell wrote:
On Sat, 3 Oct 2009 14:42 -, Andre.Albsmeier wrote:
FYI,
after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
samba33 programmes did abort() immediately after start. The
solution was to use
CONFIGURE_ARGS+=
On Saturday 03 Oct 2009 19:28:50 you wrote:
ral probably does not populate it's initial channel list according to
the device capabilities. I'm guessing it falls back on the system code
to do that and it fills in only channels 1-11. This means future
changes to regulatory cannot setup the
On Sat, 3 Oct 2009, Andre Albsmeier wrote:
Hi,
On Sat, 03-Oct-2009 at 16:27:32 -0400, jhell wrote:
On Sat, 3 Oct 2009 14:42 -, Andre.Albsmeier wrote:
FYI,
after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
samba33 programmes did abort() immediately after start. The
solution
