Re: Sorry had to post this
On Tue, Jun 19, 2001 at 11:18:22PM +0530, Angshuman Dasgupta wrote: > The problem is not with my mailer but with the original poster's mailer. My mailer >is mutt + vi which doesn't insert stupid newlines into a line to break it up. If your mailer doesn't break lines up, then you do have a problem. It is bad email form to keep messages as one big line. The problem is that recipients, with clients like mutt or pine, will insert a break at the character that touches the end of the line, rather than go about it intelligently. Then you might wind up with lines that look like such: My mailler is mutt + vi whic +h doesn't insert newlines i +nto a line to break it up. It is th sender who is responsible for breaking messages into an orderly block of text, not the recipient. And newlines used for this purpose aren't "stupid," they are necessary to preserve the sanity of email, and its readers' good moods. As you will see above, mutt also chokes on your unbroken line, because it puts a reply arrow at the beginning of the line only. If you have color enabled, you will see the first line of your reply text is green, but the second is not. Certainly it is easy to make out what is what, but this is not the case in long messages. It makes for rough reading. If you use vim with mutt, you can set the vim arguments to be + -c "set textwidth=72" -c "set wrap" and it will wrap characters with the generally accepted standard 72-column width. This will help maintain your good reputation on mailing lists like this. There are many (myself included) who simply ignore unwrapped messages, because reply text becomes a nightmare. Yours is the only exception I've made in a number of months. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: natd blues
On Mon, May 21, 2001 at 09:14:36AM -0400, Normand Leclerc wrote: > It looks like my natd is slowing down my cable internet transfers. > When running, I can't get the speed I get when natd isn't around (tested > downloading 20 megs with natd diverting packets from gateway and then > tested with an extra ipfw pass all rule before divert). With divert, > ETA is around 30 mins, without: 8 mins! And I tested it more than once. > >I didn't have this kind of slowdown on 3.4 ... Is there a kernel > option that can slow down ipfw diverts like that? > > Normand Leclerc > [EMAIL PROTECTED] I have no such trouble with natd; I am running 4.2-STABLE from 3-4 months ago. My firewall is a P90 with two $15 NICs, 32M RAM. Please post a complete listing of your ipfw ruleset, as well as the arguments you use with natd. I would suspect a bad rule somewhere in your chain rather than a problem with natd. Also, please explain in detail how your network is configured. Describe the client machine, the gateway, the cable modem, client IP address, gateway IP address, and anything else that even seems *remotely* relevant. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ports-supfile (-picobsd -science)
On Tue, Apr 24, 2001 at 08:36:24PM +0200, Andre Goeree wrote: > [output from CVSup logfile] > Exchanging collection information > Server message: Unknown collection "ports-picobsd" > Server message: Unknown collection "ports-science" > [snip] > Skipping collection ports-picobsd/cvs > Skipping collection ports-science/cvs > > Are these collections not enabled yet? > Would specifying ports-all instead of the seperate collections make > any difference? > > -Andre. I've never heard of a ports that have anything to do with PicoBSD; PicoBSD itself is part of the main source tree (/usr/src/release/picobsd). As for ports-science, I have a ports/science directoy in the tree... Yes, specifying ports-all will get everything the tree has, without breaking. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Click on to meet someone you Click with
On Sun, Apr 22, 2001 at 07:20:13PM -0500, ben hubbard wrote: > This may be way out of left field, but I was thinking about it last night > > Would it be possible to filter the mail in anyway with the mail list software > at freebsd.org based on the subject lines? For example, for this message, the > subject line would be > > Subject: [freebsd-stable] Re: Click on to meet someone you Click with > > or some variant. If it didn't have the [freebsd-stable] (change for whatever > the list address was) then the the reply bounces with a polite "you need to > put in your subject line" message to the original sender. This would > stop the spam (since they usually have specific subject lines) and it would > also (added bonus) make it easier for those of us that filter the incoming > traffic from multiple lists to plop it all in the right folders. > > the flip side is that this adds complication. But is it really all that bad? > If someone has to go find out the list address already anyway, they can read > another line about the subject line, or worse, they just get the bounce back > and get to send it again. Might also stop the various subscribe messages that > end up in the list, too ;-) > > Of course, this may not be possible with the lsitserv software - it's not > something I've ever worked with to any great extent before. With mutt, to reply to this message, I press "g", hit enter, hit enter again, press "y", then type my response. In order to get a "[freebsd-stable] Re: ..." subject, I would have to press "g", hit enter, hold down the arrow keys until it reaches the front of the subject line, type "[freebsd-stable]", hit enter, press "y", then type my response. The arrows and addition more than quadruple the time it takes me to start typing a response. Plus, I would have to clean up old subjects, lest to get "[freebsd-stable] Re: [freebsd-stable] Re: [freebsd-stable] ..." ad nauseum. What you would find after a short time is that the most helpful people--the people who answer many questions every day--will stop responding as frequently. The overall usefulness of the list will decline. Also remember that a great deal of spam (at least most of the stuff that comes to me) has my name as a greeting in the body, or in the subject line. It would be trivial to automate the process of adding [freebsd-stable] to the front of the subject line when the message is sent to [EMAIL PROTECTED] This would have us all working extra for no reason. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-RELEASE: One final delay
On Fri, Apr 13, 2001 at 06:05:28PM +1000, Robert wrote: > I agree entirely. Better to be certain than rush something out the door. > > Robert > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of bsddiy > > Sent: Friday, 13 April 2001 5:03 PM > > To: [EMAIL PROTECTED]; Jordan Hubbard > > Cc: [EMAIL PROTECTED] > > Subject: Re: 4.3-RELEASE: One final delay > > > > > > Delay is good. > > We are very pleasant with your wonderful work. > > > > Thanks, > > David Xu As long as my supfile says RELENG_4, I don't really care if it's called -RELEASE, -STABLE, -RC or -BETA. Hell, you could call if -SHITPILE, if you really wanted to. Just keep providing a stable BSD platform, and I'll keep contributing in any way possible. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disklabel 101?
On Mon, Apr 09, 2001 at 09:16:51AM -0700, David Wolfskill wrote: > OK, since folks are comparing unusual disk layouts, here's one I've been > using on my laptop for the last few weeks (since I got it). Now, this > isn't something that you can tell sysinstall to do directly; more about > that should be at http://www.catwhisker.org/~david/FreeBSD/laptop.html. > > It should also be understood that I'm tracking both -CURRENT and -STABLE > on the machine; that I'm working (as time permits) on some code that > will permit the space pointed to by the 4th MBR "partition table" entry > to be used as a "suspend to disk partition". I just finished building > -CURRENT for today, and did the multi-user boot, so that's what it's > running at the moment. (I'll probably switch to today's -STABLE shortly > after posting this.) > > As in Mike's case, I share the swap space among the kernels; I also share > /var and /common -- basically, everything on what the 3rd "partition tabel" > entry points to. /common is where /usr/local points, as well as /home. > And /usr/obj in each case is a symlink to /common/*/obj (where "*" is one > of "C", "S1", or "S2"). /common/cvs is where I keep my CVS repository. > > It seems to be working OK for me so far. :-) > Well, I'll throw my config in the ring too. My 20G drive is sliced in two, with s1 being 7.5G, and s2 being as large as the rest of the drive. On s2, I have a 250M /, 200M /var, 100M swap, and the remainder (about 10G) as /usr. s1 contains only one partition, /usr/home on ad0s1a. I never saw the need for a separate /tmp, especially since every partition has soft updates enabled. /usr/home is located elsewhere because I switched to FreeBSD from Linux, and I wanted to devote my entire disk to FreeBSD. When I had Linux across the entire drive, I packed it into the first 7.5G, made a BSD slice in the upper region of the drive, installed it, copied my data over from Linux, wiped out Linux, turned the free space into s1, and made that /usr/home. It needs to be 7G for my MP3s. :) I like this. Since /usr always has about 7-8G free, any time I need a new operating system, all I need to do is move /usr/home onto /usr¸ and I have 7G to play with. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Network performance question
On Sun, Apr 01, 2001 at 02:45:16PM -0400, Jason T. Luttgens wrote: > -Original Message- > From: Mike Smith [mailto:[EMAIL PROTECTED]] > Sent: Sunday, April 01, 2001 1:25 PM > To: David W. Chapman Jr. > Cc: Jason T. Luttgens; [EMAIL PROTECTED] > Subject: Re: Network performance question > > > > > FreeBSD kinda disappointed me. It gets ~1000 interface errors on about > > > 514000 packets. I switched the 3COM card out for a NetGear FA311 (sis > > > driver). After receiving ~31 packets, the network goes down (can't > > > ping/telnet anywhere). At that point I have to ifconfig down and up the > > > interface to get it back. > > >You're disappointed in *FreeBSD* because of this? These are *hardware* > >failures you're describing here... > > Hmmso the Linux 2.4.3 kernel is somehow accessing the hardware as to not > cause hardware failures then? That's not it at all. Remember, FreeBSD and Linux can grab packets just as fast as they come into the interface... the processor is many times faster than the network card. This is definitely a hardware issue, packets are coming too fast to handle. I'd be willing to bet that Linux simply ignores the interface errors, rather than reporting them. I think what you're seeing is not that Linux handles networking better than FreeBSD, but instead that FreeBSD is more verbose in its error reporting. The important thing to remember here is that the card--not the OS--determines whether or not to drop packets. Even at 100 Mbps, a typical processor only has to poll the card 1/10 to 1/8 of the time in order to catch every bit coming in. I should point out that virtually every real-world networking test shows FreeBSD outperforms comparably configured Linux. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Trouble with audio discs and burncd
I created a wav file using mpg123's -w switch. When I try to burn it to an audio cd using `burncd -f /dev/acd0c audio file.wav`, I get the following output: >next writeable LBA 0 >writing from file file.wav size 79051 KB >only wrote -1 of 37632 bytes When I try to burn it to a data CD using `burncd -f /dev/acd0c data file.wav`, it burns just fine. This suggests that there is a bug in the way burncd handles audio file processing, not in the delivery of the data to the drive. Does anybody know of this problem? Is there a fix? As reported by dmesg, I have the following CD-RW drive: > acd0: CD-RW at ata1-master using WDMA2 Thanks. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Multihead XFree86
Hello. XFree86 4.0.x is... buggy... with my i810. 4.0.2 starts up fine, but after switching consoles, and going back, the video is garbled and I must reboot to fix it. I still have keyboard functionality, since ctrl+alt+del does what it is supposed to, but the video is gone. 4.0.1 is just crashy, and while I was on an xterm-opening craze to see if I really had more than 31 ptys, I got it to garble my video and reboot itself uncleanly. I want to go back to 3.3.6, but I need help with dual head. I think XFree86 3.3.6 supports the i810, even in FreeBSD. In addition to the i810, I have an ATI Xpert 98, which is a Mach64, definitely supported in 3.3.6. Does anybody know how to configure multihead systems with xfree86 3.3.6? Can I still use the screen/server configuration and the "Rightof", "Leftof", et al., or any other method of making two screens behave as one? Xinerama isn't a concern, since my window manager of choice does not support it. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: top/systat
I'm probably going to make an ass out of myself¸ which has certainly happened before. Still, a disclaimer: I don't know what I'm talking about. Take everything I say with the whole canister of salt. As I understand it, a symbol describes the relative entry point of a function in a given block of code, so that programs know where to find the functions they are looking for. Without symbols, programs have no idea where to find functions in other programs. By removing the kernel's symbols, you are saving some space. However, you are also cutting away anything that isn't absolutely essential to running the system. When you try to run top, it looks for the symbol that represents nlist, and when it can't find it, it doesn't know where to find the nlist kernel function. I'm guessing nlist has something to do with a process list... hence, when top can't find nlist, it throws a fit. Please let me know how wrong or simplistic this understanding is... Now I'm curious, too! On Fri, Mar 09, 2001 at 03:32:10AM -0500, Mikhail Kruk wrote: > btw this doesn't seem to make sense. I'd appreciate if you point me to > something that would clarify this to me. I don't understand how top and > friends use the symbols in kernel and I feel that I would like to know > that. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ABIT KT7 and temp monitoring
You do have smbus and all that good stuff in your kernel, right? Without that stuff in my kernel, lmmon tells me my processor runs at 255 degrees C, and the fans spin at 0 rpm. With that stuff in, my kernel panics. :| On Thu, Mar 08, 2001 at 03:31:33PM -0500, Lee Cremeans wrote: > Has anyone been able to get healthd or any of the temperature monitoring > tools in ports/ to to work on a ABIT KT7? I tried both, and neither can find > the chip on my board (healthd dies, the other utility gives me bogus data). > Any ideas? I'm running FreeBSD 4.2-STABLE. > > -lee > > -- > ++ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | > | [EMAIL PROTECTED] | http://wakky.dyndns.org/~lee | > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Typo in pkg_check(1) manpage
A minor error, to be sure, but still something that can be corrected. When I call up the manpage for pkg_check(1), it calls up the pkg_sign(1) manpage, which describes usage for both programs. The problem is under the "NAME" section, where it says: "pkg_sign, check_sign - handle package signatures" However, it ought to read: "pkg_sign, pkg_check - handle package signatures" The program check_sign doesn't even come on my system. :) -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Oh no...
Of course, this won't help you now, but it serves as a clever warning. Regardless of your backup procedure, it is always wise to make a backup copy of your boot sector. In fact, as well as on another disk, I believe you can store a copy on the disk in question itself. Between the MBR and the first partition, there is a section of null space. If it is big enough, one can use careful math to place a copy of the bootsector in the gap. A few seconds with dd and you would have a working system right now. :) Sorry, and good luck. On Wed, Mar 07, 2001 at 07:01:36PM +1100, Kal Torak wrote: > Hiyas... > > I kinda did a fdisk -BI on my main HDD by accident... It killed > all my partitions... I tried to get them back with sysinstall and > the live file system, but I cant mount them and stuff... > > Is there some way I can get my data back? I dont care so much about > the file systems.. But there are some files I would *LOVE* to get > back... > > Any pointers would be great... > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: df output incosistency
While it is technically free, you won't be able to use it in day-to-day operations. It is reserved for the superuser. I believe it is so that if something should flood the filesystem, the superuser still has space to operate on the partition. This can result in ridiculous amounts of reserved space for large partitions, so the larger the filsystem, the lower the percentage that should be reserved. > I was aware of that, but how come it wasn't marked as used before > my operational error? Anyway, you basically say that everything is ok, > and the space is free indeed, although not promptly visible from df? > > Thanks a lot for the info. > > -past > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Andrew Hesford - [EMAIL PROTECTED] "355/113 -- Not the famous irrational number PI, but an incredible simulation!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
