From: Akio Takebe <takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [Patch] adding some scripts at installing
Date: Tue, 30 Oct 2007 18:29:28 +0900 [thread overview]
Message-ID: <CAC81AD75E5BE2takebe_akio@jp.fujitsu.com> (raw)
Hi,
I wanted to use network with --mac optin of kvm script on guest,
but I didn't use it because I didn't know needing to copy some scripts.
I think it is better that we can use --mac option after "make install".
So I modified install section in the Makefile.
Signed-off-by: Akio Takebe <takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
---
--- kvm-49/Makefile 2007-10-29 02:14:57.000000000 +0900
+++ kvm-49.new/Makefile 2007-10-30 18:14:42.000000000 +0900
@@ -43,6 +43,10 @@ install:
$(kcmd)make -C kernel DESTDIR="$(DESTDIR)" install
make -C user DESTDIR="$(DESTDIR)" install
make -C qemu DESTDIR="$(DESTDIR)" install
+ install -d $(DESTDIR)/$(confdir)
+ cp scripts/kvm $(DESTDIR)/$(initdir)/kvm
+ cp scripts/qemu-ifup $(DESTDIR)/$(confdir)/qemu-ifup
+ install -t $(DESTDIR)/etc/udev/rules.d scripts/*kvm*.rules
tmpspec = .tmp.kvm.spec
RPMDIR=$$(pwd)/RPMS
Best Regards,
Akio Takebe
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-30 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 9:29 Akio Takebe [this message]
2007-10-30 9:36 ` [Patch] adding some scripts at installing Alexey Eremenko
[not found] ` <64F9B87B6B770947A9F8391472E032160C95C584-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-10-30 10:31 ` Akio Takebe
[not found] ` <CAC81AD75E5BE2takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-10-30 11:25 ` Avi Kivity
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=CAC81AD75E5BE2takebe_akio@jp.fujitsu.com \
--to=takebe_akio-+cum20s59erqfuhtdcdx3a@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox