Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261301AbTEEUiR (ORCPT ); Mon, 5 May 2003 16:38:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261311AbTEEUiR (ORCPT ); Mon, 5 May 2003 16:38:17 -0400 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:9385 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id S261301AbTEEUiQ (ORCPT ); Mon, 5 May 2003 16:38:16 -0400 Date: Mon, 5 May 2003 16:50:45 -0400 From: Pete Zaitcev Message-Id: <200305052050.h45KojH30693@devserv.devel.redhat.com> To: D.A.Fedorov@inp.nsk.su cc: linux-kernel@vger.kernel.org Subject: Re: The disappearing sys_call_table export. In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1090 Lines: 30 > I use the following calls: > > sys_mknod > sys_chown > sys_umask > sys_unlink > > for creating/deleting /dev entries dynamically on driver > loading/unloading. It allows me to acquire dynamic major > number without devfs and external utility of any kind. Well, duh. "Without devds and external utility" is a no-goal. You set it, you screw trying to achieve it. It's like a well-known Russian joke: "[...] We remove the adenoid tissue... through the anal opening with a blowtorch". > I use sys_write to output loading/device detection/diagnostic > messages to process's stderr when appropriate. Yes, it may look as > "wrong thing" but it uses only legal kernel mechanisms and it saves > lots of time with e-mail support: > /sbin/insmod driver verbose=1 2>&1 | mail -s 'it does not works' me@ And pray tell how is syslog different? -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/