Re: questions@ vs. freebsd-questions@
On Wednesday 15 August 2007 08:15:46 pm Chad Perrin wrote: On Wed, Aug 15, 2007 at 07:14:43AM -0400, Gerard wrote: Is there a reason that you cannot just use the address specified in the email headers of messages distributed by this forum. This is a snippet from the headers from your message. List-Id: User questions freebsd-questions.freebsd.org List-Unsubscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:[EMAIL PROTECTED] List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions List-Post: mailto:freebsd-questions@freebsd.org List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:[EMAIL PROTECTED] That reminds me: Is there any particular reason there isn't a List-Reply for this list? You wouldn't happen to be referring to: List-Post: mailto:freebsd-questions@freebsd.org would you? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: reposted question
Well, if it were me, I'd simply do: # rm -r /home/ncvs Then I'd change prefix='home/ncvs to prefix=/usr, just so I could cvsup the ports tree if I ever wanted to. But after makeing that change, I'd run: # portsnap fetch extract And know that that next time I wanted to update the ports tree, I'd run: # portsnap fetch update Followed by (since I'd have portupgrade installed) running: # portversion -v | grep needs or some other method of dtermining which ports needed upgrading. But that's just me, and the way I would do it. There are other ways. Don Z. Wade Hampton wrote: Hello to all, Not long ago, I ran cvsup successfully. In the example cvs-supfile, the following opening lines exist: # base=/var/db # This specifies the root where CVSup will store information # about the collections you have transferred to your system. # A setting of /var/db will generate this information in # /var/db/sup. Even if you are CVSupping a large number of # collections, you will be hard pressed to generate more than # ~1MB of data in this directory. You can override the # base setting on the command line with cvsup's -b base # option. This directory must exist in order to run CVSup. # # prefix=/home/ncvs # This specifies where to place the requested files. A # setting of /home/ncvs will place all of the files # requested in /home/ncvs (e.g., /home/ncvs/src/bin, # /home/ncvs/ports/archivers). The prefix directory # must exist in order to run CVSup. I attempted running cvsup with base and prefix locations other than the ones stated above; and, it did not work. However, when I edited the supfile as described above, the whole process ran to completion, successfully. Well, now I have an updated ports tree in /home/ncvs/ports instead of /usr/ports. So, my question this morning is what do I do with that? Do I treat /home/ncvs/ports as if it were /usr/ports? Do I copy the entire /home/ncvs/ports directory to /usr/ports for updated ports? Thank you in advance for directives. Z. Wade Hampton Twin Bridges, Montana ___ 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]
Re: freebsd desktop
On Sunday 26 November 2006 13:15, probsd org wrote: Regarding my earlier email Do not install FreeBSD as a desktop I don't care how long I have been using FreeBSD, or yadda yadda or yadda when I cvsup ports, update the databse, and install www/firefox and go to a website I expect firefox's javascript or whatever to work. Perhaps you enjoy perusing the internet looking for different switches and knobs to make it work, I don't. Maybe it would be good if you install java. It just might work then. If you don't, you can't expect it too work. Since you don't care, yadda, yadda, yadda, etc, I'll tell you anyway: if you don't install something that's needed to make something else work and you don't get the results you want, it won't work. No ifs, ands, or buts about it, it just won't work. And that's a fact, Jack. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache port compile error
On Saturday 25 November 2006 05:31, VeeJay wrote: Hi When compiling apache20 from ports and enabling/diabling knobs, I am writing the make command as follow; #make WITHOUT_MODULES=charset-lite include env setenvif status autoindex asis cgi negotiation imap actions userdir alias so WITH_MODULES=mpm=prefork access auth log_config mime dir #make install And after compiling with above command, I am getting this error when running apache # /usr/local/sbin/apachectl start Syntax error on line 41 of /usr/local/etc/apache2/httpd.conf: Invalid command 'Order', perhaps mis-spelled or defined by a module not included in the server configuration Even though I have added access, auth modules already in the make command... Please help!!! What's on line 40, 41, and 42 of your httpd.conf? I you just want a working apache20, skip what you're doing and just do a make install. Is there a reason that you would want to use apache20 rather than apache22? Just curious. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installworld Problem... Please help!!!
On Sunday 19 November 2006 06:47, VeeJay wrote: Hello, Please help!!! I have CVSup'ed my 6.1 Fresh Install. No problems with buildworld or kernel build, but I am getting failures during installworld. When I give this command in single user mode: # make installworld A Partial output of the Screen Dump cd /usr/src/etc; make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -eU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -eU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -eU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p / cd /; rm -f /sys; ln -s usr/src/sys sys rm: /sys: Read-only file system *** Error code 1 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # Information about my FSTAB: # cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/mfid0s1b none swapsw 00 /dev/mfid0s1a / ufsrw 1 1 /dev/mfid0s1g /home ufs rw 2 2 /dev/mfid0s1e /tmp ufs rw 2 2 /dev/mfid0s1f /usr ufs rw 2 2 /dev/mfid0s1d /var ufs rw 2 2 /dev/acd0/cdromcd9660 ro, noauto 0 0 What are you doing to go into single user mode? It looks like your not mounting in r/w. The handbook Section 21.4.5, gives a very good method (two actually) of what to do. I used to use the first, I have used the second for several years. Try that. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qmail Vpopmail From Ports
On Saturday 18 November 2006 20:54, Rachel Florentine wrote: 7883- Original Message From: Tom Ierna [EMAIL PROTECTED] I've installed qmail/vpopmail many ways - from source, using the instructions from qmailrocks and most recently using the instructions found here: http://www.tnpi.biz/internet/mail/toaster/install.shtml108 The toaster method seems to me to be the most comprehensive, and you can use (or not use) ports as you see fit. make test resulted in this: Failed Test Stat Wstat Total Fail Failed List of Failed --- t/Toaster.t1 256411 2.44% 22 t/toaster-watcher.t1 256231 4.35% 21 7 tests and 5 subtests skipped. Failed 2/24 test scripts, 91.67% okay. 2/364 subtests failed, 99.45% okay. *** Error code 255 Stop in /usr/local/Mail-Toaster-5.03. I'm toast. Rachel To run that script and install the toaster, you are going to find that you need to install one heck of a lot of perl programs. You did see the part at the very beginning about installing perl, correct? It's not just install perl, that's the easy part, it's all the other perl helper programs that need to be installed. A very much easier method to install is located here: http://freebsdrocks.net/ Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firefox 2.0 and flash 7
On Saturday 04 November 2006 09:24, Michael S wrote: Thanks for the tip. I will try it out. Just don't remove the old symlinks in /usr/X11r6/lib/browser_plugins, if you take them out, firefox won't open. Put in the new ones in /usr/local/lib/browser_plugins and you should be good to go. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firefox 2.0 and flash 7
On Friday 03 November 2006 16:06, Michael S wrote: Good day all. I am running 5.5 RELEASE and I have just upgraded Firefox from 1.5 to 2.0. Flash 7 was working very well under 1.5, however after upgrade it didn't. Moreover, flash doesn't appear anymore in the about:plugins. Has anyone had a similar experience and was able to resolve it? Thanks in advance, Michael ___ Check to see if firefox is now located in /usr/local/lib. If it is, you need to change your Flash symlinks from /usr/X11R6/lib/browser_links to /usr/local/lib/browser_links. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam trouble
On Tuesday 17 October 2006 05:47, Johan Johansen wrote: Actually, on my system I can do mount_udf /dev/acd0 and copy a 3GB file, I just tried. My problem is adding CAM support, which the handbook tells me I have to use to burn dvd. johan I'm unable to copy a file from a udf-mounted DVD regardless of whether atapicam is loaded or not, so I'm not sure if atapicam is just making a problem more apparent or what. Are you able to do so? Thanks, Josh On 10/16/06, Johan Johansen [EMAIL PROTECTED] wrote: I still have the same problem as below, even when running 6.2-BETA2 from a FreeSBIE - cd. I wonder if this could have to do with badly supportet motherboard, ASUS P5B, since I dont see any temp-readings with sysctl. cpuTemp and MBTemp are displayed under bios-config. ___ Look in /boot/kernel and see if atapikam.ko is there. It should be. If it is, you can use 'atapicam_load=YES' in /boot/loader.conf to load atapicam at boot. You can use 'kldload atapicam.ko' to just load it while system is running to see if it works before going any further. You can use kldstat to varify that it's loaded. Below is the output of kldstat from one of my systems: # kldstat Id Refs AddressSize Name 1 15 0xc040 5cae28 kernel 21 0xc09cb000 59f4 snd_atiixp.ko 32 0xc09d1000 22b88sound.ko 41 0xc09f4000 4ae8 atapicam.ko 51 0xc09f9000 5a78 if_fwip.ko 61 0xc09ff000 59f00acpi.ko 72 0xc4f2f000 16000linux.ko 81 0xc504a000 2000 rtc.ko Hope this will help you guys a bit. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: startkde: cannot start kdeinit. Check your installation
On Friday 13 October 2006 21:17, Karl Agee wrote: --- Donald J. O'Neill [EMAIL PROTECTED] wrote: On Friday 13 October 2006 20:11, Karl Agee wrote: 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #4: Mon Oct 2 08:40:06 PDT 2006 I cannot start kde. Installed kde 3.5.4 from pkg_add -r kde and everything installed fine. I put in my ~/.xinitrc file: startkde but I keep getting this error: /usr/local/bin/startkde: permission denied startkde: could not start kdeinit. check your installation I have changed the entry in .xinitrc to : exec startkde # and to /usr/local/bin/startkde with the same results. I also cannot start kde as root, I get the same thing. kdeinit is: -r--r--r-- 1 root wheel 39876 Oct 6 01:18 /usr/local/bin/kdeinit I have tried changing permissions on kdeinit but with the same result. I have also removed the kdebase package and reinstalled it, but with the same results. I've searched everywhere and have seen the same problems posted with different OS's and versions of kde but nothing solid as to solutions. anybody got any ideas? chmod 555 /usr/local/bin/kdeinit permisions should also be 555 for startkde You may have some other files permission problems. Don Don: I did that, same exact error. --Karl Karl, Try this. What do you get, now. #ls -l /usr/local/bin/kdeinit -r-xr-xr-x 1 root wheel 39716 Sep 29 03:22 /usr/local/bin/kdeinit #ls -l /usr/local/bin/startkde -r-xr-xr-x 1 root wheel 11828 Jul 23 09:23 /usr/local/bin/startkde #ls -l .xinitrc -rw-r--r-- 1 username username 48 Sep 23 07:10 .xinitrc #cat .xinitrc exec startkde Do you have xorg installed? xorg.conf is in place and configured? What happens if you: #xdm Does x start up? Have you looked at the handbook for information on x? What about the FAQ? You have a permissions problem somewhere. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: startkde: cannot start kdeinit. Check your installation
On Saturday 14 October 2006 11:44, Karl Agee wrote: Don: ls -la /usr/local/bin/kdeinit -r-xr-xr-x 1 root wheel 39876 Oct 6 01:18 /usr/local/bin/kdeinit ls -la /usr/local/bin/startkde -r-xr-xr-x 1 root wheel 11828 Oct 13 17:04 /usr/local/bin/startkde ls -la .xinitrc -rw-r--r-- 1 kdagee wheel 37 Oct 13 19:14 .xinitrc I use X all the time. I use windowmaker as my environment. Works fine. Using X.org. cat .xinitrc /usr/X11R6/bin/wmaker #exec startkde when I try starting kde I remove the # from the starkde line and put it in the wmaker line. Nothing abnormal in my .kde directory or owned by others. ls -la .kde total 8 drwx-- 3 kdagee wheel 512 Oct 13 09:30 . drwxr-xr-x 43 kdagee wheel 3584 Oct 14 09:25 .. lrwxr-xr-x 1 kdagee wheel24 Oct 12 21:01 cache-enterprise.myhome.westell.com - /var/tmp/kdecache-kdagee lrwxr-xr-x 1 kdagee wheel24 Oct 12 21:59 cache-myhome.westell.com - /var/tmp/kdecache-kdagee drwx-- 8 kdagee wheel 512 Oct 12 21:01 share lrwxr-xr-x 1 kdagee wheel19 Oct 13 09:30 socket-myhome.westell.com - /tmp/ksocket-kdagee lrwxr-xr-x 1 kdagee wheel15 Oct 13 09:30 tmp-myhome.westell.com - /tmp/kde-kdagee --Karl Hi Karl, Sorry I didn't get back to you sooner. I had to weld up a special grill to go over a fire pit, and it took a long time. Then of course, it had to be tested with steaks, and of course, lots of beer. It worked great, looks good, I might have to sell some of these. I think I've exhausted all of the things I can tell you to check. I haven't exhausted all of my knowledge, but I can't think of anything else to say. Somewhere, something doesn't have the correct permissions. Startkde is a script, if you go through it and check the permissions on what it's calling up, it may give you a better idea of where the problem is. When you find the problem, and I'm sure you will, it's probably going to be something so easy that you'll be kicking yourself for not seeing it. The brain is a funny thing, it will most often see what is expected, rather than what is. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: startkde: cannot start kdeinit. Check your installation
On Friday 13 October 2006 20:11, Karl Agee wrote: 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #4: Mon Oct 2 08:40:06 PDT 2006 I cannot start kde. Installed kde 3.5.4 from pkg_add -r kde and everything installed fine. I put in my ~/.xinitrc file: startkde but I keep getting this error: /usr/local/bin/startkde: permission denied startkde: could not start kdeinit. check your installation I have changed the entry in .xinitrc to : exec startkde # and to /usr/local/bin/startkde with the same results. I also cannot start kde as root, I get the same thing. kdeinit is: -r--r--r-- 1 root wheel 39876 Oct 6 01:18 /usr/local/bin/kdeinit I have tried changing permissions on kdeinit but with the same result. I have also removed the kdebase package and reinstalled it, but with the same results. I've searched everywhere and have seen the same problems posted with different OS's and versions of kde but nothing solid as to solutions. anybody got any ideas? chmod 555 /usr/local/bin/kdeinit permisions should also be 555 for startkde You may have some other files permission problems. Don __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ 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]
Re: Problems properly setting up /etc/exports
On Saturday 30 September 2006 13:39, stan wrote: I've got a FBSD 6 machine built from a 6.2 PRERELEASE set of sources that I need to use as an NFS server for some other similar machines. If I specify the machines by host name, or IP address in /etc/exports, I can mount the requisite directories from the test client. However, I really need to be able to allow 2 whole 1/2 class C's to mount these directories. My reading of the /etc/exports man page leads me to believe that I should be able to use a line like this: /usr/ports/distfiles maproot=root -network aaa.bbb.ccc.0 -mask 255.255.255.128 When I do this, and start mountd with the -d flag, I get: ountd: getting export list mountd: got line /usr/ports/distfiles maproot=root -network aaa.bbb.ccc.0 -mask 255.255.255.128mountd: making new ep fs=0x3e331e2f,0xe47d1981 But when I try to mount from a client n this network, it reports premission denied. I also tried putting a line like this in /etc/exports: /usr/ports/distfiles maproot=root -network mine and putting the following in /etc/networks: mineaaa.bbb But I still get the same error. What am I doing wrong? Try this line in /etc/exports: /usr /usr/ports /usr/ports/distfiles -maproot=root \ -network aaa.bbb.ccc -mask 255.255.255.128 Do you have something like this in /etc/rc.conf: rpcbind_enable=YES nfs_server_enable=YES mountd_flags=-r That should help you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The Ports collection / FreeBSD CDs
Perry Hutchison wrote: Before you can build from ports, you need to have ports tree in place, the standard way to do this is by running portsnap. with the caveat that, at least in my recent experience, an up-to-date ports tree does not always play nicely with a not-updated base install from CD. OP might be better off loading the ports collection from the same CD set as the rest of the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] That's very interesting. However, the ports tree on the CD isn't complete, as in: not all the ports are there. I stopped installing the ports tree from the install CD a long time ago for that reason. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The Ports collection / FreeBSD CDs
Perry Hutchison wrote: ... at least in my recent experience, an up-to-date ports tree does not always play nicely with a not-updated base install from CD. That's very interesting. However, the ports tree on the CD isn't complete, as in: not all the ports are there. Any idea why? (I am referring to the ports tree itself, i.e. the collection of skeleton directories. The set of distfiles provided on CDs 3 and 4 is necessarily incomplete, both due to limited space and because some distfiles have legal restrictions that prevent their inclusion.) I stopped installing the ports tree from the install CD a long time ago for that reason. Perhaps sysinstall's rather strong recommendation to install the ports ought to be toned down a bit, e.g. to suggest installing the ports from CD only if one does not have a high-speed Internet connection. You've asked a question, given some clarification as to what you are referring to, and I can tell you I don't have anything other than possibilities - which may be far from the truth - as to why this is. You're referring to a 4 CD set, that can't be downloaded from FreeBSD.org, that has to come from somewhere else, such as the FreeBSD Mall or somewhere else. I would use that if I couldn't connect to the Internet at all. Maybe, I should say: I can't tell you why it is that way. I've never been very concerned about it, just understood that it was that way and lived with it. I've never had a problem with an up-to-date ports tree not playing nicely with a RELEASE or a STABLE install. I suspect the reason is that I just never happened to up-date the ports tree at a time when there were problems. It does happen at times, but then... You've probably heard the advice somethings wrong with your ports tree, blow it off and re-install it. It's not a big problem to deal with, the problem comes when you need to do it and don't. Sysinstall only asks if you want to install the ports tree. If I was going to update it with cvsup, I would install it from there. I use portsnap, so I don't install it from the CD. Yes, I have a hi-speed connection. It makes things easier. I wouldn't be without it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Word processor for 6.1
On Monday 04 September 2006 02:08, Perry Hutchison wrote: Anyone know where I can find a working word processor for 6.1? AbiWord and OpenOffice both require Gnome, which won't build. richtext builds OK, but as soon as I try to select bold it writes 4 lines to stderr and drops core: Message backtrace: bold bold OutOfBounds: offset 0, size 0 ___ You can go to http://porting.openoffice.org/freebsd/ and download openoffice2.0.3 pre-built binaries from there. I would suggest that, rather than trying to build it. You're probably going to need java. I suggest getting the pre-built binary for diablo-jdk-1.5.0.07.00, you can get it here: http://www.freebsdfoundation.org/downloads/java.shtml Try to save yourself as much pain as possible. Building openoffice from ports tends to fall in the category of pain. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Word processor for 6.1
On Monday 04 September 2006 13:55, Perry Hutchison wrote: Try to save yourself as much pain as possible. Building openoffice from ports tends to fall in the category of pain. So it would seem :( I thought the whole point of the Ports Collection was to avoid this sort of problem. That's the idea, and in most cases that's true. The ports system just keeps getting better and better. However,there are some ports that are just a pain to build and install. Either they can be tricky to do, they take a really long time, or both. OpenOffice falls in there. I'll avoid building it and use a pre-built package. After you install it, you'll find that it shows up for an update because two lines were swapped in the Makefile. Since I don't care to accidentally be rebuilding openoffice because of this, I have +IGNOREME in /var/db/pkg/en-openoffice.org-US-2.0.3, it doesn't show up as needing an upgrade. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Word processor for 6.1
If you installed programs from packages when you installed the system, you may get problems with version conflicts installing from an updated ports collection - this happens usually when the last release is getting old. In that case, maybe you should clean out the system, deinstall all packages, update ports and start again. This takes time but given that 6.2 is coming up. It would also thoroughly defeat the purpose of installing from CD! Not hardly. It doesn't even come close to it. I wonder if I ought to wipe the partitions and start completely over with a fresh install, and this time *don't* try to update the Ports. This is a decision you have to make for yourself. I personally think it to be a very unwise choice and one I would never consider, but then... I would also like to point out that when you ask for help on questions@ and someone asks you a question, if you have the information it should be given, even if it was already posted on another list. I'm pretty sure that most of us don't follow all of the possible lists. So, even if I did follow the gnome list, if you said something is already posted there, that's too bad, I'm not about to do a lot of extra work trying to help you out. That's time I can put to better use working on my own equipment, or helping someone who will work with me to help them. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel won't build: 6.1-RELEASE 6.1-STABLE
On Saturday 22 July 2006 10:49, Kyrre Nygard wrote: Hello, I'm trying to upgrade my kernel from 6.1-RELEASE to 6.1-STABLE. But it will not work, it fails out when dealing with umass. This is a freshly installed system. The command I issued was: make buildworld KERNCONF=SURIA You really only need 'make buildworld', KERNCONF=SURIA isn't used at this point. # # /usr/src/sys/i386/conf/SURIA # machine i386 cpu I686_CPU ident SURIA Try with a GENERIC config file, see if that builds. You may have taken something out that needed to be in the config file. I have one computer that has to be done that way. options SCHED_4BSD options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options MAC options MD_ROOT options NFSSERVER options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options COMPAT_43 options COMPAT_FREEBSD4 options COMPAT_FREEBSD5 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options AHC_REG_PRETTY_PRINT options AHD_REG_PRETTY_PRINT options ADAPTIVE_GIANT device isa device eisa device pci device sio device agp device apic device ata device atadisk device atapicd device atapifd device fdc device firewire device sbp device uhci device ohci device ehci device usb device udbp device ugen device uhid device ukbd device ums device ulpt device uscanner device umass device psm device atkbdc device atkbd device vga device radeondrm device splash device sc device npx device ether device miibus device bge device loop device mem device io device random device sl device ppp device tun device pty device md options INET options INET6 options IPSEC options IPSEC_ESP options IPSEC_DEBUG device gif device faith device bpf device pf device pflog # # Build transcript # [...] *** Error code 1 Stop in /usr/obj/usr/src/sys/SURIA. *** Error code 1 Stop in /usr/src. *** Error code 1 Thank you all, Kyrre ___ You may have a problem with your sources. You can try blowing off the source tree and re-cvsuping it. I've had to do that before. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: post re jdk port
On Friday 21 July 2006 04:54, eoghan wrote: Hi I postd a question about the jdk port but didnt see my message get to the list. Since Im using a gmail account it may be something to do with this, but I do remember seeing previous posts I made. Can someone let me know if it got through and if not I can post the same again. Thanks Eoghan. ___ It got through to the list. Have a little more patience, sometimes things don't work quite as we want them to. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jdk port
On Thursday 20 July 2006 16:11, eoghan wrote: Hi While installing openoffice I had to grab jdk15. This is the build error: Note: * uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 21 errors 12 warnings gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/ java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. *** Error code 1 Are the suggested zip for jdk the same for amd64? How would I go about fixing this problem? Thanks Eoghan ___ Installing openoffice can be a pain and so can installing jdk15. So, unless you're determined to have the experience of installing them from the Ports Tree, I would suggest installing pre-built binaries instead. For java, you can find what you want here: http://www.freebsdfoundation.org/downloads/java.shtml For openoffice, look here: http://porting.openoffice.org/freebsd/ Install the diablo package first, then openoffice. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CUPS, one more try
On Wednesday 12 July 2006 22:42, E. J. Cerejo wrote: I've been trying to configure my HP Officejet 4315 using CUPS 1.2.0 but so far all I can do is configure a printer using the web interface and I'm able to print a test page but when I try to print any other document I'm unable to print, I get that quick popup window saying that cups is starting but nothing else, but today I notice something else whenever I run lpstat command I get this: Printer '[EMAIL PROTECTED]' - cannot open connection - No such file or directory Make sure the remote host supports the LPD protocol Printer '[EMAIL PROTECTED]' - cannot open connection - No such file or directory Make sure the remote host supports the LPD protocol pr-b is the name of my printer, through some googling I found out it maybe looking for my printer, do I need to edit some other file to tell lpd where this printer is? EJC www.only7bucks.com - Did you happen to check /usr/bin/ to see if lp, lpq, lpr, and lprm are there? If they are, you need to either remove them or rename them. Cups installs these in /usr/local/bin and since it's later in the path, they're never used. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CUPS, one more try
On Thursday 13 July 2006 08:09, E. J. Cerejo wrote: Don I just did what you told me but I still get the same message when run lpstat, and still can't print. EJC www.only7bucks.com - Take a look at: http://home.nyc.rr.com/computertaijutsu/cups.html Go to the section on FreeBSD and NetBSD, this should help you out. There are a number of suggestions here that I didn't give, sorry, I wanted to give you some help, not hand it to you on a platter. Do a 'ps ax |grep cup' and make sure that you see 'cupsd'. If you don't, you will need to do a 'cupsd', recheck that you have cupsd running. Go to http://localhost:631/admin (user would probably be root and password would be the root password. Configure printers from there. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAPICAM
On Tuesday 11 July 2006 14:16, Beni wrote: On Tuesday 11 July 2006 18:33, Chris Maness wrote: How do I load atapicam at boot time. I tried to have it load the same way I have the sound modules load, and it doesn't work. After the system is up and running I can load just fine. Why don't you add device atapicam to your kernel and rebuild the kernel ? It should take care of loading it at boot too. Beni. ___ Or, you could put 'atapicam_load=YES' in /boot/loader.conf and save the kernel for another time. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to avoid recompiling applications?
On Monday 05 June 2006 09:49, Lowell Gilbert wrote: Jonathan Horne [EMAIL PROTECTED] writes: so, could i theoretically use 'make reinstall' on a fresh system where the port had never been previously installed? Maybe, maybe not. If make install doesn't work because there's already a .install_done... file in the work directory, then reinstall will be what you need. ___ I think a fresh system, where a port has never been installed, would not have a work directory in that port, so make install would work unless the port is broken. Using make reinstall in a port on a system that has been freshly reinstalled isn't going to save the OP anytime by avoiding recompiling ports, they'll be recompiled. How to save time is what he asked about, as he tends to experiment with this system and screw it up, requiring a reinstall from scratch. He also said that using pkg_add -r with, say kde, always tends to have something wrong with it. The answer is: when he installs the ports, make a package using make package. Unfortunately, this doesn't make a package for ports required for that port, But, make package-recursive would, with the exception of certain ports, and he can get around that if he's clever enough. Another thing he can do is: use pkg_create -b some-port-already-installed and save it somewhere. Then he can do pkg_add that-saved-port.tbz and get that port and the required dependencies. If he's missing a dependency, oh well, guess what. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to avoid recompiling applications?
On Sunday 04 June 2006 12:19, Nikolas Britton wrote: On 6/4/06, Jonathan Horne [EMAIL PROTECTED] wrote: so, could i theoretically use 'make reinstall' on a fresh system where the port had never been previously installed? No, you can't. Yes... but what's the point?... when you can make your own packages. instead of typing 'make install' type 'make package', this will spit out a .tbz file you can use with pkg_add etc... http://www.onlamp.com/pub/a/bsd/2003/08/07/FreeBSD_Basics.html Now, this is what I do, except do it make package-recursive, that way you get any packages that have been installed as requirements. Be sure to do mkdir /usr/ports/packages, otherwise, the packages you're making are going to be stored in the individual port. If you have /usr/ports/packages, they'll be stored in one location that you can copy elsewhere, cd or dvd for instance. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to avoid recompiling applications?
On Sunday 04 June 2006 12:54, Mikhail Goriachev wrote: Donald J. O'Neill wrote: On Sunday 04 June 2006 12:19, Nikolas Britton wrote: On 6/4/06, Jonathan Horne [EMAIL PROTECTED] wrote: so, could i theoretically use 'make reinstall' on a fresh system where the port had never been previously installed? No, you can't. Yes... but what's the point?... when you can make your own packages. instead of typing 'make install' type 'make package', this will spit out a .tbz file you can use with pkg_add etc... http://www.onlamp.com/pub/a/bsd/2003/08/07/FreeBSD_Basics.html Now, this is what I do, except do it make package-recursive, that way you get any packages that have been installed as requirements. Be sure to do mkdir /usr/ports/packages, otherwise, the packages you're making are going to be stored in the individual port. If you have /usr/ports/packages, they'll be stored in one location that you can copy elsewhere, cd or dvd for instance. You could also use pkg_create. man pkg_create Cheers, Mikhail. Yes, you could, if it's already installed on the computer. If I took the output from pkg_info and compared it to what packages were in /usr/ports/packages/All, I could use pkg_create to build the missing packages I wanted to save to do a fast reinstall. But, if the port hasn't been built and installed yet, pkg_create will complain about it and conk out. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: makeworld FAILURE on 5.4-STABLE
On Wednesday 17 May 2006 05:10, Kyrre Nygard wrote: Hey man, # df Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1a248M 35M193M15%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad4s1d248M 80M148M35%/var /dev/ad4s1e248M 10K228M 0%/tmp /dev/ad4s1f142G118G 12G91%/usr Great shot! :) So in my case, can I not first mount /dev/ad4s1f from FreeSBIE maybe, delete everything except my home directory, and then run a FreeBSD 6.1-RELEASE reinstall, skipping the parts that would mess with my /dev/ad4s1f? Hehe, no it would not be the end of the world. But it would put an end to the fruits of a lot of struggle. See you around man, Kyrre The problem is that you've got home mounted under usr. Usr is going to have to be redone when you install 6.1 . Did you set your disk up according to what was recommended? I got bit in the ass one time doing it that way, it took me about a week to determine that '/' wasn't big enough. After that, I setup according to what I know won't give me a problem if I ever have to do something. I think, if it was me, I'd look at some big harddrives and go from there. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: makeworld FAILURE on 5.4-STABLE
On Tuesday 16 May 2006 03:30, Kyrre Nygard wrote: Hello Don! Yes it's the `make buildworld' as far as I know. The /etc/make.conf contains PERL_VER=5.8.7 and PERL_VERSION=5.8.7. Is it possible, do you think, to use a FreeSBIE CD maybe to clean out everything on my harddrive but my /home/kyrre where all my important files are, and then reinstall the latest FreeBSD without reformatting? It might be risky, let's say I hit the wrong switch and it does format everything, but you get my point right? To just lay a new FreeBSD on top of an empty harddrive? I hope this is possible somehow ... Well, take care Don! -- Kyrre Is /home on a slice of its own. Mine is, for the reason that if I have to blow off the system and reinstall, I can safely do that, as long as I don't make any changes to /home, just remount it as /home. You can do this with sysinstall, very easlily. Send the output from 'df', I can tell from that. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: makeworld FAILURE on 5.4-STABLE
On Tuesday 16 May 2006 05:30, Kyrre Nygard wrote: Is /home on a slice of its own. Mine is, for the reason that if I have to blow off the system and reinstall, I can safely do that, as long as I don't make any changes to /home, just remount it as /home. You can do this with sysinstall, very easlily. Send the output from 'df', I can tell from that. Don Hello! Actually, my /home is under /usr ... uh oh huh? No can do then? Thanks for the tip of having /home as a seperate slice though, I'll treasure it for the rest of my days! Peace, Kyrre Not as you have it now. However, I read a possible solution that I think might work, to you from David Stanford. I think it will work, it just needs a couple of suggestions to flesh it out a bit. I'll requote it here: How large is your /var slice? If it's large enough to fit /home (or at least the files you'd like to save), maybe try booting into single-user mode, mount /usr and /var, wipe out /var, copy the files from /usr/home to /var, and just remember to document what slice /var was. Then you could just reinstall the base system around it using a 6.1-RELEASE CD, no? Just a shot in the dark... === Not a bad shot in the dark, I think it will work if you do it this way: 1) Follow what David said above, be sure to document what slice /var is. You're going to need that information when you reinstall with the 6.1-RELEASE disc. 2) boot up the release disc. Use the standard install method. The first thing you come to is fdisk partitioning. The only thing you're going to do here is make an existing partition bootable, don't change anything else, don't make any new partitions, don't delete any. Just make the one partition bootable, then go on to the next step and install the boot manager. 3) BSDlabel is the next step. Since you didn't change any partitions on your disc, the existing slices should come up. You can remove and recreate all of them except the one you had for /var. You're going to mount that one as /home. At this point, you can create your other slices and mount points. Make sure that the slice you now have as /home is not going have 'newfs' run on it, all the others need to have it done, but not /home. Then go on with the installation. Until you go through the disk label step, you haven't changed anything. Once you get through that step, you're committed, and what will be, will be. So, if you need any clarification, ask for it. Just remember, if you make a mistake, it's unpleasant and you'll be kicking yourself in the ass, but it's not the end of the world. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: makeworld FAILURE on 5.4-STABLE
On Monday 15 May 2006 04:03, Kyrre Nygard wrote: Hello Don, good old friend :) Yes I am back. I had to change my alias because too many people were after me. And also I'm still stuck on the same problem. I did make a clean 6.1-RELEASE blow at my Pentium 120mhz firewall which needed the buildworld the most. Now it's my Pentium III 3,2ghz workstation that needs it, however it's got too much data on it that I'm currently in no position to back up, not even temporarily, so I'm not sure what to do other than this buildworld. Any suggestions? Oh yeah, I accidentally left the `*' out in chflags -R noschg. Take care, K* I was hoping it be as simple as a missing '*', but I would think there would be error messages showing up about that. Oh, well. Ok, you're stuck in the same place as before, and by that I mean you are failing the 'make buildworld' part of the sequence, correct?. That means that there's something you're either doing or not doing, prior to starting the buildworld that's causing a problem. What's in your /etc/make.conf? Try doing 'make buildworld' with the GENERIC conf file rather than your NINJA one. The problem may be there. If you can get through the upgrade using the GENERIC you've got the upgrade in place and you can find out what's wrong with NINJA. That's the best I can suggest for now. And do the 'make cleandir' twice, as Gerard suggested. It's not irrelevant. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: makeworld FAILURE on 5.4-STABLE
On Sunday 14 May 2006 07:31, Kyrre Nygard wrote: I believe it should be: chflags -R noschg /usr/obj/usr rm -rf /usr/obj/usr cd /usr/src Yes, the 'make cleandir' statement is run twice. -- Gerard Seibert [EMAIL PROTECTED] Once or twice, it is still irrelevant. Thank you so much though. -- Kyrre Ah, Kristian, I see you're back. And you still can't get past 'buildworld'. And you're still giving kind of flip answers, although with a thank you at the end. What processor are you using? You know, your best bet might be to blow off the 5.4 and do a new install with a 6.1-RELEASE disk. At least then you could get upgraded. Ok, I saw an error in your beginning procedure: cvsup -g -L 2 /etc/cvsupfile cd /usr/obj chflags -R noschg It's right here. You need to use this: chflags -R noschg * rm -rf * cd /usr/src make clean Also, Instead of 'make clean' , run 'make cleandir', twice, as was suggested. Try that and be sure to keep it out of a script. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE !!
On Monday 08 May 2006 10:55, Ceri Davies wrote: On 8/5/06 15:39, Jonathan Horne [EMAIL PROTECTED] wrote: on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? It essentially means that the release has been finished, and is being built/uploaded. Ceri It's sitting on the mirror sites, if you look. I downloaded one this morning. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why do I have to keep doing portsnap extract?
On Friday 05 May 2006 01:06, Peggy Wilkins wrote: On 5/4/06, Colin Percival [EMAIL PROTECTED] wrote: Peggy Wilkins wrote: On 5/4/06, Jason Morgan [EMAIL PROTECTED] wrote: Did you run `extract' after your original `fetch'? Yes, I did; I followed the instructions exactly. I ran portsnap for the first time a couple weeks ago after which I successfully did a bunch of portupgrades. Then the ports tree sat there on my disk untouched for a couple of weeks until I ran portsnap fetch update today. For some reason it insisted that I needed to run extract when as far as I can tell that shouldn't have been necessary. Do you have a .portsnap.INDEX file in your ports tree? Yes; I don't know if it was there before I ran portsnap today, though. -rw-r--r-- 1 root wheel 1230186 May 4 16:39 .portsnap.INDEX plw ___ Have you stopped using cvsup for updating your ports? If you do, you're going to have to use extract the next time you use portsnap. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel not compiling
On Tuesday 02 May 2006 10:07, Steve Davidson wrote: Here are the last few lines from the kernel build output: /usr/src/sys/netinet/ip_output.c: In function `ip_ctloutput': /usr/src/sys/netinet/ip_output.c:1550: internal compiler error: in expand_stmt, at c-semantics.c:883 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/obj/usr/src/sys/ROBAIX. *** Error code 1 Stop in /usr/src. *** Error code 1 On 5/1/06, Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, May 01, 2006 at 05:48:52PM -0400, Bill Moran wrote: On Mon, 1 May 2006 14:38:37 -0700 Steve Davidson [EMAIL PROTECTED] wrote: Greetings, I recently installed FreeBSD 6_0 and after building a custom kernel it failed to compile. I saved the output from make kernel KERNCONF=CUSTOMKERNELbut it is so long I wasn't sure if posting here was such a good idea. Forgive as I am relatively new to FreeBSD, should I be posting to a different list? The only error I see from the output is error type 1. Any help or a point in the right direction would be most appreciated This is the right list. Generally, posting the last 100 lines or so of the output will be enough for people to help you. If folks need more information, they'll ask you for it. I recommend using the script(1) command to capture everything, then truncated to to just the last 100 lines or so when you email it. First go back and compare your custom kernel to GENERIC: chances are you removed something mandatory and broke the build that way. Kris -- Steve Macs, Music and more ___ What you sent doesn't help at all. The last 100 lines or so would have told more. Send that. Also send your /etc/make.conf and your custom_KERN-conf. Just paste them right into the e-mail. Just what was the procedure you used. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_add -r openoffice Error: FTP Unable to get ftp:
On Monday 01 May 2006 02:31, robert wrote: On Mon, 2006-05-01 at 03:12 -0400, [EMAIL PROTECTED] wrote: Thanks but: pkg_add -r openoffice.org pkg_add: can't stat package file 'openoffice.org' that was the logical and first thing I tried. On Mon, 1 May 2006, Kris Kennaway wrote: On Sun, Apr 30, 2006 at 11:04:32PM -0400, [EMAIL PROTECTED] wrote: pkg_add -r openoffice.org-2.0.2.tbz You don't use the full versioned package name, you use the name in the Latest/ directory, which is probably something like openoffice.org. Error: FTP Unable to get ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6-stable/ Latest/openoffice.org-2.0.2.tbz: Kris _ Douglas Denault http://www.safeport.com [EMAIL PROTECTED] Voice: 301-469-8766 Doug, With open office, you need to chose the major revision, both 1.0 and 2.0 are listed. You may need to add the major version number ie pkg_add -r openoffice.org-2.0 may work. Rob I don't understand what the problem is that you all are having. Yes I do, you're not using a procedure that works well. If you want the latest Openoffice binary package, which is 2.0.2, you trundle your web browser over to here: http://www.openoffice.org/ Click on the green box that says: Get openoffice.org version 2.0.2 which redirects you to: http://download.openoffice.org/2.0.2/index.html. When you get to this page, you click on the box that says: Download OpenOffice.org which gets you to a page where you select your language, OS, and download site. If you did it correctly, that download site clickdown box will have FreeBSD page in it when selected. This will take you to another page, here you select the Continue to Download box which takes you to the actual site where you get to pick what you want to download. Maybe you can go straight to it by using this URL: http://porting.openoffice.org/freebsd/ Once you get there, download the darn thing and install it using pkg_add whatever the name is or using pkg_add -v whatever the name is. Oh, I almost forgot, this is how you get a binary package that was built for Freebsd 5.5 or 6.1 Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I think I butchered my supfile - can anyone tell me why I get this result?
On Wednesday 12 April 2006 06:45, Jim Stapleton wrote: *default host=cvsup13.us.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6 *default delete use-rel-suffix *default date=2006.04.01.12.00.00 collections. src-all tag=. ports-all tag=. doc-all tag=. Thanks, -Jim Hi Jim, The line collections.src-all tag=. is your problem. A line like src-all would fix it. Since you want to follow 6-STABLE, I think you would be better off using three separate sup-files, which could be done like this: sup-src: *default tag=RELENG_6 *default host=cvsup8.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs delete use-rel-suffix src-all * sup-ports: *default tag=. *default host=cvsup8.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs delete use-rel-suffix ports-all * sup-doc: *default tag=. *default host=cvsup8.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs delete use-rel-suffix doc-all Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Monday 03 April 2006 14:27, M. Warner Losh wrote: OK. I got bordered photo printing working. I haven't gotten borderless printing working, alas. The key points I learned: (1) Install print/cups. (2) Install graphics/hpijs. This filters .ps - goo the printer groks (3) Install graphics/gimp.This makes .ps files (4) Kill lpr/lpd before starting cups. (5) Make sure you configure lpr/lpd not to startup on boot (6) Remove lp* binaries (7) Setup buildworld /etc/make.conf so it doesn't build lpr with NO_LPR or WITHOUT_LPR (8) Add printer via localhost:631 web interface. (8) Set printer to draft mode via cups for testing (9) Use firefox to generate test prints. (10) To print from gimp, I have to remove the '-l' from the command line every time I print in the printer setup. This causes the raw .ps file to go to the printer, rather than via cups' postscript filter for the printer. (11) To get photos, one must set photo quality via cups setup interface. #10 is was tripped me up for a long time. That's why printing to the black and white printer worked for me (it was a postscript printer), while it failed to the color. I hadn't noticed before that it printed the raw postscript and then lots of new lines. Since these newlines weren't accompanied by CR, all text was off the edge of the papper, all I got was a bunch of blank pages. #5 bit me on boot. Since cups replaces the /etc/printcap unconditionally, when lpd started it failed to start. I lost a bunch of print jobs before I worked out where they had gone and why things had gone south. I'd love to know how to print borderless prints (right now I get 1/4 (8mm) boarder on the prints). I'd also love to know how to setup gimp correctly. However, these are really side issues now that I have basic functionality working. Thanks to everybody who was helpful in getting me to this point. It got me over the hump. My HP DeskJet 5850 is working great as a color printer with CUPS and my LaserJet 2200 continues to work like before. Now, all I gotta do is to figure out my OfficeJet 4200, at least the scanning portion... But that can wait until my photo printing backlog is cleared... Thanks again, Warner Hi Warner, You have to have a printer that's capable of doing borderless prints. Most printers will only print to within 1/4 of the page. Try a custom size paper (increase the size by 1/2), maybe that will help do it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI disables network (why?)
On Friday 31 March 2006 21:59, Peter wrote: Here is what I have for irq. It looks like irq 22 is being overused. $ dmesg | grep irq ioapic0 Version 1.1 irqs 0-23 on motherboard ohci0: OHCI (generic) USB controller mem 0xfc003000-0xfc003fff irq 22 at device 2.0 on pci0 ohci1: OHCI (generic) USB controller mem 0xfc004000-0xfc004fff irq 21 at device 2.1 on pci0 ehci0: EHCI (generic) USB 2.0 controller mem 0xfc005000-0xfc0050ff irq 20 at device 2.2 on pci0 pcm0: nVidia nForce3 250 port 0xe000-0xe07f,0xdc00-0xdcff mem 0xfc001000-0xfc001fff irq 22 at device 6.0 on pci0 nvidia0: GeForce FX 5500 mem 0xe000-0xefff,0xf800-0xf8ff irq 16 at device 0.0 on pci1 skc0: Marvell Gigabit Ethernet port 0xc000-0xc0ff mem 0xfb00-0xfb003fff irq 19 at device 11.0 on pci2 fdc0: floppy drive controller port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 __ Not necessarily, I counted two uses. On one of my computers, irq 19 is used 4 times. There's only so many irq's available, sometimes some of them are shared. The problem is when some devices don't want to share. Do 'dmesg | grep storm', and 'dmesg | grep throt' that will tell you what irq has the problem and something is being shutdown. Then you can do 'dmesg | grep irq from above' to find what devices are using that irq and determine what to do. With my computers I have found a bad usb mouse (dam' microsloth product, should have known better), some devices that couldn't be plugged into the usb2.0 ports I have, they had to be plugged into usb1.1 ports only, a modem that I thought was shot but would work like a champ by repositioning it on the pci bus, and some NICs that would work best by repositioning. I also found out, what FreeBSD likes, Windows XP doesn't necessarily like. After I got everything straightened around for FreeBSD-STABLE, Windows XP took a 1/2 hour to come up, booting up with the XP install disc took about the same. It still did it after a fresh install of XP. so, I told my wife: Windows is shot, Microsoft wans me to call them to get a new number which won't help. You don't do anything on Windows that you can't do as well as or better on FreeBSD. I can't tell exactly what's wrong, Microsoft doesn't want me to know, FreeBSD thinks I want to know. I'm pulling the plug on windows and their money grubbing ways. By the way, I do give FreeBSD lessons, but pay attention or you'll have to learn on your own. Yeah, one less Windows XP installation to worry about. Of course, I didn't figure out a reason (for myself) for what was happening with Windows XP till later. You're probably going to have to put your NIC in a different slot. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Friday 31 March 2006 00:08, M. Warner Losh wrote: Let us suppose that I have a HP DeskJet 5850 that I can talk to via CUPS. I can print test pages w/o any problem. What are my options to print photos and what kind of quality can I expect relative to Windows? Warner ___ Hi Warner, The reviews of the 5850 say it prints pretty good pictures. So, the printer is capable. The problem is the cups driver your using may not be so capable, and you need to locate one that is capable of photo quality printing. A long (couple of years or so) I had an HP 2000c. The driver for windows would print very good color pictures. Since this was a networked printer and I had a FreeBSD computer connected to the LAN, I wanted to be able to use it through FreeBSD. The cups driver did a very good job with text and graphics that didn't need to be photo quality. On photos, it just plain sucked. I think I was able to use the HP2000c PPD from the Windows install - I can't say positively that's where I got it from. I had to have the 2000c installed in cups twice, once as HP2000, with the cups PPD; and once as PHOTO, with the photo capable PPD. You don't want to use the photo PPD for plain text. With that setup it was capable of print quality every bit as good as Windows. So, you should be able to print photos with the same quality as Windows, if you locate a PPD that will do it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Friday 31 March 2006 10:34, M. Warner Losh wrote: Let's assume for the moment that my PPD is good. I guess I'm looking for something more basic: how do I take the .jpg from my camera and get a photo on my printer. What's the conversion process? Warner Your going to have to look at gphoto2 and libgphoto2, and digikam. I don't have a camera anymore so I can't check it to make sure of the exact procedure. I would also expect to be doing it as root until you get the permissions set right. The camera I used connected to a serial port. There are more options available now with newer cameras. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Friday 31 March 2006 10:37, M. Warner Losh wrote: Bob, Thanks for the tips. I have these ports installed, but am tripping over something stupidly basic: what converts the pict0001.jpg into something that can be fed to the hpijs driver that will print? Warner ___ Gimp will do image manipulation as well as print, openoffice, several in kde - kuickshow for one, several in gnome. I just printed a jpg using kuickshow, so I know it will do it. Pretty much, once you've got the jpg off the camera, what you do with it depends on your preferences. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Friday 31 March 2006 11:56, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Donald J. O'Neill [EMAIL PROTECTED] writes: : On Friday 31 March 2006 10:37, M. Warner Losh wrote: : Bob, : : Thanks for the tips. I have these ports installed, but am : tripping over something stupidly basic: what converts the : pict0001.jpg into something that can be fed to the hpijs driver : that will print? : : Warner : ___ : : Gimp will do image manipulation as well as print, openoffice, : several in kde - kuickshow for one, several in gnome. I just : printed a jpg using kuickshow, so I know it will do it. Pretty : much, once you've got the jpg off the camera, what you do with it : depends on your preferences. gimp doesn't have my printer listed, and printing .ps to it fails. Is there some file I need to put somewhere? Warner Are you using cups? Or something else? If you have your printer working under cups, then I would think that gimp would print to it. I remember when I was using an HP2000c, it wasn't listed under gimp either, but I was able to install it there because I was able to use it with cups. Failing that, there are other programs you can use to print the adjusted jpg file, kuickshow is one, openoffice2.0.2 has several, kde has several besides kuickshow, gnome2 has several. Warner, I know you are expert on FreeBSD, and know you know your way around a computer at least as well as I do, if not better, I have several emails from you concerning ACPI, and you show up in various other lists that I belong to, so I know who you are. My question to you is: do you have some hidden reason for showing up on questions and acting like a newbie, or are you sincerely looking for help here. With the hand holding your asking for, I'm beginning to wonder. If you do in-fact, need the help, then you should know that without providing information, that you haven't been volunteering, we aren't going to get anywhere fast. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to print photos
On Friday 31 March 2006 14:16, Bob Johnson wrote: In principle, an application feeds it to CUPS, CUPS feeds it to GhostScript, and GhostScript uses the HPIJS driver to print it. Or something like that. In practice, I use APSFILTER instead of CUPS, and I haven't ever tried to do photo printing from FreeBSD, although getting my wife's HP photo printer working with FreeBSD is on my list of things to do this weekend, or next weekend, or maybe the weekend after that. The process works for printing JPEGs from web pages on my laser printer (although not with HPIJS), and since the HPIJS driver is supposed to autodetect photo paper in your printer, I would expect it to just work for photos if you can print a web page with it. As for a specific application, The Gimp knows something about printing photos, but again, I haven't actually done it. Digikam also looks very promising as a photo manipulation tool. Anything that can display it and knows how to print ought to do it (kview for example?). I'm sure someone with actual experience can provide a more complete answer.;-) So far, I've printed from the Gimp by writing the file to a USB thumbdrive, and plugging that into the photo printer. The Gimp will let you define the picture dimensions in inches, which may be necessary to get the printing results you want. Otherwise you may end up with a picture that is 1 x 1.5 inches, or one point by one point, or a piece of an 8x10 printed on 4x6 paper, or any of several other possible defaults I've managed to print in the past. Some printers also do bad things if the image has too many pixels (or maybe bytes), so I've sometimes needed to reduce the image resolution before printing. - Bob ___ Unless the printer was capable of determining what sort of paper it was loaded with, I just don't see how the HPIJS driver would autodetect photopaper. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0 APCI Config PMAP
On Friday 31 March 2006 18:55, Don O'Neil wrote: I am 'burning in' some hardware and drives before putting them into production using various tools (raidtest, etc...) and have a couple of questions.. Occasionally under high load when doing the raid test, I see: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC What does this mean, and what should I change it to to correct the problem? I also get the occasional error that it couldn't write to the device (twed) ... Everything seems to work ok though. Also, my motherboards APCI is horribly broken, I can boot ok without APCI if I select option 2 from the boot menu (it's a 'stock' 6.0 install). How do I configure the system to boot without APCI automatically? Thanks! ___ Moving to 6-STABLE should fix APCI. It's about the first thing I do. After that, no problems with APCI. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI disables network (why?)
On Friday 31 March 2006 19:16, Peter wrote: I've been meaning to ask this one for awhile. I'm running 5.4-STABLE and I cannot use my network card *without* booting with ACPI enabled. The net contains trouble with people having this type of issue with Realtek cards and ACPI *enabled*. I have a Gigabyte m/b with an onbard adapter that is assigned the sk driver. So the symptom is watchdog timeout during DHCP discovery at the boot stage. My networking is non-functional if I try to boot with ACPI. dmesg says (during a successful boot): pcib2: ACPI PCI-PCI bridge at device 14.0 on pci0 pci2: ACPI PCI bus on pcib2 skc0: Marvell Gigabit Ethernet port 0xc000-0xc0ff mem 0xfb00-0xfb003fff irq 19 at device 11.0 on pci2 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:0f:ea:ec:f1:4e miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto Any ideas? __ One thing you can check for in DMESG is irq storms, throttling offending device. If you see that, it means you've got devices that don't want to share an irq, and you'll have to shuffle the cards on the pci bus until that clears up. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ASCII files becoming double lined
On Thursday 30 March 2006 09:04, Kris Kennaway wrote: On Thu, Mar 30, 2006 at 04:59:36PM +0200, Vaaf wrote: Hello! Sometimes I notice ASCII files becoming double lined. As in there somehow appearing an empty line in between every line. Why is this? And: 01 How can I detect files with double lines? 02 And then eliminate this double lining? Haha, what makes you think you can troll the mailing list one day and then ask for help the next? Go away, silly person. Kris I'm not sure, but I think his most useful purpose is providing comic relief for the list. On the face of it Kris, you're comment to him isn't much, but I keep laughing about it. Just think, all this comedy comes from one person. One person who can't successfully do a buildworld sequence, even with all the advice he's received on this list. What can I say Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a number of widly varied questions [FreeBSD 6.0; stdc++6, Xorg/Drivers issues, one KDE issue]
On Thursday 30 March 2006 09:48, Jim Stapleton wrote: Sorry if some of these aren't all exactly appropriate for here, but this seems like the best place to ask for a number of them, especially given my system is FreeBSD, and I've gotten everything from ports. I'm putting all of this in one email as just a not-so-quick, quick overview, and to ask if I should do everything in one email, or should I split it into several emails? snip Regardless, my monitor (Samsung 712N) likes 1280x1024, Xorg refuses to run at anything but 1280x960 (which isn't even in my /etc/X11/xorg.conf file). I expect in answering this my xorg.conf and my Xorg.0.log file will be desired quantities, but this is just an overview mail, and I don't want to waste space until I know this group is right for this question, or you are going to ship me off to one of the xorg lists (which I can't seem to find on their site). I'm using the dri driver module. Also, on an athlon64, and a 64 bit installtion, what's the best way to get the drm module working? ports/graphics/drm-kmod wants an i386 compile (and while I'll be setting up a i386 cross compiler for open office, I seriously doubt a 386 kernel module will be happy in a 64 bit kernel). Thank you for your time, -Jim Stapleton ___ I can help you with the monitor part. I have a Samsung 712N that runs at 1280x1024. Towards the end of xorg.conf there is a section that looks something like this: Section Screen Identifier Screen0 Device Card0 Monitor Monitor0 DefaultDepth24 SubSection Display Viewport0 0 Depth 24 Modes 1280x1024 EndSubSection That's what's in mine, and thats what gets the 1280x1024 display. You're also going to have to look for something that looks like this: Section Monitor #DisplaySize340 270 # mm Identifier Monitor0 HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 # Option DPMS EndSection I think using 'Xorg -configure' will generate a pretty good xorg.conf file (actually xorg.conf.new) that you can look at, make changes to, and test with 'Xorg -configure xorg.conf.new', you'll have to use ^Backspace to get out of it, but you'll find out if you've get things set right and if the mouse is working. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ASCII files becoming double lined
On Thursday 30 March 2006 11:27, Vaaf wrote: At 17:58 30.03.2006, Donald J. O'Neill wrote: On Thursday 30 March 2006 09:04, Kris Kennaway wrote: On Thu, Mar 30, 2006 at 04:59:36PM +0200, Vaaf wrote: Hello! Sometimes I notice ASCII files becoming double lined. As in there somehow appearing an empty line in between every line. Why is this? And: 01 How can I detect files with double lines? 02 And then eliminate this double lining? Haha, what makes you think you can troll the mailing list one day and then ask for help the next? Go away, silly person. Kris I'm not sure, but I think his most useful purpose is providing comic relief for the list. On the face of it Kris, you're comment to him isn't much, but I keep laughing about it. Just think, all this comedy comes from one person. One person who can't successfully do a buildworld sequence, even with all the advice he's received on this list. What can I say Don Whatever. You guys asked for root password, that's a risk I can't take. I don't see anything on here asking for a root password, so you must be referring to somewhere else. I'll tell you what. I wouldn't give out a root password either. I think, though, the reason it was asked for was you were proving to be so inept that it was wanted so the problem could be fixed and you would stop with your shenanigans on that issue. If you would use the suggestions given, so you have a base to work from, you could then figure out how to put it in a script and run the script to your hearts content. But until you have that base to work from, a whole lot of you're scripts aren't going to work the way you want them to. Before you can run, you learn to walk; before you walk, you learn to stand; before you stand, you learn to crawl; before you crawl, you learn to sit up; before you learn to sit up, you lay there and shit in your diapers. I'm not sure exactly were you are, but I know it's not at the run stage. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird and Firefox dead after portupgrade
On Thursday 30 March 2006 17:53, Albert Shih wrote: Le 30/03/2006 à 14:42:10-0800, Micah a écrit [EMAIL PROTECTED] wrote: 1.5.0.1_2 was commited last night, so it's probably a recent breakage. I just found a bug report on it at http://www.freebsd.org/cgi/query-pr.cgi?pr=95100 So we have four confirmed cases of firefox not working. five...but not for firefox...for thunderbird (well I don't use it at all...;-) ) Same problem when I try to laucnh thunderbird, nothing append, no error.. Regards. using : FreeBSD 6.1-PRERELEASE -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. Heure local/Local time: Fri Mar 31 01:51:25 CEST 2006 ___ This happened to me also, until I remembered this has happened before and what to try. Login as root, start the GUI (mine is KDE), open a terminal program and start firefox from there. After that, I had no problems. It's working fine. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 6.0 ipfilter nat redirect not working.
Just a quick question. How are you connecting to the Internet, by that I mean are you using aDSL? If you are, I can help you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error Compiling Open Office
On Tuesday 28 March 2006 22:08, Chris Maness wrote: I just updated my ports and tried to compile open office. got this failure while trying to compile. Any suggestions? g++-ooo: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. dmake: Error code 1, while making '../unxfbsd.pro/obj/textenc.obj' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /usr/ports/editors/openoffice.org-2.0/work/OOB680_m5/sal/textenc dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' *** Error code 255 ___ Just a thought. You can download the package for 2.0.2 and install that. Are you sure you want the experience of doing it from the port? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why are so many people using 4.x?
On Wednesday 29 March 2006 09:27, Vaaf wrote: At 14:46 29.03.2006, [EMAIL PROTECTED] wrote: of FreeBSD to building a skyscraper on shallow grounds. apparently, you did not read much of the source tree did you. or appreciate the fact that FreeBSD boots so fast and clean. Whatever. I love FreeBSD, however I'm just stating the facts. anyway, you rant made me think why my email block was not working properly. i need to check the to: and cc: -fields as well! thanks alot! regards, usleep ___ I have a question for you Kristian. Since you switched to DragonFly, why are you asking questions here? Isn't DragonFly providing support? Don't they go along with your failed method of doing a buildworld sequence either? I saw in an earlier post of yours, that we told you your method was wrong, but you think you're right. That would mean that everyone who can do it and tried to help you is wrong, and you who can't do it with your method, is right. Is that what it amounts to? I have to think about that. As for blocking your email, while the idea sounds good, I won't do that. I would miss out on some serious entertainment that you provide. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: package vs ports question
On Monday 27 March 2006 09:26, Kevin Kinsey wrote: Luiz Eduardo Guida Valmont wrote: Thanks for the answer. I just hope I'm not messing things too much. So if a port may override a package, is the only solution to this generate a package then install it? Now if this happens, what will happen for example (supposing I install everything from packages - or make package then pkg_add for that matter) when I install Adobe Acrobat? Are all its dependancies going to be installed as well? I mean, ports doesn't know which packages were installed by pkg_add, which is how I suppose those packages are installed. Sorry if I cannot make myself clear enough, but there's still the fog that blinds newbies like me. :) Sorry if I'm interjecting stupid stuff here .. . haven't yet backtracked this thread. What exactly do you mean, ports doesn't *know* which packages were installed by pkg_add ... they use the same database, and as far as the ports(7) mechanism is concerned, they are the same thing. The difference is in the details visible to the user; as far as the ports system is concerned, files is files, and port/package data is data. Is it possible to generate packages for all the dependancies? Does make package do this for all packages for which a package can be created? I hope I won't need to reinstall them but you know... you never know. :) 'make package' should include all dependencies, by my understanding; however, my understanding isn't the greatest, so YMMV. Thanks again... HTH, KDK 'make package' will install the missing dependencies but will only make a package of the the port being installed. If you want to make a package of the dependent ports you need to use 'make package-recursive'. Be advised, probably somewhere in the build of the packages, something will be missing and it will break. At least, it always has for me. So, packages are built for some of the dependent ports, but not for others. You need to check that /usr/ports/packages exists and if it doesn't, do a 'mkdir /usr/ports/packages', otherwise the built packages are put in the port. Not a really convenient place. I very seldom build packages anymore. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: package vs ports question
On Monday 27 March 2006 09:49, RW wrote: On Monday 27 March 2006 14:20, Norberto Meijome wrote: make package will actually make the package and install it for you, you dont need to do a pkg_add after that (yes, a bit counter-intuitive, but really handy) Make package creates a package out of an installed port (it will install the port first, if neccessary). It doesn't install the package - there would be no point. ___ 'make install' builds a package from the port and installs it. 'make package' builds a package and installs it, it also saves it in compressed form so it can be reinstalled if necessary. A port is a skeleton, it contains the information needed to build a package and that's it. The ports aren't installed, it's the package that results from building a port that is installed. Ports are only skeletons, the contain the information necessary to allow the port to be built into an installable package. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade fails to upgrade after using portsnap
On Saturday 18 March 2006 08:06, Jez Hancock wrote: Hi all, For a long time I've been using cvsup and portupgrade to update the ports tree once a week; this has worked well for years now. Recently though I changed to using portsnap to update the ports tree, still using portupgrade once a week to update the ports. I followed the method outlined in the handbook more or less for upgrading using portsnap, essentially running a cronjob: portsnap cron portsnap update portupgrade -arRF pkg_version -v -I -l to grab and extract the latest port snapshot, fetch any newer port distfiles/tarballs and then report by mail what ports are out of date. This worked well for a few weeks up until Feb 25th - since then not a single out of date port has been reported and 'portupgrade -arR' fails to upgrade anything. I thought this might have been to do with the recent ports freeze, though checking now I see that only went on from the start of March... I've changed back to use cvsup and the old method - basically 'cvsup -g -L2 supfile cd /usr/ports make fetchindex portsdb -u' - but still no joy. I was convinced it was the ports db files that were out of synch and thought this might do the trick to fix the problem, but unfortunately no - if I view the resulting INDEX file from this procedure I can see there are ports out of date as well, it's just 'portupgrade -arR' etc refuses to find any updates. Questions then: What could the problem be? For future reference what is the best way to purge the ports system of out of date db files and regenerate them all so 'portupgrade -arRi' will work? Cheers. -- Jez Hancock ___ Doing a little better job of reading the man page would help. While it tells you how to set up a cronjob, it also tells you this is a bad idea. You ran the cronjob, which succeeded, but failed to update the ports tree because it had nothing to update it with. If you had ever run portsnap manually, I think you would have set-up your cronjob a little differently. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade fails to upgrade after using portsnap
On Saturday 18 March 2006 08:06, Jez Hancock wrote: Hi all, For a long time I've been using cvsup and portupgrade to update the ports tree once a week; this has worked well for years now. Recently though I changed to using portsnap to update the ports tree, still using portupgrade once a week to update the ports. I followed the method outlined in the handbook more or less for upgrading using portsnap, essentially running a cronjob: portsnap cron portsnap update portupgrade -arRF pkg_version -v -I -l to grab and extract the latest port snapshot, fetch any newer port distfiles/tarballs and then report by mail what ports are out of date. This worked well for a few weeks up until Feb 25th - since then not a single out of date port has been reported and 'portupgrade -arR' fails to upgrade anything. I thought this might have been to do with the recent ports freeze, though checking now I see that only went on from the start of March... I've changed back to use cvsup and the old method - basically 'cvsup -g -L2 supfile cd /usr/ports make fetchindex portsdb -u' - but still no joy. I was convinced it was the ports db files that were out of synch and thought this might do the trick to fix the problem, but unfortunately no - if I view the resulting INDEX file from this procedure I can see there are ports out of date as well, it's just 'portupgrade -arR' etc refuses to find any updates. Questions then: What could the problem be? For future reference what is the best way to purge the ports system of out of date db files and regenerate them all so 'portupgrade -arRi' will work? Cheers. -- Jez Hancock ___ Jez, I think my first response was a little unkind and I apologize for that. The way I see it, your cronjob succeeded in doing what you set it to do. It just didn't do what you wanted. First, portsnap requires fetch to get the files it needs, 'portsnap upgrade' doesn't do that. You need to run 'portsnap fetch upgrade' or 'portsnap fetch' ' portsnap upgrade'. Had you done that, it probably would have worked and you would have gotten something from the portupgrade portion of your cronjob. As it was, there was nothing new for portupgrade to work with and report. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade fails to upgrade after using portsnap
On Saturday 18 March 2006 12:06, Jez Hancock wrote: Hi Donald, Thanks for the replies. On 3/18/06, Donald J. O'Neill [EMAIL PROTECTED] wrote: On Saturday 18 March 2006 08:06, Jez Hancock wrote: Hi all, For a long time I've been using cvsup and portupgrade to update the ports tree once a week; this has worked well for years now. Recently though I changed to using portsnap to update the ports tree, still using portupgrade once a week to update the ports. I followed the method outlined in the handbook more or less for upgrading using portsnap, essentially running a cronjob: portsnap cron portsnap update portupgrade -arRF pkg_version -v -I -l to grab and extract the latest port snapshot, fetch any newer port distfiles/tarballs and then report by mail what ports are out of date. This worked well for a few weeks up until Feb 25th - since then not a single out of date port has been reported and 'portupgrade -arR' fails to upgrade anything. I thought this might have been to do with the recent ports freeze, though checking now I see that only went on from the start of March... I've changed back to use cvsup and the old method - basically 'cvsup -g -L2 supfile cd /usr/ports make fetchindex portsdb -u' - but still no joy. I was convinced it was the ports db files that were out of synch and thought this might do the trick to fix the problem, but unfortunately no - if I view the resulting INDEX file from this procedure I can see there are ports out of date as well, it's just 'portupgrade -arR' etc refuses to find any updates. Questions then: What could the problem be? For future reference what is the best way to purge the ports system of out of date db files and regenerate them all so 'portupgrade -arRi' will work? Cheers. -- Jez Hancock ___ Jez, I think my first response was a little unkind and I apologize for that. The way I see it, your cronjob succeeded in doing what you set it to do. It just didn't do what you wanted. First, portsnap requires fetch to get the files it needs, 'portsnap upgrade' doesn't do that. You need to run 'portsnap fetch upgrade' or 'portsnap fetch' ' portsnap upgrade'. Had you done that, it probably would have worked and you would have gotten something from the portupgrade portion of your cronjob. As it was, there was nothing new for portupgrade to work with and report. Ok, I think you posted that before I clarified things in my last post :) By the by anyway... the issue I have is that when I run pkg_version or portversion I'm told there are a dozen or so ports need upgrading. However when I run portupgrade, portupgrade finds no ports to upgrade. Very frustrating. The general gist is in the following typescript/commandline output: [14:43:05] [EMAIL PROTECTED] /usr/ports# portversion -vl bash-3.1.10 needs updating (port has 3.1.10_1) mtr-nox11-0.69_2 needs updating (port has 0.69_3) mutt-devel-1.5.11_1 needs updating (port has 1.5.11_2) mysql-server-4.0.26_1 needs updating (port has 4.0.26_2) netpbm-10.26.25 needs updating (port has 10.26.26) nmap-4.01 needs updating (port has 4.01_1) p5-Archive-Tar-1.28 needs updating (port has 1.29) p5-Mail-Tools-1.73needs updating (port has 1.74) p5-XML-RSS-1.05_1 needs updating (port has 1.10) tiff-3.8.0_1 needs updating (port has 3.8.1) vim-6.4.6 needs updating (port has 6.4.6_1) w3m-0.5.1_4 needs updating (port has 0.5.1_5) [14:43:10] [EMAIL PROTECTED] /usr/ports# portupgrade -arRi --- Session started at: Sat, 18 Mar 2006 14:43:16 + -snip- ** No need to upgrade 'bash-3.1.10' (= bash-3.1.10). (specify -f to force) -snip- ** No need to upgrade 'mtr-nox11-0.69_2' (= mtr-nox11-0.69_2). (specify -f to force) -snip- ** No need to upgrade 'mutt-devel-1.5.11_1' (= mutt-devel-1.5.11_1). (specify -f to force) etc etc This is all the result after running 'cd /usr/ports make fetchindex' to get the latest ports INDEX db then running 'portsdb -u' to update /var/db/pkg/pkgdb.db. Any ideas why portversion says various ports are out of date but portupgrade doesn't want to update them? Is there any db that portupgrade would use to determine out of date ports other than /var/db/pkg/pkgdb.db? Thanks again. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://freebsd.munk.nu/ - A FreeBSD Diary http://ipfwstats.sf.net/- ipfw peruser traffic logging ___ Jez, I have no clue. If portversion is saying there is a port in need of upgrade, 'portupgrade -arRi' should find it. That's a portupgrade problem, not a portsnap problem. I would suggest trying
Re: Portupgrade fails to upgrade after using portsnap
On Saturday 18 March 2006 15:50, Duane Whitty wrote: Hi, I seem to remember needing to run portsnap fetch extract update the first time I ran portsnap. Afterwards portsnap fetch update worked as I expected. Perhaps you have already tried this? If so, my apologies for the useless noise. HTH, Duane -- Hi Duane, Don't worry about trying to help out. Sometimes the simple things can go un-noticed and cause problems. Of course, it's easy for me to say, I didn't have the problem. I think, from what Lex has been saying to me, that he's pretty much decided that, at least for now, he's going to go with cvsup. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I386 Installation
On Tuesday 14 March 2006 02:47, Eileen Wasson wrote: I'm a newbie to unix and freebsd. I'm trying to follow your documentation and keep failing the install. I have an HP COmpaq desktop dc5100 MT and it will NOT detect my iso image for the i386. i did not see it in your hardware list.htm. does that mean it's not supported or do i need new drivers? if i put it in an older ibm, the cd works. i also tried using your floppy method and that failed as well. it said no boot/loader. this box has xp loaded it already. any help would be greatly appreciated. ~Eileen __ You need to burn that iso to a cd, then you can boot from it and it'll go into install. It looks like your computer came with an 80GB hard drive. Do you have only 1 hard drive, or do you have 2? If only 1, are you planning on over-writing what's presently installed? Which iso image do you have? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail client like mulberry
On Tuesday 14 March 2006 12:40, Benjamin Lutz wrote: On Tuesday 14 March 2006 18:15, Paul Schmehl wrote: What does this New Messages feature do? It's like Favorites, except it only displays folders that have new messages in them. I have so many folders that it's a real PITA to have to scroll through 20 that have no new messages in them just to get to 10 that do. It also needs to be SMIME/PGP aware and handle IMAP gracefully (according to the RFCs, not like MS crap.) How about KMail then. It's SMIME/PGP implementation is very good (and it renders signed content very nicely too imo) and works great with IMAP. It can be comfortably used with the keyboard only (much more so than, say, Thunderbird). It doesn't filter folders, however it has a Next Unread Folder command, which makes it directly switch to the next folder with unread messages in it. Cheers Benjamin Yes, Kmail does filter folders, if you're talking about filtering messages that come in from e-lists (such as questions@) and moving them to a designated folder. The filters are easy to set up. The folders can show how many messages are in the folder,how many are new and will decrement the new filter count as they are accessed. It can also remove duplicate messages from a folder. It is one heck of an e-mail client and I haven't found anything to touch it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail client like mulberry
On Tuesday 14 March 2006 17:39, Norberto Meijome wrote: On Tue, 14 Mar 2006 13:15:07 -0600 Donald J. O'Neill [EMAIL PROTECTED] wrote: It doesn't filter folders, however it has a Next Unread Folder command, which makes it directly switch to the next folder with unread messages in it. Cheers Benjamin Yes, Kmail does filter folders, if you're talking about filtering messages that come in from e-lists (such as questions@) and moving them to a designated folder. The filters are easy to set up. I think the original poster meant the virtual folders that only show folders with new email - not email filtering (which is, I'd say, a must have feature of any software worth calling itself mail client). The folders can show how many messages are in the folder,how many are new and will decrement the new filter count as they are accessed. It can also remove duplicate messages from a folder. sylpheed-claws can do all this, as well as creating processing (as well as filters, of course) rules (which I have NO idea how or what to use it for ...but i does sound cool :D). supports IMAP and identities, like thunderbird. IMAP is not a problem at all. and I have all my folders with new email in a nice bright blue (vs. grey for folders w no unread email, and black for folders with unread email, but no new email) PGP inline and SMIME works great too. It is one heck of an e-mail client and I haven't found anything to touch it. When you subscribe to a lot of e-lists (I subscribe to about35) and you get a lot messages coming in, you learn really quick about filter rules and how handy they are. I used sylpheed-claws a number of years ago and it was very good. I used it for a bit. There is also evolution, I haven't looked at it in a while. I may want to look at them again. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cg 0: bad magic number (used to be Disappointed with version 6.0)
On Saturday 11 March 2006 21:08, you wrote: Hi Donald. It's me again. I sent this to the list and saw I didn't include you. I haven't seen the one on the list yet, this one got here first. . Ok, I have narrowed down my problem a great deal. It appears that FreeBSD cannot read the partition table of my 300 GB Seagate Barracuda. My dos diagnostic utility works because it accesses the disk in a different way. I used the entire disk (one slice/partition) and attempted to format it. This is what I get after it reaches the end of the disk: cg 0: bad magic number It also slows down significantly about 3/4 through the procedure. Are you doing this through sysinstall or are you manually running fdisk and bsdlabel. Well, maybe with a disk that big , it was getting tired and wanted to rest up before giving you the bad news. Now the funny part. I create two partitions and the newfs output is exactly the same as before when I try to format the first partition! It tries to format as if there is only one partition and produces the same error. If I remove the slice via sysinstall and then try fdisk I get this: # fdisk -vBI ad3 *** Working on device /dev/ad3 *** parameters extracted from in-core disklabel are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Information from DOS bootblock is: 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 586072305 (286168 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 812/ head 15/ sector 63 2: UNUSED 3: UNUSED 4: UNUSED fdisk: Geom not found Anyone? -- Peter __ Peter, Is this a brand new disk? Has it ever been used before? Is it still under warrantee? If it is, take it back and get it replaced. Hey, I just saw it. You made Google search. It looks to me like things just went through the motions and not the actuality of installing ufs on the drive. That's happened to me a couple of times and from what I remember, I had to start the install over from the beginning - and I seem to recall something about having to install windows first and reformatting all the hard-drives with NTFS, then I could go back in and install FreeBSD. Otherwise, I couldn't get FreeBSD to install, it just went through the motions, wiping out whatever was on the hard-drives but not putting in FreeBSD. Without a CDROM, it's going to be a little bit rough to do. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cg 0: bad magic number (used to be Disappointed with version 6.0)
On Saturday 11 March 2006 23:51, Peter wrote: Are you doing this through sysinstall or are you manually running fdisk and bsdlabel. Through sysinstall. Both disklabel and fdisk don't work. The former gives input/output error and output to the latter I gave in my last post. Is this a brand new disk? Has it ever been used before? Is it still under warrantee? If it is, take it back and get it replaced. Yeah, I'm leaning that way too. Hey, I just saw it. You made Google search. Huh? Yeah. Do a google search for Seagate ST3300831A, then search within for problems and there it is, at the bottom of the first page: Google Group results for Seagate ST3300831A problem Disappointed in version 6.0 - list.freebsd.questions - March 11, 2006 Seagate hard drive warranty - comp.sys.ibm.pc.hardware.stora ... If you search for petermatulis, there are about 263 hits. It appears at one time you were doing OpenBSD. Just a piece of trivia. I can be found also. It looks to me like things just went through the motions and not the actuality of installing ufs on the drive. That's happened to me a couple of times and from what I remember, I had to start the install over from the beginning - and I seem to recall something about having to install windows first and reformatting all the hard-drives with NTFS, then I could go back in and install FreeBSD. Otherwise, I couldn't get FreeBSD to install, it just went through the motions, wiping out whatever was on the hard-drives but not putting in FreeBSD. Without a CDROM, it's going to be a little bit rough to do. I don't understand why you mention Windows. Surely I don't require Windows to get this drive to work. As for the cdrom, I can always put it back to do an install. It doesn't cause trouble -just slows down the boot drive. I had a hard drive one time that I just couldn't get FreeBSD to format, no matter what I did. I finally gave up and put WindowsXP on it, which was somewhat of struggle too. After that, since what I wanted was FreeBSD, I retried installing it, it worked this time, I don't know why but it did. I can only think that there was something wrong with the original installation of FreeBSD and I wasn't experienced enough, at that time to figure out what it was, other than it wasn't working right. If I'm remembering correctly, a while later the drive would operate intermittently and I put it in the basement. -- Peter Hi Peter, Since you can play around a bit. Try reconnecting the CDROM and just the 300GB Seagate on the other ata channel. Then see if FreeBSD will successfully install on the drive. How much time do you have to work with this problem? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb warning message
On Sunday 12 March 2006 07:07, Gerard Seibert wrote: When running the following command: pkgdb -Fv, I receive the following message: Duplicated origin: devel/libtool15 - libtool-1.5.22_1 libtool-1.5.22_2 Unregister any of them? [no] I am unsure of what action to take, therefore I have chosen the default [no] one suggested. Would it be prudent to delete one of these duplicates, and if so does it matter which one? If it was me, I would think that when libtool-1.5.22_1 was upgraded to libtool-1.5.22_2, the registration for libtool-1.5.22_1 wasn't removed from the database properly. So, yes, it would be best to delete the registration of libtool-1.5.22_2 through pkgdb -F. Answer [no] yes cr and get rid of it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Friday 10 March 2006 22:57, Peter wrote: I'm setting up a new server on 6.0 I've been planning for a long time and I am very disappointed with two critical issues. My motherboard is the ASUS K8V-X SE that I chose because it was listed as compatible at the FreeBSD/amd64 Project: http://www.freebsd.org/platforms/amd64/motherboards.html I wonder if going back to 5.4 might help? Onto the problems... 1. I have 4 IDE drives: primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate Barracuda 300 GB (slave) Problem: The 300 GB drive is unusable. I set it up ok with sysinstall during the installation but the system will not boot properly if it has an entry in /etc/fstab. I get many errors like: ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 I also get input/output error if I try to examine its label with disklabel. dmesg output is at the end of this post when I booted without fstab line. The strange thing is that the two drives on the secondary controller are so similar. Same manufacturer, same product line, the speeds are the same. Everything is the same except the size. I ran dos-level diagnostics on it and no problems were found. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) Origin = AuthenticAMD Id = 0xf4a Stepping = 10 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P GE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 536543232 (511 MB) avail memory = 515702784 (491 MB) snip ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Saturday 11 March 2006 13:38, Peter wrote: --- Donald J. O'Neill [EMAIL PROTECTED] wrote: [...] ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Can this be causing the problem with the 300 GB drive on the other controller? What I don't understand is why is there a problem only with one drive on the secondary controller? As for the cdrom, how else can it be connected? It will ALWAYS be slower than the hard disk. Or do you mean it should just not be connected to the boot drive? I never had such a problem before. I'll move around my drives and see what happens. Thanks for your help. -- Peter Hi Peter, You're going to have to have the cdrom connected, just not with a hard-drive or you'll have problems. As for the third hard-drive, that may have more to do with the way you set up the system than the problems with the connections as they are now. But, if you remove that drive and reinstall the system, I think (actually, I know, if you do it right) that will clear up a lot of problems. You've got two SATA ports on that MB, I think you would have problems then too. If you need that 40 GB drive, I suggest you go out and get a controller that you can run all three drives off of.. What I mean is, if you have the cdrom and the 40GB HD connected to the same port, on the same cable, as you have, it will only run at the speed of the cdrom. You have to get the HD off of that port. Since you've used the slave port with the other two HDs, your only choice is to install a Controller card, like a Promise or some other card. I had a problem like that at one time and that was the only way to fix it. That's why I sent that snippet from the at man page, it tells you what's going to happen if you do it this way. I don't think you're going to like have at ATA100 drive as the system drive running at UDMA33, it just might result in timing problems. Don PS At this point I probably can't answer anymore questions, at least not today. I've had too many beers and I'm having a tough time typing. I can still make sense, I just am having a problem getting it from my brain to the e-mail. And I intend to have some more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Saturday 11 March 2006 18:48, Peter wrote: You can answer me tomorrow if you like but here is an update: I removed the cdrom and the problem remains. I got the usb ports to work as well by updating the bios and fiddling with some settings. It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. Again, it is detected fine by the bios; it passes dos level diagnostics; it is on the same ide cable (as slave) as the 200 GB drive that is identical to it save for an extra 100 GB. My next step is to boot with knoppix to see how it behaves. -- Peter Hi Peter, I've recovered sufficiently enough that I can type without spending all my time correcting spelling errors that a spelling checker can't fix. OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Saturday 11 March 2006 20:03, Peter wrote: OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. dmesg now says: ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA133 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 So ad0's speed has increased by 100 MB/s? I was guessing that it was an ata100, it seems to be an ata133 instead. Now you can see what the difference is when connecting a hard-drive with a cdrom. Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Yes, per install defaults ufs (and most probably soft updates) was used. Everything was done via the default sysinstall procedure. I said to use entire drive and then made one partition. It creates /dev/ad3s1d. I just entered sysinstall again to start fresh and during the format portion Doing newfs I hear some sounds I've never heard before on a hard drive. Like a mechanical arm is trying to move but it keeps bouncing back. Then I get: Error mounting /dev/ad3s1d on /images : Input/output error But if there was something mechanically wrong then my dos-level diagnostics would of picked it up (I had an disk excercise tool running on it for 20 minutes without any problems). No, Microsloth makes things run (or appear to run) by hiding a lot of information from you. When did you run the dos-level diagnostics on the disk, before or after you installed FreeBSD? I ask because if it was after, well, dos-level disk diagnostics can't access a ufs formated disk without doing nasty things to what's on it. If was before, you should have run spinrite 6.0 on it, but that's going to run for about , oh say, at a wild guess, on a drive that size, 2 or 3 days. Your twenty minute run on that drive wouldn't really tell you much unless the drive was drastically failing. Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I need all three drives: 1. system drive (40 GB) 2. client data backups (200 GB) 3. client data images (300 GB) The #3 drive (the problematic one) will actually be removed offsite once the (client hard drive) images have been stored. And this is where I might be able to weasel out of my current predicament. I can put back the cdrom afterwards. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? No, no. This is a brand new install of 6.0 (I can therefore mess around with impunity). When I mentioned go back to 5.4 I did not mean to imply I upgraded. Just don't cable back with the cdrom. -- Peter Now, what about your usb? a message like: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Nothing wrong with that message. Base on that message, you don't have a problem. It's when you see messages like irq storm on some device throttling source, or device returns some error message, or can't assign an irq, then you know you've got a problem that's going to require some swapping around on the pci bus. As a matter of fact, I was having usb problems until I went 6-RELEASE to 6-STABLE. Which at that time I was able to determine that it wasn't actually a usb problem, I was having a problem with a modem and bad usb mouse. I pulled the modem and was going to throw it away, put it away instead, until I had a need for one at which point I found out that it's position on the pci bus made the difference in whether it would play nicely with the cards or not. The mouse did get tossed, it would work intermittently under windows and FreeBSD would only get to a certain load point and then reboot. Actually, finding it was a little more difficult than I've said. Don ___ freebsd-questions@freebsd.org mailing list
Re: Haven't been able to make world in about a year
On Monday 06 March 2006 10:31, Kristian Vaaf wrote: At 16:36 03.03.2006, Giorgos Keramidas wrote: On 2006-03-03 15:08, Kristian Vaaf [EMAIL PROTECTED] wrote: Sorry sorry sorry, I am so very sorry. http://www.home.no/hedhnta/result.txt is indeed online now. This doesn't look right. Are you sure your source tree is clean and up to date? As Donald has posted latter: On 2006-03-03 09:09, Donald J. O'Neill [EMAIL PROTECTED] wrote: Alright Kristian, why don't you post your supfile, make.conf, rc.conf, output of uname -a, a description of what equipment your doing this with, what you're trying to accomplish and why, what you're doing to make this come about, what you expected to happen, what did happen. How you're taking all the advice you've been given and bending it to suit yourself - which, I have to tell you, IS NOT WORKING, or you would be singing a different tune. Please post all the details Donald has requested. You all got the details I posted earlier? Alright, I just finished retrying the whole process after adding these lines to my /etc/make.conf: CFLAGS= -O2 -pipe COPTFLAGS= -O2 -pipe And there is no change, I still get: -- stage 2.3: build tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL=sh /usr/src/tools/install.sh PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy /usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/u sr/bin WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS=-m /usr/src/tools/build/mk -m /usr/src/share/mk /usr/obj/usr/src/make.i386/make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=504100 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools === bin/csh (obj,build-tools) grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep '^#define' sh.err.h cc -E -O2 -pipe -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='/bin/csh' -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/bin/csh/../../contrib/tcsh/tc.const.c /usr/src/bin/csh/../../contrib/tcsh/sh.char.h /usr/src/bin/csh/config.h /usr/src/bin/csh/../../contrib/tcsh/config_f.h /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char \1[];/' | sort tc.const.h In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:93, from /usr/src/bin/csh/../../contrib/tcsh/tc.const.c:33: /usr/include/wchar.h:33:18: cwchar: No such file or directory cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 -pipe -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='/bin/csh' -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/bin/csh/../../contrib/tcsh/gethost.c In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:93, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/include/wchar.h:33:18: cwchar: No such file or directory In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:93, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/include/wchar.h:35: error: syntax error before std In file included from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/sh.h:97: error: syntax error before eChar /usr/src/bin/csh/../../contrib/tcsh/sh.h:97: warning: data definition has no type or storage class In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:1304, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/sh.decls.h:221: error: syntax error before readc /usr/src/bin/csh/../../contrib/tcsh/sh.decls.h:221: warning: data definition has no type or storage class *** Error code 1 Stop in /usr/src/bin/csh. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Just to be clear, this is on the Pentium 120MHz, as I have a make buildworld problem on both of my FreeBSD 5.4-STABLE boxes. Good bye, Vaaf Well Kristian, it looks to me like your procedure sucks, since it's failing on two computers. That should tell you something is wrong with the way you're doing things. This has been going on for over three weeks. Pick someone you think knows what they're doing and follow their suggestions. Running a script is not saving you any time if it fails. Do it without running a script. There is a difference between running a script and running script (the program) to make a record of what went on. In your supfile, I suggest the following changes: *default host=cvsup.no.FreeBSD.org Are you actually using this line? Or, are you trying to disguise it so we're more confused than already and assume you actually know something. *default base=/usr change this to: *default base=/var/db *default prefix=/usr
Re: Haven't been able to make world in about a year
Well Kristian, it looks to me like your procedure sucks, since it's failing on two computers. That should tell you something is wrong with the way you're doing things. This has been going on for over three weeks. Pick someone you think knows what they're doing and follow their suggestions. Running a script is not saving you any time if it fails. Do it without running a script. There is a difference between running a script and running script (the program) to make a record of what went on. In your supfile, I suggest the following changes: *default host=cvsup.no.FreeBSD.org Are you actually using this line? Or, are you trying to disguise it so we're more confused than already and assume you actually know something. +++ My apologies about the above comment Kristian. I see that it does exist Don *default base=/usr change this to: *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6 change this to: default release=cvs tag=RELENG_6_0 *default delete use-rel-suffix src-all #ports-all tag=. #doc-all tag=. Just upgrade src. Don't be mucking around with ports and doc at this time. Leave them be. Blow away your sources and re-cvsup src. Follow somebodies procedure that is known to work. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Sunday 05 March 2006 07:38, Kristian Vaaf wrote: At 16:36 03.03.2006, Giorgos Keramidas wrote: On 2006-03-03 15:08, Kristian Vaaf [EMAIL PROTECTED] wrote: Sorry sorry sorry, I am so very sorry. http://www.home.no/hedhnta/result.txt is indeed online now. This doesn't look right. Are you sure your source tree is clean and up to date? As Donald has posted latter: On 2006-03-03 09:09, Donald J. O'Neill [EMAIL PROTECTED] wrote: Alright Kristian, why don't you post your supfile, make.conf, rc.conf, output of uname -a, a description of what equipment your doing this with, what you're trying to accomplish and why, what you're doing to make this come about, what you expected to happen, what did happen. How you're taking all the advice you've been given and bending it to suit yourself - which, I have to tell you, IS NOT WORKING, or you would be singing a different tune. Please post all the details Donald has requested. Sure thing! # cat /etc/cvsupfile *default host=cvsup.no.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_6 *default delete use-rel-suffix src-all ports-all tag=. doc-all tag=. # uname -a FreeBSD arba.domain.com 5.4-STABLE FreeBSD 5.4-STABLE #4: Wed Sep 21 01:34:15 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARBA i386 These apply to both the box that fails into result.txt (Intel Pentium 120MHz) and result_2.txt (Intel Pentium 4 3,2GHz). I am trying to upgrade these boxes. I expect things to work :) This is how I do it: cvsup -g -L 2 /etc/cvsupfile cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src make clean make buildworld make buildkernel KERNCONF=ARBA make installkernel KERNCONF=ARBA make installworld mergemaster Hope that helps! All the best, Vaaf ___ Yes, it does. If this is the way you do it, after all the advice you've been given, it tells me that you aren't much on following advice that you have sought. Keep on doing it your way and continue to fail. If that's not what you have in mind, go back and reread the advice already given by myself, and others. We are successful, you are not. That's why we're giving advice and you're asking. You could be successful. You still only gave part of what was asked for. Sorry if this upsets you, but that's the way it is. I, for one, can't help you if you refuse to accept advice already given. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: script(1) Why does it output in CR/LF?
On Friday 03 March 2006 04:52, Kristian Vaaf wrote: At 16:05 28.02.2006, James Bailie wrote: Glenn Dawson wrote: At 02:30 AM 2/28/2006, Kristian Vaaf wrote: Hello. I am just curious why the files I generate with script(1) output in CR/LF forcing me to run dos2unix on them everytime? Script just captures the output of your shell, and your shell has to send crlf in order to get the cursor back to the beginning of a line. No it doesn't. The script(1) utility interposes a pseudo-terminal between the program whose output is to be captured and itself, so the program thinks its running on a terminal device and behaves accordingly. Then script(1) acts like a transparent filter, shuttling data back-and-forth from the actual terminal to the pseudo-terminal, while sending a copy of the program's output to the log file as well. It is the terminal driver in canonical mode, inside the pseudo-terminal, that is expanding NLs in the proggy's output stream into CRNL pairs. -- James Bailie [EMAIL PROTECTED] http://www.jamesbailie.com Thank you man, that was a wonderful description :) The last question though, don't you find it the least bit stupid? Thanks! Christian, Just a quick question: what are you using to look at them? If things just work, there is no problem. I don't understand why you have to do this. Are you looking at them on a windows box? I know you're emailing the list from a windows box. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Users and groups properly organized?
On Friday 03 March 2006 08:32, Kristian Vaaf wrote: Hello. Have you all ever had a look at your /etc/master.passwd and /etc/group? Stupid question. But notice the user and group identifications being thrown about as if they didn't matter. To me they do, and I would like some order in my system. Starting with my user and group identifications. Can I do something like this? find -s . -uid foo | xargs chown bar find -s . -gid foo | xargs chgrp bar To be able to arrange master.passwd like this, where UIDs and GIDs go by a chronological order? nobody:*:5:5::0:0:Unprivileged:/nonexistent:/usr/sbin/nologin root:$1$xsL49xbt$of5hvUCiVT/b/D3B70bZv1:0:0::0:0:Core:/root:/usr/loca l/bin/zsh daemon:*:1:1::0:0:System Processes:/root:/usr/sbin/nologin operator:*:2:2::0:0:Operator:/:/usr/sbin/nologin kmem:*:3:65533::0:0:KMem:/:/usr/sbin/nologin bin:*:4:4::0:0:Binaries:/:/usr/sbin/nologin tty:*:5:65533::0:0:Titty:/:/usr/sbin/nologin news:*:6:6::0:0:News:/:/usr/sbin/nologin man:*:7:7::0:0:Manuals:/usr/share/man:/usr/sbin/nologin sshd:*:101:101::0:0:Secure Shell:/var/empty:/usr/sbin/nologin www:*:102:102::0:0:World Wide Web:/usr/local/www:/usr/sbin/nologin ftp:*:103:103::0:0:File Transfer Protocol:/home/websites:/usr/sbin/nologin mysql:*:104:104::0:0:MySQL:/var/db/mysql:/sbin/nologin proxy:*:105:105::0:0:Packet Filter:/nonexistent:/usr/sbin/nologin smmsp:*:106:106::0:0:Sendmail Submission:/var/spool/clientmqueue:/usr/sbin/nologin mailnull:*:107:107::0:0:Sendmail Default:/var/spool/mqueue:/usr/sbin/nologin postfix:*:108:108::0:0:Postfix:/var/spool/postfix:/usr/sbin/nologin cyrus:*:109:109::874400:0:Cyrus:/nonexistent:/usr/sbin/nologin spamd:*:110:110::0:0:SpamAssassin:/var/spool/spamd:/sbin/nologin vscan:*:111:111::0:0:Scanner:/var/amavis:/bin/sh clamav:*:112:112::0:0:ClamAV:/nonexistent:/usr/sbin/nologin tinydns:*:113:113::0:0:TinyDNS:/nonexistent:/usr/sbin/nologin axfrdns:*:114:114::0:0:Transfers:/nonexistent:/usr/sbin/nologin dnscache:*:115:115::0:0:Cache:/nonexistent:/usr/sbin/nologin dnslog:*:116:116::0:0:Logging:/nonexistent:/usr/sbin/nologin vaaf:*:1001:0::0:0:Kristian:/home/vaaf:/usr/local/bin/zsh nomad:*:1002:1002::0:0:Hednod:/home/nomad:/usr/local/bin/zsh polvott:*:1003:1003::0:0:Thomas:/home/polvott:/usr/local/bin/zsh speak:*:1004:1004::0:0:Poetry:/home/speak:/usr/local/bin/zsh And groups equally: nobody:*:5: wheel:*:0:root daemon:*:1: operator:*:2:root kmem:*:3: bin:*:4: tty:*:5: news:*:6: man:*:7: sshd:*:101: www:*:102: ftp:*:103: mysql:*:104: proxy:*:105: smmsp:*:106: mailnull:*:107: postfix:*:108: cyrus:*:119: spamd:*:110: vscan:*:111: clamav:*:112: tinydns:*:113: axfrdns:*:114: dnscache:*:115: dnslog:*:116: nomad:*:1002: polvott:*:1003: speak:*:1004: And so on ... Maybe such order, harmony or balance or whatever will help boost system performance? Just a superstitious thought. Cheers! :) All the best, Vaaf = Try to take care of one problem at a time. If you don't look at them, they have plenty of harmony and balance, and they work. Concentrate more on 'make buildworld', you haven't gotten through that yet. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Friday 03 March 2006 08:08, Kristian Vaaf wrote: Sorry sorry sorry, I am so very sorry. http://www.home.no/hedhnta/result.txt is indeed online now. Also, strangely, my other FreeBSD 5.4-STABLE box (I have two) also errors out on build world. Different error though. Please also see http://www.home.no/hedhnta/result_2.txt The file was originally 8MB or so, so I had to cut it down a little. Basically, what I really need to do (among all these brilliant tips and tricks I've received) is to run mergemaster before I start making? One question, however, is it possible to make mergemaster install new files automatically except the ones that I've edited? That is, the ones without a FreeBSD CVS $Id$ tag? Normally, or actually in all cases, I say yes to install newer versions of all files except the ones that are part of my custom configuration. Well, that's it. Again I'm sorry for standing you guys up with the upload. All the best, Vaaf = Alright Kristian, why don't you post your supfile, make.conf, rc.conf, output of uname -a, a description of what equipment your doing this with, what you're trying to accomplish and why, what you're doing to make this come about, what you expected to happen, what did happen. How you're taking all the advice you've been given and bending it to suit yourself - which, I have to tell you, IS NOT WORKING, or you would be singing a different tune. How can you take the advice that I gave you, which has worked for me since FreeBSD 4.4, and it doesn't work for you. What about the advice that others gave you that was similar to mine and should have the same outcome. You're obviously doing something wrong. I would think you would want to successfully get through at least one buildworld sequence before screwing with things. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: plugin in firefox
This libmap.conf is what works for me, compare it with yours. It's one I spent a whole lot of time and trouble reading advice for what worked. Don === # /etc/libmap.conf for FreeBSD 6.0(6.0-BETA3 and later) and 7-current # $Id: libmap.conf-FreeBSD6,v 1.23 2005/11/13 01:46:14 nork Exp $ ### # [ALPHA SUPPORT] Flash7 with Mozilla [/usr/X11R6/lib/linux-flashplugin7/libflashplayer.so] libpthread.so.0 libpthread.so.2 libdl.so.2 pluginwrapper/flash7.so libz.so.1 libz.so.3 libm.so.6 libm.so.4 libc.so.6 pluginwrapper/flash7.so ### # Flash6 with Opera is not avilable. # Flash6 with Konqueror # SEE ALSO: http://freebsd.kde.org/howtos/konqueror-flash.php # This configuration was integrated to following one. # Flash6 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so] libpthread.so.0 pluginwrapper/flash6.so libdl.so.2 pluginwrapper/flash6.so libz.so.1 libz.so.3 libstdc++-libc6.2-2.so.3libstdc++.so.5 libm.so.6 libm.so.4 libc.so.6 pluginwrapper/flash6.so ### # Acrobat5 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/X11R6/Acrobat5/Browsers/intellinux/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Acrobat7 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/local/lib/acroread/usr/local/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Japanese Acrobat7 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/X11R6/Acrobat7/Browser/intellinux/nppdf.so] libc.so.6 pluginwrapper/acrobat.so ### # Helix RealPlayer with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/X11R6/lib/linux-mozilla/plugins/nphelix.so] libstdc++.so.5 libstdc++.so.5 libc.so.6 pluginwrapper/realplayer.so ### # Java3D # NOTE: THESE ARE SAMPLES. PLEASE SEE ALSO INSTALL MESSAGES # OF java/java3d PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libJ3D.so] libdl.so.2 pluginwrapper/java3d.so libm.so.6 libm.so.4 libnsl.so.1 pluginwrapper/java3d.so libpthread.so.0 pluginwrapper/java3d.so libc.so.6 pluginwrapper/java3d.so [/usr/local/jdk1.4.2/jre/lib/i386/libj3daudio.so] libm.so.6 libm.so.4 libnsl.so.1 pluginwrapper/java3d_snd.so libpthread.so.0 pluginwrapper/java3d_snd.so libc.so.6 pluginwrapper/java3d_snd.so [/usr/local/jdk1.4.2/jre/lib/i386/libJ3DUtils.so] libpthread.so.0 pluginwrapper/java3d.so libc.so.6 pluginwrapper/java3d.so ### # Java Advanced Imaging (JAI) API # NOTE: THIS IS A SAMPLE. PLEASE SEE ALSO INSTALL MESSAGES # OF java/jai PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libmlib_jai/libmlib_jai.so] libm.so.6 libm.so.4 libc.so.6 pluginwrapper/jai.so ### # JAI Image I/O Tools # NOTE: THIS IS A SAMPLE. PLEASE SEE ALSO INSTALL MESSAGES # OF java/jai-imageio PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libclib_jiio.so] libm.so.6 libm.so.4 libc.so.6 pluginwrapper/jai.so ### # Photo Image Print System (for EPSON bubble jet printers driver) #[/usr/local/lib/pips/] #libc.so.6 pluginwrapper/pips.so #libdl.so.2 pluginwrapper/pips.so ### #[/compat/linux/usr/lib/oracle/10.1.0.3/client/lib/libclntsh.so.10.1] #libdl.so.2 pluginwrapper/oci8.so #libm.so.6 libm.so.4 #libpthread.so.0libpthread.so.2 #libnsl.so.1pluginwrapper/oci8.so #libc.so.6 pluginwrapper/oci8.so === On Friday 03 March 2006 09:15, Antony M Rasat wrote: First try man ldconfig. An example quick-fix for your situation is perhaps ldconfig -m /usr/X11R6/lib/browser_plugins. Regards, Anthony M. Rasat PT. Kalteng Pos Press Palangkaraya - Indonesia.- -Original Message- From: Mikael Backman [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 03 Mar 2006 15:50:34 +0100 Subject: plugin in firefox I use FreeBSD 6.0 and Firefox 1.5 I think I've done all the things I
Re: plugin in firefox
On Friday 03 March 2006 10:07, Mikael Backman wrote: Thank you for your reply. But it didn't help to replace libmap.conf with your file or run ldconfig. I get the same error messages. I must be doing somthing stupid somewhere. Maybe I should use linux-firefox? ___ No, it does work with a native firefox. I've got it working on mine, I have FreeBSD 6.1 PRERELEASE, so you can get it working on yours. The big problem is, I can't remember where I found the information. It could have been on ports@, I think there was quite a discussion on there at one time. ls -l /usr/X11R6/lib/browser_plugins should look something like this: === flashplayer.xpt - /usr/X11R6/lib/linux-flashplugin6/flashplayer.xpt libflashplayer.so - /usr/X11R6/lib/linux-flashplugin6/libflashplayer.so libjavaplugin_oji.so - /usr/local/jdk1.4.2/jre/plugin/i386/ns610/libjavaplugin_oji.so nphelix.so - /usr/X11R6/lib/linux-mozilla/plugins/nphelix.so nphelix.xpt - /usr/X11R6/lib/linux-mozilla/plugins/nphelix.xpt nppdf.so - /usr/local/lib/acroread/usr/local/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so == It appears that I've got some more work to do to get Acrobat7 to work, but everything else is. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tracking Security in Ports and Base System
On Thursday 02 March 2006 13:59, Chris Hill wrote: On Wed, 1 Mar 2006, [EMAIL PROTECTED] wrote: [snip] Is my supfile correct to track security for freebsd-6.0? [snip] *default release=cvs tag=RELENG_6 [snip] As I understand it, that tag will get you the latest released version of 6.x. So today it would apply security and bugfix updates for 6.0, but after 6.1 comes out you would get 6.1, and so on. If you want to track 6.0 specifically, use RELENG_6_0. Right now there is no difference between RELENG_6 and RELENG_6_0, but later there will be. As everyone else has said, see the Handbook for definitive answers. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ This is not quite correct. tag=RELENG_6 will give you the src for 6-STABLE, which is to say FreeBSD 6.1 PRELEASE, or maybe its RELEASECANDIDATE now. tag=RELENG_6_0 will get you the sources for the 6.0 release branch, used only for security and other critical fixes. So yes, there is a difference between the two tags. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tracking Security in Ports and Base System
On Thursday 02 March 2006 16:23, Chris Hill wrote: Sorry for the misinformation! You are right, RELENG_6 is equivalent to -STABLE. I sit corrected. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] That's ok Chris. I knew you really knew what you were talking about. It just didn't quite come out the way you meant. That's happened to me often enough. After I send something, actually as I'm in motion to hit the send, I realize too late, what I said was just a little off. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making APC 500 Back UPS (basic) work with FreeBSD
Hi Mannish, I guess all you have to do is look at the first four letters in FreeBSD. One of the many reasons why I love this operating system, and it just keeps getting better, even I'm not. Don On Wednesday 01 March 2006 13:15, manish jain wrote: Hi Don, Thanks for the reply. But yes, APC is selling in India the models it can't sell anywhere else. My 500 VA Back UPS (purchased new last month) does not have any cuaa/usb interface. It's not just APC alone, there's a whole lot of companies that throw their junk in here in this country. Thankfully FreeBSD is not one of them. Regards Manish Jain Donald J. O'Neill [EMAIL PROTECTED] wrote: On Tuesday 21 February 2006 08:26, Chuck Swiger wrote: manish jain wrote: I just purchased an APC 500 Back UPS (the basic model, not the pro/smart one). It does not have any serial/usb interface. Can I get apcupsd or any other daemon to work with it so that the system automatically shuts down before backup supply runs out ? No. If your UPS isn't smart and does not have an external USB or serial port, apcupsd has nothing to work with. As best I can tell from the OP's description, and the APC website, they all have a UPS port. Go from there. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tracking Security in Ports and Base System
On Wednesday 01 March 2006 16:31, Chris Maness wrote: Thanks, I do have port audit installed. I was refering to system security. The base system + FreeBSD userland. I wanted to do this because I did get a notice from the security list today. Do I do a make buildworld, to update the system? Do I do this in /usr/src ? ___ There are a couple of ways to do it. First, did you read the announcement? It tells you what the methods are that you can use. I suggest you start there and don't pay any attention to any other nonsense. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where to place refuse file for CVSUP?
On Wednesday 01 March 2006 21:10, Jose Borquez wrote: In my ports-supfile my base=/var/db and prefix=/usr. Does that mean I should place my refuse file in /var/db/sup/ ? I am a little confused, so if anyone can help me out it would be greatly appreciated. Thanks in advance, Jose ___ Why do you want to use a refuse file? Do you understand that if you use one you are going to create upgrading problems for yourself? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Tuesday 28 February 2006 05:46, Giorgos Keramidas wrote: On 2006-02-28 12:15, Kristian Vaaf [EMAIL PROTECTED] wrote: Your buildworld sequence appears to be a little lacking - either in the detail you gave, or because some things are missing. The buildworld sequence I us is: === (I use the alternate step 10 when I run the sequence) 1)Script /home/script/buildworld/bw-?date run? 2)cd /usr/obj pwd 3)chflags -R noschg * 4)rm -rf * 5)cd /usr/src pwd make cleandir make cleandir 6)make buildworld make buildkernel KERNCONF=customconfname 7)make installkernel KERNCONF=customconfname 8)exit 9)shutdown now Enter 10) Enter to accept default location of sh alternate step 10 a) shutdown -r now Enter b) at boot menu6 c) boot -s Enter d) fsck -p Enter e) mount -u / Enter f) mount -a -t ufs Enter g) swapon -a Enter h) cd /usr/src Enter i)adjkerntz -i Enter 11) script /home/script/buildworld/iw-?date run 12) cd /usr/srcpwd 13) mergemaster -p 14) make installworld 15) mergemaster -i ?install everything? 16) exit 17)shutdown -r now === This should help a bit. Hello Don! Thank you for some good help. My make.conf only had some use.perl stuff. I added your flags. Also I've revised my sequence: cvsup -g -L 2 /etc/cvsupfile \ cd /usr/obj \ chflags -R noschg * \ rm -rf * \ cd /usr/src ; make clean \ make buildworld \ make buildkernel KERNCONF=NINJA \ make installkernel KERNCONF=NINJA \ make installworld \ mergemaster \ And am now ready to give it another go :) Until you are satisfied that everything works without any problems at all, please don't use scripts to run the builds. For instance, your script above lacks a call to ``mergemaster -p'' before the ``make buildworld'' step, which may be necessary. That's a call to 'script' to run, telling it where to put the resulting text file. While it is running, commands are given and executed. Later, if something goes wrong, or you saw something you want to check on, you have a record of what happened that you can look at, and pass on to others, if needed. Could you explain the logic of running mergemaster -p, when you have nothing to run it on. /usr/obj was blown away at the beginning of the buildworld sequence. What are you going to check at that point? Please take a look at the handbook for the sequence that things should occur in. I would say look at /usr/src/UPDATING, but their sequence doesn't include installing the kernel anymore. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Tuesday 28 February 2006 05:15, Kristian Vaaf wrote: Hello Don! Thank you for some good help. My make.conf only had some use.perl stuff. I added your flags. Also I've revised my sequence: cvsup -g -L 2 /etc/cvsupfile \ cd /usr/obj \ chflags -R noschg * \ rm -rf * \ cd /usr/src ; make clean \ make buildworld \ make buildkernel KERNCONF=NINJA \ make installkernel KERNCONF=NINJA \ make installworld \ mergemaster \ And am now ready to give it another go :) All the best, Vaaf Krisstian, There are some places in your sequence, that I think are going to give you trouble. DO NOT run this as a script, run script while you're doing it. I think you're misunderstanding some things, so, I give the procedure I use again with some comments about what is happening: cvsup -g -L 2 sup-src script /home/script/buildworld/bw-20060228 cd /usr/obj pwd /usr/obj this is confirmation I am where I want to be ls usrHey, there is something there chflags -R noschg * rm -rf * ls it's gone, great cd /usr/src pwd /usr/src I am where I want to be make cleandir whole bunch of action on the screen make cleandir run it again, yes you want to do that make buildworld make buildkernel KERNCONF=PRES1750-i386 make installkernel KERNCONF=PRES1750-i386 exit shut off script shutdown -r now at the boot menu, hit the 6 key you want to come up in single-user mode, not multi-user. If you make a mistake, reboot and do it right. If it went by too fast, use the spacebar to halt the boot process. 6 OK boot -s boots up but you're not done yet Enter full pathname of shell or RETURN for /bin/sh: Enter # fsck -p Enter # mount -u /Enter # mount -a -t ufs Enter # swapon -a Enter # script /home/script/buildworld/iw-20060228 # cd /usr/src # pwd am I where I want to be # /usr/src yes, I am # mergemaster -prun mergemaster in preinstall mode # make installworld hey, look at it go # mergemaster -i answer d to remove the old temporary directory, you don't need it anymore. answer i to everything mergemaster asks, I don't care that the recommedation is to handle it later, if you don't know what you're doing, doing anything other i is just likely to screw you up in ways you don't understand now, but you will later. # exit shutdown 'script' # shutdown -r now boot the system, come back up in multiuser mode. If you did everything right, you're done with the buildworld sequence. Again, DO NOT run this in a script. You're running the 'script' program. If you don't want to sit and watch this go on, do something else. It takes me about an hour and ten minutes to run it with an AMD64 3500+, with an amd-tbird (1.3Mhz), it takes about two hours, with a 500Mhz Pentium pIII, I run the buildworld and buildkernel part (and maybe the installkernel, usually not) overnight. I hope I caught you in time. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Tuesday 28 February 2006 08:52, Kris Kennaway wrote: On Tue, Feb 28, 2006 at 08:48:15AM -0600, Donald J. O'Neill wrote: 11) script /home/script/buildworld/iw-???date run 12) cd /usr/srcpwd 13) mergemaster -p 14) make installworld 15) mergemaster -i ???install everything? 16) exit 17)shutdown -r now === This should help a bit. Hello Don! Thank you for some good help. My make.conf only had some use.perl stuff. I added your flags. Also I've revised my sequence: cvsup -g -L 2 /etc/cvsupfile \ cd /usr/obj \ chflags -R noschg * \ rm -rf * \ cd /usr/src ; make clean \ make buildworld \ make buildkernel KERNCONF=NINJA \ make installkernel KERNCONF=NINJA \ make installworld \ mergemaster \ And am now ready to give it another go :) Until you are satisfied that everything works without any problems at all, please don't use scripts to run the builds. For instance, your script above lacks a call to ``mergemaster -p'' before the ``make buildworld'' step, which may be necessary. That's a call to 'script' to run, telling it where to put the resulting text file. While it is running, commands are given and executed. Later, if something goes wrong, or you saw something you want to check on, you have a record of what happened that you can look at, and pass on to others, if needed. Could you explain the logic of running mergemaster -p, when you have nothing to run it on. /usr/obj was blown away at the beginning of the buildworld sequence. What are you going to check at that point? Please take a look at the handbook for the sequence that things should occur in. I would say look at /usr/src/UPDATING, but their sequence doesn't include installing the kernel anymore. He means to run mergemaster -p before make installworld, as in the instructions quoted at the top of this email and in /usr/src/UPDATING. Also, the documented sequence *does* include installing the kernel, so I don't know what you mean there either. Kris He may mean that, but it's not what he said. I went by what he said. From /usr/src/UPDATING: To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make sure you have good level 0 dumps make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE [1] reboot in single user [3] mergemaster -p [5] make installworld make delete-old mergemaster [4] reboot To upgrade in-place from 5.x-stable or higher to 6.x-stable --- make sure you have good level 0 dumps make buildworld [9] make kernel KERNCONF=YOUR_KERNEL_HERE [8] [1] reboot in single user [3] mergemaster -p [5] make installworld make delete-old mergemaster -i [4] reboot I just don't see where it says make installkernel KERNCONF=YOUR_KERNEL. It used to. That's where I got my original procedure from as the handbook at the time was somewhat confusing. Now the procedure in the handbook is better. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Tuesday 28 February 2006 09:02, Giorgos Keramidas wrote: On 2006-02-28 08:48, Donald J. O'Neill [EMAIL PROTECTED] wrote: On Tuesday 28 February 2006 05:46, Giorgos Keramidas wrote: Until you are satisfied that everything works without any problems at all, please don't use scripts to run the builds. For instance, your script above lacks a call to ``mergemaster -p'' before the ``make buildworld'' step, which may be necessary. That's a call to 'script' to run, telling it where to put the resulting text file. While it is running, commands are given and executed. Later, if something goes wrong, or you saw something you want to check on, you have a record of what happened that you can look at, and pass on to others, if needed. Could you explain the logic of running mergemaster -p, when you have nothing to run it on. /usr/obj was blown away at the beginning of the buildworld sequence. What are you going to check at that point? Please take a look at the handbook for the sequence that things should occur in. I would say look at /usr/src/UPDATING, but their sequence doesn't include installing the kernel anymore. On 2006-02-28 09:52, Kris Kennaway [EMAIL PROTECTED] wrote: He means to run mergemaster -p before make installworld, as in the instructions quoted at the top of this email and in /usr/src/UPDATING. Also, the documented sequence *does* include installing the kernel, so I don't know what you mean there either. Yes, thanks Kris. Sorry for the buildworld/installworld confusion. I meant right before 'make installworld'. There are cases where 'installworld' will try to chown files to a newly added system account (i.e. `_dhcp'), but will fail, leaving a half-installed system if you don't run ``mergemaster -p'' before ``installworld''. This is why I suggested *avoiding* a scripted, unattended build and install cycle, until the OP who started this thread is comfortable that his builds and installs are indeed going to succeed. I knew where to do it, I hoped you did, but the OP might not and try to do it where you said. I agree with you on running a script. What I told the OP to do was run script and do things inside there. After I sent my response off, I took another look at what Kristian had written and decided I misunderstood what you had said. Sorry, I agree with you to not run it in a script, however, I do think he should run the program 'script' and do things from there, to at least have something to refer to when things go wrong. They will go wrong. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On Tuesday 28 February 2006 13:17, Kris Kennaway wrote: OK, but you were still confused, because mergemaster doesn't need a populated /usr/obj to do its thing (only a source tree). You can run it at any time, before during or after your buildworld. Well, I learned something new then. Thank you. make kernel KERNCONF=YOUR_KERNEL_HERE [8] [1] reboot in single user [3] mergemaster -p [5] make installworld make delete-old mergemaster -i [4] reboot I just don't see where it says make installkernel KERNCONF=YOUR_KERNEL. It used to. That's where I got my original procedure from as the handbook at the time was somewhat confusing. Now the procedure in the handbook is better. 'make kernel' = 'make buildkernel' + 'make installkernel' Kris OK, I can see that I totally about different make targets and just read that as being half a step - reading it as really being 'make buildkernel'. However, the 'make buildkernal' 'install kernel' steps are more explicit and I prefer that. Possibly I looked on it as similar to 'make world'. Maybe that's why I never said anything about it in the past. Thank you again. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Monday 27 February 2006 03:19, Ashley Moran wrote: On Saturday 25 February 2006 03:07, Donald J. O'Neill wrote: Why are you deleting the portsnap files. That's a 39 MB file that you have to download everytime you do that. The idea is to just download the patches necessary to update the ports tree after 'portsnap fetch', 'portsnap install' has been run once. After that, all you need to do is run 'portsnap fetch update', you'll get plenty of action from that. I think by now you're going to have to remove the ports tree and start over. Why not do it an easier way. I deleted the portsnap files because the incremental update didn't work, so I wanted to know if it would work from scratch. I'm not in a habit of deleting them every time I update the ports tree! For some reason though, neither works now, although they fail in (apparently) different ways. Ashley That file you were missing, lives in /var/db/portsnap/files/ , did you look there to see if it was there or not? Did you do anything to the setup of portsnap? Did you somehow, happen to install portsnap from the ports system? A dumb question I know, but it's got to be asked. did you make any changes to /etc/portsnap.conf? Just what portsnap files did you delete? How did you use portsnap, any options when you ran it? Just a funny thought: do you have defaultrouter=some IP address in /etc/rc.conf. One final thought, did portsnap ever work for you? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Sunday 26 February 2006 08:10, ptitoliv wrote: Hello Everybody, I made lots of searches on the Internet and I found something about the option net.inet.tcp.inflight.enable. If I set this value to 0, my bandwitdh problems are resolved. Does anybody knows something about this options and why can it be the origin of this problem ? Regards, Ptitoliv ___ I made some quick check, there is some information available. Most of it seems to be pretty recent. I suggest joining freebsd-stable@ as there is some questions going on about it there. You can also google for information on: net.inet.tcp.inflight.enable There may be other things to look at and good reasons to have it enabled, or disabled. Take from chapter 11 of the handbook: = 11.13.2.2 TCP Bandwidth Delay Product The TCP Bandwidth Delay Product Limiting is similar to TCP/Vegas in NetBSD. It can be enabled by setting net.inet.tcp.inflight.enable sysctl variable to 1. The system will attempt to calculate the bandwidth delay product for each connection and limit the amount of data queued to the network to just the amount required to maintain optimum throughput. This feature is useful if you are serving data over modems, Gigabit Ethernet, or even high speed WAN links (or any other link with a high bandwidth delay product), especially if you are also using window scaling or have configured a large send window. If you enable this option, you should also be sure to set net.inet.tcp.inflight.debug to 0 (disable debugging), and for production use setting net.inet.tcp.inflight.min to at least 6144 may be beneficial. However, note that setting high minimums may effectively disable bandwidth limiting depending on the link. The limiting feature reduces the amount of data built up in intermediate route and switch packet queues as well as reduces the amount of data built up in the local host's interface queue. With fewer packets queued up, interactive connections, especially over slow modems, will also be able to operate with lower Round Trip Times. However, note that this feature only effects data transmission (uploading / server side). It has no effect on data reception (downloading). Adjusting net.inet.tcp.inflight.stab is not recommended. This parameter defaults to 20, representing 2 maximal packets added to the bandwidth delay product window calculation. The additional window is required to stabilize the algorithm and improve responsiveness to changing conditions, but it can also result in higher ping times over slow links (though still much lower than you would get without the inflight algorithm). In such cases, you may wish to try reducing this parameter to 15, 10, or 5; and may also have to reduce net.inet.tcp.inflight.min (for example, to 3500) to get the desired effect. Reducing these parameters should be done as a last resort only. Note: In 4.X and earlier releases of FreeBSD the inflight sysctl variables are directly under net.inet.tcp. Their names were (in alphabetic order): net.inet.tcp.inflight_debug, net.inet.tcp.inflight_enable, net.inet.tcp.inflight_max, net.inet.tcp.inflight_min, net.inet.tcp.inflight_stab. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with IP Filter 4.1.8
On Sunday 26 February 2006 11:19, fbsd_user wrote: Since you say the same ipf rules work on your 5.3 system and you are trying to run them on 6.1-PRERELEASE, I would say the problem is 6.1-PRERELEASE. Prereleases versions and RC version are not intended for public use. They are version for people who know how to debug kernel code and help the developers test new version. It does not look like you know how to debug kernel code or you would not be asking this question. You should be using 6.0 as that's the current production version. If you still have this problem on 6.0 then repost your question. Hi all, I am having a problem with ipf after recent upgrade to 6.1-PRERELEASE. Any help would be greatly appreciated. ipf: IP Filter: v4.1.8 (416) Kernel: IP Filter: v4.1.8 Running: yes Log Flags: 0 = none set Default: pass all, Logging: available Active list: 0 Feature mask: 0xa I am trying to allow outgoing dns requests from my server to DNS server of ISP. Here is my ruleset: ipfstat -oh 0 pass out quick on lo0 from any to any 0 pass out quick on xl0 proto tcp from any to any port = domain flags S/FSRPAU keep state 1 pass out quick on xl0 proto udp from any to any port = domain keep state 0 block out log quick on xl0 all ipfstat -ih 0 pass in quick on lo0 from any to any 0 block in quick on xl0 all I tried `host www.google.com` and the connection was timed out, although there was a hit on a rule allowing 53/udp. The interesting thing is that there is another server running 5.3-STABLE with ipf v3.4.35 (336) and it has the same ruleset and everything is working just fine. Thank you for your time. ___ If you're not going to give any better advice than this, why did you give it all? I don't see anything in the OP's message that requires kernel debugging. Just some advice that he should check to see what changes have been made to ipf v4.1.8 as compared to v3.4.35 and how they affect rules. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to upgrade portsnap in freebsd 6.0?
On Sunday 26 February 2006 16:50, Steve P. wrote: pkg_delete worked, as confirmed by pkg_version does not show it anymore. However, when I attempt to make install it from ports, I get this: # make install === portsnap-1.0 portsnap now contained in the base system. *** Error code 1 Any idea? - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Steve P. [EMAIL PROTECTED] Subject: Re: How to upgrade portsnap in freebsd 6.0? Date: Sun, 26 Feb 2006 17:33:26 -0500 On Sun, Feb 26, 2006 at 05:29:26PM -0500, Steve P. wrote: I am attemping to upgrade my portsnap program as a result of this: $ pkg_version -v | grep portsnap portsnap-0.9.4 needs updating (port has 1.0) When I attempt to upgrade via portupgrade, I get this: # portupgrade portsnap /usr/local/etc/pkgtools.conf:213: warning: already initialized constant HOLD_PKG S ** Port marked as IGNORE: sysutils/portsnap: portsnap now contained in the base system I would appreciate info on how to upgrade this item. It's now contained in the base system, so the correct way to upgrade it is to use pkg_delete. Kris 2.dat Reread what Kris replied, especially the part that says: It's now contained in the base system, then read the message from when you try to make from the ports system: === portsnap-1.0 now contained in the base system. What that all means is that since you deinstalled the port, you are done. Finished. Nothing more to do. Nothing tricky needed. Just use portsnap v1.0 Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Sunday 19 February 2006 11:54, ptitoliv wrote: Mathieu CHATEAU a écrit : try this: ping -c 1000 -s 1500 IP_TO_PING wait for the 1000 ping to go trough. You should not have more than 0,5% of loss (is the servers aren't overload). If it's more or equal than 0,5%, it comes from the network (cables or switches fault). Each host would be in 100 full (via autoselect to be sure the conf is ok on the switch). I made the tests on the two boxes = 0 % packet loss. I man an other interesting test. I try to transfert between the BSD Box and a server located at home behind my 1MB/s ADSL Line. Here are the results : FreeBSD box = Workstation at home : 300 kB/s Debian box on the same network = Workstation at home : 950 kB/s. This test confirms cleraly that there is a problem with the BSD, I guess. Could it be a bug from the VR driver ? Regards, Ptitoliv ___ Not hardly. I'll bet that 950kB/s for the Debian box was the peak download speed and it didn't maintain it through the entire download. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Saturday 25 February 2006 16:30, ptitoliv wrote: Donald J. O'Neill a écrit : Not hardly. I'll bet that 950kB/s for the Debian box was the peak download speed and it didn't maintain it through the entire download. Don The Debian Box is capable to make a 5 MB/s stable connection easily. Regards, Ptitoliv Maybe, but not to the internet on an 1.5Mb/s connection. Your aDSL line is only good for at most 1.5M and that's not guaranteed to happen all the time. There are a lot of things that go on to throttle that. At home I can connect between computers at 100 Mb/s, so what. I can't connect to the internet at faster than what's capable of being supplied by the ISP. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Saturday 25 February 2006 18:00, ptitoliv wrote: Donald J. O'Neill a écrit : Maybe, but not to the internet on an 1.5Mb/s connection. Your aDSL line is only good for at most 1.5M and that's not guaranteed to happen all the time. There are a lot of things that go on to throttle that. At home I can connect between computers at 100 Mb/s, so what. I can't connect to the internet at faster than what's capable of being supplied by the ISP. I think there is a misunderstanding : boxes are not on my ADSL line but on a datacenter with 100 Mbits/s connectivity. When I say the Debian is able to make a 5 MB/s connexion it is not with my adsl line but another server located on the internet. Ptitoliv I guess you're right to say there's a misunderstanding. I was going by what you said here: === I made the tests on the two boxes = 0 % packet loss. I man an other interesting test. I try to transfert between the BSD Box and a server located at home behind my 1MB/s ADSL Line. Here are the results : FreeBSD box = Workstation at home : 300 kB/s Debian box on the same network = Workstation at home : 950 kB/s. This test confirms cleraly that there is a problem with the BSD, I guess. Could it be a bug from the VR driver ? Regards, Ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Thursday 23 February 2006 05:33, Ashley Moran wrote: I'm trying to update my ports tree on a 6.0-RELEASE/amd64 machine. I get this error: Updating from Wed Feb 15 08:30:17 GMT 2006 to Thu Feb 23 10:20:03 GMT 2006. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... /usr/sbin/portsnap: cannot open f1777c019669546744ef448c17531bdd125884253a6bf4b73f6e77001d7a0b12.gz: No such file or directory If I delete the portsnap files and try to fetch a new snapshot, I get this error instead: Fetching snapshot generated at Thu Feb 23 03:09:19 GMT 2006: f4b0454e7bce8a4decdb9190e22b8325a966e92005df5f 97% of 39 MB 118 kBps 00m08s fetch: transfer timed out Neither of my i386 boxes have this problem. Does anyone know where the issue lies? Ashley Why are you deleting the portsnap files. That's a 39 MB file that you have to download everytime you do that. The idea is to just download the patches necessary to update the ports tree after 'portsnap fetch', 'portsnap install' has been run once. After that, all you need to do is run 'portsnap fetch update', you'll get plenty of action from that. I think by now you're going to have to remove the ports tree and start over. Why not do it an easier way. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: release in cvsup supfile
On Friday 24 February 2006 20:35, Peter wrote: --- Michael P. Soulier [EMAIL PROTECTED] wrote: Hey people, I notice that in my supfile, I have this: *default release=cvs tag=. I'm using FreeBSD 5.4. Should I change the tag to 5.4-RELEASE? I don't want ports that aren't going to work on 5.4. Is that a concern? No, that's the way it should be. The Handbook is quite clear on this point: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html# CVSUP-CONFIG-VERS Well now, I think that depends on what else he's got in his supfile. He may have a problem at some point. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: release in cvsup supfile
On Friday 24 February 2006 22:35, Peter wrote: --- Nikolas Britton [EMAIL PROTECTED] wrote: On 2/24/06, Michael P. Soulier [EMAIL PROTECTED] wrote: Hey people, I notice that in my supfile, I have this: *default release=cvs tag=. I'm using FreeBSD 5.4. Should I change the tag to 5.4-RELEASE? I don't want ports that aren't going to work on 5.4. Is that a concern? No, but you need to have at least two cvsup files, one for the system and the other for ports Maybe I'm doing something wrong. I have only one file for everything: *default host=cvsup1.ca.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5 *default delete use-rel-suffix *default compress src-all doc-all ports-all tag=. It works the way you have it. However,You can split that into three files. You're following 5-STABLE, there are times when you don't want to be downloading src, unless you're planning to run buildworld cycles a lot. Instead of cvsuping ports, you could use portsnap. Once it's run the first time, it's a lot, lot faster way to upgrade the ports tree than using cvsup. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Alert : pkg_add and packages Q (do not want to compile)
On Wednesday 22 February 2006 21:59, Ow Mun Heng wrote: On Wed, 2006-02-22 at 21:36 -0600, Donald J. O'Neill wrote: On Wednesday 22 February 2006 20:59, Ow Mun Heng wrote: what about the dependency then? Ignore it? What if there are files needed by xorg-clients? eg: libXX.so.Y and which is not present in the new xterm? Since you want to replace it with a newer version, why are you worried about the dependencies. The newer version will take care of that. Of course, if you delete xterm and don't replace it, then you will have to handle the dependencies. So, I do pkg_del -f xterm and then a pkg_add -vr xterm-206_1 and it will upgrade xorg-clients if needed? If yes, then Good. No. It would only upgrade xterm. Xterm isn't dependent on xorg-clients. It's required by xorg-clients. So, that brings up a question. Are you really trying to upgrade xorg and xterm was the example you used? If that's the case, my advice would have been different. What you are trying to do is update using downloaded packages and that is going to work for you. You need to upgrade those packages using the ports system. IS or is not? Is or is not what? I don't understand what you're asking here. You need to use more than a 4 word question, of which 2 of the words are the same. It tends to be confusing. Sorry but You're confusing me too. Read your sentence update using downloaded packages and that is (?NOT?) going to work for you OK, I see what happened. I didn't put not in the sentence, as you pointed out. Since not is what I meant, I refused to see that it wasn't there, in fact my brain expected it to be there, and so when I looked at what you were asking, I saw it. Sorry. Again, I don't want to compile it. I want the binary package. It's available on the mirrors. No It's not. The port is available on the mirrors. So compile it, or leave the old one in place. lftp ftp.tw.frebsd.org lftp ftp.tw.freebsd.org:/pub/FreeBSD/ports/i386/packages-6-stable/x11 ls -l | grep xterm lrwxr-xr-x Nov 28 09:12 xterm-206_1.tbz - ../All/xterm-206_1.tbz get xterm-206_1.tbz quit tar -v -t -f xterm-206_1.tar -rw-r--r-- root/wheel 1560 2006-02-07 15:20:18 +CONTENTS -rw-r--r-- root/wheel 42 2006-02-07 15:20:18 +COMMENT -rw-r--r-- root/wheel 479 2006-02-07 15:20:18 +DESC -r--r--r-- root/wheel 8654 2006-02-07 15:20:18 +MTREE_DIRS -r--r--r-- root/wheel 1313 2006-02-07 15:19:55 man/man1/resize.1.gz -r--r--r-- root/wheel41772 2006-02-07 15:19:55 man/man1/xterm.1.gz -rwxr-xr-x root/wheel10104 2006-02-07 15:19:54 bin/resize -rwxr-xr-x root/wheel 2118 2006-02-07 15:19:54 bin/uxterm -rws--x--x root/wheel 252996 2006-02-07 15:19:54 bin/xterm -r--r--r-- root/wheel 1527 2006-02-07 15:19:55 lib/X11/app-defaults/UXTerm -r--r--r-- root/wheel 6551 2006-02-07 15:19:55 lib/X11/app-defaults/XTerm -r--r--r-- root/wheel 4232 2006-02-07 15:19:55 lib/X11/app-defaults/XTerm-color I'm proficient with the CLI, and being a long time Linux person, I'm sad to say that FreeBSD ports/packages is really confusing to me. Use Windows instead. All that takes is money. Why the sarcasm? At that moment, I had a lapse of brain power. My fingers took control of the keyboard without interference from the part of my brain which says DON'T do this. It's wrong to say something like that. And then they hit the send button and it was too late to retract it. I believe: once something is said or done, it cannot be unsaid or undone, it may be fixed, forgiven, but not forgotten. I'm sorry for the sarcasm. Available packages are not as up to date as the ports system is. Again, the package _is_ available and I've verified it. Thanks I'm sorry. You've verified the port was available. The package is not. I just checked. See above. I too do my own verification before shooting emails out to mail lists OK, I see where you were looking. I looked in the wrong place. When you look in the right place, yes, it's there. At this point, I'm going to close my ears eyes to you. You've been given advice by me and others and I thank you and them for it. Thanks again. I hope that by this time, you've received enough information to do what you wanted to do. One thought just occurred to me. What is the output from 'uname -a', mine is: FreeBSD pres1750.mylan.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Wed Feb 8 08:20:10 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PRES1750-i386 i386 You'll see that it has FreeBSD 6.1-PRERELEASE in it. If yours has FreeBSD 6.0-RELEASE in it. Then you can't install a package using pkg_add -r 'some package' for a package built for FreeBSD 6.0-STABLE. You need to have 6.0-STABLE in order to install packages built for 6.0-STABLE. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd
Re: Making APC 500 Back UPS (basic) work with FreeBSD
On Wednesday 22 February 2006 05:07, Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Donald J. O'Neill Sent: Tuesday, February 21, 2006 8:47 AM To: Chuck Swiger Cc: manish jain; freebsd-questions@freebsd.org Subject: Re: Making APC 500 Back UPS (basic) work with FreeBSD Then, thats got to be a really old, old one. I've been working (playing with actually) with computers since the color computer. I won't admit to anything further back than that. I've never seen one that didn't have some means of communication (monitoring). Not from APC anyway. APC has made a lot of older BackUPSs that didn't have the com port that date back to the Color Computer days, you just wern't paying attention. For example the BackUPS 200VA (that unit was discontinued years ago) didn't have one, neither did the BackUPS 250 and 300 VA units from that era. (all of those are discontinued) However the models that didn't have the com port back in the olden days, were all very low, low VA units, under 350VA. It wasn't until modern times that APC decided to screw it all up. Ted Bill Gates had come out with: you can't do multi-user, multitasking with an 8 bit micro-processor. Here was this inexpensive computer from Radio Shack, already on the market, that would if you used OS9, also available from Radio Shack. About that time, I decided that Bill Gates aught to pay more attention to what was going on. At that time, my concern with, and about, power backup units was somewhere between none and none. I did know what one was, what it did, and why it was desirable to have one. I just didn't really have a need for one for a long time. After all, if you shutoff the PC, who cared if the power went down - as long as you shut down before that happened. As to your last statement, I'm wondering if you were saying, in a different way: they took a nice, simple piece of equipment, that did its job well, and added capabilities to it, that in order to utilize them, required more capabilities added to the units they were supplying power backup to. Ah, I see by your later post to the list OP, given more in depth and with good advice, that's what you meant. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Alert : pkg_add and packages Q (do not want to compile)
On Wednesday 22 February 2006 19:58, Ow Mun Heng wrote: Hi, I've googled. I've read the handbook, I've read Absolute BSD and still I can't understand FreeBSD Ports/Packages esp when it comes to upgrading via packages. I'm from a Linux (gentoo linux) background so I'm not a rough diamond. Problem statement. FreeBSD-Release-6 Install from minimal cd (and packages added via FTP) i've done cvsup (cvsup -L2 -h cvsup.tw.freebsd.org /usr/share/examples/ports-supfile) pkg_version -v states that I have a few packages which can be upgraded. eg: xterm-203 needs updating (port has 206_1) $pkg_add -vr xterm pkg_add: unable to fetch 'ftp://ftp.tw.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/xt erm.tbz' by URL $pkg_add -vr x11/xterm pkg_add: unable to fetch ftp://ftp.tw.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/x11 /xterm.tbz' by URL ftp into it, it's listed via with it's suffix. (google found that for some odd reason, pkg_add doesn't add the suffix) $pkg_add -vr x11/xterm-206_1 pkg_add: package 'xterm-206_1' or its older version already installed So.. How do I install it? $pkg_delete xterm-203 pkg_delete: package 'xterm-203' is required by these other packages xorg-clients-6.8.2 pkg_delete -f xterm-203 cd /usr/ports/x11/xterm make install This will handle that problem for you. So.. That can't be done. What can I do to upgrade my packages? I've even tried sysinstall but that only lists xterm-203 as the package to install. (I suspect this is because its packagesite is packages-6-release) $export | grep -i pack declare -x PACKAGESITE=ftp://ftp.tw.freebsd.org/pub/FreeBSD/ports/i386/packages -6-stable/ In gentoo, it's a simple emerge xterm and all will be done automatically. (Granted, this is compile from source and not from binary packages, which I know can do cd /usr/ports/x11/xterm make install clean, but since FreeBSD has binary packages, I rather use that) Thanks What you are trying to do is update using downloaded packages and that is going to work for you. You need to upgrade those packages using the ports system. You really need to look at the Handbook. That's why it was written. Available packages are not as up to date as the ports system is. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
