1 |
I see your point |
2 |
|
3 |
Here's /etc/fstab |
4 |
----------------------- |
5 |
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. |
6 |
/dev/hda1 /boot reiserfs |
7 |
noauto,noatime,notail 1 1 |
8 |
/dev/hda7 / reiserfs noatime |
9 |
0 0 |
10 |
/dev/hda6 none swap sw |
11 |
0 0 |
12 |
/dev/hda5 /tmp reiserfs noatime |
13 |
0 0 |
14 |
/dev/hda2 /home reiserfs noatime |
15 |
0 0 |
16 |
/dev/cdrom /mnt/cdrom iso9660 noauto,ro,users |
17 |
0 0 |
18 |
/dev/fd0 /mnt/floppy auto noauto,users |
19 |
0 0 |
20 |
proc /proc proc defaults |
21 |
0 0 |
22 |
----------------------- |
23 |
|
24 |
lilo.conf has |
25 |
|
26 |
---------------------- |
27 |
image = /boot/bzImage |
28 |
root = /dev/hda7 |
29 |
label = Gentoo |
30 |
---------------------- |
31 |
|
32 |
Also, note that |
33 |
|
34 |
------------------------- |
35 |
yababa root # /sbin/lilo -t |
36 |
Fatal: open /boot/bzImage: No such file or directory |
37 |
yababa root # |
38 |
------------------------- |
39 |
|
40 |
If the root for boot was changed, lilo should have found the /boot/bzImage. |
41 |
|
42 |
Also, I did |
43 |
|
44 |
--------------------------- |
45 |
yababa root # find / -name bzImage |
46 |
/usr/src/linux-2.4.19-gentoo-r9/arch/i386/boot/bzImage |
47 |
/usr/src/linux-2.4.19-gentoo-r10/arch/i386/boot/bzImage |
48 |
yababa root # |
49 |
---------------------------- |
50 |
|
51 |
I am not sure where is the /boot/bzImage that shows up in the lilo.conf file. |
52 |
|
53 |
Appreciate help. |
54 |
Regards |
55 |
Pete |
56 |
|
57 |
------------------------- |
58 |
|
59 |
|
60 |
|
61 |
On Sun, 26 Feb 2006 18:02:07 -0600, "Boyd Stephen Smith Jr." |
62 |
<bss03@××××××××××.net> wrote : |
63 |
|
64 |
> On Sunday 26 February 2006 17:51, "Pete" <pi2list@×××××××.com> wrote about |
65 |
> '[gentoo-user] system boot': |
66 |
> > This is what I don't understand |
67 |
> > |
68 |
> > ------------------ |
69 |
> > |
70 |
> > yababa root # ls -l /boot/ |
71 |
> > total 1272 |
72 |
> > -rw-r--r-- 1 root root 483904 Feb 26 04:56 |
73 |
> > System.map-2.4.19r10AR lrwxrwxrwx 1 root root 1 Jan 12 |
74 |
> > 2003 boot -> . -rw-r--r-- 1 root root 814688 Feb 26 04:40 |
75 |
> > bzImageAR yababa root # |
76 |
> > |
77 |
> > --------------------- |
78 |
> > |
79 |
> > boot points to itself. |
80 |
> |
81 |
> That's pretty standard. From my system: |
82 |
> |
83 |
> # mount /boot |
84 |
> # ls /boot/boot -l |
85 |
> lrwxrwxrwx 1 root root 1 Jan 30 10:46 /boot/boot -> . |
86 |
> # umount /boot |
87 |
> # ls /boot -l |
88 |
> total 0 |
89 |
> lrwxrwxrwx 1 root root 1 Aug 6 2005 boot -> . |
90 |
> drwxr-xr-x 2 root root 80 Jan 31 09:29 grub |
91 |
> |
92 |
> Not really sure why that grub directory is in there... |
93 |
> |
94 |
> > Before I copied the System.map-2.4.19r10AR and |
95 |
> > bzImageAR, there was nothing in there. |
96 |
> > |
97 |
> > How does the system boot? ? ? |
98 |
> |
99 |
> Could boot be on a separate partition? Check /etc/fstab. |
100 |
> |
101 |
> -- |
102 |
> "If there's one thing we've established over the years, |
103 |
> it's that the vast majority of our users don't have the slightest |
104 |
> clue what's best for them in terms of package stability." |
105 |
> -- Gentoo Developer Ciaran McCreesh |
106 |
> -- |
107 |
> gentoo-user@g.o mailing list |
108 |
> |
109 |
> |
110 |
> |
111 |
> |
112 |
-- |
113 |
gentoo-user@g.o mailing list |