From: Brian Hancock <bhancock@harvest.rutgers.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Printing to a network printer via ftpfs..
Date: Tue, 12 Mar 2002 14:15:28 -0500 [thread overview]
Message-ID: <200203121915.g2CJFT704640@harvest.rutgers.edu> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0203121142001.15345-100000@pali.cps.cmich.edu>
Ishwar, has it worked before?
I just tried it and it worked:
ftpfs <printer IP>
220 ID FTP Server Ready
User [default: bhancock]:
331 Username OK, send email as password.
Password:
230- Hewlett-Packard FTP Print Server Version 2.0
Directory: Description:
Port 1 Print to port 1 HP Laserjet 4100 series
230 User logged in.
215 UNIX type: L8
257 "/" is current directory
term% cp file.txt /n/ftp
226- Ready
226- Processing job
term% unmount /n/ftp
Brian
On Tuesday 12 March 2002 11:44 am, you wrote:
> Does not seem to work. Is there a way yo do it?
>
> cpu% ftpfs <printer>
> ...
> "/PRT0" is curent directory
> cpu% cp file /n/ftp
>
> just hangs..
>
> -ishwar
next prev parent reply other threads:[~2002-03-12 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 16:44 Ish Rattan
2002-03-12 19:15 ` Brian Hancock [this message]
2002-03-12 19:44 ` Ish Rattan
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=200203121915.g2CJFT704640@harvest.rutgers.edu \
--to=bhancock@harvest.rutgers.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).