Native links break zsh
Hi! After adding export CYGWIN='winsymlinks: nativestrict' command to my .zshrc file I'm experiencing the problem with zsh HISTFILE. The message says: History locking file failed: No such file or directory. I don't know how this is related since HISTFILE isn't a link at all. Thanks. Yuriy.
Re: [ITP] man-db
Chris J. Breisch wrote: Yaakov Selkowitz wrote: On 2014-06-02 16:12, Chris J. Breisch wrote: Yaakov (Cygwin/X) wrote: On 2014-06-02 10:37, Chris J. Breisch wrote: I've incorporated Yaakov's patches. There is a new version at http://files.breisch.me/pub/cygwin/man-db-64/ The setup.hint looks like it wasn't replaced. Shouldn't it have been replaced if I did a cygport man-db.cygport all? I just copied the dist folder it created up to the web. Am I missing some key bit? The tarballs look new, but the setup.hint is definitely old. Depending on how you uploaded these files, maybe you forgot to overwrite that one? Yaakov No, I deleted everything. I also deleted the build tree before running cygport. I'll do it again, but the setup.hint that's up there is the one created by cygport after I included your patches. Ok, I figured it out. I had forgotten that I actually had a setup.hint file and that cygport wasn't creating it. I built it correctly now, I think. I'll be uploading a new one within the hour. -- Chris J. Breisch
Re: [ITP] man-db
Chris J. Breisch wrote: Ok, I figured it out. I had forgotten that I actually had a setup.hint file and that cygport wasn't creating it. I built it correctly now, I think. I'll be uploading a new one within the hour. http://files.breisch.me/pub/cygwin/man-db-64 and http://files.breisch.me/pub/cygwin/man-db-32 -- Chris J. Breisch
Re: Native links break zsh
On Wed, Jun 04, 2014 at 12:56:45PM +0400, Yuriy Chernyshov wrote: Hi! After adding export CYGWIN='winsymlinks: nativestrict' command to my .zshrc file I'm experiencing the problem with zsh HISTFILE. The message says: History locking file failed: No such file or directory. I don't know how this is related since HISTFILE isn't a link at all. This is not a bug reporting mailing list. You've already posted this topic to the cygwin list and you have had responses to your message. Please continue the discussion there. I'm unsubscribing you from cygwin-apps.
Re: [ITP] AtomicParsley
On 04/06/2014 00:32, Yaakov Selkowitz wrote: On 2014-06-03 14:05, David Stacey wrote: AtomicParsley is a utility for reading and writing metadata tags on MP4 files. It is found in many Linux distros, including Fedora [1]. The package name has been capitalised to reflect the name of the executable and to mirror the Fedora package name. Debian and Ubuntu both use the lowercase 'atomicparsley' for the package name, but keep the executable as 'AtomicParsley'. Personally, I prefer the Fedora convention, but I'm happy to change this if there's precedent elsewhere. Generally we base this on the tarball name, but I see there aren't anymore. The old (=0.9.0) tarballs were CamelCased, but the hg repo is lowercase (go figure). Under the circumstances, I'd say it's up to you. Thank you for taking the time to look at this. I think I would prefer to keep with 'AtomicParsley', as this reflects the executable name. Finally, I've been asked in the past to provide man pages for executables in my packages. AtomicParsley doesn't come with a man page, so I've generated one using help2man(1). I'm tempted to drop the man page though - even the Debian build comes without a man page these days [2]. help2man only provides good output if --help itself follows certain conventions; AtomicParsley does not. Since we don't really have a policy to *require* manpages where they don't already exist (this isn't Debian), and the resulting manpage doesn't look all that readable anyway, I suggest you just drop it. It's gone. I wasn't overly keen on the man page either :-) As for the actual build, you should drop src_compile() and use the default cygautoreconf/cygconf/cygmake combination. Cygwin-specific READMEs are optional, so you may drop that too if you wish. Otherwise this looks GTG. As per your suggestion I have dropped src_compile(). I've also removed my custom src_install() - I don't need this since I'm not installing a man page anymore. I've kept the Cygwin-specific README, as this is generated and it would be more work to remove it than keep it. If you're happy with this then please could you (or CGF) add an entry for AtomicParsley to cygwin-pkg-maint. I'll give the new build one last test tomorrow and then upload it. Thanks again for your constructive suggestions, Dave.
New Version 1.7.30-1: Passwd -R option. Can only update logged in user.
Hi, Recently there was an update to the passwd -R feature in 1.7.30-1 which allows you to pipe in a password to the passwd -R. This is a something that we really need and the update is appreciated. :) There is still an issue in that you can only update the registry for the user that is currently logged in. In previous versions (such as 1.7.25), an administrator could update for any user (although the piping feature was unavailable). In the new version 1.7.30-1, when an attempt to update for any other user an error is produced stating: Storing password failed: No such file or directory. Is this something that the Cygwin team would be able to fix ? Looking for the ability to pipe in a password and update the registry with various users password. This functionality needs to be incorporated into cloud product. The original issue is related to something that Corinna was working on. See https://cygwin.com/ml/cygwin/2014-04/msg00449.html I haev screen shots but your email server will not accept them. Please let me know how to send if needed. I appreciate any help or suggestions you can provide. Thanks, tom Thomas Fay @ IBM IT Specialist IBM Global Technology Services Enterprise Services for Microsoft Technologies -- 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: Emacs-w32... still crashing
On 6/3/2014 4:01 PM, Zdzislaw Meglicki wrote: And another crash... captured under gdb again. Segmentation fault again, but this time: Program received signal SIGSEGV, Segmentation fault. 0x000100631d84 in deselect_palette (f=0x0, hdc=0x0) at /usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:123 123 if (f-output_data.w32-old_palette) and the backtrace shows the following: (gdb) backtrace #0 0x000100631d84 in deselect_palette (f=0x0, hdc=0x0) at /usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:123 #1 0x000100631e53 in release_frame_dc (f=0x0, hdc=0x0) at /usr/src/debug/emacs-24.3.90-1/src/w32xfns.c:154 #2 0x0001006351f9 in uniscribe_encode_char ( font=0x101071d30 , c=99) at /usr/src/debug/emacs-24.3.90-1/src/w32uniscribe.c:585 #3 0x000100462d9b in get_char_glyph_code (c=99, font=0x101071d30 , char2b=0x434726 L) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:23697 #4 0x00010046b995 in x_produce_glyphs (it=0x435790) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:25806 #5 0x0001004572c5 in display_line (it=0x435790) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:19963 #6 0x00010044c7b4 in try_window (window=4312112205, pos=..., flags=0) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:16708 #7 0x00010044937a in redisplay_window (window=4312112205, just_this_one_p=true) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:15983 #8 0x000100442ccb in redisplay_window_1 (window=4312112205) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:14188 #9 0x0001005968ac in internal_condition_case_1 ( bfun=0x100442c8c , arg=4312112205, handlers=4305621542, hfun=0x100442c09 ) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:1378 #10 0x0001004420a5 in redisplay_internal () at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:13834 #11 0x000100442606 in redisplay_preserve_echo_area (from_where=2) at /usr/src/debug/emacs-24.3.90-1/src/xdisp.c:14017 #12 0x00010040e024 in Fredisplay (force=4305639474) at /usr/src/debug/emacs-24.3.90-1/src/dispnew.c:5834 #13 0x000100599b62 in Ffuncall (nargs=1, args=0x439140) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2815 #14 0x0001005dcaa2 in exec_byte_code (bytestr=4301839321, vector=4301839357, maxdepth=28, args_template=3076, nargs=1, args=0x4396c8) at /usr/src/debug/emacs-24.3.90-1/src/bytecode.c:919 #15 0x00010059a286 in funcall_lambda (fun=4301839277, nargs=1, arg_vector=0x4396c0) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2983 #16 0x000100599d77 in Ffuncall (nargs=2, args=0x4396b8) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2864 #17 0x0001005dcaa2 in exec_byte_code (bytestr=4303055217, vector=4303055253, maxdepth=16, args_template=4305639474, nargs=0, args=0x0) at /usr/src/debug/emacs-24.3.90-1/src/bytecode.c:919 #18 0x00010059a5a0 in funcall_lambda (fun=4303055165, nargs=1, arg_vector=0x1007b6995 ) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:3049 #19 0x000100599d77 in Ffuncall (nargs=2, args=0x439c90) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2864 #20 0x000100593cfb in Fcall_interactively (function=4310211282, record_flag=4305639474, keys=25777929493) at /usr/src/debug/emacs-24.3.90-1/src/callint.c:836 #21 0x000100599bb3 in Ffuncall (nargs=4, args=0x439fc8) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2822 #22 0x0001005dcaa2 in exec_byte_code (bytestr=4302634489, vector=4302634525, maxdepth=52, args_template=4100, nargs=1, args=0x43a560) at /usr/src/debug/emacs-24.3.90-1/src/bytecode.c:919 #23 0x00010059a286 in funcall_lambda (fun=4302634445, nargs=1, arg_vector=0x43a558) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2983 #24 0x000100599d77 in Ffuncall (nargs=2, args=0x43a550) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2864 #25 0x0001005994ca in call1 (fn=4305696770, arg1=4310211282) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:2614 #26 0x000100500128 in command_loop_1 () at /usr/src/debug/emacs-24.3.90-1/src/keyboard.c:1556 #27 0x000100596707 in internal_condition_case ( bfun=0x1004ff821 , handlers=4305705682, hfun=0x1004fef62 ) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:1354 #28 0x0001004ff4e5 in command_loop_2 (ignore=4305639474) at /usr/src/debug/emacs-24.3.90-1/src/keyboard.c:1174 #29 0x000100595e81 in internal_catch (tag=4305695746, func=0x1004ff4b3 , arg=4305639474) at /usr/src/debug/emacs-24.3.90-1/src/eval.c:1118 #30 0x0001004ff474 in command_loop () at /usr/src/debug/emacs-24.3.90-1/src/keyboard.c:1153 #31 0x0001004feadf in recursive_edit_1 () at /usr/src/debug/emacs-24.3.90-1/src/keyboard.c:777 #32 0x0001004fec83 in Frecursive_edit () at /usr/src/debug/emacs-24.3.90-1/src/keyboard.c:845 #33 0x0001004fca49 in main (argc=2, argv=0x43ab00) at /usr/src/debug/emacs-24.3.90-1/src/emacs.c:1646 Would you mind making an emacs bug report (M-x report-emacs-bug)? For the first time, this looks like a backtrace that the emacs experts might be able to make sense out of. In the future, it would help debug
How to run gtk3-demo?
When I run gtk3-demo in cygwin, I got error as below, what should I have to do next? $ gtk3-demo ** ERROR:/usr/src/ports/gtk3/gtk3-3.10.7-2.i686/src/gtk+-3.10.7/demos/gtk-demo/main.c:892:setup_default_icon: assertion failed: (pixbuf) Aborted (core dumped) -- 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: How to run gtk3-demo?
On 04/06/2014 14:54, Zang Zhengrong wrote: When I run gtk3-demo in cygwin, I got error as below, what should I have to do next? $ gtk3-demo ** ERROR:/usr/src/ports/gtk3/gtk3-3.10.7-2.i686/src/gtk+-3.10.7/demos/gtk-demo/main.c:892:setup_default_icon: assertion failed: (pixbuf) Aborted (core dumped) It works fine for me, so please follow guidelines Problem reports: http://cygwin.com/problems.html 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
Emacs-w32... still crashing
This is just to confirm: I had a yet another crash, was running my emacs session under gdb and captured the event. The trace is the same as before, that is, there is a problem in deselect_palette that causes segmentation fault. Yes, I will report the bug to Emacs maintainers. Zdzislaw (Gustav) Meglicki Indiana University -- 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: cygpath -u inside backticks differs
Eric - thanks for the info! I see the problem, yes, and it is simple - I have completely slepth through the $() business :-) I am all set now - thanks! Ivan -- 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: RemoteServerAdministrationTools problem
Aside from this set of Windows tools, can you reproduce the same behavior with some more commonly available and more compact utility? I had two system exhibiting this symptom. Wish there was an official way to install an older cygwin, like 1.7.27 or .26. No other commands are behaving differently that I am aware of. I did reinstall win7 ent on my second system, installed RSAT and cygwin and dsquery works again. Not sure what I did in both systems to create this problem. I though it was Proxy32 for proxywinconsole.exe which let me go interactive from a cygwin shell to powershell for my powershell wrapper (see https://bitbucket.org/jbianchi/powershell) but I only installed that on my main system. I'll rebuild and continue to install all the utils to see what breaks it again. The RSAT tools give command line access to AD and lets me script so much. I'm blown away by how a windows admin will work so inefficiently using the Active Directory User and Computers GUI tool. Batch scripting is terrible and the windows console is worse. And don't start me on Powershell! Powershell has a crappy console, no history retention ... how can they be valid shells/consoles? You just dont develop ps1 scripts to call ps1 scripts to build more powerfull utils in powershell like you do in unix. Cygwin with RXVT gives me a complete enough unix shell with a great console (cut and paste anyone?). I can script mixing powershell, dos batch and cygwin I can make windows managable. -- 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: cygpath -u inside backticks differs
Eric Blake ebl...@redhat.com writes: see why `` is obsolete, and you should be using $()? Among other reasons, \ inside `` has weird rules. Wow, when did this happen? I've been using `` for years, and never heard of $(). What version did this change? I think I need to go back and re-read some documentation! Dave -- 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: Compiling cygwin1.dll
On Tue, Jun 3, 2014 at 6:07 PM, Larry Hall (Cygwin) wrote: On 06/03/2014 08:57 AM, Michael Wild wrote: On Tue, Jun 3, 2014 at 12:32 PM, Andrey Repin wrote: Greetings, Michael Wild! In order to pinpoint an error I'm trying to compile cygwin1.dll from source following the instructions here: My question is: do you actually need to rebuild it, or you just need the debug symbols? https://cygwin.com/faq.html#faq.programming.building-cygwin. However, when building binutils, I trip over this error: https://sourceware.org/ml/binutils/2014-02/msg00064.html. According to DJ (https://sourceware.org/ml/binutils/2014-02/msg00067.html), attempts to build the old binutils/gdb in CVS are going to be doomed. Apparently the development of these packages is now tracked in a separate git repo. So, my question is now, how do I get a working build for the cygwin DLL? Do I have to replace binutils/gdb in the CVS checkout with the git checkout? How are the current snapshots built? Thanks for any pointers in the right direction. Dear Andrey, I really need to build it, in order to pinpoint which commit breaks things. OK but why are you building 'binutils' if you just want to build the Cygwin DLL? -- Larry You tell me. I just checked out the source and followed the instructions as I said in my first message. When doing so, there is a dependency and binutils gets built. If the instructions are outdated, I did something obviously wrong, or there is a better way, please let me know. Michael -- 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: How to run gtk3-demo?
2014/06/04 21:54、Zang Zhengrong zhengrong.z...@gmail.com のメッセ�`ジ: When I run gtk3-demo in cygwin, I got error as below, what should I have to do next? $ gtk3-demo ** ERROR:/usr/src/ports/gtk3/gtk3-3.10.7-2.i686/src/gtk+-3.10.7/demos/gtk-demo/main.c:892:setup_default_icon: assertion failed: (pixbuf) Aborted (core dumped) Thanks, I got what I need, now hello window is displayed. -- 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
How to set big font for xterm in cygwin/X
Now I can use cygwin/X to run gtk3-demo, but my eyes is bad and xterm font in cygwin/X is very small, how can I set to bigger font for xterm? Thanks a lot. -- 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: cygpath -u inside backticks differs
On 06/04/2014 08:31 AM, J. David Boyd wrote: Eric Blake ebl...@redhat.com writes: see why `` is obsolete, and you should be using $()? Among other reasons, \ inside `` has weird rules. Wow, when did this happen? I've been using `` for years, and never heard of $(). What version did this change? $() has existed in all sh variant shells except Solaris /bin/sh pretty much since the 80s; it was standardized in POSIX in the 90s. (On Solaris, you have to use /usr/xpg4/bin/sh instead of /bin/sh to get it) -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: How to set big font for xterm in cygwin/X
In message 92c60106-8a54-434b-a470-744b8e4d4...@gmail.comyou write: Now I can use cygwin/X to run gtk3-demo, but my eyes is bad and xterm font = in cygwin/X is very small, how can I set to bigger font for xterm? Thanks a= lot.= Well, if you hold down the ctrl key and hit the right mouse button, you will get a menu of VT Fonts and select Large or Huge. Or you could do what I've done -- Make a my_xterm shell script: ## #!/bin/sh # export LANG=C export XTERM_LOCALE=C exec xterm \ -fa lucidatypewriter -fs 16 \ -fg green \ -bg black $* ## I find the green on black much easier to read than other combinations. -- 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: How to set big font for xterm in cygwin/X
Zhengrong Zang wrote: Now I can use cygwin/X to run gtk3-demo, but my eyes is bad and xterm font in cygwin/X is very small, how can I set to bigger font for xterm? Thanks a lot. I use the following in my ~/.Xdefaults. Change the faceName and faceSize to suit you. XTerm*faceName: Bitstream Vera Serif Mono XTerm*faceSize: 10 XTerm*toolBar: false XTerm*Background: black XTerm*Foreground: white XTerm*cursorColor: LightBlue XTerm*ScrollBar: true XTerm*rightScrollBar: true -- Chris J. Breisch -- 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: Compiling cygwin1.dll
Greetings, Michael Wild!
You tell me. I just checked out the source and followed the
instructions as I said in my first message. When doing so, there is a
dependency and binutils gets built.
If the instructions are outdated, I did something obviously wrong, or
there is a better way, please let me know.
I've used this script to rebuild it.
#!/bin/sh
SUITE_ROOT=/c/dev/sdc1/cygwin
BUILD_PATH=$SUITE_ROOT/build
INSTALL_PATH=$SUITE_ROOT/install
BUILD_MODULE=$SUITE_ROOT/src${PWD##$BUILD_PATH}
{
$BUILD_MODULE/configure -v --prefix=$INSTALL_PATH
LANG=C make
} | tee rebuild.log
Checked out the repository into $SUITE_ROOT/src, recreated the necessary paths
in $SUITE_ROOT/build and restarted the script from certain paths until I
succeed in building required portions of suite. (I was mainly intersted in
winsup.)
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 04.06.2014, 21:29
Sorry for my terrible english...
--
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: Compiling cygwin1.dll
On Wed, Jun 4, 2014 at 7:32 PM, Andrey Repin wrote:
Greetings, Michael Wild!
You tell me. I just checked out the source and followed the
instructions as I said in my first message. When doing so, there is a
dependency and binutils gets built.
If the instructions are outdated, I did something obviously wrong, or
there is a better way, please let me know.
I've used this script to rebuild it.
#!/bin/sh
SUITE_ROOT=/c/dev/sdc1/cygwin
BUILD_PATH=$SUITE_ROOT/build
INSTALL_PATH=$SUITE_ROOT/install
BUILD_MODULE=$SUITE_ROOT/src${PWD##$BUILD_PATH}
{
$BUILD_MODULE/configure -v --prefix=$INSTALL_PATH
LANG=C make
} | tee rebuild.log
Checked out the repository into $SUITE_ROOT/src, recreated the necessary paths
in $SUITE_ROOT/build and restarted the script from certain paths until I
succeed in building required portions of suite. (I was mainly intersted in
winsup.)
Hi Andrey Repin
Many thanks. So you are saying, you never used the top-level build
system? That would explain a lot. So it is just an iterative trial and
error process? Way to go...
Cheers
Michael
--
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: Compiling cygwin1.dll
Greetings, Michael Wild! Many thanks. So you are saying, you never used the top-level build system? I don't NEED to rebuild whole toolchain to begin with. And it takes about half an hour just to configure it on my system. Or at least half an hour up to first error, which I'm unable to get much sense from, since I'm no expert in bird languages. That would explain a lot. So it is just an iterative trial and error process? Way to go... For me, it was. YMMV. -- WBR, Andrey Repin (anrdae...@yandex.ru) 04.06.2014, 23:53 Sorry for my terrible english... -- 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: Compiling cygwin1.dll
On Wed, Jun 04, 2014 at 11:55:32PM +0400, Andrey Repin wrote: Greetings, Michael Wild! Many thanks. So you are saying, you never used the top-level build system? I don't NEED to rebuild whole toolchain to begin with. If you follow the instructions for checking out cygwin you shouldn't HAVE the whole toolchain. cgf -- 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
CYGWIN - As admin setup other users SSH for them?
I've got a Windows system setup with SSH in CYGWIN working. I've used mkpaswd to install the users in /etc/passwd. As administrator I want to: 1) generate the key pairs for the other users. 2) install the public key in the users $home/.ssh/authorized_keys. 3) deliver the private key to the user along with the rest of the instructions on how to use it in the provided apps. With out their passwords I can't login to establish their $home directory structure, run ssh-keygen, copy the key files. Thanks. -- 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: Compiling cygwin1.dll
On Wed, Jun 4, 2014 at 11:07 PM, Christopher Faylor wrote: On Wed, Jun 04, 2014 at 11:55:32PM +0400, Andrey Repin wrote: Greetings, Michael Wild! Many thanks. So you are saying, you never used the top-level build system? I don't NEED to rebuild whole toolchain to begin with. If you follow the instructions for checking out cygwin you shouldn't HAVE the whole toolchain. cgf AHA! I must have blundered when performing the CVS checkout. Annoyingly confusing old thing... Anyways, many thanks for all your help! Michael -- 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
