Re: The disappearing sys_call_table export.

[Dmitry A. Fedorov]

On Mon, 5 May 2003 [e-mail] wrote:

> On Mon, May 05, 2003 at 08:30:38PM +0700, Dmitry A. Fedorov wrote:
> > 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.
> > And there is no risk of intersection with statically assigned major
> > numbers, as it is for many others third-party sources.
> 
> *yuck*
> 
> Do that from modprobe.  "No external utility" is not a virtue, especially
> when said utility is a trivial shell script.

What about modprobe? Dynamic major number can be acquired only by the
module itself. Only after that the appropriate /dev entry can be
created. External utility must get major number from the module
but without the /dev entry there is no communication end point with the
module.

Only two possibilities exists:

1. /dev entries created with statically assigned major/minor numbers.
It is inconvenient for third-party modules.

2. devfs or procfs (/dev entry is just a symlink to some /proc/ entry
which will be created with the device attributes later).

You should look at my approach as tiny portable private devfs library.
It would works with and without devfs, without procfs (stripped in
embedded environment), with old and new kernels.
There is no "illegal" kernel mechanisms used.

Only one thing required - availability of systems calls.