Re: [ANNOUNCEMENT] New: sl-5.02-1
On 09/01/2015 07:13 PM, Jared Buck wrote: [...] > On Tue, Sep 1, 2015 at 4:07 PM, Yaakov Selkowitz > wrote: >> The following package has been added to the Cygwin distribution: >> >> * sl-5.02-1 >> >> SL (Steam Locomotive) runs across your terminal when you type 'sl' >> as you meant to type 'ls'. It's just a joke command, and not useful at >> all. Damnit Yaakov! You beat me to packaging this. I guess my packaging train wasn't fast enough. These are really funny btw: http://manpages.org/sl/6 https://github.com/mtoyoda/sl/pull/31 https://github.com/mtoyoda/sl/pulls From the current (properly translated into English) manpage: > BUGS > It sometimes lists directory contents. -Mike signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCEMENT] New: sl-5.02-1
LOL a little funny stuff isn't a bad idea at all :) Jared On Tue, Sep 1, 2015 at 4:07 PM, Yaakov Selkowitz wrote: > The following package has been added to the Cygwin distribution: > > * sl-5.02-1 > > SL (Steam Locomotive) runs across your terminal when you type 'sl' > as you meant to type 'ls'. It's just a joke command, and not useful at > all. > > -- > Yaakov > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New: sl-5.02-1
The following package has been added to the Cygwin distribution: * sl-5.02-1 SL (Steam Locomotive) runs across your terminal when you type 'sl' as you meant to type 'ls'. It's just a joke command, and not useful at all. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: lighttpd-1.4.37-1
The following package has been updated in the Cygwin distribution: * lighttpd-1.4.37-1 Security, speed, compliance, and flexibility -- all of these describe lighttpd which is rapidly redefining efficiency of a webserver; as it is designed and optimized for high performance environments. With a small memory footprint compared to other web-servers, effective management of the cpu-load, and advanced feature set, lighttpd is the perfect solution for every server that is suffering load problems. This is an update to the latest upstream release: http://www.lighttpd.net/2015/8/30/1.4.37/ -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: "permission denied" issues when removing files/folders created by cygwin
On Sep 1 13:05, Michael Enright wrote: > On Tue, Sep 1, 2015 at 12:48 PM, Roger Pack wrote: > > It appears the problem lies with creating a file named "NUL" windows > > utilities just don't know how to deal with it (you can recreate it by > > creating a folder, then from cygwin bash $ touch NUL) then try and > > remove the folder with windows explorer. > > The utilities "know" how to deal with it, given their design: > http://blogs.msdn.com/b/oldnewthing/archive/2003/10/22/55388.aspx And then there's https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-dosdevices You can create and delete those files even in CMD, btw. You just have to use the long pathname prefix "\\?\", e.g.: bash$ cmd /c 'echo foo > \\?\c:\cygwin64\home\corinna\nul' bash$ ls -l nul -rwxr-xr-x 1 corinna vinschen 6 Sep 1 22:30 nul delete with bash$ rm nul or bash$ cmd /c 'del \\?\c:\cygwin64\home\corinna\nul' Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgphMGYMkB3ef.pgp Description: PGP signature
Re: Subversion crashes
Op Thu, 27 Aug 2015 15:59:25 -0700 schreef David Rothenberger : > I can replicate the error if I set HOME to a share like //xxx/yyy, > such as yours is set. If I use a local path, or mount the share to a > local path and then set HOME to that, it works correctly. > > I may or may not try to debug this and fix it in Subversion, but > hopefully this will provide you with a reasonable work-around. Local path works, thanks for the tip. I'll have a go at finding the root of the problem during lunch break(s). -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: "permission denied" issues when removing files/folders created by cygwin
On Tue, Sep 1, 2015 at 12:48 PM, Roger Pack wrote: > It appears the problem lies with creating a file named "NUL" windows > utilities just don't know how to deal with it (you can recreate it by > creating a folder, then from cygwin bash $ touch NUL) then try and > remove the folder with windows explorer. The utilities "know" how to deal with it, given their design: http://blogs.msdn.com/b/oldnewthing/archive/2003/10/22/55388.aspx -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
"permission denied" issues when removing files/folders created by cygwin
As a note, after using cygwin to build some libraries (worked well, thanks team!) when trying to delete a folder via windows explorer, I got the message "Destination folder access denied, you need to confirm this action" (followed by a UAC prompt) and also "Delete folder, Invalid MS-DOS function" It appears the problem lies with creating a file named "NUL" windows utilities just don't know how to deal with it (you can recreate it by creating a folder, then from cygwin bash $ touch NUL) then try and remove the folder with windows explorer. I would not have expected cygwin to allow itself the privilege of creating files that are unremovable by windows explorer, but I just thought I'd throw it out there. Cheers! -roger- -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: fish-2.2.0-3
Andrew Schulman writes: > 100 history files? Where? I have only one history file, ~/.config/fish/fish_history.abcd (some four-letter random string IIRC, like those created by mkstemp). Each of the files is having some portion of my history in it, maybe something to do with the timestamp in the original history file. I haven't looked in more detail. > I've seen those errors before, but in my case instead of "Device or resource > busy" it was "Permission denied" because of an ACL problem. Yeah, the amount > of > noise there is so high as to make fish undesirable to use. Yes, but the ACL problem was solvable. > fish uses ~/.config/fish/fishd.MYCOMPUTER.x86_64 to store universal variables, > which are shared between instances of fish. Apparently it rewrites that file > often. > > Do you see those messages when only one instance of fish is running? Or only > when there's more than one? No, I've never ran more than one instance of fish at once so far. >> Is there anything I can do to resolve these issues? > > For #2, maybe a solution would be to add a switch, say an environment > variable, > that would tell fish not to split its history file. > > For #1 and #3, it seems that these are caused by use of a network profile and > I > don't know what the solution is. > > My recommendation is to report these issues in the upstream issue queue, at > https://github.com/fish-shell/fish-shell/issues. In my experience the fish > developers are quite responsive to issues posted there, and want to support > Windows. I also watch that queue and will help as I can. I don't plan on getting a GitHub account, so that venue is closed. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: suggestion for setup.exe: on quiet mode start window minimized option
On 8/28/15, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Roger Pack sent the following at Friday, August 28, 2015 1:29 PM
>>Today I wanted to script an unattended install of cygwin. It works well.
>>However, I also wanted to be able to do it without showing a window to
>>the user at all. Suggestion/feature request: for --quiet-mode start
>>minimized, or perhaps add a "--start-minimized" option. Cheers. -roger-
>
> How do you start setup? Maybe one of the following will work for you.
>
> A Windows shortcut can be set up to start minimized. My impression is
> that one can use and mechanism to launch a Windows shortcut and then
> Windows will follow the instructions ("Start in:", "Run:", etc.) in the
> shortcut.
>
> In cmd:
> start /min
>
> From a command line (though not a bash shell when cygwin, bash, or maybe
> mintty are being updated):
> cygstart --minimize
> or
> cmd /c start /min
Thanks that did it!
For followers, I ended up using
start /min /wait setup-x86.exe -P ...
(since I wanted to wait for it to terminate before proceeding in my
batch script, like it does when run as straight setup-x86.exe).
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Default Architecture of Package Search/List Pages
Corinna Vinschen sent the following at Tuesday, September 01, 2015 11:59 AM >On Sep 1 15:50, Buchbinder, Barry (NIH/NIAID) [E] wrote: >> Corinna Vinschen sent the following at Tuesday, September 01, 2015 11:35 AM >> >On Sep 1 12:36, Buchbinder, Barry (NIH/NIAID) [E] wrote: >> >> On the cygwin package search and package list pages, the >> >> architectures are listed with 32 bit first/default. >> >> >> >> x86 x86_64 >> >> >> >> If it is known that currently the majority of cygwin users are using >> >> 64 bit, might it be appropriate to make 64 bit the default? >> >> >> >> Thanks for considering this. >> > >> >Done. >> >> Thanks. (That was fast!) >> >> Package List, too? >> https://cygwin.com/packages/package_list.html > >Yep, Corinna Danke!
Re: Default Architecture of Package Search/List Pages
On Sep 1 15:50, Buchbinder, Barry (NIH/NIAID) [E] wrote: > Corinna Vinschen sent the following at Tuesday, September 01, 2015 11:35 AM > >On Sep 1 12:36, Buchbinder, Barry (NIH/NIAID) [E] wrote: > >> On the cygwin package search and package list pages, the > >> architectures are listed with 32 bit first/default. > >> > >> x86 x86_64 > >> > >> If it is known that currently the majority of cygwin users are using > >> 64 bit, might it be appropriate to make 64 bit the default? > >> > >> Thanks for considering this. > > > >Done. > > Thanks. (That was fast!) > > Package List, too? > https://cygwin.com/packages/package_list.html Yep, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp_t_ObMmLh7.pgp Description: PGP signature
RE: Default Architecture of Package Search/List Pages
Corinna Vinschen sent the following at Tuesday, September 01, 2015 11:35 AM >On Sep 1 12:36, Buchbinder, Barry (NIH/NIAID) [E] wrote: >> On the cygwin package search and package list pages, the >> architectures are listed with 32 bit first/default. >> >> x86 x86_64 >> >> If it is known that currently the majority of cygwin users are using >> 64 bit, might it be appropriate to make 64 bit the default? >> >> Thanks for considering this. > >Done. Thanks. (That was fast!) Package List, too? https://cygwin.com/packages/package_list.html Thanks again, - Barry Disclaimer: Statements made herein are not made on behalf of NIAID.
Re: Default Architecture of Package Search/List Pages
On Sep 1 12:36, Buchbinder, Barry (NIH/NIAID) [E] wrote: > On the cygwin package search and package list pages, the > architectures are listed with 32 bit first/default. > > x86 x86_64 > > If it is known that currently the majority of cygwin users are using > 64 bit, might it be appropriate to make 64 bit the default? > > Thanks for considering this. Done. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp4EIp3UsGwC.pgp Description: PGP signature
Re: Running Cygwin's "setup.exe" on a new computer
On 01/09/2015 14:50, Dr Rainer Woitok wrote:
Greetings,
having installed Cygwin on my old computer it's now time to move to new
hardware. Are there any Cygwin configuration or status files I could
copy from the old box to the new one which would cause "setup.exe" on
the new machine to automatically install the same packages as on the old
computer (except for version changes or new dependencies)?
One minor additional problem perhaps: the old box is 32 bit, while the
new one is 64 bit.
Any help welcome.
Sincerely,
Rainer
PS: Please also reply by personal mail as I am not subscribed to the
Cygwin mailing list.
something like this should work
$ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' >
cyg-install-x86_64.bat
$ chmod +x cyg-install-x86_64.bat
Of course copy the "cyg-install-x86_64.bat" where the
"setup-x86_64.exe" is on the new computer.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Running Cygwin's "setup.exe" on a new computer
Greetings, having installed Cygwin on my old computer it's now time to move to new hardware. Are there any Cygwin configuration or status files I could copy from the old box to the new one which would cause "setup.exe" on the new machine to automatically install the same packages as on the old computer (except for version changes or new dependencies)? One minor additional problem perhaps: the old box is 32 bit, while the new one is 64 bit. Any help welcome. Sincerely, Rainer PS: Please also reply by personal mail as I am not subscribed to the Cygwin mailing list. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Default Architecture of Package Search/List Pages
On the cygwin package search and package list pages, the architectures are listed with 32 bit first/default. x86 x86_64 If it is known that currently the majority of cygwin users are using 64 bit, might it be appropriate to make 64 bit the default? Thanks for considering this. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Error while building GMP on cygwin "configure: error: could not find a working compiler"
Hi, I got the following error in configuring GMP while building a bare metal GNU cross toolchain for Xtensa on cygwin configure: error: could not find a working compiler, see config.log for details The build was performed using a crosstool-NG downloaded from the site http://wiki.linux-xtensa.org/index.php/Crosstool-NG using the git clone git clone https://github.com/foss-xtensa/crosstool-NG.git This downloads GMP-5.1.1 while downloading GCC and related packages. 1. Build environment - cygwin 2. The GMP version number - GMP-5.1.1 3. Output of gcc -v $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.9.3/lto-wrapper.exe Target: i686-pc-cygwin Configured with: /cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3/configure --srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3 --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C --build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin --without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib --enable-shared --enable-shared-libgcc --enable-static --enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic --disable-sjlj-exceptions --enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ --enable-graphite --enable-threads=posix --enable-libatomic --enable-libgomp --disable-libitm --enable-libquadmath --enable-libquadmath-support --enable-libssp --enable-libada --enable-libjava --enable-libgcj-sublibs --disable-java-awt --disable-symvers --with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix --without-libintl-prefix --with-system-zlib --enable-linker-build-id Thread model: posix gcc version 4.9.3 (GCC) 4. The output from running ‘uname -a’. $ uname -a CYGWIN_NT-6.1 si-hnhari 2.1.0(0.287/5/3) 2015-07-14 21:26 i686 Cygwin The output of config.log and build.log is attached. Please let me know if you need any more information. Thanks and Regards, Hari -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Restrict active directory logins
On Mon, Aug 31, 2015 at 11:39 PM, E. Winston wrote: > Hi all, > > I am running cygwin 2.2.1(0.289/5/3) and OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul > 2015 on a domain joined Windows 2012 R2 server. I am not using /etc/passwd or > /etc/group and I would prefer not to use theses files as I anticipate a large > number of accounts needing to be configured. As part of our group policy, NT > AUTHORITY\Authenticated Users and NT AUTHORITY\Interactive are both part of > the local Users group. The group policy also places NT > AUTHORITY\Authenticated Users into "Log on Locally" security policy. My > primary purpose is to use this as an SFTP server. I have been able to deny > SSH logins and limit access to on SFTP. > > What I would like to know is with this setup, is if there is a way to prevent > any user in our domain from logging into the server? > > Currently I have directory permissions set so they cannot see anything, but > I'd rather not allow them to login at all. > > I have a local group created with only the domain accounts I want to be able > to explicitly login but thus far I have not been able to determine how to > limit logins to just the members of this group. > > Thanks in advance, > > -Ed > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Ed, I have a similar arrangement. Short of reprogramming Cygwin to *not* do an interactive logon (i.e. do a network logon instead), I think you're out of luck. A network logon would work for what an SFTP server needs to do, but probably isn't right for other purposes such as a full SSH terminal session -- and unfortunately both authentication process goes through the same function in Cygwin. I thought about proposing some configurable setting in Cygwin on the mailing list, but the need is really too nuanced to merit implementation (in my opinion). If the users don't have access to the console, just make sure that you're not also allowing "Allow log on through Remote Desktop Services" -- that should prevent a user from being logged into via Remote Desktop. That said, the problem may actually be worse than you think. If you have roaming profiles enabled, they may be getting synced every time a user logs in via SFTP. If this isn't desired, you'll want to enable user profile cleanup and disable roaming profiles to that system, in general. It'll slow down the login in addition to bloat the profile directory. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: fish-2.2.0-3
> It seems that fish still has problems with my home directory that is on the > network (roaming profile in Windows). It takes ages to start up (does it > try to enumerate all users perhaps?). I've removed the ACL that seemed to > trip it up, but no change with the startup time. I've never used a roaming profile in Windows, so I haven't seen this problem and don't know what would cause it. > Fish seems to have picked > up my (large) tcsh history and produced about a hundred history files from > that. That will become another killer when I were to try and log in via VPN > (reading one large file is a lot faster than reading many small ones). 100 history files? Where? I have only one history file, ~/.config/fish/fish_history. It's about 234K. I'm not sure if it has my old bash history in it; it may. > Last > but not least, when it has finally started it constantly bickers about this; > roughly six or seven times for each command issued: > > Unable to rename file from '/home/gratz/.config/fish/fishd.tmp.q4rCYs' to > '/home/gratz/.config/fish/fishd.MYCOMPUTER.x86_64': Device or resource busy > > This is one of those network shares that can do hardlinks, but the link > count is always 1 (due to a NetApp bug that makes inode numbers unstable). I've seen those errors before, but in my case instead of "Device or resource busy" it was "Permission denied" because of an ACL problem. Yeah, the amount of noise there is so high as to make fish undesirable to use. fish uses ~/.config/fish/fishd.MYCOMPUTER.x86_64 to store universal variables, which are shared between instances of fish. Apparently it rewrites that file often. Do you see those messages when only one instance of fish is running? Or only when there's more than one? > Is there anything I can do to resolve these issues? For #2, maybe a solution would be to add a switch, say an environment variable, that would tell fish not to split its history file. For #1 and #3, it seems that these are caused by use of a network profile and I don't know what the solution is. My recommendation is to report these issues in the upstream issue queue, at https://github.com/fish-shell/fish-shell/issues. In my experience the fish developers are quite responsive to issues posted there, and want to support Windows. I also watch that queue and will help as I can. Good luck, Andrew -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Restrict active directory logins
E. Winston hotmail.com> writes: > I am running cygwin 2.2.1(0.289/5/3) and OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015 on a domain > joined Windows 2012 R2 server. I am not using /etc/passwd or /etc/group and I would prefer not to use theses > files as I anticipate a large number of accounts needing to be configured. As part of our group policy, NT > AUTHORITY\Authenticated Users and NT AUTHORITY\Interactive are both part of the local Users group. The > group policy also places NT AUTHORITY\Authenticated Users into "Log on Locally" security > policy. My primary purpose is to use this as an SFTP server. I have been able to deny SSH logins and limit > access to on SFTP. Why can't you just override the group policy and forbid local logins (except for another AD group that you explicitly allow)? Regards, Achim.
