From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Landley Subject: Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk Date: Sat, 11 May 2019 23:12:44 -0500 Message-ID: References: <20190509112420.15671-1-roberto.sassu@huawei.com> <4aee6e10-0eec-1d76-af66-dc8c7b68b766@landley.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4aee6e10-0eec-1d76-af66-dc8c7b68b766@landley.net> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski , Roberto Sassu Cc: Al Viro , LSM List , linux-integrity , initramfs@vger.kernel.org, Linux API , Linux FS Devel , LKML , Mimi Zohar , silviu.vlasceanu@huawei.com, dmitry.kasatkin@huawei.com, takondra@cisco.com, kamensky@cisco.com, "H. Peter Anvin" , Arnd Bergmann , james.w.mcmechan@gmail.com List-Id: linux-api@vger.kernel.org On 5/11/19 11:04 PM, Rob Landley wrote: > P.P.S. Sadly, if you want an actually standardized standard format where > implementations adhere to the standard: IETF RFC 1991 was published in 1996 and Nope, darn it, checked my notes and that wasn't it. I thought zip had an RFC, it's just zlib, deflate, and gzip, and that's not the number of any of them. I still think sticking with a lightly modified cpio makes the most sense, just... in band signalling that _doesn't_ solve the y2038 problem, the file size limit, or address sparse files seems kinda silly. Rob