Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!uunet!idsnh!ben
From: ben@idsnh.UUCP (Ben Smith)
Newsgroups: comp.unix.xenix
Subject: Re: SCO Xenix 2.2.1 lp problem
Message-ID: <24@idsnh.UUCP>
Date: 15 May 88 15:00:16 GMT
References: <22@libove.UUCP>
Reply-To: ben@.UUCP (Ben Smith)
Distribution: comp
Organization: Integrated Decision Systems, Inc. - NH
Lines: 22

In article <22@libove.UUCP> root@libove.UUCP (The Super User) writes:
| 
| I tar'ed off my whole SCO Xenix 2.2.1 filesystem and reinstalled only
| the most basic system from the distribution floppies, then untar'ed
| the backup back on to the system. I've found that a bunch of empty
| directories did not get restored...
| 
| I have a problem somewhere in that with the line printer stuff.
| I can't get the scheduler running. 

You almost have the answer to your problem right here in your question.
The problem is that tar will not create empty directories. It just creates
directories if they needed to copy files.

The print spooler has a number of empty directories to store its spooling
information and linked files. In particular is a directory with the "device"
name as its name under /usr/spool/lp/request.  For instance, the device
named laserjet would have a subdirectory of its own:
	/usr/spool/lp/request/laserjet

The best discussion of printer spooling is in David Fiedler's book
_UNIX_System_Administration_.