In message <01be9cef$64202e60$2c4b9...@william> "William Woods" writes:
: I am haveing a bear of a time getting pcmcia cards to work in 3.1-Stable and
: was wondering how well current performs with these.
Hmmm. I don't think that -current will help, and may even hurt. What
kind of laptop
In message <199905122048.qaa72...@misha.cisco.com> Mikhail Teterin writes:
: Perhaps, the newbus vs. newconfig discussion can be summarized to both
: sides' satisfaction offline and then presented to the rest of the world?
It is my impression that the language barrier has made this discussion
ha
In message <199905120901.saa04...@srapc288.sra.co.jp> Noriyuki Soda writes:
: This reminds me another ugly kluge in sys/pccard/i82365.h:
: #define PCIC_INDEX_00x3E0
: #define PCIC_INDEX_1(PCIC_INDEX_0 + 2)
: This is the way what some clever FreeBSD people saids "right" to
: Naka
On Thursday, 13 May 1999 at 14:19:23 +0930, Greg Lehey wrote:
> I've had a couple of these in a 3.2-BETA box today:
>
> May 13 14:11:51 daemon /kernel: spec_getpages: I/O read failure: (error
> code=16)
> May 13 14:11:57 daemon /kernel: size: 65536, resid: 65536, a_count: 65536,
> valid: 0x0
> M
> It's certainly not because of the helping hands that have been
> extended to him.
-current doesn't come with seat belts or air bags. If you're looking
for a helping hand rather than a ranger combat course where people
just boot you in the ass whenever you fall into the mud, go next
door to -sta
On Wednesday, 12 May 1999 at 21:56:53 -0700, Jordan K. Hubbard wrote:
>> No offense surely, but I have been running -current in this (and others
>> with Libretto too) box since 2.2-current, in true, without too much
>> trouble, and I am survived to a lots of nasty things in the meantime. I
>
> Thi
> No offense surely, but I have been running -current in this (and others
> with Libretto too) box since 2.2-current, in true, without too much
> trouble, and I am survived to a lots of nasty things in the meantime. I
This only constitutes a confession on your part that you've survived
by pure lu
At 12/05/99, you wrote:
>> Pardon, but I am not be able to figure by myself what you asked to me...
>> If you can explain me step by step in a newbie way I can do everything ...
>> The crashes is easily reproducible...
>
>No offense, but are you sure you should even be running -current? A
>certain
I've had a couple of these in a 3.2-BETA box today:
May 13 14:11:51 daemon /kernel: spec_getpages: I/O read failure: (error code=16)
May 13 14:11:57 daemon /kernel: size: 65536, resid: 65536, a_count: 65536,
valid: 0x0
May 13 14:11:57 daemon /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16
A
I am haveing a bear of a time getting pcmcia cards to work in 3.1-Stable and
was wondering how well current performs with these.I have current
running on a few desktop systems here so running it is no
prob..reccomendations?
William
To Unsubscribe: send mail to majord...@freebsd.org
with
On Thu, 13 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> An old 486 of mine still cant see its IDE driver with versions of ata-all.c
> later than 1.8, and my soundcard (PAS16) still doesn't seem to generate
> interrupts since the nexus stuff went in.
my stock SB16 + free
I had two systems reboot at nearly the same time. (30 seconds apart), and
are completely unrelated.
One system was running 2.2.8, and my core file presents me with this:
su-2.02# gdb -k
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show cop
> On whose authority do you say that? Garrett is a core team member.
I heard from Asami-san, Any voting not yet for new-bus. After
that, "new-bus patch" merge is decided. new-bus merge is core
decision, but "drop static configration", ... these are not yet voted.
> Then explain to us why newbus i
> Because if it's a day of coding, you should just do it. If it's a 3
> month project, you don't waste such time, and you should communicate it.
> The time factor is judged by folks who code for a living, and maybe it's
> a little high, but not too bad. I haven't seen this rule misapplied,
> but
On Wed, 12 May 1999, David Schwartz wrote:
>
> > I have to comment on this, it's too outrageous. Several times in the
> > past, folks have written in and asked, if they wrote some particular
> > piece of software, would it get committed. They said that it was a
> > large undertaking, and that t
An old 486 of mine still cant see its IDE driver with versions of ata-all.c
later than 1.8, and my soundcard (PAS16) still doesn't seem to generate
interrupts since the nexus stuff went in.
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a mil
> I have to comment on this, it's too outrageous. Several times in the
> past, folks have written in and asked, if they wrote some particular
> piece of software, would it get committed. They said that it was a
> large undertaking, and that they wouldn't undertake it, unless there was
> general
On Thu, 13 May 1999, Noriyuki Soda wrote:
> This doesn't answer my wondering. The core members can safely postpone
> the decision after Usenix, because all of core members must know that
> both new-bus people and newconfig people will come to Freenix track.
> Who is the chair of Freeunix track ? :
I've just had some convincing reports that Vinum in current doesn't
work at the moment. This is almost certainly something to do with the
change in the representation of device numbers, and it's something
I've been half expecting, but I don't have time to look at it this
week. If you're using Vin
On Wed, 12 May 1999, Mike Smith wrote:
> > This option should automatically select the appropriate sources
> > which is compiled into kernel, according to the source is needed
> > only in UP case, or only in SMP case, or both. This is what
> > oldconfig and newconfig does.
>
> This is, aga
Mikael Karpberg wrote:
> That would be so lovely, with a DEVFS too:
> Plug your Cool card into your pcmcia slot, and get the message on
> the sytem console that an unknown pcmcia card called "Cool", made
> by CoolMakers, Inc. Damn... not even a generic driver wanted this card.
> Pull the card
> On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote:
> > > well, I wonder if other people have noticed this also, but if you don't
> > > have a previous boot loader installed (like windows/dos) the ONLY way
> > > to install onto a machine is TO use a dangerously dedicated mode...
> >
> >
On Thu, May 13, 1999 at 12:16:17PM +1200, a little birdie told me
that Joerg Micheel remarked
>
> Virgin systems is not virgin disks. If you buy a complete PC, this
> bootloader from Redmonton is already on the disk. I had similiar
> problems a while back and unless someone has explicitely looked
Mike,
On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote:
> > well, I wonder if other people have noticed this also, but if you don't
> > have a previous boot loader installed (like windows/dos) the ONLY way
> > to install onto a machine is TO use a dangerously dedicated mode...
>
> This
On Thu, 13 May 1999, Noriyuki Soda wrote:
>
> It is actually true that FreeBSD becomes Linux.
>
It is truely unfortunate that it comes to this..
however it has always been to me a source of great frustration to me that
Linus was able to implement a driver framework that allows a very dynamic
> This doesn't answer my wondering. The core members can safely postpone
> the decision after Usenix, because all of core members must know that
> both new-bus people and newconfig people will come to Freenix track.
I'm not sure this was adequate reason to postpone the decision either,
and like I
On Wednesday, 12 May 1999 at 18:41:15 +0200, Gianmarco Giovannelli wrote:
> At 12/05/99, you wrote:
>>
>> At least put DDB in your kernel, type "trace" when it
>> panics and tell us what it says.
>
> Ok... it's a bit long ... (Tell me there isn't a command to write the trace
> output on a disk :-)
> Mike Smith scribbled this message on May 12:
> > >
> > > no, it's a "dangerously dedicated" SCSI disk.
> >
> > That's never a good start.
>
> well, I wonder if other people have noticed this also, but if you don't
> have a previous boot loader installed (like windows/dos) the ONLY way
> to ins
< said:
> Have you ever asked to newconfig people?
> No, no one of core members who takes charge of kernel part contacted
> to newconfig people, ever.
It's your responsibility to communicate with us, not the other way
around. The only way for your views to be even considered is for you
to make t
> > NetBSD people have not the same stated aim of completely eliminating
> > config, so for them it made more sense to migrate to config.new.
>
> I think it's also safe to say that because of NetBSD's interest in
> supporting 'older' hardware, it would be suicide to use a truly dynamic
> scheme
Mike Smith scribbled this message on May 12:
> >
> > no, it's a "dangerously dedicated" SCSI disk.
>
> That's never a good start.
well, I wonder if other people have noticed this also, but if you don't
have a previous boot loader installed (like windows/dos) the ONLY way
to install onto a machin
> NetBSD people have not the same stated aim of completely eliminating
> config, so for them it made more sense to migrate to config.new.
I think it's also safe to say that because of NetBSD's interest in
supporting 'older' hardware, it would be suicide to use a truly dynamic
scheme since much of
ok,
here is a reason for all this...
It has benn a common thought among the FreeBSD people I have spoken too
(and that's nearly all of the main developers, INCLUDING bill Jolitz)
that with cheaper RAM and better organosed busses teh way to go is
towards removing all static devoce information from
Is there an alternative way of specifying where system dumps are to go
similar to the now obsolete:
config kernel root on da0s1 dumps on da0s1b
line? I am experiencing a panic on a recently cvsuped -current kernel
and need to get a crash dump during boot (prior to dumpon being
executed).
Tha
> > It is actually true that FreeBSD becomes Linux.
> Comments like this will only ensure that you wind up in kill files,
> mine included. They add nothing to the discussion.
I see, sorry.
--
soda
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body
It seems Mike Smith wrote:
>
> > It is actually true that FreeBSD becomes Linux.
>
> This is a childish troll, especially coming from you. If for no other
> reason, this is an excellent reason _not_ to be working with your team.
Oh boy...
Could we end this now please ??
We've made our decisi
> It is actually true that FreeBSD becomes Linux.
Comments like this will only ensure that you wind up in kill files,
mine included. They add nothing to the discussion.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> > On Wed, 12 May 1999 15:09:05 -0700, Mike Smith said:
>
> > It would appear that you don't understand the problem, as no
> > configuration technique can telepathically determine in advance which
> > new drivers you are going to load.
>
> Apparently you misunderstand newconfig. :-)
> The
> On Wed, 12 May 1999 15:09:05 -0700, Mike Smith said:
> It would appear that you don't understand the problem, as no
> configuration technique can telepathically determine in advance which
> new drivers you are going to load.
Apparently you misunderstand newconfig. :-)
There is compiled f
On Wednesday, 12 May 1999 at 15:37:40 +0200, Dag-Erling Smorgrav wrote:
> I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing
> me some pains. If I boot with flags 0x80ff, everything works fine:
>
> wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
> wdc0: unit 0 (wd0): , 32-bit, multi-block
On Wednesday, 12 May 1999 at 15:01:51 +0200, Christian Carstensen wrote:
>
> Hi,
>
> Does anyone else experience problems with the current kernel release
> and vinum?
> I've compiled a new kernel along with a make world today. After rebooting
> vinum did not start: "/dev/vinum/Control: invalid oper
>/usr/local/bin/jade -V html-manifest -ioutput.html -c
/usr/doc/share/sgml/catal
>og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c
/usr/local/share/sg
>ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d
/usr/doc/share/
>sgml/freebsd.dsl -t sgml handbook.sgml
>/usr/local/b
> On Wed, 12 May 1999 14:53:31 -0700,
"Jordan K. Hubbard" said:
>> I agree that this is better way to solve the conflicts between new-bus
>> and newconfig. Although I wondered why FreeBSD's core decide to choose
>> new-bus before Usenix.
> We didn't choose it "before USENIX" as if
> Mike Smith once wrote:
>
> > For a usable dynamic architecture, loadable modules need to be
> > compiled to support both UP and SMP architectures simultaneously. Thus
> > the locking primitives need to be conditionalised at _runtime_.
>
> What about
>
> kldload /modules/up/whatev
Mikael Karpberg wrote:
> According to Mike Smith:
> > This is actually a major defect in the newconfig design; if the kernel
> > doesn't already know about a device when it is built, it can never
> > support it.
>
> That would be so lovely, with a DEVFS too:
>
> Plug your Cool card into your pcmc
Mike Smith once wrote:
> For a usable dynamic architecture, loadable modules need to be
> compiled to support both UP and SMP architectures simultaneously. Thus
> the locking primitives need to be conditionalised at _runtime_.
What about
kldload /modules/up/whatever.ko
and
According to Mike Smith:
> This is actually a major defect in the newconfig design; if the kernel
> doesn't already know about a device when it is built, it can never
> support it.
That would be so lovely, with a DEVFS too:
Plug your Cool card into your pcmcia slot, and get the message on
the syt
> > Why should we, as a 3rd millenium OS need a static config tool ?
>
> For example,
>
> - To specify the drivers which is linked statically to kernel.
> As I said earlier, you cannot link console driver dynamically,
> If you do this, you cannot get error message when dynamic
> linking of
Noriyuki Soda wrote:
> NOTE: Please Cc: s...@sra.co.jp, I am not subscribing this mailing
> list, because I am a NetBSD user. :-)
Aha! Now a few things are starting to make sense...
> > > It depends on old-config, so poor mechanism. newconfig already
> > > implimented best match probe/atta
now now :-)
On Wed, 12 May 1999, Matthew Dillon wrote:
> Maybe whoever committed the supposedly innocuous dev_t changes should
> back it out.
>
> Just a thought.
>
> -Matt
> Matthew Dillon
>
> NOTE: Please Cc: s...@sra.co.jp, I am not subscribing this mailing
> list, because I am a NetBSD user. :-)
>
> > > It depends on old-config, so poor mechanism. newconfig already
> > > implimented best match probe/attach.
> >
> > And a very useful mechanism it is. Which is why I implemente
>
> no, it's a "dangerously dedicated" SCSI disk.
That's never a good start.
> the loader shows the floppy as DISK A and the SCSI disk as DISK B.
Are you sure it lists the SCSI disk as B and not C? If it's showing up
as B your BIOS is doing funny stuff.
--
\\ Sometimes you're ahead,
> Pardon, but I am not be able to figure by myself what you asked to me...
> If you can explain me step by step in a newbie way I can do everything ...
> The crashes is easily reproducible...
No offense, but are you sure you should even be running -current? A
certain amount of skill in doing such
> I agree that this is better way to solve the conflicts between new-bus
> and newconfig. Although I wondered why FreeBSD's core decide to choose
> new-bus before Usenix.
We didn't choose it "before USENIX" as if it were somehow part of the
objective to get this feature in before a public event,
In message <65947.926544...@zippy.cdrom.com>, "Jordan K. Hubbard" writes:
>> Try disabling "ultra DMA" in the BIOS, that seems to have worked for
>> me on my IBM-DJNA-371800 drive.
>>
>> (Jordan: We may want to put something in the README about this in 3.2!)
>
>I'd welcome suggestions as to what t
In message <199905122048.qaa72...@misha.cisco.com>, Mikhail Teterin writes:
>Or, the core team may just say: "Because we said so" (which I think was
>already done once) and stop discussing this...
We did I think.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org
Maybe everybody should read to the end of their mailboxes before
they come forward with baseless and unfounded snide remarks.
And I never said they were "innocuous". This is Current mind you.
Poul-Henning
In message <199905122048.naa88...@apollo.backplane.com>, Matthew Dillon writes:
>Mayb
> Try disabling "ultra DMA" in the BIOS, that seems to have worked for
> me on my IBM-DJNA-371800 drive.
>
> (Jordan: We may want to put something in the README about this in 3.2!)
I'd welcome suggestions as to what the text should look like; I'm
still unclear as to what exactly the problem us. :
MS is trying desperatly to fight off and contained Linux and I am not
sure that Microsoft will succeed
--
Amancio Hasty
ha...@star-gate.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Ustimenko Semen wrote:
>On Tue, 11 May 1999, Luigi Rizzo wrote:
...
>> http://research.microsoft.com/programs/NTSrcLicInfo.htm
>>
>> Microsoft makes Windows NT source code available to universities
>> and other "not-for-profit" research institutions at no charge.
...
>P.S. What's happenin
Mikhail Teterin says:
:
: Perhaps, the newbus vs. newconfig discussion can be summarized to both
: sides' satisfaction offline and then presented to the rest of the world?
But didn't this already happen. I seem to recall a round of discussions
that went on a week before the new-bus switch. T
> On Wed, 12 May 1999 12:12:54 -0700 (PDT),
Julian Elischer said:
> The eventual aim is to have a kernel which is a very sparse skelaton,
> with very few services and drivers loaded (in fact possibly none).
This is also aim of newconfig, although console driver should be
linked stati
"Jordan K. Hubbard" wrote:
> Should I just turn NODOC on for the -current snapshot builds? The problem
> is that I'm not getting *any* -current (or releng3, for that matter)
> snapshots out at releng3.freebsd.org and current.freebsd.org because
> on the days when src isn't broken, the handbook is
Dag-Erling Smorgrav once wrote:
As an outside observer, who does not understand most (all?) of the
differences involved, I must say, this will have to be an unfairly
"uphill" explanation. Because, using the style exemplified by PHK today,
the newconfig people could say something like:
Maybe whoever committed the supposedly innocuous dev_t changes should
back it out.
Just a thought.
-Matt
Matthew Dillon
:
:It looks like something has come unstuck
/usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catal
og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sg
ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/
sgml/freebsd.dsl -t sgml handbook.sgml
/usr/local/bin/ja
> Wilko Bulte wrote:
> > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> > Writing Makefile for DynaLoader
> > ==> Your Makefile has been rebuilt. <==
> > ==> Please rerun the make command. <==
> > false
> > false: not found
> > *** Error code 1
>
> I periodically see this one reported, and It
:I think we need to think a bit more about the right semantics before
:making such a change. M_WAIT is supposed to mean `I am in process
:context and don't mind sleeping in order to get an mbuf, but there is
:too much locking going on inside the network stack to be able to
:safely sleep without se
As Gianmarco Giovannelli wrote ...
>
> In 4.0-current sometimes the box will froze again after the :
> "Waiting 3 seconds for SCSI devices to settle"
> then nothing happens.
> It was a thing happened also in early 1999, before the branch in
> 4.0-current and 3.1 stable, if I remember well.
>
> An
As e...@habatech.no wrote ...
>
> On 12-May-99 Ustimenko Semen wrote:
> >
> > Are we going to get this license? I am interested in NTFS
> > source code a lot...
> >
> > P.S. What's happening with MS?
> >
> They have got a virus. I think they're calling it Open Source...
Na... it's called US
Ustimenko Semen wrote:
>
> Hi,
>
> On Tue, 11 May 1999, Luigi Rizzo wrote:
>
> > Hi,
> > maybe i am the last one in the world to know, but were you guys aware
> > of this:
> >
> > http://research.microsoft.com/programs/NTSrcLicInfo.htm
> >
> > Microsoft makes Windows NT source code available
i tried it, i belive it's only for SCSI scanners, my UMAX 1220P is for the
parallel port.
On Wed, 12 May 1999, Edwin Culp wrote:
> Have you tried /usr/ports/graphics/sane?
>
> ed
--
==
Tomer Weller
s...@i.am
well...@netvision.net.il
"Drugs are good, and if
My personal opinion is that static configuration is a subset of dynamic
configuration.
The eventual aim is to have a kernel which is a very sparse skelaton,
with very few services and drivers loaded (in fact possibly none).
At boot time, the needed drivers and services are loaded and configured
(
I also am experiencing a kernel panic whenever I start X using today's
kernel. Thanks
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
NAKAGAWA Yoshihisa writes:
> > mechanism was unacceptable -- else we would have used it years ago.
> It is not formal core decision.
On whose authority do you say that? Garrett is a core team member.
> > Our policy in all areas has been that we'd rather do the Right Thing
> > than follow the cro
On Wed, 12 May 1999, Mark Murray wrote:
> Bob K wrote:
> > Well, I did some reading through rfc821, and an email address is defined
> > as follows:
>
> Email addresses != Usernames. What this suggests to me is that having
> an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
Sigh.
In the last episode (May 12), Mark Murray said:
> Bob K wrote:
> > Well, I did some reading through rfc821, and an email address is
> > defined as follows:
>
> Email addresses != Usernames. What this suggests to me is that having
> an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
On Wed, 12 May 1999, David Wolfskill wrote:
> >Date: Wed, 12 May 1999 14:15:12 -0400 (EDT)
> >From: Bob K
>
> >People on -current: Just to recap, adduser (and rmuser) disallow .'s in
> >usernames on FreeBSD-stable; passwd(5) cites that some mailers have
> >problems with dots in usernames. Howe
Bob K wrote:
> Well, I did some reading through rfc821, and an email address is defined
> as follows:
Email addresses != Usernames. What this suggests to me is that having
an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.ca
>Date: Wed, 12 May 1999 14:15:12 -0400 (EDT)
>From: Bob K
>People on -current: Just to recap, adduser (and rmuser) disallow .'s in
>usernames on FreeBSD-stable; passwd(5) cites that some mailers have
>problems with dots in usernames. However, they are becoming more common,
>and are a legal part
Wilko Bulte wrote:
> PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> Writing Makefile for DynaLoader
> ==> Your Makefile has been rebuilt. <==
> ==> Please rerun the make command. <==
> false
> false: not found
> *** Error code 1
I periodically see this one reported, and It is always repaired
b
On Wed, May 12, 1999 at 10:28:45AM -0700, David O'Brien wrote:
> > > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure
> > > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT.
> ..snip..
>
> > Have you tried /usr/ports/graphics/sane?
>
> It doesn't build under 4.0
Well, I did some reading through rfc821, and an email address is defined
as follows:
::= "@"
::= |
::= | "."
^^^ !
::= |
::= """ """
::= "\" | "\" | |
::= | "\"
::= any one of the 128 ASCII characters, but not any or
::= any one of the 128 ASCII characters (no exce
I bought two of the cards in order to decide whether or not I wanted
to use them in my research group's PII cluster. Right now, they're
plugged into a 233MHz Pentium Pro and a 400Mhz K6-2 (using an
Aladdin V-based board). I did a bunch of NFS testing over the
gigabit link last week and didn't see
Pierre Beyssac writes:
> if (resid >= MINCLSIZE) {
> MCLGET(m, M_WAIT);
> + if (m == 0) {
> + error = ENOBUFS;
> + goto release;
> +
Joe Abley writes:
> (he asked :)
As I understand it, 3.2 is simply a release tag on the already existing
branch called RELENG_3 (aka 3.1-stable). So there will be no additional
branch for 3.2, just a release tag: RELENG_3_2_0 or somesuch.
-Archie
_
Hello Geoff,
Wednesday, May 12, 1999, 4:35:54 PM, you wrote:
GR> I'm currently running into a problem, that when I start my system,
GR> it spontaneously reboots when starting X. Has anyone else run into
GR> this?
yes, i'm experiencing the same problem with today's (May, 12) kernels.
Best rega
> > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure
> > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT.
..snip..
> Have you tried /usr/ports/graphics/sane?
It doesn't build under 4.0-CURRENT.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To U
< said:
> Another big problem is that there's a check in m_retry and friends
> that panics when falling short of mbufs! I really believe this does
> more harm than good, because it prevents correct calling code
> (checking for NULL mbuf pointers) from exiting gracefully with
> ENOBUFS...
I think
At 12/05/99, you wrote:
>Ok, what I'd like you to do is, run this command,
> nm -n /kernel | more
>the output is the list of symbols in the kernel sorted by their addresses
>(the left-most column), page through the output, find symbols around the
>address 0xc0155ca4, and send me those symbol
At 12/05/99, you wrote:
>
>At least put DDB in your kernel, type "trace" when it
>panics and tell us what it says.
Ok... it's a bit long ... (Tell me there isn't a command to write the trace
output on a disk :-)
After the panic make by "screen" ...
>trace
Stopped at ttyflush+0x48: movl 0x14(%eax)
> On Wed, 12 May 1999 17:45:45 +0200,
Poul-Henning Kamp said:
>> What is the definition of "config"?
> config(8)
>> Why do you want to remove it?
> Why should we, as a 3rd millenium OS need a static config tool ?
For example,
- To specify the drivers which is linked statica
From: Poul-Henning Kamp
Subject: Re: cvs commit: src/sys/pci pcisupport.c
Date: Wed, 12 May 1999 17:45:45 +0200
Message-ID: <5756.926523...@critter.freebsd.dk>
phk>
phk> >phk> >Since newconfig appears technically superior, what are the
issues that
phk> >phk> >are hindering its acceptance?
On Wed, 12 May 1999, Stefan Bethke wrote:
> Any pointer on Forth literature/web pages would be appreciated, especially
> if it's not the ANSI standard (I've looked at it, and it is that: a
> standard, not a reference manual or a tutorial). My Forth knowledge is
> rather rusty, I realised... last
On Wed, May 12, 1999 at 05:43:27PM +0200, Stefan Bethke wrote:
> I've discussed this with Garett back in September. The reason is quite
> simple: unless all cases of not checking for a NULL pointer returned are
> fixed (or instrumented with a panic), it is better to fail with a panic
> than with s
Only one problem with that - screen and keyboard are not responding when
it panics. I'm hoping that I will be able to get a dump which I can
look at post mortem.
I'm going to try again though. The kernel I have at the moment is
totally messing up my keyboard, and I cannot even get a single user
At least put DDB in your kernel, type "trace" when it
panics and tell us what it says.
In message <19990512154854.78032.qm...@rucus.ru.ac.za>, "Geoff Rehmet" writes:
>Luoqi Chen writes :
>
>I'm trying to get a crash dump myself, but the kernel I have
>right now, is screwing up my keyboard, and I
Luoqi Chen writes :
I'm trying to get a crash dump myself, but the kernel I have
right now, is screwing up my keyboard, and I cannot even log
in!
I will try again.
Geoff.
> > After make world this morning I received this panic :
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault vi
>phk> >Since newconfig appears technically superior, what are the issues
>that
>phk> >are hindering its acceptance?
>phk>
>phk> That we want to have no "config" at all.
>
>That is too short an answer.
No, it is complete and to the point.
>What is the definition of "config"?
config
Pierre Beyssac wrote:
> Another big problem is that there's a check in m_retry and friends
> that panics when falling short of mbufs! I really believe this does
> more harm than good, because it prevents correct calling code
> (checking for NULL mbuf pointers) from exiting gracefully with
> ENO
1 - 100 of 164 matches
Mail list logo
