I've already posted question about /dev/shm/sysconfig/xenbridges before. After some investigation: On openSUSE 11.1 /dev/shm/sysconfig was created by /etc/sysconfig/network/scripts/functions.common:

# RUN_FILES_BASE contains the path to the configuration data cache. # It __must__ __not__ contain a trailing slash. RUN_FILES_BASE=/dev/shm/sysconfig test -d $RUN_FILES_BASE || mkdir -p $RUN_FILES_BASE

xen bridge creation stores information then (/etc/xen/scripts/network-bridge):

# Record creation of bridge in /dev/shm/sysconfig/xenbridges so other # tools, e.g. yast2 lan, know that Xen bridging is active. [ -d /dev/shm/sysconfig/xenbridges ] || mkdir /dev/shm/sysconfig/xenbridges touch /dev/shm/sysconfig/xenbridges/${bridge}

But in openSUSE 11.2 RUN_FILES_BASE was changed:

# RUN_FILES_BASE contains the path to the configuration data cache. # It __must__ __not__ contain a trailing slash. RUN_FILES_BASE=/dev/.sysconfig/network test -d $RUN_FILES_BASE || mkdir -p $RUN_FILES_BASE

I was unable to find anything that takes care of creation '/dev/shm/sysconfig' directory used in '/etc/xen/scripts/network-bridge' I think the simplest way to fix this is to add '-p' option to mkdir inside of /etc/xen/scripts/network-bridge Please advise. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org