There is a LOT different. The most noticeable seems to be the outputs of cmp -l in the first column are about 2-3 times larger than the second one. I'm guessing maybe vi chopped some long lines, if that's what those numbers are? Why would ifhp care?
In any case, I'm going to produce a set of small df's to post and see what the consensus is... this is driving me /nuts/. ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630 On Tue, 24 Jun 2003, Dave Lovelace wrote: > Ryan Novosielski wrote: > > > > Nope -- the file behaves exactly the same after the tr (I redirected it to > > another file), and still will work only after being vi'd (or probably > > otherwise massaged, but this is what I know works). > > > I was somewhat doubtful about CRs being the problem; in my experience, > vi leaves them alone. (The vim that's on the RedHat Linux I use most now > invisibly assumes that you really mean to edit a DOS/Win file, strips them > off when you start editing, and adds them back when you save. vi on > the Unix versions I'm familiar with treats them as characters, displayed > as "^M".) > > A suggestion for determining what *is* changing: > - make a backup copy of your file > - load & save with vi as you've been doing > - Look at the files. Are they still the same size? Try "cmp -l" (that's > lowercase "L" to look for differences. Also, these are supposed to > be text files, IIRC, aren't they? Try running the before & after > versions through "cat -vt" and running diff on the results. > > Actually, I just had a thought. Probably not the cause of your problem, > but one thing I *know* vi is apt to do to a file. If your file ends > without a linefeed, vi will add one. (Again, I'm assuming I'm remembering > correctly that this is supposed to be text for this idea to make any > sense at all.) In that case, "echo >> yourfile" would work as well as > running through vi. > > -- > - Dave Lovelace > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
