From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LvFAL-0007AN-SK for qemu-devel@nongnu.org; Sat, 18 Apr 2009 14:21:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LvFAH-00079m-Be for qemu-devel@nongnu.org; Sat, 18 Apr 2009 14:21:25 -0400 Received: from [199.232.76.173] (port=49142 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvFAH-00079c-2T for qemu-devel@nongnu.org; Sat, 18 Apr 2009 14:21:21 -0400 Received: from moutng.kundenserver.de ([212.227.126.177]:57234) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LvFAG-00051I-0l for qemu-devel@nongnu.org; Sat, 18 Apr 2009 14:21:20 -0400 Received: from localhost ([127.0.0.1] ident=stefan) by flocke.weilnetz.de with esmtp (Exim 4.69) (envelope-from ) id 1LvFA5-0005We-Mk for qemu-devel@nongnu.org; Sat, 18 Apr 2009 20:21:09 +0200 Message-ID: <49EA1A15.1080803@mail.berlios.de> Date: Sat, 18 Apr 2009 20:21:09 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink References: <20090418160104.GA18120@volta.aurel32.net> <390D1A11-602E-4449-BEA0-EA431F91D109@web.de> <20090418174555.GA16360@hall.aurel32.net> In-Reply-To: <20090418174555.GA16360@hall.aurel32.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Aurelien Jarno schrieb: > On Sat, Apr 18, 2009 at 07:22:20PM +0200, Andreas Färber wrote: > >> Am 18.04.2009 um 18:01 schrieb Aurelien Jarno: >> >> >>> For historical reasons, qemu system on i386 is called qemu instead of >>> qemu-system-i386. This seems to confuse users. >>> >>> This patch installs it as qemu-system-i386, and create a compatibility >>> symlink qemu -> qemu-system-i386 as some tools may call it that way. >>> We can change or remove this symlink after a few releases when all the >>> tools have migrated to this new name. >>> >>> Signed-off-by: Aurelien Jarno >>> >> In general a good idea imo, but don't just assume you can create >> symlinks on a given file system. Git uses hardlinks and copying as >> fallbacks iirc. >> > > For hardlinks that's clear. For symlinks, what (file)systems are you > thinking of? NTFS?