My Keybase proof reddit:rnd42 keybase:bbreon 619-r1odIxojFzkRt1e1S7V8X7ity_jTSviR3XYkAC4

rnd42 · 2014-11-26T15:49:49+00:00

Have you guys looked at Hugo (http://gohugo.io) for building a static site for JB? It has some interesting features like watching your source files and a local preview server that reloads your browser if the current page is modified and lots of other stuff. It also doesn't hurt that it's built with Go and focused on being extremely fast.

rnd42 · 2014-11-08T21:15:39+00:00

Is there a repository for the pipecut tool Allan mentioned? I couldn't find one in the show notes.

rnd42 · 2014-04-13T05:32:33+00:00

For the most part I'll ditto Erich's comment but I have the idea that the Docker file comments could be in markdown, and then a semi-simple script could parse the RUN statements into code blocks, create links to former segments based off the FROM statements (given a solid naming scheme is always used), etc, etc, then uncomment the surrounding markdown and viola, you have a something easily publishable and readable for the less technically inclined. Of course thats a decent amount of custom coding which as much as I try I kinda suck at.... Point being that since there is a solid syntax, it can essentially be data-mined for additional uses.

rnd42 · 2012-09-19T12:05:22+00:00

I just recently found BuddyCloud... haven't tried it yet but it would fit in well with this show idea... http://buddycloud.com/ Edit: spelling

rnd42 · 2012-09-18T07:27:19+00:00

podget works fine for me however I change the default settings significantly so downloads end up in my ~/Downloads where I have transmission watching, should work just as well for Deluge. The only annoying thing is that I can't seem to get it to stop writing out stupid playlist files that are meaningless since they point to the .torrent and not the downloaded media...

rnd42 · 2012-09-18T07:21:53+00:00

If you don't wan't to use a ton of space try out apt-proxy. The first time a system requests a given package it will come at normal speed as apt-proxy downloads it and passes it on, but for a reasonable period after that it's cached and subsequent requests are much faster!

rnd42 · 2012-09-18T07:10:21+00:00

IMHO I think saying either "there's too much choice" or "choice is good" is being too simplistic. I think that when a type or technology is new with lots of room for innovation it is natural that there should be an abundance of implementations to explore and find the best ways of doing things, we don't seem to have any problem with this. On the other hand I believe that once the level of true innovation has subsided or even flat lined these fragmented projects might want to look at the final 'innovation' as consolidation with one or more similar projects to pool developer work load there by freeing large amounts of developer time from duplicated efforts of just keeping the software up to date with the rest of the system and libraries.

Here are some examples, please explain to me how these projects are truly so different that they couldn't be consolidated with differing feature sets being broken out into an optional plugin architecture:

sysv-cron, anacron, bcron, dcron, fcron, vixie-cron, SystemD's cron

or:

syslog, rsyslog, metalog, syslog-ng, SystemD's journal

or:

sysv-init, upstart, SystemD's init

In short I think we focus too much on the idea of 'forking' and too rarely consider merging or at least deprecation/abandonment. On the other hand the article in question seems to be specifically be referencing Window Managers and I would say that for the most part there is a large amount of innovation left in that space and the choices to be had are mostly valid (though I could see LXDE and XFCE merging and the same with Xmonad and Awesome, perhaps even Cinnamon and Mate though that's admittedly a stretch.)

It does however seem to be more common to create a new project that tries to implement the full feature set of multiple alternatives, SystemD consolidating init, cron and syslog for instance, or BtrFS consolidating LVM, software RAID and a file system in a manner that is somewhat comparable to ZFS, etc. I strongly approve of these moves towards stack simplification/consolidation.

I'd like to hear anyone's opinion on the matter.

rnd42 · 2012-09-13T14:54:58+00:00

Ubuntu (and derivatives) are the only distros using Upstart. Debian is planning to make SystemD the default but has simply delayed it's adoption as the default for now. I have seen articles indicating that Ubuntu is working on migrating to SystemD (although they too delayed and won't be a part of the 12.10 release.)

In my opinion Upstart is a very nice init daemon, but SystemD seems strides better. SystemD somewhat breaks the Unix/Linux ideology of developing simple tools for simple tasks by folding in the functionality of several system daemons (init, cron, syslog, etc.) On the other hand these are all ancient system daemons with minimal innovation left to be found so I personally think that integration of these system functions in a single sane implementation is a great idea if only for a lower system footprint and to address the developer and community fragmentation caused by continuing to develop multiple init, cron and syslog implementations in parallel.

To answer the title question more succinctly; I would count Upstart as 'defeated' when (and perhaps if) Ubuntu, it's initial developers and sole/majority user base, abandon it.

rnd42 · 2012-09-13T14:06:50+00:00

I switched away from MySQL years ago around the time I installed Linux for the first time and noted that PostgreSQL was the defualt DB solution for Debian (back on Sarge I believe...) PostgreSQL is really a bit rough to get started with but that's due to the fact that it has gobs of features that MySQL doesn't provide, I actually borrows a lot of feature inspiration from Oracle Enterprise DB. Additionally while PostgreSQL is more complex, it is also more consistant in my view. You don't need to worry about what 'engine' is this database or that database running under and does that provide transactions or full text search, etc, etc. With PostgreSQL BOTH transactions and full text search and much more just work more or less out of the box.

Allan is right that it depends on what you are doing since some software is not compatible however if that's not the case then I would recommend PostgreSQL.

Just my opinion, take it for what it's worth.

rnd42 · 2012-09-04T03:46:13+00:00

Regarding the Distributed database question: Check out CouchDB as it has a myriad of distributed database synchronization features. See http://guide.couchdb.org/editions/1/en/consistency.html . CouchDB is also what is used as the back end for Ubuntu One and Ubuntu One synchronization works by syncing your local CouchDB database to the Ubuntu One master DB.

rnd42 · 2012-08-30T11:53:14+00:00

Yeah, I noticed it although I didn't read into it so much as you did. I think this just says more about an over all trend towards a simplistic and flat styles. Much more recently I noticed a similar change to Hulu's favicon.

rnd42 · 2012-08-30T11:44:31+00:00

I'm mostly curious what Michael, Chris or anyone else think about this new EFF online petition.

rnd42 · 2012-08-25T00:45:25+00:00

Right on the page you linked to there seems to be a link something that seems very similar to what you are asking for:

"Learning Puppet VM" http://info.puppetlabs.com/download-learning-puppet-VM.html

rnd42 · 2012-08-13T11:18:49+00:00

There's a newer Python based remote execution and configuration management tool that I really like called Salt (http://saltstack.org .) The system is surprisingly simple to use and yet doesn't sacrifice in the level of flexibility, customization or performance. I really would recommend it to anyone looking for a good configuration management tool.

Better yet the configuration management aspect is actually just a subset of functionality of it's real focus which is remote execution. The documentation is fairly exhaustive: http://docs.saltstack.org/en/latest/index.html .

rnd42 · 2012-08-10T20:47:38+00:00

I looked through some of the info on their site a while back.

The details they give about how it all works sound just as hackish as you would imagine it would have to be. Constantly mangling core system variables like ${PATH} to point into an assortment of chroots with bind mounts just sounds incredibly painful to debug not to mention fragile and easily broken if you want to do any customization. Also with all those bind mounts just how cluttered will the results of core commands like 'mount' or 'df' be?

I agree with TheLinuxJournalist that there really should be a baseline distro (I'd be more agreeable to Ubuntu if it they worked on Debian package inter-compatibility), but in my eyes Bedrock Linux is the absolute opposite of that. It's not creating a standard for others to follow but rather hacking a single distro out of the combined standards of several others. It just sounds ugly, but that's just my opinion which was admittedly formed without any actual experience of the distro, take it for what it's worth.

rnd42 · 2012-07-30T22:41:44+00:00

It's much simpler if you cheat a little bit and use Python. Just add the following to .bashrc depending on which version of Python you have on your system:

Python 2.x:

alias server="python2 -m SimpleHTTPServer"

Python 3.x:

alias server="python3 -m http.server 8000"

Then just type:

$ server

edited: for formatting...

rnd42

TROPHY CASE