On Mon, Sep 19, 2011 at 6:40 AM, bouleetbil <[email protected]> wrote: > Le Mon, 19 Sep 2011 13:21:25 +0200, > Miklos Vajna <[email protected]> a écrit : > >> On Mon, Sep 19, 2011 at 11:25:46AM +0200, bouleetbil >> <[email protected]> wrote: >> > When I update a box the "minimum" for me it's my system should start. >> > >> > Result frugalware don't boot => kernel panic. >> > I think we should patch menu.lst for add the initrd. >> >> Right, grubconfig does this. Do you have any better idea than the news >> entry on the website? > Perhaps add to post-install "WARNING WARNING you should update menu.lst ...". > I'me pretty sure that users will don't read the news. > And if it's not translate you don't see the news :)
I think bouleetbill is right in this case. We definately should have had such a warning. My grub wasn't even installed by the Frugalware I'm using so nothing could have modified it. I just realised that if it weren't for talking with ryuo on IRC I would have had a non-booting OS as well. So yes we definately should include this kind of notes to let users know what's going on. > >>Adding the initrd to the menu.lst automatically is >> too problematic, that's why the decision was made not to touch menu.lst >> from a post_upgrade scriptlet. > why problematic to update frugalware entry with sed into menu.lst ? > >> >> > I think we would bump, add some features too quickly and it's not >> > enought tested. The result (I talk for me and probably some users) >> > When I update my system I say what will be break with this update and >> > It's not normal. (When I've choose to use frugalware it's also for the >> > stability) >> >> I think your current problem is about a scriptlet did not touch >> automatically a config file - while usually we consider that a feature. > Ok >> So in this particular case I don't think it's about too less testing. > Perhpas but I'm not sure. For me it missing something but I don't know what. > >> Note that I actively try to control how much breakage do we have during >> upgrades for each release - i.e. it was intentional that I did not want >> dracut for 1.5, when we already caused enough problems for upgraders >> with systemd. > I know and I'm agree with that >> >> > Before bump add some features we should fix missing packages into >> > testsuite, ruby bump is not finish since some months some ruby pkg are >> > broken as deprecated rubygems... >> >> We already recommend doing such bumps in a WIP repo if it can't be >> finished within a workday. So as long as we create a WIP repo for such >> upgrades, it won't be a problem. >> >> To sum up: I understand your frustration, but I think that's the best we >> could do right now. Users not interested in testing should use stable, >> where we always publish an upgrade guide, that contains instructions on >> how to avoid a kernel panic on reboot. >> >> BTW, if you read the news entry, I hope current will be usable for you >> again. :) > In french I don't have this entry :D > > And current work here I was just irritate after updated a box for have a > kernel panic. > >> Thanks. > > _______________________________________________ > Frugalware-devel mailing list > [email protected] > http://frugalware.org/mailman/listinfo/frugalware-devel > _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
