[Noisebridge-discuss] noisebridge-discuss: mailing list versus forum system
jim at systemateka.com
Thu Jan 27 18:54:16 UTC 2011
For me, "locally hosted" does not necessarily mean
box in the space, rather box that we, noisebridge people,
can get at, physically if necessary. There's something
hackerly about access to the silicon and metal itself,
though probably ineffable.
It also means as much freedom from shifts in some
other entity's policies as possible, which is the big
deal for me.
A possibly useful comparison is between renting a
VM on a monthly basis from go grid on one hand and
maintaining a box in a monkey brains rack at 200 Paul.
both are subject to policies, but we get to visit our
box and pet it and such, unlike the vm. granted the vm
is more scaleable and reliable, but those don't seem
important aspects to hackers. and we can move the box
to another entity, which is different from moving the
vm to another hosting entity.
On Thu, 2011-01-27 at 10:35 -0800, Dr. Jesus wrote:
> On Wed, Jan 26, 2011 at 9:41 PM, aestetix aestetix <aestetix at gmail.com> wrote:
> > I'd really not rather use something that's not locally hosted. What if their
> > system had a malfunction and we couldn't get access to troubleshoot it?
> You use the out of band management card. Most people aren't aware of
> how much control RMCP and similar protocols give the ops folks these
> days. Look at the feature set for Intel AMT 6, for example. You can
> reflash the BIOS over the network without even turning the computer on
> now. ASF 2.0 lets you turn computers on and lock out the local
> console, too.
> > Also, global politics aside, I don't like someone who is not a Noisebridger
> > having the "god key" to enable or disable the entire system.
> > Further, regardless of the complexity, if we have something local, we can
> > modify it, and even create new modules and patches for it.
> Why does the physical proximity to the machine have anything to do
> with the hackability of its software? Root is root.
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
More information about the Noisebridge-discuss