> Anyway, this module was meant more as a joke, but if you guys like it so
> much you could vote for putting it in the tree...
My vote is a resounding "Yes!".
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
Kevin Day wrote:
>
> A> Anyway, this module was meant more as a joke, but if you guys like it so
> > > much you could vote for putting it in the tree...
> >
> >What do you mean "vote"? I was waiting for it to show up on my tree
> >after a cvsup!
>
> I hate to keep bringing things like this up, o
Mike Smith wrote:
>
> > Hi, my mentor :-)
> >
> > phk> Am I the only one to see these ?
> >
> > Me too. I found it other files as well.
> > It seems that adding following line is required in some source code.
> >
> > #include
>
> Argh! I knew that taking it out of sys/systm.h was a bad idea. 8
Matthew Dillon wrote:
>
> :Hate to ask, do we support CD-RW?
>
> Yup! In fact, I recommend that you get a 5-pack of CD-RW disks
> so you don't turn your CD-R's into scrap while playing with the
> unit.
Scrap? HA!
http://students.seattleu.edu/hodeleri/Images/CDs.gif
--
Eric Hodel
A> Anyway, this module was meant more as a joke, but if you guys like it so
> > much you could vote for putting it in the tree...
>
>What do you mean "vote"? I was waiting for it to show up on my tree
>after a cvsup!
I hate to keep bringing things like this up, or start a legal war, but this
scr
Andrzej Bialecki wrote:
>
> On Sat, 21 Aug 1999, Nik Clayton wrote:
>
> > FWIW, there are at least two other 'matrix' implementations out there.
> > One is part of xscreensaver, and is quite nice -- it's even better if you
> > halve the size of the image it's using first. This has the advantage
On Sun, 22 Aug 1999, Andrzej Bialecki wrote:
> Anyway, this module was meant more as a joke, but if you guys like it so
> much you could vote for putting it in the tree...
It's extremely small, so why not? Got my vote. :-)
-- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD: Th
:> I'm generating a core dump. Please note that as tara is my test machine, I use
:> "INVARIANT" & "INVARIANT_SUPPORT". Should I remove them ?
:>
:> It seems that from my reading of the code, the panic would not had happened
:> without INVARIANT.
:>
:It is these options that caused the panic, y
:> Does anyone know why our NFS clients are sending a separate RPC for each
:> 8K buffer? If the dirty space is contiguous across a number of buffers
:> we should be able to send a *SINGLE* commit rpc to the server. That would
:> greatly reduce system overhead on both the client
> I'm generating a core dump. Please note that as tara is my test machine, I use
> "INVARIANT" & "INVARIANT_SUPPORT". Should I remove them ?
>
> It seems that from my reading of the code, the panic would not had happened
> without INVARIANT.
>
It is these options that caused the panic, you eith
I forgot to mention: It's the 'Multi-patch #1' section of the web page,
the section at the top. Ignore all the stuff that comes after that -
they've already been committed, as have many other things not listed.
http://www.backplane.com/FreeBSD4/
Ok, I have put up the current patch set -- for patching against CURRENT
only - on my web site.
http://www.backplane.com/FreeBSD4/
They contain a bit more then the NFS stuff, but it's all related to
performance. It would take me too long to try to separate them out
(t
I have a 3.2-Stable and a 4.0-Current system at home, both running rc5des.
On both systems I set the priority in the rc5 options menu to '0',
indicating lowest possible priority. On the -Stable system it's running at
nice level '0', but it seems to be taking advantage of the idprio stuff
s
On Sat, 21 Aug 1999, Nik Clayton wrote:
> FWIW, there are at least two other 'matrix' implementations out there.
> One is part of xscreensaver, and is quite nice -- it's even better if you
> halve the size of the image it's using first. This has the advantage that
> the characters actually look
:Hello,
:
:I just got a panic when trying to play with NFSv3. The system is a dual
:PentiumPro system, running CURRENT/SMP. I use NFS as a kld.
The very first thing I would do is compile NFS into the kernel and not
use it as a kld. Then see if you can repeat the problem.
Bill Paul wrote:
> Ai! The stupid bus interface description file escaped before I
> could commit it with the rest of the miibus code. Okay, I just fixed
> it. Thanks for the heads up and sorry for the trouble. My turn to
> wear the pointy hat again.
Hey, no sweat. It is -current afte
"Jordan K. Hubbard" wrote:
>
> > The X also protected test from the case where the expansion included a
> > string like "-x", although with most modern implementations of test (or
> > shells with test as a builtin) this is no longer a problem.
>
> And certainly not in any of these cases. :
This is my kernel compile error and where it died
e -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../..
-I../../../include -DKERNEL -include opt_global.h -elf ../../dev/aha/aha.c
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-exte
I'm with you 100% I've got about 100 Bonnies of trying to optimize
Linux Clients (pre and post NFSv3 patch) vs. FreeBSD server. I've gone
to current so that I can watch it happen. I'm currently writing around
4.5M - 5.0M/sec vs. 10-15M/sec on my vinum stripe locally.
I went through a similar t
Andrzej Bialecki wrote:
>
> Hi,
>
> Due to unexpected demand . . .
Ok, I have to say that pretty much rocks. :) Any chance of making an X
version of this? The guy in the cube across from mine and I are both big
science fiction fans, and he would turn *cough* green with envy . . .
Doug
Of all the gin joints in all the towns in all the world, Doug had to
walk into mine and say:
> Cvsup'ed today, make -DNOCLEAN world failed in gcc, did a 'make includes'
> and 'make world' and now it fails in:
>
> ===> sys/modules/mii
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i386/incl
Cvsup'ed today, make -DNOCLEAN world failed in gcc, did a 'make includes'
and 'make world' and now it fails in:
===> sys/modules/mii
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
perl /usr/src/sys/modules/mii/../../kern/makedevops.pl -h
/usr/src/sys/modules/mii/../../kern/bus_if.
> The X also protected test from the case where the expansion included a
> string like "-x", although with most modern implementations of test (or
> shells with test as a builtin) this is no longer a problem.
And certainly not in any of these cases. :)
> I agree with some of your changes
Matthew Dillon wrote:
> Does anyone know why our NFS clients are sending a separate RPC for each
> 8K buffer? If the dirty space is contiguous across a number of buffers
> we should be able to send a *SINGLE* commit rpc to the server. That would
> greatly reduce system overhead
"Jordan K. Hubbard" wrote:
>
> > I gather the reason for using the X trick *and* the quotes is because there
> > might be some whitespace in there, too.
>
> Actually, that's mostly just historical legacy. When the quotes, it's
> safe even if the expansion is empty or contains whitespace.
> I gather the reason for using the X trick *and* the quotes is because there
> might be some whitespace in there, too.
Actually, that's mostly just historical legacy. When the quotes, it's
safe even if the expansion is empty or contains whitespace. I got
kinda annoyed with this last night and
I understand that folks use X$foo becuase if $foo evaluates to -whatever
then there is a *chance* that test will misunderstand.
I gather the reason for using the X trick *and* the quotes is because there
might be some whitespace in there, too.
Given that "case" is a builtin and using "case" inst
Hi,
In my case is a lot easier to customize a simple shell script and use it.
Is just that gcombust comes from linux perhaps if I keep using
I can get over my hurdle 8)
Have Fun Guys!
> Heh. I see, you want a program that one could use without
> having to know _anything_. Your right
Heh. I see, you want a program that one could use without
having to know _anything_. Your right thats not what gcombust is,
but its still useful for those of us who know `something'...
On Fri, Aug 20, 1999 at 05:02:07PM -0700, Amancio Hasty wrote:
> Yes, I tried gcombust and opted for the comma
Matthew Dillon said:
> :> Well, the issue with converting many of the macros to inline functions
> :> is with the embedded goto's and references to variables defined outside
> :> the macros. Converting them to functions would basically require
> :> rewriting a huge chunk of NFS
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
> : -if [ X$start_vinum = XYES ]; then
> : +if [ X"${start_vinum}" = X"YES" ]; then
>
> I never understood why you check against X"YES"? XYES always seemed
> much better than X"YES" since the latter is somewhat obscure.
On Fri, Aug 20, 1999 at 08:10:51PM -0400, Keith Stevenson wrote:
> On Fri, Aug 20, 1999 at 04:11:42PM -0600, Oscar Bonilla wrote:
> > then xlock already includes a module for this... I'm using it on my
> > laptop..
... ahh. ... Meanwhile I've updated my xlock to xlockmore-4.14 including
'the matri
> With current source tree as of 9 am pacific, I can no longer build a kernel :
My mistake; should be fixed now.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscrib
On Sat, 21 Aug 1999, Mike Smith wrote:
> Argh! I knew that taking it out of sys/systm.h was a bad idea. 8(
I committed the fix for this, FYI, after it tripped someone up on IRC.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED]
In message <[EMAIL PROTECTED]> Mike Smith writes:
: If you're going to do that, take a look at the ACPI spec and implement
: at least the base set of power states that it defines, since we are
: going to have to live with hardware that behaves like that for some
: time to come.
Good idea... H
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : APM is only attached to the ISA bus for crufty reasons; I'm going to
>
> Actually, APM is attached to NEXUS. Why pass it kernel environment
> variables when it will likely be modified to grok whatever config
> scheme comes from newbus?
Be
> : If you need more functionality than DEVICE_SUSPEND and DEVICE_RESUME,
> : then add more methods.
>
> That DEVICE_SUSPEND and DEVICE_RESUME methods are exactly the same
> thing as we have right now with the apm code. No need to reinvent the
> wheel here. It was on my list of cleanups to do a
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : Seriously though, I'm in the process of replacing a number of the
> : ad-hoc event handler callout lists in the kernel (most notably the
> : at_shutdown and apm* lists) with a generic implementation.
>
> Shouldn't the apm stuff use the new
> Hi, my mentor :-)
>
> phk> Am I the only one to see these ?
>
> Me too. I found it other files as well.
> It seems that adding following line is required in some source code.
>
> #include
Argh! I knew that taking it out of sys/systm.h was a bad idea. 8(
--
\\ The mind's the standard
In message <[EMAIL PROTECTED]> Garrett
Wollman writes:
: You missed the point. The bus hierarchy has support designed-in to
: pass power-management requests down the device tree. The only
: functions which should be registering themselves with APM directly
: are:
:
: 1) Old device drivers
In message <[EMAIL PROTECTED]> Mike Smith writes:
: APM is only attached to the ISA bus for crufty reasons; I'm going to
Actually, APM is attached to NEXUS. Why pass it kernel environment
variables when it will likely be modified to grok whatever config
scheme comes from newbus?
Warner
To U
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > In message <[EMAIL PROTECTED]> Mike Smith writes:
: > : Seriously though, I'm in the process of replacing a number of the
: > : ad-hoc event handler callout lists in the kernel (most notably the
: > : at_shutdown and apm* lists) with a generi
> > > > "Another possibility, if you have the RAM, is to use the team(1)
> > > > program (it's in the ports) to buffer the data as it goes to the burner.
> > >
> > > Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
> >
> > Any reason to? I mean, I never had to go over the defaul
Hello,
I just got a panic when trying to play with NFSv3. The system is a dual
PentiumPro system, running CURRENT/SMP. I use NFS as a kld.
The FS on keltia is exported as:
/z -alldirs -maproot=0 tara
And mounted on tara with
keltia:/z /spare rw,nfsv30 0
I tried making a d
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> So I still stick with my statement that the -current bootblocks/loader
>> doesn't have the computrons needed to use the ad device (or any non
>> wd/da/fd device for that matter) for anything usefull :)
>
>The loader is fine; the problem is just
< said:
>> [Quoting somebody unidentified, presumably Warner:]
>> Shouldn't the apm stuff use the new-bus hooks? I've migraded a couple
>> of uses in pccard to using that now that I have newbus node to hang
>> them off of...
> APM is only attached to the ISA bus for crufty reasons; I'm going t
> As David O'Brien wrote ...
> > > "Another possibility, if you have the RAM, is to use the team(1)
> > > program (it's in the ports) to buffer the data as it goes to the burner.
> >
> > Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
>
> Any reason to? I mean, I never had to g
> So I still stick with my statement that the -current bootblocks/loader
> doesn't have the computrons needed to use the ad device (or any non
> wd/da/fd device for that matter) for anything usefull :)
The loader is fine; the problem is just that Poul never finished fixing
the mountroot code. A
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : Seriously though, I'm in the process of replacing a number of the
> : ad-hoc event handler callout lists in the kernel (most notably the
> : at_shutdown and apm* lists) with a generic implementation.
>
> Shouldn't the apm stuff use the new
> Then there is no advantage in using `team' vs. ``cdrecord -fs=XX'', right?
>
> --
> -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
As far as I can tell there is no difference other one component less to use
and ease of use.
Cheers
--
Amancio Hasty
[EMAIL PROTECTED]
> > > "Another possibility, if you have the RAM, is to use the team(1)
> > > program (it's in the ports) to buffer the data as it goes to the burner.
> >
> > Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
>
> Any reason to? I mean, I never had to go over the default cdrecord u
I am purposely panic()ing the system early in boot so I can get a look at some
startup information... unfortunately the 'config kernel dumps on...' no
longer works. how is one supposed to get crash dumps from early in the boot
process?
--
David Cross | email: [EMA
Hi, my mentor :-)
phk> Am I the only one to see these ?
Me too. I found it other files as well.
It seems that adding following line is required in some source code.
#include
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sorry to late...
plm> Now suspend works. However still the disks keep spinning until they
plm> reach their BIOS timeout. In Linux & Windows, there is some hook when
plm> going to suspend mode that spins down the (IDE) disks. This is nice,
plm> since it is well possible that you go to suspend but
Am I the only one to see these ?
critter# make
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf
../../
plm> If I use 'zzz', I have to do the known 'sleep 1; zzz' trick. This is
plm> the difference.
I'll commit the patch for `key release event prevent suspend' problem
if no objections.
Thanks a lot!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
Hi, sorry to late.
> > 1. Standby by PM timer in BIOS setting fails with the system activity.
>
> If by fails you mean enters standby mode, then yes the computer enters
> standby mode while the system is active, after the period of time set in
> the bios, as long as no keys have been pressed on
As David O'Brien wrote ...
> > "Another possibility, if you have the RAM, is to use the team(1)
> > program (it's in the ports) to buffer the data as it goes to the burner.
>
> Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
Any reason to? I mean, I never had to go over the def
:> Well, the issue with converting many of the macros to inline functions
:> is with the embedded goto's and references to variables defined outside
:> the macros. Converting them to functions would basically require
:> rewriting a huge chunk of NFS code.
:>
:My working kerne
:On Thu, 8 Jul 1999, The Hermit Hacker wrote:
:> Three weeks ago, I, and a few other INN administrators, posted about
:> FreeBSD -STABLE's inability to run the newest INN code, due to MMAP() race
:> conditions...essentially, after X hours of run time, on a heavily loaded
:> INN server, the whole t
With current source tree as of 9 am pacific, I can no longer build a kernel :
cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions
-ansi -nostdinc -I- -I. -I../.. -I../../../include
> However I'd REALLY like to emphasize again that if we're going to do
> this the proper fix is to use case wherever possible. There are
> numerous reasons for this, not the least of which are making the
> variable case insensitive (and therefore more user friendly)
I have to really agree with Do
At 10:26 AM 8/21/99 +0100, Nik Clayton wrote:
>On Fri, Aug 20, 1999 at 07:34:31PM +0200, Andrzej Bialecki wrote:
> > Both versions are available at:
> >
> > http://www.freebsd.org/~abial/matrix_3.2.tgz
> > http://www.freebsd.org/~abial/matrix_4.0.tgz
>FWIW, there are at least two other
> If you have the physical memory sure however if you don't then
> you will start swapping and most likely your cd recording will
> fail.
>
> Hence my recommendation for a small size buffer.
Then there is no advantage in using `team' vs. ``cdrecord -fs=XX'', right?
--
-- David([EMAIL PRO
I'm assuming that you are using egcs-1.1.2.
gcc-2.95 seems to work OK. It doesn't discard the initialization of
answer like egcs-1.1.2 does.
Dan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Mike Smith wrote (1999/08/11):
> > Yes, thanks. Information reported by 0x4F01 function about any video
> > mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
> > program for VESA support...
>
> Bleagh. Have you tried ignoring that attribute in our code and seeing
> what
On Fri, Aug 20, 1999 at 07:34:31PM +0200, Andrzej Bialecki wrote:
> Both versions are available at:
>
> http://www.freebsd.org/~abial/matrix_3.2.tgz
> http://www.freebsd.org/~abial/matrix_4.0.tgz
I knew I should have taken the blue pill.
FWIW, there are at least two other 'matrix'
Matthew Dillon said:
> :> global references across subroutine calls! I'll send Luoqi another email.
> :>
> :> In the case of the NFS stuff, the changes have been pretty well tested
> :> so I think we are in the clear.
> :
> :On a somewhat similar note, what do you think about convert
It seems Mike Smith wrote:
> > Our boot blocks/loader dont have the needed computrons to use the
> > "ad" device name. However I have some patches to boot2 that allows
> > to boot off an ad root device, provided you dont use the loader, and
> > put the rigth boot string in boot.config.
>
> This s
>If you don't have the time to trim, we don't have the time to read your
Easy , Easy we are coming along fine so far so please keep
the flame temperature down. If you are compelled or annoyed
at the poster send him private e-mail and possibly a pointer
to net - etiguette. If you do it nicely you
If you have the physical memory sure however if you don't then
you will start swapping and most likely your cd recording will
fail.
Hence my recommendation for a small size buffer.
And to the list.
Please keep the comments or suggestions rolling and hopefully
by early next we will have a nice
After compiling yesterday's -current kernel, I see the following in dmesg:
...
ahc0: aic7880 SBLKCTL = 0x0
SSTAT0 = 0x0
SFUNCT = 0x0
Single Channel A, SCSI Id=7, 16/255 SCBs
...
Notice the "SBLKCTL"... stuff. I guess this is some forgotten debug printf
left, or am I mistaken?
Blaz Zupan, [EMAIL
On Fri, 20 Aug 1999, Andrew Gallatin wrote:
>
> Doug Rabson writes:
> > On Thu, 19 Aug 1999, Andrew Gallatin wrote:
> >
> > >
> > > I do most of my development on alphas & I just turned some local code
> > > into a loadable kernel module. It works fine when compiled into the
> > > kerne
On Fri, Aug 20, 1999 at 01:04:47PM +0200, Werner Griessl wrote:
Werner, like you we all got 246 line email message. You did not have to
quote the *ENTIRE* thing back to us just to add 3 lines.
If you don't have the time to trim, we don't have the time to read your
reply.
--
-- David([EMA
> "Another possibility, if you have the RAM, is to use the team(1)
> program (it's in the ports) to buffer the data as it goes to the burner.
Any reason not to use ``cdrecord -fs=64m'' (or some simular size)
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail
> I managed to build gdb-4.17 in FreeBSD 4.0, here's how to do it:
...
> Then it should all build (and perhaps work). The same hacks probably apply
> to gdb-4.18 and gdb-current (but so far gdb-4.17 is the most useful version
> I've seen for debugging C++).
Are you saying 4.17 is better than 4.1
On Thu, 8 Jul 1999, The Hermit Hacker wrote:
> Three weeks ago, I, and a few other INN administrators, posted about
> FreeBSD -STABLE's inability to run the newest INN code, due to MMAP() race
> conditions...essentially, after X hours of run time, on a heavily loaded
> INN server, the whole thing
Hi
Linux land does not look so pretty now days ...
Playing with Sun's java jre on linux.
Ran jre libgc on redhat 6.0 no problem.
slackware 4.0 appears to only like jre libc
Suse 6.1 does not like either jre libc nore jre libgc.
So on
My customer should ship an entire linux box with the
78 matches
Mail list logo
