From: Michael Xue <xue@photonex.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: inetd problem on NT
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <29F72BB79DF7D411AB6200B0D068C3EF2095D2@EARTH> (raw)
Thanks. I did follow pointer 1. But I have no idea as how to install the mount points in
the system mount table, right now if I do mount in a bash shell, I come up with
C:\cygwin\bin on /usr/bin type user (binmode)
C:\cygwin\lib on /usr/lib type user (binmode)
C:\cygwin on / type user (binmode)
c: on /cc type user (binmode,exec)
d: on /dd type user (binmode)
showing the mount points /, /usr/bin, and /usr/lib as user mounts. I un-mount the / and
try to mount it with
mount -bs c:\cygwin /
but it does not work.
Thanks for any further help,
-Mike
> I just downloaded and installed the lastest cygwin, set up/ran theinetd according to the inetutils document.
> When I trid to telnet to my NT, it failed and the event view says
>
> The description for Event ID ( 0 ) in Source ( inetd ) could not befound. It contains the
following insertion string(s): inetd : Win32 ProcessId = 0x9F : Cygwin Process Id = 0x9F : /etc/inetd.conf: No such fileor directory.
>
> Looks like inetd does not understand the mount points.
>
> Can anyone give me a pointer? Thanks
Two pointers, both from /usr/doc/Cygwin/inetutils-1.3.2.README:
- Before starting any program, be aware that all neccessary configuration
files in /etc have to be generated first! Call
iu-config
once after you installed the inetutils the first time. That
generates some files: [...]
- No user mount point is valid anymore! You have to install all
your mount points in the system mount table. This doesn't
change after you have logged in to a normal user account eg.
via telnet/rlogin. [...]
Corinna
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This e-mail message and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify PhotonEx immediately -- by replying to this message or by sending an email to mailto:administrator@photonex.com -- and destroy all copies of this message and any attachments. Thank You.
For more information about PhotonEx, please visit http://www.photonex.com.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-11-17 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 8:26 Michael Xue [this message]
2001-11-11 8:26 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2001-11-11 8:26 Winbox X
2001-11-11 8:26 Michael Xue
2001-11-11 8:26 ` Corinna Vinschen
2000-08-22 14:40 Inetd " Junwu Cao
2000-08-22 14:49 ` Tom Weichmann
2000-08-22 16:04 ` David Starks-Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29F72BB79DF7D411AB6200B0D068C3EF2095D2@EARTH \
--to=xue@photonex.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).