<div class="gmail_quote">On Mon, Jan 26, 2009 at 3:15 PM, Joshua Kite <span dir="ltr"><<a href="mailto:jwkite@gmail.com">jwkite@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote">2009/1/26 Michael B. Trausch <span dir="ltr"><<a href="mailto:mike@trausch.us" target="_blank">mike@trausch.us</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">
<div>On Sun, 25 Jan 2009 21:42:55 -0500<br>
Joshua Kite <<a href="mailto:jwkite@gmail.com" target="_blank">jwkite@gmail.com</a>> wrote:<br>
<br>
> I have a machine that had Ubuntu Feisty on it. I needed to add some<br>
> packages when I realized the shortcomings of not keeping a distro<br>
> current; the Feisty packages have been archived because it is no<br>
> longer supported. Long story short, I ultimately ended up changing<br>
> the sources.list file to point to Hardy and managed to mostly get the<br>
> box upgraded. However, I continually had issues apt installing<br>
> linux-generic and other kernel-related packages. I had run in to<br>
> dependency hell.<br>
<br>
</div>The problem here is that you skipped from Feisty to Hardy. Probably<br>
the best bet would have been to upgrade from Feisty (7.04) to Gutsy<br>
(7.10), and then to Hardy (8.04).<br>
<br>
Officially speaking, Ubuntu's upgrading infrastructure only supports<br>
upgrading from one release to the next immediate release; the only<br>
exception for that is from LTS to LTS. For example, users of Dapper<br>
did not have to upgrade from Dapper to Edgy to Feisty to Gutsy to<br>
Hardy. They were able to skip Edgy, Feisty, and Gutsy altogether and<br>
just upgrade directly to Hardy. When the next LTS comes out, Hardy<br>
will be able to upgrade directly to it, as well.<br>
<br>
I don't suppose that there is probably a way to revert the packages to<br>
the state that they were in before you started with this. Given that,<br>
I would wipe the drive and install Intrepid. :-P<br>
<br>
You mentioned 2.2 kernels. I don't know what you're referring to,<br>
there; Ubuntu uses the 2.6 series and has all the way back to Ubuntu<br>
4.10, the very first release (which used Linux 2.6.8 for its kernel).<br>
<br>
Could you provide some extra data? If you could pastebin the following<br>
files:<br>
<br>
/boot/grub/menu.lst<br>
/var/log/apt/term.log [Only starting from the upgrade]<br>
<br>
Also, the output of the following commands will be useful:<br>
<br>
ls -ld /boot/*<br>
dpkg -l<br>
<br>
I mentioned pastebin because some of these are going to be quite<br>
lengthy and shouldn't be on-list. I'd recommend pasting them there and<br>
then providing links here.<br>
<br>
--- Mike<br>
<font color="#888888"><br>
--<br>
My sigfile ran away and is on hiatus.<br>
<a href="http://www.trausch.us/" target="_blank">http://www.trausch.us/</a><br>
</font><br></div></div><div class="Ih2E3d">_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></div></blockquote></div>Mike,<br><br>Thanks for the help. After a good night's sleep, I have booted via livecd and chrooted into my system. Just to cover all the bases, my system has / /boot /home /usr and /var on different partitions, and I mounted all of those before chrooting.<br>
<br>I have used apt-get to remove all linux images and similar packages. My goal at this point is to install the linux-server package, although I would be content with any working kernel at this point.<br><br>Per your request, here are the files you asked for (and thanks, btw, for introducing me to pastebin):<br>
<br>/boot/grub/menu.lst <a href="http://pastebin.com/m27055ad2" target="_blank">http://pastebin.com/m27055ad2</a><br><br>/var/log/apt/term.log (starting after the upgrade got the machine stable but before I ended up removing the kernel) <a href="http://pastebin.com/m76ada55f" target="_blank">http://pastebin.com/m76ada55f</a><br>
<br><br>ls -ls /boot/* <a href="http://pastebin.com/m75fd2534" target="_blank">http://pastebin.com/m75fd2534</a><br>dpkg -l <a href="http://pastebin.com/m16834573" target="_blank">http://pastebin.com/m16834573</a><br><br>
When I attempt the following:<br>
sudo apt-get install linux-server I receive the following: <a href="http://pastebin.com/d5ff8059f" target="_blank">http://pastebin.com/d5ff8059f</a><br><br>The part that confuses me are the last five lines:<br><br> 1.<br>
Errors were encountered while processing:<br>
2.<br> linux-image-2.6.24-23-server<br> 3.<br> linux-ubuntu-modules-2.6.24-23-server<br> 4.<br> linux-image-server<br> 5.<br><br> linux-server<br><br>How does one go about resolving dependency problems when attempting to install the kernel???<br>
<br>Thanks Mike and anyone else for your help.<br><br>Josh Kite<br><br>
</blockquote></div><br><br>As an update - it looks like the upgrade caused grub to be uninstalled. The result was that the update-grub script didn't exist, causing the kernel updates configurations to fail. I have re-installed grub and apt-get is no longer throwing errors. I'm about to reboot to see what happens.<br>
<br>This is one of those processes where I have learned a lot, but I do not want to repeat.<br><br>I'll post the results and any additional lessons learned. Lesson one - keep Ubuntu systems current.<br><br>Josh Kite<br>