howto make 8.0-RELEASE-i386-disc1.iso

hi,everyone. each time I use disk1 to install my FreeBSD system.Now I want to make my own FreeBSD distro.My question is how to make disk1? thanks. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freeb

Re: leak of the vnodes

You can either increase kern.maxvnodes, the default value is very conservative on amd64, where a lot of KVA is available. On the other hand, increase of the value on i386 could easily cause KVA exhaustion. The increase helps, the system become responsive. In fact I previously suspected schedule

Re: write(2) size is limited by INT_MAX on amd64 -- is it a bug or a feature?

On Fri, Apr 02, 2010 at 11:53:09AM -0700, Artem Belevich wrote: > Hi, > > I've ran into a problem on 8-stable/amd64 today. Basically any attempt > to pass 2GB chunk of data to write(2) returns EINVAL. It looks like > we're limiting amount of data to be written to INT_MAX which looks > rather rest

Re: leak of the vnodes

On Fri, Apr 02, 2010 at 07:45:03PM +0200, Petr Salinger wrote: > Hi, > > I have the same problem as in > http://lists.freebsd.org/pipermail/freebsd-hackers/2009-August/029227.html > > During "make check" of gcc-4.3 the vfs.numvnodes goes up, > after reaching default limit 10 the machine is st

write(2) size is limited by INT_MAX on amd64 -- is it a bug or a feature?

Hi, I've ran into a problem on 8-stable/amd64 today. Basically any attempt to pass 2GB chunk of data to write(2) returns EINVAL. It looks like we're limiting amount of data to be written to INT_MAX which looks rather restrictive on LP64 platforms. NetBSD/OpenBSD do use SSIZE_MAX which does seem t

leak of the vnodes

Hi, I have the same problem as in http://lists.freebsd.org/pipermail/freebsd-hackers/2009-August/029227.html During "make check" of gcc-4.3 the vfs.numvnodes goes up, after reaching default limit 10 the machine is stuck. kern.maxvnodes: 10 kern.sigqueue.alloc_fail: 0 kern.sigqueue.overf

Re: Compiling kernel with gcc43 [SOLVED] -ADDENDUM

Well, to tell the truth I wasn't that thrilled with the results. I didn't [snip] -- Compiling vbox/vbox-devel with gcc43 1) /usr/include/cam/cam.h needed #include for FILE define, complained by: [snip] and /etc/src

Re: Compiling kernel with gcc43 [SOLVED]

On Thursday 01 April 2010 16:53:36 Pegasus Mc Cleaft wrote: > On Thursday 01 April 2010 15:27:41 Oliver Fromme wrote: > > Mario Lobo wrote: > > > [...] > > > It's compiling right now. > > > > > > I'll post my findings and impressions on results and performance right > > > after the next reboo