gitolite/c3d2-wiki
gitolite/c3d2-wiki
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

/* Transcript KenMoore/KrisMoore zum aktuellen Stand */

Browse Source
This commit is contained in:
TonyBoston 2015-09-28 17:54:56 +00:00
parent 7244b54ad1
commit 96403d19cd
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Yocage.mw
View File

@ -80,9 +80,9 @@ tboston: okay, I'll keep that in mind
tboston: can you be more specific on that low-level tool? Like what would it need and what is the OS/Admin getting out of it?
kenmoore: Well, '''I was thinking about 2-components:
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'''