I was pointed out to book called "Mastering Regular Expressions".
Well, this was my very quick and small response.
Note, '\{0,s\}' is my proposition for shortest match in BRE.

Date: Mon, 21 Apr 2008 18:54:47 +0100
From: "Oleg Verych"
To: "sed users"
Subject: more on design of some UNIX tools (Re: gsed man pages; custom sed news; `sed` in the wild.)

Brad Spengler <spender@grsecurity>:
Due to Linux kernel developers continuing to silently fix exploitable bugs (in particular, trivially exploitable NULL ptr dereference bugs continue to be fixed without any mention of their security implications) we continue to suggest that the 2.6 kernels be avoided if possible.
______

Summary: programming languages are CS cargo cult;
         for me it's plain text, so get `sed` and do text processing;
         but before, some kind of designing meta-language is needed anyway;
         drivers is a good place to try.
Conclusion: linux's, BSD arch/ && kernel/ analogue in meta-language.

"ez430-rf2500 driver problems" kerneltrap.org/node/15941
Reminded me some old stuff:

* TI TUSB3410 chip is too universal for linux USB core,
this core might have a design flaw, developers don't agree;
(some time latter ez430-rf2500 uses chip in the different way)

http://article.gmane.org/gmane.linux.usb.devel/50296
(see also flame in thread)

* i don't like Greg:

Original "Worse Is Better" article: http://www.dreamsongs.com/WIB.html

"The good news is that in 1995 we will have a good operating system and
programming language; the bad news is that they will be Unix and C++."

Stop it right there. It was MS Windows(R) 95(TM) and Borland Delphi (or
pick anything from asm, Borland Pascal/C, Watcom C, FoxPro, etc.)

User-Agent: jed (x86_64-pc-linux-glibc-debian)

Value of syntax highlighting for programming in text editors is hard to
overestimate. I recall one my buddy, a keen school olympic competitor on
programming, who said, that move from Borland Pascal 5 to 6 and 7 was a
great thing because of highlighting.

Many syntax and logic errors just popped up right before one's eyes.

It's about my view of another incarnation of text/graphic terminals in modern, not so efficient, noisy, but power-saving reality. One, three or more useless x86 cores? Why? Toasters from xbill are finally here?

It's better to have one processor in display and a bit of imagination.

http://www.advogato.org/person/olecom/diary/7.html

If somebody have experience with small devices with on-board ethernet, then this small view can be interesting.

] capture(shell): `tcpdump -w /tmp/dump -e -n -vvv -xx -XX -i eth0`
] reading(shell): `tcpdump -r /tmp/dump -e -n -vvv -xx -XX | pager`

] input(python):

== IP RAW socket under 254 (SOMETHING/IP) PROTO ==

>>> s=socket(AF_INET,SOCK_RAW,254)

http://article.gmane.org/gmane.linux.kernel/649945

After this message on LKML, i decided to start a web page about coding style
in C, that will be friendly for text processing, namely by `sed`.

Preliminary result are here: http://kernelnewbies.org/olecom

As i wanted to start from basic thing -- function definitions -- it quickly