deo@eecs.cs.pdx.edu (Steven Furber) (11/18/90)
Has anyone been able to use the printer (/dev/lp) with very much success? So far when I try to print I get about 1 page with the rest of it cut off. I've checked to make sure that the /dev/lp is set up according to /etc/stup_root. I have also applied the various fixes that Pickert has put up on this newsgroup and recompiled everything with only a few warnings about incompatible pointer types. Once recompiled and rebooted with the NEWboot, ps still will not work. The problem is that it cannot read /dev/kmem (error: 0) for the proc table. Ideas?
webber@csd.uwo.ca (Robert E. Webber) (11/18/90)
In article <700@pdxgate.UUCP> deo@eecs.cs.pdx.edu (Steven Furber) writes: >I have also applied the various fixes that Pickert has put up on this newsgroup >and recompiled everything with only a few warnings about incompatible pointer >types. Once recompiled and rebooted with the NEWboot, ps still will not work. >The problem is that it cannot read /dev/kmem (error: 0) for the proc table. > >Ideas? chmod'ing ps to 4755 was the only thing I had to do other than following Pickert's patches. I installed the patches by hand rather than thru patch. Turns out that it is necessary for the test directory to be publically writable in order for some of the test routines to work. In the shell test routines, one of the tests done is on patch. It didn't work until I chmem'd patch. Patch would claim not to be able to install patch through one strategy and then would apparently quit while trying other strategy. Examining the files afterword, some of the patch worked and some didn't. If you have been installing the patches using the patch program, it might be worthwhile taking a look at the resulting files just to be sure. --- BOB (webber@csd.uwo.ca)
archetyp@uxh.cso.uiuc.edu (Joseph R Pickert) (11/20/90)
deo@eecs.cs.pdx.edu (Steven Furber) writes: >Has anyone been able to use the printer (/dev/lp) with very much success? So >far when I try to print I get about 1 page with the rest of it cut off. I've >checked to make sure that the /dev/lp is set up according to /etc/stup_root. /dev/lp buffers up a page in memory. Always use pr to print to it. If you print 1.5 pages, the second page won't come out until you print an additional .5 pages (in lines that is, not chars or words). For ps, don't forget to chmod the new ps you built so it can read /dev/kmem.
jhf@c3.lanl.gov (Joe Fasel) (11/20/90)
In article <1990Nov19.182656.22199@ux1.cso.uiuc.edu> archetyp@uxh.cso.uiuc.edu (Joseph R Pickert) writes: >/dev/lp buffers up a page in memory. Always use pr to print to it. >If you print 1.5 pages, the second page won't come out until you print >an additional .5 pages (in lines that is, not chars or words). Does a close system call flush the page buffer? What about termination of a process that has /dev/lp open? --Joe Fasel Los Alamos National Laboratory