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 order to > > know when the service will claim that motherboard was changed, that > > indeed it was changed. > > Then, in addition to the high tech methods, you can probably resolve > to some low-tech like putting a mark and/or a sticker on some > component on the board. If you do it conspicuous enough they probably > won't bother moving it to the other board. > > BTW - what about writing something to the NVRAM. A quick debian > package search found only "nvram-wakeup" but maybe that's enough. > > --Amos > > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
