sorry about the vinum comment.

I would like to apologise for the missleading comment I made about vinum and using 4 18 gig drives with vinum. In teaching myself the software I have been using 4 18 gig drives in serveral configurations including striping, striping/mirroring and raid 5. in each situation I had to wait a long tim

more softpower/apm..

Hi Does anyone know if its possible for FreeBSD to execute a halt from the powerswitch? >From reading the apmd doco, this is what apmd is suppose to do, handle events from the APM bios and execute according to apmd.conf If an ATX powersupply/motherboard is setup to suspend on power button, (i.e

gdb and ELF shared libraries

It appears to me that the gdb 4.18 port on FreeBSD 3.3 doesn't provide support for ELF shared libraries. Am I correct about that, or did I just snag myself on some obscure gdb bug that was masquerading as ELF shared library non-support? Anyway, assuming that my supposition is correct, and that

Re: fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in3.X !!!!

Great Thanx... > i'm not sure why the change happened, but here's a fix: > > --- sigio.old.c Tue Nov 23 19:18:01 1999 > +++ sigio.c Tue Nov 23 19:19:21 1999 > @@ -36,7 +36,14 @@ > int > main(int argc,char **argv) > { > + int arg; > + > + arg = getpid();

Re: fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in3.X !!!!

On Wed, 24 Nov 1999, Seva Semenov wrote: > Why my little proggy can't get SIGIO in FreeBSD 3.3-RELEASE, > when i type my keyboard? > > In 2.2.6-RELEASE it works right. > > > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include

fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in 3.X !!!!

Why my little proggy can't get SIGIO in FreeBSD 3.3-RELEASE, when i type my keyboard? In 2.2.6-RELEASE it works right. #include #include #include #include #include #include #include #include #include #include void rkbd(int sig) { int i,j; u_char b[1024],*c;

Re: arpresolve: can't allocate llinfo for 127.0.0.1rt [PLAIN TEXT]

See PR bin/12136. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

arpresolve: can't allocate llinfo for 127.0.0.1rt [PLAIN TEXT]

Ok... my apologies to all those whose email clients are not capable of parsing html emails... my settings indicated that my email was to be sent plain text... this was apparently not the case as someone was kind enough to point out... thanks! Aaron Sonntag -Original Message- From: [EM

Re: ip checksum

Hey, I am sort of confused with the parameters for IPsumReplaceShort function, I understand that I will pass the &ip-ip_sum for the cksump parameter. but I am not able to understand wht oldvap & newvalp stand for.. Xavier. On Mon, 22 Nov 1999, Julian Elischer wrote: > How many bytes have y

Re: ip checksum

On Tue, 23 Nov 1999, Clinton Xavier Berni wrote: > Hey, > I am sort of confused with the parameters for IPsumReplaceShort function, > I understand that I will pass the &ip-ip_sum for the cksump parameter. > > but I am not able to understand wht oldvap & newvalp stand for.. cksump points to

NFS hangs/locks CPU

Hi, I'm running FreeBSD 2.2.8. We have used 2.2.8 to build a telecom application and have had great success deploying other telecom applications on 2.2.8 until now. We are using NFS to distribute binaries and config files to others machines so that we can achieve availability. Here's our proble

RE: H323/Ldap support in natd/libalias

You might take a look at http://www.willamowius.de/openh323gk.html I haven't looked at it in a couple of months but they are basically working on a H323 stack and proxy. It's not exactly what your talking about but close enough that it might be a good starting place. Brian Haskin [EMAIL PROTECTED

H323/Ldap support in natd/libalias

Hello, i am trying to add an H323/LDAP support to NATD in FreeBSD to enable full video/audio functionnalities of video-conference clients in a private network. i posted some messages in newsgroups, but the only answer i got was to buy a commercial product like "phonepatch" (which does not work o

Re: wacky rpc.lockd idea...

On Tue, 23 Nov 1999, Ronald G. Minnich wrote: :On Mon, 22 Nov 1999, David E. Cross wrote: :> I've noticed about 99% of the panics on our machines are the result of NFS, :> more often than not it is the result of a backing store file being blown :> away underneath the client. ie. person editing

Re: Ok, that's it, enough is enough! (rpc.lockd)

> : Ok... I have *had* it with the meta, but not really, lockd. Are there any > : kernel issues with correctly implimenting rpc.lockd?How can I take a > : filehandle and map it into a filename, with path, so I may open it and lock > : it on the server? Are there any protocol specs? I downl

Re: Ok, that's it, enough is enough! (rpc.lockd)

In message <[EMAIL PROTECTED]> "David E. Cross" writes: : Ok... I have *had* it with the meta, but not really, lockd. Are there any : kernel issues with correctly implimenting rpc.lockd?How can I take a : filehandle and map it into a filename, with path, so I may open it and lock : it on the

arpresolve: can't allocate llinfo for 127.0.0.1rt

This one fell through the cracks on the questions list… probably cause its not a simple question… or at least I would like to think so ;-) It is regarding an error occurring in the route table on various machines under various configurations.  The one similarity is dhclient. Read below…

Re: wacky rpc.lockd idea...

On Mon, 22 Nov 1999, David E. Cross wrote: > I've noticed about 99% of the panics on our machines are the result of NFS, > more often than not it is the result of a backing store file being blown > away underneath the client. ie. person editing a file on one machine, > compiling and running on

Re: whats up with vinum?

On Sunday, 21 November 1999 at 4:40:54 -1000, Richard Puga wrote: > I am fooling around with vinum which I have set up in a raid 5 > configuration under FreeBSD 3.3-RELEASE. > > The trouble is that my machine keeps locking up under heavy use. If I > try and "make world" it dies about 15-60 second

Re: Non-standard FFS parameters

On Tue, 23 Nov 1999, Joe Greco wrote: > > On Fri, 8 Oct 1999, Matthew Dillon wrote: > > > > > :> > > > :> Adjusting the bytes-per-inode (-i) specification in newfs should not > > > :> pose a problem. > > > : > > > :IOW now you say it's ok to use very high values of -i... ;-) > > > : >

VB

Title: VideBula-991118 VideBula   "Não importa o que tiraram de você, o que importa é o que você vai fazer com o que sobrou."   "Você não pode estar só se gostar da pessoa com quem fica quando esta sozinho."  RECEBER NÃORECEBER PUBLICAR CRÍTICAS, DÚVIDAS & SUGESTÕES

Serial console oddity

So, I've been doing serial consoles for a while and every so often, the following pops up. Seems to happen on SMP machines. Don't recall if it happens on non-SMP machines. This has happened for a _very_long_time_ (like since pre-3.0). BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D:

Help: SoundBlaster PCI 16, 64, 128, 64V, 128V revisions

Hi, I'm trying to list the full range of SoundBlaster PCI models. >From my research I have found the following Creative Labs models. CT4700 SB PCI 128 - (12 months ago) ES1370. 2 line outs for 4 speakers. Retail Box CT SB PCI 64V - unknown chip. 64 Value edition. 1 line out. OEM Market.