On 22:20 19-Apr 2015 Stuart Henderson wrote:
> On 2015/04/19 11:27, Mikhail wrote:
> > -.Dd $Mdocdate: March 30 2015 $
> > +.Dd $Mdocdate: April 19 2015 $
>
> No need to change this, it happens at commit.
>
> > -The RTL8188CUS is a highly integrated 802.11n adapter that combines
> > -a MAC, a 1T1
On 2015/04/19 11:27, Mikhail wrote:
> -.Dd $Mdocdate: March 30 2015 $
> +.Dd $Mdocdate: April 19 2015 $
No need to change this, it happens at commit.
> -The RTL8188CUS is a highly integrated 802.11n adapter that combines
> -a MAC, a 1T1R capable baseband and an RF in a single chip.
> +The RTL8188
Hi,
when security(8) uses open(..., '-|', ...) to fork a command
and capture the output, and that command fails, it reports
the exit status in the daily security mail. One of the
commands forked that way is diff(1), which is documented
as follows:
EXIT STATUS
The diff utility exits with o
On Sun, Apr 19, 2015 at 11:27:52AM +0300, Mikhail wrote:
> I'm not sure what is the correct procedure
> of submitting it to firmware.openbsd.org.
Please prepare a patch for /usr/ports/sysutils/firmware/urtwn.
> I've tested it with TP-LINK TL-WN725N with usual network activity.
Thanks! I will tak
This paragraph should talk about prebinding instead of prelinking,
shouldn't it?
Also, it seems "prebind data" sounds more correct than "prebinding
data", but I could easily get wrong here.
--
WBR,
Vadim Zhukov
Index: ldconfig.8
Hello, I inline the patch for rtl8188eu chip support in urtwn driver,
origins for this patch are in r264912[1] from FreeBSD. In order to work,
correct firmware must be presented in /etc/firmware - one can be found
in FreeBSD commit itself[2] - I'm not sure what is the correct procedure
of submittin
