LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Harald Dunkel <harri@afaics.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: how to avoid that install.sh goes mad, if I am not root?
Date: Thu, 20 Jan 2011 20:16:24 +0100 [thread overview]
Message-ID: <4D388A08.1010004@afaics.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
I am trying to build my own custom Debian kernel package. Problem:
If the kernel is supposed to be installed in a temporary package
build directory, then it dies with
:
:
make[1]: Entering directory `/var/tmp/build_kernel/raw-kernel-2.6.37/linux-2.6.37'
sh /var/tmp/build_kernel/raw-kernel-2.6.37/linux-2.6.37/arch/x86/boot/install.sh 2.6.37 arch/x86/boot/bzImage \
System.map "/var/tmp/build_kernel/raw-kernel-2.6.37/debian/raw-kernel-2.6.37/boot"
run-parts: executing /etc/kernel/postinst.d/dkms 2.6.37 /var/tmp/build_kernel/raw-kernel-2.6.37/debian/raw-kernel-2.6.37/boot/vmlinuz-2.6.37
dkms: running auto installation service for kernel 2.6.37:
nvidia-current (260.19.29)...done.
vboxhost (3.2.12)...done.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.37 /var/tmp/build_kernel/raw-kernel-2.6.37/debian/raw-kernel-2.6.37/boot/vmlinuz-2.6.37
run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.37 /var/tmp/build_kernel/raw-kernel-2.6.37/debian/raw-kernel-2.6.37/boot/vmlinuz-2.6.37
touch: cannot touch `/var/run/do-not-hibernate': Permission denied
run-parts: /etc/kernel/postinst.d/pm-utils exited with return code 1
make[3]: *** [install] Error 1
make[2]: *** [install] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/var/tmp/build_kernel/raw-kernel-2.6.37/linux-2.6.37'
AFAICS this happens because the arch/x86/boot/install.sh script calls
/sbin/installkernel, which in turn runs all the scripts delivered
by various other packages. This is fine for a regular kernel install
as well as for an installation of the final kernel package, but for
a non-root install in a package build directory /sbin/installkernel
and all the run-parts scripts should not be run. installkernel doesn't
even know the redefined install directory.
Would it be possible to avoid that /sbin/installkernel is run by
install,sh, e.g. if the install directory has been redefined, or if
UID != 0?
Any helpful comment would be highly appreciated
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk04igIACgkQUTlbRTxpHjcO3wCcCXsb6ma4ypqQliWi8XYyFcUE
6PYAnA1JP78Bw2uZM4eyr4FHO9uBi0Ex
=zAFX
-----END PGP SIGNATURE-----
next reply other threads:[~2011-01-20 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 19:16 Harald Dunkel [this message]
2011-01-20 21:47 ` Mikael Pettersson
2011-01-21 12:49 ` WANG Cong
2011-01-21 22:08 ` Harald Dunkel
2011-01-24 10:21 ` [Patch] make installkernel configurable from command line (was Re: how to avoid that install.sh goes mad, if I am not root?) Américo Wang
2011-01-24 11:43 ` Mikael Pettersson
2011-01-25 5:48 ` Américo Wang
2011-01-26 10:02 ` Mikael Pettersson
2011-01-28 7:58 ` WANG Cong
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=4D388A08.1010004@afaics.de \
--to=harri@afaics.de \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: how to avoid that install.sh goes mad, if I am not root?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).