lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.63.0607271732010.8976@alpha.polcom.net>
Date:	Thu, 27 Jul 2006 17:39:40 +0200 (CEST)
From:	Grzegorz Kulewski <kangur@...com.net>
To:	Pavel Machek <pavel@....cz>
Cc:	Hans Reiser <reiser@...esys.com>,
	Matthias Andree <matthias.andree@....de>,
	lkml@...productions.com, Jeff Garzik <jeff@...zik.org>,
	Theodore Tso <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>,
	ReiserFS List <reiserfs-list@...esys.com>
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org
 regarding reiser4 inclusion

On Wed, 26 Jul 2006, Pavel Machek wrote:

> Hi!
>
>>> of the story for me. There's nothing wrong about focusing on newer code,
>>> but the old code needs to be cared for, too, to fix remaining issues
>>> such as the "can only have N files with the same hash value".
>>>
>> Requires a disk format change, in a filesystem without plugins, to fix it.
>
> Well, too bad, if reiser3 is so broken it needs on-disk-format-change,
> then I guess doing that change is the right thing to do...

Sorry for my stupid question, but could you tell me why starting to make 
incompatible changes to reiserfs3 now (when reiserfs3 "technology" is 
rather old) and making reiserfs3 unstable (again), possibly for several 
months or even years is better than fixing big issues with reiser4 (if 
there are any really big left) merging it and trying to stabilize it?

For end user both ways will result in mkfs so...


Thanks,

Grzegorz Kulewski

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