386 to 686 updating

[Bill Christiansen]

It wont do any harm just to leave the 386 kernel there and it will give
you an extra option to boot in grub just in case something goes wrong
with the 686 kernel. This happened to me when I tried to install a bad
homemade deb that messed up my 686 modules directory. I was able to go
back to booting the 386 version until I had a chance to fix it properly.
Bill
On Fri, 2004-12-03 at 14:34 +0000, jp wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> pol wrote:
> | On Fri, 03 Dec 2004 14:01:57 +0000, jp <jaypee at hotpop.com> wrote:
> |
> |
> |>I had to recompile that lufs module for 686. But that was it. 686 works
> |>a lot faster. I was suprised by how much.
> |
> |
> | now i am even more confused!
> |
> | okay. i get all the terminal stuff, but the line above: i don't know
> | ANYTHING about recompiling a file in linux. if i just uninstall all
> | that stuff in terminal then ask synaptic to update everything do you
> | think it would catch the 686 lufs module and add it in?
> |
> | mulata
> |
> 
> I just needed that module for my own work. If you are currently running
> a 686 build you don't need to worry about it.
> 
> Sorry to confuse the matter that way.
> 
> In the future you might find you want functionality that is not
> supported in the default kernel. That's when you need to worry about
> modules.
> 
> if you open a terminal and type
> 
> # uname -r
> 
> and get something like this
> 
> 2.6.8.1-3-686
> 
> you are running a 686 kernel you can remove the 386 stuff without fear.
> 
> 
> 
> - --
> jp
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFBsHltc4kjKy6rlhMRAnKjAJ0QI8Wtps5KQx/yFYL7GP6shROwrACgq7P8
> 1CEvWwCl8MyscWZyyCm9irk=
> =ddLG
> -----END PGP SIGNATURE-----
> 
>