Re: Uninstall Apache???
Martin P. Hansen wrote: On Sun, 25 Dec 2005, Jose Borquez wrote: I would like to know how you can uninstall Apache is it was installed from source? I did a search on Google and read that you could just stop the service and then delete the apache source tree. Is this true? It probably depends on your definition of uninstall. Usually the service binaries are installed in /usr/local/bin or sometimes in paths like /usr/local/apache. Same goes for configuration files see also hier(7). So stopping the service and removing the source tree wont remove these. Some makefiles comes with an uninstall target, so you might try ``make uninstall''. Otherwise you can do a rebuild and reinstall from the sources again and look for recently changed files with something like ``find / -newerct 10 minutes ago''. This probably have some shortcomings, but if you are careful it might do the job. ...or you could read pkg_delete(1) and pkg_deinstall(1) and follow instructions. (make uninstall is not a valid target for any Makefile in the ports tree that I am aware of.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding lines to /etc/rc.conf during sysinstall wihout being REMOVED
Josh Endries wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does anyone know the correct way to add lines to rc.conf without sysinstall commenting them out and prepending REMOVED to them, during an automated install.cfg routine? Currently I have a pkg I made that adds stuff like ntp.conf and rc.conf, but all the lines in my custom rc.conf are removed after the script finishes. I looked through the code for sysinstall but didn't see any way to disable this behavior (my C isn't very good). What would be the correct way to do this? I'm now having my pkg install a rc.d script which cat's /etc/rc.conf... Thanks, Josh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDovfOV/+PyAj2L+IRAjzcAJ4lJm+8vIP3QLy/DmuxTB0b4APp1gCfbhI1 waoWrsCORg3CiQMVToAFEaI= =RlT3 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Put the settings you do not want changed in /etc./rc.conf.local Settings in /etc/rc.conf.local override those in /etc/rc.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Who's Charlie Root?
I've been using FreeBSD for quite a few years, and I've sometimes wondered but never asked before: In the FreeBSD standard distribution, why is the user root always named Charlie? There must be some bit of Unix lore or anecdote that explains it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
one answer
legalois wrote: I've been using FreeBSD for quite a few years, and I've sometimes wondered but never asked before: In the FreeBSD standard distribution, why is the user root always named Charlie? There must be some bit of Unix lore or anecdote that explains it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I found one answer, but not really an explanation. According to Wikipedia (http://en.wikipedia.org/wiki/Charlie_Root) The name of a famous American baseball player (1899-1970) ...gives rise to the name used for many root system accounts under the UNIX operating system. But that does not explain when, how or why? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: one answer
Gary W. Swearingen wrote: legalois [EMAIL PROTECTED] writes: But that does not explain when, how or why? It was earlier than 20'jun'93, the oldest master.passwd in CVS which says that it was imported from 386BSD 0.1. It's easier to guess an explanation for this orignal entry: daemon:*:1:31::0:0:The devil himself:/root: That lasted only 8 months in FreeBSD, and the exorcism was not mentioned in the CVS commit message. That helps and provides a lead. Based on that provenance, I guess Marshall Kirk McCusick would know. (He probably would know, in any case.) Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade or # ./perl-after-upgrade I also tried just # perl-after-upgrade No joy. Just for the heck of it, I tried * sh perl-after-upgrade and dang if it didn't run. It didn't look to me like an sh script, but what do I know? It wasn't supposed to change anything without the -f option, but goose ran afterward, so it obviously changed things. I looked for Curses.pm, and it moved to a directory listed in @INC. Anybody have any advice? Comments? How was I supposed to get perl-after-upgrade to run? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A longish message appears at the end of the perl upgrade build, that explains how to run perl-after-upgrade. If you overlooked that, the same instructions are at #perldoc perl-after-upgrade If the script is in a directory not in your root's path, find the full path to the script with #locate perl-after-upgrade (but make sure your locate db is up-to-date, first). - Jacques ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
