hi, there!
On Sun, 4 Jun 2000, James Housley wrote:
> I would like to use tcp_wrappers (libwrap) in a program. I din't see
> any examples or a reference to a web site. I have read the man page.
> Is there a good example of a program in the FreeBSD 4 tree that is not
> inetd spawned and uses l
On Sun, 04 Jun 2000 15:42:28 -0700, W Gerald Hicks <[EMAIL PROTECTED]> wrote:
> Arun Sharma wrote:
>
> > I don't know if the gas support is public, but you can certainly get the
> > Intel assembler for IA-64, which has been open sourced under the BSD
> > license from developer.intel.com. It may n
On Sun, Jun 04, 2000 at 07:34:54PM -0400, James Housley wrote:
> I would like to use tcp_wrappers (libwrap) in a program. I din't see
> any examples or a reference to a web site. I have read the man page.
> Is there a good example of a program in the FreeBSD 4 tree that is not
> inetd spawned a
Look through /modules...
Daniel C. Sobral had the audacity to say:
>
> M... ethernet drivers are already auto-loaded, fs modules are
> already auto-loaded... what am I missing?
>
> --
> Daniel C. Sobral (8-DCS)
>
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTEC
hi,
I sent this question to -questions but got no response. Perhaps someone
on -hackers can help... I'm being puzzled by how to use FIFOs properly.
I've written a small test program,
#include
#include
#include
#include
#include
#include
#define _PATH_FIFO "fifo"
int
main(void) {
On Thu, Jun 01, 2000 at 07:00:08PM -0700, Jordan K. Hubbard wrote:
> Just following up on this - are there any plans to merge this work
> back into the mainstream so that we can generate "localized" installation
> floppies for the Japanese community in future releases? Thanks!
>
> (Yes, I'm real
"Andrey A. Chernov" wrote:
>
> On Mon, Jun 05, 2000 at 08:42:47AM +0900, Daniel C. Sobral wrote:
> > Huh? I'm obviously missing something here... Why would the branches be
> > damaged by this?
>
> Because they forked. It cause merge troubles on the next import into the
> vendor branch forever.
David Malone wrote:
>
> On Sun, Jun 04, 2000 at 07:34:54PM -0400, James Housley wrote:
> > I would like to use tcp_wrappers (libwrap) in a program. I din't see
> > any examples or a reference to a web site. I have read the man page.
> > Is there a good example of a program in the FreeBSD 4 tree
Coleman Kane wrote:
>
> Well, they are already moving in that direction with the newbus driver
> interface. It really simplifies converting your driver to a kld if
> you write it properly. Now a perfect addition would be a daemon or
> something that takes care of loading/unloading all of them so
On Mon, Jun 05, 2000 at 08:42:47AM +0900, Daniel C. Sobral wrote:
> Huh? I'm obviously missing something here... Why would the branches be
> damaged by this?
Because they forked. It cause merge troubles on the next import into the
vendor branch forever.
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
"Andrey A. Chernov" wrote:
>
> On Sun, Jun 04, 2000 at 11:36:47PM +0900, Daniel C. Sobral wrote:
> > You revert to the original by applying the reverse patch of your changes
> > and committing that. This can be easily done with cvs. And then you
>
> Are you joking? CVS branches will be damaged b
On Sun, Jun 04, 2000 at 02:03:56PM -0400, Bob K wrote:
> If I understand what he's proposing correctly, he wants to develop a
> system in which all of the device drivers are loaded in the same way KLD's
> are.
>
> (I'm not a programmer, so I'd be unable to help)
Uhm. 90% of the klds _are_ devic
>
> >
> > I believe HP provides a IA64 emultor which runs on Linux/Windows? I recall
> > stumbling into when looking at the IA64 compiler that SGI recently
> > releases.
>
> It was mentioned on SGI's pages, but I couldn't find it anywhere on HP's
> site (the link didn't work). If you have
I would like to use tcp_wrappers (libwrap) in a program. I din't see
any examples or a reference to a web site. I have read the man page.
Is there a good example of a program in the FreeBSD 4 tree that is not
inetd spawned and uses libwrap?
Thanks,
Jim
--
Unix is very user-friendly. It's ju
> > Would the person or person(s) interested in developing a kerneld-like, dynamic
> > module (un)loader for FreeBSD please email me. I am really interested in this.
> > It would be very advantageous to begin to move kld module use into the
> > mainstream for all components. I'd like to do what I
>
> I believe HP provides a IA64 emultor which runs on Linux/Windows? I recall
> stumbling into when looking at the IA64 compiler that SGI recently
> releases.
It was mentioned on SGI's pages, but I couldn't find it anywhere on HP's
site (the link didn't work). If you have a pointer to thi
Arun Sharma wrote:
> I don't know if the gas support is public, but you can certainly get the
> Intel assembler for IA-64, which has been open sourced under the BSD
> license from developer.intel.com. It may not be of much practical use,
> but might help in understanding the architecture (which r
On Sat, Jun 03, 2000 at 07:10:56PM +0200, Gerald Pfeifer wrote:
> However you do it, please fix this ASAP, and be it by reverting the
Ask Peter to commit this patch at least...
--- include/curses.h.in.bak Wed May 24 14:44:45 2000
+++ include/curses.h.in Mon Jun 5 02:28:33 2000
@@ -1313,8 +1
Well, they are already moving in that direction with the newbus driver
interface. It really simplifies converting your driver to a kld if
you write it properly. Now a perfect addition would be a daemon or
something that takes care of loading/unloading all of them so that the
user doesn't have to f
Well, they did away with kerneld, but not the concept. Most of the
distributions have moved onto a more sophisticated utility that does the
job.
Alfred Perlstein had the audacity to say:
> I thought Linux did away with thier kerneld concept. Afaik we can
> currently load a kld from within kernel
On Sun, Jun 04, 2000 at 11:36:47PM +0900, Daniel C. Sobral wrote:
> You revert to the original by applying the reverse patch of your changes
> and committing that. This can be easily done with cvs. And then you
Are you joking? CVS branches will be damaged by this again.
> changes in the past fir
On Sun, Jun 04, 2000 at 07:43:23PM +0300, Anatoly Vorobey wrote:
> Do you mean just "you" or "anyone with -current"? I thought our binutils
> (e.g. gas) had no IA-64 support. Has that changed?
I mean you, Anatoly. I really don't have any clue how developed the
IA-64 support is; I'm just assuming
In muc.lists.freebsd.hackers, you wrote:
> On Sun, Jun 04, 2000 at 11:12:22AM -0400, Will Andrews wrote:
> > On Sun, Jun 04, 2000 at 01:18:39AM +0800, Belldandy wrote:
> > > Is there any effort(or at least, any thought) on making an
> > > IA-64 port of FreeBSD? It seems Intel is trying to push I
* Coleman Kane <[EMAIL PROTECTED]> [000604 10:51] wrote:
> Would the person or person(s) interested in developing a kerneld-like, dynamic
> module (un)loader for FreeBSD please email me. I am really interested in this.
> It would be very advantageous to begin to move kld module use into the
> main
Would the person or person(s) interested in developing a kerneld-like, dynamic
module (un)loader for FreeBSD please email me. I am really interested in this.
It would be very advantageous to begin to move kld module use into the
mainstream for all components. I'd like to do what I can to help with
On Sun, Jun 04, 2000 at 11:12:22AM -0400, Will Andrews wrote:
> On Sun, Jun 04, 2000 at 01:18:39AM +0800, Belldandy wrote:
> > Is there any effort(or at least, any thought) on making an
> > IA-64 port of FreeBSD? It seems Intel is trying to push IA-64
> > to be 'the platform' for servers and wor
"Andrey A. Chernov" wrote:
>
> > However you do it, please fix this ASAP, and be it by reverting the
> > original, broken patch!
>
> I wish but I can't. If I'll touch those misterious CVS branches structure
> again, everyone shoot at me as in previous time. I think it is enough for
> me. Nowd
On Sun, Jun 04, 2000 at 01:18:39AM +0800, Belldandy wrote:
> Is there any effort(or at least, any thought) on making an
> IA-64 port of FreeBSD? It seems Intel is trying to push IA-64
> to be 'the platform' for servers and workstations, and I think
> FreeBSD definitely can't be left out
Hi,
>
> On Sat, 3 Jun 2000, Jordan K. Hubbard wrote:
>
> > Intel has furnished us with IA-64 hardware and a porting effort is
> > already underway. Contact [EMAIL PROTECTED] if you would like to
> > help out in some way with the process.
>
> What can those of us just out here do?
>
>
I believe
I have made available the following `sym' driver patch for testing:
http://people.freebsd.org/~groudier/sym-1.6.0-20000604.diffs
This patch is against driver version in -current. Changes are pretty
trivial and mostly nil-potent for ia32, but it seemed to me they may
need some tes
> On Sat, 3 Jun 2000, Jordan K. Hubbard wrote:
>
> > Intel has furnished us with IA-64 hardware and a porting effort is
> > already underway. Contact [EMAIL PROTECTED] if you would like to
> > help out in some way with the process.
>
> What can those of us just out here do?
That depends on wha
31 matches
Mail list logo