Re: Non-standard FFS parameters

1999-11-22 Thread Matthew Dillon
:What's the recommended way to reduce the number of cylinder groups a bit? :-c's maximum limit is affected by combinations of -b and -i, possibly some :others. PHK was talking about new, more sensible values for filesystem :parameters, but I don't know what happened. I just think it's a bit sill

Re: Non-standard FFS parameters

1999-11-22 Thread Joe Greco
> 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... ;-) > > : > > :Andrzej Bialecki > > > > No, I didn't say that

Re: ip checksum

1999-11-22 Thread Julian Elischer
How many bytes have you changed? is it possible that some of the values have already been ntohs()'d or something similar? rather than recalculate the whole packet, just update the exisitng value. there is an rfc for this but it took me a while to get the code right in C on a 386. The trick is

Re: ip checksum

1999-11-22 Thread Bosko Milekic
On Tue, 23 Nov 1999, Parthasarathy M. Aji wrote: !>Hey, !> !>I am trying to recompute the checksum of an IP packet. I use !>netinet/in_chksum.c to do this. The values returned are not correct. I've !>reset the ip_sum field to 0 before doing the sum. Is there something !>missing? !> !>thanks !>

ip checksum

1999-11-22 Thread Parthasarathy M. Aji
Hey, I am trying to recompute the checksum of an IP packet. I use netinet/in_chksum.c to do this. The values returned are not correct. I've reset the ip_sum field to 0 before doing the sum. Is there something missing? thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: stat(2) weirdness

1999-11-22 Thread Peter Wemm
Bjoern Fischer wrote: > Hello, > > recently while debugging a problem in wwwoffle-2.5b I realized, > that stat(2) behaves at least extremely strange on 3.3-STABLE: > > This small example... > > #include > #include > #include > > int main(int argc, char *argv[]) { > > char

stat(2) weirdness

1999-11-22 Thread Bjoern Fischer
Hello, recently while debugging a problem in wwwoffle-2.5b I realized, that stat(2) behaves at least extremely strange on 3.3-STABLE: This small example... #include #include #include int main(int argc, char *argv[]) { char*fname = argv[0]; struct stat sb; int

Re: wacky rpc.lockd idea...

1999-11-22 Thread David E. Cross
> That's really up to the server lockd/nfsd implementation, but considering > that more likely than not the server's lockd will have an open reference > to the file until the lock is gone the answer is probably yes. Hmm... I wold think even without having the file "open" a lock would be enough. S

Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ?

1999-11-22 Thread Sergey Babkin
Eduardo Viruena Silva wrote: > > O! wise FreeBSD gurus! > I ask for your advice... > > I have a FreeBSD 3.3 system in a Pentium computer and an old 486 > computer that I want to make a diskless system. > > I found that in directory: /usr/src/sys/i386/boot/netboot > there is a way of building

Re: Threads and my new job.

1999-11-22 Thread Matthew Dillon
:... :*) Make a real libpthread, rather than relying on the -pthread linker : magic. This is high on Daniel Eischen's wish list, so maybe he already : has something in the works. =) : :If you know of other outstanding issues that have a prayer of being :addressed before 4.0 ships, please spea

Threads and my new job.

1999-11-22 Thread Jason Evans
Walnut Creek has hired me as a full time employee to work primarily on improving and expanding FreeBSD's threads support. This is very exciting to me, and I hope my work will be of benefit the FreeBSD community. There is a lot of work to be done in order to make FreeBSD's threads support truly

Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ?

1999-11-22 Thread Peter Wemm
Mark Newton wrote: > Eduardo Viruena Silva wrote: > > > FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. > > You should be able to build an a.out kernel by putting > >makeoptions KERNFORMAT=aout > > into your kernel config file. Also, the plan is that it s

Re: PPPoE offer.

1999-11-22 Thread Brian Somers
[.] > We also have patches in the works to allow full kernel bypass of > the ppp daemon in the common case, resulting in Mucho performance > increase. > > with the version we have now, a 100KB/sec ppp session took 6% of a > P6-200 [.] CCP will kill performance. Without it however, I've

Re: PPPoE offer.

1999-11-22 Thread David Gilbert
> "Julian" == Julian Elischer <[EMAIL PROTECTED]> writes: Julian> (the other end was a 486DX50 :-) with enough RAM we could Julian> probably serve 10K sessions, though that would require 10K ppp Julian> daemons until we got the kernel bypass working. in either Julian> case it would presently

Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ?

