~alpine/devel

Let is_xen_dom0 fail silently v1 PROPOSED

Eivind Uggedal <eivind@uggedal.com>
10 years ago 
Eivind Uggedal: 1
 Let is_xen_dom0 fail silently

 1 files changed, 1 insertions(+), 1 deletions(-)
Export patchset (mbox)
How do I use this?

Copy & paste the following snippet into your terminal to import this patchset into git: 

curl -s https://lists.alpinelinux.org/~alpine/devel/patches/582/mbox | git am -3
Learn more about email & git
Reply to thread View this thread in the archives

[alpine-devel] [PATCH] Let is_xen_dom0 fail silently Export this patch

Eivind Uggedal <eivind@uggedal.com>
10 years ago 
/proc/xen/capabilities can be non-existent while /proc/xen
exists.

This behaviour was seen when booting in rescue mode on
Linode.
---
 libalpine.sh.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libalpine.sh.in b/libalpine.sh.in
index a03deb3c6b91..7aec8155d1be 100644
--- a/libalpine.sh.in
+++ b/libalpine.sh.in
@@ -89,7 +89,7 @@ is_xen() {
# Detect if we are running Xen Dom0
is_xen_dom0() {
	is_xen && \
	grep -q "control_d" /proc/xen/capabilities
	grep -q "control_d" /proc/xen/capabilities 2>/dev/null
}

# list of available network interfaces that aren't part of any bridge or bond

-- 
1.8.4.1



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---