On 3/04, John Polstra wrote:
[don't allocate big structs on kernel stack]
Many years ago, I wrote a tool that analysed stack requirements by
parsing the assembler output from the compiler. It determined the
stack frame requirements and built a call flow graph to determine
total stack depth. It
On Thu, 13 Apr 2000, Warner Losh wrote:
> bsd.libnames.mk:
>
> .if defined(NOSHARED) && ${NOSHARED} != "no" && ${NOSHARED} != "NO"
>
> is where I saw it.Warner
Okay, thats probably the single case in the tree then :-)
Kris
In God we Trust -- all others must submit an X.509 certificate.
In message <[EMAIL PROTECTED]> Kris
Kennaway writes:
: Like where? I certainly didn't come across any of these when I did a sweep
: of /usr/src for 'NOxxx'.
bsd.libnames.mk:
.if defined(NOSHARED) && ${NOSHARED} != "no" && ${NOSHARED} != "NO"
is where I saw it.Warner
To Unsubscribe: send mail
On Thu, 13 Apr 2000, Warner Losh wrote:
> Is that still true? I've been seeing more and more things that used
> to be
> .if !defined(NOFOO)
> morph into
> .if !defined(NOFOO) && ${NOFOO} != "no" && ${NOFOO} != "NO"
Like where? I certainly didn't come across any of these when I did a
In message <[EMAIL PROTECTED]> Kris
Kennaway writes:
: rc.conf cares about the value of the variable. make.conf does not (for
: most of them), and just cares whether the variable is set at all
: (i.e. they're not booleans)
Is that still true? I've been seeing more and more things that used
to b
On Thu, 13 Apr 2000, David O'Brien wrote:
...
> Sounds like linux_pam would make a nice port.
No.
I don't think that the patch for linux_base:
--- Makefile.oldThu Apr 13 23:28:55 2000
+++ MakefileThu Apr 13 23:29:58 2000
@@ -90,2 +90,3 @@
readline-2.2.1-5.${MACH
On Wed, Apr 12, 2000 at 12:17:03AM +0200, Michael Reifenberger wrote:
> > I don't think pam is a development tool, which makes linux_devtools the
> > wrong port. I also don't think we need pam in any other port if it's
...
> In this case, you are right.
> The problem is generally that linux ports
Hi,
when using a linux java app (SAP PlatinGUI 46Cb2) I get the above panic.
FreeBSD -current. Kernel+mods in sync.
Linux from ports. Linux-Java-JDK 1.2.2 from blackdown as of yesterday.
Backtrace see crash.txt. Kernelconfig see nihil.
Any thoughts anyone?
Bye!
Michael Reifenberger
^.*Plaut.
On Thu, 13 Apr 2000, Thomas T. Veldhouse wrote:
> You are correct. We seem to have some odd conventions. "YES" in rc.conf
> and "TRUE" in make.conf.
rc.conf cares about the value of the variable. make.conf does not (for
most of them), and just cares whether the variable is set at all
(i.e. the
-On [2412 01:35], Walter Brameld ([EMAIL PROTECTED]) wrote:
>I see the same thing on 4.0-STABLE, so far only using linux-netscape.
>When I go to select a directory for download, or when accessing an HTML
>file to be opened, certain directories always appear to be missing.
>Only one that comes
On Mon, 10 Apr 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]>
>[EMAIL PROTECTED] writes:
> : On the same hardware
> : 3.4 and 4.0 sees pcic0 on 0x3e2, but with CURRENT kernel don't see it
> : and don't say anything about pcic when booted with -v
> :
> : But when I've changed ioaddr o
>
> Well ... for that purpose I'd vote for the following:
>
> a) make more
> NO_ (sendmail, bind, whatever)
>knobs in /etc/make.conf as needed
> b) make the Makefiles in the install target more complete by
>removing (old) occurrencies of sendmail, bind, if such a
>NO_XXX knob has
> > Maybe I missed something - but I think you want "YES" instead of "true".
>
> It says true in /etc/defaults/make.conf. That is why I used it instead of
> YES or yes.
>
> > Tom Veldhouse
> > [EMAIL PROTECTED]
> >
You are correct. We seem to have some odd conventions. "YES" in rc.conf
and "
unsubscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 11:21 PM -0700 2000/4/12, Jordan K. Hubbard wrote:
> They subsequently disappeared into the same black hole which swallows
> so many prospective volunteers, it seems, and all that was left to
> mark the event was the echos of thread in the mail archives. :-)
Sorry, my fault. I sho
15 matches
Mail list logo
