WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] vif could not be connected. Hotplug scripts not working.

On Fri, 2007-01-12 at 09:19 +0100, Ulrich Windl wrote:
> On 12 Jan 2007 at 4:25, Tim Post wrote:
> 
> > On Thu, 2007-01-11 at 19:23 +0000, John Hannfield wrote:
> > > Hi all,
> > > 
> > > I'm trying to boot a Centos domU, but when I do a "xm create -c 
> > > centos.cfg"
> > > it just hangs, and eventually times out with:
> > > 
> > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> > > 
> > 
> > Ensure that /bin/sh leads to /bin/bash (i.e. readlink /bin/sh ).. if
> > not, ln -s -f /bin/bash /bin/sh
> 
> Actually that should be /usr/bin/sh for at least 10 years ;-) 
> /bin/cp and /bin/cat are UNIX dinosaurs, just as /bin/sh. Traditionally these 
> exist as symbolic links to the updated locations.

Amen! Brother! Can you please CC Redhat, Debian and Knoppix on that?
While your at it, tell them that exiting 0 = good, !0 = bad, or
something other than good, and please apply that logic to everything
found in /bin , /sbin, /usr/bin and /usr/sbin. 

> 
> > 
> > Its quite possible on your system /bin/sh leads to dash, which isn't
> > capable of parsing the hotplug scripts in /etc/xen/scripts, which is the
> > cause of this error.
> 
> I'm sure everybody is aware that when using /bin/sh, you may only use the 
> features 
> of the classic Bourne shell, wile /usr/bin/sh most likely is a POSIX shell, 
> and 
> "bash" is ... well: "bash". Expecting from /bin/sh to be more capable than 
> Bourne 
> shell of 15 years ago is a mistake. Personally I'm using POSIX features 
> unless I 
> absolutely need Bash, but then I specify /bin/bash as Shell.
> 
> Sorry for preaching.

No your not preaching, very few realize the shell changes with its
invocation, not many are aware :) Most scripts define the bourne-ish (or
other than perl) interpreter living in /bin, while perl scripts
typically predicate /usr/bin. 

So, yeah, 15 or so year time line is correct :) Amazing how things
linger.

> 
> Ulrich
> 

Best,
--Tim

> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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