Re: PHP ITP Status Update (was: [Maybe-ITP] PHP)
Max, I'd like you to take a look at Gentoo Linux PHP ebuild, http://www.gentoo.org/cgi-bin/viewcvs.cgi/dev-lang/php/ . It handles single-pass build of cli, cgi and apache module if "fastbuild" USE option is set and always worked fine to me.You can get great ideas how to run single pass cygwin php build looking at the gentoo php build script. On Tue, 2006-05-02 at 11:56 +0100, Max Bowsher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Just a quick status update: > > I've now successfully hacked the buildsystem to produce the cgi-fcgi > version of the binary a well as the cli version. > > I intend to try to tweak the build into producing a core DLL before > posting any prospective packages - I think this is fairly necessary, as > otherwise the entire php interpreter is included three times, linked > into the cli .exe, the cgi-fcgi .exe, and the apache2 module. This bloat > is more than I'm comfortable with - and a core DLL will be a > prerequisite for any future work on making extensions build shared. > > Max. > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2.1 (Cygwin) > > iD8DBQFEVzrEfFNSmcDyxYARAlpgAKDDILRVUH69xydlMmtzvD4lyNODPQCcCTpW > KnTDh8NBfhTznZiO8ZJhT8M= > =jRZO > -END PGP SIGNATURE- >
Re: 1st summary (was Re: [HEADSUP] ALL Maintainers, please reply.)
It would be nice if somebody will take care about these packages, I can't maintain the packages, I'm Windows-free now:-) On Пнд, 2005-09-19 at 12:54 +0200, Corinna Vinschen wrote: > LIST 2: PACKAGES WITHOUT REPLY FROM MAINTAINER SO FAR > = > > agetty > chkconfig > initscripts > sysvinit > xinetd
RE: setup.exe sizes
I wonder if most of people have any knoweladge about setup command line arguments, I believe in most cases setup is being started directly from cygwin web page. It's the most important rule of any GUI program design - all settings must be available in GUI. On Wed, 2004-10-27 at 08:07, Buchbinder, Barry (NIH/NIAID) wrote: > There are command line options to avoid this; see > http://sources.redhat.com/ml/cygwin-apps/2003-03/msg00526.html >-n --no-shortcuts Disable creation of desktop and start >-N --no-startmenu Disable creation of start menu shortcut >-d --no-desktop Disable creation of desktop shortcut > > At Monday, October 25, 2004 10:14 PM, Thomas Wolff wrote: > > * setup does not remember the user preferences about the final two > > questions; it especially annoys me that I have to click off > > the option to create a desktop icon every time >
RE: A new method of storing package data base information, proposing packages, and announcing updates
>
> Currently, I store all package information in a large XML
> document which I update by hand whenever a new package is
> ITPd, an existing package is updated, or some other change
> must be made against the live repository. XSL transformations
> convert this XML document into several other formats,
> including the plaintext PPL, MPL, and make files to automate
> downloading, reviewing, and pushing packages into the live repository.
>
If all backend processing is xml-based and all setup.hint files have to
be modified why to not switch the format of setup.hint (and perhaps
setup.ini) files to xml also? The only disadvantage I see is that
current setup.hint format is human-readable, xml is hard to read for
both human and computer:-)
http://www.example.net/products/foomaster/Cygwin/libfoo-%{version}-%{re
lease}.tar.bz2"/>
http://www.example.net/products/foomaster/Cygwin/libfoo-%{version}-%{re
lease}-src.tar.bz2"/>
http://www.example.net/products/foomaster/Cygwin/libfoo.hint"/>
Sergey Okhapkin
Somerset, NJ
RE: Maintainers/Packages List, 2003-11-22
> ) >initscripts Sergey Okhapkin !!! no > source and no external-source !!! last updated 2002-11-19 > ) Shouldn't need source since it is source. > > Alrighty; another binary-only. > Do you mean "source-only"?-) Sergey Okhapkin Somerset, NJ
RE: Updated sysvinit package available for upload
Sure we can, but... Init have to be located on the root filesystem to be accessible at the boot time. /usr might point to a network mount in some installation. I'd like to follow FHS layout of other unixes. Sergey Okhapkin Somerset, NJ > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen > Sent: Wednesday, September 03, 2003 4:49 AM > To: [EMAIL PROTECTED] > Subject: Re: Updated sysvinit package available for upload > > > On Tue, Sep 02, 2003 at 09:28:25PM -0400, Sergey Okhapkin wrote: > > The package rebuilt for 1.5.X Cygwin kernel, changed directory > > structure to follow new Cygwin FHS. > > > > ftp://sokhapkin.dyndns.org/pub/sysvinit/setup.hint > > ftp://sokhapkin.dyndns.org/pub/sysvinit/sysvinit-2.84-4-src.tar.bz2 > > ftp://sokhapkin.dyndns.org/pub/sysvinit/sysvinit-2.84-4.tar.bz2 > > Uploaded. > > What I don't like, though, is that init.exe is in /sbin. > Every other daemon is in /usr/sbin. Can't we move init to > /usr/sbin as well? > > Corinna > > -- > Corinna Vinschen Please, send mails > regarding Cygwin to > Cygwin Developer > mailto:[EMAIL PROTECTED] > Red Hat, Inc. > >
Updated sysvinit package available for upload
The package rebuilt for 1.5.X Cygwin kernel, changed directory structure to follow new Cygwin FHS. ftp://sokhapkin.dyndns.org/pub/sysvinit/setup.hint ftp://sokhapkin.dyndns.org/pub/sysvinit/sysvinit-2.84-4-src.tar.bz2 ftp://sokhapkin.dyndns.org/pub/sysvinit/sysvinit-2.84-4.tar.bz2 Sergey Okhapkin Somerset, NJ
RE: joe-2.8 - a new package for review
Joe requires ncurses too, isn't it? Sergey Okhapkin Somerset, NJ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jari Aalto+mail.emacs Sent: Friday, July 04, 2003 7:24 AM To: [EMAIL PROTECTED] Subject: joe-2.8 - a new package for review Project http://heather.cs.ucdavis.edu/~matloff/joe.html has been ported. Please review. I personally like joe because it includes 'jmacs', a joe Emacs keybinding emulation. Jari http://tierra.dyndns.org:81/cygwin/joe/joe-2.8-1-src.tar.bz2 http://tierra.dyndns.org:81/cygwin/joe/joe-2.8-1.tar.bz2 sdesc: "Fast and simple editor which emulates 5 other editors" ldesc: "JOE emulates several other editors. JSTAR is a close immitation of WordStar with many JOE extensions. JPICO is a close immitation of the Pine mailing system's PICO editor, but with many extensions and improvements. JMACS is a GNU-EMACS immitation. RJOE is a restricted version of JOE, which allowes you to edit only the files specified on the command line." category: Editors requires: cygwin drwxr-xr-x root/None 0 2003-07-04 14:17:34 etc/ drwxr-xr-x root/None 0 2003-07-04 14:17:34 etc/joe/ -rw-r--r-- root/None 17169 2003-07-04 14:17:34 etc/joe/joerc -rw-r--r-- root/None 16344 2003-07-04 14:17:34 etc/joe/jmacsrc -rw-r--r-- root/None 15142 2003-07-04 14:17:34 etc/joe/jstarrc -rw-r--r-- root/None 16348 2003-07-04 14:17:36 etc/joe/rjoerc -rw-r--r-- root/None 13352 2003-07-04 14:17:36 etc/joe/jpicorc -rw-r--r-- root/None 4926 2003-07-04 14:17:36 etc/joe/termcap -rw-r--r-- root/None 4668 2003-07-04 14:17:36 etc/joe/terminfo drwxr-xr-x root/None 0 2003-07-04 14:17:28 usr/ drwxr-xr-x root/None 0 2003-07-04 14:17:28 usr/doc/ drwxr-xr-x root/None 0 2003-07-04 14:17:28 usr/doc/joe-2.8/ -rw-r--r-- root/None 7121 2003-07-04 14:17:28 usr/doc/joe-2.8/INFO -rw-r--r-- root/None 4935 2003-07-04 14:17:28 usr/doc/joe-2.8/LIST -rw-r--r-- root/None 10624 2003-07-04 14:17:30 usr/doc/joe-2.8/README -rw-r--r-- root/None 1178 2003-07-04 14:17:30 usr/doc/joe-2.8/TODO -rw-r--r-- root/None 4688 2003-07-04 14:17:30 usr/doc/joe-2.8/VERSION drwxr-xr-x root/None 0 2003-07-04 14:17:30 usr/doc/Cygwin/ -rw-r--r-- root/None 1520 2003-07-04 14:17:32 usr/doc/Cygwin/joe-2.8.README drwxr-xr-x root/None 0 2003-07-04 14:17:32 usr/bin/ -rwxr-xr-x root/None187904 2003-07-04 14:17:32 usr/bin/joe.exe -rwxr-xr-x root/None187904 2003-07-04 14:17:34 usr/bin/jmacs.exe -rwxr-xr-x root/None187904 2003-07-04 14:17:34 usr/bin/jstar.exe -rwxr-xr-x root/None187904 2003-07-04 14:17:34 usr/bin/rjoe.exe -rwxr-xr-x root/None187904 2003-07-04 14:17:34 usr/bin/jpico.exe -rwxr-xr-x root/None 21099 2003-07-04 14:17:34 usr/bin/termidx.exe drwxr-xr-x root/None 0 2003-07-04 14:17:34 usr/man/ drwxr-xr-x root/None 0 2003-07-04 14:17:34 usr/man/man1/ -rw-r--r-- root/None 36895 2003-07-04 14:17:36 usr/man/man1/joe.1 -- http://tiny-tools.sourceforge.net/ Swatch @time http://www.ryanthiessen.com/swatch/resources.htm Convert @time http://www.mir.com.my/iTime/itime.htm
RE: minires-0.95 - a new package ready for review
libresolv is a standalone library on many unixes, for example BIND installs this lib. I see no reason to include the library into newlib, let's keep it standalone. Sergey Okhapkin Somerset, NJ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor Sent: Wednesday, June 11, 2003 11:15 PM To: [EMAIL PROTECTED] Subject: Re: minires-0.95 - a new package ready for review On Wed, Jun 11, 2003 at 10:33:36PM -0400, Nicholas Wourms wrote: >Now as to whether it should be spun as a separate dll/import library >(-lresolv), is another matter, entirely. Of course, feel free to >disagree, as I could be wrong ;-). I think it belongs in newlib, too. Anyone willing to take a shot at getting it into newlib? cgf
Updated sysvinit-2.84-3 package available for upload
The release adds missed /bin/pidof. http://users.rcn.com/sokhapkin/release/sysvinit/setup.hint http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-3-src.tar.bz2 http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-3.tar.bz2 -1 and -2 releases may be deleted from the download area. Sergey Okhapkin Somerset, NJ
Re: xinetd and chkconfig - ok to upload ?
From: "Charles Wilson" <[EMAIL PROTECTED]> > I don't think there is a clean way to do this (and ssh doesn't clean up > /usr/bin/sshd-*-config either) unless we have a set of scripts like > > /etc/postinstall/ > /etc/postupgrade/ > /etc/preupgrade/ > /etc/preremove/ > > and setup "knows" about upgrades vs. removals, and calls the "correct" > scripts. But that's a MESS -- and would probably break a lot of > existing packages that depend on the current behavior for proper Yep! You got my point. We can't do a clean package uninstall without distinguishing between uninstall/upgrade actions. Moreover, I can't do /usr/sbin/chkconfig --del xinetd in xinetd's preremove script because chkconfig may be removed already by setup on simultaneous upgrade of both xinetd and chkconfig pachages! BTW, shouldn't setup remove/install the packages one by one? Currently if several packages are upgraded at the same time setup removes _all_ the packages to be upgared first and installs all the upgrade packages after that. > Sergey said: > > Me too. I'd like to build rpc-aware xinetd with sunrpc package. > > I'm not sure if that means he wants to WAIT for the sunrpc package to be > accepted into cygwin, then rebuild his xinetd package so that it uses > the rpc stuff, or if he wants to go forward with xinetd AS-IS and add > rpc stuff later on as an update. > > I suspect the latter. You're right, I'm going to add RPC support to the next version of xinetd, I'd like to have XXX-1 version of xinetd to be uploaded as is. Sergey Okhapkin Somerset, NJ
Re: Pending packages status
- Original Message - From: "Charles Wilson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 23, 2002 10:40 AM Subject: Re: Pending packages status > > Sergey Okhapkin wrote: > >> >>5. sunrpc > > Me too. I'd like to build rpc-aware xinetd with sunrpc package. > > Errrwhat do you mean? > > 1) xinetd can be built so that it (somehow) USES rpc calls, and you want > to do that, or > > 2) you're simply proposing to include startup scripts for sunrpc (e.g. > portmapper) in the xinetd package (e.g. in /etc/xinetd.d/) I mean 1). Xinetd has a built-in rpc support. > where should daemon startup scripts "live"? >a) As part of xinetd.d/ in the xinetd package, >b) in /etc/rc.d/init.d/ as part of the initscripts package >c) or in [/etc/rc.d/init.d|/etc/xinetd.d/] as part of whatever > package the daemon itself is in? > > IMO, (c) is the right answer. That is, /etc/rc.d/init.d/sshd should be > part of the sshd package, not initscripts. Ditto Agree. I put init.d/sshd script to initscripts package as an example. Sergey Okhapkin Somerset, NJ
Re: Pending packages status
- Original Message - From: "Hack Kampbjorn" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 23, 2002 8:32 AM Subject: Re: Pending packages status > Corinna Vinschen wrote: > > On Fri, Dec 20, 2002 at 04:23:26PM +0100, Pavel Tsekov wrote: > >>5. sunrpc > >>6. nfs-server > > > > > > Definitely my vote, too. > > Both have my vote Me too. I'd like to build rpc-aware xinetd with sunrpc package. Sergey Okhapkin Somerset, NJ
Re: Pending packages status
From: Charles Wilson
> spkg doesn't seem to work properly -- the patch is VERY large.
> This is because xinetd-2.3.9-1.sh sets "objdir=${srcdir}".
You have to run "clean" before "spkg". "all" target creates a correct diff
file. objdir have to be set to srcdir because of xinetd's makefile bugs.
I'm going to fix these bugs in the next release - I want to build xinetd
with a just announced RPC package.
> should have an /etc/preremove script, to do the following
> (*) rm -f /etc/xinetd.d/*
> (*) rmdir /etc/xinetd.d
> (*) rm -f /etc/xinetd.conf
I can't do that:-( Preremove script is executed on package upgrade too,
all user-created or modified settings will be lost on upgrade.
Regarding chkconfig:
> conf) Why --disable-nls? Just to avoid the dependency on libintl?
Because chkconfig build fails otherwice:-) --with-included-gettext
configure option fixes the problem, but I'd like to investigate first waht
is wrong with chkconfig's configure/Makefile.
--
Sergey Okhapkin
Somerset, NJ
Re: Pending packages status
Thank you for your reviews! I will update the packages/answer your questions tonight. Sergey Okhapkin Somerset, NJ
xinetd package
I'd like to make xinetd package available for review, but I prefere to wait for chkconfig package to be uploaded first. xinetd and initscripts don't require chkconfig to be installed, but chkconfig makes the xinetd and initscripts configuration and maintenance much more easier. Sergey Okhapkin Somerset, NJ
Re: chkconfig package available for review/download
In xinetd's postinstall script I'm doing the following: If /etc/rc.d/init.d directory exists then put xinetd's startup script there. If -x /usr/sbin/chkconfig then execute "/usr/sbin/chkconfig --add xinetd". Sergey Okhapkin Somerset, NJ - Original Message - From: "Christopher Faylor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 11:40 PM Subject: Re: chkconfig package available for review/download > On Thu, Nov 21, 2002 at 08:26:36PM -0800, Joshua Daniel Franklin wrote: > >I've finally gotten around to reviewing this, it builds cleanly > >and works as advertised (like sysvinit/initscripts, with the provided > >sshd sample script). There isn't a post-install script or info page or > >anything--it's seems very straighforward. It has my vote. > > > >One question--since there is now a complete sysvinit framework, are > >we going to start encouraging service maintainers/submitters > >(exim, postgresql) to add a /etc/rc.d/init.d/foobar script? Should there > >be some new language telling prospective package contributors about this? > > I think it's premature for that however it would be interesting to have > to transform all of the "How do I get inetd/sshd/crond to start?" > questions into a "How do I get init to start?" question. > > What does everyone else think? > > cgf
Re: Pending packages status
> 6. initscripts > > version: 0.9-1 > status : reviewed; needs some packaging fixes I did the fixes already a while ago... Sergey Okhapkin Somerset, NJ
Re: Updated sysvinit package available for review/upload
From: "Corinna Vinschen" <[EMAIL PROTECTED]> > > http://users.rcn.com/sokhapkin/release/sysvinit/setup.hint > > http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-2-src.tar.bz2 > > http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-2.tar.bz2 > > A minor(?) nit: The postinstall script doesn't differ between NT and 9x > so it asks 9x users to install init as service, too. Fixed. I borrowed OS check code from your excellent ssh-host-config script. Sergey Okhapkin Somerset, NJ
Updated sysvinit package available for review/upload
postinstall script modified to create /var/log and /var/run dirs and empty utmp/wtmp files (if not exist). Removed /etc/inittab Removed some manual pages http://users.rcn.com/sokhapkin/release/sysvinit/setup.hint http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-2-src.tar.bz2 http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-2.tar.bz2 Sergey Okhapkin Somerset, NJ
Re: initscripts package available for review/upload
I see no reason to release a new version just to rename a file, I'd like to get some feedback from users first. Moreover, /etc/inittab is very easy and clear file, initscripts package provides a ready-to-use-for-all version of the file. That's why I want to make initscripts package available via setup ASAP. Sergey Okhapkin Somerset, NJ - Original Message - From: "Max Bowsher" <[EMAIL PROTECTED]> To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, November 13, 2002 5:56 PM Subject: Re: initscripts package available for review/upload > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > The problem is in existance of configfile.default in 2 different > > packages (sysvinit and initscripts). Sysvinit's /etc/inittab is > > almost useless, initscript's postinstall creates a usefull one. It > > would be better to remove /etc/inittab from the next sysvinit release > > and to replace it with /etc/inittab.sample. > > Why not do that then? sysvinit isn't a bulky package, so rereleasing it, > even for just a small change, shouldn't annoy even dialup users. > > Max. >
Re: initscripts package available for review/upload
The problem is in existance of configfile.default in 2 different packages (sysvinit and initscripts). Sysvinit's /etc/inittab is almost useless, initscript's postinstall creates a usefull one. It would be better to remove /etc/inittab from the next sysvinit release and to replace it with /etc/inittab.sample. Sergey Okhapkin Somerset, NJ - Original Message - From: "Max Bowsher" <[EMAIL PROTECTED]> To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, November 13, 2002 5:13 PM Subject: Re: initscripts package available for review/upload > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > Creating a new inittab.default will not activate the package. That's > > why I prefer to save an existing inittab and create a new one. > > /etc/inittab should absolutely not be packaged as such, because otherwise > setup will delete it (and may therefore destroy user configuration) at > package reinstalls/upgrades/uninstalls. > > The configfile.default + postinstall script copying configfile.default to > configfile if it does not exist is a reasonably well accepted Cygwin > packaging method. Why not do that? > > Max. >
Re: initscripts package available for review/upload
Creating a new inittab.default will not activate the package. That's why I prefer to save an existing inittab and create a new one. Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 13, 2002 7:30 AM Subject: Re: initscripts package available for review/upload > On Tue, Nov 12, 2002 at 07:31:29PM -0500, Sergey Okhapkin wrote: > > I did it already, but I can change the script if that's incorrect. I'd like > > to avoid introduction of *-config script... > > I think (but I'm not sure) people are most confused if their > config files are changed w/o further notice. We should avoid > that. However, in case of the inittab stuff, this could be > accomplished most easily by a postinstall script. INstead > of an /etc/inittab file have a /etc/inittab.default (or so) > nd copy it to /etc/inittab if it doesn't already exist. That's > all. > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: initscripts package available for review/upload
I did it already, but I can change the script if that's incorrect. I'd like to avoid introduction of *-config script... Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 7:33 AM Subject: Re: initscripts package available for review/upload > On Mon, Nov 11, 2002 at 09:16:40PM -0500, Sergey Okhapkin wrote: > > I included a postinstall script to the package to rename existing > > /etc/inittab and create a new one. > > Sorry, you will do that or you already did that? > > One problem I just thought about: How do you keep the user informed > that you substituted and moved her old inittab file? You can't send > a mail to root apparently... > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: init and agetty packages available for review/upload.
Thanx! To be included into the next sysvinit release. Sergey Okhapkin Somerset, NJ > BTW, I had found that the following was necessary in cygutil's > postinstall script when I added last and utmpdump to cygutils. Now that > those programs are in sysvinit, sysvinit's /etc/postinstall script > should contain these commands (that's /etc/postinstall/sysvinit.sh, not > /usr/bin/init-config): > > #!/bin/sh > if [ ! -d /var/run ] ; then \ >mkdir -p /var/run ; > fi > if [ ! -d /var/log ] ; then \ >mkdir -p /var/log ; > fi > if [ ! -f /var/run/utmp ] ; then \ >touch /var/run/utmp ; > fi > if [ ! -f /var/log/wtmp ] ; then \ >touch /var/log/wtmp ; > fi > > --Chuck >
Re: initscripts package available for review/upload
I included a postinstall script to the package to rename existing /etc/inittab and create a new one. Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 8:42 AM Subject: Re: initscripts package available for review/upload > On Mon, Nov 11, 2002 at 07:16:51AM -0500, Sergey Okhapkin wrote: > > http://users.rcn.com/sokhapkin/release/initscripts/setup.hint > > http://users.rcn.com/sokhapkin/release/initscripts/initscripts-0.9-1.tar.bz2 > > > > BTW, I just realized that sysvinit and initscripts have a common file - > > /etc/inittab. sysvinit includes a basic one, but initscripts has a full > > featured file. initscripts package has no postinstall script, /etc/inittab > > will be overwritten silently on the package installation. But I need to > > The answer is probably "don't do this". The initscripts package should > only contain skeleton files and/or scripts which create the correct files > on demand of the user. My first OpenSSH packages did overwrite the > config files, too, but that resulted in too much complains. Since then, > unpacking config files in place is considered bad practice for Cygwin. > > At least the postinstall script of the package should rename the old > config file (as *.rpmsave on rpm based installations). > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: initscripts package available for review/upload
I can't include a full featured file into sysvinit because it requires other files from /etc/rc.d, these files are a part of initscripts package. Sergey Okhapkin Somerset, NJ - Original Message - From: "Joshua Daniel Franklin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 9:33 AM Subject: Re: initscripts package available for review/upload > --- Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > BTW, I just realized that sysvinit and initscripts have a common file - > > /etc/inittab. sysvinit includes a basic one, but initscripts has a full > > featured file. > > Why not include the full-featured file in sysvinit and not at all in > initscripts? I mean, sysvinit is already required for initscripts to > run properly anyway. > > Also, Corinna, did I see correctly that you've uploaded this package? > I don't believe all its dependencies have been uploaded. >
Re: initscripts package available for review/upload
Agree. What do you think - could postinstall script rename inittab silently and replase it with a new one? Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 8:42 AM Subject: Re: initscripts package available for review/upload > On Mon, Nov 11, 2002 at 07:16:51AM -0500, Sergey Okhapkin wrote: > > http://users.rcn.com/sokhapkin/release/initscripts/setup.hint > > http://users.rcn.com/sokhapkin/release/initscripts/initscripts-0.9-1.tar.bz2 > > > > BTW, I just realized that sysvinit and initscripts have a common file - > > /etc/inittab. sysvinit includes a basic one, but initscripts has a full > > featured file. initscripts package has no postinstall script, /etc/inittab > > will be overwritten silently on the package installation. But I need to > > The answer is probably "don't do this". The initscripts package should > only contain skeleton files and/or scripts which create the correct files > on demand of the user. My first OpenSSH packages did overwrite the > config files, too, but that resulted in too much complains. Since then, > unpacking config files in place is considered bad practice for Cygwin. > > At least the postinstall script of the package should rename the old > config file (as *.rpmsave on rpm based installations). > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: initscripts package available for review/upload
http://users.rcn.com/sokhapkin/release/initscripts/setup.hint http://users.rcn.com/sokhapkin/release/initscripts/initscripts-0.9-1.tar.bz2 BTW, I just realized that sysvinit and initscripts have a common file - /etc/inittab. sysvinit includes a basic one, but initscripts has a full featured file. initscripts package has no postinstall script, /etc/inittab will be overwritten silently on the package installation. But I need to replace the existing inittab with a new one. What is the best way to avoid the file conflict? OTOH, I see no need to uninstall initscripts without sysvinit uninstallation... Sergey Okhapkin Somerset, NJ - Original Message - From: "Sergey Okhapkin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 6:48 AM Subject: Re: initscripts package available for review/upload > OK. > > Sergey Okhapkin > Somerset, NJ > - Original Message - > From: "Corinna Vinschen" <[EMAIL PROTECTED]> > To: "cygwin-apps" <[EMAIL PROTECTED]> > Sent: Monday, November 11, 2002 6:21 AM > Subject: Re: initscripts package available for review/upload > > > > On Sun, Nov 10, 2002 at 06:27:52PM -0500, Sergey Okhapkin wrote: > > > Canonical download: > > > http://users.rcn.com/sokhapkin/release/initscripts > > > > Sergey, please include the paths to all files (setup.hint, binary, source) > > separately in your postings. It actually makes reviewing more easy. > > > > Corinna > > > > -- > > Corinna Vinschen Please, send mails regarding Cygwin to > > Cygwin Developermailto:cygwin@;cygwin.com > > Red Hat, Inc. > >
Re: init and agetty packages available for review/upload. (fwd)
Wow! I fixed the permissions. http://users.rcn.com/sokhapkin/release/sysvinit/setup.hint http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-1-src.tar.bz2 http://users.rcn.com/sokhapkin/release/sysvinit/sysvinit-2.84-1.tar.bz2 Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 6:29 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > On Sun, Nov 10, 2002 at 10:55:58AM -0500, Sergey Okhapkin wrote: > > Done. I added /etc/postinstall/sysvinit.sh. The script sets up default > > /etc/inittab and /etc/rc (if not exist) and copies itself to > > /usr/bin/init-config for setting up init as a service later. > > > > http://users.rcn.com/sokhapkin/release/sysvinit/ > > Sorry but there's a package fault in the binary: > > drwx-- sos/None 0 2002-11-10 07:29:10 etc/ > d- Administrators/None 0 2002-11-10 07:29:30 etc/postinstall/ > -- Administrators/None 3584 2002-11-10 07:19:53 etc/postinstall/sysvinit > > Look at the permissions. > > Other than that, the package seems to be ok now. Please send the full > URLs to your files in the next mail. > > > Thanks, > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: initscripts package available for review/upload
OK. Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: "cygwin-apps" <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 6:21 AM Subject: Re: initscripts package available for review/upload > On Sun, Nov 10, 2002 at 06:27:52PM -0500, Sergey Okhapkin wrote: > > Canonical download: > > http://users.rcn.com/sokhapkin/release/initscripts > > Sergey, please include the paths to all files (setup.hint, binary, source) > separately in your postings. It actually makes reviewing more easy. > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
chkconfig package available for review/download
http://users.rcn.com/sokhapkin/release/chkconfig/ category: System requires: cygwin initscripts sdesc: "Runlevel/xinetd services editor" ldesc: "chkconfig provides a simple command-line tool for maintaining the /etc/rc[0-6].d directory hierarchy by relieving system administrators of the task of directly manipulating the numerous symbolic links in those directories." chkconfig -- Chkconfig provides a simple command-line tool for main- taining the /etc/rc[0-6].d directory hierarchy by reliev- ing system administrators of the task of directly manipu- lating the numerous symbolic links in those directories. Runtime requirements: cygwin-1.3.15 or newer Build requirements: cygwin-1.3.15 or newer Canonical homepage: http://www.buttsoft.com/~thumper/software/sysadmin/chkconfig/ Canonical download: http://www.buttsoft.com/~thumper/software/sysadmin/chkconfig/ Build instructions: unpack chkconfig-1.2.24h-1-src.tar.bz2 if you use setup to install this src package, it will be unpacked under /usr/src automatically cd /usr/src ./chkconfig-1.2.24h-1.sh all --- Files included in the binary distro etc/ etc/postinstall/ usr/ usr/doc/ usr/doc/chkconfig-1.2.24h/ usr/doc/chkconfig-1.2.24h/INSTALL usr/doc/chkconfig-1.2.24h/README usr/doc/Cygwin/ usr/doc/Cygwin/chkconfig-1.2.24h.README usr/man/ usr/man/man8/ usr/man/man8/chkconfig.8 usr/sbin/ usr/sbin/chkconfig.exe -- Port Notes: - version 1.2.24h-1 - Initial release Cygwin port maintained by: Sergey Okhapkin <[EMAIL PROTECTED]> Sergey Okhapkin Somerset, NJ
initscripts package available for review/upload
category: System requires: bash sysvinit sdesc: "A System-V-like collection of system initialization scripts" initscripts -- A System-V-like collection of system initialization scripts Runtime requirements: cygwin-1.3.14 or newer Build requirements: cygwin-1.3.14 or newer Canonical download: http://users.rcn.com/sokhapkin/release/initscripts Build instructions: No build required. --- Files included in the binary distribution etc/ etc/inittab etc/rc.d/ etc/rc.d/init.d/ etc/rc.d/init.d/functions etc/rc.d/init.d/sshd etc/rc.d/rc etc/rc.d/rc.local etc/rc.d/rc.sysinit etc/rc.d/rc0.d/ etc/rc.d/rc1.d/ etc/rc.d/rc2.d/ etc/rc.d/rc3.d/ etc/rc.d/rc4.d/ etc/rc.d/rc5.d/ etc/rc.d/rc6.d/ usr/ usr/doc/ usr/doc/Cygwin/ usr/doc/Cygwin/initscripts.README -- Port Notes: Requires sysvinit package. The package includes sample script to start/stop sshd daemon. Suggested download: Download and install chkconfig package to simplify runlevel editing. To activate sshd script execute "/sbin/chkconfig --add sshd" - version 0.9-1 - Initial release Cygwin distribution maintained by: Sergey Okhapkin [EMAIL PROTECTED] Sergey Okhapkin Somerset, NJ
Re: init and agetty packages available for review/upload. (fwd)
Done. I added /etc/postinstall/sysvinit.sh. The script sets up default /etc/inittab and /etc/rc (if not exist) and copies itself to /usr/bin/init-config for setting up init as a service later. http://users.rcn.com/sokhapkin/release/sysvinit/ BTW, how to upgrade or uninstall the package if the package's application runs as a service? We need to stop the service first on upgrade/uninstall and to remove the service on uninstall. We need some kind of postinstall counterparts - preupgrade and preuninstall scripts. Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 10, 2002 9:14 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > On Sun, Nov 10, 2002 at 01:41:54PM -, Max Bowsher wrote: > > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > > > Because these scripts are accessible for everyone and may change > > > global configuration settings, these scripts are for for cygwin > > > administrator only. > > > > They won't be able to do anything that the user didn't have priviledges to > > do anyway, but I suppose they could confuse a user. > > I suppose there is an argument for putting admin-only scripts in /usr/sbin. > > But balance that against increased chance of them not being noticed, and > > change of a Cygwin convention. > > I agree with Max here. I don't see how these scripts could do more harm > than any other application in /bin, e. g. cygrunsrv. Especially I don't > think this design decision is actually bound to putting two new packages > into the Cygwin distro. I'm not against discussing this but we can do > this completely independant from your new packages. First of all, the > *existence* of such a script is important to help users setting up things. > Putting all these scripts into another place is the next step. > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: init and agetty packages available for review/upload. (fwd)
OK, I'll provide postinstall and init-config shortly. Corinna, I'll take you iu-config as an example. Sergey Okhapkin Somerset, NJ - Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 10, 2002 9:14 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > On Sun, Nov 10, 2002 at 01:41:54PM -0000, Max Bowsher wrote: > > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > > > Because these scripts are accessible for everyone and may change > > > global configuration settings, these scripts are for for cygwin > > > administrator only. > > > > They won't be able to do anything that the user didn't have priviledges to > > do anyway, but I suppose they could confuse a user. > > I suppose there is an argument for putting admin-only scripts in /usr/sbin. > > But balance that against increased chance of them not being noticed, and > > change of a Cygwin convention. > > I agree with Max here. I don't see how these scripts could do more harm > than any other application in /bin, e. g. cygrunsrv. Especially I don't > think this design decision is actually bound to putting two new packages > into the Cygwin distro. I'm not against discussing this but we can do > this completely independant from your new packages. First of all, the > *existence* of such a script is important to help users setting up things. > Putting all these scripts into another place is the next step. > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developermailto:cygwin@;cygwin.com > Red Hat, Inc.
Re: init and agetty packages available for review/upload. (fwd)
Because these scripts are accessible for everyone and may change global configuration settings, these scripts are for for cygwin administrator only. Sergey Okhapkin Somerset, NJ - Original Message - From: "Max Bowsher" <[EMAIL PROTECTED]> To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, November 10, 2002 8:20 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > I don't feel myself safe with these potentialy dangerous files in the > > PATH... > > Why are they dangerous? > > > My proposal is to move these files somewhere else. > > Well, thats a discussion which will probably require Chris's arbitration. > > -- > Max. > > > - Original Message - > > From: "Max Bowsher" <[EMAIL PROTECTED]> > > To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Sunday, November 10, 2002 8:06 AM > > Subject: Re: init and agetty packages available for review/upload. > > (fwd) > > > > > >> Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > >> > >>> I don't want to introduce extra files in /bin or /usr/bin. > >>> XXX-config scripts should be located somewhere else, not in a path, > >>> something like /etc/package-config, the directory should be > >>> designated for config scripts only. > >> > >> $ ls /usr/bin/*-config > >> /usr/bin/iu-config > >> /usr/bin/libpng-config > >> /usr/bin/libpng12-config > >> /usr/bin/pcre-config > >> /usr/bin/ssh-host-config > >> /usr/bin/ssh-user-config > >> > >> The convention seems a little bit entrenched by now. > >> > >> Max.
Re: init and agetty packages available for review/upload. (fwd)
I don't feel myself safe with these potentialy dangerous files in the PATH... My proposal is to move these files somewhere else. Sergey Okhapkin Somerset, NJ - Original Message - From: "Max Bowsher" <[EMAIL PROTECTED]> To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, November 10, 2002 8:06 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > Sergey Okhapkin <[EMAIL PROTECTED]> wrote: > > > I don't want to introduce extra files in /bin or /usr/bin. XXX-config > > scripts should be located somewhere else, not in a path, something > > like /etc/package-config, the directory should be designated for > > config scripts only. > > $ ls /usr/bin/*-config > /usr/bin/iu-config > /usr/bin/libpng-config > /usr/bin/libpng12-config > /usr/bin/pcre-config > /usr/bin/ssh-host-config > /usr/bin/ssh-user-config > > The convention seems a little bit entrenched by now. > > Max. >
Re: init and agetty packages available for review/upload. (fwd)
- Original Message - From: "Corinna Vinschen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 10, 2002 3:40 AM Subject: Re: init and agetty packages available for review/upload. (fwd) > Why not having an init-config script as Max suggested, instead of just > a README? The announcement could elaborate on this, too. > I don't want to introduce extra files in /bin or /usr/bin. XXX-config scripts should be located somewhere else, not in a path, something like /etc/package-config, the directory should be designated for config scripts only. Sergey Okhapkin Somerset, NJ
Re: init and agetty packages available for review/upload. (fwd)
Done. http://users.rcn.com/sokhapkin/release/sysvinit/ Sergey Okhapkin Somerset, NJ - Original Message - From: "Sergey Okhapkin" <[EMAIL PROTECTED]> To: "Max Bowsher" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, November 09, 2002 7:05 PM Subject: Re: init and agetty packages available for review/upload. (fwd) > > What if I want to install init just to look at the included readmes? Or if > I > > want to install it as a service with slightly different settings? Or > simply > > dislike my computer doing too much without telling me about it? > > > > OK, I give up:-) I will remove postinstall script and provide installation > instruction in sysvinit.README. But I'm not sure it's the best solution, who > read README files?-) > > Sergey Okhapkin > Somerset, NJ > >
Re: init and agetty packages available for review/upload. (fwd)
> What if I want to install init just to look at the included readmes? Or if I > want to install it as a service with slightly different settings? Or simply > dislike my computer doing too much without telling me about it? > OK, I give up:-) I will remove postinstall script and provide installation instruction in sysvinit.README. But I'm not sure it's the best solution, who read README files?-) Sergey Okhapkin Somerset, NJ
Re: [list] Re: init and agetty packages available for review/upload. (fwd)
> Huh, what about typing init on the command line to switch > runlevels? bash-2.05b$ oldps af PID TTY STAT TIME COMMAND 844 0 S0:00 bash 2080 0 R0:00 \_ oldps af bash-2.05b$ ./chkconfig --list xinetd 0:off 1:off 2:off 3:on4:on5:on6:off xinetd based services: chargen:on chargen-udp:on daytime:on daytime-udp:on echo: on echo-udp: on ftpd: on rexec: on rlogin: on rsh:off rsync: off servers:on services: on talk: on telnet: on time: off time-udp: off bash-2.05b$ net start init The init service is starting. The init service was started successfully. bash-2.05b$ oldps af PID TTY STAT TIME COMMAND 1432 ? S0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid 1988 ? S0:00 /bin/cygrunsrv 2436 ? S0:00 \_ init [3] 844 0 S0:00 bash 712 0 R0:00 \_ oldps af bash-2.05b$ /sbin/init 1 bash-2.05b$ oldps af PID TTY STAT TIME COMMAND 1988 ? S0:00 /bin/cygrunsrv 2436 ? S0:00 \_ init [1] 844 0 S0:00 bash 2316 0 R0:00 \_ oldps af bash-2.05b$ I can't release xinetd package now because patched to support ioctl(fd, FIONREAD, ...) on pipes cygwin1.dll required to run xinetd. I sent the patch to cygwin-developers already. When the patch will be included into a net release, I will release xinetd, chkconfig and initscripts packages. BTW, my /etc/inittab is # # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]> # Modified for RHS Linux by Marc Ewing and Donnie Barnes # # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. #ud::once:/sbin/update # Trap CTRL-ALT-DELETE (SIGINT on cygwin) #ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. #pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. #pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run agettys in standard runlevels #S0:2345:respawn:/sbin/agetty -L -T vt100 -n ttyS0 9600 ttyS0 # Run xdm in runlevel 5 # xdm is now a separate service #x:5:respawn:/etc/X11/prefdm -nodaemon
Re: init and agetty packages available for review/upload. (fwd)
> > > > Sshd can run as stand-alone service or from inetd. Init supposed to run as a > > service only. I don't expect somebody need to run init from something other > > than cygrunsrv:-) > > Well, yes, but just because someone downloads init (for example, to > run agetty) doesn't mean they want it running every time they start > up thier computer! > This case the user can change the service startup type to "manual". I believe most of init's users will run it as auto-startup service. Sergey Okhapkin Somerset, NJ
Re: init and agetty packages available for review/upload.
I fixed the symlinks in the updated sysvinit package. The symlinks now point to the executable with .exe suffix: lrwxrwxrwx Admin/Admin0 2002-11-09 08:21:22 sbin/telinit -> init.exe Sergey Okhapkin Somerset, NJ - Original Message - From: "Christopher Faylor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 09, 2002 11:53 AM Subject: Re: init and agetty packages available for review/upload. > On Fri, Nov 08, 2002 at 07:31:53PM -0500, Sergey Okhapkin wrote: > >What are the symlink problems? Do you mean a symlink points to the > >executable name without .exe suffix? > > Yes. But I was confused. I didn't remember (or maybe didn't know) that > a symlink didn't have to contain a .exe when it was linking to a .exe. > > I think that's arguably a bug but it's probably entrenched enough now to > be considered a feature. > > So, nevermind and sorry for the confusion. > > cgf
Re: init and agetty packages available for review/upload.
Agetty and init packages are updated on http://users.rcn.com/sokhapkin/release/ according to your feedback: agetty: added "login" to required packages list added explanation of cygwin-Windows serial port names mapping to agetty.README init: fixed symlinks problem in the binary package. Sergey Okhapkin Somerset, NJ - Original Message ----- From: "Sergey Okhapkin" <[EMAIL PROTECTED]> To: "cygwin-apps" <[EMAIL PROTECTED]> Sent: Friday, November 08, 2002 5:55 PM Subject: init and agetty packages available for review/upload. > I'm going to maintain the cygwin ports of init and agetty packages. You can > get the source code and binary packages at > http://users.rcn.com/sokhapkin/release/. agetty allows to login into Windows > NT box via a serial cable connected to a com port. > > category: System > requires: cygwin cygrunsrv > sdesc: "A System-V Init Clone" > ldesc: "Init is the parent of all processes. Its primary role is > to create processes from a script stored in the file > /etc/inittab (see inittab(5)). This file usually has > entries which cause init to spawn gettys on each line that > users can log in. It also controls autonomous processes > required by any particular system." > > > category: System > requires: cygwin > sdesc: "An improved getty program" > ldesc: "Traditionally, getty is the program that listens on terminal and > modem > ports and that prompts for a login name. Agetty is an alternative for > the System V or SunOS 4 environments that sports some useful features." > > > > Sergey Okhapkin > Somerset, NJ > > > > >
Re: init and agetty packages available for review/upload.
What are the symlink problems? Do you mean a symlink points to the executable name without .exe suffix? Sergey Okhapkin Somerset, NJ - Original Message - From: "Christopher Faylor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 08, 2002 6:47 PM Subject: Re: init and agetty packages available for review/upload. > On Fri, Nov 08, 2002 at 05:55:27PM -0500, Sergey Okhapkin wrote: > >I'm going to maintain the cygwin ports of init and agetty packages. You can > >get the source code and binary packages at > >http://users.rcn.com/sokhapkin/release/. agetty allows to login into Windows > >NT box via a serial cable connected to a com port. > > This has my vote. I notice a couple of symlink problems in the sysvinit package, > however. They are .exe related: > > rwxr-xr-x Administrator/Administrators 36864 2002-11-08 14:51:09 sbin/init.exe > -rwxr-xr-x Administrator/Administrators 17920 2002-11-08 14:51:09 sbin/killall5.exe > -rwxr-xr-x Administrator/Administrators 10752 2002-11-08 14:51:09 sbin/runlevel.exe > lrwxrwxrwx Administrator/Administrators 0 2002-11-08 14:51:10 sbin/telinit -> init > > Looks good otherwise. > > cgf
init and agetty packages available for review/upload.
I'm going to maintain the cygwin ports of init and agetty packages. You can get the source code and binary packages at http://users.rcn.com/sokhapkin/release/. agetty allows to login into Windows NT box via a serial cable connected to a com port. category: System requires: cygwin cygrunsrv sdesc: "A System-V Init Clone" ldesc: "Init is the parent of all processes. Its primary role is to create processes from a script stored in the file /etc/inittab (see inittab(5)). This file usually has entries which cause init to spawn gettys on each line that users can log in. It also controls autonomous processes required by any particular system." category: System requires: cygwin sdesc: "An improved getty program" ldesc: "Traditionally, getty is the program that listens on terminal and modem ports and that prompts for a login name. Agetty is an alternative for the System V or SunOS 4 environments that sports some useful features." Sergey Okhapkin Somerset, NJ
