Commit Graph
14 Commits
Author SHA1 Message Date
kaf24@firebug.cl.cam.ac.uk 3244faf9d5 Make sure that installed files have sensible permissions and are owned by the
user running install. Also clean up the install script a little.

Signed-off-by: Horms <horms@verge.net.au>
Signed-off-by: Keir Fraser <keir@xensource.com>
2006-03-02 11:41:48 +01:00
emellor@leeni.uk.xensource.com f3ac9a462d check_hotplug fails on one of my machines running ubunto 4.10 "Warty
Warhog", due to misparsing the udevinfo version string. The problem is
caused by an old version of sed that does not appreciate the
regexp. This patch fixes it, and also works on debian unstable and
SLES9SP2. Please apply...

Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org>
Signed-Off-By: Orna Agmon <ladypine@ladypine.org>
2005-11-25 15:26:19 +00:00
emellor@leeni.uk.xensource.com 20e3f38ade Changes check for "udev", so that it works on debian sid (that does not
have /sbin/udev anymore).

Signed-off-by: Murillo F. Bernardes <mfb@br.ibm.com>
2005-11-21 17:03:21 +01:00
kaf24@firebug.cl.cam.ac.uk e7b975b0b6 If /sbin/ isn't in the path, udev rules will erroneously not get
installed.

Signed-off-by: Nivedita Singhvi <niv@us.ibm.com>
2005-11-14 11:05:34 +01:00
kaf24@firebug.cl.cam.ac.uk 726081b63b Add installation of the udev rules if appropriate. With a normal 'make
install', the udev rules will be installed if udev version is >= 059;
otherwise, the hotplug rules get installed.

When 'make dist' is done, we set a variable so that both hotplug and
udev rules are installed into the dist tarball.  install.sh then takes
care of picking the proper rules.

Also changes the hotplug check to look for a proper udev version

Signed-off-by: Jeremy Katz <katzj@redhat.com>
2005-10-07 14:47:45 +01:00
iap10@freefall.cl.cam.ac.uk 6f0a999a9c bitkeeper revision 1.1159.258.152 (42905f2aihfbXcLOp47iveS8Fn06aQ)
Fix install.sh script so that it doesn't dereference all symlinks.
Signed-off-by: ian@xensource.com
2005-05-22 10:30:02 +00:00
cl349@firebug.cl.cam.ac.uk d334aaae95 bitkeeper revision 1.1159.258.123 (42852fd48Nr7wIoriw8GV3ZAjVOw8Q)
Many files:
  Create vmlinuz-$(VERSION).$(PATCHLEVEL)-$(XENGUEST) and
  vmlinuz-$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)-$(XENGUEST) symlinks in
  dist/install/boot from kernel build target.
install.sh:
  No need to create vmlinuz symlinks in dist/install/boot from install.sh
  anymore.
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
2005-05-13 22:53:08 +00:00
kaf24@firebug.cl.cam.ac.uk 9b82bd2d0c bitkeeper revision 1.1159.258.59 (423a99c28LSWeyvb5zB2Je7BjDgLww)
Fix install script to follow symlinks.
Signed-off-by: Paul Larson <pl@us.ibm.com>
Signed-off-by: Keir Fraser <keir@xensource.com>
2005-03-18 09:05:06 +00:00
iap10@freefall.cl.cam.ac.uk 8e86d6ab9f bitkeeper revision 1.1159.258.40 (423085c6l2rF-ZZuQiNGB3ZR9Vzj7A)
Tiny hack to fix install.sh for the case where /etc/init.d is a symlink.
Signed-off-by: ian@xensource.com
2005-03-10 17:37:10 +00:00
iap10@freefall.cl.cam.ac.uk 35fcf16038 bitkeeper revision 1.1159.223.43 (41f7fa5dY-DhsXNFoEJlVfLdK5MEXQ)
fix missing space
2005-01-26 20:15:25 +00:00
iap10@freefall.cl.cam.ac.uk ae69d44b66 bitkeeper revision 1.1159.223.33 (41f5a006O57aqVcLmvmGSgDN2Chvbw)
install.sh now creates vmlinuz-2.6.99-xen0 -> vmlinuz-2.6-xen0 links etc

Signed-off-by: pl@us.ibm.com
Signed-off-by: ian.pratt@cl.cam.ac.uk
2005-01-25 01:25:26 +00:00
iap10@labyrinth.cl.cam.ac.uk a5f3892433 bitkeeper revision 1.1159.165.1 (418aa0f4koam0mhscMMP2HGuqLK5kQ)
install.sh now does a few checks to warn the user if prerequisite tools are missing.
2004-11-04 21:36:52 +00:00
kaf24@freefall.cl.cam.ac.uk b37cf37288 bitkeeper revision 1.1159.1.340 (4187f582gn4AZ67FyEzNonoTpbod3w)
Fix 'make dist' so that it creates a dist/ directory suitable for turning
into a binary-only distribution tarball.
2004-11-02 21:00:50 +00:00
kaf24@freefall.cl.cam.ac.uk e81e528835 bitkeeper revision 1.1159.1.338 (4187ca95yoh3y8SwBJw4uTmgIxLCTw)
A new install script to install from the intermediate 'install' subdir.
Also now a bit more careful in use of 'cp -a'. When installing to
system-wide directories we probably do not want to preserve ownership
of the random unprivileged user that originally built the binaries.
The user who does the install (probably root) is the correct person
to own the target files.
2004-11-02 17:57:41 +00:00