"Christian MacAuley" <[EMAIL PROTECTED]> wrote:
>I wrote this script to get rid of the ghastly carriage returns in my DOS
>files on my FreeBSD system.
>===
>#!/usr/local/bin/tsh
>
>if test $# -eq 0
> then echo "You didn't enter a filename."
>elif test -f "$1"
> then cat $1 |
Excerpts from linuxchix: 3-May-100 [techtalk] OT - [job opp] o.. by
"Sidra M. S. Vitale"@ope
> Ugh, an off-topic post! Icky-icky poo! Could some kind
> soul let me know what the appropriate forum is for a job
> opp? Or is *this* the appropriate forum?
Surprisingly, it would be [EMAIL PROTECTE
Ugh, an off-topic post! Icky-icky poo! Could some kind
soul let me know what the appropriate forum is for a job
opp? Or is *this* the appropriate forum?
My company is looking to hire some code monkeys --
open-source, perl, html, SQL, and the occasional
communication skill a plus. ;-) I'm ha
> What does signal 11 mean?
Signal 11 is SIGSEGV. It means that the process accessed (tried to, anyway)
memory that it had no access to, either because the address didn't exist in
its address space or because it didn't have the right permissions.
The question you probably wanted answered more
1) I have been trying to reinstall Linux after it crashed on me. I have
tired
Mandrake version 6.1 & 7.0. Both have not worked correctly. I have even
gone as far as low level formating the hard drive to make sure it was not
the problem. After reformatting the hard drive I did install Win98
s
"Shelly L. Hokanson" wrote:
>
> can anyone recommend a good linux mini-distro (single floppy based) for a
> router - (or present your opinions on a few)? i've been playing with coyote
> linux, freesco, and floppyfw - i know coyote is based on the LRP, not sure
> about the others. any suggestions
can anyone recommend a good linux mini-distro (single floppy based) for a
router - (or present your opinions on a few)? i've been playing with coyote
linux, freesco, and floppyfw - i know coyote is based on the LRP, not sure
about the others. any suggestions?
basically i suppose what i'm looking
> The Quick'n'dirty way to do this in vi is as follows:
>
> 1. Open the dos text file in vi.
> vi dosfile.txt
> 2. Type the following:
> :%s/^M//g
> ...where you "compose" the ^M character by pressing Ctrl+v then Ctrl+m
> 3. Save the file:
> :w New.Unix.File.txt
If you have
I wrote this script to get rid of the ghastly carriage returns in my DOS
files on my FreeBSD system. I use it like this:
> nocr dosfile.txt
===
#!/usr/local/bin/tsh
if test $# -eq 0
then echo "You didn't enter a filename."
elif test -f "$1"
then cat $1 | tr -d "\015" >
On Tue, 2 May 2000, Robert Kiesling wrote:
> Usually when translating files from msdos to unix, you have to
> translate at least the line termination characters. Msdos
> uses a carraige return-line feed combination (hex 0xd0xa) to
> terminate lines, while unices use only a line feed. Some util
Thanks everybody for the help. I did find all I wanted to know
on the matter from the suggestions offered.
Deepa
>When I switched from Eudora to Pine, I had to convert all of the files
>from DOS text to Unix text -- the specific problem was something with the
>carriage returns. Since Eudora stores messages in mbox format, everything
>else went fine. Before converting them, Pine saw the mailboxes as just
>one
12 matches
Mail list logo
