* new install of cygwin with pdksh doesn't work @ 2000-12-20 14:41 David M. Karr 2000-12-20 15:36 ` Christopher Faylor 0 siblings, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-20 14:41 UTC (permalink / raw) To: cygwin I have a relatively recent install of cygwin, along with pdksh-2.14. I have scripts that reference "/bin/ksh" that work fine. Today I've been setting up these tools on another PC, and now when I execute "ksh", I get the following: ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected I'm sure this has something to do with line endings, but I don't understand what has to be done. In case it matters, here are my simple ".bashrc", ".bash_profile", and ".bashvars" files: ----------.bashrc: cut here------ case $- in *i*) if [ "$TERM" = "dumb" ] ; then alias ls="ls -aFC --color" else alias ls="ls -aFC"; fi PS1="[\H;] " . $HOME/.bash_profile ;; esac ----------.bashrc: cut here------ ----------.bash_profile: cut here------ umask 2 . $HOME/.bashvars ----------.bash_profile: cut here------ ----------.bashvars: cut here------ export HISTSIZE=64 unset HISTFILE export ENV=$HOME/.bashrc export PAGER=less export MPAGE="-4 -b Letter -H -X -c -f -z lp" export PATH="$PATH:.://d/dmk/lisp/jde-2.1.8/lisp" export PATH="$PATH:/usr/local/bin" export TP_OPTS="-m DRAFT -i --n -C --f --F -S 2 -4" function dospathinbash () { echo $(cygpath -w $1) | sed -e 's,\\,/,g' } export -f dospathinbash ----------.bashvars: cut here------ -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 14:41 new install of cygwin with pdksh doesn't work David M. Karr @ 2000-12-20 15:36 ` Christopher Faylor 2000-12-20 15:51 ` David M. Karr 0 siblings, 1 reply; 28+ messages in thread From: Christopher Faylor @ 2000-12-20 15:36 UTC (permalink / raw) To: cygwin On Wed, Dec 20, 2000 at 02:39:08PM -0800, David M. Karr wrote: >I have a relatively recent install of cygwin, along with pdksh-2.14. >I have scripts that reference "/bin/ksh" that work fine. > >Today I've been setting up these tools on another PC, and now when I >execute "ksh", I get the following: > > ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected > >I'm sure this has something to do with line endings, but I don't >understand what has to be done. Remove the ^Ms in .bashrc. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 15:36 ` Christopher Faylor @ 2000-12-20 15:51 ` David M. Karr 2000-12-20 16:19 ` Christopher Faylor 0 siblings, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-20 15:51 UTC (permalink / raw) To: cygwin >>>>> "Christopher" == Christopher Faylor <cgf@redhat.com> writes: Christopher> On Wed, Dec 20, 2000 at 02:39:08PM -0800, David M. Karr wrote: >> I have a relatively recent install of cygwin, along with pdksh-2.14. >> I have scripts that reference "/bin/ksh" that work fine. >> >> Today I've been setting up these tools on another PC, and now when I >> execute "ksh", I get the following: >> >> ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected >> >> I'm sure this has something to do with line endings, but I don't >> understand what has to be done. Christopher> Remove the ^Ms in .bashrc. I have none. These are the exact same files I used on the other PC that is working fine. I copied them directly from the PC that doesn't have the problem to the PC that does have the problem, without change. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 15:51 ` David M. Karr @ 2000-12-20 16:19 ` Christopher Faylor 2000-12-20 16:59 ` David M. Karr 0 siblings, 1 reply; 28+ messages in thread From: Christopher Faylor @ 2000-12-20 16:19 UTC (permalink / raw) To: cygwin; +Cc: dkarr On Wed, Dec 20, 2000 at 03:49:32PM -0800, David M. Karr wrote: >>>>>> "Christopher" == Christopher Faylor <cgf@redhat.com> writes: > Christopher> On Wed, Dec 20, 2000 at 02:39:08PM -0800, David M. Karr wrote: > >> I have a relatively recent install of cygwin, along with pdksh-2.14. > >> I have scripts that reference "/bin/ksh" that work fine. > >> > >> Today I've been setting up these tools on another PC, and now when I > >> execute "ksh", I get the following: > >> > >> ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected > >> > >> I'm sure this has something to do with line endings, but I don't > >> understand what has to be done. > > Christopher> Remove the ^Ms in .bashrc. > >I have none. These are the exact same files I used on the other PC >that is working fine. I copied them directly from the PC that doesn't >have the problem to the PC that does have the problem, without change. What are you using to verify this? od -c should show you if your supposition that there are no ^Ms in your file is correct. I would not be surprised to find out that you are wrong and that your .bashrc file has lines that end with ^M^J(\r\n). Editing the file with 'vi -b' should also show any ^Ms. If you really don't have any ^Ms in your file then I am at a loss as to why they would show up in your error output. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 16:19 ` Christopher Faylor @ 2000-12-20 16:59 ` David M. Karr 0 siblings, 0 replies; 28+ messages in thread From: David M. Karr @ 2000-12-20 16:59 UTC (permalink / raw) To: cygwin >>>>> "Christopher" == Christopher Faylor <cgf@redhat.com> writes: Christopher> On Wed, Dec 20, 2000 at 03:49:32PM -0800, David M. Karr wrote: >>>>>>> "Christopher" == Christopher Faylor <cgf@redhat.com> writes: Christopher> On Wed, Dec 20, 2000 at 02:39:08PM -0800, David M. Karr wrote: >> >> I have a relatively recent install of cygwin, along with pdksh-2.14. >> >> I have scripts that reference "/bin/ksh" that work fine. >> >> >> >> Today I've been setting up these tools on another PC, and now when I >> >> execute "ksh", I get the following: >> >> >> >> ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected >> >> >> >> I'm sure this has something to do with line endings, but I don't >> >> understand what has to be done. >> Christopher> Remove the ^Ms in .bashrc. >> >> I have none. These are the exact same files I used on the other PC >> that is working fine. I copied them directly from the PC that doesn't >> have the problem to the PC that does have the problem, without change. Christopher> What are you using to verify this? od -c should show you if your Christopher> supposition that there are no ^Ms in your file is correct. Christopher> I would not be surprised to find out that you are wrong and that your Christopher> .bashrc file has lines that end with ^M^J(\r\n). Christopher> Editing the file with 'vi -b' should also show any ^Ms. Christopher> If you really don't have any ^Ms in your file then I am at a loss as Christopher> to why they would show up in your error output. Ok, now I have a little more useful information. The file does have "\r\n" line endings. Even my original file, from the PC installation which works. So the Cygwin installed on the first PC (from a couple of months ago) can deal with ^Ms, but the new install cannot. I tried creating an ordinary file with Emacs, and it also produces ^Ms (using "vi -b" to verify). I can't use this arrangement if the files produced by Emacs are invalid with Cygwin. Again, I don't have this problem on the original installation. So does this have something to do with one of the initial choices you get when you run "setup", which is "Default Text File Type", choices "Dos" or "Unix"? In order to get this to work, do I have to completely reinstall, selecting "Dos"? I believe that when I installed Cygwin on the first PC, I didn't get those choices. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <Earnie>]
[parent not found: <Boyd's>]
[parent not found: <message>]
[parent not found: <of>]
[parent not found: <"Thu,>]
[parent not found: <"Wed,>]
[parent not found: <20>]
[parent not found: <Dec>]
[parent not found: <2000>]
[parent not found: <16:39:43>]
[parent not found: <-0800>]
[parent not found: <(PST)>]
* Re: new install of cygwin with pdksh doesn't work @ 2000-12-20 16:39 ` Earnie Boyd 2000-12-20 17:36 ` David M. Karr 0 siblings, 1 reply; 28+ messages in thread From: Earnie Boyd @ 2000-12-20 16:39 UTC (permalink / raw) To: David M. Karr, cygwin --- "David M. Karr" <dkarr@tcsi.com> wrote: > >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: > Earnie> --- "David M. Karr" <dkarr@tcsi.com> wrote: > >> > >> I'm sure this has something to do with line endings, but I don't > >> understand what has to be done. > > Earnie> Then use setup to install Cygwin on the other machine. It does all > that needs > Earnie> to be done for those who don't know what to do. > > I did. I installed Cygwin with "setup", then installed "pdksh". The > given error is what I get when I try to execute "ksh". I don't get > that when I try to use "bash". Cygwin bash has been modified to handle this crap. > However, on my own PC, where I > installed Cygwin & pdksh a couple of months ago, I don't see this > problem at all. > Compare the differences of the output of `cygcheck -s -r -v' from both systems. I'm guessing you have mixed text vs binary mounts somewhere. Cheers, ===== Earnie Boyd mailto:earnie_boyd@yahoo.com --- < http://earniesystems.safeshopper.com > --- --- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > --- --- Minimalist GNU for Windows < http://www.mingw.org/ > --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 16:39 ` Earnie Boyd @ 2000-12-20 17:36 ` David M. Karr 2000-12-20 18:18 ` Chris Abbey 0 siblings, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-20 17:36 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 177 bytes --] cygcheck output from \"good\" installation cygcheck output from \"bad\" installation -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple [-- Attachment #2: nachos.cygcheck.out --] [-- Type: text/x-Algol68, Size: 7865 bytes --] Cygnus Win95/NT Configuration Diagnostics Current System Time: Wed Dec 20 17:26:23 2000 WinNT Ver 4.0 build 1381 Service Pack 6 Path: /cygdrive/d/jdk1.3/bin /usr/bin /cygdrive/c/WINNT4/SYSTEM32 /cygdrive/c/WINNT4 /cygdrive/c/atria/bin /cygdrive/d/emacs-20.7/bin /cygdrive/d/gnuserv /cygdrive/c/WINDOWS /cygdrive/c/WINDOWS/COMMAND /cygdrive/c/shiva /cygdrive/c/PROGRA~1/SSHCOM~1/SSHSEC~1 . //d/dmk/lisp/jde-2.1.8/lisp /usr/local/bin SysDir: C:\WINNT4\System32 WinDir: C:\WINNT4 PWD = `/cygdrive/d/dmk/java/propmaster/demo/guitest' USER = `dkarr' MAKE_MODE = `unix' HOME = `/cygdrive/d/dmk' NUMBER_OF_PROCESSORS = `1' PROMPT = `$p$g' LOGONSERVER = `\\ALYSSA' OS2LIBPATH = `C:\WINNT4\system32\os2\dll;' TMPDIR = `/cygdrive/c/TEMP' COMSPEC = `C:\WINNT4\system32\cmd.exe' PAGER = `less' SYSTEMDRIVE = `C:' HOSTNAME = `NACHOS' PROCESSOR_REVISION = `0502' EMACSLOCKDIR = `D:/emacs-20.7/lock' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' COMPUTERNAME = `NACHOS' JAVAHELP_HOME = `d:/jh1.1' WINDIR = `C:\WINNT4' USERPROFILE = `C:\WINNT4\Profiles\dkarr' PROPMASTER_HOME = `d:/dmk/java/propmaster' EMACSPATH = `D:/emacs-20.7/bin' WINBOOTDIR = `C:\WINDOWS' ENV = `/cygdrive/d/dmk/.bashrc' EMACSDOC = `D:/emacs-20.7/etc' MACHTYPE = `i686-pc-cygwin' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 5 Stepping 2, GenuineIntel' EMACS = `t' SBOOTP = `c:\shiva' OS = `Windows_NT' OLDPWD = `/cygdrive/d/dmk' PROCESSOR_ARCHITECTURE = `x86' TEMP = `/cygdrive/c/TEMP' SHIVA = `c:\shiva' TERMCAP = `emacs:co#80:tc=unknown:' PROCESSOR_LEVEL = `6' SYSTEMROOT = `C:\WINNT4' TMP = `/cygdrive/c/TEMP' HOMEDRIVE = `C:' EMACS_DIR = `D:/emacs-20.7' EMACSDATA = `D:/emacs-20.7/etc' SHLVL = `1' TP_OPTS = `-m DRAFT -i --n -C --f --F -S 2 -4' HOMEPATH = `\' USERDOMAIN = `BOTHELL' MPAGE = `-4 -b Letter -H -X -c -f -z lp' SHELL = `bash' USERNAME = `dkarr' EM_PARENT_PROCESS_ID = `340' HOSTTYPE = `i686' EMACSLOADPATH = `D:/emacs-20.7/site-lisp;D:/emacs-20.7/lisp;D:/emacs-20.7/leim' OSTYPE = `cygwin' HISTSIZE = `64' TERM = `emacs' JDKHOME = `d:/jdk1.3' LOG4J_HOME = `d:/log4j-v0.9.1' PATHSEP = `;' _ = `/usr/bin/cygcheck' TZ = `PST8PDT7,M4.1.0/2,M10.5.0/2' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `d:/cygwin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `d:/cygwin/bin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `d:/cygwin/lib' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/A N/A c: hd FAT 2047Mb 83% CP UN d: hd NTFS 6008Mb 40% CP CS UN PA FC e: cd N/A N/A f: cd N/A N/A g: net NTFS 4282Mb 20% CP CS UN PA FC Dev m: net MVFS 1000Mb 50% CP CS CCase d:\cygwin\bin /usr/bin system binmode d:\cygwin\lib /usr/lib system binmode d:\cygwin / system binmode Found: d:\cygwin\bin\bash.exe Found: d:\cygwin\bin\cat.exe Found: d:\cygwin\bin\cpp.exe Found: d:\cygwin\bin\find.exe Found: c:\WINDOWS\COMMAND\find.exe Warning: d:\cygwin\bin\find.exe hides c:\WINDOWS\COMMAND\find.exe Found: d:\cygwin\bin\gcc.exe Found: d:\cygwin\bin\gdb.exe Found: d:\cygwin\bin\ld.exe Found: d:\cygwin\bin\ls.exe Found: d:\cygwin\bin\make.exe Found: d:\cygwin\bin\sh.exe 56k 2000/12/03 d:\cygwin\bin\cygbz21.0.dll - os=4.0 img=1.0 sys=4.0 "cygbz21.0.dll" v0.0 ts=2000/11/20 15:53 45k 2000/12/07 d:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0 "cygform5.dll" v0.0 ts=2000/12/6 22:41 18k 2000/10/23 d:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0 "cyggdbm.dll" v0.0 ts=2000/10/22 19:26 17k 2000/11/30 d:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0 "cyghistory4.dll" v0.0 ts=2000/11/29 18:28 14k 2000/10/23 d:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2000/10/23 12:02 81k 2000/12/05 d:\cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0 "cygitcl30.dll" v0.0 ts=2000/11/25 17:43 35k 2000/12/05 d:\cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0 "cygitk30.dll" v0.0 ts=2000/11/25 17:43 45k 2000/10/22 d:\cygwin\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0 "cygjbig1.dll" v0.0 ts=2000/10/22 16:06 119k 2000/10/23 d:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0 "cygjpeg6b.dll" v0.0 ts=2000/10/22 17:58 26k 2000/12/07 d:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0 "cygmenu5.dll" v0.0 ts=2000/12/6 22:40 159k 2000/12/07 d:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses++5.dll" v0.0 ts=2000/12/6 22:42 225k 2000/12/07 d:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses5.dll" v0.0 ts=2000/12/6 22:39 15k 2000/12/07 d:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0 "cygpanel5.dll" v0.0 ts=2000/12/6 22:40 162k 2000/10/23 d:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0 "cygpng2.dll" v0.0 ts=2000/10/22 17:40 108k 2000/11/30 d:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0 "cygreadline4.dll" v0.0 ts=2000/11/29 18:28 390k 2000/12/05 d:\cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0 "cygtcl80.dll" v0.0 ts=2000/11/25 17:39 5k 2000/12/05 d:\cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0 10k 2000/12/05 d:\cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0 "cygtclreg80.dll" v0.0 ts=2000/11/25 17:39 243k 2000/10/23 d:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0 "cygtiff3.dll" v0.0 ts=2000/10/22 18:14 623k 2000/12/05 d:\cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0 "cygtk80.dll" v0.0 ts=2000/11/25 17:43 41k 2000/11/20 d:\cygwin\bin\cygXpm-noX4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-noX4.dll" v0.0 ts=2000/11/19 18:41 45k 2000/11/20 d:\cygwin\bin\cygXpm-X4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-X4.dll" v0.0 ts=2000/11/19 18:45 49k 2000/10/23 d:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2000/10/22 17:22 609k 2000/11/22 d:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2000/11/21 18:00 Cygwin DLL version info: dll major: 1001 dll minor: 6 dll epoch: 19 dll bad signal mask: 19005 dll old termios: 5 dll malloc env: 28 api major: 0 api minor: 30 shared data: 3 dll identifier: cygwin1 mount registry: 2 cygnus registry name: Cygnus Solutions cygwin registry name: Cygwin program options name: Program Options cygwin mount registry name: mounts v2 cygdrive flags: cygdrive flags cygdrive prefix: cygdrive prefix cygdrive default prefix: build date: Tue Nov 21 21:00:16 EST 2000 shared id: cygwin1S3 Use -h to see help about each section -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) [-- Attachment #3: popcorn.cygcheck.out --] [-- Type: text/x-Algol68, Size: 10289 bytes --] Cygnus Win95/NT Configuration Diagnostics Current System Time: Wed Dec 20 17:18:57 2000 WinNT Ver 4.0 build 1381 Service Pack 6 Path: /cygdrive/d/IONA/BIN /cygdrive/d/JDK1.3/BIN /cygdrive/d/DMK/BIN /usr/bin /cygdrive/c/WINNT/SYSTEM32 /cygdrive/c/WINNT /cygdrive/c/atria/bin /cygdrive/d/winvi /cygdrive/d/emacs-20.7/bin /cygdrive/d/gnuserv /cygdrive/d/mpage /cygdrive/d/miscbins . /cygdrive/d/dmk/lisp/jde-2.1.8/lisp /usr/local/bin SysDir: C:\WINNT\System32 WinDir: C:\WINNT HOME = `/cygdrive/d/dmk' MAKE_MODE = `unix' PWD = `/cygdrive/d/dmk/java' USER = `dkarr' ACME_HOME = `d:/dmk/java' CLASSPATH = `d:\jdk1.3\lib\tools.jar;d:\xerces-1_1_3\xerces.jar;.;d:\jakarta-tomcat\lib\jasper.jar;d:\jakarta-tomcat\lib\xml.jar;d:\jakarta-tomcat\lib\servlet.jar;d:\jakarta-tomcat\lib\webserver.jar;d:\jakarta-tomcat\classes' COMPUTERNAME = `POPCORN' COMSPEC = `C:\WINNT\system32\cmd.exe' EMACS = `t' EMACSDATA = `D:/emacs-20.7/etc' EMACSDOC = `D:/emacs-20.7/etc' EMACSLOADPATH = `D:/emacs-20.7/site-lisp;D:/emacs-20.7/lisp;D:/emacs-20.7/leim' EMACSLOCKDIR = `D:/emacs-20.7/lock' EMACSPATH = `D:/emacs-20.7/bin' EMACS_DIR = `D:/emacs-20.7' EM_PARENT_PROCESS_ID = `597' ENV = `/cygdrive/d/dmk/.bashrc' GETOPT_HOME = `d:/dmk/java/propmaster/java-getopt' HISTSIZE = `64' HOMEDRIVE = `C:' HOMEPATH = `\' HOSTNAME = `POPCORN' HOSTTYPE = `i586' IT_CONFIG_PATH = `d:/Iona/config' IT_ERRORS = `d:\iona\config\ErrorMsgs' JAVAHELP_HOME = `d:/jh1.1' JAVA_HOME = `d:/jdk1.3' JDKHOME = `d:/jdk1.3' JHHOME = `d:/jh1.1' LOG4J_HOME = `d:/log4j-v0.8.5b' LOGONSERVER = `\\ALYSSA' MACHTYPE = `i586-pc-cygwin' MPAGE = `-4 -b Letter -H -X -c -f -z lp' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/cygdrive/d/dmk/java/linebreak' ORBIXWEB_HOME = `d:\Iona' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' OSTYPE = `cygwin' PAGER = `less' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PATHSEP = `;' PRIMARY_CLEARCASE_GROUP = `gtenmo' PRINTER = `"\\ALYSSA\steel"' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 5 Stepping 2, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0502' PROPMASTER_HOME = `d:/dmk/java/propmaster' SHELL = `bash' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEMP = `/cygdrive/c/TEMP' TERM = `emacs' TERMCAP = `emacs:co#81:tc=unknown:' TMP = `/cygdrive/c/TEMP' TMPDIR = `/cygdrive/c/TEMP' TOMCAT_HOME = `d:\jakarta-tomcat' TP_OPTS = `-m DRAFT -i --n -C --f --F -S 2 -4' USERDOMAIN = `BOTHELL' USERNAME = `dkarr' USERPROFILE = `C:\WINNT\Profiles\dkarr' WINDIR = `C:\WINNT' XALAN_HOME = `d:/xalanj-1.2' XERCES_HOME = `d:/xerces-1_1_3' _ = `/usr/bin/cygcheck' dospathinbash = `() { echo $(cygpath -w $1) | sed -e 's,\\,/,g' }' TZ = `PST8PDT7,M4.1.0/2,M10.5.0/2' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000020 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `d:\cygwin' flags = 0x00000002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `d:/cygwin/bin' flags = 0x00000002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `d:/cygwin/lib' flags = 0x00000002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 (default) = `C:' unix = `/' fbinary = 0x00000000 fsilent = 0x00000000 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Installed Components HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Installed Components\d:/cygwin (default) = `20000517' bash = `0002.0004.0001' binutils = `19990818.0002' bison = `0000' byacc = `0000' bzip = `0000' clear = `0001.0000' cygwin = `0001.0001.0002' dejagnu = `0000' diff = `0000' expect = `0000' fileutils = `0000' findutils = `0000' flex = `0000' gawk = `0003.0000.0004' gcc = `0002.0095.0002.0002' gdb = `20000610' gperf = `0000' grep = `0000' groff = `0001.011a.0001' gzip = `0000' inetutils = `0001.0003.0002.0004' less = `0000' libpng = `0001.0000.0006.0001' login = `0001.0003' m = `0000' make = `0003.0079.0002' man = `0001.005g.0002' opengl = `0001.0002.0001.0001' patch = `0000' sed = `0003.0002.0001' shellutils = `0000' tar = `0000' tcltk = `20000610' termcap = `20000618.0001' texinfo = `0000' textutils = `0000' time = `0000' zlib = `0001.0001.0003.0001' HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin B20 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin B20\B20.1 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\13 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\14 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\15 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\16 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\17 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\18 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\19 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1A HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1B HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1C HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1D HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\GNUPro HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\GNUPro\i586-cygwin32 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\GNUPro\i586-cygwin32\i586-cygwin32 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\GNUPro\i586-cygwin32\i586-cygwin32\cygwin-B20.1 (default) = `d:\cygnus-b20\cygwin-b20' HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Cygnus Cygwin B20 (default) = `C:\WINNT\IsUninst.exe -fd:\cygnus-b20\cygwin-b20\Uninst.isu' DisplayName = `Cygwin B20' a: fd N/A N/A c: hd FAT 1498Mb 83% CP UN d: hd NTFS 6557Mb 44% CP CS UN PA FC e: cd N/A N/A f: net NTFS 4282Mb 20% CP CS UN PA FC Dev m: net MVFS 1000Mb 50% CP CS CCase z: net MVFS 1000Mb 50% CP CS CCase d:\cygwin\bin /usr/bin user binmode d:\cygwin\lib /usr/lib user binmode d:\cygwin / user binmode Found: d:\cygwin\bin\bash.exe Found: d:\cygwin\bin\cat.exe Found: d:\cygwin\bin\cpp.exe Found: d:\cygwin\bin\find.exe Found: d:\cygwin\bin\gcc.exe Found: d:\cygwin\bin\gdb.exe Found: d:\cygwin\bin\ld.exe Found: d:\cygwin\bin\ls.exe Found: d:\cygwin\bin\make.exe Found: d:\cygwin\bin\sh.exe 83k 2000/06/11 d:\cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0 "cygitcl30.dll" v0.0 ts=2000/6/10 20:34 35k 2000/06/11 d:\cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0 "cygitk30.dll" v0.0 ts=2000/6/10 20:34 402k 2000/06/11 d:\cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0 "cygtcl80.dll" v0.0 ts=2000/6/10 20:30 5k 2000/06/11 d:\cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0 10k 2000/06/11 d:\cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0 "cygtclreg80.dll" v0.0 ts=2000/6/10 20:30 639k 2000/06/11 d:\cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0 "cygtk80.dll" v0.0 ts=2000/6/10 20:34 586k 2000/08/04 d:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2000/8/3 17:53 Cygwin DLL version info: dll major: 1001 dll minor: 4 dll epoch: 19 dll bad signal mask: 19005 dll old termios: 5 api major: 0 api minor: 26 shared data: 3 dll identifier: cygwin1 mount registry: 2 cygnus registry name: Cygnus Solutions cygwin registry name: Cygwin program options name: Program Options cygwin mount registry name: mounts v2 build date: Thu Aug 3 20:53:46 EDT 2000 CVS tag: cygwin-1-1-4 shared id: cygwin1S3 Use -h to see help about each section ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 17:36 ` David M. Karr @ 2000-12-20 18:18 ` Chris Abbey 0 siblings, 0 replies; 28+ messages in thread From: Chris Abbey @ 2000-12-20 18:18 UTC (permalink / raw) To: cygwin As Earnie suggested, comparing the outputs, with attention to the mount point information will show that /cygdrive/? is mounted differently between the two machines, popcorn (I'll guess is the working one) mount with the flags as 0x0020 while nachos (I'll guess doesn't work) mounts with 0x0022. I'll venture a guess that you're accessing the scripts from /cygdrive/?/... right? (because the other mounts are the same for both. a solution, as Christopher suggested, is to remove the ^M from the files. the easiest way I know of to do this is to pipe the script through "tr -d '\r'" so for example: tr -d '\r' < /cygdrive/c/myscript > /tmp/myscript mv -f /tmp/myscript /cygdrive/c/myscript the other would be to mount the location of the script in an explictly controlled mount point (text mode), or to change the default mount mode. now the forces of openness have a powerful and unexpected new ally http://ibm.com/linux/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work @ 2000-12-21 6:27 ` Earnie Boyd 2000-12-21 8:33 ` David M. Karr 2000-12-21 12:17 ` David M. Karr 0 siblings, 2 replies; 28+ messages in thread From: Earnie Boyd @ 2000-12-21 6:27 UTC (permalink / raw) To: David M. Karr, cygwin --- "David M. Karr" <dkarr@tcsi.com> wrote: > > I don't understand the option of setting text mode mount points. I > have no idea what the ramifications of that would be. > Sigh. How long have you been on this list? I'll now suggest that you refer to the documentation, FAQ and mail archives for which you can find URL pointers at http://cygwin.com . Cheers, ===== Earnie Boyd mailto:earnie_boyd@yahoo.com --- < http://earniesystems.safeshopper.com > --- --- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > --- --- Minimalist GNU for Windows < http://www.mingw.org/ > --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 6:27 ` Earnie Boyd @ 2000-12-21 8:33 ` David M. Karr 2000-12-21 12:17 ` David M. Karr 1 sibling, 0 replies; 28+ messages in thread From: David M. Karr @ 2000-12-21 8:33 UTC (permalink / raw) To: cygwin >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: Earnie> --- "David M. Karr" <dkarr@tcsi.com> wrote: >> >> I don't understand the option of setting text mode mount points. I >> have no idea what the ramifications of that would be. Earnie> Sigh. How long have you been on this list? I'll now suggest that you refer to Earnie> the documentation, FAQ and mail archives for which you can find URL pointers at Earnie> http://cygwin.com . Ok, fine. I apologize. I have unpacked and printed the user's guide. I'll read it. I've already looked through the FAQ and found nothing very useful. I'll look through the mail archives later. In the meantime, can someone verify whether rerunning setup and setting the "DOS" text file type should resolve my problem? When I tried that, it appeared to have no effect. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 6:27 ` Earnie Boyd 2000-12-21 8:33 ` David M. Karr @ 2000-12-21 12:17 ` David M. Karr 2000-12-21 12:48 ` Larry Hall (RFK Partners, Inc) 1 sibling, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-21 12:17 UTC (permalink / raw) To: cygwin >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: Earnie> --- "David M. Karr" <dkarr@tcsi.com> wrote: >> >> I don't understand the option of setting text mode mount points. I >> have no idea what the ramifications of that would be. Earnie> Sigh. How long have you been on this list? I'll now suggest that you refer to Earnie> the documentation, FAQ and mail archives for which you can find URL pointers at Earnie> http://cygwin.com . Ok, after reading the user's guide, I did the following on the new system: mount -t d: /d After this, the output of "mount" is the following: Device Directory Type Flags d:\cygwin\bin /usr/bin system binmode d:\cygwin\lib /usr/lib system binmode d:\cygwin / system binmode d: /d user textmode I now find that my original .bash* files work fine, even with ^Ms. Is this the correct solution for this? All of the files I create will be stored on the D: partition, but I guess any files that I read from directories which map to the three "binmode" mounts will be interpreted differently. I don't know how much of an issue that is. The mount table from the original installation just has the first three, with the only difference being the "Type" is "user" instead of "system". From my reading of the UG, that shouldn't matter. I guess this means that the default mode for unmapped directories is "text" on my original installation, and "binary" for the second installation. Since directories like "d:/dmk" (my home directory) are not covered by the original mount table, I would get the default. So, when I install it again, if I select the "DOS" text file type, I won't have to add this mount to get files on the "D:/" drive to use DOS text file mode, correct? What exactly in the "cygcheck" output (or any other place, for that matter) tells me what the default text file type is? -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 12:17 ` David M. Karr @ 2000-12-21 12:48 ` Larry Hall (RFK Partners, Inc) 0 siblings, 0 replies; 28+ messages in thread From: Larry Hall (RFK Partners, Inc) @ 2000-12-21 12:48 UTC (permalink / raw) To: David M. Karr, cygwin At 03:15 PM 12/21/2000, David M. Karr wrote: > >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: > Earnie> --- "David M. Karr" <dkarr@tcsi.com> wrote: > >> > >> I don't understand the option of setting text mode mount points. I > >> have no idea what the ramifications of that would be. > > Earnie> Sigh. How long have you been on this list? I'll now suggest that you refer to > Earnie> the documentation, FAQ and mail archives for which you can find URL pointers at > Earnie> http://cygwin.com . > >Ok, after reading the user's guide, I did the following on the new >system: > > mount -t d: /d > >After this, the output of "mount" is the following: > > Device Directory Type Flags > d:\cygwin\bin /usr/bin system binmode > d:\cygwin\lib /usr/lib system binmode > d:\cygwin / system binmode > d: /d user textmode > >I now find that my original .bash* files work fine, even with ^Ms. Right. >Is this the correct solution for this? All of the files I create will >be stored on the D: partition, but I guess any files that I read from >directories which map to the three "binmode" mounts will be >interpreted differently. I don't know how much of an issue that is. If you had selected "DOS" originally in setup, all these mounts would have been set to text. If that's what you wanted, set them that way now and you don't need your added entry. Otherwise, mount all the other drives you want to act "DOS" drives with the "text" setting. >The mount table from the original installation just has the first >three, with the only difference being the "Type" is "user" instead of >"system". From my reading of the UG, that shouldn't matter. If you want your settings to affect only you, that's correct. >I guess this means that the default mode for unmapped directories is >"text" on my original installation, and "binary" for the second >installation. Since directories like "d:/dmk" (my home directory) are >not covered by the original mount table, I would get the default. You should be able to reset your default mode for unmapped drives using the --change-cygdrive-prefix setting for mount but specify the "-t" flag too. I haven't tried this myself so I don't know if it actually works. >So, when I install it again, if I select the "DOS" text file type, I >won't have to add this mount to get files on the "D:/" drive to use >DOS text file mode, correct? Right. >What exactly in the "cygcheck" output (or any other place, for that >matter) tells me what the default text file type is? Nothing. cygcheck doesn't output that yet. Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work @ 2000-12-21 13:06 ` Earnie Boyd 2001-01-03 9:56 ` David M. Karr 0 siblings, 1 reply; 28+ messages in thread From: Earnie Boyd @ 2000-12-21 13:06 UTC (permalink / raw) To: Larry Hall (RFK Partners, Inc), David M. Karr, cygwin --- "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote: > > >I guess this means that the default mode for unmapped directories is > >"text" on my original installation, and "binary" for the second > >installation. Since directories like "d:/dmk" (my home directory) are > >not covered by the original mount table, I would get the default. > > > You should be able to reset your default mode for unmapped drives using > the --change-cygdrive-prefix setting for mount but specify the "-t" flag > too. I haven't tried this myself so I don't know if it actually works. > If you chose the "Everyone" radio button, add a -s to that. > > >So, when I install it again, if I select the "DOS" text file type, I > >won't have to add this mount to get files on the "D:/" drive to use > >DOS text file mode, correct? > > > Right. > > > >What exactly in the "cygcheck" output (or any other place, for that > >matter) tells me what the default text file type is? > > > Nothing. cygcheck doesn't output that yet. > That's not true. The output of the registry data can tell you. 0x00000020 is text mode 0x00000022 is binary mode. Cheers, ===== Earnie Boyd mailto:earnie_boyd@yahoo.com --- < http://earniesystems.safeshopper.com > --- --- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > --- --- Minimalist GNU for Windows < http://www.mingw.org/ > --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 13:06 ` Earnie Boyd @ 2001-01-03 9:56 ` David M. Karr 2001-01-03 14:03 ` Larry Hall (RFK Partners, Inc) 0 siblings, 1 reply; 28+ messages in thread From: David M. Karr @ 2001-01-03 9:56 UTC (permalink / raw) To: cygwin >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: Earnie> --- "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote: >> >> >I guess this means that the default mode for unmapped directories is >> >"text" on my original installation, and "binary" for the second >> >installation. Since directories like "d:/dmk" (my home directory) are >> >not covered by the original mount table, I would get the default. >> >> You should be able to reset your default mode for unmapped drives using >> the --change-cygdrive-prefix setting for mount but specify the "-t" flag >> too. I haven't tried this myself so I don't know if it actually works. Earnie> If you chose the "Everyone" radio button, add a -s to that. >> >So, when I install it again, if I select the "DOS" text file type, I >> >won't have to add this mount to get files on the "D:/" drive to use >> >DOS text file mode, correct? >> >> Right. >> >> >What exactly in the "cygcheck" output (or any other place, for that >> >matter) tells me what the default text file type is? >> >> Nothing. cygcheck doesn't output that yet. Earnie> That's not true. The output of the registry data can tell you. 0x00000020 is Earnie> text mode 0x00000022 is binary mode. Sorry for needing to rehash this, but could someone tell me EXACTLY what I need to execute to permanently change the default text file type to DOS? I've tried numerous variations of what's described here, and I can't get it to work on a third installation of this (where the user neglected to select "DOS" on the initial install). I've tried the following: mount -ts --change-cygdrive-prefix /cygdrive mount -ts --change-cygdrive-prefix /d mount -t --change-cygdrive-prefix /d These all just echo the usage message. After the following: mount -t d: /d I get "mount: warning - /d does not exist". Doing "mount" after this shows a new mount entry in textmode, but running "ksh" still gets the usual error. -- =================================================================== David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2001-01-03 9:56 ` David M. Karr @ 2001-01-03 14:03 ` Larry Hall (RFK Partners, Inc) 0 siblings, 0 replies; 28+ messages in thread From: Larry Hall (RFK Partners, Inc) @ 2001-01-03 14:03 UTC (permalink / raw) To: David M. Karr, cygwin At 12:53 PM 1/3/2001, David M. Karr wrote: > >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: > Earnie> --- "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote: > >> > >> >I guess this means that the default mode for unmapped directories is > >> >"text" on my original installation, and "binary" for the second > >> >installation. Since directories like "d:/dmk" (my home directory) are > >> >not covered by the original mount table, I would get the default. > >> > >> You should be able to reset your default mode for unmapped drives using > >> the --change-cygdrive-prefix setting for mount but specify the "-t" flag > >> too. I haven't tried this myself so I don't know if it actually works. > > Earnie> If you chose the "Everyone" radio button, add a -s to that. > > >> >So, when I install it again, if I select the "DOS" text file type, I > >> >won't have to add this mount to get files on the "D:/" drive to use > >> >DOS text file mode, correct? > >> > >> Right. > >> > >> >What exactly in the "cygcheck" output (or any other place, for that > >> >matter) tells me what the default text file type is? > >> > >> Nothing. cygcheck doesn't output that yet. > > Earnie> That's not true. The output of the registry data can tell you. 0x00000020 is > Earnie> text mode 0x00000022 is binary mode. > >Sorry for needing to rehash this, but could someone tell me EXACTLY >what I need to execute to permanently change the default text file >type to DOS? I've tried numerous variations of what's described here, >and I can't get it to work on a third installation of this (where the >user neglected to select "DOS" on the initial install). > >I've tried the following: > >mount -ts --change-cygdrive-prefix /cygdrive >mount -ts --change-cygdrive-prefix /d >mount -t --change-cygdrive-prefix /d > >These all just echo the usage message. AFAICT, mount doesn't accept combined flag options, at least for --change-cygdrive-prefix. Use -t -s. Also its best to make sure that you invoke the --change-cygdrive-prefix option without the -s flag, since you may have set the option for your personal login to something other than text in your attempts. Do the following: mount -t -s --change-cygdrive-prefix /cygdrive mount -t --change-cygdrive-prefix /cygdrive That should do it. BTW, I don't recommend using a path like "/d" for your cygdrive path. Since many people tend to mount their D: drive to /d, this may become confusing for you. Whatever suits you is fine, providing you understand what you're doing. >After the following: > > mount -t d: /d > >I get "mount: warning - /d does not exist". Doing "mount" after this >shows a new mount entry in textmode, but running "ksh" still gets the >usual error. As you said, you got the warning. Mount really wants the POSIX path you mount to exist, but it doesn't force it to. Type "mkdir /d" before the mount to remove this warning. >-- >=================================================================== >David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting >dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004) Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <14:50:18>]
[parent not found: <+0000>]
[parent not found: <(CT0)>]
* Re: new install of cygwin with pdksh doesn't work @ 2000-12-20 19:38 ` Earnie Boyd 2000-12-20 22:54 ` David M. Karr 0 siblings, 1 reply; 28+ messages in thread From: Earnie Boyd @ 2000-12-20 19:38 UTC (permalink / raw) To: Chris Abbey, cygwin --- Chris Abbey <cabbey@bresnanlink.net> wrote: > As Earnie suggested, comparing the outputs, with attention to the mount > point information will show that /cygdrive/? is mounted differently between > the two machines, popcorn (I'll guess is the working one) mount with the > flags as 0x0020 while nachos (I'll guess doesn't work) mounts with 0x0022. > I'll venture a guess that you're accessing the scripts from /cygdrive/?/... > right? (because the other mounts are the same for both. > Yep, that be it. The HOME directory is /cygdrive/d/dmk on both. > a solution, as Christopher suggested, is to remove the ^M from the files. > the easiest way I know of to do this is to pipe the script through "tr -d > '\r'" > so for example: > > tr -d '\r' < /cygdrive/c/myscript > /tmp/myscript > mv -f /tmp/myscript /cygdrive/c/myscript > > the other would be to mount the location of the script in an explictly > controlled mount point (text mode), or to change the default mount > mode. > And the other would be to rerun setup and choose the DOS radio button. Just rerun setup, no need to redownload anything. Cheers, ===== Earnie Boyd mailto:earnie_boyd@yahoo.com --- < http://earniesystems.safeshopper.com > --- --- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > --- --- Minimalist GNU for Windows < http://www.mingw.org/ > --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 19:38 ` Earnie Boyd @ 2000-12-20 22:54 ` David M. Karr 2000-12-21 6:40 ` Markus Hoenicka 0 siblings, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-20 22:54 UTC (permalink / raw) To: cygwin >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: >> a solution, as Christopher suggested, is to remove the ^M from the files. >> the easiest way I know of to do this is to pipe the script through "tr -d >> '\r'" >> so for example: >> >> tr -d '\r' < /cygdrive/c/myscript > /tmp/myscript >> mv -f /tmp/myscript /cygdrive/c/myscript >> >> the other would be to mount the location of the script in an explictly >> controlled mount point (text mode), or to change the default mount >> mode. Earnie> And the other would be to rerun setup and choose the DOS radio button. Just Earnie> rerun setup, no need to redownload anything. As I still have to work with other applications (Emacs, etc.) which will continue to write files with DOS line endings, removing the ^Ms is not a practical option, as I'd have to do that constantly. I understand the option of rerunning setup and setting the DOS radio button, but I actually already tried that. After going through a few dialogs, it said "Nothing to update" (or something like that), and it seemed like it had no effect. However, based on my limited understanding of this, I think this would probably be the best option (if I can get it to work). I don't understand the option of setting text mode mount points. I have no idea what the ramifications of that would be. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 22:54 ` David M. Karr @ 2000-12-21 6:40 ` Markus Hoenicka 2000-12-21 8:48 ` David M. Karr 2000-12-21 16:10 ` Jari Aalto+mail.emacs 0 siblings, 2 replies; 28+ messages in thread From: Markus Hoenicka @ 2000-12-21 6:40 UTC (permalink / raw) To: cygwin David M. Karr writes: > As I still have to work with other applications (Emacs, etc.) which > will continue to write files with DOS line endings, removing the ^Ms > is not a practical option, as I'd have to do that constantly. If Emacs is your major concern, stick the following into your .emacs: (setq-default buffer-file-coding-system 'undecided-unix) New files will then be unix-style. Works great here. regards, Markus -- Markus Hoenicka, PhD UT Houston Medical School Dept. of Integrative Biology and Pharmacology 6431 Fannin MSB4.114 Houston, TX 77030 (713) 500-6313, -7477 (713) 500-7444 (fax) Markus.Hoenicka@uth.tmc.edu http://ourworld.compuserve.com/homepages/hoenicka_markus/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 6:40 ` Markus Hoenicka @ 2000-12-21 8:48 ` David M. Karr 2000-12-21 10:46 ` Larry Hall (RFK Partners, Inc) 2000-12-21 16:10 ` Jari Aalto+mail.emacs 1 sibling, 1 reply; 28+ messages in thread From: David M. Karr @ 2000-12-21 8:48 UTC (permalink / raw) To: cygwin >>>>> "Markus" == Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> writes: Markus> David M. Karr writes: >> As I still have to work with other applications (Emacs, etc.) which >> will continue to write files with DOS line endings, removing the ^Ms >> is not a practical option, as I'd have to do that constantly. Markus> If Emacs is your major concern, stick the following into your .emacs: Markus> (setq-default buffer-file-coding-system 'undecided-unix) Markus> New files will then be unix-style. Works great here. Emacs is a major concern, but not my only one. I don't think it's practical to try to fix every Windows program to produce Unix line endings. I have to focus on getting Cygwin to work with DOS line endings. My original installation works fine. When I ran the second installation, I think I probably left the "Unix" flag on. Is it conceivable that I'll have to uninstall completely so I can reinstall with the "DOS" flag set? Rerunning it and setting that flag had no effect. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 8:48 ` David M. Karr @ 2000-12-21 10:46 ` Larry Hall (RFK Partners, Inc) 0 siblings, 0 replies; 28+ messages in thread From: Larry Hall (RFK Partners, Inc) @ 2000-12-21 10:46 UTC (permalink / raw) To: David M. Karr, cygwin At 11:46 AM 12/21/2000, David M. Karr wrote: > >>>>> "Markus" == Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> writes: > Markus> David M. Karr writes: > >> As I still have to work with other applications (Emacs, etc.) which > >> will continue to write files with DOS line endings, removing the ^Ms > >> is not a practical option, as I'd have to do that constantly. > > Markus> If Emacs is your major concern, stick the following into your .emacs: > > Markus> (setq-default buffer-file-coding-system 'undecided-unix) > > Markus> New files will then be unix-style. Works great here. > >Emacs is a major concern, but not my only one. I don't think it's >practical to try to fix every Windows program to produce Unix line >endings. I have to focus on getting Cygwin to work with DOS line >endings. > >My original installation works fine. When I ran the second >installation, I think I probably left the "Unix" flag on. Is it >conceivable that I'll have to uninstall completely so I can reinstall >with the "DOS" flag set? Rerunning it and setting that flag had no >effect. David, you should find the background to answer your question in the Cygwin User's Guide in the sections discussing mounts and the binary/text issue. Setting the "DOS" flag in the installation only indicates whether mount uses the "-b" (binary) flag or not by default. This applies to all mounts setup makes as well as the /cgydrive notation. There's no other "magic" going on here. Good luck, Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 6:40 ` Markus Hoenicka 2000-12-21 8:48 ` David M. Karr @ 2000-12-21 16:10 ` Jari Aalto+mail.emacs 2000-12-21 16:22 ` Corinna Vinschen ` (2 more replies) 1 sibling, 3 replies; 28+ messages in thread From: Jari Aalto+mail.emacs @ 2000-12-21 16:10 UTC (permalink / raw) To: cygwin * Thu 2000-12-21 Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> list.cygwin * Message-Id: < 14914.6314.575000.452009@gargle.gargle.HOWL > | David M. Karr writes: | | > As I still have to work with other applications (Emacs, etc.) which | > will continue to write files with DOS line endings, removing the ^Ms | > is not a practical option, as I'd have to do that constantly. | | If Emacs is your major concern, stick the following into your .emacs: | | (setq-default buffer-file-coding-system 'undecided-unix) | | New files will then be unix-style. Works great here. But that Idiot CVS pulls the ^M back from he CVS server if you run it in DOS. (under NT Emacs) I would appreciate if bash could tolerate ^M in the end of lines. Jari -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 16:10 ` Jari Aalto+mail.emacs @ 2000-12-21 16:22 ` Corinna Vinschen 2000-12-21 16:32 ` Christopher Faylor 2000-12-21 16:31 ` Christopher Faylor 2000-12-22 6:29 ` Markus Hoenicka 2 siblings, 1 reply; 28+ messages in thread From: Corinna Vinschen @ 2000-12-21 16:22 UTC (permalink / raw) To: cygwin On Friday 22 December 2000 01:11, Jari Aalto+mail.emacs wrote: > I would appreciate if bash could tolerate ^M in the end of lines. It does. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 16:22 ` Corinna Vinschen @ 2000-12-21 16:32 ` Christopher Faylor 0 siblings, 0 replies; 28+ messages in thread From: Christopher Faylor @ 2000-12-21 16:32 UTC (permalink / raw) To: Corinna Vinschen On Fri, Dec 22, 2000 at 01:22:27AM +0100, Corinna Vinschen wrote: >On Friday 22 December 2000 01:11, Jari Aalto+mail.emacs wrote: >> I would appreciate if bash could tolerate ^M in the end of lines. > >It does. > >Corinna LOL. I responded almost exactly the same way before I read your email. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 16:10 ` Jari Aalto+mail.emacs 2000-12-21 16:22 ` Corinna Vinschen @ 2000-12-21 16:31 ` Christopher Faylor 2000-12-22 6:29 ` Markus Hoenicka 2 siblings, 0 replies; 28+ messages in thread From: Christopher Faylor @ 2000-12-21 16:31 UTC (permalink / raw) To: cygwin On Fri, Dec 22, 2000 at 02:11:38AM +0200, Jari Aalto+mail.emacs wrote: >* Thu 2000-12-21 Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> list.cygwin >* Message-Id: < 14914.6314.575000.452009@gargle.gargle.HOWL > >| David M. Karr writes: >| >| > As I still have to work with other applications (Emacs, etc.) which >| > will continue to write files with DOS line endings, removing the ^Ms >| > is not a practical option, as I'd have to do that constantly. >| >| If Emacs is your major concern, stick the following into your .emacs: >| >| (setq-default buffer-file-coding-system 'undecided-unix) >| >| New files will then be unix-style. Works great here. > >But that Idiot CVS pulls the ^M back from he CVS server if you >run it in DOS. (under NT Emacs) > >I would appreciate if bash could tolerate ^M in the end of lines. It can. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-21 16:10 ` Jari Aalto+mail.emacs 2000-12-21 16:22 ` Corinna Vinschen 2000-12-21 16:31 ` Christopher Faylor @ 2000-12-22 6:29 ` Markus Hoenicka 2000-12-23 7:03 ` Jari Aalto+mail.linux 2 siblings, 1 reply; 28+ messages in thread From: Markus Hoenicka @ 2000-12-22 6:29 UTC (permalink / raw) To: cygwin I don't use CVS here. Is there a specific reason why do you run it in DOS under NT Emacs? Bash and ash run just fine as interactive and non-interactive shells in NT Emacs. Markus Jari Aalto+mail.emacs writes: > But that Idiot CVS pulls the ^M back from he CVS server if you > run it in DOS. (under NT Emacs) > > I would appreciate if bash could tolerate ^M in the end of lines. > > Jari > > > -- > Want to unsubscribe from this list? > Check out: http://cygwin.com/ml/#unsubscribe-simple > -- Markus Hoenicka, PhD UT Houston Medical School Dept. of Integrative Biology and Pharmacology 6431 Fannin MSB4.114 Houston, TX 77030 (713) 500-6313, -7477 (713) 500-7444 (fax) Markus.Hoenicka@uth.tmc.edu http://ourworld.compuserve.com/homepages/hoenicka_markus/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-22 6:29 ` Markus Hoenicka @ 2000-12-23 7:03 ` Jari Aalto+mail.linux 0 siblings, 0 replies; 28+ messages in thread From: Jari Aalto+mail.linux @ 2000-12-23 7:03 UTC (permalink / raw) To: cygwin * Fri 2000-12-22 Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> list.cygwin * Message-Id: < 14915.26523.510000.202002@gargle.gargle.HOWL > | I don't use CVS here. Is there a specific reason why do you run it in | DOS under NT Emacs? Bash and ash run just fine as interactive and | non-interactive shells in NT Emacs. I run both: DOS and BASH shells and sometimes I forgot. And pcl-cvs.el, runs Emacs call-process, which I think is native 98 kernel, and CVS yanks the ^M to the perfect unix-files that I store in Linux end. I hate it :-) I want always plain \n, no matter what platform I use CVS on. I have to push the CVS developers more to really understand that "automatic" and non-user-controllable end-of-line conversions are bad. Maybe they hear if I request it long enough, or find the time to offer them a patch...time to go clone myself to get more job done. Jari -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work
@ 2000-12-20 14:48 Earnie Boyd
2000-12-20 14:59 ` David M. Karr
0 siblings, 1 reply; 28+ messages in thread
From: Earnie Boyd @ 2000-12-20 14:48 UTC (permalink / raw)
To: David M. Karr, cygwin
--- "David M. Karr" <dkarr@tcsi.com> wrote:
>
> I'm sure this has something to do with line endings, but I don't
> understand what has to be done.
>
Then use setup to install Cygwin on the other machine. It does all that needs
to be done for those who don't know what to do.
Cheers,
=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com
--- < http://earniesystems.safeshopper.com > ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
--- Minimalist GNU for Windows < http://www.mingw.org/ > ---
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: new install of cygwin with pdksh doesn't work 2000-12-20 14:48 Earnie Boyd @ 2000-12-20 14:59 ` David M. Karr 0 siblings, 0 replies; 28+ messages in thread From: David M. Karr @ 2000-12-20 14:59 UTC (permalink / raw) To: cygwin >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes: Earnie> --- "David M. Karr" <dkarr@tcsi.com> wrote: >> >> I'm sure this has something to do with line endings, but I don't >> understand what has to be done. Earnie> Then use setup to install Cygwin on the other machine. It does all that needs Earnie> to be done for those who don't know what to do. I did. I installed Cygwin with "setup", then installed "pdksh". The given error is what I get when I try to execute "ksh". I don't get that when I try to use "bash". However, on my own PC, where I installed Cygwin & pdksh a couple of months ago, I don't see this problem at all. -- =============================================================================== David M. Karr ; dkarr@tcsi.com ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004) -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <Markus>]
end of thread, other threads:[~2001-01-03 14:03 UTC | newest] Thread overview: 28+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2000-12-20 14:41 new install of cygwin with pdksh doesn't work David M. Karr 2000-12-20 15:36 ` Christopher Faylor 2000-12-20 15:51 ` David M. Karr 2000-12-20 16:19 ` Christopher Faylor 2000-12-20 16:59 ` David M. Karr [not found] <Earnie> [not found] ` <Boyd's> [not found] ` <message> [not found] ` <of> [not found] ` <"Thu,> [not found] ` <"Wed,> [not found] ` <20> [not found] ` <Dec> [not found] ` <2000> [not found] ` <16:39:43> [not found] ` <-0800> [not found] ` <(PST)> 2000-12-20 16:39 ` Earnie Boyd 2000-12-20 17:36 ` David M. Karr 2000-12-20 18:18 ` Chris Abbey 2000-12-21 6:27 ` Earnie Boyd 2000-12-21 8:33 ` David M. Karr 2000-12-21 12:17 ` David M. Karr 2000-12-21 12:48 ` Larry Hall (RFK Partners, Inc) 2000-12-21 13:06 ` Earnie Boyd 2001-01-03 9:56 ` David M. Karr 2001-01-03 14:03 ` Larry Hall (RFK Partners, Inc) [not found] ` <14:50:18> [not found] ` <+0000> [not found] ` <(CT0)> 2000-12-20 19:38 ` Earnie Boyd 2000-12-20 22:54 ` David M. Karr 2000-12-21 6:40 ` Markus Hoenicka 2000-12-21 8:48 ` David M. Karr 2000-12-21 10:46 ` Larry Hall (RFK Partners, Inc) 2000-12-21 16:10 ` Jari Aalto+mail.emacs 2000-12-21 16:22 ` Corinna Vinschen 2000-12-21 16:32 ` Christopher Faylor 2000-12-21 16:31 ` Christopher Faylor 2000-12-22 6:29 ` Markus Hoenicka 2000-12-23 7:03 ` Jari Aalto+mail.linux -- strict thread matches above, loose matches on Subject: below -- 2000-12-20 14:48 Earnie Boyd 2000-12-20 14:59 ` David M. Karr [not found] <Markus>
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).