[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#67888: marked as done ([CVS-fixed] Netwinder/arm port shouldn't ask about maintaining 2.0 compatability)



On Mon 27 Nov, Adam Di Carlo wrote:
> Wookey <wookey@aleph1.co.uk> writes:
> 
> > On Thu 23 Nov, Adam Di Carlo wrote:
> > > Wookey <wookey@aleph1.co.uk> writes:
> > 
> > > > On Tue 21 Nov, Debian Bug Tracking System wrote:
> > 
> > > > > >From andersen@codepoet.org Sat Jul 29 01:11:08 2000
> > > > > Return-path: <andersen@codepoet.org>
> > 
> > > > > The debian installer for potato worked just fine on the netwinder,
> > > > > one I convinced it to tftp boot the provided netwinder-rescue
> > > > > image.  One hitch though -- the question about maintaining 2.0
> > > > > compatability for the ext2 fs should be removed and forced to
> > > > > "yes".  Answering "no" causes the netwinder's firmware (which is
> > > > > just a stripped down linux kernel) to be unable to read the
> > > > > filesystem -- so it is unable to boot the system.  Not that big a
> > > > > deal though.
> > 
> > > Could you file this as a bug?
> > 
> > erm, are you confused adam? The above para has already been filed as
> > a bug and you replied saying it was fixed in bf2.2.17 (see below -
> > it was this message that I replied to). That's all fine so far as I
> > can tell. Or do you mean I should file the fact that this causes
> > (may cause?) a different problem for RiscPC as a bug?
> 
> Yes, the different problem.

OK. I've researched this a little and have actually found a good reason to
keep kernel 2.0 compatibility by default (the RISCOS ext2fs reader iscafs
needs it). So we can stick with the same option as netwinders for now. I'll
include this in my forthcoming boot-floppies patches for arm, and not file a
bug about it.

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/



Reply to: