Talk:1764: XKCDE - Revision history

108.162.221.117 at 13:31, 29 November 2016

2016-11-29T13:31:49Z

108.162.221.117 at 13:30, 29 November 2016

2016-11-29T13:30:39Z

108.162.221.117 at 13:29, 29 November 2016

2016-11-29T13:29:12Z

108.162.221.117 at 13:27, 29 November 2016

2016-11-29T13:27:10Z

141.101.98.219 at 18:12, 28 November 2016

2016-11-28T18:12:18Z

108.162.241.53: A better reason why some seeds spin when falling

2016-11-28T13:14:50Z

A better reason why some seeds spin when falling

Davidhbrown at 19:12, 27 November 2016

2016-11-27T19:12:24Z

Davidhbrown: containers=>software containers as in Docker?

2016-11-27T19:11:08Z

containers=>software containers as in Docker?

162.158.59.173 at 04:27, 27 November 2016

2016-11-27T04:27:58Z

SabreWolfy at 09:44, 26 November 2016

2016-11-26T09:44:17Z

@@ Line 27: / Line 27: @@
 I wrote this a while back which nests KVM indefinitely -- or at least in theory, in practice I can only get to L4 on hardware I have available.  http://git.annexia.org/?p=supernested.git;a=summary [[Special:Contributions/141.101.98.219|141.101.98.219]] 18:12, 28 November 2016 (UTC)
 A slightly simpler, but more error prone script.
   #!/bin/bash

@@ Line 37: / Line 37: @@
   ProcessorCnt=$(grep '^processor' /proc/cpuinfo | wc -l)
-  if [[ "$VM_Mem" -ge "$MemUsed"  ]] ; then
+  if <nowiki>[[ "$VM_Mem" -ge "$MemUsed"  ]]</nowiki> ; then
     echo "-------------Still have ${MemAvail}M and only using ${MemUsed}M. Spinning up another!-------------"
     qemu-system-x86_64 --enable-kvm -cpu host -smp $ProcessorCnt -m $VM_Mem -drive $VM_Drive

@@ Line 28: / Line 28: @@
 I wrote this a while back which nests KVM indefinitely -- or at least in theory, in practice I can only get to L4 on hardware I have available.  http://git.annexia.org/?p=supernested.git;a=summary [[Special:Contributions/141.101.98.219|141.101.98.219]] 18:12, 28 November 2016 (UTC)
 A slightly simpler, but more error prone script.
-#!/bin/bash
+ #!/bin/bash
-# If you hate yourself, (DO NOT DO THIS) set file=/dev/sda and add this script to init. Expect corruption.
+ # If you hate yourself, (DO NOT DO THIS) set file=/dev/sda and add this script to init. Expect corruption.
-# Untested, though I came close to running it on accident.
+ # Untested, though I came close to running it on accident.
-VM_Drive='format=raw,file=__Enter_A_Modified_Run_From_Ram_Img__,if=virtio'
+ VM_Drive='format=raw,file=__Enter_A_Modified_Run_From_Ram_Img__,if=virtio'
-MemAvail=$(free -m | grep '^Mem:' | awk '{print $7}')
+ MemAvail=$(free -m | grep '^Mem:' | awk '{print $7}')
-MemUsed=$(free -m | grep '^Mem:' | awk '{print $3}')
+ MemUsed=$(free -m | grep '^Mem:' | awk '{print $3}')
-VM_Mem=$(echo "$MemAvail - 10" | bc -l)
+ VM_Mem=$(echo "$MemAvail - 10" | bc -l)
-ProcessorCnt=$(grep '^processor' /proc/cpuinfo | wc -l)
+ ProcessorCnt=$(grep '^processor' /proc/cpuinfo | wc -l)
-−
-if [[ "$VM_Mem" -ge "$MemUsed"  ]] ; then
+ if [[ "$VM_Mem" -ge "$MemUsed"  ]] ; then
-    echo "-------------Still have ${MemAvail}M and only using ${MemUsed}M. Spinning up another!-------------"
+   echo "-------------Still have ${MemAvail}M and only using ${MemUsed}M. Spinning up another!-------------"
-    qemu-system-x86_64 --enable-kvm -cpu host -smp $ProcessorCnt -m $VM_Mem -drive $VM_Drive
+   qemu-system-x86_64 --enable-kvm -cpu host -smp $ProcessorCnt -m $VM_Mem -drive $VM_Drive
-else
+ else
-    echo "!!!!!!!!!!!!!Only have ${MemAvail}M and using ${MemUsed}M.  Not spinning up any more!!!!!!!!!!!!!!"
+   echo "!!!!!!!!!!!!!Only have ${MemAvail}M and using ${MemUsed}M.  Not spinning up any more!!!!!!!!!!!!!!"
-fi
+ fi
 [[Special:Contributions/108.162.221.117|108.162.221.117]] 13:27, 29 November 2016 (UTC)

