Best bet is to make the request on the talk page: https://en.wikipedia.org/wiki/Talk:Comparison_of_file_systems
Does that help? - J On Sun, Jun 14, 2015 at 5:55 PM, Blibbet <[email protected]> wrote: > Is there a way to request a feature to be added to Wikipedia? Is there > an issue tracking system to request new content? > > Open source projects often have ticketing/issue tracking systems to tack > feature requests, in addition to developer-contributed features that > include patches. Here's a case where I see a need in the Wikipedia > content, but don't currently have time to address it, and am wondering > if there's any resources to submit this request to, if they have spare > cycles to work on it. > > This page: > https://en.wikipedia.org/wiki/Comparison_of_file_systems > needs a new column that shows if the file system uses UTC or local time > or some other time for it's files. > > Below question is a thread from a firmware development mailing list, > UEFI firmware is reporting wrong dates in the UEFI Shell. The Apple > firmware guys are asking: > > "I’m guessing more modern filesystems probably store the time in UTC?" > > The above Wikipedia Comparison page is very good. If it had this data, > it would be better, and useful in this specific case (and probably other > software, not just below case), so the UEFI apps would get correct file > dates. > > Unfortunately, I currently don't have time to research all of it at the > moment. Apparently, FAT, CDS (ISO9660), DVDs (OSTA UDF) use local, NTFS > uses UTC: > > > https://msdn.microsoft.com/en-us/library/windows/desktop/ms724290%28v=vs.85%29.aspx > > This column needs data on (ZFS, Ext2-Ext4, FreeBSD's current file > systems, BTRFS, Apple HFS+ on-disk formats, and SMB/CIFS and NFS network > protocols), at least, to become useful ... of course data for all FSs > would be best. The data should be in the specs of these file systems, or > the source code of their [cloned] open source implementations, it just > takes a bit of time to track down the data from each FS's spec and > sources. There maybe a few cases where multiple FS implementations > return different TZ values, in which case I'd call that a bug. :-) > > I'll try to create this if nobody else does, but probably not for a > while, and only for a half-dozen file systems. Access to live > implementations of these file systems and FS diagnostic tools would also > help, but not sure if that kind of data is useful for Wikipedia references. > > Thanks. > > -------- Forwarded Message -------- > Subject: Re: [edk2] [ShellPkg] I think there is an issue in ls. > Date: Wed, 10 Jun 2015 18:38:58 -0700 > From: Andrew Fish <[email protected]> > To: [email protected] > > > On Jun 10, 2015, at 6:33 PM, Carsey, Jaben <[email protected]> > wrote: > > > > Andrew, > > > > I agree, that looks like an issue. Can you submit a patch with this > fixed? > > Sorry don’t have time right now. > > > I will put this on the list of issues. > > > > Thanks, I hit this issue in another location and look to see what the > shell did. Since the shell seemed to be doing the wrong thing I decided > to at least report it to the mailing list. > > I’m guessing more modern filesystems probably store the time in UTC? > > Thanks, > > Andrew Fish > > > -Jaben > > > >> -----Original Message----- > >> From: Andrew Fish [mailto:[email protected]] > >> Sent: Wednesday, June 10, 2015 6:26 PM > >> To: [email protected] > >> Subject: [edk2] [ShellPkg] I think there is an issue in ls. > >> Importance: High > >> > >> Dear ShellPkg maintainer, > >> > >> I think there is an issue with the ls command. It does not use the > TImeZone, > >> so it seems it is hard coded to assume that a filesystem stores time > like FAT, in > >> local time. The FAT driver always returns EFI_UNSPECIFIED_TIMEZONE, > which > >> implies the values are local time. But what if a filesystem is > storing time in UTC > >> (EFI_TIME.TimeZone == 0)? it seems the current path in the shell assumes > >> EFI_UNSPECIFIED_TIMEZONE (thus all time is local time). I don’t think > this > >> follows the UEFI spec. I think the correct algorithm is: > >> > >> if FileSystemTime.TimeZone == EFI_UNSPECIFIED_TIMEZONE > >> // This is the current path in the code > >> Assume time is local time, and print it out > >> else: > >> // This is the missing path. > >> Adjust the FileSystemTime.TimeZone for the System.TimeZone (and > >> System.Daylight), thus display the time in local time. > >> > >> Thanks, > >> > >> Andrew Fish > >> > >> > >> > > ------------------------------------------------------------------------------ > >> _______________________________________________ > >> edk2-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/edk2-devel > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > edk2-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/edk2-devel > > > > ------------------------------------------------------------------------------ > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/edk2-devel > > > > > _______________________________________________ > Wikimedia-Cascadia mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia > _______________________________________________ Wikimedia-Cascadia mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia
