Re: flex: exec failed? (root install/mount)
>As a follow-up and clarification to my previous post, what I would >like to be able to do is to pipe output to a printer, e.g. >ls -l | lpr >This doesn't work for me as I explained previously. Using notepad /P I'll bet it doesn't! From the lpr manpage: No formatting is done -- data is sent "raw". This means your printer has to understand *raw* text, which is what the 'ls' command generates. Many printers can do this, but U'll probably have to play with driver setup to make it work. BTW, I didn't see this thread on gmane yet, so I just started it over. I apologize for messing up threading, but I just *had* to reply. Click to see huge collection of designer watches. http://thirdpartyoffers.juno.com/TGL2131/fc/Ioyw6iie2atUHtI1aAGPjGD6RZew9zmJ8AOq3k8bX2bmvK7k16TTx4/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: pdksh package: Error when issuing a 'typeset -r' statement
Mark J. Reed mail.com> writes: > > I had to modify it somewhat to make it bash-friendly (main culprits: > array syntax, unsupported typeset options, "print", "whence", > coprocesses.) > What do U use to replace ksh coprocesses? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Default Location of Cygwin
Hello: This past weekend, I updated the Cygwin installation on my laptop. It broke big-time, because I have a customization that is apparently no longer allowed. Most installations put the root at c:/cygwin, but I put mine at c:/util/cygwin. My attempts to install from three or four mirrors all put the installation at c:/cygwin anyway, and because I didn't bother clearing out my Cygwin tree first, I didn't notice at first what had happened. Luckily for me, the mounts for /lib/ and /usr/bin/ were also changed, so after a bit I found out what was going on. I'm not going to post my cygcheck -srv here, because I don't want anybody to waste time on my problem yet; I'm still working on it myself. The reason I'm posting this is that I want to give anybody else with a non-standard location for their installation of Cygwin a heads-up. If I run into serious roadblocks, I'll be back! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installer tasks
George alink.co.za> writes: > > Hi All, > > Assuming I wish to copy the c:\cygwin\ directory from one computer to > another, are there any further utilities/updates which I need to do to > ensure it works correctly? > > I have create a script which redoes the mount points (mount -m). > > Is there anything further which I need to do? > > Advice/pointers to documentation appreciated. > > George > > Assuming that the mounts are the same, that should be enough to run most applications (fileutils, etc.). I use a `lite' Cygwin installation on our customer's machines, mostly to make my job easier, but occasionally to script something for a customer. The customer's machines are usually very close to identical from one installation to another, which helps a lot. The only issue I've had is that our latest machines are based on WinXP Embedded, which is on a read-only flash card, so that registry modifications are not persistent across reboots. I haven't put my 'lite' Cygwin installation on any such machine yet, nor have I played around with one yet, but I suppose I'll have to run the mount script from any scripts I may write on such machines (shouldn't present a problem). -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ADMINISTRIVIA] We soon will be blocking legal disclaimers
Matthew Woehlke users.sourceforge.net> writes: > > Long, Phillip GOSS wrote: > > Sigh ... if I had a way, I'd clip out the bozo string my employer's > > email server tacks onto the end of every message. > > nntp://news.gmane.org/gmane.os.cygwin > - \ | | | | | / \-/ \__|__|__|__|__|__|__|__|__|__|_/ (really /bad/ rendition of a _*/huge/*_ grin). OK, I get it! -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Deprecating ntea
Corrina Vinschen wrote: > Hi, > > I think it's time to remove the CYGWIN=ntea setting from Cygwin. > (see http://cygwin.com/cygwin-ug-net/using-cygwinenv.html) > > The reason is that it's just a fake. It fakes POSIX permission bits > by using the "extended attributes" capability built into NTFS. it > also works on FAT by creating a bulky file in the root directory > of the partition. Extended attributes were never implemented on > FAT32, so "ntea" could never work on FAT32. > > So, IMO, ntea is not at all necessary. Given that practically all > Windows systems nowadays are using NTFS and given that NTFS supports > real permissions, not only faked ones, I don't see any need for ntea. > > I even consider ntea as dangerous, because it pretends a security > which doesn't exist. That's what the default ntsec setting is for, > utilizing real permission settings. > > Ok, that's my opinion, which should make it clear that I think > ntea is old cruft which should be removed from Cygwin. > > My questions are thus: Does anybody seriously use ntea? Do you think > you can't live without it? Is using ntsec or just switching off > ntsec no option for you? Why? Or, to phrase it as I did on the > cygwin-developers list: > > Does anybody have a good argument to keep this cruft against all > reason? > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin > to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat Corinna: I agree that 'ntea' should be removed. Besides being dangerous, it can also cause pain. When I first started using Cygwin, I misunderstood the intent of 'ntea' and included it in the setting of my CYGWIN environment variable. Recently, I upgraded one of my installations, and the 'ntea' setting started causing files on some fileservers to which I connect to be treated as device files. Worse yet, these fileservers would occasionally _not_ show up that way, so the intermittent nature of the problem drove me nuts. Eventually I removed the 'ntea' setting, and the problem went away. The lesson I learned was two-fold: (1) Be _very_ careful when changing settings from the default; (2) Go back occasionally to make _/sure/_ that the settings used make sense. OK, anybody other than the brain-dead should have already known number 2, but I'm a little slower than normal... FREE Reminder Service - NEW from AmericanGreetings.com Click HERE and never forget a Birthday or Anniversary again! http://track.juno.com/s/lc?s=197335&u=http://www.americangreetings.com/products/online_calendar.pd?c=uol5752 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: username should be lower-case for $USER
On 10-jan-2007 Dave Korn wrote: >On 09 January 2007 22:15, David Smiley wrote: > >> I forgot to add, I log into a windows domain and so I can't set the case. >> Perhaps this issue only relates to windows domain logins. Maybe they >> are case insensitive because when I log into the domain, I ALWAYS >> specify it in lower case. I don't think I've ever seen it presented >> to me (in Windows) as upper case. Yet in CYGWIN, $USER=DSMILEY. If >> domain logins are case *in*sensitive (appears likely), then it would >> seem to me that it should be normalized to lower-case for use in CYGWIN. > > That's a non-sequitur. It should not be /normalised/; it should be *canonicalised*. And the canonical definition is whatever your domain server reports to cygwin that your user name is. Case-preserving but case-insensitive, remember? > > Since it's insensitive, just hand-edit your /etc/passwd to look the way you like and you're done. > > BTW, I log-on to a domain, and my $USER name has always been lower-case. >It's just the way your admin has created your account. I also log into a domain, and my username there is 'LongPhil'. I have gone through several computers while at this job, and have transferred stuff from one machine to the next each time. Our MIS department allowed _me_ to log in when setting up initially most times, after which they took over and did their thing (although it's almost all automated now; we're at the cutting edge of the late 1980s). Sometimes I logged in as 'LongPhil', and sometimes as 'longphil'; depending on how _I_ logged in, the local profile was created with _that_ _name_ _and_ _case_. Forever afterwards, most, if not all, references to my account made by the system used the same case that I used. If your MIS guys don't allow U to log in to a new machine the first time, maybe they're using all uppercase characters when they log in using your account. The profile would then be 'DSMILEY', not 'dsmiley'. FREE Reminder Service - NEW from AmericanGreetings.com Click HERE and never forget a Birthday or Anniversary again! http://track.juno.com/s/lc?s=197335&u=http://www.americangreetings.com/products/online_calendar.pd?c=uol5752 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
