Re: [Wine] tascam us-16x08 settings panel

2015-09-24 Thread James McKenzie
Mr. Kraus:

HTML and picture attachments are stripped by the list mailer. Might I
suggest using the Forums for assistance with Wine issues?

James McKenzie


On Tue, Sep 22, 2015 at 12:10 AM, Mr. Kraus  wrote:

> An HTML attachment was scrubbed...
> URL: <
> http://www.winehq.org/pipermail/wine-users/attachments/20150922/efca08fa/attachment.html
> >
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: systemd-nspawn and /run/resolvconf/resolv.conf

2015-09-24 Thread Tom H
On Tue, Sep 22, 2015 at 10:19 AM, Ralf Mardorf
 wrote:
> On Tue, 22 Sep 2015 08:36:27 -0400, Tom H wrote:


> Thank you Tom for taking the time.

You're welcome.


>> So it works when using "-b".
>>
>> But you're right, it doesn't when not using "-b".
>>
>> Ubuntu decided to default to using resolvconf with 12.04. I suspect
>> that it'll take more than "it doesn't work when using systemd-nspawn
>> as a basic chroot process" for this change to be reversed.
>
> So I don't report it as a bug.

It might be worth reporting it so something like what lxc used to do
(see below; I grepped through the various lxc scripts and didn't find
anything resolv.conf related, so it no longer does this AFAICS).

When systemd-nspawn is used without "-b" it's eseentially a chroot
without having to mount/bind-mount anything before entering the
chroot.

You need to ensure that a proper resolv.conf exists in a chroot before
switching to it. When installing Gentoo, for example, you "cp -L
/etc/resolv.conf $chroot/etc" before chrooting because the
installation tarball doesn't have a resolv.conf. I'm sure that if you
check the Arch installation scripts, you'll find something similar.


>> Do you have lxc installed? How does it handle resolv.conf as a symlink?
>
> No. Since I never used it, it's too time consuming to care about
> LinuxContainers now.

I installed lxc and set up a container. I'd forgotten that it starts
up with the systemd-nspawn "-b" by default so a resolv.conf symlink
works.

I haven't used lxc in a while but I remembered as I was setting up my
container that there used to be a routine to detect whether
resolv.conf was a symlink and, if it was, back it up and copy the
host's resolv.conf.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: systemd-nspawn and /run/resolvconf/resolv.conf

2015-09-24 Thread Tom H
On Thu, Sep 24, 2015 at 10:18 AM, Tom H  wrote:
>
> You need to ensure that a proper resolv.conf exists in a chroot before
> switching to it. When installing Gentoo, for example, you "cp -L
> /etc/resolv.conf $chroot/etc" before chrooting because the
> installation tarball doesn't have a resolv.conf. I'm sure that if you
> check the Arch installation scripts, you'll find something similar.

The arch-chroot installation script has the following function:

chroot_add_resolv_conf() {
  local chrootdir=$1 resolv_conf=$1/etc/resolv.conf

  # Handle resolv.conf as a symlink to somewhere else.
  if [[ -L $chrootdir/etc/resolv.conf ]]; then
# readlink(1) should always give us *something* since we know at this point
# it's a symlink. For simplicity, ignore the case of nested symlinks.
resolv_conf=$(readlink "$chrootdir/etc/resolv.conf")
if [[ $resolv_conf = /* ]]; then
  resolv_conf=$chrootdir$resolv_conf
else
  resolv_conf=$chrootdir/etc/$resolv_conf
fi

# ensure file exists to bind mount over
if [[ ! -f $resolv_conf ]]; then
  install -Dm644 /dev/null "$resolv_conf" || return 1
fi
  elif [[ ! -e $chrootdir/etc/resolv.conf ]]; then
# The chroot might not have a resolv.conf.
return 0
  fi

  chroot_add_mount /etc/resolv.conf "$resolv_conf" --bind
}

So they mount the host's resolv.conf on the chroot's.

And there's the following patch in lxc 0.7.5-3ubuntu69:

# cat 0031-ubuntu-template-resolvconf.patch
Description: handle /etc/resolv.conf being a symlink
 This will be forwarded upstream.
Author: Serge Hallyn 
Forwarded: no
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/922706

Index: lxc/templates/lxc-ubuntu.in
===
--- lxc.orig/templates/lxc-ubuntu.in 2012-01-27 10:45:16.167886074 -0600
+++ lxc/templates/lxc-ubuntu.in 2012-01-27 10:50:39.567880601 -0600
@@ -389,9 +389,13 @@
 chroot $rootfs apt-get install --force-yes -y
python-software-properties
 chroot $rootfs add-apt-repository ppa:ubuntu-virt/ppa
 fi
-cp /etc/resolv.conf "${rootfs}/etc"
+ cresolvonf="${rootfs}/etc/resolv.conf"
+ mv $cresolvonf ${cresolvonf}.lxcbak
+cat /etc/resolv.conf > ${cresolvonf}
 chroot $rootfs apt-get update
 chroot $rootfs apt-get install --force-yes -y lxcguest
+ rm -f ${cresolvonf}
+ mv ${cresolvonf}.lxcbak ${cresolvonf}
 fi
 }

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: systemd-nspawn and /run/resolvconf/resolv.conf

2015-09-24 Thread Ralf Mardorf
On Thu, 24 Sep 2015 13:03:32 -0400, Tom H wrote:
>  chroot_add_mount /etc/resolv.conf "$resolv_conf" --bind
>}
>
>So they mount the host's resolv.conf on the chroot's.
>
>And there's the following patch in lxc 0.7.5-3ubuntu69:
>
># cat 0031-ubuntu-template-resolvconf.patch
>Description: handle /etc/resolv.conf being a symlink

:)

Since I don't want to use the systemd-nspawn boot option, I'll keep a
resolv.conf in Ubuntu's /etc.

Regards,
Ralf

PS: OT: Today I replaced my ADSL-modem with a router.

# pidof pppd || echo ":D"
:D

I still use a LAN cable for my PC and WLAN only for a tablet PC. I
wonder how secure the WLAN is and how to disable it, so I have to read
a little bit.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss