Re: how can I find which motherboard I have and the mac address?

2008-05-02 Thread Shachar Shemesh
Amos Shapira wrote: BTW - what about writing something to the NVRAM. A quick debian package search found only nvram-wakeup but maybe that's enough. --Amos Writing something to nvram is as simple as echo something /dev/nvram. That is not the trick. The trick is writing something to

Re: how can I find which motherboard I have and the mac address?

2008-05-02 Thread sara fink
Bingo, that's a very good idea. I believe nvram-wakeup will suffice. I will read more about it. On Fri, May 2, 2008 at 8:25 AM, Amos Shapira [EMAIL PROTECTED] wrote: On Fri, May 2, 2008 at 2:38 PM, sara fink [EMAIL PROTECTED] wrote: I was trying to find as much as possible identification in

Re: IR Receiver

2008-05-02 Thread Michael Tewner
I have a friend that has built a BUNCH of LIRC receivers. IIRC, he got the parts at kashing(???) - Jerusalem, King George street - near the bell-tower building (less than one block from Yaffo). Downstairs. They have EVERYTHING. On Tue, Apr 29, 2008 at 3:58 PM, Geoffrey S. Mendelson [EMAIL

/proc/pid/mem not working?

2008-05-02 Thread Shachar Shemesh
Hi all, I'm having some strange time with /proc/pid/mem. The manual page says: /proc/[number]/mem This file can be used to access the pages of a process's memory through open(2), read(2), and lseek(2). Some digging through the internet reveals that that is, indeed, the

Re: IR Receiver

2008-05-02 Thread Geoffrey S. Mendelson
On Fri, May 02, 2008 at 01:43:30PM +0300, Michael Tewner wrote: I have a friend that has built a BUNCH of LIRC receivers. IIRC, he got the parts at kashing(???) - Jerusalem, King George street - near the bell-tower building (less than one block from Yaffo). Downstairs. They have EVERYTHING.

Re: /proc/pid/mem not working?

2008-05-02 Thread guy keren
Shachar Shemesh wrote: Hi all, I'm having some strange time with /proc/pid/mem. The manual page says: /proc/[number]/mem This file can be used to access the pages of a process's memory through open(2), read(2), and lseek(2). Some digging through the internet reveals that

Re: /proc/pid/mem not working?

2008-05-02 Thread Adam Morrison
On Fri, May 02, 2008 at 03:13:13PM +0300, Shachar Shemesh wrote: Hi all, I'm having some strange time with /proc/pid/mem. The manual page says: /proc/[number]/mem This file can be used to access the pages of a process's memory through open(2), read(2), and lseek(2).

Re: how can I find which motherboard I have and the mac address?

2008-05-02 Thread shimi
On Fri, May 2, 2008 at 12:08 AM, sara fink [EMAIL PROTECTED] wrote: I would like to know what motherboard I have and the mac address of the laptop. How can I find the information. May I suggest a more user-friendly tool for finding information about hardware than dmidecode that was already

Re: how can I find which motherboard I have and the mac address?

2008-05-02 Thread sara fink
Thanks. will try this one as well. On Fri, May 2, 2008 at 5:14 PM, shimi [EMAIL PROTECTED] wrote: On Fri, May 2, 2008 at 12:08 AM, sara fink [EMAIL PROTECTED] wrote: I would like to know what motherboard I have and the mac address of the laptop. How can I find the information. May I

Solved: /proc/pid/mem not working?

2008-05-02 Thread Shachar Shemesh
Adam Morrison wrote: Gcc sign-extends the memory pointer into a possibly-wrong value when casting to off_t, which is signed. The subsequent read() therefore tries accessing an unmapped area in the victim process and fails. Thank you! That was, indeed, the problem. Changing all casts to