Searched refs:offensive (Results 1 – 4 of 4) sorted by relevance
462 char *tpath, *offensive; in add_file() local482 offensive = NULL; in add_file()485 offensive = off_name(path); in add_file()489 path = tpath = offensive; in add_file()490 offensive = NULL; in add_file()511 path = tpath = offensive; in add_file()512 offensive = NULL; in add_file()563 do_free(offensive); in add_file()573 all_forts(fp, offensive); in add_file()682 obscene->path = offensive; in all_forts()[all …]
25 Fortunes are split into potentially offensive and not potentially26 offensive parts. The offensive version of a file has the same name as the27 non-offensive version with "-o" concatenated, i.e. "fortunes" is the standard28 fortune database, and "fortunes-o" is the standard offensive database. The30 "-o" is potentially offensive, and should therefore only be displayed if33 Potentially offensive fortune files should NEVER be maintained in35 To create a new, potentially offensive database, use caesar to rotate it,41 MUST be in the potentially offensive database. Fortunes containing any43 potentially offensive database. Political and religious opinions are often44 sequestered in the potentially offensive section as well. Anything which
4 The potentially offensive fortunes are installed by default on FreeBSD
130117 offensive