Dev9 1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Dev9 1 (Default branch)
# 1  
Old 10-06-2008
Dev9 1 (Default branch)

Dev9 is a Linux /dev manager. The idea is to writea 9p2000.u server that ends up providing the samefunctionality as a combined devfs and udev.License: BSD License (revised)Changes:
This is the first release of the project. It should theoretically work, but there are some issues with character devices. Nevertheless, automounting, socket I/O, parsing /sys, creating device nodes themselves, and processing rules to create nodes all work as they should.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
DEV_CLONE(9)						   BSD Kernel Developer's Manual					      DEV_CLONE(9)

NAME
dev_clone, drain_dev_clone_events -- eventhandler for name-based device cloning in devfs SYNOPSIS
#include <sys/param.h> #include <sys/conf.h> void clone_handler(void *arg, struct ucred *cr, char *name, int namelen, struct cdev **dev); EVENTHANDLER_REGISTER(dev_clone, clone_handler, arg, priority); void drain_dev_clone_events(); DESCRIPTION
A device driver may register a listener that will be notified each time a name lookup on the devfs(5) mount point fails to find the vnode. A listener shall be registered for the dev_clone event. When called, it is supplied with the first argument arg that was specified at handler registration time, appropriate credentials cr, and a name name of length namelen that we look for. If the handler decides that the name is appropriate and wants to create the device that will be associated with the name, it should return it to devfs in the dev argument. The drain_dev_clone_events() function is a barrier. It is guaranteed that all calls to eventhandlers for dev_clone that were started before drain_dev_clone_events() call, are finished before it returns control. SEE ALSO
devfs(5), namei(9) BSD
January 3, 2009 BSD