| 1 |
On Friday, 29 July 2011 07:58:13 Daniel Hilst Selli did opine thusly: |
| 2 |
> Em 28-07-2011 12:05, Alan McKinnon escreveu: |
| 3 |
> > On Thursday 28 July 2011 11:53:04 Daniel Hilst Selli did opine |
| 4 |
thusly: |
| 5 |
> >> I have some old kernel trees here.. But there is no Makefiles |
| 6 |
> >> for some of them. I did not remove the Makefiles. There is |
| 7 |
> >> anyone having the same problem? Whats happen? |
| 8 |
> >> |
| 9 |
> >> I emerge -NuD periodically, some times I see my kernel |
| 10 |
> >> being updated.. May portage remove my Makefiles?? |
| 11 |
> > |
| 12 |
> > In real life, portage seldom (if ever) *updates* a kernel src |
| 13 |
> > package. Almost all kernel versions, even ones with teeny-weeny |
| 14 |
> > -r changes in the version number, are an entirely new package |
| 15 |
> > which installs into it's own directory in /usr/src/ |
| 16 |
> > |
| 17 |
> > So, |
| 18 |
> > gentoo-sources-2.6.39-r1 |
| 19 |
> > will touch nothing belonging to |
| 20 |
> > gentoo-sources-2.6.39 |
| 21 |
> > |
| 22 |
> > This is in contrast to how most packages work, where -r versions |
| 23 |
> > contain gentoo patches or ebuild tweaks but still use exactly |
| 24 |
> > the same sources. |
| 25 |
> > |
| 26 |
> > Perhaps you have unmerged old kernel sources that were |
| 27 |
> > previously |
| 28 |
> > built. In this case portage will remove the files it put there |
| 29 |
> > and leave everything the compiler built. Run this: |
| 30 |
> > |
| 31 |
> > du -sh /usr/src/* |
| 32 |
> > |
| 33 |
> > Anything with a size of about 300M has probably had this happen. |
| 34 |
> > Intact trees that were built tend to come out at around 700M |
| 35 |
> |
| 36 |
> Thanks for replying, so this might be the case |
| 37 |
> output -> http://sprunge.us/YMAM |
| 38 |
|
| 39 |
Please don't use images on websites like that for command output, |
| 40 |
rather just copy the text from your console into the body of the mail. |
| 41 |
|
| 42 |
> Can this be done after a emerge --depclean, while booted on some |
| 43 |
> newly emerged kernel? |
| 44 |
|
| 45 |
--depclean is unlikely to do that as kernel sources almost always end |
| 46 |
up in world. It will behave different if you emerge the sources with -1 |
| 47 |
|
| 48 |
The running kernel has nothing to do with what portage may or may not |
| 49 |
do with your installed sources, much like how KDE will still run fine |
| 50 |
regardless of whether you have the tarballs downloaded or not, or |
| 51 |
whether you have KDE source trees lying around or not. |
| 52 |
|
| 53 |
I don't know what the answer to your question is, your statements are |
| 54 |
vague and only apply to principles but you want specifics. You are |
| 55 |
going to have to look inside those directories and see what is there, |
| 56 |
because I can't. |
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
alan dot mckinnon at gmail dot com |
Archives