Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-15 Thread John Clarke
On Wed, Jun 15, 2005 at 02:05:51 +1000, John Clarke wrote: > Hmm, I wonder if I can replace lesstif with openmotif. It looks like Well I couldn't do this directly because lesstif2 provides libXm.so.2 and libmotif3 provides libXm.so.3, but I could do it by removing lesstif-dev, installing libmoti

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread John Clarke
On Wed, Jun 15, 2005 at 01:44:36 +1000, Jeff Waugh wrote: > > > > > You're best off letting the MOTU team know by filing a bug in Malone > > > (launchpad.ubuntu.com). > > > > Do you think it's worth doing that now, or should I wait until I know > > whether it's a lesstif bug? > > It'll bring it

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread Jeff Waugh
> > You're best off letting the MOTU team know by filing a bug in Malone > > (launchpad.ubuntu.com). > > Do you think it's worth doing that now, or should I wait until I know > whether it's a lesstif bug? It'll bring it to the attention of more people, so worth doing now. You may also want to c

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread John Clarke
On Wed, Jun 15, 2005 at 11:11:05 +1000, Jeff Waugh wrote: > > > > 1. Download nedit-5.5-1 sources from Internode's Ubuntu mirror > > (nedit_5.5.orig.tar.gz and nedit_5.5-1.diff.gz). > > If you have deb-src lines in your sources.list, you can just "apt-get source > " too. Like I said before

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread Jeff Waugh
> 1. Download nedit-5.5-1 sources from Internode's Ubuntu mirror > (nedit_5.5.orig.tar.gz and nedit_5.5-1.diff.gz). If you have deb-src lines in your sources.list, you can just "apt-get source " too. > It didn't help though; the new package has the same problems as 5.4, and > both are almo

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread John Clarke
On Tue, Jun 14, 2005 at 07:25:36 +1000, Michael Chesterton wrote: > Do you know how to build breezy packages in hoary? I had no idea how to rebuild any debian/ubuntu packages from source, but I figured out a way: 1. Download nedit-5.5-1 sources from Internode's Ubuntu mirror (nedit_5.5.orig

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-14 Thread Michael Chesterton
John Clarke <[EMAIL PROTECTED]> writes: > Thanks. I did install a package from breezy (nedit-5.5 because the > nedit-5.4 in hoary is broken) so it looks like that was my problem. I'm > now trying again, this time building nedit-5.5 from source because the > nedit-5.5 binary from nedit.com doesn't

RE: [SLUG] Ubuntu kernel upgrade woes

2005-06-13 Thread Carlo Sogono
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Clarke > Sent: Friday, 10 June 2005 11:58 AM > To: slug@slug.org.au > Subject: [SLUG] Ubuntu kernel upgrade woes > > Hi all, > > Ubuntu released a new kernel yesterday, which I d

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-13 Thread John Clarke
On Fri, Jun 10, 2005 at 07:37:52 +1000, Michael Chesterton wrote: > > I don't know what happened in your situation, you might have been > > unlucky, or hit a bug. It usually just works. IIRC the kernel was upgraded when I did an 'apt-get upgrade' after the initial installation and it worked fine.

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-10 Thread Michael Chesterton
Michael Chesterton <[EMAIL PROTECTED]> writes: > John Clarke <[EMAIL PROTECTED]> writes: > >> You've probably guessed what happened next. Neither of the new kernels >> would boot -- the error was "VFS: Unable to mount root fs on unknown >> block (0,0)". I tried for about half an hour to fix it,

Re: [SLUG] Ubuntu kernel upgrade woes

2005-06-10 Thread Michael Chesterton
John Clarke <[EMAIL PROTECTED]> writes: > You've probably guessed what happened next. Neither of the new kernels > would boot -- the error was "VFS: Unable to mount root fs on unknown > block (0,0)". I tried for about half an hour to fix it, but without There are some kernel bugs I hit recently

[SLUG] Ubuntu kernel upgrade woes

2005-06-09 Thread John Clarke
Hi all, Ubuntu released a new kernel yesterday, which I duly installed with 'apt-get upgrade'. I'm used to keeping the old kernel in place until I've verified that the new one boots (rpm allows two different versions to be installed at the same time), but I couldn't figure out how to do that with