In message [EMAIL PROTECTED] Bruce A. Mah writes:
: Unfortunately it's not guaranteed...a lot of new hardware has been
: released since December 1998 (the date of 2.2.8-RELEASE). :-p
Copy the 2.2.8 cdrom onto a disk. Put your sources in that tree.
Chroot. you now have the 2.2.8 compilers.
On Tue, Jul 17, 2001 at 10:43:44PM -0700, Eric Melville wrote:
Modified files:
gnu/lib/libdialogchecklist.c menubox.c radiolist.c
textbox.c tree.c yesno.c
Log:
Improve the interface provided by libdialog. Move a cursor around over
the
Hi -hackers,
I'm developing some assembly routines that are called from a C library
under FreeBSD. Some of these routines do not return anything (ie,
prototyped in C, their return type is 'void'). Does the compiler
expect that the asm routines that don't return anything will preserve
the value
hello,
given that the various printf's in systm.h are format-checked, it probably
makes sense to add this to sbuf_printf also. Could somebody please commit
this?
harti
Index: sbuf.h
===
RCS file: /usr/ncvs/src/sys/sys/sbuf.h,v
I'm currently trying to get pspell compiled into PHP, and make pspell use
the aspell library.
I have managed to get it to work on one box, using 4.3 release, without any
trouble, but I can't get it to repeat. When I load something that links to
the pspell module which plugs into aspell it
Carlo Dapor wrote:
I haven't received any CTMs since July 12th. Am I the only one ?
My guess is that the main distribution point is malfunctioning.
Hi, Yes, there is a central problem, being worked on,
Announcements on CTM issues are made to
[EMAIL PROTECTED]
All ctm recipients should
Hi all,
Is it possible to use libpcap with pthreads?
(I want to use just pcap_dispatch() function)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
- Original Message -
From: Kris Kennaway [EMAIL PROTECTED]
Newsgroups: lucky.freebsd.hackers
Sent: Friday, July 06, 2001 1:00 PM
Subject: Re: Status of dialog(1) and libdialog.
Just to throw some more fuel onto the fire, Thomas Dickey maintains
his own version of dialog, which is
Richard Hodges wrote:
Now TX buffers are a problem - I have to take what I get and just
deal with it. If both start address and length need to be aligned,
then I'm pretty much screwed - I have to copy...
No, exactly ythe opposite: the TX buffer is _not_ a problem. This
is because
(Choosing a random message to reply to ...)
While looking for commercial electronics CAD software for FreeBSD, I
came across Whitely Research Inc (http://www.srware.com/) which has
this note on their site:
http://www.srware.com/linux_numerics.txt
In light of this thread, I thought
done.
In message [EMAIL PROTECTED], Harti Brandt writes:
hello,
given that the various printf's in systm.h are format-checked, it probably
makes sense to add this to sbuf_printf also. Could somebody please commit
this?
harti
Index: sbuf.h
Stefan Hoffmeister wrote:
One obvious reason that the Linux approach is wrong is
that it ends up requiring the save and restore of FP
registers on context switches, which is overhead they
ate anyway, by doing TSS based context switching. The
amount of state with SSE is up to something like
Albert D. Cahalan wrote:
The defaults for the Linux emulator are different than
the defaults for Linux. Linux sets some stuff up wrong,
FreeBSD sets stuff up wrong. This is a choice between bad
and worse, since the CPU does not support what you want.
FreeBSD complies strictly with
John Baldwin wrote:
Actually, since the 486, it's been possible for us to turn on unaligned
access exceptions on the x86. We should probably consider doing this, to
ensure better performance, and to avoid the unnecessary bus overhead we
eat for unaligned access today... not to mention
Farooq Mela wrote:
Hi -hackers,
I'm developing some assembly routines that are called from a C library
under FreeBSD. Some of these routines do not return anything (ie,
prototyped in C, their return type is 'void'). Does the compiler
expect that the asm routines that don't return
Hi folks,
I'm busy developing a libdaemon implementation and have come unstuck on
a weird problem with functions using variable argument lists in FreeBSD
4.3-STABLE.
What I really want is a static inline void function declared in a header
file and included in various source files, looking
On Wed, Jul 18, 2001 at 07:34:08PM +0200, Sheldon Hearn wrote:
Hi folks,
I'm busy developing a libdaemon implementation and have come unstuck on
a weird problem with functions using variable argument lists in FreeBSD
4.3-STABLE.
What I really want is a static inline void function
Sheldon Hearn [EMAIL PROTECTED] writes:
static inline void
xdaemonwarn(char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
if (!daemon_quiet)
warn(fmt, ap);
^^
Shouldn't this be `vwarn'?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Wed, Jul 18, 2001 at 08:47:15PM +0300, Peter Pentchev wrote:
On Wed, Jul 18, 2001 at 07:34:08PM +0200, Sheldon Hearn wrote:
Hi folks,
I'm busy developing a libdaemon implementation and have come unstuck on
a weird problem with functions using variable argument lists in FreeBSD
* Sheldon Hearn [EMAIL PROTECTED] [010718 12:33] wrote:
Hi folks,
I'm busy developing a libdaemon implementation and have come unstuck on
a weird problem with functions using variable argument lists in FreeBSD
4.3-STABLE.
What I really want is a static inline void function declared in
Hi,
I've been looking for a way to get inter-process synchronization between multithreaded
processes. (I need synchronized access to
an area of shared memory between multiple instances of the same process)
Since I was using SysV shared memory, I had first thought of using SysV semaphores for
On 18-Jul-01 Terry Lambert wrote:
John Baldwin wrote:
It's the AC bit in eflags.
Note that this will not trap 64 bit unaligned accesses, only 32.
And only at pl 3...
Also note that this will play hell with some of the recent
copy avoidance changes made by Bill Paul to the ethernet
On 18-Jul-01 Terry Lambert wrote:
John Baldwin wrote:
Actually, since the 486, it's been possible for us to turn on unaligned
access exceptions on the x86. We should probably consider doing this, to
ensure better performance, and to avoid the unnecessary bus overhead we
eat for
Godday.
I'm quite new to KLD-programming and have a question:
Is it possible to read/write to files from a module without
too much effort, but still staying in kernelspace?
/suid-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the
Yes. But it is not easy. Look at code vfs_vnops.c. You can let a user
process open a file and then push the file descriptor into kernel via a
special system call. Search the mailing list archive and you will find
discussions on how to add a new system call.
-Zhihui
On Wed, 18 Jul 2001, suid
probably you should try :
#define LOCK_NB0x04 /* don't block when locking */
Also if you have shared memory, why not use
/* Get a spin lock, handle recursion inline (as the less common case) */
#define _getlock_spin_block(mtxp, tid, type) ({ \
From: Julian Elischer [EMAIL PROTECTED]
probably you should try :
#define LOCK_NB0x04 /* don't block when locking */
But I do want to block; I just don't want the whole process to block.
Also if you have shared memory, why not use
/* Get a spin lock, handle recursion
Alfred Perlstein [EMAIL PROTECTED] wrote:
The easiest way would be to have thttpd fork after listening a
pre-determined amount of servers, then they'll all compete calling
accept() to grab connections.
This is exactly what we did at Demon, which was for a long time
the largest thttpd
Howdy!
I built oidentd from ports on FreeBSD 4.3 R.
Every time oidentd gets querried it logs an error
Error: sysctlbyname: Operation not permitted.
I can trace this log message to the source file
freebsd4.c and the failure of the system call
if
Privjet Andrey,
On Wed, Jul 18, 2001 at 04:27:39PM +0400, Andrey Simonenko wrote:
Is it possible to use libpcap with pthreads?
(I want to use just pcap_dispatch() function)
I very much doubt so. It's not possible to use it in any kind of
multithreaded applications, even with select()
hi, there!
I have made second attempt to implement Arcnet support for FreeBSD
(the first was made about two years ago and nothing was ever committed)
Current bits can be fetched from http://iclub.nsu.ru/~fjoe/arcnet/
In order to use them you should copy dev/, net/ and modules/ to /sys and
apply
Hi,
I want to add support for reading crash dumps to libdevstat. This will
allow iostat and vmstat to fully work on crashdumps (with some
additional patches).
To give this a reasonable interface, a kvm handle needs to be passed
to getnumdevs, getgeneration, getversion, checkversion and getdevs.
I was reading the Makefile in /usr/src/release and wondering about the
for dir in bin sbin ; do \
ln -sf /stand $$dir; \
done
part in release.8 - it is my understanding that all that is under /stand is
linked to files in $$dir.
What does this accomplish?
To Unsubscribe: send mail to [EMAIL
In message p05101004b77bb785b82d@[128.113.24.47] Garance A Drosihn writes:
: At 12:54 AM -0600 7/18/01, Warner Losh wrote:
: Bruce A. Mah writes:
: : Unfortunately it's not guaranteed...a lot of new hardware has been
: : released since December 1998 (the date of 2.2.8-RELEASE). :-p
:
: Copy the
But what does this accomplish in the contect of release.8 if our purpose is
to 'copy' all the binaries to the new mfsroot?
On 18-Jul-01 Etienne de Bruin wrote:
I was reading the Makefile in /usr/src/release and wondering about the
for dir in bin sbin ; do \
ln -sf /stand $$dir; \
done
I'm currently trying to write a driver for the hardware monitoring
function of the Via 686a/b chipset, but I have a problem. I'm trying to
get my module (which right now does mostly nothing except probing and
attaching) to detect the ACPI function of this chip, but right now pciconf
-l shows it
Sheldon Hearn [EMAIL PROTECTED] writes:
static inline void
xdaemonwarn(char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
if (!daemon_quiet)
warn(fmt, ap);
va_end(ap);
return;
}
GCC gives syntax error before 'void'. Fair enough.
As
Sheldon Hearn [EMAIL PROTECTED] writes:
static inline void
xdaemonwarn(char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
if (!daemon_quiet)
warn(fmt, ap);
va_end(ap);
return;
}
GCC gives syntax error before 'void'. Fair enough.
$ cat
Terry Lambert wrote:
cc -S is your friend.
Right, well that can certainly help, but what gcc generates can be
dependant on calling convention, optimization setting, c c, and
though the code generated in one particular scenario may not be an
absolute indicator of it's behavior. In other words,
39 matches
Mail list logo
