From owner-freebsd-hackers Tue Apr 15 06:39:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA09796 for hackers-outgoing; Tue, 15 Apr 1997 06:39:28 -0700 (PDT) Received: from inter03.lion.net ([195.50.148.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA09790 for ; Tue, 15 Apr 1997 06:39:22 -0700 (PDT) Received: from lucky.lion.de ([192.109.89.2]) by inter03.lion.net (Netscape Mail Server v2.0) with SMTP id AAA8840; Tue, 15 Apr 1997 15:36:39 +0200 Received: from willi.lion.de by lucky.lion.de (SMI-8.6/SMI-4.1) id PAA00756; Tue, 15 Apr 1997 15:38:11 +0200 Received: from localhost by willi.lion.de (5.x/SMI-SVR4) id AA13323; Tue, 15 Apr 1997 15:37:59 +0200 Date: Tue, 15 Apr 1997 15:37:59 +0200 (MET DST) From: Christoph Haas To: Joerg Wunsch Cc: freebsd-hackers@FreeBSD.org Subject: Re: Commercial vendors registry In-Reply-To: <19970414215550.KK19956@uriah.heep.sax.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Apr 1997, J Wunsch wrote: > > whether you (the developers) try to help me a little bit or not. All I ask > > from you is to leave me a little note if you break something seriuosly. I > > Well, the problem with this is, you often don't know that you're > breaking something, Right, but that's ok. I want to be informed if you break something on purpose. If you, for example, know that you are going to break the syntax of a certain command or a kernel structure, then why not drop me a short note about it ? Of course you are not supposed to tell me "everything that might break today, tommorow, next week or not at all". Just obvious changes... > let alone that it might be something very > important for a particular vendor. Well, that's what I wanted certain information from registered vendors for. If they tell me that they rely on certain parts of the kernel or on userland commands, I can inform them about chnages in the next RELEASE. > Things like the utmp change are > obvious, but there was no secret about it. Other things are hidden > gotchas, where it will only be apparent afterwards that they might > have broken some compatibility. Shit happens ;-). But if it's allready broken, vendors can send their complaints to me, and I'll try to dispatch them. So if we find a bug in the PCI subsystem, I would forward the report to Stefan Esser (just an example. No, don't beat me, Stefan!!) We can't expect every vendor to know who is responsible for what part of the system. So we should provide a single "help desk". Christoph -- Christoph Haas o.tel.o GmbH | Never trust an operating UNIX Sysadmin Universitaetsstrasse 140| system you don't have the 44799 Bochum / Germany | sources for. mailto:haas@lion.de http://www.o-tel-o.de | http://www.freebsd.org