Date: Wed, 25 Feb 1998 00:13:07 -0500 (EST) From: "Joe \"Marcus\" Clarke" <marcus@miami.edu> To: Greg Lehey <grog@lemis.com> Cc: FreeBSD User Questions List <freebsd-questions@FreeBSD.ORG> Subject: Re: udma hdd Message-ID: <Pine.OSF.3.96.980225000939.22740A-100000@jaguar.ir.miami.edu> In-Reply-To: <19980225153306.35040@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, Greg, my fault. I had my terminal set to 132 lines, and forgot to set it back. Quite frankly I hate using Netscape and the like to send mail. I prefer pine and the vi editor from a nice UNIX shell. Anyway, I was asking about UDMA controllers/drives. I just bought one, adnd it works fine. My question is does FreeBSD have a problem with UDMa, or just some UDMA controllers or drives? Joe Clarke P.S. I hope this is a little easier to read. On Wed, 25 Feb 1998, Greg Lehey wrote: > On Tue, 24 February 1998 at 23:55:11 -0500, Joe "Marcus" Clarke wrote: > > Recently there have been a few postings to the list regarding UDMA, and I'm a little curious. I just bought what is > > supposedly a UDMA 5.1 GB drive. I have a PCI IDE controller that supports UDMA. I installed a file system on it just fine. > > I've been using it for /usr/local for a while now with no problem. I just enabled 32-bit access and 16-sector transfers on > > it in the kernel (added flags 0x80ff to wdc0 in kernel config) and it seems to be okay. Is there really a problem with UDMA > > and FreeBSD, or is it just certain drives/controllers? > > I'm sorry, I can't read this message. It contains no line breaks in > paragraphs, it is a pain to read, and it's completely avoidable. I no > longer reply to the contents of such messages. Since I haven't > examined the message more closely, this also means that I may send you > more than one copy of this message, and that I don't know whether I > could answer your question or not. > > I'm not writing to bitch about this: there are a couple of serious > reasons. First, writing this kind of message significantly reduces > your chances, and secondly there's a good chance that you're not aware > this is happening. If this is the case, there is a possibility that > it is due to your mailer, either because it is broken by design, or > because it is incorrectly configured. I have noted that the following > mailers seem to have problems in this area: > > "Microsoft Mail" > Microsoft Outlook > Mozilla (Netscape) > Yahoo! mail > exmh > > Why do so many "reputable" mailers have these problems? Bugs are one > reason, of course, but there's more to it than that. Microsoft-based > mailers think they're doing you a favour by either leaving it to the > receiver to decide how to display the message (this results in > one-line paragraphs), or ensuring that no line is longer than a > certain length. If this 'certain length' is slightly shorter than > what you enter, it creates a long and a short line out of each line. > > So what's wrong with these approaches? > > 1. The mail standards are explicit: the mail type "text/plain" should > display exactly as written. This is a feature, not a bug. > Microsoft, in particular, often ignores this requirement. > Consider what this can do to a message which is split into two > columns. > > 2. Normally, when you reply to a mail message, you 'quote' it by > putting a '> ' sequence at the beginning of each line. For > example: > > --- example --- > Fred Bloggs said: > > OK, Joe, how about gettting together on Saturday and finding > > out what's wrong with this machine. I can bring along a > > logic analyzer and a second machine for debugging. > > Thanks, Fred, let's do it. How does 2:30 pm sound? > --- end example --- > > If your mailer wraps this message, you could get things like: > > > OK, Joe, how about gettting together on Saturday and finding > out > what's wrong with this machine. I can bring along a > logic > analyzer and a second machine for debugging. > > alternatively, they could be: > > > OK, Joe, how about gettting together on Saturday and > finding out > > what's wrong with this machine. I can bring along a > logic > > analyzer and a second machine for debugging. > > I hope you'll agree that both of these look much worse. > > Of course, it could be that my examples don't show up well on your > system. I don't know how to help you in that case. > > For further information, take a look at > http://www.lemis.com/email.html > > If you do succeed in fixing the configuration, please let me know. It > seems to be difficult, and so far I don't have much information to > offer in the web page. > > Greg > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.980225000939.22740A-100000>