On Sun, Mar 16, 2008 at 3:35 AM, vichy [EMAIL PROTECTED] wrote:
Dear all:
I plug my mass storage to my computer.
But how could I know the exact controller and port number that my device
plugs in?
Hi.
dmesg ?
N.-
--
http://arhuaco.org
--
To unsubscribe from this list: send an email
vichy, Sunday, 16. March 2008:
I plug my mass storage to my computer.
But how could I know the exact controller and port number that my device
plugs in?
What about lsusb?
Markus
--
To unsubscribe from this list: send an email with
unsubscribe kernelnewbies to [EMAIL PROTECTED]
Please read
Hi all,
I was reading about the lost-write problem in filesystems (see link
below) and wanted to know how traditional linux systems like
ext{2,3,4} or other popular ones handle this case, since most/all of
them don't have any control over the raid.
Really a very informative and interesting thread.
Thank you all for your efforts.
Rgds,
Adil
On 3/16/08, Peter Teoh [EMAIL PROTECTED] wrote:
Thank you everyone for the time spent in the analysis. I understand
better now.
I was confused, as I thought the module_free() below actually free
Hello,
I'm trying to understand how the bytes I get from recv(2) comes
through the nic to the sockets interface. I tried following it from
sys_recv (net/socket.c) to the driver functions being used. But I got
stuck on:
err = security_socket_recvmsg(sock, msg, size, flags);
and
