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

Re: [boot-floppies] `mke2fs' and new Linux 2.2 ext2 features ?



Wow. I looked it over again.

In article <[🔎] oaoga4xqf8.fsf@arroz.fake>,
  at 29 Jan 2000 21:07:55 -0500,
    on Re: [boot-floppies] `mke2fs' and new Linux 2.2 ext2 features ?,
 Adam Di Carlo <adam@onshore.com> writes:

> Given that you can't even say what's the benefit of removing back
> compatability, it seems to me that retaining back-compatability is
> more desirable than removing it.

If we should retain backward-compatibility (I think we should do this
because many users may use slink system as well as potato, or some one
(not so many, but not so rare nor ignorable) uses 2.0 kernel on potato),
then

>   /* Oflag:  1 == 2.0 compat; 0 == 2.2 only */
>   Oflag = 0;

I doubt this line. Maybe "Oflag = 1;" is right ?

>   if ( bootargs.isverbose ) {
>     sprintf(prtbuf, _("This 2.2 version of the Linux kernel has new \"ext2\" filesystem features not present in earlier kernel versions. Using these features, however, means that you can no longer run earlier kernels, such as Linux 2.0. Do you want to retain Linux kernel 2.0 compatability?"),
> 	  p->name);
>     Oflag = yesNoBox(prtbuf, _("Pre-2.2 Linux Kernel Compatibility?"));
>   }
> 
> Thus, 2.0 compat is retained by default.

This default "Oflag = 0" does not retain 2.0 compat, with the current lines at

  sprintf(prtbuf, "mkfs.ext2 %s %s %s",( Oflag ? "" : "-O none"),
          ( cflag ? "-c" : ""), p->name);

-- 
  Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>


Reply to: