1 |
On Mon, 25 Jun 2012 00:05:25 -0500, Dale wrote: |
2 |
|
3 |
> It appears that grub2 is coming soon. Thread on -dev said a couple |
4 |
> months or so till it hits the tree, keyworded and/or masked I'm sure. I |
5 |
> guess it is about time to jump off the cliff and give this a try. |
6 |
|
7 |
If GRUB legacy is working for you, I see no need to change. I put GRUB 2 |
8 |
on new installs but haven't seen any reason to switch over existing |
9 |
systems. |
10 |
|
11 |
On the other hand, if you want to learn more about it, go for it! |
12 |
I |
13 |
> My first question is, how hard is this to change from old grub to |
14 |
> grub2? |
15 |
|
16 |
The same as installing GRUB 2 from scratch. I would waste time trying to |
17 |
have both installed (I'm not sure if that's even supported any more) |
18 |
as it's easy enough to reinstall legacy from a live CD if you have to, but |
19 |
keep your menu.lst. |
20 |
|
21 |
> I must confess tho, I'm a |
22 |
> hoarder of kernels. LOL I generally have several versions of them on |
23 |
> here. Is there a way for it to only see say the last 3 versions or so? |
24 |
> I only have three right now but I cleaned out all the non-init kernels a |
25 |
> while back. Given time, I may have a dozen or so. I would rather not |
26 |
> have that many lines on the grub screen when booting. |
27 |
|
28 |
You could edit the script that searches for an adds Linux kernels, or |
29 |
disable it. I use the custom script to add my own entries at the top of |
30 |
the menu and let the standard 10_linux script add all detected kernel |
31 |
below. It lists them most recent first, so any excess of kernels falls |
32 |
off the bottom of the screen :) |
33 |
|
34 |
> Also, will it know what init thingy image to connect the kernels too? I |
35 |
> name my kernels with the version and name the init thingy with a similar |
36 |
> name. Looks someting like this: |
37 |
> |
38 |
> root@fireball / # ls -al /boot/bzImage-3.* |
39 |
> -rw-r--r-- 1 root root 4740064 May 16 20:25 /boot/bzImage-3.3.5-2 |
40 |
> -rw-r--r-- 1 root root 4758496 May 23 13:09 /boot/bzImage-3.4.0-1 |
41 |
> -rw-r--r-- 1 root root 4758816 Jun 14 09:00 /boot/bzImage-3.4.2.r1-1 |
42 |
> root@fireball / # ls -al /boot/initramfs-3.* |
43 |
> -rw-r--r-- 1 root root 3560934 May 12 05:03 /boot/initramfs-3.3.5-1.img |
44 |
> -rw-r--r-- 1 root root 3560423 May 23 13:10 /boot/initramfs-3.4.0.img |
45 |
> -rw-r--r-- 1 root root 3561170 Jun 14 09:05 /boot/initramfs-3.4.2.img |
46 |
|
47 |
That should work, although I do not use a separate initramfs file so I |
48 |
haven't tried it. |
49 |
|
50 |
> There are times when I may have more than one kernel but only one init |
51 |
> thingy tho. So far, one init thingy will work with any kernel of that |
52 |
> version. I have not tried mixing tho. |
53 |
|
54 |
Use symlinks, or a custom menu. |
55 |
|
56 |
> Also, how much disk space does grub take up on /boot? Mine is on a |
57 |
> separate partition and I hope it is large enough. |
58 |
|
59 |
% df /boot |
60 |
Filesystem Type Size Used Avail Use% Mounted on |
61 |
/dev/md0 ext2 482M 406M 51M 89% /boot |
62 |
|
63 |
However, 380MB of that is a System Rescue CD ISO, one of the nice things |
64 |
about GRUB 2 is that you can boot straight fro the ISO, no need to go |
65 |
hunting for a CD when you need a live boot (unless the reaso you need a |
66 |
live boot is that you screwed up GRUB :) |
67 |
|
68 |
% du /boot/grub2 |
69 |
1.5M /boot/grub2 |
70 |
|
71 |
A GRUB legacy box here gives |
72 |
|
73 |
% du /boot/grub |
74 |
990K /boot/grub |
75 |
|
76 |
so not much difference. |
77 |
|
78 |
> Miss the compile output? Hint: |
79 |
> EMERGE_DEFAULT_OPTS="--quiet-build=n" |
80 |
|
81 |
This is redundant now, portage has gone back to the old method of |
82 |
spamming your screen with compiler output when using --jobs 1. |
83 |
|
84 |
|
85 |
-- |
86 |
Neil Bothwick |
87 |
|
88 |
Home is where you hang your @. |