|−|In Linux, you can use /proc to see various bits of kernel and system info. In FreeBSD, the equivalent is [[sysctl]]. Linux also has sysctl, but its usefulness is nowhere near that of FreeBSD' s sysctl. FreeBSD versions prior to 5.0 had a working /proc implementation. However, several serious security issues were discovered and it was decided to move away from / proc. The replacement is [[sysctl]]. |+|
,to ., the .'had a . to /and . , and to for the .
|−|FreeBSD 5.x still has a mountable /proc system, and it is still used for certain debugging programs, including truss. FreeBSD 6.x has moved away from /proc completely, and you need to jump through several hoops in order to get it mounted. No tools included with FreeBSD actually use it for anything, though. FreeBSD 7.x will probably be the first release without any trace of /proc. |+|
|−|[[Category : Linux Equivalents]] |+|
Hi Rene9,You need to point it to the results file geretaned earlier (xccdf-results.xml), not the XCCDF file itself.I do plan to integrate them in the ebuild later when they're more fixed and had a few other looks on them as well. Submitting them upstream will take a little more since I then first want to have gentoo-specific probes and OVAL tests approved (the upstream patch would then contain both the XCCDF/OVAL as well as the probe definitions and such). For now, I abuse the system a bit and first have a script generate the necessary output only to parse the output file (rather than using direct probes for the information).