All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: xen-devel@lists.sourceforge.net
Subject: [PATCH] Add checks for iptables and iproute2 (Was Re: Coral with Xen)
Date: Sun, 09 Jan 2005 17:10:24 -0600	[thread overview]
Message-ID: <41E1B9E0.40008@codemonkey.ws> (raw)
In-Reply-To: <3b793f1a05010913532e834754@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

The following two scripts add checks for iptables and iproute2 during 
install.

Not all distributions include these by default.  I know this was a 
source of problems (with Gentoo) for me as the network scripts used by 
Xend silently fail if these commands aren't available.

It could be that Coral does not include one of these two packages by 
default.

Regards,
Anthony Liguori

Kero-Chan wrote:

>Hi!
>
>Coral isn't working from Xen. If you can please try it, maybe i'm just
>doing something wrong. However it works from outside Xen with the same
>setup.
>Can Xen cause this kind of DNS errors? 
>
>Try something like: http://www.scs.cs.nyu.edu.nyud.net:8090/coral/
>or http://www.google.com.nyud.net:8090/
>
>  
>


[-- Attachment #2: check_iproute2 --]
[-- Type: text/plain, Size: 114 bytes --]

#!/bin/bash
# CHECK-INSTALL

function error {
   echo 'Check for iproute2 failed.'
   exit 1
}

which ip || error

[-- Attachment #3: check_iptables --]
[-- Type: text/plain, Size: 124 bytes --]

#!/bin/bash
# CHECK-INSTALL

function error {
   echo 'Check for the iptables failed.'
   exit 1
}

which iptables || error

  reply	other threads:[~2005-01-09 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 21:53 Coral with Xen Kero-Chan
2005-01-09 23:10 ` Anthony Liguori [this message]
2005-01-10 18:24   ` [PATCH] Add checks for iptables and iproute2 Jan Kundrát

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41E1B9E0.40008@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.