db> On Jun 08, 1996 at 19:30, Keith Richardson of 3:711/934.6 wrote:



 db>> (/^\-\-\-$/ || /^\-\-\- /) && (Qscan == 0) {

 KR> and who said that awk is a write only language (:



 db> Not me!  If the current input record (line) matches either regular

 db> expression:



only a cs major would say that, the rest of the world are sane (:



 db> and the variable Qscan is set to zero, then execute the
"action" code

 db> that follows.  You want write-only code?  Try sed or Perl!  ;-)



i have had a copy of perl for some time, i am waiting for a burst of insanity to

get to try it.



 KR> btw, speaking of linux, linux's fdisk is a heap of shit!



 db> I know!  That's why I partitioned my drives using OS/2's FDISK, then

 db> just used Linux's FDISK for the final

 db> "set-partition-type-to-format-'x'" phase.  I read somewhere of

 db> somebody having trouble with both DOS' FDISK and Linux's FDISK (can't

 db> recall specifics), but that OS/2's FDISK worked fine.  *shrug*



the dos one seemed to run fine



 KR> my install properly with separate paritions for swap and home.



 db> That's what I've done - swap, root, home, usr and var partitions (/usr

 db> is 2Gb, containing all the usual installed packages).



i dont accord linux that much resources at present, it is a toy and learning

tool, i have to do a lot more with unix in the near future as it spreads into

the mainstream. i have given /root 650 megs and /swap and /home 50 meg each,

with 48 megs of ram i dont expect a lot of swapping to go on! i have compiled

the kernel properly this time and have upgraded the kernel to 1.3.30. that was

fun with no docs (:



i do still have a problem, i cant make the damn thing print. i specified

parallel printer support in the kernel configuration, but running lpr just gets

rude messages. also is there a way of looking at .dvi files on screen? i

also

have some uglies with x-windows that look like video driver problems.



 KR> first fdisk winged like mad because the disk was more than 1 gig in size,



 db> Bloody stupid thing - did you use the command-line "fdisk" or the

 db> full-screen "cfdisk"?  In any case, it's a complete shambles.



just the command line version.



 KR> split the original partion into 3, it complained that the partitions that

 KR> *it* created were invalid because they overlapped, even though looking at

 KR> them with the "p" option didn't show this.



 db> Someone had a similar problem at work, splitting up a 4Gb drive -

 db> apparently a bug in "fdisk" itself.



linux is an interesting toy, but doesn't seem ready for prime time yet



 KR> to create the partitions, and used linux's to change these to type 83 and

 KR> 82. a good couple of hours wasted - bah humbug!



 db> Well, if you'd done it "properly" from the start...  ;-)



you are right, i should have used w95 to do it (:



                       keith





... SET PATH=Bookshelf;DeskDrawer;Closet;BoxUnderBed;GarbageCan



--- PPoint 2.00