From: Ronald G Minnich <rminnich@lanl.gov>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: install issues
Date: Mon, 17 Jul 2006 08:44:57 -0600 [thread overview]
Message-ID: <44BBA269.6020002@lanl.gov> (raw)
xen shares a problem with a lot of python installers: if you build the
xen on a file system mounted with root squash, the install fails:
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map -b / -r 2.6.16.13-xen; fi
make[3]: Leaving directory
`/home/rminnich/src/xen-3.0-testing.hg/linux-2.6.16.13-xen'
make -C linux-2.6.16.13-xen ARCH=i386 INSTALL_PATH=/ vmlinuz
make[3]: Entering directory
`/home/rminnich/src/xen-3.0-testing.hg/linux-2.6.16.13-xen'
rm: cannot remove `.kernelrelease': Permission denied
make[3]: *** [.kernelrelease] Error 1
make[3]: Leaving directory
`/home/rminnich/src/xen-3.0-testing.hg/linux-2.6.16.13-xen'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/home/rminnich/src/xen-3.0-testing.hg'
make[1]: *** [linux-2.6-xen-install] Error 2
make[1]: Leaving directory `/home/rminnich/src/xen-3.0-testing.hg'
make: *** [install-kernels] Error 1
This is a particularly annoying attribute of many python install tools,
that you can't run it as root and you can't NOT run it as root.
I don't know how this ought to be fixed, but note that (e.g.) linux
install gets this one right.
thanks
ron
next reply other threads:[~2006-07-17 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 14:44 Ronald G Minnich [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-10 11:17 Install issues H.Merijn Brand
2008-11-10 11:39 ` Miklos Vajna
2008-11-10 16:31 ` H.Merijn Brand
2008-11-10 17:51 ` Miklos Vajna
2008-11-11 7:59 ` H.Merijn Brand
2008-11-11 9:17 ` Andreas Ericsson
2008-11-11 17:47 ` Junio C Hamano
2008-11-11 18:02 ` H.Merijn Brand
2008-11-11 23:03 ` Boyd Lynn Gerber
2008-11-11 23:35 ` H.Merijn Brand
2008-11-11 23:42 ` Junio C Hamano
2008-11-11 23:53 ` H.Merijn Brand
2008-11-12 8:14 ` Andreas Ericsson
2008-11-11 21:11 ` Junio C Hamano
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=44BBA269.6020002@lanl.gov \
--to=rminnich@lanl.gov \
--cc=xen-devel@lists.xensource.com \
/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.