| |||||||||||||
Evolution of shells in Linux (developerWorks)Evolution of shells in Linux (developerWorks)Posted Dec 12, 2011 21:34 UTC (Mon) by ccchips (guest, #3222)In reply to: Evolution of shells in Linux (developerWorks) by Cyberax Parent article: Evolution of shells in Linux (developerWorks)
Interesting.
Does Samba4 or related utility have the fix?
I was a bit surprised to learn about the [System.DateTime]::FromFileTime() function in Powershell. I did a lot of research into this previously and didn't see that.
(Log in to post comments)
Evolution of shells in Linux (developerWorks) Posted Dec 12, 2011 21:41 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link]
No. Why should there be a fix?
LastLogon is a valid timestamp, just in a very braindead format (in 100-s nanosecond increments since 1601).
Evolution of shells in Linux (developerWorks) Posted Dec 13, 2011 16:20 UTC (Tue) by ccchips (guest, #3222) [Link]
There should be a fix because people need to use that information, not dig around on the Internet, figure out how braindead the timestamp is, and come up with a scheme to read it in human-readable form. Quest Software fixed it by providing a conversion method.
I was asking about fixing *accessibility to the information.* Which is far more important to me than what shell handles what arguments, and how the pipelines work.
|
|||||||||||||