On Mon, Oct 31, 2005 at 03:00:39AM +0100, Christian Müller wrote: > > >That is beside the point. The miboot stuff wasn't included for legal > >reasons, > >and i don't even understand why it was included in woody. > > > Yep, remember reading that somewhere - would it be possible to take the > NetBSD code producing ofwboot.xcf, legal-wise or is it also unfree in > the debian terms?
No idea of what that even is, could you describe it and provide a pointer to it ? That said it has been rumored that it may be possible to scratch the non-free bit of the boot sector and that it will then just work, but despite my repeated calls for testing this, nobody has still come out and tried it over the paste year or so. > >If you had bothered to check the mailing list archive of both debian-boot > >and/or debian-powerpc, you would have noticed numerous posts about this > >selfsame issue going back over a year, please go and read them, and then > >appreciate the rather consequent work we all invested in this issue for > >mostly > >old and obsolet hardware nobody uses anyway, and then i expect you to show > >a > >bit more humility next time. What have you done yourself, downloaded a > >couple > >of floppies without even investigating the issues, and made wild claims ? > > > > > You were talking about attitude - "numerous posts" about this don't come > from nowhere, they alone should proove that it's in use by people. Let Well, indeed 5-10 people, but the point there is that i have been trying as best i could to support oldworld, and if it had not been for me driving this discussion, and the work i have invested, as well as a few others over the years, there would be no miboot floppies at all, so your critics of use being lazy and irresponsible and not doing proper testing was very badly received. > alone those, that do not report their successes and failures. I > actually do have read tons of posts and yes, there is this selfsame > issue coming up once in a while with other beings getting frustrated of > apple's bugs and their refusal to provide documentation for the specific > macosrom (and the subsequent kludges, legal+technical, developers have > to use to make it work anyway). And now fixed. These issues don't fix themselves, you know ? > I don't see the point in shutting people up that have to plain say > what's wrong -and I did nothing more. There is no template for writing Nope, you implied we did sup-par work on the miboot floppies, and this is the problem, and the result didn't lieve up to your expectations and you blamed us for it. > polite emails (well, maybe file a clean and sterile bug-report) and what > is usual tone for some might get other people started. What do you > want? You have my respect, but I will not gracefully bow in front of > you or wrap my plain words in flowers. A lot of testers have probably > been in my situation before, either giving up or kissing the ring. Just be constructive in your comments, and let asside the denigrating ones. > My conclusion is to better not give feedback to the community next time > (which is what-I've-done), cause my frustrated state of mind could > negatively influence the wording so that others are incapable of > separating the signal from the noise. Which, in turn, results in > lengthy calls to rethink a position I did not occupy in the first place. Hehe, well, no, but you have to be aware that some of your wording may hit the wrong place, and as said, you should not have gone to personal emails. Anyway, it should be fixed in yesterday's and todays build, please test them and provide feedback. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
