RE: UNC paths are not supported. Defaulting to Windows directory [and side comment on lists]
Hi, pretty new to the list though have been using cygwin for several months now, first under win98, and now under XP. This may have been covered elsewhere -- sorry, but I doubt I will have enough time to read all the archives of all the lists despite what the warnings say about 'do your research for a day or two, first, then if you can't find the answer post it, and very often have your answer in 5 minutes'. I thought the power of networking was that you didn't have to do *everything* yourself, but you used a network of collective knowledge to do more in less time...if each of us had to write the cygwin toolset ourselves...sheesh! But I know the 'sentiment' of having to rehash the same basic questions again and again -- different people have different levels of patience and tolerance for such. Perhaps a 'newusers' list might allow for the repetitious beginner type questions with those with more patience staying on that list to answer possibly repetitive questions. We don't have an MVP bonus-pat-on-the-head program like in the MS-newsgroups. Sorta a smart idea of MS's -- reward users with 'recognition' as MVP's for helping newbies that might otherwise be asking those questions of MS support people. A surreptitious way to recruit free helpdesk volunteers! :-) But to the main point I found creating a shortcut to bash (and calling it 'cygwin') seems to shortcut the need for using cmd.exe. When I use the provided 'cygwin.bat', I end up with a process tree: EXPLORER: CMD.EXE BASH.EXE --- makes sense, shell cmd calls bash.exe -- but I noticed this annoying feature -- if I had pressed 'control-c' sometime during my bash session, then when I hit control-d to exit from bash, CMD would ask do you really want to terminate this BATCH job (y/n)? Of course since it was at the end of the batch file, it didn't matter y or n, but it did requirement me to select an answer and hit return. Being lazy, my first try at getting around this was to put 'start' in front of the call to bash.exe. On WinXP, (and maybe win2k), the default on this has changed from being a call prog; wait to the equivalent of call prog (no wait), so the main cmd.exe would terminate and I'd be left with only BASH.EXE parented by Explorer. However, the purist in me wanted to know why I should call the CMD shell soley for the purpose of calling the bash shell. So..enter latest method: short cut to bash: in properties I have target: C:\root\bin\bash.exe --login -i (root=cygwinroot), and the start-in dir is set to C:\root\bin -- all like the batchfile would have done -- except this is a shortcut used directly by explorer -- no invocation of CMD -- *SO*, answering the original question: you can specify your starting dir as \\Mydomain (or server)\home and end up with your domain home directory (if you have one) or a exported 'home' dir on a local server. Since CMD is never in the picture, no complaints about it not liking UNC paths. I don't have it setup fully yet, but I'm working toward making extensions .sh, .bsh and .bash all invoke the Bash script interpreter just like visual basic or java script are invoked on their shell languages. Then I should be able to just say foobar, where there is a foobar.sh in my path and I believe is should transparently use bash to interpret the results! As an aid in all this, I put the normal cygwin directories in my path (put them in the 'env' path entry in my current user tree -- I might want to have move them to HKLM so it's available for any user, but since I'm my only user right now, it shouldn't make a difference. I like the idea of creating a Bash Here context dir in the same vein as Command Prompt Here as suggested by Troy, but I'd likely try for a registry solution over the scripting solution -- seems more integrated with Winenv. Anyone see any gotchas with my approach? Is there a reason/need for CMD.EXE to stay resident in memory or be called before bash? thanks, newbie Linda -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: UNC paths are not supported. Defaulting to Windows directory [and side comment on lists]
I think you made several overstatements in your observations below. If you recheck the email archives or even the Cygwin web site, I think you'll find clear explanations of the expectations for list inquiries. Simply put, if any poster cannot make a minimal effort to ensure that the issue in question has not already been addressed in the documentation, email archives, or FAQ, it's often hard for those who read the list regularly to feel sympathy for the poster's plight and take the time to respond (though sometimes a response comes anyway. ;-) ) But, if you do find someplace where the statement is made that posters are expected to do *everything* yourself, let us know. That would be an overstatement on our part that should be corrected. Larry Original Message: - From: linda w \(cyg\) [EMAIL PROTECTED] Date: Fri, 6 Dec 2002 11:02:16 -0800 To: [EMAIL PROTECTED] Subject: RE: UNC paths are not supported. Defaulting to Windows directory [and side comment on lists] Hi, pretty new to the list though have been using cygwin for several months now, first under win98, and now under XP. This may have been covered elsewhere -- sorry, but I doubt I will have enough time to read all the archives of all the lists despite what the warnings say about 'do your research for a day or two, first, then if you can't find the answer post it, and very often have your answer in 5 minutes'. I thought the power of networking was that you didn't have to do *everything* yourself, but you used a network of collective knowledge to do more in less time...if each of us had to write the cygwin toolset ourselves...sheesh! But I know the 'sentiment' of having to rehash the same basic questions again and again -- different people have different levels of patience and tolerance for such. Perhaps a 'newusers' list might allow for the repetitious beginner type questions with those with more patience staying on that list to answer possibly repetitive questions. We don't have an MVP bonus-pat-on-the-head program like in the MS-newsgroups. Sorta a smart idea of MS's -- reward users with 'recognition' as MVP's for helping newbies that might otherwise be asking those questions of MS support people. A surreptitious way to recruit free helpdesk volunteers! :-) mail2web - Check your email from the web at http://mail2web.com/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: UNC paths are not supported. Defaulting to Windows directory [and side comment on lists]
linda w (cyg) wrote: I found creating a shortcut to bash (and calling it 'cygwin') seems to shortcut the need for using cmd.exe. When I use the provided 'cygwin.bat', I end up with a process tree: EXPLORER: CMD.EXE BASH.EXE --- makes sense, shell cmd calls bash.exe -- but I noticed this annoying feature -- if I had pressed 'control-c' sometime during my bash session, then when I hit control-d to exit from bash, CMD would ask do you really want to terminate this BATCH job (y/n)? Of course since it was at the end of the batch file, it didn't matter y or n, but it did requirement me to select an answer and hit return. Yeah, ugly! Kludgy! Then again I find the Windows window that you get from cmd and the default Cygwin.bat to be ugly too. Have you ever tried cut and paste from that sort of window? It works but it's not ideal. Try rxvt! And then you can make an ~/.Xdefaults such as: ! Rxvt defaults ! Global *font: Lucida Console-*-15 *saveLines: 500 *termName: cygwin *scrollBar_right: True *smallfont_key: *bigfont_key: *geometry: 80x24 *loginShell:True Rxvt.background:AntiqueWhite Rxvt.foreground:Black Rxvt.colorBD: Blue Rxvt.colorUL: Red Rxvt.cursorColor: Blue Being lazy, my first try at getting around this was to put 'start' in front of the call to bash.exe. On WinXP, (and maybe win2k), the default on this has changed from being a call prog; wait to the equivalent of call prog (no wait), so the main cmd.exe would terminate and I'd be left with only BASH.EXE parented by Explorer. Yeah. Actually I used to do cmd /c start /b rxvt -e bash --login -i as the command line for my shortcuts and I would set them to running minimized so that you don't see the flicker of the initial cmd window. Now I use /usr/X11R6/bin/run instead of cmd yeilding '/usr/X11R6/bin/run rxvt -title Logging onto local host as adefaria... -e bash --login -i' However, the purist in me wanted to know why I should call the CMD shell soley for the purpose of calling the bash shell. So..enter latest method: short cut to bash: in properties I have target: C:\root\bin\bash.exe --login -i (root=cygwinroot), and the start-in dir is set to C:\root\bin -- all like the batchfile would have done -- except this is a shortcut used directly by explorer -- no invocation of CMD -- *SO*, answering the original question: you can specify your starting dir as \\Mydomain (or server)\home and end up with your domain home directory (if you have one) or a exported 'home' dir on a local server. Since CMD is never in the picture, no complaints about it not liking UNC paths. I tend to prefer mount -bsf //loginserver/homeshare /home. As an aid in all this, I put the normal cygwin directories in my path (put them in the 'env' path entry in my current user tree -- I might want to have move them to HKLM so it's available for any user, but since I'm my only user right now, it shouldn't make a difference. It makes a difference if you want to set up inetutils and allow telnet/rsh access or run other services via inetd. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
