* Terry Lambert <[EMAIL PROTECTED]> [020331 00:05] wrote:
> Michael Smith wrote:
> > > What's the basis of the assumption that the I/O range is
> > > unsupported in the first place, and why isn't it true for this
> > > bridge chip, if it's a valid assumption for others?
> >
> > The information wa
Terry Lambert wrote:
> Kris Kennaway wrote:
> > How does one fix this in a library? I've been moving the
> > initialization to main() for applications.
>
> Use assembly glue to put it in a linker set that gets pulled
> in by the .init code.
>
> This will only work for user space code, since it
At 10:46 PM -0800 3/30/02, Kris Kennaway wrote:
>On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote:
> > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote:
> > > No. This isn't something that is guaranteed to work per
> > > the standards, iirc. The proper fix is to put
Alfred Perlstein wrote:
> * Terry Lambert <[EMAIL PROTECTED]> [020331 00:05] wrote:
> > Michael Smith wrote:
> > > > What's the basis of the assumption that the I/O range is
> > > > unsupported in the first place, and why isn't it true for this
> > > > bridge chip, if it's a valid assumption for o
* Kris Kennaway <[EMAIL PROTECTED]> [2002-03-31 08:48]:
> On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote:
> > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote:
> >
> > > : David O'Brien committed a workaround to the clog port yesterday to
> > > : move the initializer
Garance A Drosihn wrote:
> >How does one fix this in a library? I've been moving the
> >initialization to main() for applications.
>
> If all else fails, have some global static variable, and check
> the value in the routine(s) which care. if the flag variable
> is still zero, then initialize t
> Yeah, you do. I fully understood _that_ context; I think Mike
> was talking about other context. It's pretty clear to me that
> ranges ought to be per bridge chipset, rather than global... I
> thought that that was what the option was working around: that
> they were not.
I can't imagine how
On Sun, 2002-03-31 at 09:51, Terry Lambert wrote:
>
> Perhaps if the kernel printf also "ignored" the request to print
> the little S.O.B. out, there would be less confusion...
I'm still sticking to the idea that one could test for kldxref, and if
it isn't there, don't execute it.
[ -x /usr/sb
On Sat, Mar 30, 2002 at 10:28:05PM -0800, Michael Smith wrote:
> >
> > This avoids a panic when probing, there's probably still some
> > badness going on with make/destroy dev in this driver.
>
> Pending commentary from Scott, I think you should commit this.
Yes, there is a lot of evilness in t
> > > Should I hold onto this card or should I suck it up and get
> > > a 3ware online somewhere?
>
> Be a man and buy a SCSI RAID controller. The Adaptec 5400S is
> all you'll ever need =-)
You will tell me where I can buy disks for $1/GB and hotswap carriers at
$20 a pop, right? 8)
--
To a
Emiel Kollof wrote:
> On Sun, 2002-03-31 at 09:51, Terry Lambert wrote:
> > Perhaps if the kernel printf also "ignored" the request to print
> > the little S.O.B. out, there would be less confusion...
>
> I'm still sticking to the idea that one could test for kldxref, and if
> it isn't there, don
Michael Smith wrote:
> > Yeah, you do. I fully understood _that_ context; I think Mike
> > was talking about other context. It's pretty clear to me that
> > ranges ought to be per bridge chipset, rather than global... I
> > thought that that was what the option was working around: that
> > they
Michael Smith wrote:
> > > > Should I hold onto this card or should I suck it up and get
> > > > a 3ware online somewhere?
> >
> > Be a man and buy a SCSI RAID controller. The Adaptec 5400S is
> > all you'll ever need =-)
>
> You will tell me where I can buy disks for $1/GB and hotswap carriers
On 31 Mär, Ollivier Robert wrote:
>> I encountered a problem when using 'moused' on /dev/ums0: On shutdown
>> or if 'moused' gets killed manually, the system freezes completely and
>> silently, no further shutdown is possible, only the resetbutton
>> operates...
>
> I think it is more of an U
Hello, Makoto Matsushita!
On Mon, Feb 04, 2002 at 12:35:51AM +0900, you wrote:
> ggombert> VMware tools for FreeBSD is woefully out of date as well,
> % cd /usr/ports/emulators/vmware-tools
> % make -V PORTVERSION
> 3.0.0.1455
>
> VMware 3.0 bundles a new VMware tools, and it is up-to-date vers
never> Maybe it's better to make two different ports vmware-tools and
never> vmware-tools3, first of which is for vmware2?
Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for
VMware _1.x_) is outdated for VMware 2.x; it doesn't have time sync
feature.
If you're VMware 2.x user
On Mon, 1 Apr 2002, Makoto Matsushita wrote:
>
> never> Maybe it's better to make two different ports vmware-tools and
> never> vmware-tools3, first of which is for vmware2?
>
> Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for
> VMware _1.x_) is outdated for VMware 2.x; i
On Sun, 31 Mar 2002, Michael Smith wrote:
> You will tell me where I can buy disks for $1/GB and hotswap carriers at
> $20 a pop, right? 8)
eBay. :)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,
On Mon, 2002-03-25 at 10:00, Dag-Erling Smorgrav wrote:
> Joe Clarke <[EMAIL PROTECTED]> writes:
> > Really? I never received it. Please send it again. Thanks.
>
> Here's an updated (but untested) version.
>
I think I found why pam_ldap wouldn't work with OpenPAM on -CURRENT.
Attached is my
On Fri, Mar 29, 2002 at 01:10:17PM -0800, Crist J. Clark wrote:
> After reviewing the world Makefiles, it sure looks like FreeBSD does
> not support 'installworld' of a cross build?
Running installworld on machine X, when you did a cross-build for
machine X on machine Y is broken. All other cases
On Sun, Mar 31, 2002 at 05:57:31PM -0800, Marcel Moolenaar wrote:
> On Fri, Mar 29, 2002 at 01:10:17PM -0800, Crist J. Clark wrote:
> > After reviewing the world Makefiles, it sure looks like FreeBSD does
> > not support 'installworld' of a cross build?
>
> Running installworld on machine X, when
On Sun, Mar 31, 2002 at 07:39:33PM -0800, Crist J. Clark wrote:
> On Sun, Mar 31, 2002 at 05:57:31PM -0800, Marcel Moolenaar wrote:
> > On Fri, Mar 29, 2002 at 01:10:17PM -0800, Crist J. Clark wrote:
> > > After reviewing the world Makefiles, it sure looks like FreeBSD does
> > > not support 'inst
When doing buildworld on current from a couple hours ago. This is an alpha,
if that makes a difference. This is my first time compiling current
(currently running stable), so apologies if this is something that is my
fault.
The error:
===> sbin/savecore
make: don't know how to make savekern
At Sat, 30 Mar 2002 11:02:47 +0100,
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
> >In message <[EMAIL PROTECTED]>, David Malone writes:
> >>On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
> >>> This is an interesting machine: A K6 wiht
On Mon, Apr 01, 2002 at 12:14:27AM -0500, Scott Sipe wrote:
> When doing buildworld on current from a couple hours ago. This is an alpha,
> if that makes a difference. This is my first time compiling current
> (currently running stable), so apologies if this is something that is my
> fault.
25 matches
Mail list logo
