Installworld errors with mtree
Hi, I was just helping a friend through an install world and, as seems to be the way with his computer, we ran into problems. We were updating an early 5 series (possibly 5.0 release) to 5.2_1. We went through all the steps as outlined in UPDATING and everything seemed to be working fine right up to the install world. The first time through we ran into some problems with gencat which we fixed by copying the gencat binary from the obj directory. Now we have run into a core dump with mtree. I have googled and come up with a reference to PR i386/30276 but this seems to be largely related to building across systems or at least changing the CPUTYPE during the build process. These errors are also quite old (April/May 2002) so it leads me to believe that there is something else up. Does anybody have ideas related to this? We would certainly appreciate any help you might offer. Limited output: mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / pid 41399 (mtree), uid 0: exited on signal 12 (core dumped) Thanks, Simon This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and If you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier electronique est une communication privee a l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'etes pas le destinataire prevu, vous etes avise, par les presentes que toute reproduction, transfert ou autre forme de diffusion de cette communication par quelque moyen que ce soit est interdite. Si vous n'etes pas specifiquement autorise a recevoir ce courriel ou si vous croyez l'avoir recu par erreur, veuillez en aviser l'expediteur original immediatement. Nous respectons les demandes similaires qui touchent la confidentialite des communications par courrier electronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Gathering required packages
Hi, I'm taking a class right now on system administration. Being a lover of FreeBSD my server box in the lab runs FreeBSD 5.1 release; alone amongst a sea of linux and Solaris. I need to setup apache, postresql and mod_php4 on the box. This is simple enough usually, however the lab does not yet have any sort of internet access. So I was thinking that I would take in a CD of packages built from my system at home using 'make package'. The problem is that the dependency tree for apache+postgresql+mod_php is huge. Is there any quick way to gather up and package all of the dependencies? Are there any gotchas I should be aware of in taking packages built from my home machine to another machine? They are both 5.1 release on i386. My thanks for your help, Simon This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD in Windows.....
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2003 3:41 PM To: Adam McLaurin Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD in Windows. On Fri, Sep 26, 2003 at 05:32:40PM -0400, Adam McLaurin wrote: On Fri, 2003-09-26 at 17:17, Kris Kennaway wrote: That won't help the OP. He's asking how to access a FreeBSD UFS _on the same computer_ while running Windows. Unless you can purchase a Windows UFS driver somewhere out there, this is not possible. The recommended way to share files from FreeBSD to Windows on a dual-boot OS is to use a FAT partition which can be mounted on both OSes. What about installing vmware (on XP), then install FreeBSD in vmware, and mounting it that way? Maybe a lot of trouble, but at least he'd be able to get at the data. Yeah, that might work. Kris If my understanding of vmware is correct that shouldn't work, couldn't work. Vmware is just an x86 emulator which sits on top of windows, the OS working in VMware should be unaware that it is running in an emulator and shouldn't have direct access to any of the host computer's resources. If the host system is unable to mount a file system then the operating system in vmware should also be unable to mount it. First because it is unaware that it exists and second because vmware uses the host system's resources and anything which is inaccessible to the host system would also be inaccessible to the emulated system. This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Off-Topic: Did I receive a virus or worm?
Jerry McAllister wrote: Below the message, however, were two blocks of gibberish. Both blocks begin with a begin line and end with an end line. There is no indication that Kmail included an attachment in-line within the email. Is it possible that the code was needed to access the web page? If so, I don't understand how clicking on the web address would send or use the blocks of code. I don't think so, I don't see any method by which these blocks of code could or would be used to access a webpage. Should I worry about these blocks of code? Yes, you should. Do not trust any unsolicited code and be cautious of that which you did request. It sounds to me like this code might be a pgp key or signature. Even if it is malicious code then chances are pretty good that it isn't going to run on FreeBSD. I don't think there are too many e-mail distributed viruses for Unix like systems, I can't think of a single one. If you're really curious then install vm ware and run the code inside there, it should provide a very secure sandbox. Worry Factor 2 - nothing much to worry about This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: frustrating *dumb* problem getting php to work under apache
humm, that does sound frustrating and you seem to be doing everything right. Did you install php or mod_php? Are you restarting apache after you change your httpd.conf? Are your php pages .php or .php3 or .php4? -Original Message- From: tb [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 1:54 PM To: [EMAIL PROTECTED] Subject: frustrating *dumb* problem getting php to work under apache hi, all -- i know this is a FAQ; in fact, it's *such* a FAQ that i've found dozens and dozens and dozens of FAs -- none of which have worked for me. and i *really* have tried before asking here. :/ and if i got djbdns, qmail and procmail working with maildir, i can't be too hopeless. or lazy. :) the goal: apache + php (under 4.8). the facts: apache, mysql, and php installed nicely. the problem: php doesn't render -- browsers either krash (konqueror), show php code, or ask me if i want DL the unknown document. php renders fine when i look at other sites, and i get the same (i.e., raw code) results looking at my host from an OSX box, so it's a server-config problem. as things stand, my httpd.conf is plain- vanilla *except for these two lines... AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps ...at ~line 634 (maybe relevant because of the order in which various items load?). however, httpd.conf is plain-vanilla now because i have a lng set of backed-up variations on it, which have included ex- periments like subsets of... LoadModule php_module modules/mod_php.so LoadModule php3_modulemodules/libphp3.so /* for PHP 3 */ LoadModule php4_modulemodules/libphp4.so /* for PHP 4 */ LoadModule perl_modulemodules/libperl.so ...both inside and outside of IfDefine SSL [...] /IfDefine. and i've tried lots of other stuff besides. what i have now is an install that works, except for this one pathetic problem, basd on the instrux here -- which worked perfectly: http://www.freebsdforums.org/forums/showthread.php?threadid=12419 i've hunted through /var/log for klews about why it's not working. i'd be happy to provide all kind of infodumps, but it seemed like a clear statement of the problem might be a good way to begin. for now, the basics: uname -a FreeBSD ... 4.8-RELEASE-p1 FreeBSD 4.8-RELEASE-p1 #0: Sat Aug 9 22:22:39 EDT 2003 ...:/usr/src/sys/compile/EKB030809 i386 -- custom-compiled for pcm support on an i810 :) httpd -v Server version: Apache/1.3.27 (Unix) Server built: Aug 12 2003 13:28:32 httpd -l Compiled-in modules: http_core.c mod_so.c suexec: disabled; invalid wrapper /usr/local/sbin/suexec php -v PHP 4.3.1 (cli) (built: Aug 12 2003 13:36:26) Copyright (c) 1997-2002 The PHP Group Zend Engine v1.3.0, Copyright (c) 1998-2002 Zend Technologies openssl version OpenSSL 0.9.7a Feb 19 2003 any advice would be much appreciated! thanks, t ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Well, we're getting closer. Still having issues installing BitTorrent.
well it isn't really a bittorrent problem but rather a python one. I am getting it too on 5.1 with a fresh ports tree. As a temp fix you can define WITHOUT_GUI and do a make install on bittorrent. That seems to work but you won't get the stylish GUI. -OR- Try editing the Makefile in /usr/ports/graphics/py-imaging/work/Imaging-1.1.3 so that the 'DEFS= @DEFS@' line reads 'DEFS=' instead. I am not familiar enough with python (or anything, really) to know if that is going to cause bad things later but the compile seems to work. I would check with the port maintainer if my change will adversely effect the port. -Original Message- From: Dragoncrest [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 7:28 AM To: [EMAIL PROTECTED] Subject: Re: Well, we're getting closer. Still having issues installing BitTorrent. Nobody has an answer for this? At 12:20 PM 8/4/03 -0400, Dragoncrest wrote: Ok, first off I want to send out thanks to whoever submitted the bug report on the python numeric port issue. Problem is, we've got a new one. When building for BitTorrent it looks for the port py23-imaging-1.1.3 and tries to install it, but instead gets this: === Building for py23-imaging-1.1.3 `Makefile' is up to date. cc -fPIC -O -pipe -I/usr/local/include/python2.3 -I/usr/local/include/python2.3 @DEFS@ -IlibImaging -I/usr/local/include -c ././_imaging.c -o ./_imaging.o cc: cannot specify -o with -c or -S and multiple compilations *** Error code 1 Anyone know if this is another bug issue needing to be reported or is this something that I can fix on my end? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Resolving domain names in KDE apps
I would bet that this is another issue related to IPv6. Take a look at a thread on this list titled Mozilla and long time in resolving Hostnames, especially a message from Dr Matthew J Seaman. Good luck. -Original Message- From: Aaron Siegel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:11 AM To: [EMAIL PROTECTED] Subject: Re: Resolving domain names in KDE apps Hello Robert I have been using FreeBSD 5.1 RELEASE and Konqueror without any noticeable problems with speed or name resolution. The problem I have are related to browser issue: not haveing support for shockwave, scripting problems, and poorly develop sites that do not work well with the KHTML and Mozilla engines. The site you referenced does load slowly for me, but I think is do to the site and it is defiantly not a result of the operating system or KDE. The webpage does load some files form ad.ca.doubleclick.net see code below. TD width=468 height=60 valign=middle SCRIPT language=JavaScript1.1 SRC=http://ad.ca.doubleclick.net/N3081/adj/ccn.com/van/indexbanner;loc=theT op;sz=468x60;stile=1;dcopt=ist;kw=van;ord=9?/SCRIPTNOSCRIPTa TARGET=_top HREF=http://ad.ca.doubleclick.net/N3081/jump/ccn.com/van/indexbanner;loc=th eTop;sz=468x60;stile=1;kw=van;ord=9?IMG NAME=i_banner ALIGN=TOP BORDER=0 VSPACE=0 HSPACE=0 WIDTH=468 HEIGHT=60 SRC=http://ad.ca.doubleclick.net/N3081/ad/ccn.com/van/indexbanner;loc=theTo p;sz=468x60;stile=1;kw=van;ord=9?/a/NOSCRIPT/TD/TR On Thursday 31 July 2003 07:41 am, Robert Froese wrote: Hello, I'm a new FreeBSD user with a performance issue. I've installed 5.1R and KDE. I've also installed Phoenix from the ports collection. When I'm using Konqueror or Phoenix to browse certain web sites they take forever to load. It appears the problem is associated with resolving domain names. While I wait (minutes!) for a problematic page to load, Phoenix will report in the notices bar at the bottom Resolving host There's no CPU or network bottleneck and the problem is reproducable in either browser with the same web sites. It seems also to relate to situations where one web page calls another for part of the content (e.g., www.vancouversun.com tries to load from ad.ca.doubleclick.net). If I open up a shell window and ask FreeBSD to resolve the same domain names with host they resolve instantly. So the problem has something to do with the way the package for KDE talks with BSD. Any advice would be greatly appreciated! ...Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: php4
Well this should really be on -questions, I'll forward it there. This is a huge config file but iff I am reading it correctly then what the problem probably is; is SSL. Mod_php4 only gets loaded if you define SSL. It may be that ssl is not defined. So try it by moving the LoadModule php4_modulelibexec/apache/libphp4.so line to outside of the IfDefine SSL tags. Then restart apache and see if that does it. If not take a look and see if mod_mime is getting loaded properly. You may also want to check the extension of you test php file. At the moment it will only pick up files with a .php extension and not ones with a .php3 or .php4 extension. If none of these work, post back to -questions and somebody there who is far smarter than me shall help you. Original Message- From: Bangle Bot [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: php4 H, I installed php4 from the ports collecthing worked great, but when I looked at a php page in my browser only the source came out and didn't start the php program. Is it a problem if i didn't compile php3? Of course I restarted apache after the install... Please help. Here is my httpd.conf file: ## ## httpd.conf -- Apache HTTP server configuration file ## # # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See URL:http://www.apache.org/docs/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # After this file is processed, the server will look for and process # /usr/local/conf/srm.conf and then /usr/local/conf/access.conf # unless you have overridden these with ResourceConfig and/or # AccessConfig directives here. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with / (or drive:/ for Win32), the # server will use that explicit path. If the filenames do *not* begin # with /, the value of ServerRoot is prepended -- so logs/foo.log # with ServerRoot set to /usr/local/apache will be interpreted by the # server as /usr/local/apache/logs/foo.log. # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerType is either inetd, or standalone. Inetd mode is only supported on # Unix platforms. # ServerType standalone # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at URL:http://www.apache.org/docs/mod/core.html#lockfile); # you will save yourself a lot of trouble. # ServerRoot /usr/local # # The LockFile directive sets the path to the lockfile used when Apache # is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or # USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at # its default value. The main reason for changing it is if the logs # directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL # DISK. The PID of the main server process is automatically appended to # the filename. # #LockFile /var/run/httpd.lock # # PidFile: The file in which the server should record its process # identification number when it starts. # PidFile /var/run/httpd.pid # # ScoreBoardFile: File used to store internal server process information. # Not all architectures require this. But if yours does (you'll know because # this file will be created when you run Apache) then you *must* ensure that # no two invocations of Apache share the same scoreboard file. # ScoreBoardFile /var/run/httpd.scoreboard # # In the standard configuration, the server will process httpd.conf (this # file, specified by the -f command line option), srm.conf, and access.conf # in that order. The latter two files are now distributed empty, as it is # recommended that all directives be kept in a single file for
crontab root not found
Hi, I seem to be having some trouble with cron. I edited my crontab file and added a line then ran #crontab /etc/crontab Now my email box is full of cron root not found. Nonsense, I said, I am root and I'm right here, I then tried waving my hands so the computer could find me more easily. Then it occurred to me that perhaps the contab file was being interpreted as a normal user crontab file and it was trying to run the command root as that is what appeared in the 6th column. So I went and read the crontab man page and found that I should run crontab with the -u option when using su. I tried that too and I'm still getting the e-mails every 5 minutes. So what command should I run to load the master crontab? I tried #crontab -u root crontab but that too seems to interpret the crontab as a user crontab too. I have removed any changes I made to the crontab so I won't bother including it in the e-mail since it is the default file. Thank you kindly, Simon This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: crontab root not found
Sure thing, here is the file. But the line I added (right at the bottom) is commented out. BTW I am running 5.1 release. I also get operator not found when it tries to run the second entry. # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a # Run portupgrade #* 2 * * * root /usr/local/scripts/cron.portupgrade -Original Message- From: Jonathan Arnold [mailto:[EMAIL PROTECTED] Sent: Friday, June 27, 2003 9:18 AM To: Timms, Simon Cc: [EMAIL PROTECTED] Subject: Re: crontab root not found I seem to be having some trouble with cron. I edited my crontab file and added a line then ran #crontab /etc/crontab Now my email box is full of cron root not found. Nonsense, I said, I am I'd say you should post the new line you added to cron. Sounds like you have the formatting incorrectlying, and it is trying to run a bogus command called either 'cron' or 'root'. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD blog: http://freebsd.amazingdev.com/blog This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Apache + PHP Issue
did you put AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps in the httpd.conf file as it tells you to at the end of the php port install? Did you restart apache? -Original Message- From: bryan cassidy [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 9:40 AM To: [EMAIL PROTECTED] Subject: Apache + PHP Issue Hello, I just installed the mod_php4 + apache ports and when I create a .php file in a directory say called test it doesn't ever want to load the script it wants me to save it on the computer. http://bsdsys.dyndns.org/test/ when you click on test.php it wants to Save it not load it. Whats goin on here? __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mod_jk, mod_jk2
Hi, I have been trying to install the mod_jk or mod_jk2 tomcat connectors from /usr/ports/www/mod_jk(2). Unfortunately I get an error during the build of either one. I have an up to date ports collection. Has anybody else got this to work? Iff so then how? /bin/sh /usr/local/share/apache2/build/libtool --silent --mode=link cc -I/usr/local/include/apache2 -O -pipe -mcpu=pentiumpro -DUSE_APACHE_MD5 -I ../common -I /include -I /include/unix -D_REENTRANT -D_THREAD_SAFE -O -pipe -mcpu=pentiumpro -DNO_IDEA -O -pipe -mcpu=pentiumpro -D_REENTRANT -D_THREAD_SAFE -o mod_jk.la -module -rpath /usr/local/libexec/apache2 -avoid-version mod_jk.lo ../common/jk_ajp12_worker.lo ../common/jk_connect.lo ../common/jk_msg_buff.lo ../common/jk_util.lo ../common/jk_ajp13.lo ../common/jk_pool.lo ../common/jk_worker.lo ../common/jk_ajp13_worker.lo ../common/jk_lb_worker.lo ../common/jk_sockbuf.lo ../common/jk_map.lo ../common/jk_uri_worker_map.lo ../common/jk_ajp14.lo ../common/jk_ajp14_worker.lo ../common/jk_md5.lo ../common/jk_ajp_common.lo ../common/jk_context.lo libtool: link: `../common/jk_ajp12_worker.lo' is not a valid libtool object gmake[1]: *** [mod_jk.la] Error 1 gmake[1]: Leaving directory `/usr/ports/www/mod_jk2/work/jakarta-tomcat-connectors-jk-1.2.2-src/jk/nativ e/apache-2.0' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/www/mod_jk2. su-2.05b# uname -a FreeBSD simserve.simon.ma.cx 5.1-RELEASE FreeBSD 5.1-RELEASE #2: Sun Jun 22 22:43:45 MDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SIMSERVE-2003-06-22 i386 Thank you! This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie. Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, tout transfert ou toute autre forme de diffusion de cette communication par quelque moyen que ce soit est interdit. Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement. Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Xfree86 Config Problems
sounds like you are doing pretty good. If you are getting the gray screen and black X then your video card is supported and you have started X. What you are missing is a window manager. I don't know what window manager you want but give fluxbox a try, it is in the ports collection. If you want something a little heavier try KDE or GNOME. I am aware that KDE/Gnome aren't window managers, thank you. Once you have installed a window manager they edit your .xinitrc and add a call to your window manager (exec startkde for kde, exec fluxbox for fluxbox). Check the archive of this list somebody has done a good walk though for this before. If you do install kde from ports then allow a good few hours for it to finish. try: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html the friendly handbook for some good examples. good luck! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 10:22 AM To: [EMAIL PROTECTED] Subject: Re: Xfree86 Config Problems Thanks for prompt reply, guys. I enjoy this community, but hate the install. While I didn't mention it in my email, I did try this as well: # XFree86 -configure And it didn't work. Gave me X cursor in gray screen and could not get out. As for checking for multiple config files, how would I know? Where would I find them? What would I do with them all, just rm them? What if I found more than one? How do I know which one is being used? Why so many config utils? Why are there so many possible locations? This is my first install of BSD, and while I've installed Linux a dozen times, I don't know where to find things in BSD. I'm overwhelmed and frustrated. Please walk me through the steps before I give up on BSD. I wonder if my S3 Savage 2000 video card is supported, even though it was on the list. I saw many posts about S3 problems, none with obvious solutions. I could use the FreeBSD 5.1 Release if that would help. I saw this link about S3 Savage at http://www.xfree86.org/support.html a private developer at http://www.probo.com/timr/savage40.html where he says: xvideo on the Savage2000 still seems to be broken. I don't know when I'll be able to get around to this. Thus far, the install process is overly complicated and not inviting to new users. I could provide specific feedback on this if anyone wants it. From Viktor Lazlo [EMAIL PROTECTED] on 23 Jun 2003: On Sun, 22 Jun 2003 [EMAIL PROTECTED] wrote: http://cgisleve.tripod.com/bsd/xfreebad.html is a web page of this info. XFree86 Configuration Problems by Steve LeBlanc © 2003.6.22 Installed FreeBSD for first time. Text login was fine. NIC worked. Did a telnet and ftp to computers on the Internet. All seemed to work except for configuring XFree86. No screen found when I did startx. Below are the details: The full commented files: XF86Config.txt and XFreelog.txt Settings XFree86 Ver:4.2.1 Release Date: 3 September 2002 OS: FreeBSD 5.0 RELEASE Video: S3 Savage2000 (generic) 64MB, 3D Monitor: Cornea MT1700 17 LCD H: 31.5-80, V: 56-75 After install I tried both: xf86cfg -textmode and xf86config to reconfigure. I read the docs deeply and redid this 15 times, using the various command line tools. Each of the last 10 times, I typed in my settings and selected my Graphics card from the list. I just can't get startx to work. Below are my XF86Config file and my XFree log file, with comments removed. Fatal server error: no screens found Check the handbook: 5.4.2 Configuring XFree86 4.X Configuration of XFree86 4.X is a multi-step process. The first step is to build an initial configuration file with the -configure option to XFree86. As the super user, simply run: # XFree86 -configure Cheers, Viktor ___ The FREE service that prevents junk email http://www.mailshell.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and if you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited. If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately. We honour similar requests relating to the privacy of email communications. Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que
