Hi,
In some cases, as have been mentioned in Advanced Programming in Unix
Environment, by Richard Stevens, files with holes report different sizes
with du -s and ls -l. But how does the reporting of du and ls -l
actually differ? What is the fundamental difference between them??
Hoping for
SVisor a écrit :
I wanted a file of garbage, not zeroes.
So I tried: dd if=/dev/random of=file bs=1k count=1024
Nope I did not abort it, I just moved the mouse to generate more random
numbers (with dd running in X terminal). What dd says is:
0+1024 records in
0+1024 records out
You have read a
On Fri, 2004-12-17 at 21:54 +0530, Rajat Jain, Noida wrote:
>
> Hi,
>
> Thanks for the reply.
>
> Actually I am developing a loadable kernel module. I agree that at the bare
> minimum, I need to copy from the NIC's device buffer to kernel's allocated
> sk_buff (socket buffer). What I want is to
I had that problem too a long time ago - it would show only a L but no
error code. (I didn't try with GRUB.) I have no idea whatsoever of
what machine it was, but I do know it had winxp on a dual boot too. I
was a mere mortal back then (win user) and believed that on a crash
the best thing was to r
Hi,
Thanks for the reply.
Actually I am developing a loadable kernel module. I agree that at the bare
minimum, I need to copy from the NIC's device buffer to kernel's allocated
sk_buff (socket buffer). What I want is to avoid FURTHER coying of data from
the sk_buffs to the buffers allocated by