← Older revision		Revision as of 13:27, 29 November 2016
Line 27:		Line 27:

	I wrote this a while back which nests KVM indefinitely -- or at least in theory, in practice I can only get to L4 on hardware I have available. http://git.annexia.org/?p=supernested.git;a=summary [[Special:Contributions/141.101.98.219\|141.101.98.219]] 18:12, 28 November 2016 (UTC)		I wrote this a while back which nests KVM indefinitely -- or at least in theory, in practice I can only get to L4 on hardware I have available. http://git.annexia.org/?p=supernested.git;a=summary [[Special:Contributions/141.101.98.219\|141.101.98.219]] 18:12, 28 November 2016 (UTC)
		+	A slightly simpler, but more error prone script.
		+	#!/bin/bash
		+	# If you hate yourself, (DO NOT DO THIS) set file=/dev/sda and add this script to init. Expect corruption.
		+	# Untested, though I came close to running it on accident.
		+	VM_Drive='format=raw,file=__Enter_A_Modified_Run_From_Ram_Img__,if=virtio'
		+	MemAvail=$(free -m \| grep '^Mem:' \| awk '{print $7}')
		+	MemUsed=$(free -m \| grep '^Mem:' \| awk '{print $3}')
		+	VM_Mem=$(echo "$MemAvail - 10" \| bc -l)
		+	ProcessorCnt=$(grep '^processor' /proc/cpuinfo \| wc -l)
		+
		+	if [[ "$VM_Mem" -ge "$MemUsed" ]] ; then
		+	echo "-------------Still have ${MemAvail}M and only using ${MemUsed}M. Spinning up another!-------------"
		+	qemu-system-x86_64 --enable-kvm -cpu host -smp $ProcessorCnt -m $VM_Mem -drive $VM_Drive
		+	else
		+	echo "!!!!!!!!!!!!!Only have ${MemAvail}M and using ${MemUsed}M. Not spinning up any more!!!!!!!!!!!!!!"
		+	fi
		+	[[Special:Contributions/108.162.221.117\|108.162.221.117]] 13:27, 29 November 2016 (UTC)

← Older revision		Revision as of 18:12, 28 November 2016
Line 25:		Line 25:

	Protecting seeds, especially light ones that autorotate, from fall damage seems pretty far-fetched. The autorotation of seeds more likely serves to increase the time they take to fall, thus increasing the distance they travel in the wind. [[Special:Contributions/108.162.241.53\|108.162.241.53]] 13:14, 28 November 2016 (UTC)		Protecting seeds, especially light ones that autorotate, from fall damage seems pretty far-fetched. The autorotation of seeds more likely serves to increase the time they take to fall, thus increasing the distance they travel in the wind. [[Special:Contributions/108.162.241.53\|108.162.241.53]] 13:14, 28 November 2016 (UTC)
		+
		+	I wrote this a while back which nests KVM indefinitely -- or at least in theory, in practice I can only get to L4 on hardware I have available. http://git.annexia.org/?p=supernested.git;a=summary [[Special:Contributions/141.101.98.219\|141.101.98.219]] 18:12, 28 November 2016 (UTC)

