http://wiki.debian.org/DebianInstaller/Today: add two entries
On Wed, Mar 26, 2008 at 6:25 PM, Frans Pop <elendil@planet.nl> wrote:
> Yes, for the following reasons:
> 1) it is only likely to confuse other users
> 2) the breakage is mostly completely outside our control
> 3) listings would be highly unreliable because of the turnover speed of
> unstabe (we'd miss most issues and run the risk of issues not getting
> cleaned up when the are resolved)
> 4) installing sid directly really isn't that good an idea and _always_ has
> the risk of failure attached; just don't do it if you're unprepared to
> deal that
> > the system did not boot anymore – it did not ask for the passphrase as
> > before (both linux images failed (2.6.22 (updated) and 2.6.24
> > (installed)). (I did not look at /etc/crypttab after the dist-upgrade.
> > But it should not have changed.)
>
> That's a known issue with busybox that would also have hit you if you'd
> installed sid directly. Again more a reason to _not_ install sid directly
> than anything else.
> Downgrading busybox and rebuilding your initrd should fix it.
Wouldn't it be great idea though if there was an official Sid
netinstall at least, even if some of the packages are a little behind?
Perhaps something similar to the daily builds for d-i testing. I'd be
happy to help test it if someone wants to work at it.
Btw, I rebuilt d-i using sid packages and all went well using the
testing version of busybox.
Rage
Reply to: