rtregn@immd3.informatik.uni-erlangen.de (Robert Regn) (09/07/88)
In our institute we have an IBM AT 6 MHz and an IBM proprinter. I get always the error: printer out of paper - printer error. I have tried to force a) the monochrome adress b) the color adress (we have a coulor monitor) - but same results. On other machines (and other printers) the driver works. In <850@ast.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes: >... and make up the final, definitive, never-again-to-changed V1.3, But please send no update vs. 1.3b but vs. 1.3a (or 1.2). Many people can so skip a step and spare a lot of work. (Updating kernel, lib and commands requires about 30 hours on an AT) >Discussion on the subject of cdiff/patch vs diff/fix should be posted I like diff/fix. The cdiffs are MUCH to big. The context is not necessary because many people don't look at the diff's. People with own fixes should have official versions too. - - - - I have written a shell script to check the sums: (it uses a sum file produced by suns: <sum> <block> <name> ) sed 's/^X//' >cksum <<EOF X#verify the checksums given in a file $1 X Xif test $# -ne 1 Xthen echo usage: $0 sumfile Xexit Xfi Xcount=1 Xfile=$1 Xset `wc -l $file` Xlen=$1 X Xwhile test $count -le $len Xdo Xset `head -$count $file |tail -1` X#sort information in checkfile line Xname=$3 Xsum=$1 Xblock=$2 X#run sum Xset `sum $name` Xif test $sum -ne $1 Xthen echo sum von $name falsch Xelse echo -n $name OK ' ' Xfi Xif test $block -ne `expr \\( $2 + 1 \\) / 2` Xthen echo block von $name falsch Xelse echo $name OK Xfi Xcount=`expr $count + 1` Xdone EOF if test `wc -c cksum` -ne 498 then echo Error in cksum fi - - - - The length of ls.c, cp.c, dosread.c and df.c of 1.3a are are not the same as posted in #7 (<768@ast.cs.vu.nl>). There were posted two chgrp.c this year but none with the lenth specified in #7. No length agreement further exists for compress.c ed.c file.c lorder.c. commands/tty.c and diskcheck.c i have never seen. Robert Regn rtregn.faui32.uucp ==================================================================== My wishes for christmas: Virtual terminals for minix (like xenix) or Berkeley enhancements for process control ====================================================================
paula@bcsaic.UUCP (Paul Allen) (09/09/88)
In article <630@faui44.informatik.uni-erlangen.de> rtregn@immd3.informatik.uni-erlangen.de (Robert Regn) writes: > >In <850@ast.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes: >>... and make up the final, definitive, never-again-to-changed V1.3, >But please send no update vs. 1.3b but vs. 1.3a (or 1.2). >Many people can so skip a step and spare a lot of work. >(Updating kernel, lib and commands requires about 30 hours on an AT) I agree that it would be less work if the final 1.3c diffs were relative to 1.2, but is MINIX really that slow? I keep my canonical reference copies of 1.1, 1.2, and 1.3* on a Sun. The major time-consumer when generating 1.2 was in assembling the *true* set of 1.2 diffs! Once I had settled on which diffs really defined 1.2, a script something like the following applied them in just a few minutes: for n in *.dif do patch `basename $n .dif` $n done Then all I had to do was go through the .rejects files and fix up the hunks that didn't apply properly. I can believe that *compiling* the whole mess would take a while! I have not been able to get all the way through a complete make of everything on my Sun IPC. MINIX won't talk to the IPC's hard disk because it is really emulated by a file in the Sun file system. Running a make on the IPC's floppies usually results in a diskette error after about a half hour of clunking away. I suspect some sort of timing glitch in the floppy driver, but haven't spent much time on it. >>Discussion on the subject of cdiff/patch vs diff/fix should be posted >I like diff/fix. The cdiffs are MUCH to big. The context is not necessary >because many people don't look at the diff's. People with own fixes should >have official versions too. Patch is much more robust than fix. I attempted to use fix to apply 1.2 and gave it up as unuseable. With due respect to the people who wrote and enhanced the fix program, patch is better. I am willing to pay the space penalty of context diffs in order to have the context around when a diff collides with a local hack and I have to apply it by hand. 'nuff for now... Paul -- ------------------------------------------------------------------------ Paul L. Allen | paula@boeing.com Boeing Advanced Technology Center | ...!uw-beaver!ssc-vax!bcsaic!paula