/* Transcript KenMoore/KrisMoore zum aktuellen Stand */
This commit is contained in:
parent
96403d19cd
commit
f2854cdfee
|
@ -82,7 +82,7 @@ tboston: can you be more specific on that low-level tool? Like what would it nee
|
|||
|
||||
kenmoore: Well, I was thinking about 2-components:
|
||||
|
||||
1) A single libary (something like libSysAdmin), with all the various low-level system interface routines (in C/C++/QtCore - any of them will work) This is the "unifier" for accessing all the various FreeBSD subsystems (networking, user '''management, etc..) because every subsystem seems to have their own files/formats/etc'''
|
||||
'''1) A single libary (something like libSysAdmin), with all the various low-level system interface routines (in C/C++/QtCore - any of them will work) This is the "unifier" for accessing all the various FreeBSD subsystems (networking, user management, etc..) because every subsystem seems to have their own files/formats/etc'''
|
||||
|
||||
'''2) The user interface (web-based, or local) which just needs to load that single library to read/change things on the system as necessary. This webclient tool that we are working on could easily become a #2, but #1 does not exist yet. #1 will probably need a couple different libs actually - a "user" level one for providing read-access for supported things, and a "root" level one for modifications so maybe a libsysadmin-[user/root] setup'''
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user