On Mon, 16 Oct 2000, Bruce Evans wrote:
On Sun, 15 Oct 2000, Steve Kargl wrote:
Actually, in this case the endian.h change exposed a bug
if the wait(2) manpage is correct. In particular, sys/types.h
is required to occur before sys/wait.h, which was missing in
libdialog/prgbox.c and
s/i386/5.0-CURRENT-20001016-JPSNAP.log
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
brian I recently added the directory /usr/include/netnatm/ to
brian BSD.include.dist, and the ppp build now depends on this.
Would you please add netnatm to 'LDIRS' definition of src/include/Makefile ?
Without this, "make buildworld" fails just like this, since no header
file in
On Sun, 15 Oct 2000, Steven G. Kargl wrote:
There is another patch needed in libdialog.
No patches are needed in applications; endian.h should be unbroken.
In what way ?
ntohl() ntonl() were previously wrong to return u_long.
They now return uint32_t (which requires sys/types.h).
They
=== usr.sbin/ppp
rm -f .depend
mkdep -f .depend -a-DHAVE_DES -I/usr/obj/usr/src/i386/usr/include
/usr/src/usr.sbin/ppp/acf.c /usr/src/usr.sbin/ppp/arp.c /usr/src/usr.sbin/ppp/async.c
/usr/src/usr.sbin/ppp/auth.c /usr/src/usr.sbin/ppp/bundle.c
/usr/src/usr.sbin/ppp/cbcp.c
The problem that when random device was not seeded, boot simply hangs (on
ldconfig! why?) Ugly init(8) gives no chance to stop booting and fall to
reboot or single mode again via ctrl-alt-del or another key combination;
sleeping on "rndblk" channel in ldconfig is not interruptible; only DDB or
On Mon, 16 Oct 2000, Brian Somers wrote:
On Sun, 15 Oct 2000, Steven G. Kargl wrote:
There is another patch needed in libdialog.
No patches are needed in applications; endian.h should be unbroken.
In what way ?
endian.h shouldn't depend on sys/types.h or include sys/types.h and
Szilveszter Adam wrote:
Hmmm. It is good that the problem got resolved, but I take both 4.1 and
-CURRENT use the same gcc version... (2.95.2) Or am I missing something?
AFAIK, -CURRENT uses a snapshot of GCC 2.96 which may have some bugs.
It reports itself as 2.95.2.
There are two
On Mon, Oct 16, 2000 at 09:49:30AM +0100, Konstantin Chuguev wrote:
There are two directories in CURRENT's src/contrib: gcc and gcc.295 (the former is
fresher). In src/gnu/{usr.bin|lib} appropriate Makefile.inc files set .PATH to
.../.../gcc.295.
There seems to be no way to switch to
On Mon, 16 Oct 2000, Szilveszter Adam wrote:
Also, since 2.96 has not even been released yet, I assume the
maintainer (bruce, AFAIK) just makes sure that it builds and compiles
stuff OK and so by the time 5.0 will be released and hopefully 2.96
too, we just have to push the button and it will
After updating over the weekend to a recent current i noticed that it does
not wake up on lan activity anymore. This - nice - feature worked fine with
the Intel fxp card before (i can't even get into the machine now to cut and
paste the bootmessage because it wakes no longer up ..)
Is this a
Hi,
I have a question about syscons, and I was wondering if there were
anyone out there who knew enough about the initialization sequence of
syscons to answer...
Basically, I'm trying to write a TGA driver around syscons, but TGA
is a PCI card, and it seems, after having looked through
I got this error while compiling the last kernel:
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
-D_KERNEL -include opt_global.h -elf
From the keyboard of hm:
After updating over the weekend to a recent current i noticed that it does
not wake up on lan activity anymore. This - nice - feature worked fine with
the Intel fxp card before (i can't even get into the machine now to cut and
paste the bootmessage because it wakes
Build kernel breaks in pci_cfreg.c :
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
-D_KERNEL -include opt_global.h -elf -march=i686
In message [EMAIL PROTECTED] Valentin Chopov
writes:
: I got this error while compiling the last kernel:
Sorry about that. I committed some of mike's changes at his request
and didn't manage to commit them all. I've fixed this now.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
In message [EMAIL PROTECTED] Are Folkestad writes:
: Build kernel breaks in pci_cfreg.c :
I screwed up and didn't commit some bits. Please re cvsup and try
again. Sorry about that. It is all in the service of cardbus.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
David O'Brien wrote:
On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote:
We've blown out the kern.flp image. Time for me to chop something
out again, unless there are any other suggestions. :|
Mind if I commit this patch?
Index: dokern.sh
On 15-Oct-00 Wes Peters wrote:
David O'Brien wrote:
On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote:
We've blown out the kern.flp image. Time for me to chop something
out again, unless there are any other suggestions. :|
Mind if I commit this patch?
Index:
Just curious on the potential release of 5.0 -- which I presume won't be
until next year.. ?
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own slice)?
I do not think loader can see stuff in
On Tue, 17 Oct 2000, Terry Lambert wrote:
I could have a 40G /, and not worry about the cylinder spanning
problem, if my /boot were in a seperate (low) partition.
I could have a / that was of an FS type not understood by the
kernel, until after a module defining the FS type had been
loaded.
I
[ ... manual driver load from third floppy ... ]
The problem with such an approach is that it's not very user-friendly
to first-time installers who have no idea how to drive the loader.
Let's not forget the linux installation floppy saga and all the
confusion it's caused people just in
In article
[EMAIL PROTECTED], Daniel
Eischen [EMAIL PROTECTED] wrote:
So far I read this as saying the sched_XXX functions operate on
processes, whereas the pthread_{set|get}schedparam functions operate
on threads.
Me too.
(4) When a running thread calls the sched_setparam()
[EMAIL PROTECTED] wrote:
In article
[EMAIL PROTECTED], Daniel
Eischen [EMAIL PROTECTED] wrote:
For SCHED_FIFO and SCHED_RR, we don't have a problem because both
the threads library and kernel now agree that the range is 0..31.
SCHED_OTHER is a problem because the threads library
25 matches
Mail list logo
