In message <[EMAIL PROTECTED]> Mike Smith writes:
: What about it in particular? Or are you referring to overflow handling?
Yes. Well, I guess I assumed it was a circular thing, and you'd need
to have some comparison against read index, which would be racible.
Warner
To Unsubscribe: send mai
You'll need to make custom install disks with the floating point emulator
in the kernel since you dont have a FPU with that processor.
On Fri, 18 Feb 2000, Kelvin Farmer wrote:
> Hi,
> I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz.
> (win95 runs on this computer ok)
> I
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: complex. For example, using fixed-length FIFOs rather then linked lists.
: The writer manipulates the write index variable, the reader manipulates
: the read index variable. No locking is required between reader and
: write
> The writer manipulates the write index variable, the reader manipulates
> the read index variable. No locking is required between reader and
> writer.
"Applause". I'm all for such solutions.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
:> with supervisor execution, and allow interrupt execution concurrent
:> with other interrupts. For example, two different ethernet interrupts
:> could be taken concurrently with only minor spinlock controls
:> on the IF queue, and both could run concurrent with the TCP stack
In message <[EMAIL PROTECTED]> "Ilmar S.
Habibulin" writes:
: Has the subject been fixed or not? And what seems to be the problem, why
: it became broken?
Soren broken non-cdrom changers for a couple of days. He's fixed
this.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
Has the subject been fixed or not? And what seems to be the problem, why
it became broken?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* Bernd Walter <[EMAIL PROTECTED]> [000326 01:51] wrote:
> On Sun, Mar 26, 2000 at 01:15:07AM -0800, Alfred Perlstein wrote:
> >
> > I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff
> > and came across a problem where it seems that 5.0 doesn't get any
> > IO down to my vinum st
-On [2327 00:00], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote:
>On Sun, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote:
>
>> dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will
>> either result in `nothing written' or `symbol not found'.
>
>Just do a "w dumpdev 0xc0b65800".
On Sun, Mar 19, 2000 at 03:24:36PM +, Nick Hibma wrote:
>
> If anyone is using the umass driver, please send me the output of (*)
>
> dmesg | grep '^\(.hci\|usb\|umass\|da\|(da\)' \
> mail -s 'Drive info' [EMAIL PROTECTED]
Just wanted to point out that the USB Zip 250 is
In message <[EMAIL PROTECTED]> Jason Garman writes:
: This has been broken for at least a few weeks. I've reported it before,
: but I haven't had any responses so far. 5.0-current, as of last night.
: Related to newbus changes?
See UPDATING:
2319:
The ISA and PCI compatability shim
> This is one of the things that made us do so badly
> in the benchmarks against NT/Linux last year.
If the benchmarks included random I/O I would think so.
By creating a small synthetic program exhibiting the problem, I may have
obscured the scale of the real-world consequences of this problem.
Hi,
I've written a new-bus probe/attach patch for the tx driver and
submitted it as PR kern/17601. It works for me, but it could definatly
use wider testing as it's my first venture into driver hacking. If
you've got one of these cards please give it a spin.
Thanks,
Brooks
--
Any statement o
> "David W. Chapman Jr." wrote:
>
> I accidently deleted my spwd.db on 4.0-stable, how do I recreate it,
> any hints would be appreciated.
Assuming that your master.passwd is up to date, the easiest way is to
do, 'pwd_mkdb -p /etc/master.passwd'. That will synch everything up for
you. Th
Matthew Dillon wrote:
> The answer is nobody knows yet :-).
>
> Interrupts will probably wind up running each in its own thread, and
> we will probably adopt the BSDI hybridized model (which runs an interrupt
> synchronously if possible and spools it to a thread otherwise) to
:I do not expect implementation right now.
:I can put some stubs in pertinent places.
:What I am looking for is some kind of
:guidelines/hints/...
The answer is nobody knows yet :-).
Interrupts will probably wind up running each in its own thread, and
we will probably adopt the
In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
>> >I'll get panics,
>>
>> You should know better than expect help providing only this little
>> information...
>
>Poul, is your mailer broken in such a way that you can't quote the
>entire message?
If you had at least told me what panic y
On Sun, Mar 26, 2000 at 11:20:53AM -0800, Matthew Dillon wrote:
> It will probably be a months before you will be able to do that. The
> mechanisms haven't even been built yet. We will continue to use the
> spl*() calls for some time.
I do not expect implementation right now.
I can
:
:I accidently deleted my spwd.db on 4.0-stable, how do I recreate it, any =
:hints would be appreciated.
as root type:
vipw
Then write it out and quit without making any changes. spwd.db should
be regenerated.
-Matt
To Un
On Sun, Mar 26, 2000 at 11:49:05AM -0800, Alfred Perlstein wrote:
> Poul, is your mailer broken in such a way that you can't quote the
> entire message?
I doubt it. One should NOT quote entire messages, only the applicable
parts.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail t
I accidently deleted my spwd.db on 4.0-stable, how
do I recreate it, any hints would be appreciated.
This has been broken for at least a few weeks. I've reported it before,
but I haven't had any responses so far. 5.0-current, as of last night.
Related to newbus changes?
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-W
* Poul-Henning Kamp <[EMAIL PROTECTED]> [000326 01:18] wrote:
> In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
> >I'm about to wander down vinum's source again.
> >
> >With a kernel and vinum module dated approx Tue Feb 29 06:53:56
> >PST 2000 everything works fine.
> >
> >I recently (to
:Subject says almost all. In anticipation of SMP I would like
:to avoid splxxx() at all in my driver. How can I do that? Let say
:for FreeBSD >= 4.0.
:
:Thanks
It will probably be a months before you will be able to do that. The
mechanisms haven't even been built yet. We will continue t
On Sun, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote:
> Ok,
>
> so thanks to Brian I can at least get a good value for my swap slice by
> using show disk/ad0s1b.
>
> It returns that the dev_t is 0xc0b65800
>
> Ok, so I then proceed to look at dumpdev
>
> A p dumpdev shows me that it is set to a
Subject says almost all. In anticipation of SMP I would like
to avoid splxxx() at all in my driver. How can I do that? Let say
for FreeBSD >= 4.0.
Thanks
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:I haven't looked at the patch so I can't comment on it (but it sounds very
:promising).
:
:I have been writing some of the infrastructure for SMP on alpha and as an
:experiment I've been using the mutex_t primitive from BSD/OS as an
:experiment. This is a nice simple api for a counting mutex whic
[ On Sunday, March 26, Julian Elischer wrote: ]
> I'm in the process of investigating UDF with the aim of
> producing a UDF filesystem (possibly only read-only)
> and a UDF enabled version of mkisofs (porst/sysutils)
>
cool!
> I have all the appropriate specs and standards here and have been r
I'm in the process of investigating UDF with the aim of
producing a UDF filesystem (possibly only read-only)
and a UDF enabled version of mkisofs (porst/sysutils)
I have all the appropriate specs and standards here and have been reading
them. I also have the linux UDF code as of a month or two ba
Hello all,
I was fishing through the archives this morning (sorting by date) looking for
information about support for UDF filesystems. I saw that there was a lot of
explaination as to what UDF was and a lot of comments stating "no, we don't
support this, yet." But, the most recent thing the sea
On Sun, 26 Mar 2000, Doug Rabson wrote:
> On Sun, 26 Mar 2000, Andrzej Bialecki wrote:
> > Well, somehow the idea of overlapping subtrees sounds nice and useful
> > IMHO. Any suggestions how to solve these issues?
> >
> > One possible way to do it would be to keep some ID of the oid's
> > creat
Note : the compile is fine without -funroll-loops
multi% gcc -v --save-temps -O -pipe -march=pentiumpro -Wall
-funroll-loops -fschedule-insns2 -DLIBC_RCS -DSYSLIBC_RCS
-I/files3/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6
-DPOSIX_MISTAKE -I/files3/src/lib/libc/../libc/locale
-DBROKEN
Ok,
so thanks to Brian I can at least get a good value for my swap slice by
using show disk/ad0s1b.
It returns that the dev_t is 0xc0b65800
Ok, so I then proceed to look at dumpdev
A p dumpdev shows me that it is set to a weird value not matching my
dev_t above.
A p *dumpdev returns
On Sun, 26 Mar 2000, Yoshinobu Inoue wrote:
> > > OK, then how about creating machine/align.h?
> >
> > That approach in general would give too many headers.
> Then, how about defining a macro which specifies name space
> polluted part, for short term solution.
>
> machine/param.h:
> #ifdef _NO
I think that if the sysctl data was reorganized, so that the per
module or instance data was at the leaves of the tree, you could avoid
the problem entirely. This is the general approach used on MIB definitions
used for SNMP; each variable is an instance (usually the 0th) at the
leaf. You don't
On Sun, 26 Mar 2000, Andrzej Bialecki wrote:
> On Sun, 26 Mar 2000, Doug Rabson wrote:
>
> > On Fri, 24 Mar 2000, Andrzej Bialecki wrote:
> >
> > > Hi,
> > >
> > > Inspired by PR kern/16928 I implemented completely dynamic
> > > creation/deletion of sysctl trees at runtime. The patches (relati
On Sun, 26 Mar 2000, Doug Rabson wrote:
> On Fri, 24 Mar 2000, Andrzej Bialecki wrote:
>
> > Hi,
> >
> > Inspired by PR kern/16928 I implemented completely dynamic
> > creation/deletion of sysctl trees at runtime. The patches (relative to
> > -current) can be found at:
> >
> > http://www.f
On Fri, 24 Mar 2000, Matthew Dillon wrote:
> Patch 04 is ready.
>
> http://www.backplane.com/FreeBSD4/
> http://www.backplane.com/FreeBSD4/smp-patch-04.diff
>
> Contains lots of cleanup of stale SMP code. There are still a few places
> where get_mplock is being called with
On Fri, 24 Mar 2000, Andrzej Bialecki wrote:
> Hi,
>
> Inspired by PR kern/16928 I implemented completely dynamic
> creation/deletion of sysctl trees at runtime. The patches (relative to
> -current) can be found at:
>
> http://www.freebsd.org/~abial/dyn_sysctl.tgz
>
> Included is an exam
On Sun, 26 Mar 2000, Kris Kennaway wrote:
> Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has
> come up several times in the past with positive feelings, but no-one
> actually did the work (it compiles trivially).
I think Robert Nordier has a better one.
> I could just as
On Sun, 26 Mar 2000, Kris Kennaway wrote:
> Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this
> has come up several times in the past with positive feelings, but
> no-one actually did the work (it compiles trivially).
Commit it.
While you're there see if any of their ext2fs /s
-On [2326 12:10], Kris Kennaway ([EMAIL PROTECTED]) wrote:
>Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has
>come up several times in the past with positive feelings, but no-one
>actually did the work (it compiles trivially).
>
>I could just as e
Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has
come up several times in the past with positive feelings, but no-one
actually did the work (it compiles trivially).
I could just as easily make it a port, depending on the consensus opinion.
Kris
In God we Trust -- al
On Sun, Mar 26, 2000 at 01:15:07AM -0800, Alfred Perlstein wrote:
> I'm about to wander down vinum's source again.
>
> With a kernel and vinum module dated approx Tue Feb 29 06:53:56
> PST 2000 everything works fine.
>
> I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff
> and c
In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
>I'm about to wander down vinum's source again.
>
>With a kernel and vinum module dated approx Tue Feb 29 06:53:56
>PST 2000 everything works fine.
>
>I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff
>and came across a pro
I'm about to wander down vinum's source again.
With a kernel and vinum module dated approx Tue Feb 29 06:53:56
PST 2000 everything works fine.
I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff
and came across a problem where it seems that 5.0 doesn't get any
IO down to my vinum
46 matches
Mail list logo
