Re: Help with Cron pleazzzzzzzzzzzz
Quoting Mike Jeays [EMAIL PROTECTED]: On October 31, 2007 07:58:21 am VeeJay wrote: I am running a status script written in Perl (*status.pl*) and want to have it *Always Running*. How can I check through CRON that status.pl is running and if NO, then start the script execution again? Please help and advise... You could write a shell script something like: A couple nits: #!/bin/bash #!/bin/sh ps -ax | grep 'status.pl' This should probably be something like ps -ax | grep 'status.pl' | grep -v grep so you don't get false positives from the grep process itself. JN if [ $q -eq 0 ] then status.pl fi grep will return zero if it finds a line containing 'status.pl', and 1 otherwise. in crontab, use * * * * * /full/path/to/script-above and it will check every minute. But a better fix would be to find the bug in status.pl that makes it crash! -- Mike Jeays http://www.jeays.ca ___ 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: port xyz: the grey screen with all the checkboxes is wrong and won't come back
On Sunday 28 October 2007, Steve Franks wrote: so where, phyisically, on the disk, does the data from make config go then? I looked in port/. after make clean, and it's as clean as fresh snow... It goes in /var/db/ports JN On 10/28/07, Erik Trulsson [EMAIL PROTECTED] wrote: On Sun, Oct 28, 2007 at 10:13:24AM -0700, Steve Franks wrote: Obviously, 'make clean' doesn't reset the configure screen. Don't know why. Because it is not designed to do that. I recall there was a faster way to fix this than 'portsnap extract' but I'll be damned if I can remember, and the ports section of the handbook doesn't even mention configure dialogs... 'make rmconfig' should remove a previously set configuration. 'make config' should display the configscreen again if it had already been set before. These are described in the ports(7) manpage (which contains lots of useful information regarding the ports system - not least the BUGS section. :-)) I'd love to add a snippet to the handbook to cover this, but the last time I made an offer like that on [EMAIL PROTECTED], it appears to have gone into dev/null... -- Insert your favourite quote here. Erik Trulsson [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: Recommended servers for FreeBSD
On Sunday 28 October 2007, Andrew Wasilczuk wrote: I'm interested to see what servers people use for FreeBSD. I used to buy the IBM xSeries x306 for firewalls and web servers and the x206 for low budget file servers, but both aren't being sold anymore. I recently got a few IBM x3200 and x3550. They are really nicely built and I hardly have any problems. However, the on-board RAID controllers (Adaptec AIC-9580W) aren't supported under FreeBSD so I fit them with 3ware 9000 series RAID cards. Although I really like those 3ware cards, it seems like an extra expense that could be avoided. What servers do you guys buy and why? I would really like to have the on-board RAID supported. Do HP servers play well with FreeBSD? If yes, which models would you recommend? Check out ixsystems.com. They build and support servers particularly for FreeBSD (and other lesser unix-like OSes) and are competitively priced. The pre-sales engineer I talked to definitely had a clue so you should be able to make a good decision before you give them any money. :) If you're more of a do-it-yourself person then servers built around supermicro boards should be reasonably compatible, but you'll want to verify the network and storage chipsets beforehand if they're onboard. HP ProLiant servers are generally decent. The onboard RAID is usually supported by the ciss driver. JN ___ 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 run vista inside freebsd
Quoting Francisco Reyes [EMAIL PROTECTED]: Frank Jahnke writes: VMs in general are a problem on Free. There is an effort to port the most recent VMware Workstation by a very good man. VMware employee? No, Orlando Bassotto, who is the programmer who did much of the work for the original VMware Workstation 3 port and kernel modules for FreeBSD. If I understand it correctly, he picked up where Vladimir Silyaev left off after porting 2. Orlando also did quite a bit of work on a Workstation 4 port for FreeBSD that reached at least alpha quality. Rsync.net code bounties and current status: http://www.rsync.net/resources/notices/2007cb.html Orlando's home page (currently blank): http://www.break.net/orlando/ JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the right next step?
On Tuesday 23 October 2007, Aliya Harbouri wrote: Hi everybody! If we've i) raised a question about a port on this list ii) sent an email to the port maintainer iii) filed a pr iv) waited ~ a month, then followed-up the pr and there's still no communication / action, what's the right next step? Is there a different list to communicate to/on for follow-up? Does your PR include a fix? If it does, make some noise about it on the freebsd-ports mailing list and include the PR number and the fact that you've not heard back from the maintainer. If it doesn't, you might still want to bring it up on -ports, but getting it fixed depends on someone volunteering to take ownership of the problem (if not outright maintainership of the port). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: resizing partitions
On Tuesday 23 October 2007, Chad Perrin wrote: I have need to alter some partition sizes on a (laptop) system I use daily, with FreeBSD 6.2-RELEASE installed. Are there tools you'd recommend for this, that should be stable and not prone to hosing up my filesystems? In particular, I probably don't need to shrink any partitions -- only grow them -- but I'm not sure how I want to handle this at this time. I worry a bit about using some Linux LiveCD's partition management tools on a FreeBSD system. Any advice would be appreciated. The best tools (IMO) for this are dump and restore. If you have external storage, storage on another system accessible by a reasonably fast network from your laptop, or dvd burner (if the example here[1] works, I haven't tried it) then this will definitely be your best option. Make your backup using dump and verify that it's complete, intact, and able to be restored from a fixit CD. Then (still from the fixit CD) blow away your existing partitions, make your new ones, and run restore to put your data back. If that option doesn't appeal to you you should still make and verify a complete backup before doing anything else. Depending on how much free space (and possibly swap) you have on your disk, you could possibly do a few different passes using growfs (in the base system) to this effect: identify next (in block order on the disk) partition to be grown. if there is no (or not enough) unpartitioned space after the growing partition, move everything from the next partition to other partitions, possibly creating temporary partitions closer to the end of the disk, or permanently relocating one or more partitions to the end of the disk, or temporarily converting your swap partition to a filesystem (be sure to not use it as swap for the duration, of course)... destroy the newly freed partition use growfs if there's room and a need, recreate the destroyed partition and restore its contents from elsewhere repeat I share your doubts about Linux utilities being able to handle UFS (esp. UFS2) filesystems correctly. JN [1] http://fuse4bsd.creo.hu/localcgi/man-cgi.cgi?dump+8 Specifically, the example command line is: /sbin/dump -0u -L -C16 -B4589840 -P 'growisofs -Z /dev/cd0=/dev/fd/0' /u ___ 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 run vista inside freebsd
On Friday 19 October 2007, Frank Jahnke wrote: On Fri, 2007-10-19 at 16:47 +0200, Frank Staals wrote: What is the status of that project if I may ask ? I did some research on it some time ago but the best I could find was that there was someone porting vmware-workstation 4.5.X to FreeBSD allthough there were quite a lot problems so there wasn't much progress it seemed. The same fellow is doing the port. I haven't corresponded with him for a while, so I can't really say what the current status is. Quite some time ago the issue was getting VMware to discuss what goes on in their kernel module (IIRC). In addition to sponsoring and contributing to the bounty for this project, rsync.net is engaged in some discussion(s) with VMware to get and keep things moving for this newest port, although status updates are a bit hard to come by (perhaps intentionally). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 1 TB data copy
Quoting Bill Moran [EMAIL PROTECTED]: In response to Monah Baki [EMAIL PROTECTED]: Hi all, We have a windows 2003 server and 1 freebsd 6.2 server. The 2003 server supports USB 1 while the freebsd supports usb 2. We went and purchased an external 1 TB usb 2 harddrive. Our objective is to copy 700GB worth of data from the windows to the freebsd server then take the external harddive to a remote client who runs windows 2003 and then copy the data back to the windows server. The throughput of copying the data from windows to the usb attached to it was ridiculous, more than 12 hours to copy 60GB of data. I tried copying a 1GB file from windows to the usb attached to the freebsd and it took less than 5 minutes, but ofcourse when I tried to mount the usb back to the windows box I could not see the 1GB file that I copied. How can use the freebsd as the destination copy since it has a much better throughput and at the same time have the windows box see the 600GB file that was copied once I attach the usb harddrive to it. I expect the filesystem is the problem. Windows doesn't understand UFS. FAT has been the traditional solution to this, since just about every OS understands FAT, but I don't believe FAT will support files as large as you're working with. I'm not completely up to speed with FreeBSD's NTFS support. Last I looked at it, it was experimental and there were warnings everywhere. I assume it's improved since then (~3 years ago) but can't say with authority. However, I think that's your only option. Luckily, since you're just using the USB drive to move a file, and can keep it safe in another location until you're sure it transferred safely, this shouldn't be too risky. I would format the drive with the Windows machine and make it NTFS, then work with the FreeBSD mount options to get FreeBSD to mount it. Have a look at mount_ntfs. I agree with your approach but, mount_ntfs is still essentially read-only. Fortunately ntfs-3g has been ported (using FUSE), so the OP should be able to use that instead. See the sysutils/fusefs-ntfs port. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Procmail not recognising /etc/procmailrc?
Quoting Lisa Casey [EMAIL PROTECTED]: Hi, This is kind of off topic for this list, but I know a lot of FreeBSD Admins use Procmail, so hopefully someone here can help. I'm running procmail 3.22 on FreeBSD. I verified that procmail does work on my system by following the testing your procmail installation in the ii Procmail Quick Start. Procmail worked flawlessly in processing a .procmailrc file in my home directory. Problem is, I can't seem to get it to do what is in my /etc/procmailrc file. Either procmail doesn't recognise the /etc/procmailrc file, or my syntax in that file is wrong. As with most FreeBSD ports, procmail on FreeBSD looks under /usr/local/etc for its configuration information. Just use that path instead of /etc in any non-FreeBSD documentation you encounter and you should be fine. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: setting up a cvsup mirror
Quoting Johan Hendriks [EMAIL PROTECTED]: I want to setup a local cvsup mirror on my local machine (someone told me if you do it right you don't need to hand apply uncommitted patches) what do I need to do this? Google, 3rd hit: http://www.onlamp.com/pub/a/bsd/2001/08/30/Big_Scary_Daemons.html Cheers, Pieter de Goeje _ I can not install the port on Current. It errors out with the following message: === cvsup-mirror-1.3_6 is an interactive port. *** Error code 1 Stop in /usr/ports/net/cvsup-mirror. Do I need to set something in /etc/make.conf? I have installed the cvsup-without-gui port Un-define BATCH, perhaps? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem compiling kdegraphics (exr problem?)
Quoting Will Wainwright [EMAIL PROTECTED]: I'm having some trouble getting kdegraphics to update. I use portmanager to keep my ports updated. Usually this works well, but the past couple of days portmanager did have problems with the latest OpenEXR update. As to my problem with kdegraphics, here is what I know. It compiles until this point: gmake[3]: Entering directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins/exr' /usr/local/bin/moc ./kfile_exr.h -o kfile_exr.moc if /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I../.. -Drestrict= -I/usr/local/include -I/usr/local/include -I/usr/local/include/OpenEXR -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kfile_exr.lo -MD -MP -MF .deps/kfile_exr.Tpo -c -o kfile_exr.lo kfile_exr.cpp; \ then mv -f .deps/kfile_exr.Tpo .deps/kfile_exr.Plo; else rm -f .deps/kfile_exr.Tpo; exit 1; fi kfile_exr.cpp: In member function `virtual bool KExrPlugin::readInfo(KFileMetaInfo, uint)': kfile_exr.cpp:229: error: `hasutcOffset' was not declared in this scope kfile_exr.cpp:229: warning: unused variable 'hasutcOffset' kfile_exr.cpp: At global scope: kfile_exr.cpp:165: warning: unused parameter 'what' gmake[3]: *** [kfile_exr.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins/exr' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/graphics/kdegraphics3. *** Error code 1 At which point the build fails. I'm not sure if this is a problem with KDE or if there is still something wrong with my install of OpenEXR. Any advice as to how to proceed? I ran in to this myself last night. I corrected it by taking the following steps. I use portupgrade so I won't give specific commands: Make sure your ports tree is up-to-date. Force-uninstall graphics/OpenEXR. Force-reinstall graphics/ilmbase. Re-install (manually if necessary) graphics/OpenEXR. Fix up dependencies. Continue with other upgrades. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem compiling kdegraphics (exr problem?)
Quoting John Nielsen [EMAIL PROTECTED]: Quoting Will Wainwright [EMAIL PROTECTED]: I'm having some trouble getting kdegraphics to update. I use portmanager to keep my ports updated. Usually this works well, but the past couple of days portmanager did have problems with the latest OpenEXR update. As to my problem with kdegraphics, here is what I know. It compiles until this point: gmake[3]: Entering directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins/exr' /usr/local/bin/moc ./kfile_exr.h -o kfile_exr.moc if /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I../.. -Drestrict= -I/usr/local/include -I/usr/local/include -I/usr/local/include/OpenEXR -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kfile_exr.lo -MD -MP -MF .deps/kfile_exr.Tpo -c -o kfile_exr.lo kfile_exr.cpp; \ then mv -f .deps/kfile_exr.Tpo .deps/kfile_exr.Plo; else rm -f .deps/kfile_exr.Tpo; exit 1; fi kfile_exr.cpp: In member function `virtual bool KExrPlugin::readInfo(KFileMetaInfo, uint)': kfile_exr.cpp:229: error: `hasutcOffset' was not declared in this scope kfile_exr.cpp:229: warning: unused variable 'hasutcOffset' kfile_exr.cpp: At global scope: kfile_exr.cpp:165: warning: unused parameter 'what' gmake[3]: *** [kfile_exr.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins/exr' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7/kfile-plugins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/kdegraphics3/work/kdegraphics-3.5.7' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/graphics/kdegraphics3. *** Error code 1 At which point the build fails. I'm not sure if this is a problem with KDE or if there is still something wrong with my install of OpenEXR. Any advice as to how to proceed? I ran in to this myself last night. I corrected it by taking the following steps. I use portupgrade so I won't give specific commands: Make sure your ports tree is up-to-date. Force-uninstall graphics/OpenEXR. Force-reinstall graphics/ilmbase. Re-install (manually if necessary) graphics/OpenEXR. Fix up dependencies. Continue with other upgrades. Or better yet, follow the (similar but not identical) directions in ports/UPDATING, which I didn't bother to check recently until now. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Tomcat
Quoting Ivan \Rambius\ Ivanov [EMAIL PROTECTED]: On 9/28/07, Yance Kowara [EMAIL PROTECTED] wrote: Would you mind explaining the difference between sun-jdk and diablo jdk? From the point of view of the end user or even the Java programmer there is no differences - both jdk's offer the same public APIs, compilers, runtime environments, etc. The differences are in the internal implementaions. Sun JDK is developed by Sun Microsystem. They officially offer binary downloads for Windows, Solaris and Linux, as well the source code (for their JDK). A FreeBSD port for Sun JDK does exists, but it is not made by Sun. Take a look at that page: http://www.freebsd.org/java/ Diablo JDK (I think) is another implementation of JDK - see http://freebsdfoundation.org/downloads/java.shtml. This is not correct. The Java packages available from the FreeBSD Foundation are based on the same codebase as any other 1.5 JDK or JRE from Sun. The difference is that they are available as certified binary packages. See the original announcement for all the details: http://freebsdfoundation.org/press/20060405-PRrelease.shtml then consider donating to the Foundation to support ongoing and future porting and certification work for Java on FreeBSD. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gstripe during install
On Friday 07 September 2007, n j wrote: Hello, I have a machine which has 2 (identical) hard disks. I would like to create RAID-0 GEOM stripe (gstripe(8)) to merge these 2 disks into 1 disk with larger capacity and install FreeBSD on it. There is this article (http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html) which shows how to setup RAID-1 gmirror during install suggesting that what I'm trying to accomplish is possible. However, I haven't found any pointers to doing same with gstripe. If anyone knows how to do this and if it's possible at all, please share. On the other hand, if setting up gstripe during install is not possible, is it possible to install FreeBSD on one disk and later setup the gstripe to use the entire capacity? Or, since performance is not a key issue here, maybe use gconcat? Any input is appreciated! I assume you're aware of all the caveats that go along with using RAID-0 (no redundancy, twice as likely to fail, etc.). You can't use the method Dru outlines to create a gstripe volume since you can't add drives to a gstripe after it's created. Also you can't boot from a gconcat volume like you can from a gmirror volume. It _is_ possible to use gconcat followed by growfs to add drives to an existing volume, but I'm not sure it would be possible to boot from such a volume. If it were me, I would a small (for some definition of small considering your disk space and software needs) partition on the first disk and install everything to that. After the system is up, create an identical partition on the second disk and set up gmirror between the two (see below). This volume would house either the entire OS or just the root partition at your option, but it needs to be large enough to house at least a minimal install of the OS temporarily. I'd then create additional partitions using the remaining space on each disk and turn those into a new, blank gstripe volume. If you don't want the whole OS on your mirror, you could then move /usr, etc over to the stripe volume (but you don't have to). See this link for a more fail-safe way to create a mirror on an already-running system than Dru's howto: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html The key difference is that the handbook version has you create a new, blank mirror and move everything to it (using dump/restore) instead of converting an existing volume over to a mirror directly and running the risk of the last sector getting clobbered by the GEOM metadata. On a whole disk the last sector is _generally_ not used by the filesystem but it's best to be sure, and the above statement is NOT true for partial-disk slices and/or partitions, especially if their sizes are round (for some power of two) numbers. You'll also want to get at least minimally familiar with the fdisk, bsdlabel and newfs commands. Good luck and feel free to ask additional questions. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gstripe during install
On Friday 07 September 2007, John Nielsen wrote: I assume you're aware of all the caveats that go along with using RAID-0 (no redundancy, twice as likely to fail, etc.). You can't use the method Dru outlines to create a gstripe volume since you can't add drives to a gstripe after it's created. Also you can't boot from a gconcat volume like you can from a gmirror volume. I meant to say you can't boot from a _gstripe_ volume.. Not sure about gconcat but I mentioned that in the following paragraph. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dump + GZIP
On Thursday 16 August 2007, Grant Peel wrote: Can I safely pump a filesystem dump through gzip during the dumping process?, or di I need to create the dump first then gzip it after? I do it all the time: dump -f - ... | gzip date_filesystem.dump.gz or with bzip2: dump -f - ... | bzip2 date_filesystem.dump.bz2 Does zipping the dumps cause any headaches at restore time? Nope: bzcat date_filesystem.dump.bz2 | restore ... -f - (I currently dump 5 servers worth of data to a raid 5 array, and am about 20% away from running out of disk space). Does gzipping a file give a decent compression ratio? Depends on what you're compressing, but generally yes. bzip2 generally compresses better but takes a lot more time, CPU and memory at compression time. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lagg(4) - configuration for /etc/rc.conf?
On Wednesday 08 August 2007 09:58:58 am Ewald Jenisch wrote: Thanks to the hints posted here about failover redundancy I've successfully set up lagg(4) in order to have a machine with redundant failover connection to two switches. The only thing that's missing is the correct configuration in /etc/rc.conf. Here's what I've got so far in my rc.conf: defaultrouter=192.168.9.1 if_lagg_load=YES This belongs in /boot/loader.conf, not /etc/rc.conf. ifconfig_bge0=UP ifconfig_bge1=UP ifconfig_lagg0=create This should be: cloned_interfaces=lagg0 Once you fix those two things you should be in good shape. JN ifconfig_lagg0=laggproto failover laggport bge0 laggport bge1 192.168.9.5 netmask 255.255.255.0 The problem is that once the machine boots the lagg0 interface doesn't get created/activated; a ifconfig done after booting shows that no lagg interface is there, but the physical interfaces (bge0, bge1) are UP. Only after I manually enable the lagg-interface it with ifconfig lagg0 create the interface is created but then it automagically gets the right IP-address and routing also works: # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:08:02:47:0d:56 media: Ethernet autoselect (1000baseTX full-duplex) status: active lagg: laggdev lagg0 bge1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:08:02:47:0d:56 media: Ethernet autoselect (100baseTX full-duplex) status: active lagg: laggdev lagg0 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet 192.168.9.5 netmask 0xff00 broadcast 192.168.9.255 ether 00:08:02:47:0d:56 media: Ethernet autoselect status: active laggproto failover laggport: bge1 flags=4ACTIVE laggport: bge0 flags=5MASTER,ACTIVE I've tried numerous variations of the ifconfig_lagg0-lines in /etc/rc.conf above - with or without create etc. - to no extent. Upon boot the lagg-interface remains down basically cutting of the box from the network until I enable the lagg-interface from the console :-(. Thanks much in advance for any clue, -ewald ___ 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: Iomega Ditto Max Pro
On Saturday 04 August 2007, jbarnet wrote: Hello, I have this drive: Iomega Ditto Max (Professional) Model: IO 1000 - PX It has a parallel port interface. Included are a bunch of 5/10 Gig [uncompressed/compressed] tapes and also a few 3.5/7 Gig [uncom/com] tapes. I was wondering if this would be usable under the FreeBSD? Version: FreeBSD 6.2-STABLE i386 The vpo(4) manpage does not mention this device, but if it uses the same parallel-to-SCSI interface as one of the other Iomega products listed then it might work. vpo is not part of the default GENERIC kernel so you'd either need to load it as a module or build a custom kernel to include it. You'll also need scbus(4) and sa(4), but they are included in GENERIC. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CRT value Absurd
On Thursday 02 August 2007 02:13:46 pm Subhro wrote: Hello Folks, Recently I got a HP nc6400 notebook for myself and decided to install FreeBSD on this. My system boots up fine but I am repeatedly getting Errors from ACPI. I am repeatedly getting acpi_tz0: _CRT value is absurd, ignored (256C) How can I solve this problem? One of my desktops started doing this after a -STABLE update a few weeks ago. I worked around it by setting hw.acpi.thermal.polling_rate=0 in /etc/sysctl.conf. For a one-time change obviously you can just run # sysctl hw.acpi.thermal.polling_rate=0 JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xf86 madness - stop installing drivers
On Tuesday 31 July 2007 02:37:36 pm Noah wrote: Hi, I am wondering if there is an easy way to stop installing all of the xf86 input an video drivers listed below. Sure, just uninstall the xorg metaport, the xorg-drivers metaport, and any of the driver ports you listed that you're not interested in. You can use pkg_delete or similar. To actually _prevent_ the packages from being installed, you should avoid installing either metaport above or anything that depends on them. If you felt so inspired, you could make your own xorg-drivers-custom metaport, have it depend on only the drivers you're interested in, mark it as conflicting with the vanilla xorg-drivers port, and use it as a replacement. You'd probably have to run pkgdb -F a lot (if you use portupgrade) or take other provisions to repair the dependencies, but it could be done. On the whole though, what are you trying to gain? X.org and XFree86 on FreeBSD have always defaulted to installing all of the available drivers. It's just more visible now that each one has its own port in the post Xorg-7.0 world. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Custom builds from ports
On Tuesday 31 July 2007 12:16:32 pm CyberLeo Kitsana wrote:
Rakhesh Sasidharan wrote:
On Sun, July 29, 2007 01:37, N.J. Mann wrote:
In message [EMAIL PROTECTED], CyberLeo Kitsana wrote:
Is there a way to specify which ports certain options are to be applied
to, without having to craft custom command lines and build ports
individually?
Is ports-mgmt/portconf what you are looking for?
I didn't know about ports-mgmt/portconf (will check it out now) but what
I use is the make.conf file.
This blog post
(http://blog.innerewut.de/articles/2006/01/14/upgrading-ports-and-preserv
e-mak e-options) is what enlightened me. And here's how the application
specific bits of my make.conf file looks:
.if ${.CURDIR:M*/shells/bash}
WITH_STATIC_BASH=yes
PREFIX=/
.endif
.if ${.CURDIR:M*/print/cups}
CUPS_OVERWRITE_BASE=yes
NO_LPR=yes
WITH_CUPS=yes
.endif
.if ${.CURDIR:M*/databases/mysql50-*}
# these two options supposedly give a speed boost
BUILD_OPTIMIZED=yes
BUILD_STATIC=yes
.endif
As you can see in the shells/bash case, I can even pass along PREFIX etc
arguments.
Hope that helps.
That's exactly what I was looking for.
Also, if you use portupgrade there's a MAKE_ARGS section
of /usr/local/etc/pkgtools.conf.
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Downgrading from current
On Sunday 29 July 2007 09:42:01 pm Ross Penner wrote: I recently upgraded my system from stable to current to try and take advantage of some of wireless features offered. Unfortunetly, things didn't work out as well as I'd like to and I want to downgrade. Reading online, it seems that downgrading isn't supported and it's probably best to just reinstall the system. This seems reasonable enough to me but I have a couple problems I need to address first. I have a lot of data on my /usr partition that I would rather not have to backup and then readd to the system. is there a way I can reinstall and leave parts of the file system intact? I assume that I can use the same partitions but I'm worried that reinstalling will clean the partitions. Obviously take good backups before you try anything. I recently downgraded one of my machines using sysinstall's binary upgrade feature. Goes something like this: Download the .iso image for the relase or snapshot you'd like to downgrade to. (Skip if you already have a CD.) Use mdconfig to create a device entry for your .iso image. (Skip if you already have a CD.) Mount the cd image to /cdrom or /mnt. (Skip if you already have a CD.) Run /usr/sbin/sysinstall (from your running system, don't boot from a CD). Go to the options screen and set the Release name to match the .iso image or CD you're using. e.g. 6.2-RELEASE or 6.2-STABLE-200706. Go back to the main menu and choose the Upgrade option. Follow the prompts. If you're using a CD then use the CD media option. If you're using a .iso image use the local directory option and give it the directory where you mounted the image. Be sure to install the src distribution. Check that the sources in /usr/src match what just got installed and then run mergemaster to fix up /etc. Reboot. These instructions come with no warranty, your mileage may vary, not responsible for items left in vehicle or data loss, etc etc. Good luck though. :) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RALUS for Linux - authentication failing
I'm trying to get the latest Linux remote agent for Backup Exec to run on a FreeBSD-amd64 machine. The exact version is RALUS-11d.7170.2, although I suspect any 10.0 - 11d version would be the same. After trying a few things (including installing on a real Linux host) I was able to identify and extract the files containing the two rpm's that are actually installed. I ran those through rpm2cpio and got a simple directory layout. I duplicated the directory structure and config file from the Linux host and ran the main executable. (The init script tries (and fails, even after I fixed all the hardcoded paths) to do some housekeeping, but none of it is necessary for the thing to actually run.) The executable seems to run okay and the host even shows up as a Unix target on the (Windows) Backup Exec server, but I'm unable to authenticate, preventing me from doing any backups. I've used the agent on other Linux and Solaris hosts successfully, and it generally just takes the OS root (or other user in the beoper group) password, without a need to set any ralus-specific passwords anywhere. Has anyone else gotten this to work on FreeBSD? If not, can anyone tell me (or speculate) what method the agent uses / might use to authenticate users? I was able to enable logging, so I know it sees the login attempt but it can't verify the password: 18006 Thu Jul 26 11:51:16 2007 : LogonUser failed for user: root because LogonUser: The input password does not match the OS password Thanks for any input (well, anything other than don't do that :) ). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RALUS for Linux - authentication failing
On Thursday 26 July 2007 12:18:52 pm John Nielsen wrote: I'm trying to get the latest Linux remote agent for Backup Exec to run on a FreeBSD-amd64 machine. The exact version is RALUS-11d.7170.2, although I suspect any 10.0 - 11d version would be the same. After trying a few things (including installing on a real Linux host) I was able to identify and extract the files containing the two rpm's that are actually installed. I ran those through rpm2cpio and got a simple directory layout. I duplicated the directory structure and config file from the Linux host and ran the main executable. (The init script tries (and fails, even after I fixed all the hardcoded paths) to do some housekeeping, but none of it is necessary for the thing to actually run.) The executable seems to run okay and the host even shows up as a Unix target on the (Windows) Backup Exec server, but I'm unable to authenticate, preventing me from doing any backups. I've used the agent on other Linux and Solaris hosts successfully, and it generally just takes the OS root (or other user in the beoper group) password, without a need to set any ralus-specific passwords anywhere. Has anyone else gotten this to work on FreeBSD? If not, can anyone tell me (or speculate) what method the agent uses / might use to authenticate users? I was able to enable logging, so I know it sees the login attempt but it can't verify the password: 18006 Thu Jul 26 11:51:16 2007 : LogonUser failed for user: root because LogonUser: The input password does not match the OS password I ended up going with the legacy agent for Linux for now. The install script actually ran okay except for installing the startup script (which I had to edit anyway), and the agent seems to be running fine. It uses its own password and authentication so I didn't have the problem I did with the modern RALUS. I'm still open to any input but I probably won't be spending more time on getting the modern agent working if I don't have any new ideas. Thanks, JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RALUS for Linux - authentication failing
On Thursday 26 July 2007 03:08:55 pm Jonathan Horne wrote: are you sure that all the executables are all running correctly? for my veritas netbackup agent, 'ldd' revealed that i was missing some older .so files, which once i took care of those, the whole thing ran like clockwork for me. The only executable that needs to run AFAICT is beremote, and I see in its log output where it is contacting the backup server and attempting to process login attempts. I also see a list of libraries in its startup output, some of which it says were loaded and many of which could not be loaded. However all of the library names begin libbe (backup exec, I assume), and the ones that are loading are present in the ralus directory. file(1) identifies beremote as a dynamically linked Linux ELF executable, but ldd(1) can't read it. I don't appear to have a Linux ldd program installed, would that help? Thanks for the input. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Drive concatenation...Which tool to use?
On Wednesday 25 July 2007, Josh Tolbert wrote: I've got a friend that wants to use a FreeBSD box for a file server. He has a huge pile of drives of different sizes, but he wants them all as one big file system. What's the appropriate tool for this? gstripe doesn't seem like it'd be smart to use with differently-sized drives. Is gvinum up to snuff and stable enough to use? Is ccd still supported? What would be your tool of choice? gconcat, perhaps? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs 6.2-release and w2k3 standard r2
On Tuesday 10 July 2007, Philip M. Gollucci wrote: Hi, I've done lots of googling and I get lots of solutions, but they don't work. I can smbclient to this share just fine: magneto# smbclient -U pgollucci glactus\\unix Password: Domain=[RIDERWAY] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ ls . D0 Fri Jul 6 20:13:59 2007 .. D0 Fri Jul 6 20:13:59 2007 55750 blocks of size 8388608. 55498 blocks available BUT BUT mount_smbfs -W Riderway -I A.B.C.D //[EMAIL PROTECTED]/unix /x1/backups-cdp Password: mount_smbfs: unable to open connection: syserr = Connection refused The share is valid, I can even write to it via smbclient. Does any one have any great ideas ? I've tried with and with -I, -W and replacing HOST with ip out-right. IIRC, Win2k3 only uses port 445 for smb/cifs by default, and our mount_smbfs can only use 139 (or thereabouts :) ). It would be nice if mount_smbfs were updated to work more easily with newer versions of Windows, but in the meantime it should be possible to tell the Windows server to also accept connections on the old port. Exactly how I don't remember ATM, but I've done it before. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs 6.2-release and w2k3 standard r2
On Tuesday 10 July 2007, John Nielsen wrote: On Tuesday 10 July 2007, Philip M. Gollucci wrote: Hi, I've done lots of googling and I get lots of solutions, but they don't work. I can smbclient to this share just fine: magneto# smbclient -U pgollucci glactus\\unix Password: Domain=[RIDERWAY] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ ls . D0 Fri Jul 6 20:13:59 2007 .. D0 Fri Jul 6 20:13:59 2007 55750 blocks of size 8388608. 55498 blocks available BUT BUT mount_smbfs -W Riderway -I A.B.C.D //[EMAIL PROTECTED]/unix /x1/backups-cdp Password: mount_smbfs: unable to open connection: syserr = Connection refused The share is valid, I can even write to it via smbclient. Does any one have any great ideas ? I've tried with and with -I, -W and replacing HOST with ip out-right. IIRC, Win2k3 only uses port 445 for smb/cifs by default, and our mount_smbfs can only use 139 (or thereabouts :) ). It would be nice if mount_smbfs were updated to work more easily with newer versions of Windows, but in the meantime it should be possible to tell the Windows server to also accept connections on the old port. Exactly how I don't remember ATM, but I've done it before. I hate not remembering things, so I just verified this on a Windows Server 2003 box I have access to. This feature (listening on port 139) is tied to NETBIOS over TCP/IP. Make sure it's enabled on the WINS tab of the Advanced TCP/IP settings dialog for the interface. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: password failure- after mergmaster
On Monday 09 July 2007 04:06:01 pm Jean-Paul Natola wrote: OOOPSS- I got mergemaster to run- but now that the system restarted the root password and my password are invalid- I can ONLY start in single user mode- I still do have level 0 dump of 5.4 on my network is this my only option ? It's always wise to back up /etc before running mergemaster to cover just this type of mistake. In this case I'm guessing you replaced your /etc/master.passwd with the default one. From single-user mode, set the root password using the passwd utility. You will probably need to re-add your user account and any others that aren't part of the system default. I would grab /etc/master.passwd from your backup and do a line-by-line comparison with the file currently installed on your system. When re-adding users, be sure to use the same UID's and GID's so that file permissions will be correct. See man pw for details. Alternatively, you could replace /etc/master.passwd with the copy from your backup and run mergemaster again. This time pay attention and actually merge the file. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Verizon VZAccess and FreeBSD
On Thursday 05 July 2007 11:20:52 am Matt Juszczak wrote: Hi all, I have a blackberry with Tethering support. The only thing keeping me from switching fully over to FreeBSD from Windows is that I use VZAccess Manager with my Blackberry to connect to the net from wherever I am. I'm just wondering if this is supported in FreeBSD at all (and if so, is the high speed EVDO also supported? I know some that have gotten it working as a modem at slower speeds). For my V620 card, the VZaccess manager is as unnecessary in FreeBSD as it is in Windows. Just create a ppp entry to dial #777 and it should connect (just like only using the Dial-up Networking item in Windows works just fine). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't build /graphics/poppler-qt after recent cvsup [FIXED]
On Tuesday 03 July 2007 04:09:37 pm John Nielsen wrote: [cc-ing gnome@ as port maintainer] On Tuesday 03 July 2007 03:52:22 pm Dan Nelson wrote: In the last episode (Jul 03), [EMAIL PROTECTED] said: I'm having an odd proble getting poppler-qt to build after my latest cvsup. I use portmanager to update my ports and when I ran it today I got the following failure as the poppler-qt port was doing it's configure: ---Snip-- checking for Qt headers... /usr/local/include checking for Qt libraries... /usr/local/lib test: xyes: unexpected operator configure: error: Qt development libraries not found It looks like QT's autoconf test is buggy. work/poppler-0.5.4/configure script, line 25757: if test x$have_qt4 == xyes; then == is not a valid comparison operator for the test command. It must be =. I was having the same problem as the OP. After Dan's post I did a make patch, then modified the configure script replacing two instances of == with = on these two lines: 25851:if test x$have_qt == xyes; then 26033:if test x$have_qt == xyes; then After that I was able to make and install the port. gnome@ folks, should I submit a PR or will you guys just take this upstream directly? Thanks ahze for commiting a fix for this. poppler-qt-0.5.9_2 now builds and installs without any modifications on my system. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_lagg(4) and rc.conf
On Tuesday 03 July 2007 02:35:16 pm Michael W. Lucas wrote: I'm trying to configure a lagg(4) interface out of rc.conf. FreeBSD doesn't want to initialize the interface at boot. I'm obviously missing some little thing. I'm successfully loading if_lagg into the kernel, so that's not the problem. I can configure the interface at the command line if I do a ifconfig lagg0 create and then enter the configuration, but there doesn't seem to be a rc.conf flag to tell the system to create an interface? Here's my rc.conf for these interfaces: ifconfig_em3=up ifconfig_em7=up ifconfig_lagg0=laggproto lacp laggport em3 laggport em7 10.184.1.19 netmask 0x I haven't played with if_lagg yet, but you should be able to use the cloned_interfaces knob in /etc/rc.conf to create the interface. e.g.: cloned_interfaces=lagg0 ifconfig_em3=up ifconfig_em7=up ifconfig_lagg0=laggproto lacp laggport em3 laggport em7 10.184.1.19 \ netmask 0x if_lagg(4) mentions this briefly (at the end before the examples), and if_bridge(4) has a pretty good example (you'd substitute lagg for bridge, of course). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't build /graphics/poppler-qt after recent cvsup
[cc-ing gnome@ as port maintainer] On Tuesday 03 July 2007 03:52:22 pm Dan Nelson wrote: In the last episode (Jul 03), [EMAIL PROTECTED] said: I'm having an odd proble getting poppler-qt to build after my latest cvsup. I use portmanager to update my ports and when I ran it today I got the following failure as the poppler-qt port was doing it's configure: ---Snip-- checking for Qt headers... /usr/local/include checking for Qt libraries... /usr/local/lib test: xyes: unexpected operator configure: error: Qt development libraries not found It looks like QT's autoconf test is buggy. work/poppler-0.5.4/configure script, line 25757: if test x$have_qt4 == xyes; then == is not a valid comparison operator for the test command. It must be =. I was having the same problem as the OP. After Dan's post I did a make patch, then modified the configure script replacing two instances of == with = on these two lines: 25851:if test x$have_qt == xyes; then 26033:if test x$have_qt == xyes; then After that I was able to make and install the port. gnome@ folks, should I submit a PR or will you guys just take this upstream directly? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Calendar for 7.0-RELEASE
On Friday 29 June 2007 09:43:12 am Oliver Herold wrote: On Fri, Jun 29, 2007 at 01:30:45PM +0200, Jose Luis Alarcon Sanchez wrote: Please, anyone knows when is planned (aprox.) FreeBSD 7.0-RELEASE will be available?. http://www.freebsd.org/releng/ Also http://www.freebsd.org/releases/7.0R/schedule.html, although there's not much on it yet. The code freeze has definitely started though, so I expect the above links will be updated fairly regularly in the coming weeks. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade from 5.5 to 5.5
On Thursday 21 June 2007 03:18:32 pm Jean-Paul Natola wrote: I just finished ( what I thought was an upgrade) to 6.0 Only to find after I rebooted that I was still at 5.5 I did it via sysinstall- it said upgrade successful reboot - And when I did I was back at 5.5 Obviously , I missed something just not sure what/where Any help would be greatly appreciated Since you mention sysinstall I'm assuming you were attempting a binary upgrade. Please provide more details, including (but not limited to): Did you boot from an install CD (or other media) or did you run sysinstall directly from the running system? What media did you select from sysinstall? (FTP, CDROM, etc) Did you go in to the sysinstall options screen and change the version string (or notice what it was)? If you did use a CD, where did it come from and what version is it? (followup: are you sure?) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade from 5.5 to 5.5
On Thursday 21 June 2007 03:44:48 pm Jean-Paul Natola wrote: On Thursday 21 June 2007 03:18:32 pm Jean-Paul Natola wrote: I just finished ( what I thought was an upgrade) to 6.0 Only to find after I rebooted that I was still at 5.5 I did it via sysinstall- it said upgrade successful reboot - And when I did I was back at 5.5 Obviously , I missed something just not sure what/where Any help would be greatly appreciated Since you mention sysinstall I'm assuming you were attempting a binary upgrade. Please provide more details, including (but not limited to): Did you boot from an install CD (or other media) or did you run sysinstall directly from the running system? What media did you select from sysinstall? (FTP, CDROM, etc) Did you go in to the sysinstall options screen and change the version string (or notice what it was)? If you did use a CD, where did it come from and what version is it? (followup: are you sure?) # I upgraded from the running system, I used passive ftp , I selected # minimal install, and just chose a an ftp server to download from In that case sysinstall got its version string from the running system (5.5), so that's what it downloaded and installed. Try it again, but this time go to the Options menu (from the main Sysinstall menu) and change the release name to what you really want. I would suggest 6.2-RELEASE unless you have a reason for wanting 6.0. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multi Monitors (More Than Two)
On Wednesday 20 June 2007 01:27:01 am Andrew Pantyukhin wrote: On 6/20/07, Garrett Cooper [EMAIL PROTECTED] wrote: Adam St. George wrote: Will FreeBSD be able to have a setup for 16 monitors? Id love to finaly, and fully switch to FreeBSD from Microsoft, but two things hold me back. 1. Multi monitors 2. Using/configuring Wine If I can have a setup with 16 monitors, are there any threads, or websites which could help me to do so? I will be using Quadro Nvidia cards (4). Thanks in advance. 1. SLI support and Crossfire support don't exist in Unix. How can you possibly setup 16 monitors? Even with splitters, it's not possible (unless you use PCI cards). I'm not sure about SLI and Crossfire, but I'm sure that Unix doesn't really need them to support that many monitors. Whether you use one Xorg instance or multiple ones, you can certainly use 16 monitors. The only issue could be nvidia's binary drivers, but I hope they support their Quadro's. Search for words like Xinerama and multiheading 2. Wine has plenty of Howto's all over the net. Linux has better support for wine, but FreeBSD is not far behind. E.g. many people are running 3D games under wine in FreeBSD. Internet Explorer is happily running on PC- BSD, which means it won't have much trouble on FreeBSD. The binary nvidia driver works just fine with Quadro cards, and between Xinerama and the built-in TwinView support (possibly only using one or the other) I'm sure you'd be able to drive all your screens and arrange them how you'd like. Just be prepared to do some research, use the nvidia-xconfig tool a couple times, do some experimenting, and then manually edit your xorg.conf to get the behavior you want. (Possibly repeated a few times). You'll have the best luck with the nvidia driver on 6.2 or 6-STABLE, and it only supports i386 (not amd64). Take a look at this list to be sure you install a version of the driver that supports your card: http://us.download.nvidia.com/freebsd/1.0-9746/README/appendix-a.html JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing FreeBSD-6.2 Xorg-7.2
On Tuesday 12 June 2007 10:47:24 am John Nielsen wrote:
On Tuesday 12 June 2007 08:55:54 am Gerard wrote:
I have had nothing but grief since updating to the new Xorg-7.2
version on my PC. Unexplained crashes, lockups, etc. No doubt, some of
the problems are my fault; however I cannot seem to get them corrected.
Now, I was wondering how this would work.
1) Download a fresh ISO of FreeBSD-6.2 on to another PC
2) Erase my HDs on the PC presently running FBSD
3) Reformat the HDs
4) Install the fresh copy of FBSD
Will that give me a system that I can directly install Xorg-7.2 on to
or do I still have to go through the procedure shown in the UPDATING
file? Suppose I install Xorg-7.2 doing the actual install of FBSD;
will that make any difference? In any case, I would build a new kernel
ASAP after the new install.
That should work fine, as long as you remember to run mergebase.sh on the
new system. It's counterintuitive and won't have much work to do, but it
will do useful things like create the /usr/X11R6 - /usr/local symlink and
change some defaults in /etc so (e.g.) rc.d and periodic scripts won't run
twice.
If it's just your ports you're trying to refresh and don't have any worries
about your base system, you could also try something like this:
0) Back up your entire system. Also make a note of what packages you have
installed (pkg_info /root/pkg-list.txt, for example).
1) Delete ALL ports from your system. I find it's most efficient to do
something like this:
a) make backups, esp of files in /usr/local/etc
b) # pkg_info | awk -F ' ' '{print $1}' | xargs pkg_delete -f
For the archives, this works better with xargs -n 1 in place of xargs
above.
JN
c) review remaining files under /usr/X11R6 and /usr/local, if any
d) # rm -r /usr/X11R6/* /usr/local/*
2) Update your base system. csup, buildworld, etc.
3) Update your ports tree. portsnap, etc.
4) Run mergebase.sh
# sh /usr/ports/Tools/scripts/mergebase.sh
5) Reinstall everything you want installed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing FreeBSD-6.2 Xorg-7.2
On Tuesday 12 June 2007 08:55:54 am Gerard wrote:
I have had nothing but grief since updating to the new Xorg-7.2
version on my PC. Unexplained crashes, lockups, etc. No doubt, some of
the problems are my fault; however I cannot seem to get them corrected.
Now, I was wondering how this would work.
1) Download a fresh ISO of FreeBSD-6.2 on to another PC
2) Erase my HDs on the PC presently running FBSD
3) Reformat the HDs
4) Install the fresh copy of FBSD
Will that give me a system that I can directly install Xorg-7.2 on to
or do I still have to go through the procedure shown in the UPDATING
file? Suppose I install Xorg-7.2 doing the actual install of FBSD;
will that make any difference? In any case, I would build a new kernel
ASAP after the new install.
That should work fine, as long as you remember to run mergebase.sh on the new
system. It's counterintuitive and won't have much work to do, but it will do
useful things like create the /usr/X11R6 - /usr/local symlink and change
some defaults in /etc so (e.g.) rc.d and periodic scripts won't run twice.
If it's just your ports you're trying to refresh and don't have any worries
about your base system, you could also try something like this:
0) Back up your entire system. Also make a note of what packages you have
installed (pkg_info /root/pkg-list.txt, for example).
1) Delete ALL ports from your system. I find it's most efficient to do
something like this:
a) make backups, esp of files in /usr/local/etc
b) # pkg_info | awk -F ' ' '{print $1}' | xargs pkg_delete -f
c) review remaining files under /usr/X11R6 and /usr/local, if any
d) # rm -r /usr/X11R6/* /usr/local/*
2) Update your base system. csup, buildworld, etc.
3) Update your ports tree. portsnap, etc.
4) Run mergebase.sh
# sh /usr/ports/Tools/scripts/mergebase.sh
5) Reinstall everything you want installed.
Have fun,
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing FreeBSD-6.2 Xorg-7.2
On Tuesday 12 June 2007 12:47:59 pm Gerard wrote:
On June 12, 2007 at 10:47AM John Nielsen wrote:
That should work fine, as long as you remember to run mergebase.sh on the
new system. It's counterintuitive and won't have much work to do, but it
will do useful things like create the /usr/X11R6 - /usr/local symlink
and change some defaults in /etc so (e.g.) rc.d and periodic scripts
won't run twice.
If it's just your ports you're trying to refresh and don't have any
worries about your base system, you could also try something like this:
0) Back up your entire system. Also make a note of what packages you have
installed (pkg_info /root/pkg-list.txt, for example).
1) Delete ALL ports from your system. I find it's most efficient to do
something like this:
a) make backups, esp of files in /usr/local/etc
b) # pkg_info | awk -F ' ' '{print $1}' | xargs pkg_delete -f
c) review remaining files under /usr/X11R6 and /usr/local, if any
d) # rm -r /usr/X11R6/* /usr/local/*
2) Update your base system. csup, buildworld, etc.
3) Update your ports tree. portsnap, etc.
4) Run mergebase.sh
#
5) Reinstall everything you want installed.
Have fun,
Having way too much fun. The system crashed again, causing me to get
really annoyed. I decided I had, had enough and totally erased the
HD's after coping any config files I would need to another PC first. I
am in the process of reformatting the two 72G HDs now.
Now, just so I get this straight.
1) I do a minimal install of FBSD.
2) Update the ports, in my case using portsnap.
3) Update the system files
4) Do a BuildWorld with custom kernel installation
5) Run: sh /usr/ports/Tools/scripts/mergebase.sh
6) Start the installation of Xorg-7.2 and other program.
I am assuming that I should have the VAR as stated in the UPDATING
file set prior to to actually attempting to update the system. After
it is completed I can remove it. Is that correct?
Looks good, except I don't know what you mean by VAR. If you're talking about
the XORG_UPGRADE environment variable you shouldn't need it as long as you
run mergebase before trying to install xorg.
Well, the next few days should be fun!
Indeed. I have an older laptop that's chugging through the upgrade now..
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating system GCC
On Friday 08 June 2007 10:07:20 am Gerard wrote: I noticed this on the FreeBSD site regarding the latest version of JAVA: January 24, 2007: Greg Lewis has released the fourth patchset (patchlevel 4, Sumatran) for the JDK 1.5.0 software. This release builds with GCC 4 and includes a number of bug fixes. FreeBSD-6.2 does not come with GCC 4 or newer. While it is relatively trivial to install it manually, it then is necessary to make changes to the system /etc/make.conf file to insure its use. Wouldn't it be more efficient for the FreeBSD team to integrate GCC 4.3 (I think that is the latest stable version) into the base system? From what I have read, this latest version has some major improvements over its predecessors. Chaning the major version number of the default system compiler is not something that is ever likely to happen on a -STABLE branch, which is what 6.x is now. GCC 4.2 has been imported into 7.0-CURRENT, and works well there. IIRC the plan is to have GCC 4.2.1 or similar for 7.0-RELEASE, but check the -current archives to verify. And actually, I think you're mis-reading the announcement. The fact that it builds with gcc 4 is an improvement over the previous patchset which didn't. That does not mean that it requires gcc 4, and I see nothing in the port's Makefile to indicate that it requires any particular version of the compiler. Just cd /usr/ports/java/jdk15 make install clean and you should be good to go (once you get all the source files downloaded manually...) JN ___ 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 correctly use 2 on board nics
Quoting Ivan Carey [EMAIL PROTECTED]: I have a server board with 2 onboard nic's I have set them up in rc.conf as follows defaultrouter=192.168.1.1 network_interfaces=em0 em1 lo0 ifconfig_em0=inet 192.168.1.3 netmask 255.255.255.0 ifconfig_em1=inet 192.168.1.4 netmask 255.255.255.0 The question, is this the correct configuration? Manually specifying network_interfaces is deprecated (take that line out). Putting both NIC's on the same subnet and segment but with different IP's like this may not be too useful.. If I have both nic's connected to the switch I can ping 192.168.1.1 and 192.168.1.3 and 192.168.1.4 If I have only em0 connected I can ping 192.168.1.1 and 192.168.1.3 If I have only em1 connected I can ping 192.168.1.3. That is because the route to 192.168.1.1 is associated with em0 at this point. What could the 2 onboard nic's be best used for. I was thinking that in the event on was to fail then the other would still be ok. For that to be most useful you'll want to set something up so they can share the same IP. The lagg(4) (link aggregation) virtual interface has already been mentioned, but I believe it is still only available in -CURRENT. Other possibilities might include attaching ifconfig scripts to link up/down events or [lack of] ping responses on one or both interfaces. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports system gone
Quoting Robert Fitzpatrick [EMAIL PROTECTED]: How can I restore my ports system? Use a valid tag in your ports-supfile (probably .) and try again. I have no idea what happened. I have a server I setup over the weekend to start testing Maia Mailguard, installed many packages over the last few days (postfix+amavisd+SA+related). I can't remember the last package installed via the ports system, I updated it to src-all and back to ports-all once to compile my kernel. Now, today I go to install a package and practically everything is gone...this is all I have left... mx1# ls /usr/ports INDEX-6 INDEX-6.db dns security INDEX-6.bz2 distfiles net mx1# ls /usr/ports/dns bind9-dlz mx1# ls /usr/ports/security/ vscan mx1# ls /usr/ports/net/ openldap23-client At this point I want to assume I mistakenly did a rm sometime, what else could cause something like this? Can't find any issues in the logs and no other issues with any services running on the box. Can't find anything else missing. If I try to run my ports update my ports, it just hangs here... mx1# cd /usr/ports mx1# /usr/local/bin/cvsup /root/ports-supfile Connected to cvsup9.us.FreeBSD.org Updating collection ports-all/cvs JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 console setup
On Saturday 02 June 2007 04:00:57 pm Kevin Kinsey wrote: Jim Capozzoli wrote: Hello list, I have 3 monitors and 3 video cards. However, one videocard and monitor isn't very X11 friendly. (X11 barely starts on it). I was wondering if it would be possible to have X11 running on two of the monitors, and then have a full screen console (like a ttyv0) on the third monitor (so I could constantly leave top or something sweet running on there :D). This is all with FreeBSD 6.2/i386 and Xorg 6.9 or 7.2. Any suggestions? Thanks. It should do do-able, perhaps somewhat easily. /usr/ports/x11-servers/x2x is what comes to mind --- IIRC, Greg groggy Lehey of The Complete FreeBSD fame uses this for several displays, and has notes on his setup in her personal pages at www.lemis.com. That link is here: http://www.lemis.com/grog/hardware.html However, I'm not sure x2x is relevant to the OP--It can be used to allow one mouse and keyboard to be used on multiple X servers, but doesn't have anything to do with console mode. I don't know if the setup the OP wants is possible or not, but here are some notes: The FreeBSD console always runs on the primary display as determined by the BIOS. Most systems give you a choice between using AGP or PCI as the primary display. If you have multiple PCI cards it is usually the first one on the bus (physically this is often the one closest to the CPU). Not sure how ISA figures in. You will want to make your bad videocard and monitor the primary display. Once you have that, I'd just run an Xorg -configure to get started. If X comes up at all using the config generated from that then it will be a good starting point. Try commenting out the device and screen sections (and possibly also a line under ServerLayout) for your bad display and see if X comes up on the other two. By default it expects to be running on the console so I'm not sure what will happen here. You also want it to grab the keyboard and mouse unless you have a second keyboard. Some trial and error and further research are probably required. Play with startx vs xdm, see what happens when you press ctrl-alt-f1, etc. I'm assuming you'll want to use Xinerama to join the two X displays and allow window-dragging between them, etc. If you don't get acceptable results using your original plan, you can always hack together your own console to run on the weakest display under X (using the vesa driver if necessary). If possible (not sure it is), don't make it part of your Xinerama display. Then don't run a window manager on it. Use xsetroot as part of your X init script to control what's on the background. This will apply to your entire display but the WM will probably take over once it starts on the good screens. You could make one or more scripts to run things on your bad screen by doing something like this: #!/bin/sh DISPLAY=:0.1#might also be :0.2 or :0.0 export DISPLAY xterm -r -geometry 120x60 /usr/bin/top Experiment with the geometry settings to see what fills your screen appropriately. You might also want to get a nice bitmap font to give the xterm more of a terminal feel. I have one I stole from bochs or somewhere that's not bad (I use it for Nethack). E-mail me off-list if you want it. That should just about do it. Do write back to the list to tell us what you learn and what works the best. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Flatbed scanners for FreeBSD
On Saturday 02 June 2007 06:48:46 pm Roland Smith wrote: On Sat, Jun 02, 2007 at 03:15:22PM -0600, Andrew Falanga wrote: Hi everybody, What scanners are best used with FreeBSD? I'm hoping for one that I can use in both Windoze and FreeBSD. Preferably, one that is USB. I've never configured a scanner for FreeBSD before and would like recommendations on hardware before purchasing. Look at the website for the SANE (acanner access now easy) project. If it is listed there, it will probably work; http://www.sane-project.org/sane-mfgs.html#SCANNERS I've had good experiences with Epson scanners, but mine is several years old, and you can't buy them anymore. If you have a specific model in mind, google for it's name in combination with SANE, to see if it comes up on the SANE mailing list. E.g. they've gotten the cheap Epson Perfection V10 working recently; http://lists.alioth.debian.org/pipermail/sane-devel/2006-November/017993.ht ml Also keep in mind that SANE can use libusb for scanner access even if said scanner is not supported by FreeBSD's uscanner. I have an Epson CX4800 scanner/printer/cardreader. If I don't have ulpt or umass in the kernel, the scanner works fine via libusb. I assume for a standalone scanner the multifunction strangeness wouldn't be an issue. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New (blade) server - stick with FreeBSD 6.x or wait for FreeBSD 7?
On Monday 04 June 2007 05:30:37 am Per olof Ljungmark wrote: Kris Kennaway wrote: On Mon, Jun 04, 2007 at 09:46:00AM +0200, Ewald Jenisch wrote: Hi, I'm about to set up a new server that should run basically network-monitoring (MRTG, Cacti etc.). Hardware will be HP C-class blade based on AMD Opterons. Should I stick with FreeBS 6.x or wait for FreeBSD 7 (see http://www.freebsd.org/releng/index.html - June 2007 Start FreeBSD 7.0 Release Process). Note start. The release is still many months away, so presumably you do not wish to wait until then to install your server :) You should definitely keep an eye on it though, there is a lot of good stuff coming up in 7.0. The question basically is: Will FreeBSD7 be current or stable? We are running several non-critical (including this T42 laptop) and one critical (SMTP) machine with -CURRENT and so far it's been a matter of getting the source from a good moment in time, mostly the snapshots. So far very few problems. You need a testbed to try stuff out on though. Note that the bge adapters in the HP c-class blades require SerDes support, which IIRC was not present in 6.2-RELEASE but has (hopefully? maybe?) been MFC'ed since then. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: X11 console setup
On Monday 04 June 2007 11:30:03 am Jim Capozzoli wrote: On 6/4/07, John Nielsen [EMAIL PROTECTED] wrote: On Saturday 02 June 2007 04:00:57 pm Kevin Kinsey wrote: Jim Capozzoli wrote: Hello list, I have 3 monitors and 3 video cards. However, one videocard and monitor isn't very X11 friendly. (X11 barely starts on it). I was wondering if it would be possible to have X11 running on two of the monitors, and then have a full screen console (like a ttyv0) on the third monitor (so I could constantly leave top or something sweet running on there :D). This is all with FreeBSD 6.2/i386 and Xorg 6.9 or 7.2. Any suggestions? Thanks. It should do do-able, perhaps somewhat easily. /usr/ports/x11-servers/x2x is what comes to mind --- IIRC, Greg groggy Lehey of The Complete FreeBSD fame uses this for several displays, and has notes on his setup in her personal pages at www.lemis.com. That link is here: http://www.lemis.com/grog/hardware.html However, I'm not sure x2x is relevant to the OP--It can be used to allow one mouse and keyboard to be used on multiple X servers, but doesn't have anything to do with console mode. I don't know if the setup the OP wants is possible or not, but here are some notes: The FreeBSD console always runs on the primary display as determined by the BIOS. Most systems give you a choice between using AGP or PCI as the primary display. If you have multiple PCI cards it is usually the first one on the bus (physically this is often the one closest to the CPU). Not sure how ISA figures in. You will want to make your bad videocard and monitor the primary display. Once you have that, I'd just run an Xorg -configure to get started. If X comes up at all using the config generated from that then it will be a good starting point. Try commenting out the device and screen sections (and possibly also a line under ServerLayout) for your bad display and see if X comes up on the other two. By default it expects to be running on the console so I'm not sure what will happen here. You also want it to grab the keyboard and mouse unless you have a second keyboard. Some trial and error and further research are probably required. Play with startx vs xdm, see what happens when you press ctrl-alt-f1, etc. I'm assuming you'll want to use Xinerama to join the two X displays and allow window-dragging between them, etc. If you don't get acceptable results using your original plan, you can always hack together your own console to run on the weakest display under X (using the vesa driver if necessary). If possible (not sure it is), don't make it part of your Xinerama display. Then don't run a window manager on it. Use xsetroot as part of your X init script to control what's on the background. This will apply to your entire display but the WM will probably take over once it starts on the good screens. You could make one or more scripts to run things on your bad screen by doing something like this: #!/bin/sh DISPLAY=:0.1#might also be :0.2 or :0.0 export DISPLAY xterm -r -geometry 120x60 /usr/bin/top Experiment with the geometry settings to see what fills your screen appropriately. You might also want to get a nice bitmap font to give the xterm more of a terminal feel. I have one I stole from bochs or somewhere that's not bad (I use it for Nethack). E-mail me off-list if you want it. That should just about do it. Do write back to the list to tell us what you learn and what works the best. JN I like the not making it a part of the Xinerama display..that would be interesting, because I'm sure a very basic X11 background with a xterm would work on there. If X starts on there, then yeah great but the problem is I don't ever recall getting it to work properly. If the card functions at all then I'm sure you could get the vesa driver running at 800x600x8 at least.. What I had in mind however, is say having the weak monitor/card as the 'default' display that the BIOS picks up, and then leaving a console on there BUT having X11 on the two other monitors. Then I'd run top on it or something, so Id have a command like... $ startxfce4 top -s 1 And then on the 'default' BIOS chosen display, you would see top running in console mode, and then pretty xfce with nice 1280x1024 ver monitor resolution on the other two (using Xinerama). I wouldn't need to have keyboard/mouse control on the 'default' console then, I'd just look at it to see which process is eating the machine, load averages, etc. My suggestion for running the weak display under X was conditional on not getting results you liked with your original idea. Re-read the first part of my first reply. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail
Re: Nvidia doesn't start on cryptic errors
On Monday 28 May 2007 11:18:07 Vittorio De Martino wrote: On my newly bought HP pavillion 6366 notebook with freebsd 6.2 - p4 and one of the latest portsnap I have an nvidia go 7400 card, *** fully *** supported by the nvidia driver according to the docs. I followed the minimal configuration by nvidia-xconfig and just taiored the language for the keyboardBUT startx fails to load X and in the log file I find I find the below reported errors. Being a beginner I find myself somewhat disorientated by these errors that I couldn't find surfing the net. (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure (EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and (EE) NVIDIA(0): that the NVIDIA device files have been created properly. (EE) NVIDIA(0): Please consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** Not too cryptic. Make sure that the nvidia kernel module is loaded and try again. To verify, type kldstat. If nvidia.ko is not listed, type kldload nvidia. To load it automatically on boot (which is the only way for it to load successfully), add a line like this to /boot/loader.conf: nvidia_load=YES Then reboot. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: raid or not raid
On Thursday 24 May 2007 06:30:06 am kalin mintchev wrote: so nobody on this list knows anything about raid? wrong list? hi all.. i have a box in a remote hosting facility that claims that the machine has two discs raided in it but df and fstab show only one disc with a bunch of slices. under devices there is another name - ad6 - but it's not mounted anywhere. the one i see both in df and the fstab is ad4 with one big slice and different partitions they insist there are 2 raided discs in tha machine. the os is 5.4 and i think at that point the raid drivers were still considered 'experimental'. it makes sense to me that if i don't see a second drive in the fstab there isn;t any mounting which means that there is no raid going on... is there any other way i can make sure if raid is actually on? would there will be any logs somewhere? the machine has been up for about 2 years and the dmesg is long gone... My guess would be that it's not actually doing RAID. Real hardware RAID controllers either require their own drivers (twe, for instance shows disks as twed0, etc) or present disks as SCSI devices (e.g. da0). ATA pseudo-raid hardware supported by FreeBSD's ata(4) driver shows both the raw disks (ad4, ad6, etc) AND an array device like ar0. If RAID was set up in the BIOS then FreeBSD is probably ignoring it, perhaps because ata(4) doesn't grok the metadata format used by the RAID card. If I were you I would aim to migrate to gmirror RSN. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gvinum and RAID
On Thursday 24 May 2007 12:43:36 pm [EMAIL PROTECTED] wrote: Is it possible to use gvinum to create a striped array that contains the root partition? I want to be able to combine all 4 of the hard disks into one logical striped array and install the boot partition on it. I have found documentation on how to mirror the root drive, but none on using a striped array for the root drive. Is this possible? Not without hardware support, no. I would create a small (1-2 GB) root partition one two or more of the drives and mirror it with gmirror (or not.. you must not care about fault tolerance if you're setting up a giant stripe). You could maybe use the same 1-2GB on the other drives for swap or tmp space (optionally mirrored as well). Then use the rest of the space on all the drives for your stripe array. I'd recommend gstripe over gvinum for ease-of-use, but it's up to you. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gvinum and RAID
On Thursday 24 May 2007 02:08:41 pm [EMAIL PROTECTED] wrote: On Thursday 24 May 2007 12:43:36 pm [EMAIL PROTECTED] wrote: Is it possible to use gvinum to create a striped array that contains the root partition? I want to be able to combine all 4 of the hard disks into one logical striped array and install the boot partition on it. I have found documentation on how to mirror the root drive, but none on using a striped array for the root drive. Is this possible? Not without hardware support, no. I would create a small (1-2 GB) root partition one two or more of the drives and mirror it with gmirror (or not.. you must not care about fault tolerance if you're setting up a giant stripe). You could maybe use the same 1-2GB on the other drives for swap or tmp space (optionally mirrored as well). Then use the rest of the space on all the drives for your stripe array. I'd recommend gstripe over gvinum for ease-of-use, but it's up to you. Is it possible to use gmirror for a small partition on two disks and then use gstripe on the remaining disk space of those drives to create a larger stripe? I didn't think that was possible. I could be wrong however :). If that will work, that would be my best option right there. Yes, that's exactly what I'm recommending. On each drive: fdisk -BI bsdlabel -wB bsdlabel -e (set up partitions here, use a for root and d for stripe) Then: gmirror label somename firstdisks1a seconddisks1a ... gstripe lable someothername firstdisks1d seconddisks1d ... etc. There are obviously a few blanks in the above but the manpages for each command and online documentation will help you fill them in. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A little bit of help understanding CVS and cvsup
On Thursday 17 May 2007 11:04:06 am Andrew Falanga wrote: Hi, This question probably hasn't much to do with CVS directly but using cvsup. I want/need to update a 6.0-RELEASE system. However, this system has some critical data on it and I'd rather not move to code that is perhaps experimental or bleeding-edge technology. I see in /usr/share/examples/cvsup several supfiles named various things. I see from the handbook that standard-supfile applies to, what seems like, the bleeding-edge and the stable-supfile is what I'm looking for .. yes? How do I ensure I update the sources to the most current, STABLE, branch? The main difference between the examples files is the cvs tag used. The . tag will get you 7.0-CURRENT. Very much bleeding edge, almost certainly not what you want. The RELENG_6 tag will get you 6-STABLE. This is the branch that will eventually become 6.3-RELEASE. Everything in this branch is reasonably conservative and well-tested, but there is still some new code and features. This might be what you want. The RELENG_6_2 tag will get you 6.2-RELEASE-pX, where X is the current patch revision level. This is 6.2-RELEASE with security and critical patches only, no new features. This is probably what you want, unless there's a feature in -STABLE that you can't live without. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hostname setting in rc.conf ignored?
On Thursday 17 May 2007 01:27:52 pm Mike Barborak wrote: Hello, I have a FreeBSD 4.7-RELEASE-p28 server that was initially configured with the hostname mydomain.com. I am trying to permanently change that to be www.mydomain.com. I have added this line to my /etc/rc.conf file: hostname=www.mydomain.com but after restarting the server it continues to return mydomain.com when i run the command hostname. Can anyone tell me what I am doing wrong? Is there a second hostname entry further down in rc.conf with the original value? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A little bit of help understanding CVS and cvsup
On Thursday 17 May 2007 02:31:59 pm Andrew Falanga wrote: On 5/17/07, Alex Zbyslaw [EMAIL PROTECTED] wrote: Andrew Falanga wrote: You can find a description of release tags in the handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html and also a description of -STABLE and -CURRENT http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable. html. Later bits in that section also describe the update procedure *even if you are updating to a RELEASE./RELENG rather then CURRENT or STABLE*. A brief description of the strings in tags is a follows: CURRENT == bleeding edge STABLE == merely leading edge RELENG == what you are calling stable; a release plus security patches only RELEASE == sort of you are calling stable, exactly what was released (not recommended since it lacks any security patches) The latest release is 6.2, so the tag you want in your supfile is RELENG_6_2. That string won't be in any supfile on your system. It's impossible for it to be, since that would require predicting what will be the latest release at the point in the future when you chose to upgrade :-) In technical terms, CURRENT is the top of the main development trunk, and is often referred to with a leading number (e.g. 7-CURRENT), but the number does no more than denote the numeric tag that will be applied when the next branch is made. Once 7.0 starts being created, CURRENT will be 8-CURRENT. STABLE is the latest branch. Code here will become the next Release. Moving code from CURRENT to STABLE, involves a CVS merge operation and is often referred to as MFC - merge from CURRENT. RELENG is a branch created when a specific release is made. It denotes the latest code on that branch, but the only changes made will be critical security fixes. RELEASE is just the point on the RELENG branch which is the actual code which was released on the Release CDs. --Alex PS Be really nice if all this info was clearly in the FAQ, and the FAQ was searchable apart from the whole website. As things stand, a search for stable returns precisely nothing, which can't be right. Thank you for the detailed description. Just one last question for you and the list, what sort of heart ache can I expect to encounter if I use the label RELEASE_6_2 in my supfile on a system that is 6.0? I need to upgrade a 6.0-RELEASE (no patches) system. Will I encounter compiler problems (that is, I'm using a compiler that's older than I should for 6.2), or similar? Or, should the upgrade be just as smooth as the run through I just completed on a non-critical notebook running 6.2-RELEASE (or rather, it was running 6.2-RELEASE, now it's 6.2-RELEASE-p4)? In my experiences upgrades that don't cross major version boundaries are relatively painless. I haven't done a 6.0-6.2 upgrade, but I've done multiple 6.0-6.1 and 6.1-6.2 upgrades, and both were quite minor so I don't think doing it in one go would introduce any problems. Compiler changes in particular will typically only happen across major versions. Nothing like that going on with 6.x. Should be smooth, just with a longer mergemaster step. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone could make Epson Stylus cx4700 work?
On Tuesday 15 May 2007 01:44:17 pm Roland Smith wrote: On Tue, May 15, 2007 at 01:51:53PM -0300, Anton Galitch wrote: Hi I tried to install my epson stylus cx4700 printer, I installed cups, then gutenprint. When configuring the printer in kde control center it detected the driver for stylus cx4700 and a device was /dev/ulpt0 (its has a usb connection). After doing that I wanted to test it, but it couldnt print anything. neither it can give me information about ink level. It says Device is busy. One thing to check for are the permissions of the device file /dev/ulpt0. Cups needs to be able to read from and write to this device, so you should add an entry for it to /etc/devfs.rules. It should _not_ be in /etc/devfs.conf, since usb devices can appear at runtime. (The first line is only needed when you haven't already got a ruleset name.) [foo=10] add path 'ulpt*' mode 0660 group cups And in /etc/rc.conf you should add: devfs_system_ruleset=foo Hope this helps. Roland Alternatively, just put this in /etc/devfs.conf: own ulpt0 root:cups permulpt0 0664 That's all I had to do to get my cx4800 printing with ulpt and cups. FYI, the cardreader on my cx4800 works when ulpt is NOT loaded or in the kernel but umass is. Similarly, the scanner only works when neither ulpt nor umass is loaded or in the kernel. It doesn't attach to uscanner but it works with libusb. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VPS, Colocation, Dedicated
On Thursday 26 April 2007 01:51:56 pm Duane Winner wrote: I am looking for any sort of insight, experience from anybody who uses VPS technology to substitute for managing their own infrastructure and servers for business apps. We are looking at different options to unload some of the burden of supporting a network and server infrastructure that is composed of 50+ FreeBSD servers. The concept of VPS technology has been put on the table, along with co-lo and dedicated server options. Web hosting is right out of the question. I've had a VPS with JohnCompanies for quite some time and have been very happy with it. A client of mine also hosts dedicated/managed servers with them with good results. Requirements: 1. We need to have servers take over the role of the 30+ web servers, which run apache and mzscheme webapps. These web servers to talk to 2+ postgresql databases on seperate servers. 2. The data on the pgsql databases is of a sensitive nature, so it needs to be secured in part by keeping these servers on a separate network segment, accessible only by the web servers, using stunnel encryption. You may want to consider running the webservers as VPS'es and the database servers on dedicated hardware (your own or managed). That would make it easy to directly control the network environment on the database side, at least. 3. All servers should have some form of firewall protection, either locally (software) or on the network. Preferably network. 4. If using VPS, the FreeBSD image should look and feel just as if we installed it ourselves from scratch, starting off barebones and installing only the apps and services we need. That's what JC gives you. 5. Web server disk space needs to be 10GB. Can scale back to 5GB if ports are kept off the server and compiled offline then synced up. 6. One of our database servers is utilizing 33GB of disk space at the moment, so we would need at least 50GB per server. Another reason to not go VPS for the DB servers. Findings: I have found about 4-5 providers who offer FreeBSD VSP's. I've evaluated 2: JohnCompanies and Verio. 1. JohnCompanies' VPS image was nearly exactly what I'm looking for -- started off barebones, and I had to do the rest. Just like in my server room. But disk space was abysmal $29/month for 2GB or $69/month for 8GB. I do think the default disk space offered with their packages is pretty low, but you can get as much more as you want/need for an extra $2/GB/mo. I would recommend contacting them directly (sales@), they are helpful and have a clue. 2. Verios turned me off right away between high-pressure sales tactics and an evaluation that saw a base image loaded with crap like it was a Linux or worse, a Windows box: NAS audio server, mp3 player, a default Apache 2.2 install (who said I want 2.2?), that wasn't a port, but built-in shared app! PHP, Xridiculous. Thanks for the warning... 3. Nobody seems to include any sort of firewall protection -- just throw the server out in the public DMZ, and then there is no option to protect database servers on a private subnet. Not even ipfw is included. Verios told me that their FreeBSD images cannot firewall, but their Linux images can, and then tried to pressure me into just converting to Linux. Sorry, they're off the list now. Again from my experience with JC.. I don't know if or how well individual VPS'es are firewalled from each other, but you can specify your own firewall rules to be run on the firewall between the VPS server host(s) and the rest of the universe. If you were to put your databases on dedicated managed servers I'm sure you could get them on their own segment, and you could run whatever firewall you choose locally. Summary: I really don't think VPS technology can scale to our requirements or meet the specs we need, in resources or security. Their are other in my group who wanted to investigate VPS technology because of the notion that it is more secure. For instance, there is the concept that because it is virtual, and more hidden, it would be more difficult for an employee at our provider to get at the data, whereas if we colocated, they could just pull a hard drive and get at the data. Personally, I think it would be easier to hi-jack a VMware session or image that it would be to get through security, and into a locked cabinet at a colo facility and reboot into single user mode or yank out a disk in a RAID array to get to the data. JC has their own segment/cage/whatever at their datacenter with their own personnel onsite 24x7. I do know that JC tech's can access the complete filesystem of any VPS at any time without any downtime, impact or evidence on the VPS itself. This is handy for e.g. backup/restore purposes but could be viewed as a security concern. On a dedicated server, you would notice downtime (disks yanked or reboot to single-user) or at least log entries (network access) if
Re: Samba and RAID 1 using gmirror on 2 new disks
On Thursday 19 April 2007 03:24:36 pm L Goodwin wrote: Hello. I have a server with 3 SCSI drives. FreeBSD is installed on da0 (4.3GB), and da1 and da2 (both identical 9GB drives) are to be used in a RAID 1 array for file storage on a LAN with Windows XP and Vista clients, using Samba to share the filesystem on da1. Backups will be taken from da2. Drives da1 and da2 are currently unused (reclaimed from a Windows server). I have not done anything to prepare these 2 drives yet. I also have not configured Samba yet. Please walk me through the process of setting up a FreeBSD 6.2 fileserver given these conditions? I tried configuring the RAID1 array using the following sources, but got judging from the errors I got, it looks like I need to prepare da1/da2 first: http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html man gmirror man newfs man mount man fstab man smb.conf man samba gmirror label -b load sambavol /dev/da1 /dev/da2 newfs -U /dev/mirror/sambavol mkdir /sambavol mount /dev/mirror/sambavol /sambavol echo '/dev/mirror/sambavol /sambavol ufs rw 2 2' /etc/fstab The samba config depends a log on how you want to use the share and handle authentication and permissions, etc. The sample config file has most of what you need. Here's a starting point for a section to share a /sambavol directory with a samba share name of sambavol: [sambavol] path = /sambavol browseable = yes writable = yes printable = no You will of course need a correctly configured global section and you'll probably want additional entries in the volume section like public, guest ok, only guest, etc. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports maintainer or adopting a port
On Saturday 31 March 2007, Kimi Ostro wrote: Not sure if this is appropriate for this list, basically I am looking to hear from past, current and future ports maintainers: is it fun? I maintain a couple ports. Both were new in that they weren't in the ports collection before I submitted them. Both were pieces of software that I wanted to use, and for me the ports system made the actual porting much easier than it otherwise would have been. I didn't have to figure out how to use gmake instead of make, didn't have to manually extract the tarball every time I wanted a clean start (just do make extract or make patch once you have a couple basic lines in the port's makefile). Similarly, once you have a basic packing list you can make install and make deinstall instead of trying to copy or delete things manually. I think it's a lot of fun as long as you don't bite off more than you can chew. what are the requirements? (besides time) In the case of software that isn't updated frequently, the requirements are pretty minimal, especially if you aren't doing the initial port. You should try to be proactive in keeping track of updates to the software (or at the very least respond quickly to e-mails to you as the port maintainer). For many programs you don't need to have much if any programming experience, just a willingness to read and understand the Porter's Handbook, and the ability to get your head around make(1) and Makefiles. Obviously programming experience is helpful in cases where things won't build cleanly or weren't written with portability in mind. what does it mean to you? do you recommend it? I definitely recommend it. One of my favorite things to get in my e-mail is Commited, thanks! I second Garrett's two cents about warm fuzzies and community contribution[1], and as a side benefit you get bragging rights which can be useful in the broader open-source community or even with regards to employment or things like discounted web hosting. best way to get started? what do I need to know about FreeBSD Ports? Partially covered above; you should be familiar with FreeBSD in general and how and where it is used. Participation in the community (esp. via the mailing lists) is at least as important actually using the OS regularly for real-world activities. To get started just pick something to work on and do it; preferably something that has some utility or importance to you. If you get stuck ask for help (here or on -ports, generally). When you get something that's usable and at least a little polished, send in a PR. The ports team does an awesome job of giving feedback and getting things committed quickly once they're ready. I am looking at adopting a port or two and looking to gain more insight, maybe someone that can do projects page for ports? which holds a list of unmaintained ports?? Others have suggested good ways to identify unmaintained ports. There is also a lot of software out there that's not in the ports tree but easily could be. Sourceforge projects, Perl modules on CPAN, and other websites might be good places to look around and see what's out there. JN [1] I enjoy esr's take on open-source and the gift culture philosophy: http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/ar01s06.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GTK filedialog crashes Firefox/Thunderbird
Quoting cpghost [EMAIL PROTECTED]: On Fri, Mar 23, 2007 at 01:44:09PM -0400, John Nielsen wrote: On Friday 23 March 2007 11:02:46 am Frank Staals wrote: It seems that I'm having problems (again) with the GTK filedialog in Firefox/Thunderbird. It happens when saving or opening a file in Firefox or thunderbird resulting in a crash. What to do: - Open Firefox - Save a file, the save-file dialog comes up, Save or cancel it. - Save a file, when the file dialog comes up, file dialog hangs and after a second or something firefox crashes I'm seeing the same behavior. I searched around on the web a while ago and saw a report (on a firefox bug issue or mailinglist I think) from another FreeBSD user about this. He later followed up to his own post saying that the problem went away after he recompiled ALL of his ports. The thing that was interesting is that he only saw the bad behavior under xfce (what WM are you using, btw?). I'm running xfce 4.4.0 and have the problem, but I haven't gotten around to recompiling everything yet. I may or may not wait for the modularXorg stuff to be committed before I do so... I'm experiencing a similar problem with the GTK file save box. Under fluxbox, the save box starts to grow and shrink horizontally by approx 40% of its size twice per second or so. The only way out of this is to kill and restart Firefox. I don't know if other GTK-based programs are affected though. Another data point: I'm too in the midst of the giant gettext upgrade tango, so this could be temporary, until everything is finally upgraded. I just want to report that I'm no longer having a problem after a complete system refresh. I upgraded to -CURRENT (mostly for better gjournal support, not because of anything in this thread), uninstalled all my ports, deleted the /var/db/ports directory, removed /usr/X11R6 entirely, set $X11BASE to /usr/local in /etc/make.conf, removed everything but a few config files in /usr/local, and installed everything again. Between the firefox issue I was seeing, the gettext upgrade, and upgrading to -CURRENT I definitely needed to reinstall everything anyway. I decided to go ahead and make the X11BASE change so my life will be easier when the default gets changed. (I'm already running the experimental modularXorg ports tree.) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GTK filedialog crashes Firefox/Thunderbird
On Friday 23 March 2007 11:02:46 am Frank Staals wrote: It seems that I'm having problems (again) with the GTK filedialog in Firefox/Thunderbird. It happens when saving or opening a file in Firefox or thunderbird resulting in a crash. What to do: - Open Firefox - Save a file, the save-file dialog comes up, Save or cancel it. - Save a file, when the file dialog comes up, file dialog hangs and after a second or something firefox crashes Same thing happens when trying to open a file using the file dialog a second time, and same for thunderbird: The second time the GTK file dialog comes up it seems to crash firefox or thunderbird. When I was running firefox-1.5 there was the exact same problem which was fixed in one of the developement releases and when first running Fx-2 I didn't have any problems with it either. I checked in the gimp and geany if there were problems with the file dialog but it worked fine in those programs. Has anyone else problems with this ? I'm seeing the same behavior. I searched around on the web a while ago and saw a report (on a firefox bug issue or mailinglist I think) from another FreeBSD user about this. He later followed up to his own post saying that the problem went away after he recompiled ALL of his ports. The thing that was interesting is that he only saw the bad behavior under xfce (what WM are you using, btw?). I'm running xfce 4.4.0 and have the problem, but I haven't gotten around to recompiling everything yet. I may or may not wait for the modularXorg stuff to be committed before I do so... JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best software raid 5 software?
On Wednesday 21 March 2007 03:03:53 am Gabriel Rossetti wrote: I am about to switch to software raid 5 for my personal server. I know hardware raid 5 is better, but being a student I'd rather not invest in a raid adapter now, plus my cpu is being used at about 0.0% 24/24 7/7, so it needs some exercise :-) I've heard of several software-based raid-5 projects, mainly of Vinum, has anybody tested it or any other ones? Which would you suggest? As far as I know, gvinum is the only software package in FreeBSD that can do RAID 5. The initial learning curve is a bit steep, but it should work fine once you get it configured. I would also suggest that you look at graid3 which, not surprisingly, supports RAID 3. As you may or may not know, RAID 3 is very similar to RAID 5. You get S*(N-1) usable space, where S is your disk size and N is the number of disks. You need at least three disks but can use more. Both allow you to lose any single disk and not lose any data. The difference is that RAID 5 stripes the redundant parity data across all of the disks and RAID 3 uses a single disk for all parity writes. As a result, RAID 5 potentially offers somewhat better read performance if disk I/O is the bottleneck (and assuming each disk has its own controller/I/O path). In the case of software raid and commodity (non-server) hardware, the difference should be nominal. Other software RAID options include gmirror (recommended for RAID1), gstripe (recommended for RAID0, can be combined w/ gmirror), ataraid (supports RAID0, RAID1, JBOD, and combinations on ata controllers only), and ccd (supports RAID0, RAID1, and JBOD; largely deprecated by gmirror and gstripe). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: negative free blocks after mirror! [was: Re: mirror without destroying existing contents]
On Monday 19 March 2007 10:46, Steve Franks wrote: Yes, the origonal disk was pretty full, but, I suspect this is not a good thing: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a507630 9525437176620%/ devfs 1 1 0 100%/dev /dev/ad0s1e507630 30688436332 7%/tmp /dev/ad0s1f 152451398 5956408 134298880 4%/usr /dev/ad0s1d 1444526103600 1225364 8%/var /dev/mirror/rainstones1 151368706 141135278 -1876068 101%/rainstone How is that even possible? This is a FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DISK-MORE-THAN-FULL Not really related to gmirror. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: manual root filesystems specification under VMware
On Monday 19 March 2007 12:21, Jeff Dickens wrote: I'm trying to move a FreeBSD 6.1 virtual machine from VMware server to VMware ESX Server. The original VM used a virtual IDE controller for the disks, and apparently VMware ESX server doesn't support this. The VMware converter applications translates the virtual disk files to use the Virtual SCSI controller under VMware ESX Server. However, I then get dumped at the Manual Root filesystem specification prompt, where I should be able to just type ufs:da0s1a and off I go. But what happens is that the system is hung right at that point and doesn't accept keyboard input. If I boot FreeBSD into safe mode I can make an entry at the prompt. But da0 is not available. If I type ? I see that all there is is acd0 and fd0. But the scsi device must be there because the system is booted from it. Anyone see how I can straighten this out? Once I get the root filesystem mounted I should be able to edit fstab and go. Update the VM to 6.2 or -STABLE before you migrate it, and be sure you have mpt(4) in the kernel. The mpt(4) in FreeBSD 6.1 doesn't work under ESX server (actually it's the virtual hardware that acts broken), but a more recent mpt will work fine. See this PR and/or the commit history for mpt(4) for more details: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84040 I haven't done any migrations, but I have successfully run FreeBSD VM's installed from scratch under ESX 3.0 and 3.0.1. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mirror without destroying existing contents
On Friday 16 March 2007 11:18, Steve Franks wrote: I get the following: #gmirror label -v -b split -s 1024 data ad0 can't store metadata on ad0: operation not permitted. That most likely means that you currently have a filesystem on ad0 mounted. If that's the case you should be glad that the OS was smarter than you. What steps had you taken prior to this? Ideas? Same behavior with /dev/ad0. Does this only work with da0 disks, not sata drives? I'm logged in as root, not su. The drive is on a promise non-raid sata card (the sw raid chipset on my asus bios lost support going from 6.1 to 6.2 - something about some new method not supported by the bios according to Soren). Gmirror should work with any GEOM provider, and definitely works with SATA disks. As long as your controller is supported to the point of seeing and accessing the disks connected to it the software raid support is irrelevant (that's what you're using gmirror for). JN On 3/13/07, John Nielsen [EMAIL PROTECTED] wrote: On Tuesday 13 March 2007 15:12, Steve Franks wrote: Anyone made a mirror w/o destroying what's in the disk already? The atacontrol man page is less than adequate in this respect...is is even possible? If you want to use gmirror (which I recommend), the most conservative approach is as follows. This can probably be adapted to other mirroring techniques/software as well. Verify that your backups are up-to-date and reliable. Create a degraded single-member mirror on the blank disk (or a partition/slice on said disk). (gmirror label command) Make sure that the size of the disk/slice/partition is equal to or smaller than the size of the disk/slice/partition which already contains your data. Create (a) new filsystem(s) on the new mirror. (newfs and possibly bsdlabel, depending on how/if you want to break it up) Transfer your data from the existing filesystem to the new filesystem (dump/restore -- it's easier than it sounds). (Alternative: restore from the backup you created to begin with.) Verify data transfer, make relevant changes to /etc/fstab, possibly other intermediate steps. Destroy the original filesystem (possibly using dd and /dev/zero) (not strictly necessary, but wiping at least the first part of the disk/slice/partition can help avoid potential confusion (for you and the system) later.) Insert the original disk/slice/partition into your new mirro (gmirror insert command). This approach can take longer than some others (due to the transfer requirement), but the finished product is less likely to contain surprises. I have successfully used this approach to migrate several types of volumes to gmirror sets, including boot partitions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mirror without destroying existing contents
On Friday 16 March 2007 15:48, Steve Franks wrote: On 3/16/07, John Nielsen [EMAIL PROTECTED] wrote: On Friday 16 March 2007 11:18, Steve Franks wrote: I get the following: #gmirror label -v -b split -s 1024 data ad0 can't store metadata on ad0: operation not permitted. That most likely means that you currently have a filesystem on ad0 mounted. If that's the case you should be glad that the OS was smarter than you. What steps had you taken prior to this? It appears to say in the manpage that you can do this on a disk with an existing filesys - would you expect it to work if the disk is unmounted first, then? Steve man gmirror: Create a mirror on disk with valid data (note that the last sector of the disk will be overwritten). Add another disk to this mirror, so it will be synchronized with existing disk: gmirror label -v -b round-robin data da0 gmirror insert data da1 I would expect it to, yes. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
On Thursday 15 March 2007 14:37, John Nielsen wrote: On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. Sorry.. I obviously didn't read your post carefully enough. My understanding is the same as yours (also from versions more recent than 4.x), so I don't have any additional input. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing a second hard disk
On Tuesday 13 March 2007 13:05, Aitor San Juan wrote: Hi List, I am trying to install a secondary hard disk in a Intel-based PC with FreeBSD 5.4 This secondary disk's capacity is 250 Gb. When I enter sysintall to try to format it and create a slice, FreeBSD says that the geometry of disk is not correct. I, then, type in the values detected by the BIOS as suggested, but FreeBSD still complains that those are not valid. FreeBSD sees the new disk as a disk of approx. 131 GB. So my question is: where is the problem? Is it that FreeBSD is not able to recognise such a big disk capacity? Any hint, suggestion, or web link would be highly appreciated. Assuming the new disk is ad4, and you want a single FreeBSD slice/partition/FS covering the whole disk: fdisk -BI /dev/ad4 bsdlabel -wB /dev/ad4s1 newfs -U /dev/ad4s1a See the manpages for each command for more details. The -B flags aren't necessary if you never plan to boot from the new disk, but they don't hurt anything either. If you want multiple FreeBSD partitions you could run a bsdlabel -e after the first bsdlabel command above, and additional newfs commands as appropriate. Continuing the example above, you could do: mkdir /newdisk mount /dev/ad4s1a /newdisk echo /dev/ad4s1a /newdiskufs rw 2 2 /etc/fstab To both mount the new filesystem and have it mounted automatically at boot. See the fstab manpage for details about that. (You could of course use a text editor to modify fstab instead of the echo command above.) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mirror without destroying existing contents
On Tuesday 13 March 2007 15:12, Steve Franks wrote: Anyone made a mirror w/o destroying what's in the disk already? The atacontrol man page is less than adequate in this respect...is is even possible? If you want to use gmirror (which I recommend), the most conservative approach is as follows. This can probably be adapted to other mirroring techniques/software as well. Verify that your backups are up-to-date and reliable. Create a degraded single-member mirror on the blank disk (or a partition/slice on said disk). (gmirror label command) Make sure that the size of the disk/slice/partition is equal to or smaller than the size of the disk/slice/partition which already contains your data. Create (a) new filsystem(s) on the new mirror. (newfs and possibly bsdlabel, depending on how/if you want to break it up) Transfer your data from the existing filesystem to the new filesystem (dump/restore -- it's easier than it sounds). (Alternative: restore from the backup you created to begin with.) Verify data transfer, make relevant changes to /etc/fstab, possibly other intermediate steps. Destroy the original filesystem (possibly using dd and /dev/zero) (not strictly necessary, but wiping at least the first part of the disk/slice/partition can help avoid potential confusion (for you and the system) later.) Insert the original disk/slice/partition into your new mirro (gmirror insert command). This approach can take longer than some others (due to the transfer requirement), but the finished product is less likely to contain surprises. I have successfully used this approach to migrate several types of volumes to gmirror sets, including boot partitions. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DST issue (still one hour behind)
On Monday 12 March 2007 21:43, Peter wrote: I rebuilt my 6.2 system entirely and ran tzsetup. My time is still one hour behind. What else do I need to do? If you run date with no arguments what timezone does it say? If it's e.g. EDT (the D being for Daylight) then all you need to do is set the time manually (assuming you updated in the last 36 hours or so, after the time change). Otherwise I'd start with a reboot and then maybe play with adjkerntz if that doesn't take care of it. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DST issue (still one hour behind)
On Monday 12 March 2007 22:24, Peter wrote: Le Lundi 12 Mars 2007 21:52, John Nielsen a écrit : On Monday 12 March 2007 21:43, Peter wrote: I rebuilt my 6.2 system entirely and ran tzsetup. My time is still one hour behind. What else do I need to do? If you run date with no arguments what timezone does it say? If it's e.g. EDT (the D being for Daylight) then all you need to do is set the time manually (assuming you updated in the last 36 hours or so, after the time change). Otherwise I'd start with a reboot and then maybe play with adjkerntz if that doesn't take care of it. I did reboot after using tzsetup. Anyway... $ date Mon Mar 12 21:22:22 EDT 2007 Change time manually you say? Yep! Since you probably had an out-of-date /etc/localtime at the time of the (new) change your system didn't know to change the clock automatically. Going forward you shouldn't need to worry about it (unless lawmakers decide to save even more energy in the future...). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing command-line resolution
On Wednesday 07 March 2007 21:48, frzburn wrote: Hi! I was wondering if there is a way to change the command-line resolution... Back then with Linux, I could adjust the resolution in grub or lilo by passing some parameters to the kernel. Is there any way to do the same thing in FreeBSD? I wouldn't want to waste that big wide screen =P I got a Dell Inspiron 6400 (e1505) with an NVidia video card running FreeBSD 6.2-STABLE amd64. Build and install a kernel with options VESA and SC_PIXEL_MODE. Reboot. Run vidcontrol -i mode. Pick one you like and make a note of its number. Then do something similar to vidcontrol -f 8x14 cp437-8x14.fnt MODE_NNN, replacing NNN with the mode you noted previously and 8x14 with one of 8x8, 8x14 or 8x16. The font file should match the font size and codepage you want your terminal to be in. Repeat until you find the settings you want, then add a line like this to /etc/rc.conf: allscreens_flags=-f 8x14 cp437-8x14.fnt MODE_NNN using the same substitutions. See also man vidcontrol, man sc, and the FreeBSD handbook. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting an FTP space ?
On Thursday 01 March 2007 01:37, Never you mind wrote: On my Mac from the Finder I can select Connect to server, give it the details of an ftp location and it will connect and display the ftp space as a drive on the desktop. Can I obtain the same sort of functionality using freeBSD and xfce desktop manager? I haven't used it, but the sysutils/fusefs-curlftpfs should allow you to mount an ftp location as a virtual filesystem. The desktop icon thing you'll have to work out on your own, but it shouldn't be too difficult (a shortcut to your chosen mountpoint should suffice). JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Future of FreeBSD 7.0 and up
On Wednesday 28 February 2007 14:26, Dwight Smith wrote: My name is Dwight Smith, and I only had a question or two in terms of the future useability of FreeBSD. I have used it on and off and found it to be a great UNIX operating system for servers, but my only major concern was the amount of time it takes to prepare a server such as an Apache Server with PHP and MySQL support as opposed to a Linux system which is what I am currently using now as well as my company. I guess my question is that will the ease of building or installing software for FreeBSD ever streamline to where you do not have to do as many steps and text config file entries? If you don't need any customizations, pkg_add -r packagename will automatically download and install almost everything available in the ports system. It will even get the newest version appropriate for the version of FreeBSD you are running. If you prefer to compile from source or need a non-default setting, going into the relevant directory in the ports tree and typing make install clean will again do everything automatically. In most cases the same command will also present you with an easy-to-use menu of options available for the port, if any. Which of those one-line commands strikes you as being less than easy from the point of view of a systems administrator, developer, technical end-user or Computer Coordinator? If you have concerns about a specific piece of software, sending a message to this or another appropriate list or directly to the port's maintainer will typically yield good information, and if you have ideas for improvements they should be well received in the appropriate forum. What had me curious to asking this is this article I read about a review on FreeBSD 6.2 (http://www.softwareinreview.com/cms/content/view/67/) The reviewer had a lot of criticisms that seemed harsh, but at the same time raised some valid points. I only ask this question as I would like to see FreeBSD get the same recognition as Linux as FreeBSD is a powerful OS that should not be overshadowed and I hope it doesn't cause it saved my IT job many a times when a server crashes and I have to piece together an old PII with 32 MB RAM and install FreeBSD with Samba. So thanks in advance for your attention in this and I wish all of you the best. My initial take on that review is that the reviewer had an earlier bad experience with FreeBSD (perhaps as a result of failing to understand that 5.0 and 5.1 were developer preview releases), tried installing 6.2 once on a single system, ran down his pre-existing checklist of complaints to see if any of them had magically been fixed (as a result, perhaps, of the FreeBSD developer community reading his mind and finding themselves in agreement), did little if any troubleshooting of the hardware compatibility issues he mentioned (even reporting such occurences is a good way to contribute to a volunteer-based project), and wrote the whole thing off as being stagnant. Some of his points and recommendations might have merit, but many seem to be the writer's wishlist for making FreeBSD into something it isn't (some hybrid of Gentoo and Fedora, perhaps). That and his general attitude of hopeless negativism[1] make it hard to take his review seriously. Personally, FreeBSD 6.2 is the best OS I have ever used and I find it extremely well-suited to my needs and tastes for both server and desktop use. The only way to see if that is the case for you is to try it (again). If there are shortcomings, be proactive about reporting them. FreeBSD's user community is one of its biggest strengths. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dual monitors
On Saturday 24 February 2007 23:34, Eric Stringer wrote: I've got FreeBSD 6.2 running with KDE 3.5 with an ATI 9700Pro card. I have my 37 LCD TV attached to the digital out, and my 17 lcd monitor attached to the analog out. In the console (not running X) it outputs the same thing to both TV and monitor, which is fine. However, when I get into KDE it only outputs to my 17 monitor. I really just want it to output to the TV, but dual monitors would be nice also. Any advice would be greatly appreciated. Thanks, Eric Oh yea forgot to post the xorg.xonf file, here it is. Also I have Xorg 6.9.0. Start by reading man 4x radeon and pay close attention to anything it says about MergedFB. Decide if there's any reason you don't want to or can't use that feature of the driver. If not, you probably want to go that route to get the performance bonus. Look around on the web for examples. If you don't end up wanting or being able to use MergedFB then you should use Xinerama (X's multi-head software). You'll need to enable it with something like this: Section ServerFlags Option Xinerama 1 EndSection Then you'll need to add an additional Screen item to your ServerLayout section (and specify the relationship between the two screens), then add additional Device, Monitor, and Screen sections to the file describing your second display. Again, there should be a lot of documentation and examples out there since (as Ted mentioned) this isn't FreeBSD-specific. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: forcing re driver to a card
On Thursday 22 February 2007 16:06, bram wrote:
Hi all,
I've been having some trouble getting my nic's to work under freebsd 6.1.
it's a jetway mini-itx board with a daughterboard with 3 rtl8110S chips on.
two out of the three appear when doing pciconf -lv
[EMAIL PROTECTED]:11:0:class=0x02 card=0x10ec16f3 chip=0x816710ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
class= network
subclass = ethernet
[EMAIL PROTECTED]:12:0:class=0x02 card=0x10ec16f3 chip=0x816710ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
class= network
subclass = ethernet
I think these should be supported by the re driver, so my questions are:
-Is there a way to force the re driver to recognize these cards ?
-Can the source of the re driver be changed so it recognizes the card
(if yes please some guidance, don't know C) ?
The answer to your second question is probably yes; requires someone to make a
patch and test with relevant hardware. Glancing at the code quickly I think
you're probably right that it should be supported by re(4).
The answer to your first question is: patch the source so it recognizes the
card. :)
The good news is that your device already seems to be listed in
src/sys/pci/if_rlreg.h. If that's the case then all you need is a two-line
patch to src/sys/dev/re/if_re.c. Something like this around line 185 of the
file (I'm looking at revision 1.46.2.20) might do the trick:
{ RT_VENDORID, RT_DEVICEID_8169SC, RL_HWREV_8169_8110SB,
RealTek 8169SC/8110SC Single-chip Gigabit Ethernet },
Drop that in the file and rebuild and reinstall your kernel and modules. If
you can confirm that that works then I'd be happy to send in a PR to get it
included.
Solaris has an /etc/driver_aliases file that lets you do things like this
without recompiling anything, but recompiling isn't really too bad once you
get the hang of it. (Especially if you can get away with using modules.)
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vmware Questions
On Wednesday 21 February 2007 20:50, Martin McCormick wrote: If one has a FreeBSD system that has 1 gigabyte of RAM and a 1-GHZ processor, would it be possible to run a couple of vmware instances of FreeBSD? I want to set up a DHCP server on each virtual machine and configure one to be optimized for DHCP failover and dynamic leases while the other is dedicated to static bootp service. It would be much easier for the 2 instances of dhcpd to run in separate machines, so to speak, since they normally use the same named files for logging and configuration. What sort of a performance hit does one usually see on a virtual machine? Depends a lot on the virtual machine. VMware Server runs VM's pretty efficiently, but there is a moderate hit. ESX server has almost n performance penalty. When we run dhcpd on a normal FreeBSD system of the type described above, the system is normally loaded around 0.05 or so so it isn't having to work too hard. Thanks for any help as to what vmware port is best. The platform is FreeBSD and the 2 virtual machines will also be FreeBSD if that makes any difference. Modern versions of VMware don't run under FreeBSD. If you really want VMware then install a supported Linux distro and run VMware server. (Or go out and buy ESX or GSX server or one of the Workstation products). FreeBSD 6.2 works great as a guest under most VMware products. There will be no X windows involved, just hopefully 2 DHCP servers running as if they were on two separate boxes. Any information to point me in the right direction or reasons why this is not a good idea are appreciated. For what you're talking about, jails make a lot more sense than virtualization or emulation. If you really want to run virtual machines under FreeBSD, take a look at qemu. qemu (even with the kqemu_kmod port (highly recommended) definitely has a noticeable performance impact, but DHCP is so lightweight that it probably won't matter. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Backup using dump and restore from dvd - restore cd loaded to ram ?drive?
On Monday 19 February 2007 10:29, Oliver Fromme wrote: [EMAIL PROTECTED] wrote: [...] The restore method will then require to boot from a bootable CD. The rescue CD system should load itself into RAM drive, so that I can dismount it and replace it with the CD/DVDs with the backup files. The rescue CD should provide basic commands and programs like mount*, newfs, bsdlabel, fdisk, vi, restore, gzip, ... I have tried the installation CD with FreeBSD 6.2, but its holographic shell does not have the commands needed and the FixIt shell depends on the CD. Building such a bootable CD is possible (I've done it), but it's not easy. Bascially you have to do it similar to the FreeBSD install CD. I suggest you have a look at it. What you have to do is prepare a kernel for the CD which has the MD_ROOT option, so it can use an mfs image as the root file system. The create such an image and put it onto the cd. On the FreeBSD install CD it is located in /boot/mfsroot.gz (you can uncompress it and then mount it via mdconfig). Actually you should be able to make a bigger mfsroot image and add the tools that you need. However, be aware that the image will eat up physical RAM, so don't be too wasteful. A simpler solution for your restore problem would be to simply use a standard FreeBSD installation CD, then make a minimal installation on your hard disk so you have all the tools that you need, then restore your actual backups. There's a ready-made FreeBSD bootable CD called Frenzy that has an option to load itself into memory. I'd suggest getting the lite (smaller) version so the memory requirements aren't so great. Check it out: http://frenzy.org.ua/eng/ I've used it to do DVD operations under a real OS on a computer that wasn't running one (namely my wife's laptop). Works like a treat. I believe FreeSBIE is planning on adding such a feature as well but I don't think they have it yet. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release 6.2
On Friday 16 February 2007 07:49, York Rapp wrote: I am looking for a DVD Image of Release 6.2 to download, but unfortunately (stupid as I am ;-)) I cannot find it. Can you give me an information or a link of a mirror. The FreeBSD Project distributes releases as a two-CD set. All you need for a basic installation is the first CD. The second CD contains many commonly used packages (in addition to those on the first CD). These are available for download on all of the FreeBSD mirrors and elsewhere. (see http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html) bsdmall.com and freebsdmall.com both make DVD sets (which include many more packages and some other goodies) available for purchase. See their respective websites for more details. It doesn't look like bsdmall.com has a 6.2 DVD available quite yet. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Internet Explorer on FreeBSD
On Friday 16 February 2007 19:32, Chris wrote: Kevin Downey wrote: I do a bit of web dev stuff so it would be nice to be able to see the page in IE. A website I use for work uses ActiveX. I hate dual booting. What is the best(easiest) way to run ie on freebsd? Four ways - in order of ease to hardness 1. Separate box that IS Windows. 2. Dual Boot 3. VMWare (or some equivalent) 4. Wine (God Luck) For current versions of Wine and FreeBSD this definitely won't work (I've tried). If you go back a few versions of one or the other or both there used to be a combination where wine's memory allocation wasn't hosed up under FreeBSD (I think). I don't understand enough about the current problem to say more than that, but there's a fair amount of discussion about it in various places. If you do get a happily functioning wine, there's a nice shell script (requires bash) package that will automatically fetch the IE binaries and dependent packages and set everything up for you. I can't remember what it's called offhand, though. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jailed VPS behind NAT
On Thursday 15 February 2007 14:44, pancho pantera wrote: hello, i don't know where to search for THIS, info about jailed VPS.and secondly handbook and other papers and docs, are some times criptic , because english is not may mother language, i usually speak spanish. usually irtual private servers has its own public internet IP address, but here in mexico this is very expensive. my project is to get just one IP address and put freebsd jails for VPS behind NAT for offer: VPS whit shared IP. something between shared webhsoting and FULL VPS (whit own public IP for each). please letme know where can ia find more info or answer for this topic. Set up NAT as you otherwise would using the real interface and IP as the external network. There are several different methods for doing this, most of which are discussed and mentioned in the handbook. I use ipfw+natd since that's what I'm most familiar with, but pf may be a better option if you're just getting started. Since your internal network doesn't have (or need) a real network interface, use the loopback interface (lo0). Create an alias in the 127.0.0.0/8 network for each jail. You should of course reserve 127.0.0.1 as the real localhost address. Set up the jails as you normally would, using the 127.x.x.x IP's you allocated above. See the jail(8) manpage to get started. There are other howtos and guides out there that might give more background and examples, but the manpage has always been adequate fo my (modest) needs. You might also want to look at the sysutils/ezjail port. See also http://erdgeist.org/arts/software/ezjail/ . Decide how you are going to allocate ports and/or proxy/share commonly used ports. For http and https (80 and 443), consider running Apache with mod_proxy and virtualhosts. Should get you started at least... JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gmirror: degraded, Component ad4 (device gm0) broken, skipping.
On Wednesday 14 February 2007 15:13, Brian A. Seklecki wrote: gmirror insert gm0 ad4 The big question is: In your example, ad4 has already been prepped for use in as a component in the gmirror by ? Or will it just overwrite anything on ad4 regardless? No prep is necessary when using raw devices such as ad4. The insert operation will overwrite everything (or the first $VOLUME_SIZE blocks) on ad4 with the contents of the mirror. Obviously if you want to use only a portion of a drive as a gmirror consumer then the drive should be fdisk'ed and/or bsdlabel'ed and the device name of the slice or partition (e.g. ad4a, ad4s1, or ad4s1a depending) should be used instead of ad4 as the gmirror consumer. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How does gmirror know of a faulty drive
On Wednesday 14 February 2007 15:10, Brian A. Seklecki wrote: On Wed, 27 Jul 2005, Ivan Carey wrote: In FreeBSD 5.3 I have set up 2 drives in RAID-1 format. How will I know if one of the drives is faulty such as either not working or has some lost sectors? Is it possible to have gmirror email me if there is a problem? I just actually replied to a thread about this. Apparently there is no automatic demotion of a device to DEGRADED. I just had a provider error for a good 5 minutes of SCSI kernel messages (bad sectors, grown defects), without any automatic corrective action taken by gmirror(4) In my experience gmirror will automatically detach any consumer that has a hard read or write error. (I haven't had occasion to use gmirror with SCSI devices yet though, so this could just be limited to ATA.) Re: e-mail notification, you can get a daily report if you set 'daily_status_gmirror_enable=YES' in /etc/periodic.conf. If you'd like more frequent checks it wouldn't be hard to put a script together to run gmirror status every N minutes from cron, parse the output and forward it to you if it said anything but COMPLETE for each provider. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad sector on drive ...
On Saturday 10 February 2007 09:47, Marc G. Fournier wrote: --On Saturday, February 10, 2007 01:00:21 -0600 Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Feb 10), Marc G. Fournier said: Short of a reformat, any way of marking the following as bad? :( Feb 10 02:27:20 ganymede kernel: ad4: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=176887263 Feb 10 02:27:25 ganymede kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=176887324 Feb 10 02:27:30 ganymede kernel: ad4: TIMEOUT - READ_DMA retrying (0 retries left) LBA=176887324 Feb 10 02:27:35 ganymede kernel: ad4: FAILURE - READ_DMA timed out LBA=176887324 Try writing to the block causing the error, using dd and the seek= option; if the write succeeds, you're done (and the drive will have either reused the block or reassigned it to a spare). 176887324 If it doesn't succeed, copy what you can off the drive and toss it, since all its spares are used up. I think LBA numbers map directly to seek= values assuming you keep bs=512 and access /dev/ad4 . I'd try reading the bad block with dd to verify it's the right one before doing a write, though. 'k, how do you use dd to write to a specific sector? dd of=/dev/ad4 seek=176887324 bs=512 if=/dev/null dd of=/dev/ad4 seek=176887324 bs=512 count=1 if=/dev/zero JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: is the list the right place to ask?
On Friday 09 February 2007 22:55, Ray wrote: Hello, Just wondering if this list is the right place to ask for suggestions for what package to use for various purposes? Yes it is. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail server recomendations (was: is the list the right place to ask?)
On Saturday 10 February 2007 01:33, Ray wrote: I'm looking for a package (or set of packages) that would provide a mail server with the following capabilities minimally: pop and smtp access that could handle 20 to 100 domains and 200 to 2000 mail boxes.(allowing some room for future growth) SMTP: sendmail is part of the base system and is pretty powerful but has a steep learning curve. There are alternatives available in the ports, one of the more popular being postfix. Others such as qmail may also be worth researching. POP, etc.: I highly recommend dovecot. It's efficient, pretty easy to configure, and can handle almost any setup you can imagine. You also get IMAP with this, which even if you don't want on its own you will want to use with your webmail package. ideally: also provide a web interface for individual users and also for administration on a per domain and whole server level. we have several customers that need to be able to administer their own domains, (Read this as I don't want ten calls a day saying I forgot my password) but we don't want them touching others accounts. Admin: webmin provides a reasonably secure web-based frontend to many different admin. tools and allows you to grant different levels of access to each tool to different users. Virtualmin might be an even better match for what you're after. Webmail: For features, go with Imp and any other parts of the Horde suite of applications that interest you. Horde's groupware package is starting to get pretty polished, and the individual components (mail, calendar, address book, tasks, etc) are all quite mature. Setup and config is a bit on the complex side, but there's work going on there and much of the initial config is now web-based. Other popular and simpler webmail packages include OpenWebMail and SquirrelMail. spam and virus scanning would be a definite plus, but from what I have read, these two parts are fairly straight forward. We have recently changed the web server from M$ to FreeBSD and now we're trying to change the mail server too. Thanks for any pointers or suggestions. I use clamAV on my mailserver, works great and keeps itself up-to-date pretty well. Easy integration with sendmail via a milter. For spam you'll likely want a combination of techniques. SpamAssassin is a good starting point. Also look at the DNS black- or greylisting features of your SMTP program (I use a couple realtime DNS blacklists with sendmail). Depending on the types of messages you're hoping to stop/detect, you might also want to look at MimeDefang. Everything above is in the ports. You have a lot of options so it's just a matter of nailing down what you want in terms of features and then selecting the best tool for the task. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.4 on a Pentium 4
On Thursday 08 February 2007 11:16, Philip Radford wrote: Hi all, Just wondering if anyone could help me out with an issue on FreeBSD which has been puzzling me for a while and only now do I have the time to go and figure it out. We currently have version 5.4 installed but understand that the architecture it is set up for is a generic i386. How do I go about optimising my base system and/or installed ports to recognise my CPU as an i686 and therefore make use of this type of CPU. I have enclosed the first part of my dmesg output to identify the CPU. CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MC A,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs Add CPUTYPE?=pentium4 to /etc/make.conf. Remove the cpu I486_CPU and cpu I586_CPU lines from your kernel config (if present), leaving only cpu I686_CPU. Rebuild your kernel, world, and ports. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Low-cost dedicated FreeBSD server or non-jail VPS?
On Wednesday 07 February 2007 23:10, Peter Clark wrote: Is this up your alley? http://www.johncompanies.com/jc_vps.html I use this service and highly recommend it, but it definitely falls under the jail category. They've modified the stock FreeBSD jails pretty heavily and most of the time it's not obvious you're running in a jail, but if you want to do anything like create virtual interfaces, use your own mountpoints or (as the OP mentioned) experiment with firewall setups you'll be out of luck. JC does also offer dedicated servers on which they're more than happy to install and support FreeBSD, but I'm not sure that meets the low-cost requirement. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.conf ...need help
On Tuesday 06 February 2007 15:58, Don Munyak wrote:
I was tweaking the /etc/rc.conf file and apparently had a typo. Now
the system boots into single user mode. I know what my error is
syslogd_enable=YES {left off the first }
How can I edit rc.conf while in single user mode. I've tried vi ee,
but system doesn't recognize either.
You can mount /usr (assuming that's not related to whatever you're trying to
fix) by typing mount /usr. You'll also need to mount / read/write before
you can modify rc.conf so I usually just do mount -a. mount / will
re-mount / with the default r/w settings.
If you do have a problem with /usr, there are statically linked versions of
both system default editors in /rescue. So you could also
do /rescue/ee /etc/rc.conf, for example.
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with mod_fcgid inside a jail.
On Sunday 04 February 2007 05:38, Vincent Bolinard wrote: I've just tried to run Apache with mod_fcgid 1.10 and 2.0, but it still does not work. Here is the error with 1.10 : [notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin/suexec) [info] mod_unique_id: using ip addr 192.168.1.3 [emerg] (2)No such file or directory: mod_fcgid: Can't create global mutex Here is the error with 2.0 : [notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin/suexec) [info] mod_unique_id: using ip addr 192.168.1.3 [emerg] (2)No such file or directory: mod_fcgid: Can't create share memory for size %zu byte Try setting jail_sysvipc_allow=yes in /etc/rc.conf. (Or you can set the security.jail.sysvipc_allowed sysctl to one, but the jail rc scripts will change it if you use them and don't have the RC variable set.) JN 2007/2/2, Josh Tolbert [EMAIL PROTECTED]: On Fri, Feb 02, 2007 at 10:51:32PM +0100, Ivan Voras wrote: Vincent Bolinard wrote: [emerg] (2)No such file or directory: mod_fcgid: Can't create share memory for size 316628 byte I'm running FreeBSD 6.2-RELEASE, Apache 2.0.59 and mod_fcgid 1.09. Try running v1.10, here's what it says in changelog: 3. Use anonymous shared memeory to make OS X happy. (Thank andkjar at obtech.net for the patch.) Maybe it will help you. Update to 2.0 will be coming soon...Maybe this weekend, if I find some time. I have no idea if it'll fix the problem, but 1.x is dead either way. Thanks, Josh -- Josh Tolbert [EMAIL PROTECTED] || http://www.puresimplicity.net/~hemi/ Security is mostly a superstition. It does not exist in nature, nor do the children of men as a whole experience it. Avoiding danger is no safer in the long run than outright exposure. Life is either a daring adventure, or nothing. -- Helen Keller ___ 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunar with Fluxbox
On Sunday 04 February 2007 08:26, Olivier Regnier wrote: I'm currently running Fluxbox on FreeBSD 6.2. I installed Thunar 0.8.0_1 and icons-tango 0.7.2_3. The problem is simple, when i start Thunar, i do not see the icons and in console, i get an error that says (thunar:1056): Gtk-WARNING **: Error loading theme icon for stock; Icon 'gnome-fs-home' not present in theme What happened ? Can you help me please ? Try installing the x11-themes/xfce4-icon-theme port and/or the misc/gnome-icon-theme port. You should also submit a PR requesting that the needed port be added as a dependency for Thunar so others don't have the same problem. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Determining daylight savings changes on BSD
On Friday 02 February 2007 17:35, Dan Nelson wrote: In the last episode (Feb 02), Robert Fitzpatrick said: On Fri, 2007-02-02 at 10:36 -0600, Dan Nelson wrote: In the last episode (Feb 02), Robert Fitzpatrick said: I use the following command on our CentOS Linux servers to find out if the system is ready for the daylight savings changes coming up, but it does not seem to work the same on our FreeBSD 5.4 and 6.1 servers. How can I do this? I see the zdump command and the man page seems to suggest the same usage, but... esmtp# zdump -v US/Eastern | grep 2007 esmtp# zdump -v US/Eastern US/Eastern Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 20:45:52 1901 UTC isdst=0 gmtoff=0 US/Eastern Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 20:45:52 1901 UTC isdst=0 gmtoff=0 US/Eastern Mon Jan 18 03:14:07 2038 UTC = Mon Jan 18 03:14:07 2038 UTC isdst=0 gmtoff=0 US/Eastern Tue Jan 19 03:14:07 2038 UTC = Tue Jan 19 03:14:07 2038 UTC isdst=0 gmtoff=0 That means you need to update your zoneinfo tables. You can also use the date command to see if you need updating: date -r 1173679260 Yes, thanks, looks like I need to do that, how do I update my zoneinfo tables? Upgrading to 5.5 or 6.2 will get you the new tables as a side-effect of the upgrade :) If you don't want to upgrade, just install the misc/zoneinfo port and rerun tzsetup. The last bit (rerunning tzsetup(8)) is good advice for anyone who hasn't run it in a while. Upgrading from earlier versions of FreeBSD will install the new tzdata files but it will not touch /etc/localtime. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports error (or warning) after cvsup
On Wednesday 31 January 2007 19:15, Petre Bandac wrote: portversion -v | grep [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 16409 port entries found .1000.2000.3000.4000.5000 .6000.7000.8000.9000.1.11000.. ...12000.13000.14000.15000.16000 . done] missing key: categories: Cannot read the portsdb! database file error but it still lists ports; how can the missing key problem be restored ? Same problem here using portupgrade. I ran a make index locally in my /usr/ports directory but the problem persisted.. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading xfce4 fails
On Saturday 27 January 2007 11:21, Warren Block wrote: On Sat, 27 Jan 2007, Markus Hoenicka wrote: I'm having a hard time upgrading xfce4 on a FreeBSD 6.1 box. I've tried portupgrade first, but as it bumped into a boatload of errors I eventually had to resort to upgrade individual packages. This left me with a mix of packages of xfce versions 4.2 and 4.4, and a build failure in xfce4-mcs-manager which I'm unable to resolve: /usr/local/lib/libxfcegui4.so: undefined reference to `xfce_desktop_entry_has_translated_entry' Saw that, or something like it. All non-xfce4 packages which the xfce4 packages depend upon appear to have upgraded ok (or so portupgrade says). Is there anything I can do except waiting for prebuilt packages? pkg_delete or make deinstall everything xfce\* and libxfce\*, then just install /usr/ports/x11-wm/xfce4. From what I've seen so far, xfce4.4 is definitely worth it. I've updated 3 machines so far using portupgrade and haven't had any undue trouble. It went something like this: #portsnap fetch update pkgdb -F pkg_version -v -l '' (my usual upgrade starter) pkgdb tells me a bunch of xfce4 ports are now obsolete. I tell it to try to delete them. It fails. I interrupt it (^C) and manually uninstall the meta-port: # pkg_deinstall x11-wm/xfce4 Then # pkgdb -F again, again telling it to delete the obsolete ports. This time it succeeds. Now the money shot: # portupgrade -rR xfce\* portupgrade -N x11-wm/xfce4 Updates everything and re-installs the meta-port, which has a couple new dependencies. Note that lots of the ports being updated have OPTIONS screens, so either keep an eye on it or run through them in advance (see the archives for scripted ways of doing this). I second Warren's endorsement of the upgrade. :) JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading xfce4 fails
On Saturday 27 January 2007 18:48, Markus Hoenicka wrote: Markus Hoenicka writes: There's one thing broken though: After the upgrade, panel plugins fail to display correct values. The battery monitor claims the battery of my laptop is at 0%. The network monitor plugin also sees the traffic at 0 kbyte/s no matter what I do. The volume plugin displays a value according to where I click in the plugin, but this does not translate to a higher or lower volume. Inversely, if I set the volume using xfce4-mixer, the value is not correctly displayed by the plugin. Did you notice similar problems? Did I miss to upgrade a package that all plugins rely on? Oops... The network monitor and the volume control plugins just required the network interfaces and device settings, respectively, and now work ok. Still, the battery monitor does not. Any clues? There's a PR open for this with a working patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108322 Download it and apply it in the ports/sysutils/xfce4-battery-plugin directory then rebuild the port. It fixed the problem for me. I'm sure it will be committed shortly. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND tool for setting up secondary records?
On Friday 26 January 2007 10:50, Robert Fitzpatrick wrote:
I am not a member of a BIND list, so I thought I'd ask here first if
anyone knows of a script tool that will query a primary name server and
setup secondary records on another BIND server? Or any other solution
for doing mass entries of domains to a BIND server to setup secondary
records with the same primary master?
If you set up a slave domain it will automatically query and stay in sync with
the master nameserver.
I use scripts on both ends for most new domains. Here's the files from the
slave side:
=== begin addconf.sh ===
#!/bin/sh
DATADIR=/etc/namedb/conf
TEMPLATE=/etc/namedb/templates/default.bind
usage() {
echo Usage: $0 \domain.name\ [templatefile]
exit 1;
}
if [ $2 ] ; then
if [ -r $2 ] ; then
TEMPLATE=$2
else
usage
fi
fi
if [ $1 ] ; then
DOMAIN=$1
else
usage
fi
echo -n Configuring ${DOMAIN} using ${TEMPLATE}..
cat ${TEMPLATE} | sed -e s/%%DOMAIN%%/${DOMAIN}/g
${DATADIR}/${DOMAIN}.bind
echo done.
=== end addconf.sh ===
=== begin default.bind ===
zone %%DOMAIN%% {
type slave;
file slave/%%DOMAIN%%.bak;
masters { my.master.server.ip; };
allow-query { 0.0.0.0/0; };
};
=== end default.bind ===
=== begin make-conf.sh ===
#!/bin/sh
inputfile=/etc/namedb/templates/named.conf.in
outputfile=/etc/namedb/named.conf
backupfile=/etc/namedb/backups/named.conf.old
confdir=/etc/namedb/conf
if [ -r ${outputfile} ] ; then
echo Backing up current file to ${backupfile}..
mv -f ${outputfile} ${backupfile}
fi
echo -n Generating ${outputfile}..
cp -f ${inputfile} ${outputfile}
for conffile in ${confdir}/*.bind; do
echo include \${conffile}\; $outputfile
done
echo done.
=== end make-conf.sh ===
For named.conf.in you just want your normal named.conf file that doesn't
include any of the domains defined in ${confdir}. Figuring out the rest of it
I leave as an exercise for the reader, but I'm happy to answer specific
questions.
JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with ipfw flush
On Wednesday 24 January 2007 15:59, Jeff Royle wrote: Jeff Royle wrote: Dan Mahoney, System Admin wrote: In trying to tweak my firewall setup I'm using a file called /etc/ipfw.rules However, it seems even though I copy my rules perfectly to that file, the system freezes up and locks me out when I do: ipfw -f flush; ipfw /etc/ipfw.rules I've also tried doing it as ipfw -f flush ipfw /etc/ipfw.rules But to no avail. if it matters, ipfw is loaded as a kernel module, not compiled in. I haven't used IPFW in a while but if I recall right IPFW has a default policy of drop. So when you flush the ruleset your pass rules are all gone. You could run the command like: ipfw -f flush ipfw /etc/ipfw.rules That should allow you flush and load your ruleset. You may also want to look into changing the default policy to accept. However this may require you to adjust your rules depending on how you wrote them. Opps I am sorry, I got pulled away while reading your original email, guess I didn't finish reading it. I see you are trying . You still may want to look into a default policy of accept for IPFW, this way its a non issue. Three things to remember when modifying ipfw rules remotely: 1) Make sure that you have a way to recover when you lock yourself out. Once you get the hang of it this doesn't happen very often, but it can definitely happen. 2) Put whatever rules you need to access your session at the top of your ruleset. (e.g. allow tcp from any to me 22 and allow tcp from me 22 to any) 3) Make sure to use nohup at the beginning of your reload command(s). It's helpful to make a script that flushes and reloads the firewall so all you have to do is nohup reload.sh. If you use screen or the like you can get the same result. The point is to keep the system from hanging up on you and interrupting your session while you're momentarily not allowed in. Changing the default to accept would alleviate the need for some or all of the above, but I've never thought that to be a good approach in situations where I actually want a firewall. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI not found during install - help!
On Tuesday 23 January 2007 15:32, John D. Reeve wrote: I'm trying to install FreeBSD on a system consisting of an Ampro Littleboard 486 with 32 Mb ram, a built-in Adaptec 6360 SCSI controller, an 18.2 Gb Quantum Atlas III SCSI drive (50 pin narrow), a 256 Mb IDE flash drive containing MS-DOS, and an IDE CD drive. I want FreeBSD to take over the entire SCSI drive. The SCSI drive has been low-level formatted using the software that came with the Ampro for the Adaptec controller. I'm trying to install FreeBSD 6.1 using three floppies (boot, kernel 1, kernel 2) and CD's containing the rest of the system. Sounds like you're well prepared. Here is the problem. After booting with the floppies and getting to the point where I'm supposed to select the drive for FreeBSD, the install program doesn't see the SCSI drive. It does see the IDE flash drive. The odd thing is that under MS-DOS, the fdisk program finds the SCSI drive and allows me to partition it, at least a 230 Mb piece of it. I can format this piece for DOS and copy files to it, so the drive does seem to be working. I have the BIOS configured to see the SCSI as the second hard drive in the system. According to the documentation with the Ampro, the BIOS can supposedly handle drives of this size or larger. DOS just uses BIOS calls to access the hard drive. FreeBSD and other real operating systems that expect decent drive performance use actual real drivers to access the hardware. In this case, the driver you need isn't enabled by default in recent versions of FreeBSD. You most likely want to use the aic(4) driver for your controller. Fortunately for you it _is_ included in the GENERIC kernel, but is just disabled in device.hints. To install, you'll need to escape to the boot loader prompt before the kernel is booted and type something like the following: set hint.aic.0.disabled=0 Then type boot to continue the normal bootup process. This is just off the top of my head and based on the aic(4) manpage and GENERIC and device.hints from my 6.2-RELEASE desktop; I haven't used your controller and I'm not 100% sure of the syntax for the preboot environment. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghostscript device 'gdi'
On Sunday 21 January 2007 20:07, [EMAIL PROTECTED] wrote: My experience with ghoscscript device 'gdi' is that even patched it generates a correct data only for 600 dpi resolution. With -r300' option printer makes pages with large horizontal black and grey stripes. Does somebody use Samsung laser printer and ghostscript device 'gdi' for printing to it? I have a Lexmark E210, which is basically a rebranded Samsung ML-1210. I print to it using Cups and the foomatic scripts/filters and haven't had any problems. I know it uses gs with the gdi device on the back end. I just printed a test page at 300 dpi and it looks fine. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove extra packages and streamline 6.2
On Saturday 20 January 2007 21:15, Joshua Lewis wrote: Hello list, After many days of hard work, a lot of caffeine and not nearly enough sleep I have a working asterisk PBX for my home. I have it working on a PIII 800 with 512MB of RAM and two 5GB drives in a Raid1 config. While this system should suffice I would like to streamline the system a little. I installed a lot of unnecessary applications during sysisntall. Is there a way to figure out what software I don't need. I did a pkg_info | wc -l and found that I have 63 apps installed. I know I don't need a bunch of these but I am afraid to delete random packages. After having a non working phone for two weeks my wife would kill me if I messed it all up again. Any ways I know I don't need xorg any more. I installed it so I could use gastman to try and get my Asterisk config working faster. I never wound up using gastman so now I need to remove it and xorg. But there are a bunch of fonts and docs and things. Is it possible to remove any packages I have not used for X amount of days? Is there some way to figure out what apps I don't need installed anymore? I'm a big fan of sysutils/pkg_cutleaves. It recurses through the dependency tree of your installed ports and shows you the leaf nodes (packages that nothing else depends on). You tell it which ones to get rid of and it uninstalls them and repeats the process until no new leaf nodes are found. I run it every couple months even on systems that don't necessarily need to be streamlined just to keep from updating software I'm not using any more. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