← Older revision		Revision as of 13:14, 28 November 2016
Line 23:		Line 23:

	The current explanation doesn't clarify "containers;" I expect Randall is thinking of [https://en.wikipedia.org/wiki/Operating-system-level_virtualization a software container] which allows you to deploy a service such as a database engine in isolation from other services using a minimum of resources. This comic makes me think of my experience trying to use [https://en.wikipedia.org/wiki/Docker_(software) Docker] on Windows. Docker is among the most popular software container systems, but is tightly bound to Linux, so deploying a Docker container under Windows (or Mac OS X) requires that you first deploy a virtual machine, thus negating some of the benefit of using containers and pushing the software running in the container down yet another level. [[User:Davidhbrown\|Davidhbrown]] ([[User talk:Davidhbrown\|talk]]) 19:11, 27 November 2016 (UTC)		The current explanation doesn't clarify "containers;" I expect Randall is thinking of [https://en.wikipedia.org/wiki/Operating-system-level_virtualization a software container] which allows you to deploy a service such as a database engine in isolation from other services using a minimum of resources. This comic makes me think of my experience trying to use [https://en.wikipedia.org/wiki/Docker_(software) Docker] on Windows. Docker is among the most popular software container systems, but is tightly bound to Linux, so deploying a Docker container under Windows (or Mac OS X) requires that you first deploy a virtual machine, thus negating some of the benefit of using containers and pushing the software running in the container down yet another level. [[User:Davidhbrown\|Davidhbrown]] ([[User talk:Davidhbrown\|talk]]) 19:11, 27 November 2016 (UTC)
		+
		+	Protecting seeds, especially light ones that autorotate, from fall damage seems pretty far-fetched. The autorotation of seeds more likely serves to increase the time they take to fall, thus increasing the distance they travel in the wind. [[Special:Contributions/108.162.241.53\|108.162.241.53]] 13:14, 28 November 2016 (UTC)

← Older revision		Revision as of 19:12, 27 November 2016
Line 22:		Line 22:
	we need to go deeper[[Special:Contributions/162.158.59.173\|162.158.59.173]] 04:27, 27 November 2016 (UTC)Guest User that doesn't know what they're doing		we need to go deeper[[Special:Contributions/162.158.59.173\|162.158.59.173]] 04:27, 27 November 2016 (UTC)Guest User that doesn't know what they're doing

−	The current explanation doesn't clarify "containers;" I expect Randall is thinking of [https://en.wikipedia.org/wiki/Operating-system-level_virtualization a software container] which allows you to deploy a service such as a database engine in isolation from other services using a minimum of resources. This comic makes me think of my experience trying to use [https://en.wikipedia.org/wiki/Docker_(software) Docker] on Windows. Docker is among the most popular software container systems, but is tightly bound to Linux, so deploying a Docker container under Windows (or Mac OS X) requires that you first deploy a virtual machine, thus negating ~~much~~ of the benefit of using containers ~~in the first place~~ and pushing the software running in the container down yet another level. [[User:Davidhbrown\|Davidhbrown]] ([[User talk:Davidhbrown\|talk]]) 19:11, 27 November 2016 (UTC)	+	The current explanation doesn't clarify "containers;" I expect Randall is thinking of [https://en.wikipedia.org/wiki/Operating-system-level_virtualization a software container] which allows you to deploy a service such as a database engine in isolation from other services using a minimum of resources. This comic makes me think of my experience trying to use [https://en.wikipedia.org/wiki/Docker_(software) Docker] on Windows. Docker is among the most popular software container systems, but is tightly bound to Linux, so deploying a Docker container under Windows (or Mac OS X) requires that you first deploy a virtual machine, thus negating some of the benefit of using containers and pushing the software running in the container down yet another level. [[User:Davidhbrown\|Davidhbrown]] ([[User talk:Davidhbrown\|talk]]) 19:11, 27 November 2016 (UTC)

← Older revision		Revision as of 19:11, 27 November 2016
Line 21:		Line 21:

	we need to go deeper[[Special:Contributions/162.158.59.173\|162.158.59.173]] 04:27, 27 November 2016 (UTC)Guest User that doesn't know what they're doing		we need to go deeper[[Special:Contributions/162.158.59.173\|162.158.59.173]] 04:27, 27 November 2016 (UTC)Guest User that doesn't know what they're doing
		+
		+	The current explanation doesn't clarify "containers;" I expect Randall is thinking of [https://en.wikipedia.org/wiki/Operating-system-level_virtualization a software container] which allows you to deploy a service such as a database engine in isolation from other services using a minimum of resources. This comic makes me think of my experience trying to use [https://en.wikipedia.org/wiki/Docker_(software) Docker] on Windows. Docker is among the most popular software container systems, but is tightly bound to Linux, so deploying a Docker container under Windows (or Mac OS X) requires that you first deploy a virtual machine, thus negating much of the benefit of using containers in the first place and pushing the software running in the container down yet another level. [[User:Davidhbrown\|Davidhbrown]] ([[User talk:Davidhbrown\|talk]]) 19:11, 27 November 2016 (UTC)

← Older revision		Revision as of 04:27, 27 November 2016
Line 19:		Line 19:

	I wonder how many xkcd comics contain lowercase letters (like 's' in "VMs")... --[[Special:Contributions/172.68.54.123\|172.68.54.123]] 19:36, 25 November 2016 (UTC)		I wonder how many xkcd comics contain lowercase letters (like 's' in "VMs")... --[[Special:Contributions/172.68.54.123\|172.68.54.123]] 19:36, 25 November 2016 (UTC)
		+
		+	we need to go deeper[[Special:Contributions/162.158.59.173\|162.158.59.173]] 04:27, 27 November 2016 (UTC)Guest User that doesn't know what they're doing

← Older revision		Revision as of 09:44, 26 November 2016
Line 7:		Line 7:

	Possible pun on existing desktop environments: KDE, CDE, LXDE, XFCE,... -> XKCDE (relies on conics using only upper-case letters). --[[User:JakubNarebski\|JakubNarebski]] ([[User talk:JakubNarebski\|talk]]) 10:51, 25 November 2016 (UTC)		Possible pun on existing desktop environments: KDE, CDE, LXDE, XFCE,... -> XKCDE (relies on conics using only upper-case letters). --[[User:JakubNarebski\|JakubNarebski]] ([[User talk:JakubNarebski\|talk]]) 10:51, 25 November 2016 (UTC)
		+
		+	^ This is a more plausible explanation ([CDE: Common Desktop Environment: https://en.wikipedia.org/wiki/Common_Desktop_Environment) than "Collaborative Development Environment) mentioned in the explanation above. [[User:SabreWolfy\|SabreWolfy]] ([[User talk:SabreWolfy\|talk]]) 09:44, 26 November 2016 (UTC)

	The title text is a take on poetry. It extends from the abstract tree (which is a digram and a datastructure type) to an actual tree with unpluggable roots and leafs which scatter in the wind and finally land spinning. Sebastian --[[Special:Contributions/162.158.91.97\|162.158.91.97]] 11:00, 25 November 2016 (UTC)		The title text is a take on poetry. It extends from the abstract tree (which is a digram and a datastructure type) to an actual tree with unpluggable roots and leafs which scatter in the wind and finally land spinning. Sebastian --[[Special:Contributions/162.158.91.97\|162.158.91.97]] 11:00, 25 November 2016 (UTC)