Date: Thu, 1 Jul 1999 13:59:32 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: hackers@freebsd.org Subject: npx0 to set maxmem broken in -current? Message-ID: <14203.43667.496647.806250@grasshopper.cs.duke.edu>
next in thread | raw e-mail | index | archive | help
I have a user with a need to run a machine in varying memory configurations. The machine has 512MB & she needs to artificially constrain memory to multiples of 32MB from 32MB to 512MB. (32MB, 64MB, 96MB, 128MB ...) I was planning on having her edit /kernel.config & change the value of iosize npx0 and have the bootloader do a load -t userconfig_script /kernel.config at boottime. However, this feature appears to be broken in current. The resource_int_value() call which grabs msize is returning ENOENT & we're seeing the full 512MB of ram. Is there any way around this, short of building her 16 different kernels? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14203.43667.496647.806250>