1999-11-22 Thread Mark Newton
Eduardo Viruena Silva wrote: > FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. You should be able to build an a.out kernel by putting makeoptions KERNFORMAT=aout into your kernel config file. - mark Mark Newton Email

FreeBSD 3.3, DISKLESS, kernel format must be AOUT ?

1999-11-22 Thread Eduardo Viruena Silva
O! wise FreeBSD gurus! I ask for your advice... I have a FreeBSD 3.3 system in a Pentium computer and an old 486 computer that I want to make a diskless system. I found that in directory: /usr/src/sys/i386/boot/netboot there is a way of building "nb3c509.com" program. This program is

Re: PPPoE offer.

1999-11-22 Thread Julian Elischer
David Gilbert wrote: > > > "Josef" == Josef Karthauser <[EMAIL PROTECTED]> writes: > > Josef> As far as I'm aware it _does_ work - in the form of user-ppp > Josef> (/usr/sbin/ppp), maintained by Brian. Why do you need to use > Josef> kernel ppp - it's a mess :) > > In some discussions with

Re: A file with holes - a bug?

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Zhihui Zhang wrote: > > > > > Please take a look at the following piece of code that creates a large > > hole in a file named hole.dat. It tries to write 0x30-0x39 both at the > > front and the tail of that file, the

Re: wacky rpc.lockd idea...

1999-11-22 Thread Alfred Perlstein
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 o

Re: A file with holes - a bug?

