printf \n|perl -pe '1;'|od -a #perl 5.8 converts to *DOS* text :-

IMHO the perl v5.6.0 that came w/1.3.20 worked correctly. In the test case below perl 5.8.0 is converting UNIX text to DOS text - (this is breaking our old scripts). Comments please. -- thanks/regards, Tom # run below to get my address: perl -e 'print unpack(u,

Re: {par script path}: {chld script path}: /bin/bash: bad interpreter: Permission denied

Igor: Thanks for your help. If your right we'd have to update several scripts to eliminate drive letters in the path. Contrary to your hint is this snippet from the FAQ: ( http://cygwin.com/cygwin-ug-net/using.html#USING-PATHNAMES ): Mapping path names Introduction Cygwin

{par script path}: {chld script path}: /bin/bash: bad interpreter: Permission denied

As always thanks for continually improving cygwin; it's a wonderful set of tools. Here's an error message example: /adm/bin/ccm_build_scripts/run_large_nb.sh: s:/adm/bin/ccm_build_scripts/run_nb.sh: /bin/bash: bad interpreter: Permission denied run_nb.sh aborts immediately, not executing

simple/free CLI tool to new Windows 2000 inherited ACLs correctly??

Greetings: I understand this is a slightly off topic question; I hope you take it as complement .. I've already looked at xcacls, showacls, dumpsec, setacl, cygwin getfacl. I'm looking for a command line tool to dump the Windows 2000 acls for a directory, with an indication of whether the ACE

postinstall/profile.sh: pls consider testing for preexisting symbolic link

how about: if [ ! -f /etc/profile -a ! -L /etc/profile]; then cp -a /etc/profile.default /etc/profile fi Rightly or wrongly I setup /etc/profile as a symblic link to a network drive version of profile, so that several hosts share the same file. The postinstall/profile.sh

Re: is inetd telnet slowness fixed? (conflict w/FTP Software's InterDrive?)

Dan: I suspect your right. I have FTP Software's InterDrive 4.0 (a NFS client) loaded on my PC. Unfortunately I need this for work. We've had other problems with InterDrive interfering with network printers. ssh, ftpd, cron, and rlogin work fine, so I'll cope ;- thanks very much for your

Re: cmd.exe as telnetd login shell: mode con LINES=24 COLS=80 has no effect..

why cmd.exe does not understand the window size Ross: I talked to a support person at ataman.com about their telnetd product. My interpretation is that cmd.exe has multiple (simultaneous?) modes of operation: o it can open STDERR/STDIN/STDOUT like a normal character based application.

cmd.exe as telnetd login shell: mode con LINES=24 COLS=80 has no effect..

pls excuse me for restarting/updating my own unanswered thread.. Hello: A couple of people that insist on using cmd.exe as their login shell when they telnet or ssh to our w2kserver. When the login shell is set to /cygdrive/c/winnt/system32/cmd, and putty is the telnet client: 1)

usg cmd.exe as login shell: more not sensing #LINES; how2 enable history..

Hello: There are a couple of people in our group that insist on using cmd.exe as their login shell when they telnet or ssh to our windows 2000 server. When the login shell is set to /cygdrive/c/winnt/system32/cmd here are the challenges: 1) more foo does not work, it has no clue