From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eY8Ru-0002id-6x for guix-patches@gnu.org; Sun, 07 Jan 2018 05:45:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eY8Rq-0007y7-W2 for guix-patches@gnu.org; Sun, 07 Jan 2018 05:45:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58255) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eY8Rq-0007xf-SU for guix-patches@gnu.org; Sun, 07 Jan 2018 05:45:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eY8Rq-0006Bb-EM for guix-patches@gnu.org; Sun, 07 Jan 2018 05:45:02 -0500 Subject: [bug#29875] [PATCH] gnu: qemu: Add wrapper for Samba. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20171228093234.42b99416@mykolab.com> <87bmiidabo.fsf@fastmail.com> <87efnd4q96.fsf@gnu.org> <20171229150224.3d6bdf82@mykolab.com> Date: Sun, 07 Jan 2018 11:44:35 +0100 In-Reply-To: <20171229150224.3d6bdf82@mykolab.com> (Rutger Helling's message of "Fri, 29 Dec 2017 15:02:24 +0100") Message-ID: <871sj2rlrg.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Rutger Helling Cc: 29875@debbugs.gnu.org Hi Rutger, Rutger Helling skribis: > I'm not sure it's as simple as that. AFAIK "/usr/sbin/smbd" only > appears in the configure file. You can modify it by specifying > smbd=3D/location/of/binary, which it then builds into the qemu* binaries. > I think it has to be a single binary (full path) with no arguments at > all or it doesn't work. That's why I chose to do it in this way. > > Maybe someone more familiar with the QEMU source code can do it by > patching the source code itself, but I would have no idea how to go > about it. Plus I'm not sure if that would end up being less complex, or > if it's even possible at all. Looking more carefully, =E2=80=98fork_exec=E2=80=99 in slirp/misc.c already= uses =E2=80=98execvp=E2=80=99 (meaning that the executable is searched for in $P= ATH), so it may be that configuring with: --smbd=3Dsmbd is enough to have =E2=80=98smbd=E2=80=99 searched for in $PATH, no? Thanks, Ludo=E2=80=99.