On Wed, Nov 11, 2015 at 6:59 PM, John-Mark Gurney wrote:
> If you have a trusted network, why not just use nc?
Perhaps more generally relevant is that ssh/scp are *waves hands* vaguely
analogous to secure versions of rsh/rlogin/rcp. I'd think that most cases
of "I wanted to send files and invoke
I built FreeBSD for my Beaglebone Black a couple of weeks ago, and went to
do an update just then. After updating /usr/ports, I ran `portversion |
grep \<` to see a list of what could be updated. Knowing that this takes a
bit longer and needing to run out the door, I also type `portupgrade -aF`
aft
On Mon, Sep 2, 2013 at 4:16 AM, Adrian Chadd wrote:
> did you contribute this stuff back up to the linux driver?
>
I did not; I was simply following a few how-tos on a colleague's machine to
help her get a stable network connection. We never did fully crack that
nut; I quickly realised how far o
> Yup. I hope I get some positive responses from Broadcom. I really don't
> want to port the Linux driver(s), it's just plain silly.
>
I've noticed a hell of a lot of problems with the B4331 rev2 under Linux on
several distributions, which have been resolved for me by splicing apart
the _Windows_
> Seriously, that explanation about different hours is not enough to prevent
> at least useful option.
> like
> sleep -f 1h
> (-f means force convert, without it you can see good explanation why sleep
> for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at
> all.).
>
Do one thing,
