Re: Release of Stable Etch
On Wednesday 14 February 2007 17:18, Andrew Sackville-West wrote:
> On Thu, Feb 15, 2007 at 12:13:08AM +1030, Stef Daniels VK5HSX wrote:
> > After trying a Sarge to Etch update, I had to redo again, making sure I
> > upgraded to udev a 2.6.12 (or higher) kernel prior to doing an apt-get
> > dist-upgrade. It does fall over due to the changeover to udev and
> > troubles using a 2.6.8 kernel. Upon doing that, it worked a treat..
>
> did you file an installation report? This is going to be a critical
> issue in the upgrade path and if its not working right yet, the dev's
> need to know.
>
> that said, I've done 2 or 3 sarge -> etch upgrades without any
> problems at all, but they were on a fresh install of sarge (lost my
> etch disk...).
>
> A
Where do you file the installation reports Andrew?
All my 3 current Debian installs were originally installed from Woody 3.0r2
cdroms, using the 2.4 bf kernel. Then installed the 2.4.27 kernel to try and
get some sounds working. Sarge was still in testing at the time. I changed
the /etc/apt/sources.list to point to Sarge. IIRC the first Woody upgraded to
Sarge had a problem, where during the upgrade The Xserver was shutdown, and I
had to continue the upgrade in text mode. The second Woody upgraded didn't
have this problem, but it was some time later on. Sarge was Stable when I did
the third Woody to Sarge upgrade, this upgrade went with no problems. Changed
the sources to point to testing, and until about 3 weeks ago was my only Etch
install. Sources on this one are now pointing to Etch, and there are still
loads of updates coming in. 152MB, 91 packages only a couple of days ago.
This Etch install will go back onto testing when Etch goes stable, then I'll
be going into unknown Lenny territory.
The Sarge to Etch upgrade I did about 3 weeks ago went like clockwork. Booted
with the 2.6.8 kernel, and went for it. I'm on dialup, and with 900+ upgraded
packages, 300+ newly installed packages, and a bunch to be removed it took
some time to DL them. I think there were about 694MB of packages to DL.
Thankfully I had loads of them available in /var/cache/apt/archives for the
current Etch install, so about 12hrs of downloading fetched the packages that
I didn't have. Another 4+ hrs to unpack, prepare, and set them up. Thankfully
I didn't lose the power during the package upgrade stage. I can deal with
losing the power during downloading. apt-get dist-upgrade just picks up where
it left off, and I'm constantly amazed as to how it does this.
Upgrade finished, and not having rebooted yet (was probably putting it off) I
installed the 2.6.17 kernel. That was a bad move, and due to something I'd
forgotten about, those darned vmlinuz, and initrd.img softlinks in / .
Rebooted with trepidation, and neither the 2.6.8, or the 2.6.17 kernel would
boot, claiming "no files found". It's late now, and I'm thinking, yeh, this
is just great. So now I'm booting my new Sarge to Etch upgrade with the
2.4.27 kernel, which thankfully boots up the system. It's late, and can't
think what's gone wrong with the 2.6.8 kernel, since I installed the 2.6.17
one. Shutdown. Go to bed.
Another new day, and I gradually realise the problem. The softlinks in / .
A quick trip with a text editor into /etc/lilo.conf, changed the initrd lines
for the 2.6.8, and 2.6.17 kernels from /initrd.img to /boot/initrd.img, and
all kernels were up and running again.
I have no complaints about the upgrade from Sarge to Etch, as it went like
clockwork. The kernel problem was my fault, and am gratefull that I still had
the 2.4.27 one.
I also have Fedora Core versions that run on this machine, and have seen loads
of problems with upgrades. I've never upgraded a Fedora core version. I've
always done fresh installs, and currently have FC1, 2, 3, 4, and 5 installed.
FC1 through 4 are no longer supported, but I don't like getting rid of old
faithfulls. I'm sending this reply from FC2, and Etch is running on the other
machine.
As far as upgrades go though, I have no complaints with Debian. Apart from the
odd glitch they have gone well.
Looking forward to the Lenny experience when Etch goes stable.
Nigel.
Reply to: