Customized Install CD
I'm looking at trying to build my own customized FreeBSD install CD. The purpose of this is to be able to install FreeBSD with customized kernel, certain packages installed and some added scripts of my own. Being that I have no idea how to do this I have two questions. 1. Is this feasible? 2. Is there some good literature regarding this on the internet that you recommend? Any information would be greatly appreciated! LIFE'S A GARDENDIG IT! smime.p7s Description: S/MIME cryptographic signature
FreeBSD Source Upgrade
Currently running FreeBSD 6.0-STABLE #0 on a development server and attempted to update source via cvsup to 6.1-STABLE. Went through the same procedures that I have always used in the past and the server stated to still be running 6.0-stable. The following are the procedures that I use. I deleted everything out of /usr/obj, then ran make update && make buildworld && make buildkernel KERNCONF=KERNELNAME && make installkernel KERNCONF=KERNELNAME from /usr/src, rebooted, ran make installworld from /usr/src, ran mergemaster, then rebooted. Make.conf has the appropriate supfile and in the supfile I'm using tag=RELENG_6. The whole process went fine. I thought something was strange when mergemaster didn't update anything except motd. Any ideas? Thanks, Cody Lifes a GardenDig It!! smime.p7s Description: S/MIME cryptographic signature
Port marked as IGNORE
I was updating the ports on one of my servers and received this error: [Updating the pkgdb in /var/db/pkg ... - 68 packages found (-1 +1) (...). done] ** Port marked as IGNORE: graphics/php4-ming: is marked as broken: doesn't work with new version of ming library What actions, if any do I need to take to fix this? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Portupgrad Problem
Using FreeBSD 5.4-Stable #0. Trying to update my ports using portsnap, pkg_version, and portupgrade. All goes well until I get to portupgrade -arR. All my ports update except for of them. Here is the message I get: # portupgrade -arR cd: can't cd to /usr/ports/archivers/pear-Archive_Tar cd: can't cd to /usr/ports/devel/pear-Console_Getopt cd: can't cd to /usr/ports/devel/pear-XML_RPC cd: can't cd to /usr/ports/devel/php4-pear ** Package 'php4-pear' has been removed from ports tree. ** Port directory not found: devel/php4-pear ** Package 'pear-Console_Getopt' has been removed from ports tree. ** Port directory not found: devel/pear-Console_Getopt ** Package 'pear-XML_RPC' has been removed from ports tree. ** Port directory not found: devel/pear-XML_RPC ** Package 'pear-Archive_Tar' has been removed from ports tree. ** Port directory not found: archivers/pear-Archive_Tar ** Listing the failed packages (*:skipped / !:failed) ! (php4-pear-4.4.1_1) (port directory error) ! (pear-Console_Getopt-1.2)(port directory error) ! (pear-XML_RPC-1.4.3) (port directory error) ! (pear-Archive_Tar-1.3.1) (port directory error) ---> Packages processed: 0 done, 73 ignored, 0 skipped and 4 failed I know this is telling me that there is no ports directory for these ports...and there isn't one. I just don't know what to do, to correct this. Any advice would greatly be appreciated. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 6.X Updating Source
I just installed a server with FreeBSD 6.0. Everything went perfect. Got it up and running and wanted to download the newest source prior to installing a lot of ports and software. Used cvsup with stable-supfile. Went throught the normal update procedure and when it was done it says that I am running FreeBSD 6.1-PRERELEASE #0. I'm using the RELENG_6 tag, and it was to my understanding that this only followed 6-stable. Is a prerelease considered stable, or am I doing something wrong? Cody Holland Network Engineer Redmoon Broadband, Inc. 972-599-3926 [EMAIL PROTECTED] ** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Autoconf Issues
Running FreeBSD 5.4-STABLE and trying to install Apache 2.0.x and getting: autoconf: not found buildconf: autoconf not found. You need autoconf version 2.13 or newer installed to build Apache from CVS. ./buildconf failed for apr *** Error code 1 I have autoconf-2.13.000227_5 installed and automake-1.4.6_2. I've removed and reinstalled autoconf several times and also tried autoconf-259. I've installed Apache many times and have never ran into an issue like this. Any ideas? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: BSD vs Linux Threads
Well in the past it was stated that on a MySQL server installed using Linux threads was faster than using the native BSD threads. I'm in the process of building a new MySQL 5 server with FreeBSD 5.4 and was wanting to know if using the Linux threads was still faster. Cody > > On Thu, Dec 01, 2005 at 02:14:05PM -0600, Cody Holland wrote: > > Ok, I know this has come up before but I cannot find any good > > documentation on BSD vs Linux threads using 5.4 or 6.0. This will > > basically be for a multi-processor mysql 5 server. What are your > > recommendations? > > What are your questions? :) > > Kris > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BSD vs Linux Threads
Ok, I know this has come up before but I cannot find any good documentation on BSD vs Linux threads using 5.4 or 6.0. This will basically be for a multi-processor mysql 5 server. What are your recommendations? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Apache::DBI Problems
I'm having some major issues with perl site I'm trying to get working. I'm running FreeBSD 5.4 stable using Apache 2.0.55 and perl 5.8.7. The error I'm getting is: Can't locate object method "connect_on_init" via package "Apache::DBI" (perhaps you forgot to load "Apache::DBI"?) I do have LoadModule perl_module libexec/apache2/mod_perl.so PerlModule Apache::DBI in my httpd.conf file. I'm pretty new to perl and have no idea what I've done wrong. Any help would greatly be appreciated. If you need more info from me, don't hesitate to ask. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Patch vs. Upgrade
On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote: > > If things are not too tight on your hard drive, consider the cvsup > > way. It's very easy - and very clearly described in the handbook. > > I've seen many people say this, but I suspect they haven't > tried looking for information on patching using cvsup in the > handbook. It's not easy to find. I think we're doing a > disservice to the community directing people there without > pointing them to a specific page (it is a 4MB document). > > The notes on using cvsup to keep your system up to date are > under the section header "Cutting Edge". I dunno about you, > but when it comes to security patches, I'd like to see them > as easy as possible, not something as elite as that. Maybe > that's just a poor choice of a title, though. > > The only specifically correct information -- using 'standard-supfile' > -- appears under the header "Using FreeBSD-CURRENT", a > section most newbies certainly ought to avoid unless they > want to run bleeding-edge may-not-compile-at-all code. > > In any case, a direct link to the information on how to keep > your system up to date is available here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/curr > ent-stable.html#AEN27683 > > You only need to read paragraph 2a -- the rest has to do with > -CURRENT and other crufty methods of getting source. Then you > can skip to: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sync > hing.html > > and read that and the next page. That should be enough to get > you going with the latest -RELEASE-pNN patch level. > Thanks for the response. I did a terrible job of asking the correct question to get the response I wanted. I do know to cvsup the source and build/make world. I currently have 4 FreeBSD servers in production serving various tasks. The question I should have been asking is: Is using the security patches provided by the FreeBSD maintainers as good as actually updating the whole server? What are the pros and cons of using the security patches vs. full source upgrade via cvsup? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Patch vs. Upgrade
I'm still pretty new to the BSD world and wanted to throw out a question to see what kind of responses I get. What is everyones take on what to do when security vulnerabities are discovered. Do you upgrade your source (not always the easiest thing to do) or patch. What are the pros and cons of patching? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Server Crash
Ok, I've successfully restored the systemI think. Basically I installed a fresh install of FreeBSD on the new system. Then, restored /etc, all of /var, all of /usr except /usr/src. Reconfigured the /etc/fstab and rebooted. Everything seems to be working finewhich has me kind of leery. It seemed to be too easy. Anyone ever restored like this, and if so had any issues I can look out for? Cody -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cody Holland Sent: Wednesday, September 28, 2005 8:21 AM To: freebsd-questions@freebsd.org Subject: Server Crash Ok, I'm having some problemsdue to the fact that I'm pretty new and have no idea on how to do this. We had a server crash, hardware related, and I want to take my dump backups and restore them on another system. The dump files are located on a remote ftp server. So basically what I'm trying to accomplish is installing FreeBSD on the new system, getting the dump files off of the backup server, and then restoring them on a live server. Is this possible, or should I be trying to do this a different way. I cannot restore everything exactly without some changes. The new server is SCSI, and the old server was on an IDE hard drive and I had re-compiled the kernel with all SCSI devices disabled (I don't know if that even matters). Anyway I'm kind of lost and am looking for some guidance. I've done plenty of reading and have attempted the restoration on my own, but keep hosing the new system. Any help would greatly be appreciated. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Server Crash
Ok, I'm having some problemsdue to the fact that I'm pretty new and have no idea on how to do this. We had a server crash, hardware related, and I want to take my dump backups and restore them on another system. The dump files are located on a remote ftp server. So basically what I'm trying to accomplish is installing FreeBSD on the new system, getting the dump files off of the backup server, and then restoring them on a live server. Is this possible, or should I be trying to do this a different way. I cannot restore everything exactly without some changes. The new server is SCSI, and the old server was on an IDE hard drive and I had re-compiled the kernel with all SCSI devices disabled (I don't know if that even matters). Anyway I'm kind of lost and am looking for some guidance. I've done plenty of reading and have attempted the restoration on my own, but keep hosing the new system. Any help would greatly be appreciated. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Restore System
Thanks for all the help. I've added the -X option to tar and have a file containing all directories and files I don't wish to backup. Cody -Original Message- From: Gayn Winters [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 4:06 PM To: Cody Holland; freebsd-questions@freebsd.org Subject: RE: Restore System > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Cody Holland > Sent: Wednesday, September 21, 2005 1:48 PM > To: freebsd-questions@freebsd.org > Subject: Restore System > I did a full backup of a server with tar using the following command: > tar cpzf servername`date +%m%d%y`.tgz / > > I'm trying to restore it on another server with the following command: > tar -xzpf /path to backup file > > The problem I'm running into is that the original system is has an IDE > harddrive, and the new system is SCSI. I'm getting the following > errors: > dev/ad0: Can't restore device node: No such file or directory > dev/ad0s1: Can't restore device node: No such file or directory > dev/ad0s1a: Can't restore device node: No such file or directory > dev/ad0s1b: Can't restore device node: No such file or directory > dev/ad0s1c: Can't restore device node: No such file or directory > dev/ad0s1d: Can't restore device node: No such file or directory > dev/ad0s1e: Can't restore device node: No such file or directory > > Is there an easy way around this? Any help would greatly be > appreciated. You should probably step back and tell us: 1. What you are trying to accomplish. 2. What hardware you have (both machines). 3. What software you are running (uname -a). You should probably at least reread the Handbook on devices, device naming, backups (in particular dump and restore). Best regards, -gayn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Restore System
I'm pretty new to the BSD and NIX world, and have never had to perform a system recovery or restore. I did a full backup of a server with tar using the following command: tar cpzf servername`date +%m%d%y`.tgz / I'm trying to restore it on another server with the following command: tar -xzpf /path to backup file The problem I'm running into is that the original system is has an IDE harddrive, and the new system is SCSI. I'm getting the following errors: dev/ad0: Can't restore device node: No such file or directory dev/ad0s1: Can't restore device node: No such file or directory dev/ad0s1a: Can't restore device node: No such file or directory dev/ad0s1b: Can't restore device node: No such file or directory dev/ad0s1c: Can't restore device node: No such file or directory dev/ad0s1d: Can't restore device node: No such file or directory dev/ad0s1e: Can't restore device node: No such file or directory Is there an easy way around this? Any help would greatly be appreciated. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BSD Updates
I just signed up and started using http://bsdupdates.com on a development server to see how it worked. Haven't had any issues yet, but wanted to know if anyone else out there is using it and your opinions. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Port Scan
> 127.0.0.1:123 from 127.0.0.1:60805 Connection attempt to UDP > 127.0.0.1:123 from 127.0.0.1:60805 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:63600 flags:0x02 Connection attempt to UDP > 206.123.80.170:137 from 67.68.138.222:61631 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:58875 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:51079 flags:0x02 Connection attempt to UDP > 127.0.0.1:123 from 127.0.0.1:59719 Connection attempt to UDP > 127.0.0.1:123 from 127.0.0.1:59719 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:50912 flags:0x02 Connection attempt to UDP > 206.123.80.170:137 from 222.213.93.106:1034 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49637 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:64161 flags:0x02 Connection attempt to UDP > 127.0.0.1:123 from 127.0.0.1:62528 Connection attempt to UDP > 127.0.0.1:123 from 127.0.0.1:62528 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:61587 flags:0x02 Connection attempt to TCP > 206.123.80.170:1433 from 84.131.177.47:21938 flags:0x02 Connection > attempt to UDP 192.168.253.32:64807 from 192.168.253.2:161 Connection > attempt to UDP 206.123.80.170:1027 from 220.175.8.154:33972 Connection > attempt to TCP 127.0.0.1:80 from 127.0.0.1:63194 flags:0x02 Connection > attempt to TCP 127.0.0.1:80 from 127.0.0.1:53348 flags:0x02 Connection > attempt to UDP 127.0.0.1:123 from 127.0.0.1:50654 Connection attempt > to UDP 127.0.0.1:123 from 127.0.0.1:50654 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to TCP > 127.0.0.1:80 from 127.0.0.1:49386 flags:0x02 Connection attempt to UDP > 206.123.80.170:137 from 82.104.59.45:1027 Cody Holland Network Engineer Redmoon Broadband, Inc. 972-599-3900x26 [EMAIL PROTECTED] ** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multi-Volume Backup
I'm trying to do a multi-volume backup to hard drive via gnu tar. It works with the following command: gtar -c -L 681574400 -f /usr/local/backup/dev1.tgz -f /usr/local/backup/dev2.tgz -f /usr/local/backup/dev3.tgz / But I really, really need this compressed. If I put a -z in the command it errors out stating: gtar: Cannot use multi-volume compressed archives gtar: Error is not recoverable: exiting now Is there any way to do a compressed multi-volume backup, with each volume being 650mb to hard drive? Either with gtar or any other backup method. Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Backup Question
Ok, I'm trying to do a simple tar+gzip backup for my file system. I can do this no problem. The backup is a little less than 2Gb. What I would like to do is chop this up into 650Mb pieces that I can ftp over to a server with a cd-r and burn them. Does anyone know a good utility that can do this, or another method that will accomplish what I'm trying to do? Thanks, Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Use older port
I'm running FreeBSD 5.4 with my ports pretty much up-to-date. I have a graphing software that required rrdtool 1.0.x and I'm running 1.2.x. How do I install an older version of this via ports or packages? Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Adding PHP Plugin
How would I go about adding a pluggin to php4-extension. I've already installed in, but need to add support for pcntl. Do I need to remove extensions all together and reinstall them from scratch, or is there an easier way?? Cody Holland Field Engineer Redmoon Broadband, Inc. 972-599-3900x26 [EMAIL PROTECTED] ** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cvsup problems
I'm having cvsup update issues right now. When I try to update I get: Cannot connect to cvsupxx.us.freebsd.org: Connection refused Will retry at xx:xx:xx No matter which server I try. Also when I try to run fastest_cvsup -c us I get timeouts on everyserver. Any ideas? Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel Log Message
I keep getting the following kernel log messages in my daily security run output. xxx.xxx.xxx.xxx kernel log messages: > Limiting closed port RST response from 283 to 200 packets/sec Limiting > closed port RST response from 283 to 200 packets/sec Limiting closed > port RST response from 235 to 200 packets/sec Limiting closed port RST > response from 256 to 200 packets/sec Limiting closed port RST response > from 275 to 200 packets/sec Limiting closed port RST response from 256 > to 200 packets/sec Limiting closed port RST response from 284 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 277 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 286 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 221 to 200 > packets/sec Limiting closed port RST response from 263 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 264 to 200 > packets/sec Limiting closed port RST response from 234 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 256 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 276 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 257 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 236 to 200 > packets/sec Limiting closed port RST response from 234 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 260 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 234 to 200 > packets/sec Limiting closed port RST response from 257 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 235 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 238 to 200 > packets/sec Limiting closed port RST response from 283 to 200 > packets/sec Limiting closed port RST response from 256 to 200 > packets/sec Limiting closed port RST response from 263 to 200 > packets/sec Limiting closed port RST response from 286 to 200 > packets/sec Limiting closed port RST response from 256 to 200 > packets/sec Limiting closed port RST response from 284 to 200 > packets/sec Limiting closed port RST response from 265 to 200 > packets/sec Limiting closed port RST response from 256 to 200 > packets/sec Limiting closed port RST response from 275 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 234 to 200 > packets/sec Limiting closed port RST response from 260 to 200 > packets/sec Limiting closed port RST response from 285 to 200 > packets/sec Limiting closed port RST response from 254 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 276 to 200 > packets/sec Limiting closed port RST response from 253 to 200 > packets/sec Limiting closed port RST response from 262 to 200 > packets/sec Limiting closed port RST response from 286 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiting closed port RST response from 275 to 200 > packets/sec Limiting closed port RST response from 233 to 200 > packets/sec Limiti
Updating Ports
After running cvsup, I then ran portdb -Uu and received the following error. Updating the ports index ... Generating INDEX.tmp - please wait..gnustep-slideshow-0.3: "/usr/ports/graphics/slideshowkit" non-existent -- dependency list incomplete ===> graphics/gnustep-slideshow failed *** Error code 1 1 error *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error How do I fix this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cvsup Source
I've been using cvsup to upgrade the ports on my Freebsd box, and it works great. My question is how often should you cvsup the src and do a buildworld? Thanks Cody ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Automake Problem
I'm a newbie to FreeBSD, so please be patient with me. I'm running 5.3 adn am trying to install php4-extensions through the ports collection and getting: ===> Installing for php4-extensions-1.0 ===> php4-extensions-1.0 depends on file: /usr/local/include/php/main/php.h - found ===> php4-extensions-1.0 depends on file: /usr/local/lib/php/20020429/ctype.so - not found ===>Verifying install for /usr/local/lib/php/20020429/ctype.so in /usr/ports/textproc/php4-ctype ===> Vulnerability check disabled, database not found ===> Extracting for php4-ctype-4.3.10_1 => Checksum OK for php-4.3.10.tar.bz2. ===> Patching for php4-ctype-4.3.10_1 ===> php4-ctype-4.3.10_1 depends on executable: phpize - found ===> php4-ctype-4.3.10_1 depends on file: /usr/local/bin/automake15 - not found ===>Verifying install for /usr/local/bin/automake15 in /usr/ports/devel/automake15 ===> NOTICE: This port is deprecated; you may wish to reconsider installing it: Please use devel/automake19 instead. ===> Vulnerability check disabled, database not found ===> Extracting for automake-1.5_2,1 => Checksum mismatch for automake-1.5.tar.gz. ===> Refetch for 1 more times files: automake-1.5.tar.gz ===> NOTICE: This port is deprecated; you may wish to reconsider installing it: Please use devel/automake19 instead. ===> Vulnerability check disabled, database not found => automake-1.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://ftp.gnu.org/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.gnu.org/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://ftp.lug.udel.edu/pub/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://gnu.mirror.mcgill.ca/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.nstu.ru/pub/mirrors/ftp.gnu.org/gnu/automake/. fetch: ftp://ftp.nstu.ru/pub/mirrors/ftp.gnu.org/gnu/automake/automake-1.5.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch from http://www.gtlib.cc.gatech.edu/pub/gnu/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://mirrors.usc.edu/pub/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://gatekeeper.dec.com/pub/GNU/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.de.uu.net/pub/gnu/automake/. fetch: ftp://ftp.de.uu.net/pub/gnu/automake/automake-1.5.tar.gz: Operation timed out => Attempting to fetch from http://ftp.funet.fi/pub/gnu/prep/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.leo.org/pub/comp/os/unix/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.wustl.edu/mirrors/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.kddlabs.co.jp/GNU/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.dti.ad.jp/pub/GNU/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://www.t.ring.gr.jp/pub/GNU/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://www.t.ring.gr.jp/archives/GNU/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.mirrorservice.org/sites/ftp.gnu.org/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.sunsite.org.uk/package/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.informatik.hu-berlin.de/pub/gnu/automake/. fetch: transfer timed out => Attempting to fetch from ftp://ftp.informatik.rwth-aachen.de/pub/mirror/ftp.gnu.org/pub/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from http://ftp.rediris.es/sites/ftp.gnu.org/pub/automake/. fetch: http://ftp.rediris.es/sites/ftp.gnu.org/pub/automake/automake-1.5.tar.gz: Not Found => Attempting to fetch from ftp://ftp.lip6.fr/pub/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.chg.ru/pub/gnu/automake/. fetch: automake-1.5.tar.gz: local modification time does not match remote => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: automake-1.5.t
