public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Rich Caloggero" <rjc@MIT.EDU>
To: <speakup@braille.uwo.ca>
Subject: Samba - windows and unix end-of-line conventions
Date: Wed, 31 Oct 2001 14:00:06 -0500	[thread overview]
Message-ID: <006301c1623e$44a01200$4c015112@vantaa> (raw)

I've finally got Samba working. What I originally invissioned using it for
is to be able to administer a linux server remotely from a windows machine.
I like windows for its file browsing and easy text editing (cursors are
tracked and movement commands are easy and intuitive). I have bad hands so
typing filenames gets tedious, so running linux from the shell gets hard on
the hands. Emacspeak is ok, but I use windows for e-mail and music stuff, so
it just seems natural to use it for my user interface stuff, and linux as my
server machine.

Now for the question:  the unix newline convention is to terminate lines
with just a line feed character (ascii 10). WIndows insists on seeing the
pair of characters ascii 13, followed by ascii 10. Is there a way to have
Samba do some sort of translation when a file is opened from the windows
side, perhaps based on the file extension, which would turn any unix end of
line sequences into windows sequences, and vice versa when the file was
written back to the Linux end? Seems like something someone has implemented,
but where to find it... Seems like something one could do with a shell
script, but how to get Samba to call it...

                    Rich






             reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Rich Caloggero [this message]
 ` Kirk Wood
 Holmes, Steve

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006301c1623e$44a01200$4c015112@vantaa' \
    --to=rjc@mit.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).