* mount command and text/binary mode
@ 2001-04-02 15:46 TaKeDa
2001-04-02 16:07 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 12+ messages in thread
From: TaKeDa @ 2001-04-02 15:46 UTC (permalink / raw)
To: cygwin
Hello cygwin,
$ mount
Device Directory Type Flags
c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
C:\CygWin\home\takeda /home/administrator user binmode
C:\CygWin\bin /usr/bin user binmode
C:\CygWin\lib /usr/lib user binmode
C:\CygWin / user binmode
$ mount --show-cygdrive-prefixes
Prefix Type Flags
/cygdrive user binmode
As you see all mounting points are set into binary mode, but I notice
that cygwin still write files in text mode and this is realy anoying.
Right now I use Windows 2000 Server, I notice this problem with older
cygwin under win98, but it disapears after some time (I guess
upgrading helps, right now I use this same version which was working
correctly under win98)
Right now I'm trying to upgrade and I will see that problem will
exists or not ...
BTW: In registry flags are:
for /cygdrive is 0x22
fo other mount points is 0x02
I check with registry in w98 and is the same ...
BTW2: Why I can't add mount point to system-wide registry location?
When I trying to use arguments -bs it displays help.
BTW3: It's normal that when I'm mounting in place of win32patch
Instead of backslashes I need to use shlashes?
ie. C:\WINDOWS I need write as C:/WINDOWS to make mount command
working.
PS: Please add to CC my e-mail, because I'm not subscribet into this
list.
--
Regards,
TaKeDa mailto:takeda@chore.swiaty.pl
Windows: Just another pain in the glass.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mount command and text/binary mode
2001-04-02 15:46 mount command and text/binary mode TaKeDa
@ 2001-04-02 16:07 ` Larry Hall (RFK Partners, Inc)
2001-04-02 16:37 ` Re[2]: " TaKeDa
0 siblings, 1 reply; 12+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-04-02 16:07 UTC (permalink / raw)
To: TaKeDa, cygwin
At 06:45 PM 4/2/2001, TaKeDa wrote:
>Hello cygwin,
>
>
>
>$ mount
>Device Directory Type Flags
>c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
>C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
>C:\CygWin\home\takeda /home/administrator user binmode
>C:\CygWin\bin /usr/bin user binmode
>C:\CygWin\lib /usr/lib user binmode
>C:\CygWin / user binmode
>
>$ mount --show-cygdrive-prefixes
>Prefix Type Flags
>/cygdrive user binmode
>
>As you see all mounting points are set into binary mode, but I notice
>that cygwin still write files in text mode and this is realy anoying.
Can you give an example and provide the output of cygcheck -s -r -v on the
system from which you ran the example?
>Right now I use Windows 2000 Server, I notice this problem with older
>cygwin under win98, but it disapears after some time (I guess
>upgrading helps, right now I use this same version which was working
>correctly under win98)
>
>Right now I'm trying to upgrade and I will see that problem will
>exists or not ...
>
>BTW: In registry flags are:
>for /cygdrive is 0x22
>fo other mount points is 0x02
>
>I check with registry in w98 and is the same ...
>
>
>BTW2: Why I can't add mount point to system-wide registry location?
>When I trying to use arguments -bs it displays help.
Try mount -b -s <the rest of the line>
>BTW3: It's normal that when I'm mounting in place of win32patch
>Instead of backslashes I need to use shlashes?
>ie. C:\WINDOWS I need write as C:/WINDOWS to make mount command
>working.
In bash/sh, yes. If you want to use backslashes, you need to escape them.
Remember, if you're in a UNIX-like shell, you're in a UNIX-like world!;-)
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] 12+ messages in thread
* Re[2]: mount command and text/binary mode
2001-04-02 16:07 ` Larry Hall (RFK Partners, Inc)
@ 2001-04-02 16:37 ` TaKeDa
2001-04-02 16:43 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 12+ messages in thread
From: TaKeDa @ 2001-04-02 16:37 UTC (permalink / raw)
To: Larry Hall (RFK Partners, Inc); +Cc: cygwin
Hi Inc),
Monday, April 02, 2001, 4:06:40 PM, you wrote:
>>$ mount
>>Device Directory Type Flags
>>c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
>>C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
>>C:\CygWin\home\takeda /home/administrator user binmode
>>C:\CygWin\bin /usr/bin user binmode
>>C:\CygWin\lib /usr/lib user binmode
>>C:\CygWin / user binmode
>>
>>$ mount --show-cygdrive-prefixes
>>Prefix Type Flags
>>/cygdrive user binmode
>>
>>As you see all mounting points are set into binary mode, but I notice
>>that cygwin still write files in text mode and this is realy anoying.
LHRPI> Can you give an example and provide the output of cygcheck -s -r -v on the
LHRPI> system from which you ran the example?
I just upgrade, and some things change, but problem is still there :/
Cygnus Win95/NT Configuration Diagnostics
Current System Time: Mon Apr 2 16:24:29 2001
WinNT Ver 5.0 build 2195 Service Pack 1
Path: /usr/local/bin
/usr/bin
/bin
/cygdrive/d/WINNT/system32
/cygdrive/d/WINNT
/cygdrive/d/WINNT/System32/Wbem
/cygdrive/d/Program Files/Network Associates/PGP
/cygdrive/c/WINDOWS
/cygdrive/c/WINDOWS/COMMAND
/cygdrive/c/COMMAND
/cygdrive/c/SERVER/PERL/BIN
/cygdrive/c/TC/BIN
/cygdrive/d/PROGRA~1/BORLAND/CBUILD~1/BIN
/cygdrive/d/PROGRA~1/BORLAND/CBUILD~1/PROJECTS/BPL
/cygdrive/c/PROGRA~1/TCL/bin
/cygdrive/d/PROGRA~1/TCLPRO1.4/win32-ix86/bin
SysDir: D:\WINNT\System32
WinDir: D:\WINNT
PWD = `/mnt/cgi'
USER = `administrator'
MAKE_MODE = `unix'
HOME = `/home/administrator'
NUMBER_OF_PROCESSORS = `1'
PROMPT = `$P$G'
WSOCK_LOG = `C:\WSOCKLOG\LOG'
LOGONSERVER = `\\TAKEDA'
OS2LIBPATH = `D:\WINNT\system32\os2\dll;'
COMSPEC = `D:\WINNT\system32\cmd.exe'
MXBIN = `D:\Program Files\FireDaemon v0.09c'
!C: = `C:\CygWin\bin'
SYSTEMDRIVE = `D:'
HOSTNAME = `TAKEDA'
PROCESSOR_REVISION = `0600'
DISKEEPERICON = `D:\Program Files\Executive Software\DiskeeperServer\'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
COMPUTERNAME = `TAKEDA'
WINDIR = `D:\WINNT'
USERPROFILE = `D:\Documents and Settings\Administrator.TAKEDA'
PS1 = `\[\033]0;\w\007
\033[32m\]\u@\h \[\033[33m\w\033[0m\]
$ '
BLASTER = `A220 I5 D1 T4'
PROGRAMFILES = `D:\Program Files'
MACHTYPE = `i686-pc-cygwin'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 6 Stepping 0, GenuineIntel'
WSOCK_FLAGS = `FTS'
OS = `Windows_NT'
OLDPWD = `/home/administrator'
PROCESSOR_ARCHITECTURE = `x86'
TEMP = `/cygdrive/d/DOCUME~1/ADMINI~1.TAK/LOCALS~1/Temp'
PROCESSOR_LEVEL = `6'
SYSTEMROOT = `D:\WINNT'
MXHOME = `D:\Program Files\FireDaemon v0.09c'
HOMEDRIVE = `D:'
ALLUSERSPROFILE = `D:\Documents and Settings\All Users.WINNT'
SHLVL = `1'
APPDATA = `D:\Documents and Settings\Administrator.TAKEDA\Application Data'
COMMONPROGRAMFILES = `D:\Program Files\Common Files'
HOMEPATH = `\'
USERDOMAIN = `TAKEDA'
USERNAME = `administrator'
SHELL = `/bin/sh'
HOSTTYPE = `i686'
CVSROOT = `:pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot'
OSTYPE = `cygwin'
TERM = `cygwin'
_ = `/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\mounts v2\/home/administrator
(default) = `C:\CygWin\home\takeda'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/mnt/cgi
(default) = `c:\SERVER\Apache\cgi-bin'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/mnt/egg
(default) = `C:\SERVER\eggdrop\1.5.3'
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
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\13
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\14
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\15
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\16
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\17
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\18
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\19
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1A
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1B
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1C
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1D
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) = `C:\CygWin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:/CygWin/bin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:/CygWin/lib'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
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
a: fd N/A N/A
c: hd FAT32 4235Mb 92% CP UN MAXTOR0
d: hd NTFS 10001Mb 84% CP CS UN PA FC MAXTOR1
e: hd FAT32 9991Mb 50% CP UN MAXTOR2
f: cd N/A N/A
g: cd N/A N/A
h: cd N/A N/A
i: hd FAT 1023Mb 33% CP UN
c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
C:\CygWin\home\takeda /home/administrator user binmode
C:\CygWin\bin /usr/bin system binmode
C:\CygWin\lib /usr/lib system binmode
C:\CygWin / system binmode
Found: C:\CygWin\bin\bash.exe
Found: C:\CygWin\bin\cat.exe
Found: C:\CygWin\bin\cpp.exe
Found: c:\TC\BIN\cpp.exe
Warning: C:\CygWin\bin\cpp.exe hides c:\TC\BIN\cpp.exe
Found: C:\CygWin\bin\find.exe
Found: c:\WINDOWS\COMMAND\find.exe
Warning: C:\CygWin\bin\find.exe hides c:\WINDOWS\COMMAND\find.exe
Found: C:\CygWin\bin\gcc.exe
Found: C:\CygWin\bin\gdb.exe
Found: C:\CygWin\bin\ld.exe
Found: C:\CygWin\bin\ls.exe
Found: C:\CygWin\bin\make.exe
Found: c:\TC\BIN\make.exe
Warning: C:\CygWin\bin\make.exe hides c:\TC\BIN\make.exe
Found: d:\PROGRA~1\BORLAND\CBUILD~1\BIN\make.exe
Warning: C:\CygWin\bin\make.exe hides d:\PROGRA~1\BORLAND\CBUILD~1\BIN\make.exe
Found: C:\CygWin\bin\sh.exe
56k 2000/12/03 C:\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
81k 2000/12/05 C:\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 C:\CygWin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0
"cygitk30.dll" v0.0 ts=2000/11/25 17:43
623k 2000/12/05 C:\CygWin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0
"cygtk80.dll" v0.0 ts=2000/11/25 17:43
18k 2000/10/23 C:\CygWin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm.dll" v0.0 ts=2000/10/22 19:26
14k 2000/10/23 C:\CygWin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
"cygintl.dll" v0.0 ts=2000/10/23 12:02
45k 2000/10/22 C:\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/22 C:\CygWin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
"cygjpeg6b.dll" v0.0 ts=2000/10/22 17:58
163k 2001/02/03 C:\CygWin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0
"cygpng2.dll" v0.0 ts=2001/2/3 13:21
82k 2001/01/21 C:\CygWin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
"cygform5.dll" v0.0 ts=2001/1/21 12:39
53k 2001/01/21 C:\CygWin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
"cygmenu5.dll" v0.0 ts=2001/1/21 12:39
414k 2001/01/21 C:\CygWin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++5.dll" v0.0 ts=2001/1/21 12:40
299k 2001/01/21 C:\CygWin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses5.dll" v0.0 ts=2001/1/21 12:38
34k 2001/01/21 C:\CygWin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
"cygpanel5.dll" v0.0 ts=2001/1/21 12:38
17k 2001/01/07 C:\CygWin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
"cyghistory4.dll" v0.0 ts=2001/1/6 20:34
108k 2001/01/07 C:\CygWin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
"cygreadline4.dll" v0.0 ts=2001/1/6 20:34
243k 2000/10/23 C:\CygWin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
"cygtiff3.dll" v0.0 ts=2000/10/22 18:14
41k 2000/11/20 C:\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 C:\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 2001/02/03 C:\CygWin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2001/2/3 12:35
615k 2001/01/31 C:\CygWin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2001/1/31 7:08
Cygwin DLL version info:
dll major: 1001
dll minor: 8
dll epoch: 19
dll bad signal mask: 19005
dll old termios: 5
dll malloc env: 28
api major: 0
api minor: 34
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: Wed Jan 31 10:08:38 EST 2001
shared id: cygwin1S3
615k 2001/01/31 c:\COMMAND\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2001/1/31 7:08
Cygwin DLL version info:
dll major: 1001
dll minor: 8
dll epoch: 19
dll bad signal mask: 19005
dll old termios: 5
dll malloc env: 28
api major: 0
api minor: 34
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: Wed Jan 31 10:08:38 EST 2001
shared id: cygwin1S3
Use -h to see help about each section
>>Right now I use Windows 2000 Server, I notice this problem with older
>>cygwin under win98, but it disapears after some time (I guess
>>upgrading helps, right now I use this same version which was working
>>correctly under win98)
>>Right now I'm trying to upgrade and I will see that problem will
>>exists or not ...
>>BTW: In registry flags are:
>>for /cygdrive is 0x22
>>fo other mount points is 0x02
>>I check with registry in w98 and is the same ...
>>BTW2: Why I can't add mount point to system-wide registry location?
>>When I trying to use arguments -bs it displays help.
LHRPI> Try mount -b -s <the rest of the line>
It works, thank you.
Because of this:
"usage mount [-bfstux] <win32path> <posixpath>"
I understand syntax incorrectly.
>>BTW3: It's normal that when I'm mounting in place of win32patch
>>Instead of backslashes I need to use shlashes?
>>ie. C:\WINDOWS I need write as C:/WINDOWS to make mount command
>>working.
LHRPI> In bash/sh, yes. If you want to use backslashes, you need to escape them.
LHRPI> Remember, if you're in a UNIX-like shell, you're in a UNIX-like world!;-)
Ok, I just say that because I was thinking that problem can be there.
--
Pozdrawiam,
TaKeDa mailto:takeda@chore.swiaty.pl
ASCII stupid question, get a stupid ANSI!
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re[2]: mount command and text/binary mode
2001-04-02 16:37 ` Re[2]: " TaKeDa
@ 2001-04-02 16:43 ` Larry Hall (RFK Partners, Inc)
2001-04-02 18:09 ` Michael A. Chase
2001-04-02 18:30 ` Re[3]: " TaKeDa
0 siblings, 2 replies; 12+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-04-02 16:43 UTC (permalink / raw)
To: TaKeDa; +Cc: cygwin
At 07:32 PM 4/2/2001, TaKeDa wrote:
>Hi Inc),
>
>Monday, April 02, 2001, 4:06:40 PM, you wrote:
>
> >>$ mount
> >>Device Directory Type Flags
> >>c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
> >>C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
> >>C:\CygWin\home\takeda /home/administrator user binmode
> >>C:\CygWin\bin /usr/bin user binmode
> >>C:\CygWin\lib /usr/lib user binmode
> >>C:\CygWin / user binmode
> >>
> >>$ mount --show-cygdrive-prefixes
> >>Prefix Type Flags
> >>/cygdrive user binmode
> >>
> >>As you see all mounting points are set into binary mode, but I notice
> >>that cygwin still write files in text mode and this is realy anoying.
>
>
>LHRPI> Can you give an example and provide the output of cygcheck -s -r -v on the
>LHRPI> system from which you ran the example?
>
>I just upgrade, and some things change, but problem is still there :/
>
And the example that shows the problem?
<snip>
> 615k 2001/01/31 C:\CygWin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
> Cygwin DLL version info:
> dll major: 1001
> dll minor: 8
> dll epoch: 19
> dll bad signal mask: 19005
> dll old termios: 5
> dll malloc env: 28
> api major: 0
> api minor: 34
> 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: Wed Jan 31 10:08:38 EST 2001
> shared id: cygwin1S3
>
> 615k 2001/01/31 c:\COMMAND\cygwin1.dll - os=4.0 img=1.0 sys=4.0
> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
> Cygwin DLL version info:
> dll major: 1001
> dll minor: 8
> dll epoch: 19
> dll bad signal mask: 19005
> dll old termios: 5
> dll malloc env: 28
> api major: 0
> api minor: 34
> 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: Wed Jan 31 10:08:38 EST 2001
> shared id: cygwin1S3
>
>Use -h to see help about each section
Get rid of one of these. Never keep duplicate cygwin1.dlls on your system.
> >>BTW2: Why I can't add mount point to system-wide registry location?
> >>When I trying to use arguments -bs it displays help.
>
>LHRPI> Try mount -b -s <the rest of the line>
>It works, thank you.
>Because of this:
>"usage mount [-bfstux] <win32path> <posixpath>"
>I understand syntax incorrectly.
Yes, this is a "bug".
> >>BTW3: It's normal that when I'm mounting in place of win32patch
> >>Instead of backslashes I need to use shlashes?
> >>ie. C:\WINDOWS I need write as C:/WINDOWS to make mount command
> >>working.
>LHRPI> In bash/sh, yes. If you want to use backslashes, you need to escape them.
>LHRPI> Remember, if you're in a UNIX-like shell, you're in a UNIX-like world!;-)
>
>Ok, I just say that because I was thinking that problem can be there.
Yes, this is a common cockpit error we see on this list.
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] 12+ messages in thread
* Re: Re[2]: mount command and text/binary mode
2001-04-02 16:43 ` Larry Hall (RFK Partners, Inc)
@ 2001-04-02 18:09 ` Michael A. Chase
2001-04-02 18:36 ` Christopher Faylor
2001-04-02 18:30 ` Re[3]: " TaKeDa
1 sibling, 1 reply; 12+ messages in thread
From: Michael A. Chase @ 2001-04-02 18:09 UTC (permalink / raw)
To: TaKeDa, Larry Hall (RFK Partners, Inc); +Cc: cygwin
----- Original Message -----
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "TaKeDa" <takeda@chore.swiaty.pl>
Cc: <cygwin@cygwin.com>
Sent: Monday, April 02, 2001 4:42 PM
Subject: Re[2]: mount command and text/binary mode
> At 07:32 PM 4/2/2001, TaKeDa wrote:
> >Hi Inc),
> >
> >Monday, April 02, 2001, 4:06:40 PM, you wrote:
> >
> >LHRPI> Try mount -b -s <the rest of the line>
> >It works, thank you.
> >Because of this:
> >"usage mount [-bfstux] <win32path> <posixpath>"
> >I understand syntax incorrectly.
>
>
> Yes, this is a "bug".
Since the options aren't groupable it looks like it should be:
usage mount [options] <win32path> <posixpath>
. . . (option descriptions)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re[3]: mount command and text/binary mode
2001-04-02 16:43 ` Larry Hall (RFK Partners, Inc)
2001-04-02 18:09 ` Michael A. Chase
@ 2001-04-02 18:30 ` TaKeDa
2001-04-02 18:38 ` Christopher Faylor
2001-04-02 18:46 ` Re[3]: " Larry Hall (RFK Partners, Inc)
1 sibling, 2 replies; 12+ messages in thread
From: TaKeDa @ 2001-04-02 18:30 UTC (permalink / raw)
To: Larry Hall (RFK Partners, Inc); +Cc: cygwin
Hi Inc),
Monday, April 02, 2001, 4:42:25 PM, you wrote:
>> >>$ mount
>> >>Device Directory Type Flags
>> >>c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
>> >>C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
>> >>C:\CygWin\home\takeda /home/administrator user binmode
>> >>C:\CygWin\bin /usr/bin user binmode
>> >>C:\CygWin\lib /usr/lib user binmode
>> >>C:\CygWin / user binmode
>> >>
>> >>$ mount --show-cygdrive-prefixes
>> >>Prefix Type Flags
>> >>/cygdrive user binmode
>> >>
>> >>As you see all mounting points are set into binary mode, but I notice
>> >>that cygwin still write files in text mode and this is realy anoying.
>>LHRPI> Can you give an example and provide the output of cygcheck -s -r -v on the
>>LHRPI> system from which you ran the example?
>>I just upgrade, and some things change, but problem is still there :/
LHRPI> And the example that shows the problem?
I notice problem witch patch command (when I was use
patch -p1 <file.patch
Modiffied files was in have \r\n (but before modiffication they was
used regular \n - patch also was in unix format)
I check right now and this is working now (probably upgrade helps).
Another thing was mine program (it was waiting for stdin and sends
encrypted file to output) in command line works correctly, but from
tcl interpreter it isn't.
Procedure for encrypting/decrypting looks like (Main(blowfish) is just
patch to file):
proc bfenc {key filein fileout} {
variable Main
set length [file size $filein]
set in [open $filein RDONLY]
fconfigure $in -blocking 1 -buffering full -translation binary
binary scan [read $in $length] H* file
close $in
if [catch {open "|$Main(blowfish) 0 $length >$fileout" WRONLY} blowfish] {
error "Can't execute $Main(blowfish): $blowfish"
} else {
fconfigure $blowfish -blocking 1 -buffering full -translation binary
puts $blowfish $key
puts -nonewline $blowfish [binary format H* $file]
close $blowfish
}
}
proc bfdec {key filein fileout} {
variable Main
set length [file size $filein]
set in [open $filein RDONLY]
fconfigure $in -blocking 1 -buffering full -translation binary
binary scan [read $in $length] H* file
close $in
if [catch {open "|$Main(blowfish) 1 $length >$fileout" WRONLY} blowfish] {
error "Can't execute $Main(blowfish): $blowfish"
} else {
fconfigure $blowfish -blocking 1 -buffering full -translation binary
puts $blowfish $key
puts -nonewline $blowfish [binary format H* $file]
close $blowfish
}
}
Can't somebody figure out where is error? or maybe is something with
tcl? :(((
>> 615k 2001/01/31 C:\CygWin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
>> Cygwin DLL version info:
>> dll major: 1001
>> dll minor: 8
>> dll epoch: 19
>> dll bad signal mask: 19005
>> dll old termios: 5
>> dll malloc env: 28
>> api major: 0
>> api minor: 34
>> 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: Wed Jan 31 10:08:38 EST 2001
>> shared id: cygwin1S3
>>
>> 615k 2001/01/31 c:\COMMAND\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
>> Cygwin DLL version info:
>> dll major: 1001
>> dll minor: 8
>> dll epoch: 19
>> dll bad signal mask: 19005
>> dll old termios: 5
>> dll malloc env: 28
>> api major: 0
>> api minor: 34
>> 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: Wed Jan 31 10:08:38 EST 2001
>> shared id: cygwin1S3
>>
>>Use -h to see help about each section
LHRPI> Get rid of one of these. Never keep duplicate cygwin1.dlls on your system.
ok :)
>> >>BTW2: Why I can't add mount point to system-wide registry location?
>> >>When I trying to use arguments -bs it displays help.
>>LHRPI> Try mount -b -s <the rest of the line>
>>It works, thank you.
>>Because of this:
>>"usage mount [-bfstux] <win32path> <posixpath>"
>>I understand syntax incorrectly.
LHRPI> Yes, this is a "bug".
PS: Please write my mail in CC: (I'm not subscribed in list)
--
Best Regards,
TaKeDa mailto:takeda@chore.swiaty.pl
Programmers don't die, they just GOSUB without RETURN.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Re[2]: mount command and text/binary mode
2001-04-02 18:09 ` Michael A. Chase
@ 2001-04-02 18:36 ` Christopher Faylor
0 siblings, 0 replies; 12+ messages in thread
From: Christopher Faylor @ 2001-04-02 18:36 UTC (permalink / raw)
To: cygwin
On Mon, Apr 02, 2001 at 05:59:15PM -0700, Michael A. Chase wrote:
>----- Original Message -----
>From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
>To: "TaKeDa" <takeda@chore.swiaty.pl>
>Cc: <cygwin@cygwin.com>
>Sent: Monday, April 02, 2001 4:42 PM
>Subject: Re[2]: mount command and text/binary mode
>
>
>> At 07:32 PM 4/2/2001, TaKeDa wrote:
>> >Hi Inc),
>> >
>> >Monday, April 02, 2001, 4:06:40 PM, you wrote:
>> >
>> >LHRPI> Try mount -b -s <the rest of the line>
>> >It works, thank you.
>> >Because of this:
>> >"usage mount [-bfstux] <win32path> <posixpath>"
>> >I understand syntax incorrectly.
>>
>>
>> Yes, this is a "bug".
>
>Since the options aren't groupable it looks like it should be:
>
>usage mount [options] <win32path> <posixpath>
>. . . (option descriptions)
Check out the todo list at http://cygwin.com/ .
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mount command and text/binary mode
2001-04-02 18:30 ` Re[3]: " TaKeDa
@ 2001-04-02 18:38 ` Christopher Faylor
2001-04-03 4:52 ` Earnie Boyd
2001-04-02 18:46 ` Re[3]: " Larry Hall (RFK Partners, Inc)
1 sibling, 1 reply; 12+ messages in thread
From: Christopher Faylor @ 2001-04-02 18:38 UTC (permalink / raw)
To: TaKeDa; +Cc: cygwin
On Mon, Apr 02, 2001 at 06:29:53PM -0700, TaKeDa wrote:
>I notice problem witch patch command (when I was use
>patch -p1 <file.patch
>
>Modiffied files was in have \r\n (but before modiffication they was
>used regular \n - patch also was in unix format)
>
>I check right now and this is working now (probably upgrade helps).
No probably about it.
>Another thing was mine program (it was waiting for stdin and sends
>encrypted file to output) in command line works correctly, but from
>tcl interpreter it isn't.
tcl isn't a cygwin program, unfortunately. So it doesn't adhere to
cygwin rules.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re[3]: mount command and text/binary mode
2001-04-02 18:30 ` Re[3]: " TaKeDa
2001-04-02 18:38 ` Christopher Faylor
@ 2001-04-02 18:46 ` Larry Hall (RFK Partners, Inc)
1 sibling, 0 replies; 12+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-04-02 18:46 UTC (permalink / raw)
To: TaKeDa; +Cc: cygwin
At 09:29 PM 4/2/2001, TaKeDa wrote:
>Can't somebody figure out where is error? or maybe is something with
>tcl? :(((
I expect that's the case.
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] 12+ messages in thread
* Re: mount command and text/binary mode
2001-04-02 18:38 ` Christopher Faylor
@ 2001-04-03 4:52 ` Earnie Boyd
2001-04-03 5:44 ` egor duda
0 siblings, 1 reply; 12+ messages in thread
From: Earnie Boyd @ 2001-04-03 4:52 UTC (permalink / raw)
To: cygwin; +Cc: TaKeDa
Christopher Faylor wrote:
>
> On Mon, Apr 02, 2001 at 06:29:53PM -0700, TaKeDa wrote:
>
> >Another thing was mine program (it was waiting for stdin and sends
> >encrypted file to output) in command line works correctly, but from
> >tcl interpreter it isn't.
>
> tcl isn't a cygwin program, unfortunately. So it doesn't adhere to
> cygwin rules.
>
Correct, however, you may be helped by adding the `binmode' option to
the CYGWIN environment variable before starting any Cygwin processes.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mount command and text/binary mode
2001-04-03 4:52 ` Earnie Boyd
@ 2001-04-03 5:44 ` egor duda
2001-04-03 7:27 ` Christopher Faylor
0 siblings, 1 reply; 12+ messages in thread
From: egor duda @ 2001-04-03 5:44 UTC (permalink / raw)
To: Earnie Boyd; +Cc: cygwin, TaKeDa
Hi!
Tuesday, 03 April, 2001 Earnie Boyd earnie_boyd@yahoo.com wrote:
>> >Another thing was mine program (it was waiting for stdin and sends
>> >encrypted file to output) in command line works correctly, but from
>> >tcl interpreter it isn't.
>>
>> tcl isn't a cygwin program, unfortunately. So it doesn't adhere to
>> cygwin rules.
>>
EB> Correct, however, you may be helped by adding the `binmode' option to
EB> the CYGWIN environment variable before starting any Cygwin processes.
it's also possible to set modes in your program on per file basis, like this:
#include <io.h>
#include <sys/fcntl.h>
...
int main (int argc, char** argv)
{
...
setmode (0, O_BINARY); /* set stdin mode to binary */
setmode (1, O_TEXT);
setmode (2, O_TEXT); /* while stdout and stderr to text */
...
}
of course, in your case, particular modes may be different.
egor. mailto:deo@logos-m.ru icq 5165414 fidonet 2:5020/496.19
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: mount command and text/binary mode
2001-04-03 5:44 ` egor duda
@ 2001-04-03 7:27 ` Christopher Faylor
0 siblings, 0 replies; 12+ messages in thread
From: Christopher Faylor @ 2001-04-03 7:27 UTC (permalink / raw)
To: cygwin
On Tue, Apr 03, 2001 at 04:41:50PM +0400, egor duda wrote:
>Hi!
>
>Tuesday, 03 April, 2001 Earnie Boyd earnie_boyd@yahoo.com wrote:
>
>>> >Another thing was mine program (it was waiting for stdin and sends
>>> >encrypted file to output) in command line works correctly, but from
>>> >tcl interpreter it isn't.
>>>
>>> tcl isn't a cygwin program, unfortunately. So it doesn't adhere to
>>> cygwin rules.
>>>
>
>EB> Correct, however, you may be helped by adding the `binmode' option to
>EB> the CYGWIN environment variable before starting any Cygwin processes.
>
>it's also possible to set modes in your program on per file basis, like this:
>
>#include <io.h>
>#include <sys/fcntl.h>
>...
>int main (int argc, char** argv)
>{
> ...
> setmode (0, O_BINARY); /* set stdin mode to binary */
> setmode (1, O_TEXT);
> setmode (2, O_TEXT); /* while stdout and stderr to text */
> ...
>}
>
>of course, in your case, particular modes may be different.
I don't see how either of these suggestions is going to help. TCL IS NOT
A CYGWIN PROGRAM. Setting the CYGWIN environment variable is not going
to affect a non-Cygwin program. A C program snippet is not going to help
with tcl.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2001-04-03 7:27 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-02 15:46 mount command and text/binary mode TaKeDa
2001-04-02 16:07 ` Larry Hall (RFK Partners, Inc)
2001-04-02 16:37 ` Re[2]: " TaKeDa
2001-04-02 16:43 ` Larry Hall (RFK Partners, Inc)
2001-04-02 18:09 ` Michael A. Chase
2001-04-02 18:36 ` Christopher Faylor
2001-04-02 18:30 ` Re[3]: " TaKeDa
2001-04-02 18:38 ` Christopher Faylor
2001-04-03 4:52 ` Earnie Boyd
2001-04-03 5:44 ` egor duda
2001-04-03 7:27 ` Christopher Faylor
2001-04-02 18:46 ` Re[3]: " Larry Hall (RFK Partners, Inc)
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).