Comments for DragonFly BSD Digest

Comment on DragonFly and Bittorrent by Justin Sherrill

Justin Sherrill — Wed, 22 May 2013 00:38:05 +0000

Tim – Nobody’s ever done it? At least not consistently; we’ve had some releases from time to time where someone sets it up, but that’s it. If/when I’m dealing with the next release, I’ll try to include that too.

Comment on DragonFly and Bittorrent by Tim Darby

Tim Darby — Tue, 21 May 2013 18:10:16 +0000

Justin, out of curiosity, why doesn’t the project have its own tracker and/or offer torrents as a standard release distribution option? I’d much prefer to get them that way.

Comment on BSD Hardware ideas by nwildner

nwildner — Tue, 21 May 2013 17:51:49 +0000

That’s a hell good initiative. And it will help other people avoid the same stupidity that i made: Buy a broadcom wireless card :P

Comment on tpm(4) module added by Lazarus

Lazarus — Thu, 16 May 2013 03:26:05 +0000

Matthew Garrett recently posted an introduction to the trusted platform module and what can be done with it.

http://mjg59.dreamwidth.org/24818.html

Comment on No Lazy Reading by Joey

Joey — Tue, 14 May 2013 13:57:30 +0000

Can’t blame you on the weather excuse (reasoning?), because the weather has been Legend….wait for it….dary! Ok, maybe not so much Legendary, but it indeed has been pretty nice especially here in the Los Angles area.

Comment on Many upgrades, and Hammer by John

John — Sat, 11 May 2013 06:55:47 +0000

“can’t find awk changelog”.

It was in the commit message itself. This would have been a better link:
http://leaf.dragonflybsd.org/mailarchive/commits/2013-05/msg00054.html

Comment on Usage for dports and pkgsrc by Anonymous

Anonymous — Fri, 10 May 2013 08:24:12 +0000

It’s just that nobody loves pkgsrc. It has always been an alien on DragonFly.

Comment on How about Ansible? by rektide

rektide — Wed, 08 May 2013 15:12:03 +0000

I haven’t had any problems operating on diverse sets of hardware at all.

Ansible uses ohai and facter to get a list of system facts specific to each host and supplements it with some of it’s own information- I’ve used those facts to do things like tailor my playbooks to install either from deb, from rpm or from source and to add additional configuration stanzas to the service being installed depending on any given host’s ansible_os_family, for instance. This is flexibility that allows a single playbook to operate regardless of what hardware it sees.

As for managing complex hardware, Ansible has a very robust inventory management system: hosts are placed into groups, and groups are allowed to define or override existing variables within the scope of the group. Playbooks can be aggregated by other playbooks, and when this happens each playbook only runs for the groups it has been directed to run on- in this way, you can run a playbook which will do a whole bunch of different configuration tasks in one swoop for all the various node-types you might have in a cluster- some are Zookeeper, some are Nginx, some are application servers, with there being no difficulty with half the Zookeeper nodes being one OS and the other half being a different OS.

Ansible is a DSL for JSON powered SSH. I love it, couldn’t be happier, at least since set_fact has been introduced, permitting some sane JSON modification while that DSL runs. http://ansible.cc/docs/modules.html#set-fact

Comment on How about Ansible? by Michel Alexandre S.

Michel Alexandre S. — Wed, 08 May 2013 08:38:21 +0000

Pretty much what Dean said, though when I have spare time I plan to tackle using Ansible’s support for shared tasks and variables to manage both our SuSE and CentOS servers from the same playbooks.

That being said, having almost no client-side footprint is absolutely brilliant.

Comment on How about Ansible? by Dean

Dean — Wed, 08 May 2013 03:29:33 +0000

Its nice if you have a *very* homogeneous infrastructure. So like all Xen VPS’s or something, if you have varying hardware in the same ‘cluster’ it starts to become hairy. If you want to manage the WHOLE machines configuration, you will spend a lot of time writing bootstrap playbooks.

