Record Buffer Provided By Awk

I have got a data file that contains 22 records.

When i write an awk script to compute the number of records, i print the value of NR variable. Why does it show 23 instead of 22?

I get the same output from FNR variable also. So what is the difference between NR and FNR variable?

In the text i found that
NR: gives number of records read- record number in the current file
FNR: file number of records read- a record number in the current file

I would like to learn more about an MX record and how to set it up.

I am using Debian 7 KVM in a cloud and I find the keyboard buffer in a terminal window is about 35 characters in length thus when I run my keyboard emulator, I have to pause after 35 keys in order not to overflow the buffer.

I want to be able to login and dump the instructions to the KVM server then go to the next one. e.g If I wanted a mass roll out of Yacy search engines or other applications.

I know no Human can type that fast. But my Program can on the PS2 interface.
The USB keyboard port maxes out a 700 WPM
over 5000 Word Per Minute

I am new to drivers development under linux kernel. After starting with the simple examples from the book Linux Device Drivers v3, I realised that the block driver API has been totally changed since the kernel 2.6.31 or maybe later versions, and I couldn't find any documentation about the new API and how to use it. There are just some few comments in the source code.

After struggling for one month I almost had something working but few parts are missing or I misunderstood something.

Here is the situation :

After fetching the request with blk_fetch_request(q), I use the macro __rq_for_each_bio for handling the full request
To transfer the segments one by one I use the macro bio_for_each_segment(bvec, bio, i) that loops over all the segments in a bio

My question is :

I need to do some DMA from/to my device (the dma engine is within the device), that's why I need some address that I could use it to DMA from/to
Which buffer should I use ? for the moment I use the buffer returned by char *buffer=bio_data(bio), Does "buffer" corresponds to the physical buffer that I can use for DMA
How to end the request in this case ? using __blk_end_request_cur(req, 0) ? or using __blk_end_request(req, 0, bytes) ?

If you don't have an answer to any of these questions, where can I find a useful documentation for the new API of the block device drivers.

I am able to view my tv@nywhere card with tv time, but when I tried to record with VLC media player I couldn't switch to the proper source. How can I switch the source or what other program can I use with knoppix 7.4. Any advice will be greatly appreciated.
Thanx
Alsparko

sir, i need to set buffer to reduce the packet loss in wireless scenerio
how can i do it? can i use queue in wireless in ns2.35?

Hi, for scientific reasons I need to record 8 audio channels simultaniously. The process has to be automated, so I want to run everything from commandline.
The device I'm using is a Presonus Audiobox 1818VSL. Ideally it should feed a RaspberryPi which stores it on a external harddrive. For my porpuse the samplerate doesn't really matter, but the file size should not not be to large. So 16 bit and 4 to 8 kHz would be great.
Up to now I've tried to use arecord with every posssible format, bitsize and samplerate, but nothing worked out so far. Obviously arecord missinterpretes the incoming signal, what results in pretty large and samplerate dependend noise.
Surprisingly everthings fine with the recording via audacity, which excludes the possibility of driver problems or something like that.
Does anybody have an idea how to solve this problem?
Thanks in advance

I remember there is this record that the OS uses to keep track of each file. and if this file runs out of space then we would get this error. but i can't recall the name of it or how to fix it. I think it is called inodes or something like that?

are you guys famaliar with what I am talking about?

Hi all,

I am trying to simulate leach on NS2 but I've had problems with running the leach_test. I've followed all steps from installing NS2 up to installing the LEACH patch (used the latest one from exidus). Here's the error message in the leach.err I found.

Code:

couldn't read file "/mit/uAMPS/uamps.tcl": no such file or directory
    while executing
"source.orig /mit/uAMPS/uamps.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel source.orig[list $fileName]"
    invoked from within
"if [$instance_ is_http_url $fileName] {
set buffer [$instance_ read_url $fileName]
uplevel eval $buffer
} else {
uplevel source.orig[list $fileName]
..."
    (procedure "source" line 8)
    invoked from within
"source /mit/uAMPS/uamps.tcl"
    (file "tcl/mobility/leach.tcl" line 18)
    invoked from within
"source.orig tcl/mobility/leach.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel source.orig[list $fileName]"
    invoked from within
"if [$instance_ is_http_url $fileName] {
set buffer [$instance_ read_url $fileName]
uplevel eval $buffer
} else {
uplevel source.orig[list $fileName]
..."
    (procedure "source" line 8)
    invoked from within
"source tcl/mobility/$opt(rp).tcl"
    (file "tcl/ex/wireless.tcl" line 187)

Your help are very much appreciated, thanks!

Hello,

I have a file server that was built before my time here. Unfortunately it was not built very well, and of course it became more and more important to production.

Using LVM the following was created:
/dev/mapper/vg_weather-sff_share 34T 30T 3.4T 90% /sff_share

This is currently made up of 30 + different volumes. I do not want to continue growth here. Our developers need to be able to write to the date in /sff_share. The data is to large to be moved or copied.

I was thinking about creating a new fresh mount /sff_share1 and building a sim link to /sff_share so that the data will still be able to be accessed, but new data will be written to he fresh file system / volume attached to /sff_share1. So to the script everything can be accessed under /sff_share.

Does this sound like a good route? Or might there be a better option.

1. I need to get write to stop on the current /sff_share
2. New data needs to write to /sff_share1
3. Both /sff_share and /sff_share1 need to be accessible under /sff_share