From: Sven Vermeulen <sven.vermeulen@rug.ac.be>
To: Linux-Kernel Development Mailinglist <linux-kernel@vger.kernel.org>
Cc: Karsten Keil <keil@isdn4linux.de>
Subject: Re: 2.4.13: some compilerwarnings...
Date: Wed, 24 Oct 2001 20:25:18 +0200 [thread overview]
Message-ID: <20011024202518.A552@Zenith.starcenter> (raw)
In-Reply-To: <20011024195342.A464@Zenith.starcenter> <Pine.LNX.4.30.0110242003430.19308-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0110242003430.19308-100000@Appserv.suse.de>; from davej@suse.de on Wed, Oct 24, 2001 at 08:07:42PM +0200
On Wed, Oct 24, 2001 at 08:07:42PM +0200, Dave Jones wrote:
[ About md5sum warnings about incorrect md5sum's ]
> Been there for a while, and should be harmless.
> If you really cared, you could add the new md5sums to the script
> that does the checking.
Can't do that. Those md5sum's are there for a reason.
In $LINUXSOURCE/Documentation/isdn/HiSax.cert :
[...]
If you change the main files of the HiSax ISDN stack, the certification
will become invalid. Because in most countries it is illegal to connect
unapproved ISDN equipment to the public network, I have to guarantee that
changes in HiSax do not affect the certification.
In order to make a valid certification apparent to the user, I have built
in some validation checks that are made during the make process. The HiSax
main files are protected by md5 checksums and the md5sum file is pgp
signed by myself:
[...]
Sven Vermeulen
--
I develop for Linux for a living, I used to develop for DOS. Going from
DOS to Linux is like trading a glider for an F117. ~(Lawrence Foard)
next prev parent reply other threads:[~2001-10-24 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 17:53 2.4.13: some compilerwarnings Sven Vermeulen
2001-10-24 18:07 ` Dave Jones
2001-10-24 18:25 ` Sven Vermeulen [this message]
2001-10-24 18:48 ` Dave Jones
2001-10-25 18:15 ` André Dahlqvist
2001-10-24 22:20 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011024202518.A552@Zenith.starcenter \
--to=sven.vermeulen@rug.ac.be \
--cc=keil@isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox