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 (:

Not me!  If the current input record (line) matches either regular expression:

(1) beginning of a line, three dashes, end of line;  or,
(2) beginning of a line, three dashes, a space (irrespective what follows),

and the variable Qscan is set to zero, then execute the "action"
code that follows.  You want write-only code?  Try sed or Perl!  ;-)

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

I know!  That's why I partitioned my drives using OS/2's FDISK, then just
used Linux's FDISK for the final
"set-partition-type-to-format-'x'" phase.  I read somewhere of
somebody having trouble with both DOS' FDISK and Linux's FDISK (can't
recall specifics), but that OS/2's FDISK worked fine.  *shrug*

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

That's what I've done - swap, root, home, usr and var partitions (/usr is
2Gb, containing all the usual installed packages).

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

Bloody stupid thing - did you use the command-line "fdisk" or the
full-screen "cfdisk"?  In any case, it's a complete shambles.

 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.

Someone had a similar problem at work, splitting up a 4Gb drive -
apparently a bug in "fdisk" itself.

 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!

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

    - dave
    d.begley{at}ieee.org

---