Well, I'm not sure what it was but it wasn't the carnage return. But there is a hidden character. I did some simple scripts and the same code works when I re-typed the entire thing.
The only parts that were effected were the encapsulated EOF tags. So there must have been some type of hidden character. Thanks for all the help. ----- Original Message ----- From: "Jerry McAllister" <[EMAIL PROTECTED]> To: "Roger 'Rocky' Vetterberg" <[EMAIL PROTECTED]> Cc: "John Bleichert" <[EMAIL PROTECTED]>; "Terry Cooper" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, October 22, 2002 7:36 AM Subject: Re: FreeBSD bootable floppy Script NOT WORKING > > > > John Bleichert wrote: > > > > *snip* > > > > > * EOM is not a command, it's an end-of-text marker, similar to the one > > > used in Perl. > > > > > > * There are text-file incompatibilities between Unix and DOS. If you're > > > copying/pasting the file from the website in Windows, ftp'ing it to a Unix > > > box and then trying to run it, all those extra linefeeds may cause > > > extremely bizzare errors. > > > > > > I hate to say it, but if you can only get the Internet on your winbox, you > > > should probably fire up vi (or whatever editor you like) and enter it > > > manally. Or run a dos2unix utility on the script on your Unix box to set > > > it up and clear out those linefeeds. > > > > A simple command like "perl -i.bak -npe 's/\r\n/\n/g' filename" will > > clear the linefeeds and even make a backup of the file. (It has never > > failed me, but you'll never know) > > I sort of doubt that extra CARRIAGE RETURNs (CR not Linefeeds LF) in the > file are what is causing his problems, but it may be. But, if you want > to get rid of all those extra returns there is an easy way - use 'tr' > This works well: > tr -d "\r" < INPUTFILE > OUTPUTFILE > > If you ftp text from a DOS environment to a UNIX environmtent, > then just set is to ASCII mode (type 'ascii' after the ftp session is > connected) and it will take care of managing the extra characters > very nicely with no other intervention needed. > > ////jerry > > > > > -- > > R > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
