Re: Unix to Dos filtering
If I edit a file on Solaris and periodically save the contents, when I open the file on my NT machine using vim I see the most recently saved version (no refresh/remap/logout/reboot necessary. Neither have I. I have never heard of such a thing. Perhaps an application is doing this? Certainly not samba This can happen with certain configuration options (oplocks IIRC) although I thought it was changes on the NT side were not visible to Unix. However configured correctly this should not be a problem. Mike
Re: Unix to Dos filtering
- Original Message - From: "Dave Zavasnik" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 13, 2000 5:31 PM Subject: Re: Unix to Dos filtering Stephen L Arnold wrote: If you work with files from a windoze client that reside on a samba share, windoze will cache the file contents locally, thus changes made from the unix/linux side (after the file has been opened once in windoze) will not be visible to the windoze client, even if you re-open the file or refresh windoze exploder (i.e., windoze will only see the cached file contents). You must reboot windoze (or maybe just logout from NT) before it will see the updated contents. I don't see this behavior. I have samba exporting my Solaris home directory. If I edit a file on Solaris and periodically save the contents, when I open the file on my NT machine using vim I see the most recently saved version (no refresh/remap/logout/reboot necessary. Neither have I. I have never heard of such a thing. Perhaps an application is doing this? Certainly not samba -- Matthew Brown
Re: Unix to Dos filtering
Karen Baldwin writes: We've been using CVS exclusively on Solaris/Unix until now. We are now porting to NT. We intend to have a single source repository on a Solaris machine, which will be accessed by users on BOTH the NT and Solaris nodes. We'll be using Samba as the cross-platform file access mechanism. Although you could use Samba to share the repository, using client/server CVS is a much better solution. Do not under any circumstances use Samba to share working directories -- the different line ending conventions between Unix and DOS/Windows will cause you no end of grief. -Larry Jones Let's pretend I already feel terrible about it, and that you don't need to rub it in any more. -- Calvin
RE: Unix to Dos filtering
On Friday, March 10, 2000 11:33 AM, Karen Baldwin [SMTP:[EMAIL PROTECTED]] wrote: Hi; just discovered this group. Help! I have a question very similar to that first asked within this thread. We've been using CVS exclusively on Solaris/Unix until now. We are now porting to NT. We intend to have a single source repository on a Solaris machine, which will be accessed by users on BOTH the NT and Solaris nodes. We'll be using Samba as the cross-platform file access mechanism. Until now I speculated that maybe the proper thing to do is to employ the cvswrappers file. specifically, using the -f option to invoke 'unix2dos' when a checkout is performed from the NT side, and to invoke 'dos2unix' when a checkin is performed from the NT side. When a checkin/checkout is done from the Unix side, we'd (somehow?) preclude those utilities from being run. Is this unrealistic? Is this a naive approach, doomed to failure? Is there a preferred approach that's been found to work by others who've 'been there' already? I think the historical consensus for this scenario is to use CVS in a client/server mode and let the client sort out line terminations. We use WinCVS as a Windows/NT front end and CVS in pserver mode on our Unix server. *** Chris CameronOpen Telecommunications NZ Ltd Software Development Team Leader [EMAIL PROTECTED] P.O.Box 10-388 +64 4 495 8403 (DDI) The Terrace fax: +64 4 495 8419 Wellington cell: +64 21 650 680New Zealand Life, don't talk to me about life (Marvin - HHGTTG)
Re: Unix to Dos filtering
Stephen L Arnold wrote: Wrong. I distinctly remember the samba guys (Allison Tridgell) saying they didn't want samba to attempt any such conversion. From the samba docs: Hmm... There is a FAQ (must dig it out if I can find it) that specifically mentions that smbfs honours the 'conv=' options line FAT does. I have had this problem myself, with files coming out differently when you read them through smbfs than when you read them on a windows machine. I generally FTP between unix and windows these days because the corruption problems are a nightmare (not to mention smbfs suddenly dropping the connection in the middle of a file copy and hanging the 'cp' process). Generally SMB mounts will only stay 'alive' for half an hour or so, then they will die. You have to unmount/remount to wake them up again. I know a lot of stability problems have been fixed recently, and maybe it's better now, but I still wouldn't recommend trying to access a repository through it. Tony -- Swamp frog: ribb-it ribb-it ribb-it Busch frog: bud..wis..er bud..wis..er Win95 frog: Re-boot Re-boot Re-boot [EMAIL PROTECTED]
RE: Unix to Dos filtering
-Original Message- From: Tony Hoyle [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 08, 2000 4:05 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Unix to Dos filtering Stephen L Arnold wrote: Wrong. I distinctly remember the samba guys (Allison Tridgell) saying they didn't want samba to attempt any such conversion. From the samba docs: Hmm... There is a FAQ (must dig it out if I can find it) that specifically mentions that smbfs honours the 'conv=' options line FAT does. [snip] smbfs and samba are two different (but related) things (and are typically merged in most people's minds). smbfs is the smb filesystem that linux/unix/whatever needs in order to mount smb shares exported from other hosts. Samba is a pair of daemons (smbd and nmbd) that provide a non-windoze host with the ability to export smb shares to other hosts on the network. Samba also does browse-master, domain logins, some domain control stuff, smb print services, etc. I believe you are right about smbfs honoring the 'conv=' stuff, however, you didn't say "smbfs" you said "samba" (so I had to chime in ;) Steve with Std.Disclaimer; use Std.Disclaimer;
RE: Unix to Dos filtering
-Original Message- From: Tony Hoyle [mailto:[EMAIL PROTECTED]] Sent: Monday, March 06, 2000 9:33 AM Subject: Re: Unix to Dos filtering [snip] Much of the same caveats exist re: sharing over samba as sharing over NFS, only worse (samba has this habit of attempting to convert text files itself unless you stop it...) Wrong. I distinctly remember the samba guys (Allison Tridgell) saying they didn't want samba to attempt any such conversion. From the samba docs: !== !== CRLF-LF-Conversions.txt for Samba release 2.0.5a 22 Jul 1999 !== We get many requests for CRLF/LF format conversion handling by samba. The problem is that there is no clean way to determine which files should / could be converted and which MUST not be. Since Unix and DOS/Windows uses alike will use .txt to represent a file containing ASCII text we can not reliably use the file extension. The same applies to the .doc extension. Samba operates around the premise that we should leave all files unchanged. By not implementing CRLF/LF conversions we can not be guilty of damaging anyone's files. When someone comes along with a sound implementation that guarantees file integrity we will jump at the opportunity to implement this feature. Until such time there is no prospect for action on this topic. !== !== end CRLF-LF-Conversions.txt !== You may want to re-think your understanding of samba, et al. Steve
Re: Unix to Dos filtering
[EMAIL PROTECTED] wrote: Dear CVS Gurus, Client developers on my site, checkout code on unix machines. They then use the checked out code on Windows using Samba. How do i make sure that when they check the files out on unix, it automatically put the Ctrl Ms on these DOS-type files? If a file is checked in with Ctrl Ms on unix, are the Ctrl Ms retained on another checkout or during commit? (All cvs commands are run on unix). Thanks in advance, aditya If the files are checked in in 'Microsoft format' on the Unix boxes, you must never attempt to subsequently check them out from a microsoft box as it will get very confused (It will get lots of CRCRLF pairs and attempt to double the number of lines in the source file). Why not just use the microsoft client, which will strip the extra CR characters out, and put them back in again? Much of the same caveats exist re: sharing over samba as sharing over NFS, only worse (samba has this habit of attempting to convert text files itself unless you stop it...) Tony -- Swamp frog: ribb-it ribb-it ribb-it Busch frog: bud..wis..er bud..wis..er Win95 frog: Re-boot Re-boot Re-boot [EMAIL PROTECTED]
Re: Unix to Dos filtering
[EMAIL PROTECTED] writes: Client developers on my site, checkout code on unix machines. They then use the checked out code on Windows using Samba. How do i make sure that when they check the files out on unix, it automatically put the Ctrl Ms on these DOS-type files? If a file is checked in with Ctrl Ms on unix, are the Ctrl Ms retained on another checkout or during commit? (All cvs commands are run on unix). Don't do that. Do check-in and check-out on the platform you intend to use the files on; sharing working directories between systems with different text file conventions is just asking for trouble. -Larry Jones Let's just sit here a moment... and savor the impending terror. -- Calvin
