Prev: Gnucash segfaults
Next: If you have a hardwood floor, times have changed.
From: Snood on 15 Mar 2010 19:20
Wayne wrote:
> Snood wrote:
>>>
>>> dpkg -l linux-image |grep ^i
>>>
>>> will show you that the version, -3, changed. The name did not.
>>>
>>> Wayne
>>>
>>>
>>
>> That command results in nothing at all on my system. Is that significant?
>>
> No, because, stupid me, forgot to type it correctly. Try this
>
> dpkg -l linux-image* |grep ^i
>
> The wildcard * tells it to check for all the linux-image files
> The |grep ^i means -- only show packages that have 'i' in the first
> column, which means show only the installed packages.
>
>
> This list code of conduct discourages sending personal mail. I am
> including the list in the cc so other users may benefit from your
> question. Please ask questions on the list and not directly to members.
>
> Thank you
>
> Wayne
>
>
Yes, sorry. I've got to get my head on straight today. I just joined
this list and forgot about the differences. Some mung, and some don't.

Output from dpkg -l linux-image* |grep ^i was:

ii linux-image-2.6.32-trunk-686 2.6.32-5
Linux 2.6.32 for modern PCs



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9EBE81.3000403(a)comcast.net
From: Snood on 15 Mar 2010 19:30
Wolodja Wentland wrote:
> On Mon, Mar 15, 2010 at 17:51 -0400, Snood wrote:
>> Stephen Powell wrote:
>>> Sam wrote:
>
>>> First of all, you replied to me personally instead of to the list.
>>> I'm putting this back on the list where it belongs.
>
> Same happened here.
>
>>> If you have already done the upgrade, you should have two kernel
>>> image packages installed: linux-image-2.6.32-3-<arch> and
>>> linux-image-2.6.32-trunk-<arch>. If you wish to purge the old
>>> kernel, shutdown and reboot first. This will cause the new kernel
>>> to be booted. Then you can purge the old one. aptitude will
>>> not let you purge or remove a running kernel.
>
>> I know about rebooting and purging. I've done it lots before. It's
>> not working that way in this case. Honestly. There's just no
>> evidence that I can find that there's more than one kernel to select
>> from. In fact, there's not even any evidence at all that there was
>> any kernel upgrade on the three machines that had the initial OS
>> installation done with the trunk kernel install option. On the other
>> system, I can see that a new linux-image package was installed. But
>> there's only one choice of kernels at boot time. And any attempt on
>> any of these systems to remove the "obsolete" kernel results in the
>> warning that the only kernel is being removed.
>
> It would be great, if you could provide us with the output of the
> following commands:
>
> # aptitude search ~i~n^linux-image
> # apt-cache policy linux-image-2.6.32-3-686
>
> It is quite likely that you have indeed two packages installed, namely
> linux-image-2.6.32-3-686 and linux-image-2.6.32-trunk-686. The latter
> is no longer present in the archives and therefore obsolete.
>
> We can see that linux-image-2.6.32-3-686 is in testing:
>
> $ rmadison linux-image-2.6.32-3-686
> linux-image-2.6.32-3-686 | 2.6.32-9 | testing | i386
> linux-image-2.6.32-3-686 | 2.6.32-9 | unstable | i386
>
> so you should have installed it. That assumes that you have a kernel
> meta-package installed, which depends on the current package that
> provides the newest kernel. That meta-package is probably
> linux-image-2.6-686.
>
> It has already been pointed out in this thread that this kernel
> update did, in contrast to previous updates, not select the kernel
> provided by linux-image-2.6.32-3-686 as default kernel for grub. I
> therefore think that the warning you get is not due to the fact that you
> have only one kernel installed, but rather that you are trying to remove
> the kernel *you are currently using*, because you booted into the "old"
> kernel.
>
> If you really have only one kernel package installed, I would suggest to
> install the aforementioned meta-package or linux-image-2.6.32-3-686,
> reboot and remove/purge linux-image-2.6.32-trunk-686. Please provide the
> complete output of any command that gives errors.

Output of
# aptitude search ~i~n^linux-image
is
i linux-image-2.6.32-trunk-686 - Linux 2.6.32 for modern PCs

Output of
# apt-cache policy linux-image-2.6.32-3-686
is
linux-image-2.6.32-3-686:
Installed: (none)
Candidate: 2.6.32-9
Version table:
2.6.32-9 0
500 http://ftp.us.debian.org squeeze/main Packages

Thank you. I'm sorry about mixing up my replies. I'm new here and have
been used to working with lists which mess around with the reply to
behavior.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9EC0EC.5000703(a)comcast.net
From: Wolodja Wentland on 15 Mar 2010 19:40
On Mon, Mar 15, 2010 at 19:21 -0400, Snood wrote:

