Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been using ZipSlack 3.9 for the last few days on a 486DX4100 PC to replace a broken terminal. The only problem I am having is printing. The terminal had a printer connected to its printer port and the program being used printed directly to the printer. When I try printing from the PC directly, it works, e.g. cat file > /dev/lp1, but not when using the program through telnet. Also, the terminal had the name 'REPORTS' assigned to it in its BIOS Setup. The program printed to several other printers, two of them on the server. It is set up like this in the program
I have run netconfig and set up the name of the PC as 'REPORTS'. The server has Red Hat Linux 7.3. There is a device called REPORTS in the /dev directory.
A good many older terminals that had printer ports relied on "escape sequences" (special ASCII characters, generally "non-printable") which told the terminal that the information following was to be directed to an attached device, like a printer.
You didn't say what model terminal you are replacing. Look around for a terminal emulator which runs on RH 7.3 which directly emulates the model you are replacing.
Careful about adding devices to /dev. They are special and you cannot just drop devices in there without setting up the class etc., also you have to have a driver associated with them for them to work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.