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] [day] [month] [year] [list]
Date:   Thu, 4 Apr 2019 13:55:45 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Stuart Swales <stuart.swales.croftnuisk@...il.com>
Cc:     Russell King - ARM Linux admin <linux@...linux.org.uk>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Ben Dooks <ben-linux-arm@...ff.org>
Subject: Re: fs/adfs - keep or kill it?

On Thu, Apr 04, 2019 at 09:44:24PM +0100, Stuart Swales wrote:
> On 04/04/2019 11:35, Russell King - ARM Linux admin wrote:
> Have posted on the RISC OS Open site. I imagine some people will
> complain just because they can. Can't see a need for it in new kernels
> myself; people can always use old systems if they need to get data off
> old ADFS IDE drives like I had to.

If it's just grabbing old data, it's far better to do that with a
userspace tool which understands the ADFS layout (several exist).
The only good reason for keeping fs/adfs/ alive is if there's need to
continue to access data that lives on an ADFS filesystem and needs to
be read/written by both a RISC OS host and a Linux host.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