WARNING, this is likely going to sound offensive to some people...
Johan M:son Lindman wrote:
On Tuesday 19 July 2005 17:02, you wrote:
Since OpenBSD is not very helpful in this case I can only enclose the
dmesg without the enclosure plugged in. But first here's the info for
the enclosure as Linux sees it (dmesg):
Read this, http://www.openbsd.org/report.html (hint, you should try a -current
snapshot to see if the problem has been fixed recently).
Interesting assumption on your part that I hadn't read that document. I
have read it. And it doesn't say anything about trying current instead
of the "stable" branch as I have. Your hint doesn't help most users as
they don't run current but stable. This OpenBSD list seems to be filled
with some of the most discourteous netizens I've encountered. If you
wanted to say that I should use the current because there is a know
problem pertaining to my situation that was fixed in current -- Then say
so. And yes I have read the changelog for current and it does have
entries for umass. But they provide no indication as to what problems
the changes address. So they are useless from a users perspective. And
I'm not about to go digging in source histories and sources themselves
to find out any more information than what is in the changelog.
So please, if you, or others know of specific changes that pertain to my
problem mention them. And I will try and figure out a way to use that
specific part of current, because I just can't follow current on a
production server (as other users will also tell you). And if there's a
FAQ on how to use only some specific current changes, instead of the
complete ball of wax, that would also be appreciated.
--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
