--=-z+uRMND92IMzw5Xy6IOv Content-Type: multipart/mixed; boundary="=-6qR855BK0gjm5p6plWov" --=-6qR855BK0gjm5p6plWov Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I have found that most of the popular editors (vi, pico, nano, vim, insert yours here) have been ported to Win32. They may be a couple versions behind but if you're not running Gentoo, then you're obviously not for the whole up-to-date version thing (Just my plug for Gentoo :-D). --=20 Bryce C CoBryce Communications --=-6qR855BK0gjm5p6plWov Content-Disposition: inline Content-Description: Forwarded message - Re: Samba client and file time and date problem Content-Type: message/rfc822 Return-Path: Delivered-To: mail.bryceconet.plug@localhost.cobryce.com Received: from localhost (localhost.localdomain [127.0.0.1]) by cobryce.myvnc.com (Postfix) with ESMTP id 3FD89BFA05 for ; Thu, 7 Aug 2003 09:23:58 -0700 (MST) Envelope-to: plug@bryceco.net Delivery-date: Thu, 07 Aug 2003 12:23:51 -0400 Received: from 66.103.137.65 by localhost with POP3 (fetchmail-5.9.7) for mail.bryceconet.plug@localhost (single-drop); Thu, 07 Aug 2003 09:23:58 -0700 (MST) Received: from [68.14.243.59] (helo=pluglist.macrosift.com) by sh2.1-sh.com with esmtp (Exim 4.20) id 19knYN-0007SI-Ho for plug@bryceco.net; Thu, 07 Aug 2003 12:23:51 -0400 Received: from lists.plug.phoenix.az.us (plug [127.0.0.1]) by pluglist.macrosift.com (Postfix) with ESMTP id D3EA61A72E8; Thu, 7 Aug 2003 09:37:04 -0700 (MST) Delivered-To: plug-discuss@lists.plug.phoenix.az.us Received: from adtron.com (h-64-105-64-37.PHNDAZ91.covad.net [64.105.64.37]) by pluglist.macrosift.com (Postfix) with ESMTP id 48D551A72E6 for ; Thu, 7 Aug 2003 09:36:30 -0700 (MST) Received: from adtron.com by adtron.com with SMTP (MDaemon.PRO.v6.7.8.R) for ; Thu, 07 Aug 2003 09:22:51 -0700 Message-ID: <3F327CC8.8080301@adtron.com> From: Alan Dayley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: plug-discuss@lists.plug.phoenix.az.us Subject: Re: Samba client and file time and date problem References: <3F318127.30407@adtron.com> <1060230164.2864.24.camel@lin-workstation.azapple.com> <3F31E713.1090203@mindspring.com> <1060235505.8059.2.camel@BryceCo1> In-Reply-To: <1060235505.8059.2.camel@BryceCo1> Content-Type: text/plain; charset=us-ascii; format=flowed X-Authenticated-Sender: adayley@adtron.com X-Return-Path: adayley@adtron.com X-MDaemon-Deliver-To: plug-discuss@lists.plug.phoenix.az.us Sender: plug-discuss-admin@lists.plug.phoenix.az.us Errors-To: plug-discuss-admin@lists.plug.phoenix.az.us X-BeenThere: plug-discuss@lists.plug.phoenix.az.us X-Mailman-Version: 2.0.13 Precedence: bulk Reply-To: plug-discuss@lists.plug.phoenix.az.us List-Help: List-Post: List-Subscribe: , List-Id: Main PLUG discussion list. List-Unsubscribe: , List-Archive: Date: Thu, 07 Aug 2003 09:22:32 -0700 Status: Content-Transfer-Encoding: quoted-printable Bryce C wrote: > I'm going to have to second the refresh option to see if the file's > datestamp has changed. Opening a file says that on a fresh pull, the > contents are right so why not do a fresh pull/poll of the file's info. > However, that shouldn't affect gcc because it should be doing its own > polling, not using win2k's cached data. > Good luck, I did some more experiments this morning and still don't have an answer.=20 I still don't think refresh or filesystem caching has anything to do=20 with it. Below is a sequence that I tried to make sure any needed=20 refresh works. (BTW, gcc is not involved here. I am using GNU Make on=20 Win2k to excute commands on a compiler from Green Hills that runs on Win2k.= ) 0. Note the date/time of target file in Win2k Command Prompt dir and=20 Explorer. 1. smbmount the Win2k share to a mount point on the Linux box. 2. Open the file in Linux from the share via the mount point. 3. Edit on the Linux box. 4. Save the file to the Win2k share via the Linux mount point. 5. Check the file date/time in Win2k Command Prompt dir and Explorer.=20 Unchanged. 6. Close the editor in Linux. 7. Check the file date/time in Win2k Command Prompt dir and Explorer.=20 Unchanged. 8. unmount the share from the Linux box. 9. Check the file date/time in Win2k Command Prompt dir and Explorer.=20 Unchanged. 10. Open file with Notepad on Win2k. See changes that were made in the=20 Linux editor. 11. Close Notepad. 12. Check the file date/time in Win2k Command Prompt dir and Explorer.=20 Unchanged. 13. Logout of Win2k. Login to Win2k. 14. Check the file date/time in Win2k Command Prompt dir and Explorer.=20 Unchanged. The share is completely disconnected from the Linux box where the=20 contents of the file were changed and saved. The new changes are=20 completely visible via editor on the Win2k box. Yet the date/time of=20 the file is the same as when the sequence started. I would think the=20 connection and filesystem refresh would have been triggered at step 4=20 when the data was correctly saved or steps 6, 8, 11 or 13. Do you see=20 somewhere else that I am missing an understanding about a refresh or=20 caching? Therefore, I don't believe it to be a filesystem refresh issue. It must=20 be permissions or SMB connection settings that don't allow for file=20 date/time changes via SMB. I don't know if the supposed settings I am=20 looking for are on the samba side in the Linux box or on the Win2k side. Thanks for the good luck wish. Looks like I'll need it. At this point,=20 I may go hunting for a decent editor to use on Win2k so gmake can=20 correctly run the build based on correct date/time stamps. Alan --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --=-6qR855BK0gjm5p6plWov-- --=-z+uRMND92IMzw5Xy6IOv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/Mn/+/wbq/C6yyPcRAmy4AKC8LLF9l6ktjDYtboMLweccZg8pWwCbBfzL wmBD7zyWTMOJYPCdgsKPkuY= =bJgx -----END PGP SIGNATURE----- --=-z+uRMND92IMzw5Xy6IOv--