I tried doing the same on FreeBSD 3.2-STABLE
but when I run it it complains that it is unable to find dynamic linker
breakpoint function and then it stops with a SIGTRAP.
Any ideas what might be wrong?
Thanks.
-Kip
On Fri, 20 Aug 1999, Richard Cownie wrote:
> I
< said:
[I wrote:]
> : And designs based on the Intel PIIX4 will generate SMI# interrupts for
> : whichever activities are programmed in the BIOS, completely bypassing
> : the traditional interrupt mechanism.
> So does that mean if we do disable them at the PIC level we'll be OK?
No, it means i
Hi,
I'm seeing the following error during a 'make release' with
sources current as of 4:30pm EST. I'll re-cvsup, and try again,
but I don't see (via the cvsweb) any commits that would fix this.
cd /usr/src/sys/i386/conf && config -r GENERIC &&
cd ../../compile/GENERIC && make depend
I notice that -current supports the 3C574, but not the newer 3C574B.
Is anyone working on support for this card?
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Matthew D. Fuller" <[EMAIL PROTECTED]> writes:
> On Wed, Sep 01, 1999 at 09:20:44PM +0800, a little birdie told me
> that Peter Wemm remarked
> >
> > 23> cat /home/ncvs/CVSROOT/options
> > tag=FreeBSD=CVSHeader
> > tagexpand=iFreeBSD,Id
>
> Speaking of the whole subject, where is this (method
Daniel O'Connor wrote in list.freebsd-current:
> On 31-Aug-99 Kevin Street wrote:
> > > Well 2MB/sec == 14x CDRom drive. Is it a 14x CDRom drive? CDRom
> > > drives are typically limited to how quickly they can get data off
> > > the platter. A faster bus transfer will not impro
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : It's reasonable to assume this, yes. However it's also worth bearing
> : in mind that since the BIOS isn't using these interrupts to _detect_
> : activity, turning them off is pretty pointless.
>
> Then why does the key up event cause the
> In message <[EMAIL PROTECTED]> Garrett
> Wollman writes:
> : And designs based on the Intel PIIX4 will generate SMI# interrupts for
> : whichever activities are programmed in the BIOS, completely bypassing
> : the traditional interrupt mechanism.
>
> So does that mean if we do disable them at
In message <[EMAIL PROTECTED]> Mike Smith writes:
: It's reasonable to assume this, yes. However it's also worth bearing
: in mind that since the BIOS isn't using these interrupts to _detect_
: activity, turning them off is pretty pointless.
Then why does the key up event cause the suspend to
In message <[EMAIL PROTECTED]> Garrett
Wollman writes:
: And designs based on the Intel PIIX4 will generate SMI# interrupts for
: whichever activities are programmed in the BIOS, completely bypassing
: the traditional interrupt mechanism.
So does that mean if we do disable them at the PIC level
>> After the import of ncurses 5.0 (beta?), I noticed strange behavior of clear
>> on my xterm. I tracked it down to an API change of tgetstr(), here is the
>> new code:
>>
>> char *tgetstr(NCURSES_CONST char *id, char **area GCC_UNUSED)
>
>It is definitely bug on ncurses side and must be fix
On Wed, Sep 01, 1999 at 09:20:44PM +0800, a little birdie told me
that Peter Wemm remarked
>
> 23> cat /home/ncvs/CVSROOT/options
> tag=FreeBSD=CVSHeader
> tagexpand=iFreeBSD,Id
Speaking of the whole subject, where is this (method of defining tags)
documented? I've searched every bit of CVS doc
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> In message <[EMAIL PROTECTED]>, Garrett Wollman writes:
>> >< said:
>> >
>> >> Actually, that's almost entirely system-dependant. The BIOS may well
>> >> poll the keyboard controller/USB controller, for example.
>> >
>> >And designs based on
> In message <[EMAIL PROTECTED]>, Garrett Wollman writes:
> >< said:
> >
> >> Actually, that's almost entirely system-dependant. The BIOS may well
> >> poll the keyboard controller/USB controller, for example.
> >
> >And designs based on the Intel PIIX4 will generate SMI# interrupts for
> >which
Thanks.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Wed, 1 Sep 1999, Nathan Ahlstrom wrote:
> "Arthur H. Johnson II" <[EMAIL PROTECTED]> wrote:
> > When I try to compile the kernel, I get this error at the end:
> >
> > ../../pci/if_xl.c
> > ../../pci/if
For the person who helped me with my xl driver kernel compile, thanks. I
am alittle pine expunge happy!
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messag
"Arthur H. Johnson II" <[EMAIL PROTECTED]> wrote:
> When I try to compile the kernel, I get this error at the end:
>
> ../../pci/if_xl.c
> ../../pci/if_xl.c:133: miibus_if.h: No such file or directory
> *** Error code 1
>
> Stop in /usr/src/sys/compile/ARTHUR.
> You must first build a kernel fir
When I try to compile the kernel, I get this error at the end:
../../pci/if_xl.c
../../pci/if_xl.c:133: miibus_if.h: No such file or directory
*** Error code 1
Stop in /usr/src/sys/compile/ARTHUR.
You must first build a kernel first.
*** Error code 1
Stop in /usr/src/sys/compile/ARTHUR.
What
On Wed, Sep 01, 1999 at 09:52:10AM -0400, Luoqi Chen wrote:
> After the import of ncurses 5.0 (beta?), I noticed strange behavior of clear
> on my xterm. I tracked it down to an API change of tgetstr(), here is the
> new code:
>
> char *tgetstr(NCURSES_CONST char *id, char **area GCC_UNUSED)
Doug White wrote:
> On Tue, 31 Aug 1999, Mark J. Taylor wrote:
>
> > I've got a -STABLE GENERIC kernel, cvsupped and built this evening,
> > that is all alone on a UFS floppy, and kgzipped.
>
> I thought kzip is for a.out only. You can kzip /boot/loader and gzip
> /kernel though.
Yes and No, if
On Wed, Sep 01, 1999 at 09:08:45AM -0400, Kevin Street wrote:
> "William R. Somsky" <[EMAIL PROTECTED]> writes:
>
> > Hmm... but what about if you're cvsup-ing the sources?
> > I'm cvsup-ing stable, not current, (cvsup file included below)
> > and $FreeBSD appears all over the place unexpanded.
Poul-Henning Kamp wrote:
>
> Peter must have forgotten some changes, until he fixes it,
> you can use this patch to revert his change to isa.c
Yeah, sorry folks. I am running that code right now (and have been for
weeks) but it was dependent on another pending change that I had forgotten.
It sh
On Tue, 31 Aug 1999, Mark J. Taylor wrote:
> I've got a -STABLE GENERIC kernel, cvsupped and built this evening,
> that is all alone on a UFS floppy, and kgzipped.
I thought kzip is for a.out only. You can kzip /boot/loader and gzip
/kernel though.
Doug White
Int
Peter Wemm writes:
>Make sure you are fetching src-all, and if you are not getting src-anything,
>then either get src-base or set up $CVSROOT/CVSROOT/options to this:
>
>23> cat /home/ncvs/CVSROOT/options
>tag=FreeBSD=CVSHeader
>tagexpand=iFreeBSD,Id
>
>Fetching src-base will do this for you, as
On Sat, 28 Aug 1999, Matthew Dillon wrote:
> * Adds a new feature to VN - swap space pre-reservation,
> in addition to the two features already added (zeroing
> and file creation/truncation).
Sounds great to me. I really hope you also update the manpage for vn(4)
and vnconf
Peter must have forgotten some changes, until he fixes it,
you can use this patch to revert his change to isa.c
Index: isa.c
===
RCS file: /home/ncvs/src/sys/i386/isa/isa.c,v
retrieving revision 1.130
diff -u -r1.130 isa.c
--- isa.c
In message <[EMAIL PROTECTED]>, Garrett Wollman writes:
>< said:
>
>> Actually, that's almost entirely system-dependant. The BIOS may well
>> poll the keyboard controller/USB controller, for example.
>
>And designs based on the Intel PIIX4 will generate SMI# interrupts for
>whichever activities
After the import of ncurses 5.0 (beta?), I noticed strange behavior of clear
on my xterm. I tracked it down to an API change of tgetstr(), here is the
new code:
char *tgetstr(NCURSES_CONST char *id, char **area GCC_UNUSED)
{
int i;
T((T_CALLED("tgetstr(%s,%p)"), id,
< said:
> Actually, that's almost entirely system-dependant. The BIOS may well
> poll the keyboard controller/USB controller, for example.
And designs based on the Intel PIIX4 will generate SMI# interrupts for
whichever activities are programmed in the BIOS, completely bypassing
the traditiona
Kevin Street wrote:
> "William R. Somsky" <[EMAIL PROTECTED]> writes:
>
> > Hmm... but what about if you're cvsup-ing the sources?
> > I'm cvsup-ing stable, not current, (cvsup file included below)
> > and $FreeBSD appears all over the place unexpanded. Is this
> > the way it's supposed to be?
"William R. Somsky" <[EMAIL PROTECTED]> writes:
> Hmm... but what about if you're cvsup-ing the sources?
> I'm cvsup-ing stable, not current, (cvsup file included below)
> and $FreeBSD appears all over the place unexpanded. Is this
> the way it's supposed to be? Isn't cvsup supposed to be
> (ef
> Should the "#include " in telnet.c be protected with a
> "#ifdef TERMCAP"?
Dunno. I have removed it from 2 builds - one clean and one with all
my crypto gunk (both failed, BTW). One box will take 1.5 hours, the
other will take 3.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.o
> > > invalid use of undefined type `struct termio'
> >
> > I suspect it's related to the international secure dist being out of sync.
> > Make sure there's no -DTERMCAP in the telnet Makefiles...
>
> Nope. The makefiles are in src/kerberosIV/... and they are not
> export restricted.
Well I'm n
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > invalid use of undefined type `struct termio'
>
> I suspect it's related to the international secure dist being out of sync.
> Make sure there's no -DTERMCAP in the telnet Makefiles...
Nope. The makefiles are in src/kerberosIV/... and they are not
export restricted.
M
--
Mark Murray
Join th
> invalid use of undefined type `struct termio'
> /usr/src/kerberosIV/usr.bin/telnet/../../../crypto/telnet/telnet/telnet.c:2065:
> invalid use of undefined type `struct termio'
> /usr/src/kerberosIV/usr.bin/telnet/../../../crypto/telnet/telnet/telnet.c:2120:
I'm so glad you said this! I though
John Hay wrote:
> A "make release" on -current also breaks there. It looks like it might be
> related to the new ncurses import, because it complains about:
>
> invalid use of undefined type `struct termio'
I suspect it's related to the international secure dist being out of sync.
Make sure ther
A "make release" on -current also breaks there. It looks like it might be
related to the new ncurses import, because it complains about:
invalid use of undefined type `struct termio'
John
--
John Hay -- [EMAIL PROTECTED]
> Partway through a make world, I'm seeing the following, I've applied up
Pascal Hofstee wrote:
> Hi,
>
> Perl seems to be broken for about 3 consecutive days now
> Anybody have any idea what might be causing this ?
I suspect it is the recent changes in rtld.
Dima
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body o
Hi,
Perl seems to be broken for about 3 consecutive days now
Anybody have any idea what might be causing this ?
bash-2.03$ mirror /usr/local/lib/mirror/packages/daemonnews
DynaLoader:/usr/libdata/perl/5.00503/DynaLoader.pm:188 Caught a SIGSEGV
shutting down at /usr/local/bin/mirror line 38
Partway through a make world, I'm seeing the following, I've applied up to
cvs-cur.5622.gz and int-cvs-cur.0118.gz. Is this likely to be fixed sometime
soon?
Stephen
cc -O -pipe -mpentiumpro -fschedule-insns2 -DKLUDGELINEMODE -DUSE_TERMIO
-DENV_HACK -DSKEY -DENCRYPTION -DAUTHENTICAT
41 matches
Mail list logo