> Output of
> # aptitude search ~i~n^linux-image
> is
> i linux-image-2.6.32-trunk-686 - Linux 2.6.32 for modern PCs

Ok - You really have only one linux-image-* package installed and you've
installed it directly, i.e. it was not installed as a dependency of a
meta-package.

> Output of
> # apt-cache policy linux-image-2.6.32-3-686
> is
> linux-image-2.6.32-3-686:
> Installed: (none)
> Candidate: 2.6.32-9
> Version table:
> 2.6.32-9 0
> 500 http://ftp.us.debian.org squeeze/main Packages

Very Good. I would suggest that you install linux-image-2.6-686 or
linux-image-686, which depend on linux-image-2.6.32-3-686. That way you
will get kernel updates in the future and don't run into this mess
again.

You can then reboot into the new kernel and remove the obsolete
linux-image-2.6.32-trunk-686 package.

> Thank you. I'm sorry about mixing up my replies. I'm new here and
> have been used to working with lists which mess around with the
> reply to behavior.

You might also want to trim your posts and interleave your answers.
Welcome to the list. :)

--
.''`. Wolodja Wentland <wentland(a)cl.uni-heidelberg.de>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
From: Snood on 15 Mar 2010 20:10
Wolodja Wentland wrote:

> Ok - You really have only one linux-image-* package installed and you've
> installed it directly, i.e. it was not installed as a dependency of a
> meta-package.

Yes, I think I understand. I used a netinst disc to install the
operating system. In Lenny installed via netinst I got kernel updates.
Does it not work that way in Squeeze?

> Very Good. I would suggest that you install linux-image-2.6-686 or
> linux-image-686, which depend on linux-image-2.6.32-3-686. That way you
> will get kernel updates in the future and don't run into this mess
> again.

> You can then reboot into the new kernel and remove the obsolete
> linux-image-2.6.32-trunk-686 package.

Thank you. I did this, rebooted into the new kernel, used aptitude to
remove the old one, and removed the obsolete kernel. Everything is
ticking along nicely.

> You might also want to trim your posts and interleave your answers.
> Welcome to the list. :)

Yes, I should have known that, too. I read it when I joined initially,
and then got rushed whilst trying to do several things at once.

Thank you for the welcome. And thank you for the very good advice.

Best regards,
Sam


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9ECBE2.1030603(a)comcast.net
From: Frank McCormick on 15 Mar 2010 23:30
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 15 Mar 2010 19:16:32 -0400
Celejar <celejar(a)gmail.com> wrote:

> On Mon, 15 Mar 2010 19:05:04 -0400
> Frank McCormick <debianlist(a)videotron.ca> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Mon, 15 Mar 2010 17:39:01 -0400 (EDT)
> > Stephen Powell <zlinuxman(a)wowway.com> wrote:
>
> ...
>
> > > to be booted. Then you can purge the old one. aptitude will
> > > not let you purge or remove a running kernel.
> >
> >
> > Uummm...yes it will. I have done it :( accidentally. What a
> > PAIN!
>
> Not sure how you could have done it by accident - aptitude warns you
> thus:
>
> -----
>
> You are running a kernel (version 2.6.34-rc1-lizzie-00005-g522dba7)
> and attempting to remove the same version. This is a potentially
> disastrous action. Not only


Yes. most of us probably know what the warning says. Guess you've
never done anything accidentally. Can you also walk on water :)




- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLnvk+AAoJEMEDyLTvrVhj5TAH/jtM9caTWRoEho0Wv8nkFSuj
YGwL8LpKkheRa+d0NA3Q1bJXzfPGjF8iMI3EUpz+xja1pHUYGrK9FWDPSrteSqXM
LULnKGm8+aT2BpCYD6uT+eyghwLBczZBjs1eRSSU0Ak/JcHwvEXNJdmY03MssZpp
Mrna7MHOA+NL/iZvIfBKzmcc5RJoBonNi2vCyr9eTI4OJZFyHL3Lx3qrb4wTjYu+
MR8nAiMWQWoWnbebBHzcMAIaq64vlLQ7SZ8FyliG4bKN0KKrGRAmKMXjVhCGHtrG
WYjPTfgQAFnMMD5ZErbNmHLuNSg5CzHcLN2wDlu4OR6cAYTygL/a161GX3ADqTs=
=qAwy
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100315232134.3cc260ca.debianlist(a)videotron.ca
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Gnucash segfaults
Next: If you have a hardwood floor, times have changed.