In Other BSDs for 2014/01/25

Back to relatively normal volume, this week.

In Other BSDs for 2014/01/18

I didn’t even need to find source links this week.

OpenBSD and electricity

The OpenBSD Project (Foundation?) needs to pay a large electrical bill for their hosting location.  I had mentioned this in a weekend BSD report just before the end of 2013, but the problem is still there and deserves a special mention.  It’s possible to contribute directly, or to the I-assume-nonprofit-so-tax-deductible-for-many-people OpenBSD Foundation.  You can set up a low but reoccurring Paypal payment for the Foundation, which would be probably unnoticeable for you but very helpful for the organization.

Even if you aren’t booting OpenBSD on anything, you’re using a technology that came out of that project – OpenSSH, pf, your dhcpclient, etc; or using 3rd-party software that received fixes from OpenBSD work.  Putting dollars towards this software development is one of the more effective things you can do with your money to help open source.

 

In Other BSDs for 2014/01/11

Running late putting this together…  Back to bullets!

In Other BSDs for 2014/01/04

Things are picking up again after the break.

In Other BSDs for 2013/12/28

Again, quiet from the holiday break.

In Other BSDs for 2013/12/21

Odds and ends for the quieter holidays.

In Other BSDs for 2013/12/14

Another week where I could get away without any commit links, just cause there’s so much BSD stuff out there.

A BSD plan: license summaries

I had a sometimes-great, sometimes-difficult trip to New York City over the past few days, and while I was there, I met the ball of energy that is George Rosamond of NYCBUG (which is having a huge party right now.)  He and I talked for a bit about various aspects of the BSD ecosystem, and one thing he noted was that people aren’t generally aware of all the licenses in use for the different software packages on the system, or even the individual licenses in the system files.

There is an ACCEPTABLE_LICENSES setting in pkgsrc, where software licensed under terms not in that list won’t install.  That’s useful, but frustrating, because it keeps people from getting what they asked for – a software install.  Something that would be useful – and it could be cross-BSD very easily – would be a license audit summary.

There’s meta-data on every package in FreeBSD’s ports and DragonFly’s dports and pkgsrc and OpenBSD’s port system.  Why not say ‘pkg licenses’ in the same way you can say ‘pkg info’, and get a summary of the licenses you have installed in the system?  (or pkg_licenses, etc.  You get the idea)  This wouldn’t prevent people from installing software, but it would give a very quick view of what you were using.


> pkg licenses

Software package    License
----------------    -------
foo-2.2.26          Apache license
bar-7.999999        Donateware
baz_ware-20131209   MIT
quux-silly-6.5      BSD

It could be extended to the base system, but I’d like to see this in all the packaging systems as a common idea, in the same way that ‘info’ in a packaging command always shows what’s installed.

In Other BSDs for 2013/12/07

Happy birthday to me!

In Other BSDs for 2013/11/30

A lighter week for commits probably because of the U.S. holiday, but still plenty of things to link.

In Other BSDs for 2013/11/23

I’m working my way up to more than just links to source for the cross-BSD news.  There’s a lot to swim through!

In Other BSDs for 2013/11/16

Not as much pulled directly from the source lists this time, which is good.

 

In Other BSDs for 2013/11/09

Not sure why, but there wasn’t a lot of things this week to pick out.

 

In Other BSDs for 2013/11/02

There’s a surprisingly large list this week.

In Other BSDs for 2013/10/26

Once again, doing this at the last minute:

In Other BSDs for 2013/10/19

I am doing this one at the last minute.  I had all the articles noted, but normally I build this post over the course of the week.