As mentioned in an earlier email the DOMU or secondary Xen system(s) can
not only talk to the DOM0 or Xen primary system but also to other other
DOMU or secondary Xen system(s) and that most likely involves not only
LAN interaction but also Internet interaction.
Where internet interaction is involved one can set up an effective
firewall involving what might seem as a few lines (5 or 6) of trciky but
yet elegantly simple code assignments which I call route management code
which defines tunneling, gateways, and other associations. There is a
set of such code for DOM0, the primary Xen system and for each DOMU, the
secondary Xen systems. This code can involve simple or complex logic
where the logic is the assignment process. The more interactive these
DOMU or secondary systems become the more complex is the so called
logic. What seems the most difficult are so called bridges. They seem
difficult to understand because we have very little to do with them
once they have been set up or someone has helped us but not passed on
the theory. A bridge is just the logic that joins or associates
(causing to share) two or more network pathways to a common interface.
It would be nice to have some examples of this route management code
with an explanation of it's operation and theory for both simple and
complex scenarios, especially some Xen scenarios.
Any takers on this??????????????????????
I've got some old examples that I might be able to dig up. .I am saving
every scenario that occurs on the Debian list on anything associated
with Xen or Xen and associated technologies. I have thousands of email
from Xen developers taken from the Xen list up to about a year or more
ago. If I can I will try to drag up that email from another email
account that a year ago I abandoned because it regularly overflowed with
sexual harrassement and a multitude of viruses, trojans, worms, and new
pests with which the various anti virus vendors of that time were
overwhelmed during that same time period. Obviously, I am not using a
linux account but that will change when I do my Xen set up.
It would be interesting to see an example where the Windows OS is
treated as a DOMU secondary system virtual machine under a Debian DOM0
primary Xen system and was also required to not only to commuicate with
the Linux LAN network but also the Windows counterpart of XP,
NT2000, etc.
In the field of MATH, mathematicians work at theories and how to's
almost as a game. There are two benefits, first even though errors may
abound one's personal knowledge base increases as they debate and
uncover their errors. Secondly, many of these theories end up becoming
useful. We in computer hardware and software development need to be
like these mathematicians and dare to explore what we do not understand.
Fear is our worst enemy. Failure should just be treated as a step
forward in the learning curve. We should crave knowledge for the sake
of knowledge as the more we dare to understand the more competant we
become at all things.
I charge extra for these pep talks. If they get snipped then I will know
they are not appreciated. Often what we need in order to do something
different is the courage to face our fears and take those steps into
successs. For those of you that have a spare machine or space on a
machine I would encourage you to engage the Xen technology and then
share your problems and successes with the rest of us so we can build on
one anothers eventual success. Xen is the technology that allows us to
build our personal knowledge base by experimenting on DOMU Xen secondary
systems. To do this all we need is to engage this promise of knowledge
and success by installing Xen and getting help if we need help.
Thanks, Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
