All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel@lists.xensource.com
Cc: Josh Nicholas <jnicholas@virtualiron.com>
Subject: [PATCH] Allow blktap specification to be a path to a file
Date: Mon, 27 Aug 2007 15:05:22 -0400	[thread overview]
Message-ID: <46D32072.5040609@virtualiron.com> (raw)

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

Minor change to allow a blktap specification to be an actual 
path to a file instead of a soft link to a file

Signed-off-by: Ben Guthro <bguthro@virtualiron.com>
Signed-off-by: Josh Nicholas <jnicholas@virtualiron.com>


[-- Attachment #2: xen-hotplug-blktap.patch --]
[-- Type: text/x-patch, Size: 473 bytes --]

diff -r b34eb51bc04c tools/examples/blktap
--- a/tools/examples/blktap	Thu Aug 16 19:37:12 2007 -0400
+++ b/tools/examples/blktap	Thu Aug 16 19:37:12 2007 -0400
@@ -18,7 +18,12 @@ then
         p=${p#*:}
     fi
 fi
-file=$(readlink -f "$p") || ebusy "$p does not exist."
+if [ -L "$p" ]; then
+    file=$(readlink -f "$p") || ebusy "$p link does not exist."
+else
+    [ -f "$p" ] || { ebusy "$p file does not exist." }
+	$file="$p"
+fi
 
 if [ "$command" = 'add' ]
 then

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2007-08-27 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 19:05 Ben Guthro [this message]
2007-08-30 15:35 ` [PATCH] Allow blktap specification to be a path to a file Keir Fraser
2007-08-30 15:43   ` Joshua Nicholas

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=46D32072.5040609@virtualiron.com \
    --to=bguthro@virtualiron.com \
    --cc=jnicholas@virtualiron.com \
    --cc=xen-devel@lists.xensource.com \
    /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.