Re: make-kpkg: permission denied making modules_image
- To: firstname.lastname@example.org
- Subject: Re: make-kpkg: permission denied making modules_image
- From: Kevin McKinley <email@example.com>
- Date: Tue, 1 Jul 2003 12:32:46 -0400
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <20030630201758.GA32603@piper.madduck.net>
- References: <20030627165013.GA6342@diamond.madduck.net> <email@example.com> <20030627165013.GA6342@diamond.madduck.net> <E19WkQX-0000Crfirstname.lastname@example.org> <20030627165013.GA6342@diamond.madduck.net> <email@example.com> <20030630201758.GA32603@piper.madduck.net>
On Mon, 30 Jun 2003 22:17:58 +0200
martin f krafft <firstname.lastname@example.org> wrote:
> > Right: with the default setup, the user who runs make-kpkg needs write
> > access to /usr/src/modules, or you need to run under sudo.
> what??? this must be a joke? /usr can be mounted read-only!
That's not a joke. You might be able to do many/most things with /usr
mounted read-only, but compiling source code [located in /usr] isn't one of
Think about this -- if /usr is mounted read-only how are object files to be