Re: assembly code in the loadable kernel module

["Robert P. J. Day" <rpjday@mindspring.com>]

On Fri, 27 Apr 2007, Marat Buharov wrote:

> On 4/27/07, Parav K Pandit <Parav_Pandit@mindtree.com> wrote:
> > DISCLAIMER:
> > This message (including attachment if any) is confidential and may be
> > privileged. Before opening attachments please check them for viruses and
> > defects. MindTree Consulting Limited (MindTree) will not be responsible for
> > any viruses or defects or any forwarded attachments emanating either from
> > within MindTree or outside. If you have received this message by mistake
> > please notify the sender by return  e-mail and delete this message from your
> > system. Any unauthorized use or dissemination of this message in whole or in
> > part is strictly prohibited.  Please note that e-mails are susceptible to
> > change and MindTree shall not be liable for any improper, untimely or
> > incomplete transmission.
>
> On 4/27/07, linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
> > ****************************************************************
> > The information transmitted in this message is confidential and may be
> > privileged.  Any review, retransmission, dissemination, or other use of this
> > information by persons or entities other than the intended recipient is
> > prohibited.  If you are not the intended recipient, please notify Analogic
> > Corporation immediately - by replying to this message or by sending an email
> > to DeliveryErrors@analogic.com - and destroy all copies of this information,
> > including any attachments, without reading or disclosing them.
>
> Damn, people. Please, remove that sort of disclaimers (about
> confidential information) while posting to public mailing lists.

good luck.  this issue comes up on a regular basis on mailing lists
all over the place and the response is always the same -- some
companies, based on the advice of their legal departments, absolutely
*require* those rambling, worthless disclaimers, and the senders have
no ability whatsoever to turn them off.

there is only one solution to that sort of thing -- blacklist the
entire sending domain until they get a clue.  yes, it's draconian, but
there's really no other way to educate them.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================