Re: cygwin-services-helper [was: Re: [ITA] inetutils-1.5-1]
On Feb 27 22:22, Charles Wilson wrote: Corinna Vinschen wrote: (4a) rewrite syslog-ng-config to use it Okay, thanks. Don't get me wrong. I was not suggesting that you should do all these conversions. It would be nice to have one or two template scripts, like iu-config and syslog-config. Every other script is rather the job of the package maintainer, isn't it? Unless you plan to speed up the migration, of course. But actually, services which don't have to switch user accounts don't really need it. True, unless you want to create an unprivileged user for the service (unless, post-XP, even LocalSystem is considered unprivileged?) I didn't mean to say that other packages shouldn't use this function library. I was merely saying that other scripts which don't have to switch the user context don't have to be converted in the first place. There's no pressure. SYSTEM is of course not an unprivileged user. It has permissions to do stuff no other account has. Since 2K3/XP 64 it has no right to create a user token *only* when used as service starter account. That's the only reason we need another account for those of our services which have to switch user context w/o password (sshd, inetd, xinetd, proftpd, cron, did I miss one?). Standard services which need a lot of permissions but no permission to create a token can stick to the SYSTEM account. Actually it's deprecated to use the SYSTEM account for services unless the service really needs SYSTEM permissions. In XP Microsoft started with introducing the LocalService (S-1-5-19) and NetworkService (S-1-5-20) accounts which have much less rights than SYSTEM and Vista introduces a much more fine grained concept. Maybe we should always add the above two service accounts to /etc/passwd. It's a small tweak to mkpasswd which might have some benefits. Erm... why are all these functions called csh_foo? Cygwin SHell? It sounds so much as if these functions are csh functions. Maybe cf or cyg would be a better prefix? Cygwin-Services-Helper. Since this is a function library that will be sourced into other scripts, I was trying to make sure it was, as far as possible, namespace clean: prefixes on all function names and public variables, ensure to label function-local vars as 'local' so they don't leak, etc. Sure. No worries. But as tcsh maintainer and user I really stumbled over the prefix :) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] VOTE: nrss 0.3.9 -- A ncurses-based RSS reader
On Feb 27 13:00, Jari Aalto wrote: Included in Debian unstable. Needs votes. http://packages.debian.org/nrss This is quite nice RSS reader with easy configuration file: $ cat ~/.nrss/config browser /usr/bin/lynx \%u\ columns 2 add http://rss.slashdot.org/slashdot/Slashdot; Slashdot Neat. +1 Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] iprint 1.3 -- Command-line integer, hex, octal and ascii print utility
On Feb 27 18:58, Jari Aalto wrote: http://cygwin.cante.net/iprint/iprint-1.3-1-src.tar.bz2 \ http://cygwin.cante.net/iprint/iprint-1.3-1.tar.bz2 \ http://cygwin.cante.net/iprint/setup.hint Uploaded. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: cygwin-services-helper [was: Re: [ITA] inetutils-1.5-1]
On Feb 28 11:34, Corinna Vinschen wrote: Actually it's deprecated to use the SYSTEM account for services unless the service really needs SYSTEM permissions. In XP Microsoft started with introducing the LocalService (S-1-5-19) and NetworkService (S-1-5-20) accounts which have much less rights than SYSTEM and Vista introduces a much more fine grained concept. Maybe we should always add the above two service accounts to /etc/passwd. It's a small tweak to mkpasswd which might have some benefits. Done. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: colordiff installs by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jerry D. Hedden on 2/26/2008 7:18 AM: | The newly added distribution 'colordiff' is set to install by default | in setup.exe. Please change it such that it needs to be selected to | be installed. Thanks. | I noticed that current setup.ini claims colordiff is in category Misc, although the original ITP and the current setup.hint on cygwin.com both put it in category Utils. At any rate, is it intentional that setup.exe treats category Misc like category Base? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHxsAE84KuGfSFAYARAjqQAJ9yySpZ+KCNl4csNlC0CKV96KpNMACgzsBh WonNERnEcpjhYlmA31sPfis= =RlDX -END PGP SIGNATURE-
Re: cygwin-services-helper [was: Re: [ITA] inetutils-1.5-1]
- Original Message - From: Corinna Vinschen To: cygwin-apps Sent: Thursday, February 28, 2008 5:34 AM Subject: Re: cygwin-services-helper [was: Re: [ITA] inetutils-1.5-1] | only reason we need another account for those of our services which have | to switch user context w/o password (sshd, inetd, xinetd, proftpd, cron, | did I miss one?). exim Pierre
tar and lzma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm about to upload tar 1.19.90, which adds the --lzma command-line option. Should I make tar depend on the lzma package? Arguments for: it already depends on gzip and bzip2. Also, there was talk on this list a while ago about switching to lzma, instead of bzip2, for files installed via setup.exe, since it gives the best compression ratios to decompression speed tradeoff among all the popular open-source generic-data compression algorithms. The --lzma option only works if lzma is properly installed. Arguments against: tar is in the Base category, so the default cygwin install would grow in size and lzma would graduate to base, even though it is still relatively new. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHx4H284KuGfSFAYARAoiRAKCOjuT/qe0b5Tle+yMvU7AfvN5AugCgtXdQ ChJz0zzjPOpV3xDATsT6bVo= =U4NI -END PGP SIGNATURE-
Re: tar and lzma
Eric Blake wrote: Arguments for: it already depends on gzip and bzip2. Also, there was talk on this list a while ago about switching to lzma, instead of bzip2, for files installed via setup.exe, since it gives the best compression ratios to decompression speed tradeoff among all the popular open-source generic-data compression algorithms. The --lzma option only works if lzma is properly installed. This would also allow the new automake dist-lzma to function. Arguments against: tar is in the Base category, so the default cygwin install would grow in size and lzma would graduate to base, even though it is still relatively new. I'm all for fighting bloat, but we're talking about 68KB extra to download and ~150KB extra disk space, so I don't think it's too big of a deal. Brian
Re: tar and lzma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Dessent on 2/28/2008 9:07 PM: | The --lzma option only works if lzma | is properly installed. | | This would also allow the new automake dist-lzma to function. automake's dist-lzma already functions if you install lzma (I know, because I used it when creating m4 1.4.10b); automake uses 'tar | lzma' rather than 'tar --lzma'. | | I'm all for fighting bloat, but we're talking about 68KB extra to | download and ~150KB extra disk space, so I don't think it's too big of a | deal. At any rate, I'll do the upload now without the dependency, and add it to the hint if we get more positive feedback for this course of action (or gripes on the main list that 'tar --lzma' is broken, which is more likely). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHx4mk84KuGfSFAYARAu1aAKDZST7xQ1C9a+wuX5mzyvUpGmLYjgCgupeO D535HkPlSKYPbSVQsUVcMoA= =O3/h -END PGP SIGNATURE-
Re: tar and lzma
Eric Blake wrote: automake's dist-lzma already functions if you install lzma (I know, because I used it when creating m4 1.4.10b); automake uses 'tar | lzma' rather than 'tar --lzma'. Right; I meant having lzma (vicariously) in Base would also help users of automake. Brian
Re: tar and lzma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Dessent on 2/28/2008 9:32 PM: | Eric Blake wrote: | | automake's dist-lzma already functions if you install lzma (I know, | because I used it when creating m4 1.4.10b); automake uses 'tar | lzma' | rather than 'tar --lzma'. | | Right; I meant having lzma (vicariously) in Base would also help users | of automake. Although in this case, automake could (and probably should) add lzma as a dependency, since automake is not in Base either. Users who want automake already committed to more than the default. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHx4vY84KuGfSFAYARAt6xAJ48bSY7BIJ7e8WwJE7gvnHaDBL0TgCeM8Nh iq46IBIgvaZdq6E99N5TQaM= =+8BZ -END PGP SIGNATURE-
