On 29 December 2010 c. 13:12:21 Paul de Weerd wrote:
> On Wed, Dec 29, 2010 at 11:03:22AM +0300, Vadim Zhukov wrote:
> | On 29 December 2010 c. 04:12:34 Jeremy C. Reed wrote:
> | > tail -r
> |
> | tail(1) saves all data in memory. So if you want to reverse very big
> | file (say, some sort of log)
On Wed, Dec 29, 2010 at 11:03:22AM +0300, Vadim Zhukov wrote:
| On 29 December 2010 c. 04:12:34 Jeremy C. Reed wrote:
| > tail -r
|
| tail(1) saves all data in memory. So if you want to reverse very big file
| (say, some sort of log) you'll have to construct monsters with help of
| awk/perl/etc.
On 29 December 2010 c. 04:12:34 Jeremy C. Reed wrote:
> tail -r
tail(1) saves all data in memory. So if you want to reverse very big file
(say, some sort of log) you'll have to construct monsters with help of
awk/perl/etc.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in w
tail -r
Hello all.
A few days ago I needed to reverse a few files line-by-line (i.e.,
make first line become last and vice versa). There was nothing to do
that in base, and rev(1) utility only may reverse characters in lines.
So I decided to improve rev(1)... here it is.
While digging there I realized th
