Date: Mon, 3 Mar 2008 19:27:40 +0100 From: "Harald Servat" <redcrash@gmail.com> To: freebsd-doc@freebsd.org Subject: importing mans from others OSes Message-ID: <d825e0270803031027q1286d04w3c11e757ca9d22d4@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello, I've recently used the call backtrace[1] from the libexec (found in /usr/local/lib) library and I've found it very useful. As it does not have (nor their relatives) a manual entry, I wondered if I could submit one for it. I'm not very skilled on writing manual documentation, and I've never submitted anything to FreeBSD but a port, but I'd like to try. As I have access to a Linux machine that has this manual entry[2], I wondered if I could use it as a base (or maybe copying it). However, as I don't want to start a BSD-License vs GPL-license war, I just want to know if it's permitted importing (using as a base, copying, ... or other possibilities that do not come into my mind right now) manual files from other OSes to FreeBSD. Regards and thank you. PS Googling around, I've also seen that MacOSX has this manual entry[3], but it's not as good as [2]. Being MacOSX BSD-based, is the situation better to import it? [1] http://www.delorie.com/gnu/docs/glibc/libc_665.html [2] http://linuxcertif.com/man/3/backtrace/ [3] http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man3/backtrace_symbols.3.html -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d825e0270803031027q1286d04w3c11e757ca9d22d4>