Path: utzoo!utgpu!watmath!clyde!att!ucbvax!husc6!rice!sun-spots-request From: sjs@ctt.bellcore.com (Stan Switzer) Newsgroups: comp.sys.sun Subject: Termcap, printcap, and remotes in Yellow Pages Message-ID: <8811222204.AA23011@dduck.ctt.bellcore.com> Date: 4 Dec 88 06:05:48 GMT Sender: usenet@rice.edu Organization: Rice University, Houston, Texas Lines: 24 Approved: Sun-Spots@rice.edu Original-Date: Tue, 22 Nov 88 17:04:21 EST X-Sun-Spots-Digest: Volume 7, Issue 37, message 12 of 12 Has anyone ever tried to use the yellow pages to serve termcap, printcap, or remotes entries? It seems like an obvious enough idea. It'd be simple enough to do for /etc/termcap, and it'd be a lot nicer scheme than System V's unspeakable arrangement. With /etc/printcap a problem arises: you need to be able to somehow tailor the file a little bit for each of the print servers. What'd probably work is to have entries with names "printer@sys" override entries "printer" on system "sys". The default entry "printer" would be a remote entry, and the overrides would specify the particulars for the servers. A less complicated scheme would involve having servers specify their overrides in their local printcap files followed by a "+" entry to pull in the common (remote) entries from the yellow pages. Of course, then you'd probably want to think about fixing the print spooler so that remote prints at diskless workstations don't end up flying over the net three times. But that's a whole 'nuther issue. The way some of these things work you'd thing all anyone ever did with Suns is run "shelltool rlogin." It's going to take some INTEGRATION to make the network BE the computer. Stan Switzer sjs@ctt.bellcore.com