From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink
Date: Sat, 18 Apr 2009 19:45:55 +0200 [thread overview]
Message-ID: <20090418174555.GA16360@hall.aurel32.net> (raw)
In-Reply-To: <390D1A11-602E-4449-BEA0-EA431F91D109@web.de>
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 <aurelien@aurel32.net>
>
> 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?
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2009-04-18 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 16:01 [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink Aurelien Jarno
2009-04-18 16:42 ` Anthony Liguori
2009-04-19 11:22 ` Stefan Weil
2009-04-19 11:32 ` andrzej zaborowski
2009-04-18 17:22 ` Andreas Färber
2009-04-18 17:45 ` Aurelien Jarno [this message]
2009-04-18 18:21 ` Stefan Weil
2009-04-18 21:12 ` Aurelien Jarno
2009-04-18 22:11 ` Anthony Liguori
2009-04-18 23:43 ` Re : " Sylvain Petreolle
2009-04-19 2:50 ` Jamie Lokier
2009-04-18 18:34 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090418174555.GA16360@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.