Re: OpenSSH HPN

[Jason Birch]

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 some commands on a remote machine,
and due to $CIRCUMSTANCE I don't need or desire encryption" are covered
by the older, also standard tools. Additionally, rsync can use rsh as its
transport, for users who desire more advanced behaviour. ssh just seems
to have more support; Installation will ask you if you'd like to run sshd
(not rshd), ssh is rather ubiquitous as a way of "doing a thing remotely"
(even in Windows soon!), etc. This is a good default to have; the
overhead of security is tiny in nearly all cases.

It would seem then that the extra complexity of maintenance development
in supporting NONE in base doesn't really grant us any additional
functionality in most cases. It's just more 'obvious'.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

portversion doesn't seem to know what's out of date

[Jason Birch]

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`
afterwards, to fetch anything that might need upgrading.

When I returned, I found that portversion seemed to think everything was up
to date, but `portupgrade -aF` had found and downloaded upgrades to ruby,
pkg, Net-SSLeay, gnutls, and emacs-nox11. Checking the verbose output of
portversion, I saw that portversion seemed to think the out-of-date version
was up to date with the port...

root@beaglebone:/usr/home/jbirch  # portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... none found.
Fetching snapshot tag from portsnap.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Thu Jul 10 04:42:24 UTC 2014 to Sun Jul 27 05:09:26 UTC
2014.

Fetching 63 new ports or files... done.

root@beaglebone:/usr/home/jbirch # portsnap update
Removing old files and directories... done.
Extracting new files:
/usr/ports/CHANGES

/usr/ports/editors/emacs-nox11/

/usr/ports/lang/ruby19/

/usr/ports/ports-mgmt/pkg/

/usr/ports/security/gnutls/

/usr/ports/security/p5-Net-SSLeay/


root@beaglebone:/usr/home/jbirch # portversion | grep \
[Reading data from pkg(8) ... - 63 packages found - done]

root@beaglebone:/usr/home/jbirch # portupgrade -aF
[Reading data from pkg(8) ... - 63 packages found - done]
---  Fetching the distfile(s) for 'ruby-1.9.3.547,1' (lang/ruby19)

---  Fetching the distfile(s) for 'pkg-1.3.1' (ports-mgmt/pkg)

---  Fetching the distfile(s) for 'p5-Net-SSLeay-1.65'
(security/p5-Net-SSLeay)

---  Fetching the distfile(s) for 'gnutls-3.2.16_1' (security/gnutls)

---  Fetching the distfile(s) for 'emacs-nox11-24.3_11,3'
(editors/emacs-nox11)


root@beaglebone:/usr/home/jbirch # portversion -v
[Reading data from pkg(8) ... - 63 packages found - done]

emacs-nox11-24.3_10,3   =  up-to-date with port

gnutls-2.12.23_6=  up-to-date with port

p5-Net-SSLeay-1.64  =  up-to-date with port

pkg-1.2.7_4 =  up-to-date with port

ruby-1.9.3.484_2,1  =  up-to-date with port


root@beaglebone:/usr/home/jbirch # uname -a
FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268309: Sun
Jul  6 22:13:49 EST 2014
jbirch@267801:/usr/home/jbirch/crochet-freebsd/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE
 arm

I'm trying to update just pkg for the moment to see if that helps the
situation, but it seems to be stuck in some sort of configure loop when
building from ports. I'll leave it for the night, as each loop seems to
compile something different.

pkg check is offering no hints as to if anything is awry -- it just looks
like portversion is looking at something completely different, or not
looking at anything at all.

Has anyone seen this behaviour before, or can point me forward?

JB
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 2013 MacBook Air Project

[Jason Birch]

On Mon, Sep 2, 2013 at 4:16 AM, Adrian Chadd adr...@freebsd.org 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 out of my depth I was :)

On Mon, Sep 2, 2013 at 11:02 AM, Lundberg, Johannes 
johan...@brilliantservice.co.jp wrote:

 This is the info OSX gives me about the 11 2013 MacBook Air.


After a little bit of Googling, it looks like the chip inside the mid-2013
MacBook Air is the Broadcom BCM4360 (Not the 4331 I've played with) which
is currently _not_ supported[1] by the legacy b43 Linux driver.
Additionally, it doesn't seem to be listed in the list of supported devices
of Broadcom's official open-source Linux drivers[2].

Broadcom's website seems a little helpful - they offer you the ability to
submit a request for driver help - but not for this model of chip. I think
your best bet will be to work from the sources of the bcmwl driver[3] -
which /might/ be related to the brcm80211 stuff? I've not dug any further.

[1] http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices
[2] http://wireless.kernel.org/en/users/Drivers/brcm80211#Supported_Chips
[3] https://launchpad.net/ubuntu/+source/bcmwl

JB
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 2013 MacBook Air Project

[Jason Birch]

 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_ driver. I don't know off hand what particular chip is inside
the 2013 MacBook Air, but if you can get some help in getting a driver
working, it would be very valuable to the larger open-source community, and
everyone who's ever dealt with flaky wireless and signal intensity issues
running something other than Windows or OS X on MacBooks.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: BSD sleep

[Jason Birch]

 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, and do it well. What you have proposed involves:
 * an additional force flag
 * interpolation of what follows the force flag (does m mean minutes, or
months?)
 * expectations around time, time zones, and what an hours is.

That fails the litmus test on complexity for me personally - it seems like
a lot of complexity for not much gain.



 P.S. There is already non-portable feature in sleep - non-integer, and I'm
 sure that no one thought about some financists from various countries, who
 used to specify long numbers with separator, e.g. 3.600, and this means for
 them one hour and not 3 point 6 seconds.


This isn't a good reason for adding another non-portable feature.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org