From: "Grzesiek Sójka" <pld-t9zbU3WrWHI@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: OT: compilation
Date: Thu, 07 Oct 2010 22:38:09 +0200 [thread overview]
Message-ID: <4CAE2FB1.3000603@pfu.pl> (raw)
In-Reply-To: <20101007233420.1f763477-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
On 10/07/10 22:34, Pekka Paalanen wrote:
> On Thu, 07 Oct 2010 22:14:19 +0200
> Grzesiek Sójka<pld-t9zbU3WrWHI@public.gmane.org> wrote:
>
>> I have two problems with the kernel compilation.
>>
>> 1. I have a small rootfs. It is too small to put all the modules
>> there without gzipping it first. So installing it requires lots
>> of sweating. That is why I was wondering if there is a (more/less
>> easy) way to make the "make modules_install" command gzip the
>> modules "on the fly".
>
> Wait, does modprobe support compressed kernel modules? I've
Yes, it does. I thing that most of the distribution pre-compiled kernels
does have gziped modules.
> never heard of that. If you really do not want to touch
> the partitioning, how about symlinking some directories
> elsewhere? Be careful on what is needed to boot, though.
Wrong idea. I already tried this.
next prev parent reply other threads:[~2010-10-07 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 20:14 OT: compilation Grzesiek Sójka
[not found] ` <4CAE2A1B.1000105-t9zbU3WrWHI@public.gmane.org>
2010-10-07 20:34 ` Pekka Paalanen
[not found] ` <20101007233420.1f763477-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-10-07 20:38 ` Grzesiek Sójka [this message]
2010-10-07 20:46 ` Grzesiek Sójka
[not found] ` <4CAE3198.3020405-t9zbU3WrWHI@public.gmane.org>
2010-10-08 0:21 ` walt
2010-10-07 20:50 ` Xavier Chantry
[not found] ` <AANLkTi=HO9rxCTOXdhagYm7WB-pF73C8_eipMCrYeGOG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-07 21:04 ` Grzesiek Sójka
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=4CAE2FB1.3000603@pfu.pl \
--to=pld-t9zbu3wrwhi@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=pq-X3B1VOXEql0@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 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.