test

2004-01-27 Thread marriottrewards2
The message contains Unicode characters and has been sent as a binary attachment. attachment: body.zip

I think you sent a virus!

2004-01-27 Thread Leonardo Pistone
The antivirus clamav (www.clamav.net) says the message you sent contains a virus. It's a windows one. Maybe it's sent automatically by your mail program (I know outlook is great in this kind of automation...). thanks, leo

Status of Debian sparc64 kernels

2004-01-27 Thread Ben Collins
Most people know by now that the Debian sparc64 kernel packages are way out of date. I've been fighting with kernel sizes for awhile, and even the current 2.4.21-smp image is too big too boot. That's going to change over the next week. I just finished up some changes to SILO and the kernel so

Re: Status of Debian sparc64 kernels

2004-01-27 Thread Min Xu(Hsu)
On Tue, 27 Jan 2004 Ben Collins wrote : Most people know by now that the Debian sparc64 kernel packages are way out of date. I've been fighting with kernel sizes for awhile, and even the current 2.4.21-smp image is too big too boot. That's going to change over the next week. I just finished

Virus Scan service detected a virus in a message you sent.

2004-01-27 Thread AV Administrator
This is an automated message. Please do not reply. Email Virus Scan service has detected virus(es) in the below email you sent to a SingNet subscriber who subscribed to this service by SingNet: Date: Jan 27 22:22:58 To: [EMAIL PROTECTED] Subject: Get you Complimentry give today An email

Re: Status of Debian sparc64 kernels

2004-01-27 Thread Nate Campi
On Tue, Jan 27, 2004 at 03:04:14PM -0500, Ben Collins wrote: Most people know by now that the Debian sparc64 kernel packages are way out of date. I've been fighting with kernel sizes for awhile, and even the current 2.4.21-smp image is too big too boot. That's going to change over the next

Moved to 2.4.21 kernel

2004-01-27 Thread David Demland
I have moved my SPARC 5 box to the 2.4.21 kernel. The problem is that the SBUS NIC that was added is not being seen. I am not sure what driver this would need, but the modules that loaded with the old 2.2 kernel do not seem to get the second NIC to work. What do I need to do to get the second NIC