Re: loader.conf options
On Sun, 17 Jul 2011, wayne mitchell wrote: am trying to configure my new system (FreeBSD 8.1-RELEASE GENERIC amd64 - on an intel core 2 duo) I'd suggest upgrading to 8.2-RELEASE or 8-STABLE. and find all possible settings to tweak i can tell from documentation that there are many options possible with /boot/loader.conf It's often counterproductive to change settings, but you'll find a much longer list in /boot/defaults/loader.conf. Do not change them there, just override by setting them in /boot/loader.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader.conf mfs statements
On Thu, Mar 04, 2010 at 09:48:27PM +0800, Fbsd1 wrote: Tyring to understand what mfsbsd is doing. In its loader.conf file i see these statements geom_uzip_load=YES mfs_load=YES mfs_type=mfs_root mfs_name-/mfsroot tmpfs_laod=YES vfs.root.mountfrom=ufs:/dev/mdo Where do I find documentation on the meaning of these statements? loader.conf(5) and /boot/defaults/loader.conf -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader.conf mfs statements
Daniel Bye wrote: On Thu, Mar 04, 2010 at 09:48:27PM +0800, Fbsd1 wrote: Tyring to understand what mfsbsd is doing. In its loader.conf file i see these statements geom_uzip_load=YES mfs_load=YES mfs_type=mfs_root mfs_name-/mfsroot tmpfs_laod=YES vfs.root.mountfrom=ufs:/dev/mdo Where do I find documentation on the meaning of these statements? loader.conf(5) and /boot/defaults/loader.conf All ready checked those sources before posting with no joy. IE: your are wrong. Those sources have no info on the mfs* statements. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf
gahn wrote: Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G# Limit physical memory. See loader(8) Could I remove the # and change that to 2G? Yes, but, would it make a difference? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. It is changeable before the system boots (during the 'loader' stage), but not changeable later. The question is, what's it currently set to? The comment means that the line in question *isn't* a physical memory limit ... what's the current setting of hw.physmem, and why would you *want* to limit it? On my systems, both 7x and 6x, hw.physmem is something like 4G by default---despite the fact I've nothing like that amount of RAM onboard. Any guru here give me some enlightenment? IANAE, but am willing to accept correction. Kevin Kinsey -- When a person goes on a diet, the first thing he loses is his temper. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf
On Fri, Apr 10, 2009 at 5:32 PM, gahn ipfr...@yahoo.com wrote: Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G # Limit physical memory. See loader(8) Could I remove the # and change that to 2G? Yes, but if your purpose is to use all the available memory, you don't need to do anything. Because it is commented, that line doesn't have effect and the system will use all the available memory. What does sysctl hw.physmem return? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. After booting, it is. Any guru here give me some enlightenment? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf
2009/4/10 Fernando Apesteguía fernando.apesteg...@gmail.com: On Fri, Apr 10, 2009 at 5:32 PM, gahn ipfr...@yahoo.com wrote: Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G # Limit physical memory. See loader(8) Could I remove the # and change that to 2G? Yes, but if your purpose is to use all the available memory, you don't need to do anything. Because it is commented, that line doesn't have effect and the system will use all the available memory. What does sysctl hw.physmem return? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. After booting, it is. I meant, it is readonly :) Any guru here give me some enlightenment? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf
gahn wrote: Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G# Limit physical memory. See loader(8) Could I remove the # and change that to 2G? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. Any guru here give me some enlightenment? hw.physmem is a loader tunable: ie. you can only set it from the boot loader before the kernel is fully operational. Once the kernel is running it can't be altered. hw.physmem is designed to let you test running a kernel with less RAM than is physically installed in a machine. Not having to pop the case and physically pull memory sticks out can be pretty useful. It's not of general interest -- only for kernel and various other software developers in the main -- as the usual thing is to make use of all the RAM you have available or (in the case of 32bit machines) that the system is capable of addressing. If hw.physmem is unset in loader.conf the kernel will automatically use all the memory available to it: this is the correct and desirable behaviour for the vast majority of systems. For a 2GB machine, that means the system will use all the RAM that's installed. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: loader.conf
Thanks for the detailed information. Best --- On Fri, 4/10/09, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: From: Matthew Seaman m.sea...@infracaninophile.co.uk Subject: Re: loader.conf To: ipfr...@yahoo.com Cc: freebsd general questions freebsd-questions@freebsd.org Date: Friday, April 10, 2009, 9:03 AM gahn wrote: Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G# Limit physical memory. See loader(8) Could I remove the # and change that to 2G? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. Any guru here give me some enlightenment? hw.physmem is a loader tunable: ie. you can only set it from the boot loader before the kernel is fully operational. Once the kernel is running it can't be altered. hw.physmem is designed to let you test running a kernel with less RAM than is physically installed in a machine. Not having to pop the case and physically pull memory sticks out can be pretty useful. It's not of general interest -- only for kernel and various other software developers in the main -- as the usual thing is to make use of all the RAM you have available or (in the case of 32bit machines) that the system is capable of addressing. If hw.physmem is unset in loader.conf the kernel will automatically use all the memory available to it: this is the correct and desirable behaviour for the vast majority of systems. For a 2GB machine, that means the system will use all the RAM that's installed. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf
Hi all: I have a machine with 2GB memory. in the file loader.conf, there is a line: #hw.physmem=1G# Limit physical memory. See loader(8) Could I remove the # and change that to 2G? # mean commented out. leave it as is or delete. you don't have to specify it unless you want intentionally reduce available memory. FreeBSD autodetects how much you have ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf fbsd 7-release
On Tue, 16 Dec 2008 13:19:54 -0500, Gary Hartl gha...@gmail.com wrote: Hi all; I need to add something to loader.conf which according to me should be in /boot Has something changed so that it wouldn't be there anymore. Or do i just create it and it will parse it out at boot. No, you're completely correct. /boot/loader.conf is to be created if neccessary to override /boot/defaults/loader.conf with the default settings. I need to add accf_http_load=YES to correct a problem with apache22 giving me the prompt/error (2)No such file or directory: Failed to enable the 'httpready' Accept Filter Just create the file and add the setting. It will then load /boot/kernel/accf_http.ko on system startup. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf fbsd 7-release
On Tue, 2008-12-16 at 13:19 -0500, Gary Hartl wrote: Hi all; I need to add something to loader.conf which according to me should be in /boot Has something changed so that it wouldn't be there anymore. Or do i just create it and it will parse it out at boot. I need to add accf_http_load=YES to correct a problem with apache22 giving me the prompt/error (2)No such file or directory: Failed to enable the 'httpready' Accept Filter Thanks Gary If /boot/loader.conf does not exist, you can create it and add that line. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: loader.conf issues
On Wed, Dec 3, 2008 at 5:45 PM, Weldon S Godfrey 3 [EMAIL PROTECTED] wrote: I did a quick search for this and didn't see anyone seeing this. I am running 7.0-PRERELEASE amd64 This is my loader.conf: vm.kmem_size_max=16106127360 vm.kmem_size=1073741824 kern.maxvnodes=80 However, this is what happens after reboot: store1# sysctl -a | grep kmem vm.kmem_size_scale: 3 vm.kmem_size_max: 3221225472 vm.kmem_size_min: 0 vm.kmem_size: 1073741824 store1# sysctl -a | grep kern.maxvn kern.maxvnodes: 10 store1# Is there some issue with vm.kmem_size_max being larger than 3G? If this has been fixed, let me know. I am using 7.0-RELEASE loader from amd64 iso since for some reason, when I complile a new loader on this Dell 2950-iii, I get an unusable loader (it just hangs before the screen to select safe mode, single user mode, etc). Quote Jeremy Chadwich talking about vm.kmem_size: 1) Consider increasing it from 512M to something like 1.5GB; do not increase it past that on RELENG_7, as there isn't support for more than 2GB total. For example, on a 1GB memory machine, I often recommend 768M. On 2GB machines, 1536M. You will need to run -CURRENT if you want more. a great day, v Thanks, Weldon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf issues
Thanks, I meant to update this earlier, it appears that the kmem tunables need a larger cast in 7.x (to use beyond 4GB kernel memory map), I opened a ticket yesterday. If memory serves me right, sometime around Yesterday, [EMAIL PROTECTED]: Weldon S Godfrey 3 [EMAIL PROTECTED] escribió: I did a quick search for this and didn't see anyone seeing this. I am running 7.0-PRERELEASE amd64 This is my loader.conf: vm.kmem_size_max=16106127360 vm.kmem_size=1073741824 kern.maxvnodes=80 I've always changed those variables in /etc/sysctl.conf ed However, this is what happens after reboot: store1# sysctl -a | grep kmem vm.kmem_size_scale: 3 vm.kmem_size_max: 3221225472 vm.kmem_size_min: 0 vm.kmem_size: 1073741824 store1# sysctl -a | grep kern.maxvn kern.maxvnodes: 10 store1# Is there some issue with vm.kmem_size_max being larger than 3G? If this has been fixed, let me know. I am using 7.0-RELEASE loader from amd64 iso since for some reason, when I complile a new loader on this Dell 2950-iii, I get an unusable loader (it just hangs before the screen to select safe mode, single user mode, etc). Thanks, Weldon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf issues
Troy Kocher wrote: Listers, For some reason my kernel setting aren't being recognized. . tao# more loader.conf geom_vinum_load=YES kern.ipc.semmni=256 kern.ipc.semmns=512 kern.ipc.semmnu=256 kern.ipc.semmap=256 kern.ipc.shmall=32768 kern.ipc.shmmax=1 On reboot shmall shmmax have to be set manually. What did I do wrong? Try adding them to /etc/sysctl.conf instead? Thanks Troy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf issues
On Tue, Jul 29, 2008 at 8:43 AM, Vincent Hoffman [EMAIL PROTECTED] wrote: Troy Kocher wrote: Listers, For some reason my kernel setting aren't being recognized. . tao# more loader.conf geom_vinum_load=YES kern.ipc.semmni=256 kern.ipc.semmns=512 kern.ipc.semmnu=256 kern.ipc.semmap=256 kern.ipc.shmall=32768 kern.ipc.shmmax=1 On reboot shmall shmmax have to be set manually. What did I do wrong? Try adding them to /etc/sysctl.conf instead? Thanks Troy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks I'll give that a try. . Troy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf != limits?
In the last episode (Feb 27), Randy Schultz said: I've been running some code with larger data sets and needed to up some kernerl parameters. I added this to loader.conf: kern.maxdsiz=1073741824 kern.dfldsiz=1073741824 kern.maxssiz=134217728 The odd thing is limits shows: Resource limits (current): cputime infinity secs filesize infinity kB datasize 1048576 kB stacksize 131072 kB Anybody know what's up with this? Should something be up? 1073741824/1024 is 1048576, which is what the limit command shows. The stack size hasn't changed because you didn't set kern.dflssiz. You can also set the default sizes in /etc/login.conf. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf != limits?
On Mon, 27 Feb 2006, Dan Nelson spaketh thusly: -}In the last episode (Feb 27), Randy Schultz said: -} I've been running some code with larger data sets and needed to up -} some kernerl parameters. I added this to loader.conf: -}kern.maxdsiz=1073741824 -}kern.dfldsiz=1073741824 -}kern.maxssiz=134217728 -} -} The odd thing is limits shows: -} Resource limits (current): -} cputime infinity secs -} filesize infinity kB -} datasize 1048576 kB -} stacksize 131072 kB -} -} Anybody know what's up with this? -} -}Should something be up? 1073741824/1024 is 1048576, which is what the -}limit command shows. The stack size hasn't changed because you didn't -}set kern.dflssiz. You can also set the default sizes in -}/etc/login.conf. Doh! Thinking powers of 10 not 2. Sorry. Didn't know about the login.conf bit tho'. Tnx. -- Randy([EMAIL PROTECTED]) 715-726-2832 email bodhisattva * There is no fire like passion, there is no shark like hatred, there is no snare like folly, there is no torrent like greed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf question
makisupa [EMAIL PROTECTED] writes: Got k3b installed and trying to sort out some issues. This is a 6.0RC1 with a custom kernel box. In /boot/loader.conf i pass a 'load_atapicam=YES'. This is the only argument there...but its not working. Once booted if I simply 'kldload atapicam' everything works like a charm -- scanbus, k3b (minus permissions but that's not the issue right now). What gives? Why is my system skipping the loader.conf? Where else should i put the argument? You mean atapicam_load rather than load_atapicam, right? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf question
That was a serious id10T error THanks, mak (i must need more coffee) On Fri, 2005-10-21 at 09:47 -0400, Lowell Gilbert wrote: makisupa [EMAIL PROTECTED] writes: Got k3b installed and trying to sort out some issues. This is a 6.0RC1 with a custom kernel box. In /boot/loader.conf i pass a 'load_atapicam=YES'. This is the only argument there...but its not working. Once booted if I simply 'kldload atapicam' everything works like a charm -- scanbus, k3b (minus permissions but that's not the issue right now). What gives? Why is my system skipping the loader.conf? Where else should i put the argument? You mean atapicam_load rather than load_atapicam, right? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
