The primary goal of the question was, as you surely guessed, the relaxation of stdin processing. If we might not specify the length we could not bother with stdin dumping.
But it's ok. 1. Have you got RFC 1179 within your grasp? Let us define the set of commands which we should use in control file. 2. Can you clarify the meaning of -C -J -h -m. Each separately. What are the reasonable defaults for these options. What are the typical values for them? What level of verbosity (if -V specified) should BB lpr support? -- Vladimir 2008/2/21, walter harms <[EMAIL PROTECTED]>: > > > [EMAIL PROTECTED] wrote: > > Hi! > > > > Next iteration comes. > > Those who wanna print from BB should try it out! > > > > Do we _have to_ specify the length of data file? > > RFC 1179 states: > > > > ------ > > 6.3 03 - Receive data file > > > > +----+-------+----+------+----+ > > | 03 | Count | SP | Name | LF | > > +----+-------+----+------+----+ > > Command code - 3 > > Operand 1 - Number of bytes in data file > > Operand 2 - Name of data file > > > > The data file may contain any 8 bit values at all. > > > > !!!!!!! > > The total number of bytes in the stream may be sent as the first operand, > > otherwise the field should be cleared to 0. > > !!!!!!! > > > ------ > > > > What should be sent if Count is set equal to zero?! > > > > Interessting question, is guess the answer is it "implementation defined". > The number is important so the system can decide to reject a job when it is > to large for its spool dir. > Several printer do not check this propperly and fail misserably. > > re, > wh > > > > > > > _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
