18 Jun
2017
18 Jun
'17
9:45 p.m.
deloptes:
Proof of concept is exactly what I am going to do this fall. Right now I
am mostly interested in how containers work and what they can do--later
this fall I will get into how to use them.
Re: resources
What you say might be true, but most people don't seem to use most of their
resources, me included. So I want to test if containers, especially
several different ones running at the same time, do bad things to
usability--under normal working conditions--and if so, why and what can be
done about it.
Keith
On Sun, Jun 18, 2017 at 1:54 PM, deloptes <deloptes(a)gmail.com> wrote:
Keith Daniels wrote:
When you use containers, you no longer
need to create individual versions or packages of TDE for every Distro.
I was thinking of this few days ago, but in different context.
As PICCORO McKAY Lenz stated a container is waste of resources, however
what
you use is your own decision, so perhaps you could setup a build env and
try to produce the packages for devuan or what you think might be useful
and go for it as proof of concept.
I personally use chroot for building packages and vmware to test and I
think
it is sufficient. Containers are cool, but I don't see advantage in
maintaining such overhead. I can of course speak only for myself. At the
end I want to have TDE native and not in some kind of virtual env.
regards
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@
lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.
pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.
pearsoncomputing.net/
Please remember not to top-post: http://trinity.
pearsoncomputing.net/mailing_lists/#top-posting