3,510 karma · joined August 4, 2012
I find Docker to be horribly counter-intuitive and ass-backwards anyway, so not much harm done there as people are in general better off with something else entirely (plain lxc, libvirt, virtualbox, xen, openvz...). I recommend to steer away from it at least until 1.0 is out.
EDIT: I put it in my .plan to build a better BusyBox image aimed at running statically compiled programs with minimal baggage, but I'm not sure when I'll get a round tuit*
*: http://i.ebayimg.com/00/s/NDgwWDY0MA==/z/z-4AAOxyUrZSr82N/$_...
watch: execute something on a schedule *in realtime*
printf: change the format of output
apropos: info on commands
dd: disk writing
ss: socket statistics (show apps *using the Internet*)
Almost but not quite.It merely does legacy IP, so what's the point?
And the results are in: http://i.imgur.com/6KMvhIa.png
(It appears that this comment itself is only good enough when I include this sentence.)
https://en.wikipedia.org/wiki/Edward_Snowden#Temporary_asylu...
cups was stopped, but it can still be activated by:
- cups.sprocket
- cups.latch
What are these things and why are they there at all? How do I shut them off? It doesn't tell, so stopping a service has become pointless. If I tell it to stop, make it stop!Also, you need more protocol relative URIs to fix the project pages.
(inspect element... untick position: fixed... done)
I love the irony in this flawed line of thinking here.