[openbeos] Re: libroot.so and libc
- From: "Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 27 Jan 2002 19:29:00 EST (-0500)
> I am compiling the list of functions in libroot.so. a modified
> libc appears to have been used to compile this library
> so I think we are on the right track with newos libc .
>
> One thing I do notice are implementations of
> ioctl, fcntl, and fork. Do these not work correctly
> for BeOS? My information was that they were
> completely missing. Perhaps they are holdovers from using
> opensource libc versions.
Yeah, they work quite well. All of them. fork()ing a multithreaded app
can generate some difficulties, and some fnctl() ops don't work
correctly, but ioctl() is absolutely integral to the function of the
BeOS.
> Anyway, is there a more comprehensive list
> of the functions contained in libroot somewhere.
Try the export table?
> I think I have them all but I also need descriptions
> of what they are for return variables, arguments, etc.
> The standard stuff isn't a problem. It's the stuff that
> is specific to the internals of BeOS that I need a
> proper list of. I want to make sure I get everything
> covered.
libroot.so falls into four categories, as far as I know:
1. Standard POSIX and ANSI C/C++ (this is in the libroot.so code)
2. The Kernel Kit, which is well documented
3. The Storage Kit global C functions, which are quite well documented
4. The undocumented horror
Note on the undocumented horror: this is run-time init code (vital
for loading apps) and direct kernel calls used by a variety of Be-
supplied applications, mostly servers, but also including things like /
bin/shutdown
-Nathan
--
Fortune Cookie Says:
Armadillo:
To provide weapons to a Spanish pickle
Other related posts:
