Re: Reboot:Relevance

"PUB @ Keystreams.net" <[email protected]> Tue, 10 Jan 2017 23:43:26 -0700
Newsgroups	gmane.org.user-groups.linux.calgary.general
Organization	Keystreams
Message-ID	<[email protected]>
At first glance I thought it had something to do with some wild swarm of unix sockets used for testing or perhaps even knocking servers offline, and I thought, whaaaa? - global domination by the unix socket swarm? peshaw! or is it actually real? hmmm, come to think of it, millions of machines all which each employ the unix socket concept - that's kind of a swarm? and then on I soared to the forming _clouds_ of "the new technology infrastructure". yay, and I went further then after...

yet at the bottom of the heap I saw from the corner of my eye the little linux kernel down below, doing its work. good kernel, I thought. buuuut, what about the HURD? is it ever going to come (in any real/usable form)?... and so on.

crazy world man.

-------

Next in line: actual swarms of bees return to the planet and gleefully pollinate everything in sight!

Fun :-)

On 01/10/2017 11:18 PM, Juan Alberto Cirez wrote:
> Yeah,
> I saw that on github. It's a pretty cool idea too :-)
>
> On Jan 10, 2017 11:16 PM, "PUB @ Keystreams.net" <[email protected]
> <mailto:[email protected]>> wrote:
>
>     "socket-swarm:
>
>     Create a swarm of socket.io <http://socket.io> clients to stress
>     test your socket-based application. Provides hooks to allow for HTTP
>     based authentication to be passed into the socket connection
>     requests if necessary, as well as listening to and responding to
>     various socket events."
>
>     It's also a cool phrase -- socket swaaaaaaarm!
>
>     On 01/10/2017 06:51 PM, PUB @ Keystreams.net wrote:
>     > That's one. Can we get a show of hands from the back?
>     >
>     > On 01/10/2017 06:36 PM, Sam Khangyi wrote:
>     > > Hail the New CLUG,
>     > >
>     > >
>     > >
>     > > On January 10, 2017 Tuesday 18:11:05 PUB @ Keystreams.net wrote:
>     > >
>     > >> to kill the name and abandon the original concept of a LUG
>     perhaps, to
>     > >
>     > >> embrace and expand and to reinvent is the question I'm getting from
>     > > this...
>     > >
>     > >>
>     > >
>     > >> Down With CLUG! All Hail the New CLUG, er, CLUG OF EXPANDED
>     DIMENSIONS -
>     > >
>     > >> meaning after that we are all CLUGed!
>     > >
>     > >>
>     > >
>     > >> for curiosity, can we see a show of hands of who is reading
>     this mailing
>     > >
>     > >> list - I think after all that it's the real glue?
>     > >
>     > >>
>     > >
>     > >> /me raises his hand
>     > >
>     > >>
>     > >
>     > >> one ping, one ping only...
>     > >
>     > >>
>     > >
>     > >> On 01/10/2017 05:35 PM, Juan Alberto Cirez wrote:
>     > >
>     > >>> Good evening fellow CLUG-philes,
>     > >
>     > >>> I have observed the posts for the past several years and my
>     take away is
>     > >
>     > >>> that we have lost a bit of relevance. By that I mean we tend
>     to post and
>     > >
>     > >>> discuss topics that are at best dated, and at worst irrelevant
>     to the
>     > >
>     > >>> idea of driving GNU/Linux forward.
>     > >
>     > >>> The world today is dominated by private/public clouds,
>     microservises,
>     > >
>     > >>> containers, virtualization, big data, machine learning, etc.
>     > >
>     > >>> Seriously, when was the last time these topics came up for
>     discussion?
>     > >
>     > >>> Knowing GNU/Linux is the nexus of all these technologies I
>     have been
>     > >
>     > >>> surprised they have been ignored. I mean, Openstack and other
>     > >
>     > >>> orquestration technologies. Docker and other container
>     technologies.
>     > >
>     > >>> Kubernetes, mesos,etc.
>     > >
>     > >>> Building a microcluster out of raspberry pi3s. Building a socket
>     > >
>     > >>> swarm...the sky is the limit.
>     > >
>     > >>> This is the golden age of GNU/Linux. We should be celebrating!!!
>     > >
>     > >>>
>     > >
>     > >>>
>     > >
>     > >>> _______________________________________________
>     > >
>     > >>> clug-talk mailing list
>     > >
>     > >>> [email protected] <mailto:[email protected]>
>     > >
>     > >>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>     <http://clug.ca/mailman/listinfo/clug-talk_clug.ca>
>     > >
>     > >>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php
>     <http://clug.ca/ml_guidelines.php>)
>     > >
>     > >>> **Please remove these lines when replying
>     > >
>     > >
>     > >
>     > >
>     > >
>     > > _______________________________________________
>     > > clug-talk mailing list
>     > > [email protected] <mailto:[email protected]>
>     > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>     <http://clug.ca/mailman/listinfo/clug-talk_clug.ca>
>     > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php
>     <http://clug.ca/ml_guidelines.php>)
>     > > **Please remove these lines when replying
>     > >
>     >
>     >
>
>
>
>     _______________________________________________
>     clug-talk mailing list
>     [email protected] <mailto:[email protected]>
>     http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>     <http://clug.ca/mailman/listinfo/clug-talk_clug.ca>
>     Mailing List Guidelines (http://clug.ca/ml_guidelines.php
>     <http://clug.ca/ml_guidelines.php>)
>     **Please remove these lines when replying
>
>
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
signature.asc (application/pgp-signature, 819 B)