bird/sysdep/unix/Modules

log.c
main_helper.c
main_helper.h
timer.h
io.c
unix.h
endian.h
config.Y
random.c

krt.c
krt.h
krt.Y
The library is now glued together from generic and OS-dependent parts by the `mergedirs' script. Few more IP address manipulation functions and some fixes. 1998-05-15 07:56:13 +00:00			`log.c`
Birdtest: Purge 'int main()' from lib/birdlib.a #1 We need link lib/birdlib.a and remaining */all.o to tests (mockups suck) Code from sysdep/unix/main.c is moved without 'int main()' function to the sysdep/unix/main_helper.c Yes, it is dirty... After remake new BIRD's build system will be this commit reverting... Actually it is not possible to build executable bird, birdc nor birdcl due duplicity of functions in main_helper.o in lib/birdlib.a and lib/main.o 2015-08-05 09:35:46 +02:00			`main_helper.c`
Birdtest: Purge 'int main()' from lib/birdlib.a #2 All origin static functions from sysdep/unix/main.c were rewrited to non-static. All origin static global variables from sysdep/unix/main.c was rewrited to extern. It is possible create executables bird, birdc and birdcl as well as run unit tests without mockuping After remake new BIRD's build system will be this commit reverting... 2015-08-05 11:42:40 +02:00			`main_helper.h`
The library is now glued together from generic and OS-dependent parts by the `mergedirs' script. Few more IP address manipulation functions and some fixes. 1998-05-15 07:56:13 +00:00			`timer.h`
Implemented timers. Using bird_clock_t for absolute time from now... 1998-05-24 14:40:29 +00:00			`io.c`
			`unix.h`
Moved all system-dependent #include's containing endianity conversion functions to sysdep header endian.h. 1999-03-29 19:14:43 +00:00			`endian.h`
Logging is now configurable. You can define multiple log outputs (to both files and syslog) and assign lists of message categories to each of them. 1999-12-06 13:45:56 +00:00			`config.Y`
Split random number functions off io.c, so that they can be documented separately. 2000-06-05 11:46:40 +00:00			`random.c`
Use traditional Unix route/iface interface only when CONFIG_NETLINK is not defined. Also moved declarations of Unix iface logic to krt.h. 1999-03-01 19:05:58 +00:00
Rewrote the kernel syncer. The old layering was horrible. The new kernel syncer is cleanly split between generic UNIX module and OS dependent submodules: - krt.c (the generic part) - krt-iface (low-level functions for interface handling) - krt-scan (low-level functions for routing table scanning) - krt-set (low-level functions for setting of kernel routes) krt-set and krt-iface are common for all BSD-like Unices, krt-scan is heavily system dependent (most Unices require /dev/kmem parsing, Linux uses /proc), Netlink substitues all three modules. We expect each UNIX port supports kernel routing table scanning, kernel interface table scanning, kernel route manipulation and possibly also asynchronous event notifications (new route, interface state change; not implemented yet) and build the KRT protocol on the top of these primitive operations. 1999-03-03 19:49:56 +00:00			`krt.c`
Since almost every UNIX system requires different techniques for reading the kernel routing table as opposed to modifying it which is approximately the same on non-netlink systems, I've split the kernel routing table routines to read and write parts. To be implemented later ;-) 1998-10-18 12:50:43 +00:00			`krt.h`
Rewrote the kernel syncer. The old layering was horrible. The new kernel syncer is cleanly split between generic UNIX module and OS dependent submodules: - krt.c (the generic part) - krt-iface (low-level functions for interface handling) - krt-scan (low-level functions for routing table scanning) - krt-set (low-level functions for setting of kernel routes) krt-set and krt-iface are common for all BSD-like Unices, krt-scan is heavily system dependent (most Unices require /dev/kmem parsing, Linux uses /proc), Netlink substitues all three modules. We expect each UNIX port supports kernel routing table scanning, kernel interface table scanning, kernel route manipulation and possibly also asynchronous event notifications (new route, interface state change; not implemented yet) and build the KRT protocol on the top of these primitive operations. 1999-03-03 19:49:56 +00:00			`krt.Y`