Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Suse sed question

On 08/28/2013 05:23 PM, David Kramer wrote:
> I need to verify this for myself, but someone working with moving some dev
> continuous integration tools from Windows to an older version of Suse
> tells me that the sed command is missing the -b option to treat input
> files as binary.  Its taking all the input files, which are in DOS format,
> and converting them to POSIX line endings, which is causing our source
> control system to act as if every line in the file is changed.
I use SED very frequently, and I have never had it change anything that 
was not in the script. Most of my scripts have multiple sed scripts, and 
usually remove the windows line endings because some of the files I 
modify have crlf in them. But, just to reiterate, I have never had sed 
change the line endings without the proper script.

Jerry Feldman <gaf at>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /