[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Kernel 2.2.10] Mount complains about msdos-drive



Andrei Ivanov <c680789@showme.missouri.edu> writes:

[...]

> To remove the kernel: do you have the old kernel laying around in /boot as
> a backup boot option? Then just boot it instead of 2.2.10.
> If not, just install the 2.0.* kernel with dselect and boot into it.

My /boot looks like this:
-rw-r--r--   1 root     root       256016 Jun 15 16:28 System.map-2.2.10
-rw-r--r--   1 root     root          512 Jun 11  1998 boot.0307
-rw-r--r--   1 root     root         4540 Feb 21 19:19 boot.b
-rw-r--r--   1 root     root         4540 Feb  2 18:31 boot.b.preserved
-rw-r--r--   1 root     root          612 Feb 21 19:19 chain.b
-rw-r--r--   1 root     root          612 Feb  2 18:31 chain.b.preserved
-rw-r--r--   1 root     root        17110 Jun 15 14:31 config-2.2.10
-rw-------   1 root     root         4096 Jul 31 18:53 map
-rw-r--r--   1 root     root          444 Apr  7 17:22 mbr.b
-rw-r--r--   1 root     root          620 Feb 21 19:19 os2_d.b
-rw-r--r--   1 root     root          620 Feb  2 18:31 os2_d.b.preserved
-rwxr-xr-x   1 root     root       696125 Jun 11  1998 vmlinuz-2.0.33*
-rw-r--r--   1 root     root      1009326 Jun 15 16:28 vmlinuz-2.2.10

/etc/lilo.conf:
boot=/dev/hda7
root=/dev/hda7
compact
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20
image=/vmlinuz
label=Linux
read-only

Uses the half os' boot manager.


Since I'm still a bit green I do not know which files the kernel needs
etc. I AFAICT the *.preserved should be copied back to get to 2.0.33
but shouldn't there be a System.map.preserved and a map.preserved?

I could use a 2.0.35 from dselect but thought I could take the chance
when I have it and get some knowledge about the working of the kernel.

Any good urls, btw?

-- 
( Jonas Steverud  @  www.dtek.chalmers.se/~d4jonas/ !    Wei Wu Wei    )
( U2MoL, Roleplaying, LaTeX, Emacs/Gnus, SCWM, etc. ! To Do Without Do )


Reply to: