1 |
Hi, Mick. |
2 |
|
3 |
On Mon, Apr 25, 2011 at 03:12:15PM +0100, Mick wrote: |
4 |
> On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote: |
5 |
|
6 |
> > > Once it completes you can run --depclean which will ask you to |
7 |
> > > remove the older 2.6 python package. |
8 |
|
9 |
> > I had to (or, at least, did) run emerge -uND @world. Funnily enough, |
10 |
> > it ran to completion without manual intervention. :-) I'd like to |
11 |
> > run --depclean, but it's threatening to remove my 2.6.31-r6 kernel |
12 |
> > sources, which correspond to my working kernel. What's the easiest |
13 |
> > way to protect these from --depclean? |
14 |
|
15 |
> Aha! That's why I said first look at what it wants to remove - you |
16 |
> don't want to cripple your system. In this case of course it won't |
17 |
> cripple anything, because it won't remove the kernel image from /boot/ |
18 |
|
19 |
> If you look in /usr/src/linux/ you will see a number of kernel sources |
20 |
> listed in there. If you've run update world there should be a more |
21 |
> up-to-date kernel awaiting for you to configure and compile it. Do |
22 |
> that first; copy the necessary files into /boot; configure grub.conf to |
23 |
> boot with you latest kernel; and after you boot into it and check that |
24 |
> all is good you can allow -- depclean to remove older kernel source |
25 |
> files. |
26 |
|
27 |
Yes, I've got new kernel sources, and yesterday and today I've spent |
28 |
about 5 hours head-banging to get a working kernel. (I've managed it, |
29 |
thankfully.) But the new kernel's X-windows isn't filling my 1920x1080 |
30 |
shiny new monitor like the old kernel did. I've still got some fiddling |
31 |
to do. |
32 |
|
33 |
Call me a clinging cry-baby if you like, but until I'm confident about my |
34 |
new kernel, I'd like to hang on to the old one, including its sources. |
35 |
It'd also be nice to run --depclean in the meantime. Do I have to do |
36 |
recursive copying or directory renaming to achiev this? |
37 |
|
38 |
As a matter of interest, do you know how to configure a framebuffer |
39 |
console to fill up a wide screen (say, to a width of 170 characters) as |
40 |
contrasted with the 128 characters which were optimum on an old fashioned |
41 |
CRT? |
42 |
|
43 |
> PS. You may need to manually remove older source files left in |
44 |
> /usr/src/linux/ when depclean completes its job. |
45 |
|
46 |
OK. I can manage that. |
47 |
|
48 |
> -- |
49 |
> Regards, |
50 |
> Mick |
51 |
|
52 |
-- |
53 |
Alan Mackenzie (Nuremberg, Germany). |