1999-11-22 Thread Brian Fundakowski Feldman
On Mon, 22 Nov 1999, Zhihui Zhang wrote: > > Please take a look at the following piece of code that creates a large > hole in a file named hole.dat. It tries to write 0x30-0x39 both at the > front and the tail of that file, the hole is therefore in the middle. > > main() > { > char c; >

wacky rpc.lockd idea...

1999-11-22 Thread David E. Cross
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 a second, then removing the binary on the first ma

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

1999-11-22 Thread David E. Cross
> Linux may have one, a temporary GPL'd port would be interesting perhaps. "There is nothing as permanent as a temporary decision." No thanks :) -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrat

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

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, David E. Cross wrote: > Does NetBSD have a working rpc.lockd... that would make this much easier. at a glance at http://cvsweb.netbsd.org/... no. Linux may have one, a temporary GPL'd port would be interesting perhaps. -Alfred To Unsubscribe: send mail to [EMAIL PROTEC

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

1999-11-22 Thread David E. Cross
Does NetBSD have a working rpc.lockd... that would make this much easier. -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer

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

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, Ronald G. Minnich wrote: > Actually I wrote a system call for opening a file given a file handle for > freebsd a while back (oh, gee, has it really been 5 years ...), as part of > mnfs i'll try to find it. You don't need to map it to a filename to > make it go. i forgot

Is there any xDSL driver been supported for FreeBSD?

1999-11-22 Thread Robert Butler
or other BSD platforms? Any pointers are excellent. ps. I understand that most of the DSL modems/routers using ethernet or ATM as the interface talking to the host. However, I'm asking about the internal DSL modem that need DSL driver. Robert ___

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

1999-11-22 Thread Ronald G. Minnich
Actually I wrote a system call for opening a file given a file handle for freebsd a while back (oh, gee, has it really been 5 years ...), as part of mnfs i'll try to find it. You don't need to map it to a filename to make it go. ron To Unsubscribe: send mail to [EMAIL PROTECTED] with "un

Re: A file with holes - a bug?

1999-11-22 Thread Brooks Davis
On Mon, Nov 22, 1999 at 01:48:38PM -0500, Zhihui Zhang wrote: > > By the way, I also find out if you copy a file with holes into another > file, the holes in the first file will be replaced with 0s in the second > file, taking more disk space (check with du). Is there a better solution > for this

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

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, David E. Cross wrote: > 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

Re: A file with holes - a bug?

1999-11-22 Thread Chris Costello
On Mon, Nov 22, 1999, Zhihui Zhang wrote: > lseek(fileno(fp), 3 * 8192, SEEK_CUR); > If I remove the fflush(fp), then the characters 0x30-0x39 will be all > written at the end of the file (use hexdump to find out), not as expected > (one at the beginning and the other at the end). It seem

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

1999-11-22 Thread David E. Cross
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 downloaded the RFC for

Re: A file with holes - a bug?

1999-11-22 Thread Ronald G. Minnich
On Mon, 22 Nov 1999, Zhihui Zhang wrote: > lseek(fileno(fp), 3 * 8192, SEEK_CUR); don't mix things that use file descriptors with stdio. End of problem. ron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

A file with holes - a bug?

1999-11-22 Thread Zhihui Zhang
Please take a look at the following piece of code that creates a large hole in a file named hole.dat. It tries to write 0x30-0x39 both at the front and the tail of that file, the hole is therefore in the middle. main() { char c; FILE * fp; fp = fopen("hole.dat", "w");

Re: vmpfw in pine via NFS

1999-11-22 Thread Robert Watson
On Mon, 22 Nov 1999, Alan Judge wrote: > Daniel> /me shivers at the thought of my (easily) 500+ new messages a day > Daniel> and hundreds of thousands of messages being stored one file for each > Daniel> message... > > Works OK for us (and a number of even larger ISPs using Maildirs). > Though w

Re: PCI DMA lockups in 3.2 (3.3 maybe?)

1999-11-22 Thread Warner Losh
In message <[EMAIL PROTECTED]> Ben Rosengart writes: : In my tests, I've found that FreeBSD is getting faster with successive : releases -- I think because the increased weight of the extra disks helps : overcome wind resistance. That's just due to the beefier system requirements. of course the

Re: Cardbus and FXP

1999-11-22 Thread Warner Losh
In message <[EMAIL PROTECTED]> Jamie Bowden writes: : : I asked on -mobile, but didn't get an answer, so now I'm asking here. I : Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus : 82559 based ethercard for this machine. What I want to know is, once : cardbus is rolle

Re: PCI DMA lockups in 3.2 (3.3 maybe?)

1999-11-22 Thread Ben Rosengart
On Sun, 21 Nov 1999, Jordan K. Hubbard wrote: > Bringing something into question without detail is useless. If I > seriously questioned your sexual orientation, for example, you'd have > every right to ask me just what the hell I was basing such a question > on and why I was uncertain about it i

Re: vmpfw in pine via NFS

1999-11-22 Thread Alan Judge
Daniel> /me shivers at the thought of my (easily) 500+ new messages a day Daniel> and hundreds of thousands of messages being stored one file for each Daniel> message... Works OK for us (and a number of even larger ISPs using Maildirs). Though we use NetApps for the file storage and they have a m

ANNOUNCE: SPY-0.1 - syscalls monitor

1999-11-22 Thread Andrzej Bialecki
Hi, SPY allows you to monitor and/or selectively block syscalls on your system. It could be used either as a safety monitoring device, policy enforcement, or debugging tool. You can download the sources (NOTE: -current only) from: http://www.freebsd.org/~abial/spy-0.1.tgz Excerpt of REA

Re: Kernel building and more

1999-11-22 Thread Jeroen Ruigrok van der Werven
-On [19991122 15:40], Milos Puzovic ([EMAIL PROTECTED]) wrote: >Hi to all! I am new to FreeBSD. I was on Linux, and with great help of >my friend Alex I got on FreeBSD. I have several questions: 1) how can I >build my kernel that he can recognize my modem...Kernel show that hi is >

Kernel building and more

1999-11-22 Thread Milos Puzovic
Hi to all! I am new to FreeBSD. I was on Linux, and with great help of my friend Alex I got on FreeBSD. I have several questions: 1) how can I build my kernel that he can recognize my modem...Kernel show that hi is testing COM3 but he cannot find there...2) my sound card is PnP and kernel found he

Re: Cardbus and FXP

1999-11-22 Thread Jeroen Ruigrok van der Werven
-On [19991122 14:15], Jamie Bowden ([EMAIL PROTECTED]) wrote: > >I asked on -mobile, but didn't get an answer, so now I'm asking here. I >Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus >82559 based ethercard for this machine. What I want to kno

Cardbus and FXP

1999-11-22 Thread Jamie Bowden
I asked on -mobile, but didn't get an answer, so now I'm asking here. I Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus 82559 based ethercard for this machine. What I want to know is, once cardbus is rolled into 3.x, or when 4.x is fianlly release, will the FXP driver