<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Intall GRUB as boot loader. Is much more automatic.<br>
<br>
For what I understand from your message you are installing the kernel,
but not updating the boot loader. What are you using if is not LiLO? If
it was GRUB it would add automatically the new kernel as default.<br>
<br>
Try installing GRUB, is much more advanced :-)<br>
<br>
Marcos<br>
<br>
<br>
Bret Busby escribió:
<blockquote cite="midPine.LNX.4.64.0703011625010.1654@localhost"
type="cite">On Fri, 23 Feb 2007, Marcos Raul Carot Collins wrote:
<br>
<br>
<blockquote type="cite">Date: Fri, 23 Feb 2007 19:31:06 +0900
<br>
From: Marcos Raul Carot Collins <a class="moz-txt-link-rfc2396E" href="mailto:marcos.carot@gmail.com"><marcos.carot@gmail.com></a>
<br>
Reply-To: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
Subject: Re: [plug] Two questions about Debian system and upgrading
<br>
<br>
Debian only updates automatically minor versions of the kernel
(usually!).
<br>
<br>
Search in Synaptic for "linux-image" and you will find all the
available
<br>
official kernels for sarge.
<br>
<br>
Happy weekend!
<br>
<br>
Marcos R. Carot Collins
<br>
Murdoch University Field Support (Rockingham)
<br>
<br>
Shannon Carver escribió:
<br>
<blockquote type="cite">Hi Bret,
<br>
<br>
Okey, firstly, if you're referencing "Stable" repositories in your
<br>
/etc/apt/sources.list, I'm pretty sure that's the only thing you have
to
<br>
change to switch between stable/unstable/testing. The message you see
<br>
at login prompt will merely be the message stored in /etc/profile, or
<br>
/etc/motd, or /etc/welcome (I can't remember for the life of me where
<br>
it's kept). It may even be in /etc/defaults/version or something like
<br>
that, a google should provide an answer.
<br>
<br>
Doing a synaptic update should do everything apart from the latest
<br>
kernel module, you'll have a -kernel or similar in your
<br>
/etc/apt/apt.conf which tells it to ignore kernel updates. I'm not
sure
<br>
how good you are with kernel building, but I'd either be getting the
<br>
kernel sources from kernel.org and building it yourself, or remove the
<br>
-kernel directive from apt sources and attempt to update to the latest
<br>
debian kernel. I remember installing sarge with an early 2.6.x kernel,
<br>
so you should be able to upgrade straight to that tree, the benefits
are
<br>
usually noticeable.
<br>
<br>
Regards
<br>
<br>
Shannon
<br>
<br>
Bret Busby wrote:
<br>
<br>
<blockquote type="cite">I am running Debian Linux on my desktop
computer, as a workstation.
<br>
<br>
At the login prompt, it says
<br>
"Debian GNU/Linux testing/unstable".
<br>
<br>
In the /etc/apt/sources.list file, is
<br>
"
<br>
deb <a class="moz-txt-link-freetext" href="http://ftp.uwa.edu.au/mirrors/linux/debian/">http://ftp.uwa.edu.au/mirrors/linux/debian/</a> stable main contrib
<br>
non-free
<br>
deb <a class="moz-txt-link-freetext" href="http://ftp.wa.au.debian.org/debian/">http://ftp.wa.au.debian.org/debian/</a> stable main contrib non-free
<br>
<br>
deb <a class="moz-txt-link-freetext" href="http://security.debian.org/">http://security.debian.org/</a> stable/updates main contrib non-free
<br>
".
<br>
<br>
ls -l shows that the file is as it is, since 2007-01-01.
<br>
<br>
Updates have been performed, using Synaptic.
<br>
<br>
The first question is, how do I convert the system to Debian stable
<br>
(sarge)? As the sources are from stable, the installed packages should
<br>
now be mostly packages that would be in the stable version.
<br>
<br>
The second issue relates to the kernel. The kernel version appears to
<br>
be 2.4.18-bf2.4 .The CPU is a Duron 1100, for which I believe that the
<br>
installed kernel is not the latest version.
<br>
<br>
Is it possible to update the kernel, without having to build a kernel
<br>
package? If so, how? I cannot find how to update the kernel, without
<br>
having to build a kernel package, in any of the documentation. When I
<br>
previously used Red Hat 7.2 (which was from before Red Hat went like
<br>
Microsoft), the update facility would update the kernel (although,
<br>
each time, I would have to manually update the file that pointed to
<br>
the kernel), but Synaptic won't do it.
<br>
<br>
Thanks in anticipation.
<br>
<br>
--
<br>
Bret Busby
<br>
Armadale
<br>
West Australia
<br>
..............
<br>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
Hello, Marcos.
<br>
<br>
Unfortunately, that does not seem to work.
<br>
<br>
When I log in to the computer, at a console (>CTRL> <ALT>
<Fx>), in the line after the "Last Login" information, is
<br>
"Linux <computer name> 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST
2002 i686 GNU/Linux".
<br>
<br>
So, I assume that the kernel is the x686 version.
<br>
<br>
In Synaptic, in the kernel packages, is kernel-image-2.6-686 , which
has the blurb:
<br>
"Linux kernel image for version 2.6 on PPro/Celeron/PII/PIII/P4.
<br>
This package will always depend on the latest 2.6 kernel image
available for Pentium Pro/Celeron/Pentium II/Pentium III/Pentium 4."
<br>
<br>
So, I selected that to install.
<br>
<br>
The Synaptic history shows:
<br>
"Commit Log for Thu Mar 1 15:17:54 2007
<br>
<br>
<br>
Installed the following packages:
<br>
kernel-image-2.6-686 (101sarge1)
<br>
kernel-image-2.6.8-3-686 (2.6.8-16sarge6)
<br>
module-init-tools (3.2-pre1-2)
<br>
" .
<br>
<br>
The module-init-tools was a dependency.
<br>
<br>
When Synaptic was doing the setup or configuration of the packages, it
came up with a message, with instructions, to the effect that it would
not work unless LILO was modified.
<br>
<br>
It said that to configure LILO, I needed to "add an 'initrd=/initrdimg'
to the image=/vmlinuz stanza of /etc/lilo.conf .
<br>
<br>
It also said that I need to put "do_initrd = Yes" in
/etc/kernel-img.conf , to avoid the message recurring whenever a kernel
is updated.
<br>
<br>
I followed those instructions, and continued with the update/upgrade,
and rebooted.
<br>
<br>
I did not run LILo, as the message from Synaptic (I think I saw it
there), said to only run LILO, if Linux was the only operating system,
and this computer is dual booting, into Windows XP and Linux. Also, In
the Syaptic dialogue, there were two prompts - the first was whether to
reun LILO, and the second was whether to create a new boot image. From
what I understand, both were recommended against, as I am running a
dual boot system, so I did not do either.
<br>
<br>
>From /var/log/messages:
<br>
"Mar 1 15:46:40 localhost kernel: Linux version 2.4.18-bf2.4
(root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Son
Apr 14 09:53:28 CEST 2002"
<br>
<br>
I then, in the boot sequence, got the message "udev needs a kernel
>= 2.6.8 so will not be loaded" (or something like that), and "HAL
needs a kernel later than 2.6 so will not be loaded", or something like
that, and both of these lines, while displayed during the boot
sequence, are not included in /var/log/messages .
<br>
<br>
Anyway, after having supposedly installed and set up the kenel image
2.6.8-3-686, it does not load on bootup, and I remain with the kernel
that, as I have just realised when putting the information together for
this message, predates the release of Debian Linux 3.1, or, sarge, as
stable, and is apparently, almost 5 years old.
<br>
<br>
--
<br>
Bret Busby
<br>
Armadale
<br>
West Australia
<br>
..............
<br>
<br>
"So once you do know what the question actually is,
<br>
you'll know what the answer means."
<br>
- Deep Thought,
<br>
Chapter 28 of Book 1 of
<br>
"The Hitchhiker's Guide to the Galaxy:
<br>
A Trilogy In Four Parts",
<br>
written by Douglas Adams,
<br>
published by Pan Books, 1992
<br>
<br>
....................................................<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a>
</pre>
</blockquote>
<br>
</body>
</html>