Re: possible move to unstable..
> c) Upgrade to Woody(testing). Woody is the new "in-between"
> distribution, which is supposed to be more stable then Sid. For
> instance, the broken LILO package never made it into Woody.
This is getting away from the thread's original subject, but the new
lilo package that did make it into woody (21.6-2) *is* broken as far as
I'm concerned. It replaces your /etc/lilo.conf with it's own (wrong)
idea of what should be there, even if you cancel out of the
configuration. That's very bad form.
Here's my /etc/lilo.conf before upgrading to lilo 21.6-2:
boot=/dev/hdc9
root=/dev/hdc9
install=/boot/boot-menu.b
map=/boot/map
lba32
prompt
timeout=100
vga=5
delay=50
read-only
verbose=2
default=linux2218.2
image=/boot/bzImage240.2
label=linux240.2
image=/boot/bzImage240.1
label=linux240.1
image =/boot/zImage2218.2
label=linux2218.2
And here's what I had afterwards:
boot=/dev/hdc9
root=/dev/hdc9
compact
install=/boot/boot.b
delay=20
map=/boot/map
append=""
read-only
image=/vmlinuz
label=Linux
image=/vmlinuz.old
label=old
The only saving grace is that it does save your old file by renaming it.
Time for a bug report, although I suspect this one is already reported.
Tom
"David B. Harris" wrote:
>
> To quote Marcial Zamora III <chic0@msdelta.com>,
> # hey all.. I know this mite stir up a great deal of debate, but its not
> my intention.. Im currently running potato, and thinking bout running
> unstable.. there are quite a few packages I would like to have in
> unstable, and I know ahead of time, to successfully install those
> packages, there are others in the same directory tree that I would
> need.. from wut I have seen in the entries in the mailing list so far,
> unstable is not really that *unstable*. The only real concern I think I
> would have is the move from Xfree86 3.3.6 to 4.0.2.. any of you guys
> have any input on this ? or any recommendations as to wut to do ahead of
> time, before I decided to go with a dist-upgrade ? to all who respond, I
> thank you in advance =)
>
> Well, there are a few things you can do;
>
> a) Add a deb-src entry in sources.list pointing to unstable, then
> 'apt-get source <package that you want>', then go into the newly created
> directory and(as root) 'dpkg-buildpackage -uc -b'. That'll give you a
> nice binary .deb built for your platform. This isn't guaranteed to
> work(since you're compiling a Sid package on a Potato machine), but it's
> always worked for me.
> b) Upgrade to Sid(unstable). It runs fine on my machine, but there are
> two things you should worry about: the upgrading process itself seems to
> be touchy - so you might run into trouble there. If you jump that hurdle
> though, you're probably set. The second thing is that you should be
> familiar with system recovery. For instance, a new LILO package was
> uploaded to Sid recently, and it made more than one machine unbootable.
> So, you should be able to restore things on your own. Also keep backups.
> :) Also, if something breaks, people are much less likely to sympathize
> with you, since you're running Sid(unstable), and you should know better
> ;)
> c) Upgrade to Woody(testing). Woody is the new "in-between"
> distribution, which is supposed to be more stable then Sid. For
> instance, the broken LILO package never made it into Woody. This is what
> I suggest to most people who ask about the different versions.
> Woody/testing is a nice compromise - you get relatively up-to-date
> packages, and your system isn't nearly as likely to die because of it.
> Currently, Woody is using XFree86 3.3.6, so if you upgrade to Woody, you
> won't need to worry about 4.0.2 yet. Hopefully, by the time 4.0.2 gets
> into Woody, a nicer setup program will exist(since the 3.3.6 and 4.0.2
> config files are vastly different). Right now, there's 'xf86config',
> which is an admirable stop-gap measure, but it's not right for at least
> 60% or the users out there.
>
> David Barclay Harris, Clan Barclay
> Aut agere, aut mori. (Either action, or death.)
>
> --
Reply to: