I have had some success (read no noticed problems), moving some text conf files from a Win <cr,lf> format to Linux and have them work. For example my zone files, moving them from my Win DNS server. But what about other files? I guess I want to know this more to prevent a mistake from crashing things, as I do have GEDIT. If I were to build an anaconda-ks.cfg in notepad, write it to a floppy then did a linux ks=floppy, would it work? I have search the archives and google, but either I am missing the right search words, or something.
dos2unix and unix2dos are your friends... On Tue, 28 Feb 2006, Robert Moskowitz wrote:> I have had some success (read no noticed problems), moving some text conf > files from a Win <cr,lf> format to Linux and have them work. For example my > zone files, moving them from my Win DNS server. > > But what about other files? I guess I want to know this more to prevent a > mistake from crashing things, as I do have GEDIT. > > If I were to build an anaconda-ks.cfg in notepad, write it to a floppy then > did a linux ks=floppy, would it work? > > I have search the archives and google, but either I am missing the right > search words, or something. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >
Robert Moskowitz wrote:> I have had some success (read no noticed problems), moving some text > conf files from a Win <cr,lf> format to Linux and have them work. For > example my zone files, moving them from my Win DNS server. > > But what about other files? I guess I want to know this more to prevent > a mistake from crashing things, as I do have GEDIT. > > If I were to build an anaconda-ks.cfg in notepad, write it to a floppy > then did a linux ks=floppy, would it work? >When in doubt, check out the dos2unix and unix2dos utilities BK
On 2/28/06, Robert Moskowitz <rgm at htt-consult.com> wrote:> I have had some success (read no noticed problems), moving some text > conf files from a Win <cr,lf> format to Linux and have them > work. For example my zone files, moving them from my Win DNS server. > > But what about other files? I guess I want to know this more to > prevent a mistake from crashing things, as I do have GEDIT. > > If I were to build an anaconda-ks.cfg in notepad, write it to a > floppy then did a linux ks=floppy, would it work? > > I have search the archives and google, but either I am missing the > right search words, or something. >CHeck out this GLP'd projrct I know it can properly read and display unix "style" text files, and IIRC you can choose how the files are written. http://www.scintilla.org/ Textpad is a non GPL'd alturnative that I know works. http://www.textpad.com/ -- Leonard Isham, CISSP Ostendo non ostento.
On Tue, 2006-02-28 at 14:50, Robert Moskowitz wrote:> I have had some success (read no noticed problems), moving some text > conf files from a Win <cr,lf> format to Linux and have them > work. For example my zone files, moving them from my Win DNS server. > > But what about other files? I guess I want to know this more to > prevent a mistake from crashing things, as I do have GEDIT. > > If I were to build an anaconda-ks.cfg in notepad, write it to a > floppy then did a linux ks=floppy, would it work?I'm not sure there is a generic answer. Some things ignore the CR's, some don't. It's always a good idea to remove them. On Windows you can edit in wordpad instead of notepad and it will put them back. If you edit in vim (either windows or Linux versions) you can write either way with the: :set fileformat option.> I have search the archives and google, but either I am missing the > right search words, or something.In the old days with real vi, you would: :%s/^v^m// to get rid of them, but vim doesn't like that. -- Les Mikesell lesmikesell at gmail.com
Les Mikesell wrote:> On Tue, 2006-02-28 at 14:50, Robert Moskowitz wrote: > > I have had some success (read no noticed problems), moving some > > text conf files from a Win <cr,lf> format to Linux and have them > > work. For example my zone files, moving them from my Win DNS > > server. > > > > But what about other files? I guess I want to know this more to > > prevent a mistake from crashing things, as I do have GEDIT. > > > > If I were to build an anaconda-ks.cfg in notepad, write it to a > > floppy then did a linux ks=floppy, would it work? > > I'm not sure there is a generic answer. Some things ignore the > CR's, some don't. It's always a good idea to remove them. On > Windows you can edit in wordpad instead of notepad and it will put > them back. If you edit in vim (either windows or Linux versions) > you can write either way with the: > > set fileformat > option. > > > I have search the archives and google, but either I am missing the > > right search words, or something. > > In the old days with real vi, you would: > :%s/^v^m// > to get rid of them, but vim doesn't like that.It depends on how Vim recognizes the file. If Vim displays the file as a DOS file, it will hide the ^M and you can't search for it. If Vim displays the file as a unix file, it will show the ^M at the end of the line and you can search and replace it with the command shown above. -- Bowie
Les Mikesell wrote:> On Wed, 2006-03-01 at 11:23, Bowie Bailey wrote: > > > > > > In the old days with real vi, you would: > > > :%s/^v^m// > > > to get rid of them, but vim doesn't like that. > > > > It depends on how Vim recognizes the file. If Vim displays the file > > as a DOS file, it will hide the ^M and you can't search for it. > > If Vim displays the file as a unix file, it will show the ^M at the > > end of the line and you can search and replace it with the command > > shown above. > > OK, but what would convince vim to display files with ^M's as > unix files? I thought it took their presence as the hint to > display in DOS mode.A screwed-up text file that doesn't have the ^M's on every line will display this way in Vim. This tends to happen when you transfer a DOS file to unix and then edit it with a program that does not do the conversion for you. The resultant file has ^M at the end of every line except ones you added with the unix editor. -- Bowie