Re: init and agetty packages available for review/upload. (fwd)
$ 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 Sorry, these files are not all the same. libpng-config libpng12-config pcre-config are used by package configure scripts to figure out where libraries and header files have been installed. E.g. they provide information; they do not modify your system. iu-config ssh-host-config ssh-user-config are "system setup" scripts used to install or initialize daemons. These modify your system. I wouldn't mind if these scripts were moved into /usr/sbin or something, but leave the libpng-config/pcre-config style scripts alone. They NEED to be in the path of normal users. --Chuck
Re: init and agetty packages available for review/upload. (fwd)
On Mon, Nov 11, 2002 at 07:06:33AM -0500, Sergey Okhapkin wrote: > 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 Thanks! Uploaded. 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: 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: 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 -, 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)
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)
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. Max.
Re: init and agetty packages available for review/upload. (fwd)
I agree with Sergey, but wouldn't /usr/sbin be a better choice of destination? /usr/sbin should not be in the PATH of a typical user. Sergey Okhapkin wrote: 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)
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)
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)
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)
On Sat, Nov 09, 2002 at 07:05:09PM -0500, Sergey Okhapkin wrote: > > 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?-) Why not having an init-config script as Max suggested, instead of just a README? The announcement could elaborate on this, too. 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)
Robert Collins wrote: On Sun, 2002-11-10 at 11:05, Sergey Okhapkin wrote: I think a postinstall script that: * sets reasonable defaults * obeys and doesn't overwrite user defined settings should be ok. The postinstall script could always query the user. Earnie.
Re: init and agetty packages available for review/upload. (fwd)
On Sun, 2002-11-10 at 11:05, Sergey Okhapkin wrote: > > What if I want to install init just to look at the included readmes? Install the source package. > Or if I > > want to install it as a service with slightly different settings? This one is important. > Or > simply > > dislike my computer doing too much without telling me about it? So don't install agetty :}. > > 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?-) I think a postinstall script that: * sets reasonable defaults * obeys and doesn't overwrite user defined settings should be ok. Just my 2c. Rob -- --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- signature.asc Description: This is a digitally signed message part
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)
Sergey Okhapkin <[EMAIL PROTECTED]> wrote: >>> 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. 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? For these reasons, and for parity with other Cygwin packages, I strongly prefer a user-run init-config script along the lines of ssh-host-config, to a postinstall script. Max.
RE: [list] Re: init and agetty packages available for review/upload. (fwd)
> > I'm too lazy to send 2 URLs:-) > > I suppose because of the overwealmingly positive response we > can make an exception... > > > > > While I really like the idea of having an init running, I don't > > > > think that simply selecting the package should make it install as a > > > > service with the postinstall script (!). You might take a look at > > > > how Corinna did sshd. > > > > 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:-) Huh, what about typing init on the command line to switch runlevels? Chris
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. (fwd)
On Fri, 8 Nov 2002, Sergey Okhapkin wrote: > I'm too lazy to send 2 URLs:-) I suppose because of the overwealmingly positive response we can make an exception... > > > While I really like the idea of having an init running, I don't > > > think that simply selecting the package should make it install as a > > > service with the postinstall script (!). You might take a look at > > > how Corinna did sshd. > > 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! > > > Some other questions that come to mind: > > > --any thoughts on more support for runlevels in inittab? > > inittab supports all runlevels. The file in the package is for reference > only. I'm going to provide redhat-like initscripts package later. Sounds great. (BTW Sergey also sent me off-list an example of running xinetd as a service started from init--though to do it properly we will need initscripts. Very exciting stuff.) > > > --does this work on Win9x/ME? > > I don't know. I have no any Win9x installation around. Can someone test this? Also, what about the cygutils /usr/bin/last.exe collision? -- Joshua Daniel Franklin Network Administrator IOCC.COM
