inetd on a Win95 machine

inetd on a Win95 machine

[EXT-Reuter, Chris H]

I'm trying to set a telnet session up from another platform to a win95 machine.  I get inetd to start and telnet in to the win95 platform. The telnetd -D report info looks good up until the point where it gives the error: "no such file: /bin/login". My paths in bash all look link /cygdrive/c/.....

I started out on my WinNT machine, where all my paths look like unix paths from within bash, and I can telnet into my  NT machine (but I don't have the right answers for the login prompt)

Also, what do I need to supply setup.exe?  When I install from a local directory, it never finds anything to install?  I've been unziping downloads by hand. Do my problems originate here?

--
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/

Re: inetd on a Win95 machine

[Larry Hall (RFK Partners, Inc)]

At 04:47 PM 7/24/2001, EXT-Reuter, Chris H wrote:
>I'm trying to set a telnet session up from another platform to a win95 machine.  I get inetd to start and telnet in to the win95 platform. The telnetd -D report info looks good up until the point where it gives the error: "no such file: /bin/login". My paths in bash all look link /cygdrive/c/.....
>
>I started out on my WinNT machine, where all my paths look like unix paths from within bash, and I can telnet into my  NT machine (but I don't have the right answers for the login prompt)
>
>Also, what do I need to supply setup.exe?  When I install from a local directory, it never finds anything to install?  I've been unziping downloads by hand. Do my problems originate here?



Are you using the latest setup.exe?  Your problems are due to the fact that
you're unzipping by hand.  You won't have everything you need to have setup
(pun intended :-) ) if you don't run setup.exe.  In the case of the paths 
you mention, the mount points for "/", "bin", and "lib" haven't been 
created.  Mind you, you can manually do all the things that setup would do 
for you and get a working installation but its going to be easier in the 
long run if you just blow away what you have and let setup.exe do it all 
for you.



Larry


--
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/

Re: inetd on a Win95 machine

[Peter Buckley]

"EXT-Reuter, Chris H" wrote:
> 
> I'm trying to set a telnet session up from another platform to a win95 machine.  I get inetd to start and telnet in to the win95 platform. The telnetd -D report info looks good up until the point where it gives the error: "no such file: /bin/login". My paths in bash all look link /cygdrive/c/.....

I remember seeing something about there being a different way to 
setup inetd and other such things that need /etc/passwd and /etc/group 
because Win95/98 don't handle the user/security stuff the same way 
as NT/2000. Try searching google for 

inetd win98 site:cygwin.com

> 
> I started out on my WinNT machine, where all my paths look like unix paths from within bash, and I can telnet into my  NT machine (but I don't have the right answers for the login prompt)
> 
> Also, what do I need to supply setup.exe?  When I install from a local directory, it never finds anything to install?  I've been unziping downloads by hand. Do my problems originate here?

Unzipping downloads by hand is "not recommended" (especially if you 
don't download ALL the packages). You should use setup.exe to download 
ALL the packages to a local directory, and then use setup.exe to install
from that local directory.

HTH,
Peter

> 
> --
> 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/

--
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/

Mount //./cdrom0 problem

[Bruce Dobrin]

Hi,
I've been backing up cd images by mounting them as block devices and using
dd to dump the image to a file  (all on win2k).   I just tryiied this on my
NT4 machine and found that :  "   mount -f -b  //./cdrom0 /dev/cda "
doesn't seem to work on NT (but works fine on win2k).  I get an error that
/dev/cda is not a recognized file or directory.  Is the Block Device name
for the cdrom on NT different than the name on Win2k?  (I tried //./cd-rom0
too,  to no effect).  Has anyone else had success with mounting the CD-rom
Bolck device on NT?

Thanks,
Bruce Dobrin...


--
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/

Re: Mount //./cdrom0 problem

[Corinna Vinschen]

On Tue, Jul 24, 2001 at 02:26:29PM -0700, Bruce Dobrin wrote:
> Hi,
> I've been backing up cd images by mounting them as block devices and using
> dd to dump the image to a file  (all on win2k).   I just tryiied this on my
> NT4 machine and found that :  "   mount -f -b  //./cdrom0 /dev/cda "
> doesn't seem to work on NT (but works fine on win2k).  I get an error that
> /dev/cda is not a recognized file or directory.  Is the Block Device name
> for the cdrom on NT different than the name on Win2k?  (I tried //./cd-rom0
> too,  to no effect).  Has anyone else had success with mounting the CD-rom
> Bolck device on NT?

You can access the cd-rom on both, NT4 and W2K, using the drive letter:

	mount -f -b //./F: /dev/cda

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: Mount //./cdrom0 problem

[Larry Hall (RFK Partners, Inc)]

At 05:57 PM 7/24/2001, Corinna Vinschen wrote:
>On Tue, Jul 24, 2001 at 02:26:29PM -0700, Bruce Dobrin wrote:
> > Hi,
> > I've been backing up cd images by mounting them as block devices and using
> > dd to dump the image to a file  (all on win2k).   I just tryiied this on my
> > NT4 machine and found that :  "   mount -f -b  //./cdrom0 /dev/cda "
> > doesn't seem to work on NT (but works fine on win2k).  I get an error that
> > /dev/cda is not a recognized file or directory.  Is the Block Device name
> > for the cdrom on NT different than the name on Win2k?  (I tried //./cd-rom0
> > too,  to no effect).  Has anyone else had success with mounting the CD-rom
> > Bolck device on NT?
>
>You can access the cd-rom on both, NT4 and W2K, using the drive letter:
>
>         mount -f -b //./F: /dev/cda
>
>Corinna



Quite true.  The problem you're having Bruce is that you rely on symbolic
names defined in the O/S.  cdrom0 exists in W2K but not in NT.  If your
interested to see the differences in this area between W2K and NT, I 
recommend WinObj which you can get at www.sysinternals.com.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: Mount //./cdrom0 problem

[Bruce Dobrin]

Thank you for the pointer to WinObj. (It also explained much which was
previously cryptic in the way the two os's handle devices and Net volumes as
well as the afore mentioned cdrom0 question).  I had been worried that
mounting the link to the drive letter,  might have bypassed blocks
accessible  by the block device link (as is the case with physicaldisk0 and
the drive letter).  I see now that this is not the case with the CDROM.

Thanks again
B. Dobrin


----- Original Message -----
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "Corinna Vinschen" <cygwin@cygwin.com>; <cygwin@cygwin.com>
Sent: Tuesday, July 24, 2001 3:10 PM
Subject: Re: Mount //./cdrom0 problem


> At 05:57 PM 7/24/2001, Corinna Vinschen wrote:
> >On Tue, Jul 24, 2001 at 02:26:29PM -0700, Bruce Dobrin wrote:
> > > Hi,
> > > I've been backing up cd images by mounting them as block devices and
using
> > > dd to dump the image to a file  (all on win2k).   I just tryiied this
on my
> > > NT4 machine and found that :  "   mount -f -b  //./cdrom0 /dev/cda "
> > > doesn't seem to work on NT (but works fine on win2k).  I get an error
that
> > > /dev/cda is not a recognized file or directory.  Is the Block Device
name
> > > for the cdrom on NT different than the name on Win2k?  (I tried
//./cd-rom0
> > > too,  to no effect).  Has anyone else had success with mounting the
CD-rom
> > > Bolck device on NT?
> >
> >You can access the cd-rom on both, NT4 and W2K, using the drive letter:
> >
> >         mount -f -b //./F: /dev/cda
> >
> >Corinna
>
>
>
> Quite true.  The problem you're having Bruce is that you rely on symbolic
> names defined in the O/S.  cdrom0 exists in W2K but not in NT.  If your
> interested to see the differences in this area between W2K and NT, I
> recommend WinObj which you can get at www.sysinternals.com.
>
>
>
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 118 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
>
>
> --
> 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/
>


--
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/