Re: Double Man Pages...
At 12:40 PM 1/28/01 -0500, Paul A. Howes wrote: >All- > >When I install a machine with a fresh 4.2-RELEASE distro, the "man" command >works as expected. When I use cvsup to bring the machine up to 4.2-STABLE >for the first time, man shows every manual page twice. By that, I mean, the >manual page displays normally, and instead of exiting back to a command line >prompt, the whole thing is displayed again, requiring me to either page >through it, or hit "q" to exit. The "info" command has the same behavior: >The manual page is in the buffer twice, in its entirety. > >Is this a problem others have seen? Or do I just have something screwy in >my configuration? > >-- >Paul A. Howes >[EMAIL PROTECTED] It might mean you have the compressed man page and the uncompressed man page. Do a find on the man page dirs, and see if you got .gz extensions and just normal .1 or .2 extensions. You might be able to fix it by running find and executing a gzip command on them. -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Urgent; stable problem on Intel MB
At 02:46 PM 2/16/01 +, Jeffrey Sewell wrote: >I have cvsup'd daily since Feb1 and recompiled. I cannot get a successful >boot out of any kernel. GENERIC, MYKERNEL, anything. >Mergemaster has been done. > >I have 2 different servers.. one ASUS, one Intel 440bx. Asus builds and >boots fine, however the Intel gets 'Fatal trap 12 caught while in kernel >mode'. Seeing how another Intel user had the same problem it must be an issue. > >Could someone please advise? I have backups and I am currently booting >from kernel.backup (thank the good man above). > >I really wish I could have a successful boot :( > >Jeff. Reseat your memory on that box. -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache show "Exec format error"
At 10:16 PM 3/14/01 +1100, sam wun wrote: >Hi, > >I know this is not an appropriate newsgropu to post this msg, but I would >think >you guys konw more about it. >I got the following error when I tried to execue a perl program with calling >.css file: > >Exec format error: exec of /usr/local/cgi-bin/store/managerstylesheet.css >failed >[Wed Mar 14 22:10:03 2001] [error] [client 192.168.1.1] Premature end of >script >headers: >/usr/local/cgi-bin/store/managerstylesheet.css > >Does anyone know what is this all about? > >Thanks >Sam Sounds like /cgi-bin/ is set as a CGI Executable directory mapped to /usr/local/cgi-bin/, so it is trying to somehow execute a .css file which is normally some cascading style sheet file. .css files are like configuration files for html files IIRC. So that .css file should not be there but should be in the html root somewhere like /usr/local/htdocs/ -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3Ware Error Messages
Hey there, running 4.5-RELEASE-p3 with an SMP kernel, and I cannot believe I did not see this message before. twed0: on twe0 twed0: 229033MB (469060608 sectors) twe0: command interrupt Mounting root from ufs:/dev/twed0s1a twe0: AEN: twe0: AEN: Oh boy, I cannot believe I did not realize this, but the array has been degraded the whole time! Since I am not running STABLE, I do not have ata-control. Is there a way I can find out which drive is bad short of power cycling and taking a look at it? Do those error messages tell me which drive is down? Surprisingly, the performance has been quite excellent for a "degraded" system. I wonder if it is just a dodgy interconnect to the IDE backplane. (Pretty sure we ran into that issue when we were testing here before deploying it. Yes, it is as a colocation facility so I cannot just out right look at it easily. ) Is there a way to nab the status of it short of power cycling it? Maybe I should cvsup to get ata-control... -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3Ware Error Messages
Oh geez, I feel silly responding to myself, but, I found the message earlier up from the dmesg output. twe0: AEN: twe0: AEN: Now the issue, is this ordinal or cardinal? (starting from 0 or starting from 1?) Basically does unit 1 mean the 1st one, or the 2nd one? Looking at the driver code it seems like it means the "2nd" one, but hey better safe than sorry. > Hey there, running 4.5-RELEASE-p3 with an SMP kernel, and I cannot believe I >did not see this message before. > > twed0: on twe0 > twed0: 229033MB (469060608 sectors) > twe0: command interrupt > Mounting root from ufs:/dev/twed0s1a > twe0: AEN: > twe0: AEN: > > Oh boy, I cannot believe I did not realize this, but the array has been >degraded the whole time! Since I am not running STABLE, I do not have ata-control. >Is there a way I can find out which drive is bad short > of power cycling and taking a look at it? Do those error messages tell me which >drive is down? Surprisingly, the performance has been quite excellent for a >"degraded" system. I wonder if it is just a dodgy > interconnect to the IDE backplane. (Pretty sure we ran into that issue when we were >testing here before deploying it. Yes, it is as a colocation facility so I cannot >just out right look at it easily. ) Is there a way to nab > the status of it short of power cycling it? > Maybe I should cvsup to get ata-control... > > -Carroll Kong > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems.
Actually, I was using smartmontools improperly in my tests. It isn't enough to hope to catch a smartd error. It is better to run the long tests with smartctl (forget about smartd) and shut most of the box's I/O down to ensure it completes within an hour or two. I wasn't sure how it worked, until I tried it on a local test host. One of the maxtor disks at the colocation with the 3ware card was failing to complete it's long tests with read errors. This is inline with Jason's postings about how maxtor disk errors can cause a total I/O hang. Note, this is the start of a disk failure, not a total disk failure. Mike's errors occured in a RAID5 DEGRADED mode system with Western Digital disks. I can only assume the 3Ware problem with handling failed IDE disks extends itself in DEGRADED mode as well as NORMAL mode (but with Maxtor disks). I strongly suggest 3ware users check their automated monitoring tools and do periodic smartctl disk checks to verify a disk's health. It is important to remove an ailing disk before a total failure since it can cause a total system hang. The bus issues do not affect us at all, or they should not I have a freak of nature 7450 card which is a 64bit/33 mhz card and no longer available. The issue only affects 66 mhz and riser card users. The bus issues were noted and documented in 3ware's advisories. Depending on when you purchased your card and if it is running at 66 mhz or not. http://www.3ware.com/KB/kb.asp https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf General idea is the older runs of the 3ware card does not handle high speed timings well which was a big problem with riser cards + 66 mhz combinations. You can purchase a special riser card from www.adexelec.com PCITX8-3R This riser card was specially designed by Adex to help resolve 3ware's known issue. Any new 3ware cards should not experience this issue. Unfortunately, this issue is not the same as mine, but I hope this information helps you. (consider purchasing the special PCI riser card with additional resistors). - Carroll Kong - Original Message - From: "Anton Ivanov" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Carroll Kong" <[EMAIL PROTECTED]>; "Jason Thomson" <[EMAIL PROTECTED]> Sent: Monday, September 13, 2004 12:00 PM Subject: Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems. > Hi Carrol, > > Pass this to the list as for some reason it times out my posts to > it. > > We had similar issues with 3ware on riser cards. 8506-8 different > board designs will either hang or not even boot on riser cards > that are not grounded correctly (see if the holes on the edges of > the riser cards are connected to the chassis). It never got past a > 30G transfer. > > After grounding the failures became less common dropping to a hang > after 300-500G or so. > > Without riser cards it does not fail. > > Dropping the bus to 33 (8506-8 a 66 card) also makes it behave (so > far). > > Basically, it is the most fussy adapter I have seen so far in terms > of bus noise requirements (we have observed the failures under all > OSes we use so it is not an OS issue). > > Brgds, > > A. > > On Thursday 09 September 2004 23:04, Carroll Kong wrote: > > Well, I tried your command first to see if we could > > get a quick "test". It ran for about 30 mins, I re-ran it on > > another partition, and I even ran another instance of it on yet > > another partition. It kept going. > > > > Then we ran some very file intensive (updates hundreds of files > > in a lot of different directories) and it seemed to stall my > > writes to the /var partition, which in turn broke one of my > > instances of dnscache, which then snowballed until doing tail > > /var/log/messages would hang the zsh completely. > > > > I am thinking it "might" be because we have not done array > > integrity checks yet because our firmware is so old and the old > > 3dm does not support it. > > > > Throughout the entire time, smartd was runing and reported two > > more errors on one of the disks, but nothing major. I am not > > 100% sure if there was as correlation between those errors and > > the ultimate meltdown > > > > I retested this again, I was able to get it to hang again. I am > > beginning to wonder if the other things I use could play a role > > in this. > > > > - using vnode backed disks/partitions > > - using jails > > - using a pci riser card (my 7450 is 64bit/33mhz, the problem > > does not apply to me) > > however, there is a slight chance that maybe my riser card isn't > > seated as well? Really trying to grasp
Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems.
Got the 3Ware 7450's firmware upgraded. Swapped out the one maxtor disk that showed some errors, reran the smartctl -t long tests and made sure every disk succeeded. The box still randomly hangs and it looks strongly like it is I/O related. I wonder if my controller itself is bad. I am about ready to give up on this setup. Problem is swapping out the card means a new riser card, well at least in theory to handle the 64 bit / 66 mhz issue with risers that 3ware has. Or I can trust 3ware's tech support that all new cards are already fixed. Heh. Or we can watch as nothing else is fixed. Or maybe it's the interconnects, (cold swap ATA backplane) but I do not see how that should lead to a full fledged I/O hang error. twe0: <3ware Storage Controller driver ver. 1.40.01.002> port 0xc800-0xc80f mem 0xfe00-0xfe7f,0xfeaffc00-0xfeaffc0f irq 2 at device 7.0 on pci1 twe0: 4 ports, Firmware FE7X 1.05.00.068, BIOS BE7X 1.08.00.048 - Carroll Kong - Original Message - From: "Carroll Kong" <[EMAIL PROTECTED]> To: "Anton Ivanov" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: "Jason Thomson" <[EMAIL PROTECTED]> Sent: Monday, September 13, 2004 11:57 PM Subject: Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems. > One of the maxtor disks at the colocation with the 3ware card was failing to > complete it's long tests with read errors. This is inline with Jason's > postings about how maxtor disk errors can cause a total I/O hang. Note, > this is the start of a disk failure, not a total disk failure. > > The bus issues do not affect us at all, or they should not I have a freak > of nature 7450 card which is a 64bit/33 mhz card and no longer available. > The issue only affects 66 mhz and riser card users. > > The bus issues were noted and documented in 3ware's advisories. Depending > on when you purchased your card and if it is running at 66 mhz or not. > > http://www.3ware.com/KB/kb.asp > https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf > > General idea is the older runs of the 3ware card does not handle high speed > timings well which was a big problem with riser cards + 66 mhz combinations. > You can purchase a special riser card from > > www.adexelec.com > > PCITX8-3R > > This riser card was specially designed by Adex to help resolve 3ware's known > issue. Any new 3ware cards should not experience this issue. > > Unfortunately, this issue is not the same as mine, but I hope this > information helps you. (consider purchasing the special PCI riser card with > additional resistors). > > > > - Carroll Kong ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 3ware & Maxtor problems
https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf Recheck this URL > > http://www.3ware.com/KB/article.aspx?id=10964 Well, I think some people just get the error, even without the riser cards. So, either you replace your motherboard or replace your 3ware card with one that has noise immunity, or try to run the slot at 33 mhz instead. Call them up about it, as it is a well documented case, they probably should not give you the run around on it (like they have for me). - Carroll Kong - Original Message - From: "Philip Jenvey" <[EMAIL PROTECTED]> To: "Carroll Kong" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, September 28, 2004 7:47 PM Subject: Re: FreeBSD 3ware & Maxtor problems > Carroll - > > Sure, I've cced -stable. > > I am actually using the card on a 66mhz bus (no riser card), and I just > noticed the Knowledge Base article before you mailed me back. The PDF > link you posted is broken. > > Is an RMA necessary in my case? It appears they are providing a > firmware upgrade that's supposed to take care of the problem (and my > firmware is older). Installing that is my next step. > > > On Sep 28, 2004, at 4:36 PM, Carroll Kong wrote: > > > Is it okay if I cc this to the mailing lists? I think a lot of people > > might > > benefit from this. > > > > - Original Message - > > From: "Philip Jenvey" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, September 28, 2004 6:52 PM > > Subject: FreeBSD 3ware & Maxtor problems > > > > > >> Carroll - > >> > >> I noticed your postings re your RAID with Maxtor disks. > >> > >> I'm having similar issues, with a 8506-4LP + 4 Maxtor DiamondMax 9 > >> 160GBs. Basically I've been getting some kind of drive error that > >> typically leads to the system hanging, and causes the RAID to be > >> degraded upon reboot. Most of the time I've been able to rebuild and > >> continue on. > > > > If you are using it in a 66 mhz slot, that is probably your problem > > right > > there. If you are using riser cards, and the controller card was > > purchased > > before Q1 2004, then you need to buy a new riser card. There is a > > physical > > bug with the card handling 66 mhz properly. Even if you directly > > connect to > > the system, you can run into issues if the system mobo supports 66 > > mhz. I > > believe they will accommodate RMAs in this case. > > > > https://www.3ware.com/kbadmin/attachments/T...20Rev%20A_P.pdf > > http://www.3ware.com/KB/article.aspx?id=10964 > > > > Now, if none of that appiles to you, then the problem continues > > > > http://forums.storagereview.net/index.php?showtopic=14162 > > > > Scroll to the last message. > > > > Implicitly they are saying that a lot of CRC errors can cause the > > drive to > > "drop a drive" from the array. In my case, I am using an older ATA > > backplane which only supports ATA/33... I am suspecting the CRC errors > > are > > related to my backplane. I am getting it swapped out tomorrow, so > > hopefully > > that will resolve that issue. If not, I have to keep replacing > > parts... > > such as my controller card itself and/or the riser card (even though I > > am > > not affected by the 66 mhz issue). I do get random harddisk dropping > > out of > > my array. I am suspecting that if my controller gets one of these > > major > > drop outs during operation, it probably can result in a hard hang. Bad > > cables can cause this problem as well. > > > > Random loss of power to the disk might cause it to drop out of the > > array as > > well. > > > >> What's the latest you've found on this issue? > >> > >> I noticed you were playing with the smart monitoring tools, have they > >> shed any light on the subject? I'm planning to try them but this RAID > >> has been down for about a half day now (at this point I'm not sure if > >> a > >> drive is dead or what, I seem to be getting errors on 2 different > >> drives now). > > > > Smartctl helped me pre-emptively remove some disks that was failing, > > however, that was not the problem. Even after removing one bad disk > > and > > rebuilding the array, I still ran into the same problems. > > > >> Have you contacted 3ware at all about the problem? > > > > I have recently contacted 3ware by emailing the result
Re: 3ware raid
Interesting. I have 3 3Ware 7xxxs. (2 7500-4LP, 1 7450) The 7450 one on a busy server is experiencing some pretty nasty problems. You can google for the thread with this subject. 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problem So far, once we backed off on the I/O load and as a result, the system has been running solid. I have not fully identified the problem, but I here is a list of things to watch out for 1) Do not use "hot swap"/"cold swap" systems. I agree with Mike now, and I believe I am paying the price for using a cold swap system. We plan on replacing the IDE backplane in hopes that it will resolve the issue. I am guessing nice swap systems are reserved for SCSI SCA for now. 2) Avoid using riser cards if you can. 3Ware claims to have fixed their issues, but put up the usual "cover your [butt]" disclaimers. Better safe than sorry, avoid using a riser card if you can. 3) Avoid using Maxtor disks with it. Yes, I know a lot of people have it working fine. Heck, my 2 7500-4LPs are working fine with Maxtors throughout. (2 in RAID1 under Win2k, 4 in RAID10 under FreeBSD 4.X) But, if you have a choice why risk it? 4) Monitor the system carefully. Apparently in DEGRADED mode, the system has a high chance of complete lockups if left unattended. It is important to note that the 3Ware controller is very sensitive. People have gone into DEGRADED mode randomly because of slight power drops or "bad" IDE cabling. Of course, your mileage may vary. I will let you know if the backplane swap out fixes everything. For now, we want to enjoy some real uptime and hold off on the upgrade as long as we can. - Carroll Kong - Original Message - From: "Mike Tancsa" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 26, 2004 5:10 PM Subject: Re: 3ware raid > At 04:30 PM 26/10/2004, Darren Pilgrim wrote: > > > Hello > > > > > > I was wandering if anybody out there has had any success using 3ware > > > 7506-8 cards with Freebsd 4.10. I was previously using a Promise > > > controller SX6000, and was having problems with this card. > > > >This is something of a FAQ. > > > >There's a long list of people using 3ware 6/7/8xxx series cards in FreeBSD > >4.x boxes with great success. AFAIK that extends to 5.x as well. > > Yes, I am one who always seems to pipe up. I use this very card > specifically on a busy pop3/imap server. The mail spool is made up of 4 > drives in RAID10 and 2 other ports are used for the base OS in RAID1. Its > been in service in this config for over a year without issue. > > When it comes time to replace bad drives, all has worked as expected for > us. We dont use hot swap trays (dont really trust the electrical design of > many of them), so we do it while powered down. Literally, shutdown, pull > the bad drive, put in the new, go into the BIOS (or you can use the cmd > line tools), add the new drive to the RAID set, exit out and let it boot > and thats it. The controller rebuilds in the background and notifies you > when done. > > There were at some point a bad batch of 7000 series cards that needed to be > RMA'd (perhaps 2+ yrs ago now ?). But other than that one time hardware > issue, they work great on all the platforms we have (i386 on FreeBSD, > Linux, Win2k). > > We also use most of the other cards, except for the 9xxx series which we > have no experience with yet. > > ---Mike > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3ware raid
Well, in the normal cases (where the disk is legimately dying) you can usually replace it and be okay. (recalling one instance from the massive thread regarding a 3ware 7506 with maxtor disks that had issues but once they replaced bad disks they were a-ok). You can use smartmontools to help you run tests on the hdds under a 3Ware controller while still in FreeBSD. It works in 4.X (with the latest snapshot of smartmontools). In the other cases where the disk appears fine, but still randomly pulls disks into DEGRADED mode, you have to find out why. In some cases it's because the power drop is too significant, which means you need to swap out your power supply. In other cases, the IDE cabling is legitimately bad (in my case, I highly suspect it is the IDE backplane, which is part of the disk-to-controller data path so I put bad cabling in quotes there). In short, 3Ware makes a note that you must ensure the entire data path is squeaky super clean. Of course, the problem could be the controller itself... 3Ware claims it takes a lot of punishment to DEGRADE the disks. There are some procedures to pull out the extended diagnostics from 3Ware controllers via the 3ware command line utility and if you send them to 3Ware they can try to tell you more information. In my case, 3Ware copped out and gave me some BS excuse for why my system had issues. - Carroll Kong - Original Message - From: "Marc G. Fournier" <[EMAIL PROTECTED]> To: "Carroll Kong" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 26, 2004 6:27 PM Subject: Re: 3ware raid > On Tue, 26 Oct 2004, Carroll Kong wrote: > > > 4) Monitor the system carefully. Apparently in DEGRADED mode, the > > system has a high chance of complete lockups if left unattended. It is > > important to note that the 3Ware controller is very sensitive. People > > have gone into DEGRADED mode randomly because of slight power drops or > > "bad" IDE cabling. > > How do you test (and fix) something like this? revive the drive and hope > the same drive doesn't happen again? > > > > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NATD 3.2-Release Issues?
Hi guys. I have been using 3.2-Release for quite some time now as a natd. Normally I have no problems with this setup at all. However, I just realized, after perusing my logs, I have been getting this error. Jul 18 17:58:41 daemon natd[107]: failed to write packet back (Host is down) Jul 18 17:58:41 daemon natd[107]: failed to write packet back (No route to host) Jul 18 17:58:45 daemon natd[107]: failed to write packet back (No route to host) (I only greped for natd in this case, it naturally has the 'last message repeated' for quite some time in between logs) Normally I get this error when my 'cable' modem goes down, so it makes sense that there is no route to host. However, as I checked the more recent logs. Jul 25 00:06:07 daemon natd[107]: failed to write packet back (Host is down) Jul 25 00:06:12 daemon last message repeated 3 times Jul 25 00:45:30 daemon natd[107]: failed to write packet back (Host is down) Jul 25 00:51:54 daemon last message repeated 18 times Now, this error is a bit different. There is no '(No route to host)' error this time. And, I get this error yet the cable modem interface did NOT go down. I do not think I changed anything significant, however, I did add these kernel options around the '5th of june'. pseudo-device bpfilter 4 #Berkeley packet filter #NATD options IPFIREWALL options IPDIVERT #DUMMYNET options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 options DUMMYNET options NMBCLUSTERS=1024 #SOFTUPDATES options SOFTUPDATES #NCFTPD SHARED MEM #optionsSHMMAXPGS=1024 #SHARED MEM OPTIONS FROM LINT options SHMALL=1025 options "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=33 options SHMSEG=9 Ok. Now, I do use dummynet, however, using ipfw show, there was no usage on that particular "pipe". The machine has maxusers set to 128, and is a k6-200 with 32 megs of ram, using Dec PCI nics (two of them), on an asus97-XE, TX Chipset. I really think the issue is software based over hardware since previous logs did not have such a "large" amount of this natd failure to write back. (previous to the 5th of july which was the last time I modified my new kernel file). I also run these services on top of the standard ones, like apache13+php3 with ssl, and I added my own loadable module, mod_fastcgi, mysqld, postgresql, ncftpd, socks5, sshd, with the default tcp wrapper, telnetd, and ftpd. (Hm. I could eliminate running mysqld, even I only have 32 megs of ram, my machine 'does' seem ok with the 'load', Kudos to FreeBSD power!). Now, I highly doubt if I just remake world it will 'fix' anything, however, I am ready to remake world since I am using 3.2-RELEASE. However, I was not aware of any significant fixes done to natd code during this time. (sorry if I missed it, by the way, is there a direct listing of fixes that grows as we progress through stable? I know it is cumbersome though, and we must as well just add the list in each release, but just curious for convenience sake). Ok. So, are any of my options somewhat "limiting" and causing a pipe to be full or something odd like that? Or is this a known problem and I should consider getting my machine 'synched' with 3.2-STABLE? It has to be my kernel setup or a 'bug' that has been squashed some how, right? On the side, could it be my bpf filter is not high enough? I do use dhcpd, but I only host maybe 3 clients. (they are not always even on all the time). Thanks in advance, I am sure we can find a solution for this problem. -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Will Dump, backup to a file?
Hi. I am using FreeBSD 3.3-Release, and I wanted to know if I can do this dump -0 /opt/tmp/varback.dmp /var (where /opt/tmp is some other free slice) The situation is, I have an old celeron machine, and we are getting a new server. However, we want to move the freebsd setup we have from an ide drive to the new scsi drive we are getting. We do not have a tape backup. We just want to copy from one harddrive to another. So, my original plan was to boot back up with the old ide drive on the new server, either using cp -aR or tar the old file systems into the new drive which we will mount. Or, just reinstall a fresh freebsd setup on the scsi drive, and copy back the old data. However, dump seems to be the real answer here, however, everyone seems to talk about how it works on tape drives. I dont' want to see it wipe out any of my file systems, so I want to make sure this will work. Even though everything in UNIX is a file, I am not sure if it will work? Thanks in advance. -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Popper
At 07:17 PM 2/12/00 +0100, Brad Knowles wrote: >At 8:42 PM +0200 2000/2/10, Yiorgos Adamopoulos wrote: > >> You can use UW-IMAPD which comes with an IMAP and a POP3 server (imapd and >> ipop3d). If you want better performance than that of using the >> standard unix >> mbox format, then you should convert to the mbx format. > > Where would one find out information regarding the differences > between mbox format, mbx format, MH format, and Maildir format? I've > heard of three of these (mbx is new to me), and I think I'm familiar > enough with at least two of them, but I'm curious. > > In particular, I'm interested in finding out more about > performance of the various formats, and what kind of evidence there is to > back those claims up. > > > Thanks! >|o| Brad Knowles, <[EMAIL PROTECTED]> Belgacom Skynet NV/SA |o| mbox is probably the most popular, but not reliable. (one huge contiguous file for messages for a user). not sure on the others... Maildir is probably the most reliable and least popular. Every email message is broken into a file. http://www.qmail.org/man/misc/INSTALL.maildir.txt One big disadvantage with Maildir is since every message is a file, it takes up at least one inode. However, since harddrives are pretty cheap nowadays, I do not see this as a big deal at all. Another disadvantage is the "lack of support." So you are restricted in the pop3 you can use and the imapd you can use since you need one that understands Maildirs. There is some movements for support in these areas though. www.qmail.org -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready...
>At 11:11 AM 4/3/00 +0200, you wrote: >Moral of the story. It is plain untrue that Windows sees all hardware in >a straightfoward way. One may need to fiddle very much with BIOS settings >and it is very long and guesswork, involving a lot of reboots. It is much >easier to use tools such as pnpdump (linux) or pnpinfo (freebsd) and >issue the proper configuration commands. Having an automatic procedure is >nice, if it works. But there is no insurance that it will work even under >Windows and with the manufacturer provided drivers. >-- > >Michel TALON This is why I refuse to buy motherboards that do not allow pci slot irq level control. Asus boards tend to do this well, so I can usually force everything in the proper irq setting and / or reserve irqs and dmas for non pnp devices. Well, it sounded like you had a few pnp isa nics, I only worked with the sound blaster awe 32 pnp. I usually turn off Pnp OS in the Bios. I multiboot windows 95, 98, windows NT, linux, and FreeBSD. My pnp devices work fine, nothing every barfs. I have seen people getting motherboards without pci slot irq level control and they got to do the "magic shuffle" like what you did. It is unfortunate, but I think most "big name vendors" do not supply motherboards with that kind of feature. Ah well. Trouble for them, fine for my own machine. Actually this confuses me a bit. So, if I say pnp os no (which is what has been so successful for me for a while), FreeBSD's kernel will still use the bios to figure out how to dish out what resources? Will it take into consideration what my bios said? So far it seems to (my pci slot irq level control settings). -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
