Changing a few things and accounting for false positives
(assuming worst case and rounding up for case 2a,
rounding down for 2b)
> * # Changes needed in 2a = row 1 + row 7 + row 8 + row 9 + row 10
> = 34 + 80 + 10 + 3 + 3 = 130
> * # Changes needed in 2b = row 1 + row 4 +
Changing a few things, accounting for false positives
(assuming worst case and rounding up for case 2a,
rounding down for 2b)
> * # Changes needed in 2a = row 1 + row 7 + row 8 + row 9 + row 10
> = 34 + 80 + 10 + 3 + 3 = 130
> * # Changes needed in 2b = row 1 + row 4 +
On Saturday 13 February 2016 13:18:32 Dave Chinner wrote:
> On Fri, Feb 12, 2016 at 01:45:49AM -0800, Deepa Dinamani wrote:
> > This is in preparation for changing VFS inode timestamps to
> > use 64 bit time.
> > The VFS inode timestamps are not y2038 safe as they use
> > struct timespec. These
On Fri, Feb 12, 2016 at 01:36:05AM -0800, Deepa Dinamani wrote:
> The VFS inode timestamps are not y2038 safe as they use
> struct timespec. These will be changed to use struct timespec64
> instead and that is y2038 safe.
> But, since the above data type conversion will break the end
> file
Thought this might be of interest to this group - changing the date to
1st January 1970 disables 64-bit iOS devices.
Original link:
https://www.reddit.com/r/jailbreak/comments/458ao3/discussion_changing_time_date_settings_to_jan_1/
Hacker News discussion:
>> static inline void ceph_encode_timespec(struct ceph_timespec *tv,
>> const struct timespec *ts)
>> {
>> tv->tv_sec = cpu_to_le32((u32)ts->tv_sec);
>> tv->tv_nsec = cpu_to_le32((u32)ts->tv_nsec);
>> }
Pointed to decode function change in
