Generally, I do the following:
- if the headers are not forged, I complain to the ISP. This often
works, and the spammer's account is canceled.
- say to the relay admins in rich headers to turn relaying off (I'm a
bad admin, I haven't yet)
- many of the spammers are secondary
On Sat, 27 Jun 1998, Eugene Leitl wrote:
- if the headers are not forged, I complain to the ISP. This often
works, and the spammer's account is canceled.
Smart ones use real domains, albeit they don't belong to it. You have to
do a bit of research to find out whether they actually have a
Andrea Arcangeli wrote:
The result for x+1 is calculated in register, which is then saved
into *stack* before calling the function again (or maybe just variable
x is saved into stack, but something in any case is saved into stack).
Again, this is an implementation issue. On RISC
Hi,
I have tried to make a user-level driver for a home-grown device,
interfaced with a serial port. Unfortunately, I couldn't make it answer
fast, even if the line is set to 38400 bps. I use termios structures with
O_NOBLOCK and select() to get the answer received, but there is a delay of
20ms
Hello people,
Long time haven't talked to the list:)).. Nice to see it's doing very
well, However, here I was playing with gdb and other things trying to
learn Linux iternals, and here's thing which confuses me:
In many manuals/references and gdb messages itself i met the term frame
(change
Rildo Pragana wrote:
I have tried to make a user-level driver for a home-grown device,
interfaced with a serial port. Unfortunately, I couldn't make it answer
fast, even if the line is set to 38400 bps. I use termios structures with
O_NOBLOCK and select() to get the answer received, but
CyberPsychotic wrote:
In many manuals/references and gdb messages itself i met the term frame
(change stack frame, no frame selected, when i try to disassemble
sometimes etc). Anyone could clarify the term "frame" to me and how it
applys here?
A function typically begins with code of the
Here is a small program I wrote because I needed to use
it.
It takes a file, and splits it into pieces, whose size
is specified on the command line.
I named it hack because:
1. It is. (A hack!).
2. It hacks the file into pieces brutally.
3. All the good names (cut, split) were taken.
Share,
Moshe Zadka wrote:
Here is a small program I wrote because I needed to use
it.
It takes a file, and splits it into pieces, whose size
is specified on the command line.
I named it hack because:
1. It is. (A hack!).
2. It hacks the file into pieces brutally.
3. All the good names
