Re: bug: wrong file times on ncpfs

From: Petr Vandrovec (VANDROVE@vc.cvut.cz)
Date: Tue Jan 25 2000 - 17:04:36 EST


On 25 Jan 2000 Oleg Makarenko wrote:
> correct shift value in its local2utc()/utc2local() functions I still
> have some anomalies: on DST the time of previously created files will be
[snip]
> I don't see how can I change ncpfs either :( cause to make it calculate
> local times correctly I need the values of dststart and dstend for local
> timezone and can't find the needed structure in the kernel and the way
> to initialize it.
> While it is possible to add needed structure and new syscall somebody on
> the list should know the better solution.
It is not completely correct. You have to have per-mountpoint function
(ioctl) which allows you to pass pre-parsed timezone data into kernel.
Server uses its own local time, not yours. Although usually they are same,
currently I have mounted three ncpfs volumes, from different timezones.
Timestamps are wrong on all that filesystems, as expected... I will not
accept any timestamp patch to ncpfs except one which correctly handles
files created in past/future too, because of although current situation is
not perfect, it is how things works for some years now...
                                        Best regards,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
                                                

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



This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:14 EST