From: Daniel Hilst Selli <danielhilst@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel make files disappear
Date: Fri, 29 Jul 2011 07:58:13 -0300 [thread overview]
Message-ID: <4E329245.4070304@gmail.com> (raw)
In-Reply-To: <1428483.41BuF8nsCn@nazgul>
Em 28-07-2011 12:05, Alan McKinnon escreveu:
> On Thursday 28 July 2011 11:53:04 Daniel Hilst Selli did opine thusly:
>> I have some old kernel trees here.. But there is no Makefiles for
>> some of them. I did not remove the Makefiles. There is anyone
>> having the same problem? Whats happen?
>>
>> I emerge -NuD periodically, some times I see my kernel
>> being updated.. May portage remove my Makefiles??
> In real life, portage seldom (if ever) *updates* a kernel src package.
> Almost all kernel versions, even ones with teeny-weeny -r changes in
> the version number, are an entirely new package which installs into
> it's own directory in /usr/src/
>
> So,
> gentoo-sources-2.6.39-r1
> will touch nothing belonging to
> gentoo-sources-2.6.39
>
> This is in contrast to how most packages work, where -r versions
> contain gentoo patches or ebuild tweaks but still use exactly the same
> sources.
>
> Perhaps you have unmerged old kernel sources that were previously
> built. In this case portage will remove the files it put there and
> leave everything the compiler built. Run this:
>
> du -sh /usr/src/*
>
> Anything with a size of about 300M has probably had this happen.
> Intact trees that were built tend to come out at around 700M
>
Thanks for replying, so this might be the case
output -> http://sprunge.us/YMAM
Can this be done after a emerge --depclean, while booted on some newly
emerged kernel?
--
"Do or do not... there is no try" Yoda Master
next prev parent reply other threads:[~2011-07-29 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 14:53 [gentoo-user] kernel make files disappear Daniel Hilst Selli
2011-07-28 15:05 ` Alan McKinnon
2011-07-29 10:58 ` Daniel Hilst Selli [this message]
2011-07-29 11:31 ` Alan McKinnon
2011-07-29 11:38 ` Michael Mol
2011-07-29 12:09 ` Joost Roeleveld
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=4E329245.4070304@gmail.com \
--to=danielhilst@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox