On Wednesday 13 June 2007 06:32:42 pm Jin Guojun wrote:
Umm, the amount of physical memory has no bearing on how the virtual
address space for userland is laid out. Do you know what virtual memory
is and how it works? Your first e-mail seems to contradict this paragraph
as in your first
On Tuesday 12 June 2007 09:20:02 pm Jin Guojun wrote:
John Baldwin wrote:
On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote:
I believe that this is a memory sub-system bug somewhere because
anything equal to or below 1G
options MAXDSIZ=(1024*1024*1024)
will work
John Baldwin wrote:
On Tuesday 12 June 2007 09:20:02 pm Jin Guojun wrote:
John Baldwin wrote:
On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote:
I believe that this is a memory sub-system bug somewhere because
anything equal to or below 1G
options
On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote:
I believe that this is a memory sub-system bug somewhere because
anything equal to or below 1G
options MAXDSIZ=(1024*1024*1024)
will work regardless how many memory is installed in the system.
I doubt this could be a
John Baldwin wrote:
On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote:
I believe that this is a memory sub-system bug somewhere because
anything equal to or below 1G
options MAXDSIZ=(1024*1024*1024)
will work regardless how many memory is installed in the system.
I doubt
I have multiple FreeBSD 6.2 machines with different hardware, but one of
them encountered
this strange error when running program wine.
I could not figure out what causes such error since /libexec/ld-elf.so.1
absolutely exists, otherwise
no program will run.
It does not matter if the wine is
Finally find cause but no idea why -- in kernel configuration, following
line causes the problem:
options MAXDSIZ=(2097152U*1024)
Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for
some program?
Jin Guojun [VFFS] wrote:
I have multiple FreeBSD 6.2 machines with
I believe that this is a memory sub-system bug somewhere because
anything equal to or below 1G
options MAXDSIZ=(1024*1024*1024)
will work regardless how many memory is installed in the system.
I doubt this could be a hardware related issue although is memory size
related.
Finally find