Its also very handy if you want to run commands on a lot of machines but using cluster-ssh or something is just a little too raw.

Comment on DragonFly and Bittorrent by Emil Mikulic

Emil Mikulic — Sun, 05 May 2013 12:16:52 +0000

Please keep distributing compressed images. As someone who lives in a third-world country with very expensive and limited bandwidth (Australia) I’m grateful to the DragonflyBSD project for compressed ISOs. I wish all systems did this.

Comment on DragonFly and Bittorrent by Justin Sherrill

Justin Sherrill — Sun, 05 May 2013 05:23:14 +0000

I see what you mean with collections and releases – I added the release number to the title. However, I don’t see how you can create a collection.

If the files are corrupted after compression, well, that’s how they are distributed everywhere else. Taking the compression off would make them take longer to download, which is the whole thing that bittorrenting is to solve. I don’t see an actual benefit to torrenting the uncompressed versions of the files.

Comment on DragonFly and Bittorrent by vorbote

vorbote — Sat, 04 May 2013 18:35:59 +0000

Change that duplicate bittorrent for “bittorrent expecification”

Comment on DragonFly and Bittorrent by vorbote

vorbote — Sat, 04 May 2013 18:35:01 +0000

A few observations:

1. The files belong to a release under the Dragonfly BSD collection. See the FlightGear releases as an example.

2. There is no real need to compress the files. The bittorrent bittorrent uses fixed-block checksumming therefore you are hiding whatever file corruption the compressor could have introduced to the original files on the one hand and you are adding a second level of usability indirection on the other.

Comment on DragonFly 3.4 release very soon by Justin Sherrill

Justin Sherrill — Tue, 30 Apr 2013 19:42:53 +0000

Thank you for testing. I put what I did into a script so (assuming I remember to run it), we’ll have correct sums for susequent releases, too.

Comment on DragonFly 3.4 release very soon by Mehmet Erol Sanliturk

Mehmet Erol Sanliturk — Tue, 30 Apr 2013 06:25:39 +0000

I have downloaded :

ftp://mirrors.nycbug.org/pub/DragonflyBSD/iso-images/dfly-x86_64-3.4.1_REL.iso.bz2
ftp://mirrors.nycbug.org/pub/DragonflyBSD/iso-images/dfly-x86_64-gui-3.4.1_REL.iso.bz2

I have extracted them with Ark .

I have computed MD5 hashes of them with K3B .

I have copied their hashes into clipboard .
I have searched them in the following pages ( one by one ) :

ftp://mirrors.nycbug.org/pub/DragonflyBSD/iso-images/md5.txt
http://www.dragonflybsd.org/release34/

They matched exactly : They are correctly computed and listed in the above pages .

Thank you very much .

Mehmet Erol Sanliturk

Comment on DragonFly 3.4 release very soon by Justin

Justin — Mon, 29 Apr 2013 14:08:52 +0000

Mehmet – I set up a script to put in the MD5 for both the compressed and uncompressed images. Can you test and see if it works for you?

Comment on Lazy Reading for 2013/04/28 by Eric Radman

Eric Radman — Mon, 29 Apr 2013 13:18:45 +0000

While IPv6 address space has a lot of bits, the way they're carved out makes most of it unusuable, and can barely connect all the devices in the world today. Why IPv6 Address Space is Too Small (link is to a Google PPT viewer)

Comment on Lazy Reading for 2013/04/28 by Justin Sherrill

Justin Sherrill — Sun, 28 Apr 2013 19:49:49 +0000

That ‘everything in Git’ link was to a place offering to host zone files via Git – but it’s been closed down.

Comment on Lazy Reading for 2013/04/28 by bla

bla — Sun, 28 Apr 2013 17:35:02 +0000

“Everything’s being put into a git repo these days”: http://uberdns.eu/information gives me a 404 notification.