Re: rc.conf and loader.conf
On Fri, 26 Oct 2012 07:37:09 +0200 (CEST), Trond Endrestøl wrote: However, I like to keep the lines in the /etc/rc.conf file in the same order as they appear in the /etc/defaults/rc.conf file, and place local stuff (from /usr/local/etc/rc.d) in alphabetical order at the bottom of the file. Slight deviation: I tend to group settings according to their functionality (network, server stuff, console settings etc.), and also have local additions at the end of the file. However, FreeBSD also supports rc.conf.local to keep them. The rc.conf file can be seen as a shell script, containing variable assignments. It is that simple. It implies that you can arrange everything (with newlines, comments, in groups, as you wish) as long as it is valid shell syntax. -- Polytropon 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
rc.conf and loader.conf
hi, what is the best order of items in rc.conf and loader.conf? actually items order is important? Best regards, Ashkan ___ 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: rc.conf and loader.conf
On Oct 25, 2012, at 5:17 PM, Ashkan Rahmani wrote: hi, what is the best order of items in rc.conf and loader.conf? actually items order is important? order does not matter (unless you have duplicates -- in which case later assignments override previous ones). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: rc.conf and loader.conf
Hi, On Fri, 26 Oct 2012 03:47:29 +0330 Ashkan Rahmani ashkan...@gmail.com wrote: hi, what is the best order of items in rc.conf and loader.conf? actually items order is important? as you know already, the order does not matter at all. But there some modules which cannot coexist. I prefer to build a custom kernel over loading modules. Of course, as this does not always lead to a perfect solution, I still have some kernel modules which are loaded at boot time or even after the system is up and running via a script I start manually. With other words, FreeBSD gives you all the freedom you need to get the best solution for your needs. Erich Best regards, Ashkan ___ 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: rc.conf and loader.conf
On Fri, 26 Oct 2012 03:47+0330, Ashkan Rahmani wrote: hi, what is the best order of items in rc.conf and loader.conf? actually items order is important? Order is not important, as explained by someone else on the list. However, I like to keep the lines in the /etc/rc.conf file in the same order as they appear in the /etc/defaults/rc.conf file, and place local stuff (from /usr/local/etc/rc.d) in alphabetical order at the bottom of the file. Just my $0.02. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ 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: mps driver overwrite using loader.conf
Hi, I have found another email id to post question so adding freebsd-questions@freebsd.org in list. Here are some more detail. mps driver is inbuilt in FreeBSD-9 and FreeBSD-10-Current. I want to use my next version of driver mps to be loaded instead of mps compiled inbuilt in kernel binary. When I added /boot/loader.conf with mps_load=YES, I see my new driver available at /boot/kernel/mps.ko is getting loaded on FreeBSD-9-RELEASE, but on FreeBSD-10-CURRENT it always use inbuilt mps driver. Any Idea if this is expected behavior ? Any change in FreeBSD-10 is causing this behavioral difference ? ` Kashyap -Original Message- From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd- s...@freebsd.org] On Behalf Of Desai, Kashyap Sent: Thursday, February 09, 2012 12:24 AM To: Kenneth D. Merry; freebsd-s...@freebsd.org Cc: Justin T. Gibbs; McConnell, Stephen Subject: mps driver overwrite using loader.conf With upstream mps driver, I am trying to do some testing with my next driver. I followed below process to overwrite existing mps driver with new one. 1. My kernel has pre-compiled mps driver (It is not part of module) 2. While booting itself I wants to replace with my next version of mps driver. 3. I copy my new mps driver at /boot/kernel/ location 4. modify /boot/defaults/loader.conf with mps_load = YES Now I see new mps is getting loaded instead of inbuilt mps driver. Here is output of sysctl with mpslsi driver loaded into kernel. [For LSI's internal tracking this driver is called mpslsi ] device mps hw.mps.disable_msi: 0 hw.mps.disable_msix: 0 dev.mpslsi.0.%desc: LSI SAS2008 dev.mpslsi.0.%driver: mpslsi dev.mpslsi.0.%location: slot=0 function=0 dev.mpslsi.0.%pnpinfo: vendor=0x1000 device=0x0072 subvendor=0x1000 subdevice=0x0072 class=0x010700 dev.mpslsi.0.%parent: pci6 dev.mpslsi.0.debug_level: 0 dev.mpslsi.0.disable_msix: 0 dev.mpslsi.0.disable_msi: 0 dev.mpslsi.0.firmware_version: 12.250.01.00 dev.mpslsi.0.driver_version: 13.255.00.01 -- New Driver dev.mpslsi.0.io_cmds_active: 0 dev.mpslsi.0.io_cmds_highwater: 1 dev.mpslsi.0.chain_free: 2048 dev.mpslsi.0.chain_free_lowwater: 2047 dev.mpslsi.0.max_chains: 2048 dev.mpslsi.0.chain_alloc_fail: 0 _But_ Strange thing is if I unload my mps module, there is still some stale entry in kernel. After I unload mpslsi driver here is output of sysctl device mps hw.mps.disable_msi: 0 hw.mps.disable_msix: 0 What is this device mps instance ? I want to understand How FreeBSD handle this kind of scenario ? ~ Kashyap ___ freebsd-s...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-scsi To unsubscribe, send any mail to freebsd-scsi-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
loader.conf options
hey am trying to configure my new system (FreeBSD 8.1-RELEASE GENERIC amd64 - on an intel core 2 duo) and find all possible settings to tweak i can tell from documentation that there are many options possible with /boot/loader.conf as well as others though i cannot find any definitive list i am sure that this - in some cases - depends on how the rest of system is configured hardware bios, software bios, kernel ... and so on i can never find the right value to set at the time that i want to set it always seems to be in passing while looking up something else am currently looking for values to tweak the kernel with, though would rather rely on module loading and loader.config settings and device.hints have got: /usr/src/sys/conf/NOTES /usr/src/sys/amd64/conf/NOTES man loader.conf man device.hints handbook FAQ am looking for: memory/bus (tweaks for I/O speeds / caching ...) attached hardware multimedia/sound/video/midi ___ 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 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
Kernel loading very slowly with specific (wrong?) loader.conf
Hi, when you use the following loader.conf: # cat /boot/loader.conf hint.sio.1.flags=0x20 comconsole_speed=115200 boot_multicons=yes and have no /boot.config, then booting the kernel is extremely slow. It writes about one character per second on the screen. Also i dont actually have a serial device (dmesg says so), although i should. cu, Leon ___ 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
Can RAID driver be loaded from loader.conf?
Hello! I'm preparing for a migration from single SATA disk attached to onboard SATA controller to 3ware 9750-4i RAID system. In preparation, while the system is still running on single disk, I downloaded the latest tws.ko driver from LSI website and added it to loader.conf: tws_load=YES Further plan is to install the controller and new disks into the system alongside with the existing disk, create partitions on new disk and copy over all the contents using dump and tar. After that remove the existing single disk. Is it safe to assume that the system will boot from RAID if RAID controller driver is loaded from loader.conf, or is it absolutely required to have the RAID driver statically built into the kernel? -- Toomas Aas ___ 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: Can RAID driver be loaded from loader.conf?
In the last episode (Feb 10), Toomas Aas said: I'm preparing for a migration from single SATA disk attached to onboard SATA controller to 3ware 9750-4i RAID system. In preparation, while the system is still running on single disk, I downloaded the latest tws.ko driver from LSI website and added it to loader.conf: tws_load=YES Further plan is to install the controller and new disks into the system alongside with the existing disk, create partitions on new disk and copy over all the contents using dump and tar. After that remove the existing single disk. Is it safe to assume that the system will boot from RAID if RAID controller driver is loaded from loader.conf, or is it absolutely required to have the RAID driver statically built into the kernel? You should be able to load raid drivers as modules just fine. /boot/loader uses BIOS calls to read both the kernel and any modules listed in loader.conf, so if it can load the kernel, it should be able to load the modules too. -- Dan Nelson dnel...@allantgroup.com ___ 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
8.0-R failing to parse DHCP root-path or loader.conf/rc vars (Diskless NFS/PXE)
All: DHCP: option root-path 192.168.224.67:/export/tftpboot/root-db; loader.rc: set vfs.root.mountfrom=nfs set vfs.root.mountfrom.options=rw set boot.nfsroot.path=/export/tftpboot/root-web set boot.nfsroot.server=192.168.224.67 loader.conf: mfsroot_load=NO nfsclient_load=YES init_path=/stand/sysinstall autoboot_delay=2 The kernel fails to mount / as RW with: mount option export is unknown Then some mysterious file system that isnt' MFS and isn't NFS show up. I don't think any of the docs out there are up to date, and from mailing list discussion, the syntax appears to have changed in 8.0 Anyone out there running a diskless config? ~BAS ___ 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
Loader.conf mfs statements
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? ___ 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
Can loader.conf give you NATD support?
The natd man page says it is still necessary to create a customer kernl with options IPFIREWALL options IPDIVERT Is that still true, or can it be accomplished vi a loader.conf? Thanks! -- John Lind j...@starfire.mn.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: Can loader.conf give you NATD support?
On Mon, 8 Feb 2010, John wrote: The natd man page says it is still necessary to create a customer kernl with options IPFIREWALL options IPDIVERT Is that still true, or can it be accomplished vi a loader.conf? It's a kernel option, so you probably can't do it at runtime. Consider using pf instead of ipfw. pf does NAT without needing natd or those kernel options. -Warren Block * Rapid City, South Dakota USA ___ 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: Can loader.conf give you NATD support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/02/2010 15:39, Warren Block wrote: On Mon, 8 Feb 2010, John wrote: The natd man page says it is still necessary to create a customer kernl with options IPFIREWALL options IPDIVERT Is that still true, or can it be accomplished vi a loader.conf? It's a kernel option, so you probably can't do it at runtime. It's a loadable module (ipfw_nat.ko) nowadays, so you probably can do it at runtime... Consider using pf instead of ipfw. pf does NAT without needing natd or those kernel options. Heartily seconded. pf and ipfw fulfil the same sort of function, but to my mind, pf wins hands down simply by having a much more usable control interface and configuration syntax. Not to mention the advanced pf features like ftp-proxy, HA configuration, relayd and a bunch more. 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 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktwOHkACgkQ8Mjk52CukIwuuwCeJwUl0RH1nSqIfYZimP7sO1hW ZZMAnjP1ZXWZVVZsPQA4YEFPtXHMWs1c =r3ny -END PGP SIGNATURE- ___ 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: Can loader.conf give you NATD support?
On Mon, Feb 08, 2010 at 08:39:14AM -0700, Warren Block wrote: On Mon, 8 Feb 2010, John wrote: The natd man page says it is still necessary to create a customer kernl with options IPFIREWALL options IPDIVERT Is that still true, or can it be accomplished vi a loader.conf? It's a kernel option, so you probably can't do it at runtime. Consider using pf instead of ipfw. pf does NAT without needing natd or those kernel options. Oh. OK! That must be new since the last time I did this. Will it be difficult to port my ipfw and natd rules to pf? -Warren Block * Rapid City, South Dakota USA ___ 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 -- John Lind j...@starfire.mn.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
specifying nfs root in loader.conf with vfs.root.mountfrom
Hi: OK, I know I'm not doing this the easy way, don't try to convince me about other ways :) I'm doing PXE boot diskless, fetching the GENERIC kernel with TFTP. Problem is that since the kernel is fetched with tftp, there is no nfs root file system mounted when kernel finish loading. There are, as I see two solutions to this: Compile the kernel with BOOTP and BOOTP_COMPAT options to allow the kernel o rerequest root-path option set with dhcp. Or, configure the root path in loader.conf: (from defaults/loader.conf) #vfs.root.mountfrom= # Specify root partition in a way the # kernel understands So, I set in my diskless loader.conf: vfs.root.mountfrom=nfs:192.168.0.1:/var/diskless/FreeBSD Booting up I get: nfs_diskless: no NFS handle Trying to mount root from nfs:192.168.0.1:/var/diskless/FreeBSD nfs_diskless: no NFS handle ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try to the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid options from /etc/fstab ... Question: How do I specify an nfs share as root path with vfs.root.mountfrom? Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.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
options IPFIREWALL and IPDIVERT or loader.conf?
I guess I can either pre-buuild a kernel with options IPFIREWALL and IPDIVERT, or I can load them via loader.conf. Why would I not always do the latter? Is there any advantage to pre-linking them? Thanks! -- John Lind j...@starfire.mn.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
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? Interestingly, the sysctl indicates the parameter of hw.physmem is not changeable. 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
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
loader.conf fbsd 7-release
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 ___ 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]
loader.conf issues
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). Thanks, Weldon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
loader.conf issues
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? Thanks 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 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]
Stuck on loader.conf
Hi All, As a newbie on freebsd I eagerly played this featureful OS, now my last one being the serial console, sure enough my two fsbd box can connect to each other console via com port/null-modem connection, unfortunately as I had already finished I revert but the old entry on /etc/ttys but forgot to take out the console=comconsole on /boot/loader.conf. As of of now I had lost connection via com port and worst stuck on boot at loader.conf section. Though erasing the whole OS would just take a minute, I look at this as an opportunity to learn how to approach, in case on a real production box. How shall I proceed? Stuck on loader at infinity, --joseph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stuck on loader.conf
As a newbie on freebsd I eagerly played this featureful OS, now my last one being the serial console, sure enough my two fsbd box can connect to each other console via com port/null-modem connection, unfortunately as I had already finished I revert but the old entry on /etc/ttys but forgot to take out the console=comconsole on /boot/loader.conf. As of of now I had lost connection via com port and worst stuck on boot at loader.conf section. 1) connect the console back, boot single user and fix loader.conf 2) boot from install/live cd, mount root partition and fix loader.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: module loads from kldload, but gives Unsupported file type from loader.conf
On Jan 5, 2008, at 8:01 PM, Steve Franks wrote: I successfully built snd_hda on my 6.3amd64 system, so I placed it in loader.conf (snd_hda_load=YES), when I boot, dmesg shows: kldload: Unsupported file type If I sudo kldload snd_hda, dmesg shows: kldload: Unsupported file type kldload: Unsupported file type pcm0: Intel 82801G High Definition Audio Controller mem 0xfdff8000-0xfdffbfff irq 16 at device 27.0 on pci0 pcm0: HDA Codec: Realtek ALC883 pcm0: HDA Driver Revision: 20071129_0050 Note: on startup, there is one unsupported, after kldload, there is two, but the module loads sucessfully! Anyone heard of this ?!? Steve The same thing happens to me with green_saver. It loads, it works, but something's unsupported. I've never got an answer why it's reported as unsupported. ___ 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]
module loads from kldload, but gives Unsupported file type from loader.conf
I successfully built snd_hda on my 6.3amd64 system, so I placed it in loader.conf (snd_hda_load=YES), when I boot, dmesg shows: kldload: Unsupported file type If I sudo kldload snd_hda, dmesg shows: kldload: Unsupported file type kldload: Unsupported file type pcm0: Intel 82801G High Definition Audio Controller mem 0xfdff8000-0xfdffbfff irq 16 at device 27.0 on pci0 pcm0: HDA Codec: Realtek ALC883 pcm0: HDA Driver Revision: 20071129_0050 Note: on startup, there is one unsupported, after kldload, there is two, but the module loads sucessfully! Anyone heard of this ?!? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
loading modules not in /boot/kernel from loader.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a fuse_load=YES will not work because of this. But, mv/cp/ln'ing it to /boot/kernel gets nuked if you rebuild/install the kernel. How to get around this? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXUAtzIOMjAek4JIRApF1AJ4wbXjTQVt4wngiRObv7A2iTJFPQwCgnFiT V63lqeMKC4vWDHdykrcxXGo= =JB+k -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The fusefs rc script will run kldload /usr/local/modules/fuse.ko. You don't need to add anything to loader.conf . Secondly, you should add kernel modules to the /boot/modules dir not /boot/kernel. Thanks but I use a handwritten /etc/rc that does not call any thing in /etc/rc.d so the question stands -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXUzbzIOMjAek4JIRAm6VAJ4ysRZCw+3+cN6q6cPKa4ARdEleAwCglfGF 85cENq4/EyFrORvY2VVwNnk= =yo/4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a fuse_load=YES will not work because of this. But, mv/cp/ln'ing it to /boot/kernel gets nuked if you rebuild/install the kernel. How to get around this? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXUAtzIOMjAek4JIRApF1AJ4wbXjTQVt4wngiRObv7A2iTJFPQwCgnFiT V63lqeMKC4vWDHdykrcxXGo= =JB+k -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The fusefs rc script will run kldload /usr/local/modules/fuse.ko. You don't need to add anything to loader.conf . Secondly, you should add kernel modules to the /boot/modules dir not /boot/kernel. -Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
In the last episode (Dec 10), Aryeh M. Friedman said: sysutils/fusefs-kmod installs to /usr/local/modules/fuse.ko and a fuse_load=YES will not work because of this. But, mv/cp/ln'ing it to /boot/kernel gets nuked if you rebuild/install the kernel. How to get around this? The loader also checks /boot/modules/ , so copy your stuff there. That's where the kqemu-kmod port puts kqemu.ko, for example. -- 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: loading modules not in /boot/kernel from loader.conf
Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The fusefs rc script will run kldload /usr/local/modules/fuse.ko. You don't need to add anything to loader.conf . Secondly, you should add kernel modules to the /boot/modules dir not /boot/kernel. Thanks but I use a handwritten /etc/rc that does not call any thing in /etc/rc.d so the question stands -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXUzbzIOMjAek4JIRAm6VAJ4ysRZCw+3+cN6q6cPKa4ARdEleAwCglfGF 85cENq4/EyFrORvY2VVwNnk= =yo/4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You could make a softlink... Rg, Tino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXWEnzIOMjAek4JIRAudyAKCMHwjBLmVkoBQ+1phqSjgxZs7oDACffqck Sqz6d33doxp89KzUcH6TsSY= =LcV4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Engel wrote: Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? If it worked I had not of asked the question (installkernel nukes it) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXWLMzIOMjAek4JIRAqblAJ4jnHJJtl78j6ocNbDpgEEUo6BvGACdGgso COMPBBIMaDET8ce2rSyPvEU= =qiMh -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
Tino Engel wrote: Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? Yeah, if you put a kernel module in /boot/kernel, installkernel will wipe it out when you install a new kernel. That's why there is /boot/modules for kernel modules. installkernel shouldn't touch that. Change to: ln -s /usr/local/modules/fuse.ko /boot/modules/fuse.ko or add this to /boot/loader.conf: module_path=/boot/modules:/usr/local/modules fusefs_load=YES ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Engel wrote: Aryeh M. Friedman schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko And it did not work? If it worked I had not of asked the question (installkernel nukes it) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXWLMzIOMjAek4JIRAqblAJ4jnHJJtl78j6ocNbDpgEEUo6BvGACdGgso COMPBBIMaDET8ce2rSyPvEU= =qiMh -END PGP SIGNATURE- So doing ln -s /usr/local/modules/fuse.ko /boot/modules/fuse.ko as proposed, should persist throughout kernel updates I assume. Rg, Tino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loading modules not in /boot/kernel from loader.conf
On 11/12/2007 2:54 AM, Aryeh M. Friedman wrote: You could make a softlink... Thats what raised the question I was doing ln -s /usr/local/modules/fuse.ko /boot/kernel/fuse.ko Remember that this is the loader which will be loading the module, so if /usr is a separate partition then this will not work as /usr doesn't get mounted until much, much later in the boot process... Alternatively, if you're using your own home-brew rc script, why not just add a kldload fuse into it? --Antony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
loading modules not in /boot/kernel from loader.conf
I have had bad experiences with loading modules anywhere except /boot/loader.conf and even so there is some hacking in the rc to make it work fine for example: (sleep 5;ntfs-3g ) is the last line in the rc Remember that this is the loader which will be loading the module, so if /usr is a separate partition then this will not work as /usr doesn't get mounted until much, much later in the boot process... Alternatively, if you're using your own home-brew rc script, why not just add a kldload fuse into it? --Antony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
unable to boot due to error in loader.conf
Hello, Since people were talking about modifying kern.hz , I went the extreme and added kern.hz=10 to loader.conf , obviously the system didn't load properly. It panics during boot process. This is 5.4-Stable, I've tried all other boot modes and the only option available is Escape to Loader Prompt. Any tips on a way to recover this machine ? Thanks, Tamouh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to boot due to error in loader.conf
Tamouh H. [EMAIL PROTECTED] writes: Since people were talking about modifying kern.hz , I went the extreme and added kern.hz=10 to loader.conf , obviously the system didn't load properly. It panics during boot process. This is 5.4-Stable, I've tried all other boot modes and the only option available is Escape to Loader Prompt. Any tips on a way to recover this machine ? Escape to the loader prompt, and set it back. I think the syntax should be set kern.hz=1000, but check the manual (online, if necessary) if I messed up on the details. Then remove the line from loader.conf once you boot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Cannot su or have root access after changing loader.conf
Loader.conf with the following statement disable all su or root access: kern.dfldsiz=1G kern.maxdsiz=1G kern.maxssiz=131072 When I add the above 3 lines, all access to su or even single user boot is restricted without any error messages. Is this a bug or 1G is not supported for maximum data size? My server is a 2GB ram E6600 with 400GB HDD. What are the valid values for these lines? thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, June 11, 2007 8:00 PM To: freebsd-questions@freebsd.org Subject: freebsd-questions Digest, Vol 182, Issue 2 Send freebsd-questions mailing list submissions to freebsd-questions@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-questions or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of freebsd-questions digest... Today's Topics: 1. Re: [FreeBSD][Newb] How I use sendmail to send mail? (Doug Hardie) 2. Re: [FreeBSD][Newb] How I use sendmail to send mail? (Bjorn Boulder) 3. Re: [FreeBSD][Newb] How I use sendmail to send mail? (Bjorn Boulder) 4. Re: [FreeBSD][Newb] How I use sendmail to send mail? (Toomas Aas) 5. tcp port error (tethys ocean) 6. Installing FreeBSD on large disk 2TB (Enrique Ayesta Perojo) 7. Re: Installing FreeBSD on large disk 2TB (Andreas Rudisch) 8. Re: [FreeBSD][Newb] How I use sendmail to send mail? (Bjorn Boulder) 9. procmailrc configuration fails (dhaneshk k) 10. Re: Installing FreeBSD on large disk 2TB (Enrique Ayesta Perojo) -- Message: 1 Date: Sun, 10 Jun 2007 21:45:48 -0700 From: Doug Hardie [EMAIL PROTECTED] Subject: Re: [FreeBSD][Newb] How I use sendmail to send mail? To: Bjorn Boulder [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Jun 10, 2007, at 21:25, Bjorn Boulder wrote: Doug, Mats Your advice is on the money; thanks. I see this: Jun 10 05:43:40 jake sendmail[15068]: l5AAhekD015068: [EMAIL PROTECTED], ctladdr=oracle (1004/1005), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30062, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1] Your tip along with that given by Mats suggests that I need to learn about /etc/mail/sendmail.cf It appears that the box cannot send mail to itself: Jun 10 03:05:44 jake sendmail[14546]: l5A84ObZ014546: to=postmaster, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=154501, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1] Jun 10 03:05:44 jake sendmail[14546]: l5485I55093939: to=root, ctladdr=root (0/0), delay=6+00:00:26, xdelay=00:00:00, mailer=relay, pri=691450, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1] Jun 10 03:05:44 jake sendmail[14546]: l5485I55093939: l5A84Oba014546: sender notify: Cannot send message for 5 days Jun 10 03:05:44 jake sendmail[14546]: l5A84Oba014546: to=root, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=152806, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1] Currently, my main assumption is that /etc/mail/sendmail.cf is the primary administrative interface for e-mail. That is correct, but you don't want to directly mess with sendmail.cf. You really want to use the mc file and then make to build the cf file. Its much easier and more readable. See /usr/ share/sendmail/cf/readme for more details. The cf files are in another directory from there named cf. You will also want to use sendmail -bv email-address to have sendmail show you how and where it will deliver for the address: email-address. That is a useful tool. -- Message: 2 Date: Sun, 10 Jun 2007 22:02:13 -0700 (PDT) From: Bjorn Boulder [EMAIL PROTECTED] Subject: Re: [FreeBSD][Newb] How I use sendmail to send mail? To: Doug Hardie [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 ok, I'll look at that readme. And I nosed around on the box for clues about sendmail.cf It looks like the previous sysadmin ignored sendmail.cf I see this: bash jake oracle /etc/mail 14 $ pwd /etc/mail bash jake oracle /etc/mail 15 $ bash jake oracle /etc/mail 15 $ bash jake oracle /etc/mail 15 $ ls -latr total 582 -rw-r--r-- 1 root wheel569 Nov 4 2004 virtusertable.sample -r--r--r-- 1 root wheel 40449 Nov 4 2004 submit.cf -rw-r--r-- 1 root wheel 57796 Nov 4 2004 sendmail.cf -rw-r--r-- 1 root
problem after editing /boot/defaults/loader.conf
Hi I have a problem after editing /boot/defaults/loader.conf, I wanted to enable a boot splash picture. So when I rebooted, I coudnt boot :s After selecting the booting type (normal boot or something) It showe loading kernel text = 0x. mem=0x. and then it freezed. I can reboot it pressing ctrl + alt + supr. Is there any way to fix it? Thanks. -- http://feudaltimes.com.ar - Feudal Times `s webmaster and programer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem after editing /boot/defaults/loader.conf
On Thu, Apr 05, 2007 at 02:44:24PM -0300, freenity wrote: Hi I have a problem after editing /boot/defaults/loader.conf, I wanted to enable a boot splash picture. So when I rebooted, I coudnt boot :s After selecting the booting type (normal boot or something) It showe loading kernel text = 0x. mem=0x. and then it freezed. I can reboot it pressing ctrl + alt + supr. Is there any way to fix it? Thanks. Well for starters you are not supposed to edit /boot/defaults, that is for default settings, not customized ones :) Override in /boot/loader.conf according to the directions in splash(4). I guess you might need to better follow the other directions there too, so if the problem persists then get back to us. Kris pgpADi0Gbt89x.pgp Description: PGP signature
Re: problem after editing /boot/defaults/loader.conf
yes i tried to load /boot/loader.conf but it says that there was syntax error while loading vesa module, the same problem happened with /boot/defaults/loader.conf I didnt edit /boot/loader.conf =) Is there any way I can edit those files? Im on winxp now, is there any program that can read/write fbsd partition? On 4/5/07, Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Apr 05, 2007 at 02:44:24PM -0300, freenity wrote: Hi I have a problem after editing /boot/defaults/loader.conf, I wanted to enable a boot splash picture. So when I rebooted, I coudnt boot :s After selecting the booting type (normal boot or something) It showe loading kernel text = 0x. mem=0x. and then it freezed. I can reboot it pressing ctrl + alt + supr. Is there any way to fix it? Thanks. Well for starters you are not supposed to edit /boot/defaults, that is for default settings, not customized ones :) Override in /boot/loader.conf according to the directions in splash(4). I guess you might need to better follow the other directions there too, so if the problem persists then get back to us. Kris -- http://feudaltimes.com.ar - Feudal Times `s webmaster and programer. http://gamescreators.sourceforge.net - linux games programing community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem after editing /boot/defaults/loader.conf
freenity wrote: yes i tried to load /boot/loader.conf but it says that there was syntax error while loading vesa module, the same problem happened with /boot/defaults/loader.conf I didnt edit /boot/loader.conf =) Is there any way I can edit those files? Im on winxp now, is there any program that can read/write fbsd partition? boot to the bsd install CD and run the live file system from the FixIt menu. Mount your drives and edit away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem after editing /boot/defaults/loader.conf
On Thu, Apr 05, 2007 at 04:58:41PM -0300, freenity wrote: yes i tried to load /boot/loader.conf but it says that there was syntax error while loading vesa module, the same problem happened with /boot/defaults/loader.conf I didnt edit /boot/loader.conf =) Then you were really doing something wrong. Please read that manpage carefully. Kris pgpqpzap0IIxi.pgp Description: PGP signature
How to bypass loader.conf at boot
Hi all, I edited the /boot/loader.conf to add values for kern.maxdsiz and kern.dfldsiz. Unfortunately my server can not boot after that (the values are too big). How can I bypass the loader.conf parameters at boot? Or how I can change these values interactively? The server is located in a data center and I can access to it through supporter. Please advice. Thanks all for helping. PS. Please CC me because I'm not in this list. - With best regards, |The Power to Serve Nguyen Tam Chinh| http://www.FreeBSD.org Loc: sp.cs.msu.su | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to bypass loader.conf at boot
* On 17/08/06 21:22 +0400, Nguyen Tam Chinh wrote: | Hi all, | | I edited the /boot/loader.conf to add values for kern.maxdsiz and | kern.dfldsiz. | Unfortunately my server can not boot after that (the values are too big). | How can I bypass the loader.conf parameters at | boot? Or how I can change these values interactively? | The server is located in a data center and I can access to it through | supporter. | Please advice. | Thanks all for helping. | | PS. Please CC me because I'm not in this list. Off the top of my head . Get the guy at the data centre to get a 5.x or 6.x installation CD. He should boot with it and choose the Fixit option, and select the live filesystem on CD. After that, he will be dropped into a shell and the following steps will work: fsck -y /dev/da0s1a (change to the correct slice name!!) Once that is complete: mount /dev/da0s1a /mnt vi /mnt/boot/loader.conf save changes Exit the Fixit mode and reboot, removing the CD, and voila! -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ Nothing is more admirable than the fortitude with which millionaires tolerate the disadvantages of their wealth. -- Nero Wolfe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to bypass loader.conf at boot
Nguyen Tam Chinh wrote: Hi all, I edited the /boot/loader.conf to add values for kern.maxdsiz and kern.dfldsiz. Unfortunately my server can not boot after that (the values are too big). How can I bypass the loader.conf parameters at boot? Or how I can change these values interactively? The server is located in a data center and I can access to it through supporter. Please advice. Thanks all for helping. Choose boot menu option 6: Escape to loader prompt Then you can set/unset anything. Use show to see the current values, set to set some parameter, load/unload to load or unload kernel or modules - see help for more. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 smime.p7s Description: S/MIME Cryptographic Signature
Re[2]: How to bypass loader.conf at boot
Hello Odhiambo, Thursday, August 17, 2006, 7:47:20 PM, you wrote: * On 17/08/06 21:22 +0400, Nguyen Tam Chinh wrote: | Hi all, | | I edited the /boot/loader.conf to add values for kern.maxdsiz and | kern.dfldsiz. | Unfortunately my server can not boot after that (the values are too big). | How can I bypass the loader.conf parameters at | boot? Or how I can change these values interactively? | The server is located in a data center and I can access to it through | supporter. | Please advice. | Thanks all for helping. | | PS. Please CC me because I'm not in this list. Off the top of my head . I don't think that this is really needed. Let the technician boot the box and tell him to escape to the boot prompt. When he will be done, he just need to unset those variables with the following command -- unset kern.maxdsiz; and unset kern.dfldsiz. After that, he will just have to type 'boot' and that's all. I hope that this will work for him ;-) Anyway, try to read through loader(8) manual page. Get the guy at the data centre to get a 5.x or 6.x installation CD. He should boot with it and choose the Fixit option, and select the live filesystem on CD. After that, he will be dropped into a shell and the following steps will work: fsck -y /dev/da0s1a (change to the correct slice name!!) Once that is complete: mount /dev/da0s1a /mnt vi /mnt/boot/loader.conf save changes Exit the Fixit mode and reboot, removing the CD, and voila! -Wash -- Best regards, Danielmailto:[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: some questions about fsck, loader.conf
On Wednesday 15 March 2006 07:31, Dan Nelson wrote: In rc.conf I have enabled fsck_y_enable=YES to allow unattended fsck fixes after improper shutdown but I have noticed there are some problems remaining as shown by a read only fsck. Does the above switch not fix all problems or is it the case the fsck bootup script only does partial tests? A read-only fsck of a mounted filesystem will never come back clean, since the filesystem's mounted :) I think the question was: why did it find an error, when fsck had run at boot? Were you running background checking? And had it completed? Also there was a bug where partitions fixed with background checking still showed a minor error when unmounted and checked - check the list for details. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some questions about fsck, loader.conf
On 17/03/06, RW [EMAIL PROTECTED] wrote: On Wednesday 15 March 2006 07:31, Dan Nelson wrote: In rc.conf I have enabled fsck_y_enable=YES to allow unattended fsck fixes after improper shutdown but I have noticed there are some problems remaining as shown by a read only fsck. Does the above switch not fix all problems or is it the case the fsck bootup script only does partial tests? A read-only fsck of a mounted filesystem will never come back clean, since the filesystem's mounted :) I think the question was: why did it find an error, when fsck had run at boot? Were you running background checking? And had it completed? Also there was a bug where partitions fixed with background checking still showed a minor error when unmounted and checked - check the list for details. good question, the reasoning for me doing the online fsck check was I suspect the hd itself is faulty from other factors such as very slow performance and recent crashes, I have no local access to the machine and I am not sure if the datacentre has been fully honest with me. Background checking is on assuming thats the default. However I then did some read only checks on another box which has never had an improper shutdown and that also showed errors which I will paste here. ** Phase 5 - Check Cyl groups 53 files, 36 used, 126803 free (43 frags, 15845 blocks, 0.0% fragmentation) ** /dev/ad2s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=4663374 OWNER=root MODE=100644 SIZE=0 MTIME=Mar 17 00:31 2006 CLEAR? no ZERO LENGTH DIR I=5087752 OWNER=root MODE=40755 SIZE=0 MTIME=Feb 2 01:47 2006 CLEAR? no UNREF FILE I=5092692 OWNER=root MODE=100755 SIZE=10036 MTIME=Dec 22 23:19 2005 CLEAR? no UNREF FILE I=5140575 OWNER=root MODE=100755 SIZE=389582 MTIME=Jan 13 13:05 2006 CLEAR? no UNREF FILE I=5206424 OWNER=root MODE=100555 SIZE=15071 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206613 OWNER=root MODE=100555 SIZE=107521 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206633 OWNER=root MODE=100555 SIZE=29059 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206638 OWNER=root MODE=100555 SIZE=25480 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206668 OWNER=root MODE=100555 SIZE=7189 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5206671 OWNER=root MODE=100555 SIZE=13884 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5252342 OWNER=frogees MODE=100644 SIZE=6 MTIME=Jan 30 22:36 2006 CLEAR? no UNREF FILE I=5325324 OWNER=root MODE=100555 SIZE=1209532 MTIME=Dec 22 23:17 2005 CLEAR? no UNREF FILE I=5347550 OWNER=allriped MODE=100644 SIZE=6 MTIME=Feb 9 09:51 2006 CLEAR? no ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no ALLOCATED FRAGS 21549328-21549351 MARKED FREE ALLOCATED FRAG 21552423 MARKED FREE ALLOCATED FRAGS 21560112-21560115 MARKED FREE 285913 files, 39238077 used, 1617 free (78934 frags, 2011661 blocks, 0.1% fragmentation) and results from last read.write check are clean. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
some questions about fsck, loader.conf
Hi I tried verbose_loading=YES in loader.conf and expected the /var/run/dmesg.boot to be more detailed but there was no change, what does this switch do if it doesnt change the bootup dmesg output? In rc.conf I have enabled fsck_y_enable=YES to allow unattended fsck fixes after improper shutdown but I have noticed there are some problems remaining as shown by a read only fsck. Does the above switch not fix all problems or is it the case the fsck bootup script only does partial tests? Can I do a full fsck test and fix on a remote machine without needing a local tech to boot the machine in single user mode? Thanks Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some questions about fsck, loader.conf
In the last episode (Mar 15), Chris said: I tried verbose_loading=YES in loader.conf and expected the /var/run/dmesg.boot to be more detailed but there was no change, what does this switch do if it doesnt change the bootup dmesg output? I think you want boot_verbose=YES. verbose_loading only makes /boot/loader itself more verbose. In rc.conf I have enabled fsck_y_enable=YES to allow unattended fsck fixes after improper shutdown but I have noticed there are some problems remaining as shown by a read only fsck. Does the above switch not fix all problems or is it the case the fsck bootup script only does partial tests? A read-only fsck of a mounted filesystem will never come back clean, since the filesystem's mounted :) -- 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]
loader.conf != limits?
Hey all, 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 coredumpsize infinity kB memoryuseinfinity kB memorylocked infinity kB maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kB Anybody know what's up with this? -- 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 != 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]
loader.conf question
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? THanks, mak ___ 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]
sysctl options loader.conf or sysctl.conf
I'm a bit confused about whcih options needs to be set where. I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. I read something about vfs.read_max=16 - where do I set this I wonder? Is there info about this somewhere? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
dick hoogendijk [EMAIL PROTECTED] writes: I'm a bit confused about whcih options needs to be set where. You're not alone. I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. Well, sysctl(8) refers to loader.conf(5), sysctl.conf(5), loader(8), which refer to /boot/defaults/loader.conf /etc/sysctl.conf and don't forget the handboot and FAQ. I read something about vfs.read_max=16 - where do I set this I wonder? Since sysctl.conf is read in only when going multi-user and that sounds like something you'd want always, I'd put it in loader.conf. Is there info about this somewhere? Google? If you think it's needed, please write a PR (probably on /boot/default/loader.conf). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
On Aug 3, 2005, at 11:21 AM, dick hoogendijk wrote: I'm a bit confused about whcih options needs to be set where. This changes over time. A lot of options once needed to be set in the loader.conf before the kernel started up, but the system is getting more flexible and some of those can be changed at runtime now I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. I read something about vfs.read_max=16 - where do I set this I wonder? Is there info about this somewhere? Look at /boot/defaults/loader.conf, that ought to give you a good idea of what needs to be (or can be) set via that. Otherwise, try using sysctl to change things, and if they are marked read-only, then they needed to be changed earlier or by rebuilding the kernel with a different config. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
On Wed, 03 Aug 2005 10:48:04 -0700 [EMAIL PROTECTED] (Gary W. Swearingen) wrote: Since sysctl.conf is read in only when going multi-user and that sounds like something you'd want always, I'd put it in loader.conf. Not so. I tried /boot/loader.conf but vfs.read_max still was default after the booting process. Putting it in /etc/sysctl.conf worked. Confusing.. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Articles, Tutorials hardware setting in loader.conf
As a newbye I just need a pointer, a hint to the following two subjects: 1) Where can I find a clear explanationt on how to use the many, multilingual articles, books, tutorials and documentation coming with a standard 5.4 version (in sgml format). In a nutshell, how can I obtain a readable article or tutorial starting fron those files? 2) Trying to solve a problem with my touchpad mouse I had to add hw.psm.flags=0x100 into /boot/loader.conf. I tried hard googling to find a complete explanation on those commands that I understand prevent from rebuilding kernels with specific options, but I only met fragmentary stuff not a complete view on the subject. Have you anything to suggest? Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Articles, Tutorials hardware setting in loader.conf
On Tue, May 24, 2005 at 05:33:10PM +0200, [EMAIL PROTECTED] wrote: As a newbye I just need a pointer, a hint to the following two subjects: 1) Where can I find a clear explanationt on how to use the many, multilingual articles, books, tutorials and documentation coming with a standard 5.4 version (in sgml format). In a nutshell, how can I obtain a readable article or tutorial starting fron those files? Normally HTML and plain text formats of the italic translations are installed in /usr/share/doc/it_IT.ISO8859-15/. English docs can be found in /usr/share/doc/en_US.ISO8859-1/. 2) Trying to solve a problem with my touchpad mouse I had to add hw.psm.flags=0x100 into /boot/loader.conf. The meaning of the flags for the psm driver is explained in the psm manpage. Execute 'man psm' from the console or xterm. I tried hard googling to find a complete explanation on those commands that I understand prevent from rebuilding kernels with specific options, but I only met fragmentary stuff not a complete view on the subject. Have you anything to suggest? The so-called sysctl above as nothing to do with recompiling the kernel. It is just one of the many kernel parameters that can be changed without recompiling the kernel. See 'man sysctl'. HTH, Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpyZqn7WK4jX.pgp Description: PGP signature
Re: Articles, Tutorials hardware setting in loader.conf
[EMAIL PROTECTED] wrote: As a newbye I just need a pointer, a hint to the following two subjects: 1) Where can I find a clear explanationt on how to use the many, multilingual articles, books, tutorials and documentation coming with a standard 5.4 version (in sgml format). In a nutshell, how can I obtain a readable article or tutorial starting fron those files? Short answer: the handbooks, articles, and other things are generally found on http://www.freebsd.org/ (and its mirrors) in HTML for your ready access. The site search feature isn't ideal IMHO, but judicious use of it can turn up the article(s) you need in the language you prefer. Lots of pre-generated HTML is also in /usr/share/doc/en, though it may fall out of date compared to the web site. Long answer (if you really have your heart set on generating documents from the raw SGML): Read all about the Documentation Project and its Primer. http://www.freebsd.org/docproj/ http://www.freebsd.org/docproj/sgml.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html (Also in /usr/share/doc/en/fdp-primer on your local system) Install ports/textproc/docproj 2) Trying to solve a problem with my touchpad mouse I had to add hw.psm.flags=0x100 into /boot/loader.conf. I tried hard googling to find a complete explanation on those commands that I understand prevent from rebuilding kernels with specific options, but I only met fragmentary stuff not a complete view on the subject. Have you anything to suggest? Sorry, not my field. For best results, it is recommended that you not ask two unrelated questions in one post. If no one jumps on this one, try again. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable loader.conf when booting? Can't boot because of it ..
On Thursday 31 March 2005 08:36 am, Daniel Johansson wrote: Hi, I really need some help here. I'm running a raid0, with vinum, and read the errata about adding geom_vinum_load=YES to loader.conf because vinim_start=YES in rc.conf paniced my system when booting. I'm running 5.3-RELEASE and the errata mentioned that one too. So I added gvinum to loader.conf and now I can't boot. All I get is a lot of scrolling text that says something about gvinum error, can't remember the exact message but it can't boot anyway. Tried single mode to delete this line but can't boot into single mode either. Tried disable-module geom_vinum in the loader but that didn't help either. It loaded the module anyway. So I'm really desperate here .. is there any way to tell my system to completly ignore loader.conf when booting so that I at least can access the system and edit loader.conf? Please CC to me if you reply. I'm not sure if you can disable loader.conf during boot (would be a cool thing to know, though). The only thing I know to do is boot from a live filesystem or from the install floppies and ttyv2(?) to get a shell. You can then mount your slices/partitions and comment the vinum_start line out. HTH, WizLayer Hi, Anyone have any other ideas I colleague of mine added a line to /boot/loader.conf I rebooted today after changing one of the boot-time variables (maximum data size) in /boot/loader.conf. I took it from 512MB to 2GB of RAM in order to improve the MySQL performance on the server. However, upon reboot, the following error comes up: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x58:0x8bc stack pointer = 0x10:0xf80 frame pointer = 0x10:0x0 code segment= base 0xc00f, limit 0x, type 0x1b = DPL 0, pres 1, def32 0, gran 0 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 9 panic: general protection fault cpuid = 0 Uptime: 1s 1) I tried resetting kern.maxdsiz backto 512MB by pressing 6 at the boot menu and doing: unset kern.maxdsiz set kern.maxdsiz=536870912 show kern.maxdsiz - this did not have any effect. 2) The above error message is not similar to ones reported by other users who set their maxdsiz too high. I have subsequently also tried to overwrite from the loader the memory variable to no effect I always get the above error and even going back to the original generic kernel does not help. We are running 5.4-RC4 on this machine. Just to make things worse the machine is in a remote data center so getting in a rebooting with a CD is possible but requires a long drive in :-) Is there any way to unset the settings placed in the /boot/loader.conf while in the interactive loader which is obviously loaded after /boot/loader.conf I assume there is no way to overwrite the /boot/loader.conf with a nul file? Any thoughts gratefully received. ALan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disable loader.conf when booting? Can't boot because of it ..
Hi, I really need some help here. I'm running a raid0, with vinum, and read the errata about adding geom_vinum_load=YES to loader.conf because vinim_start=YES in rc.conf paniced my system when booting. I'm running 5.3-RELEASE and the errata mentioned that one too. So I added gvinum to loader.conf and now I can't boot. All I get is a lot of scrolling text that says something about gvinum error, can't remember the exact message but it can't boot anyway. Tried single mode to delete this line but can't boot into single mode either. Tried disable-module geom_vinum in the loader but that didn't help either. It loaded the module anyway. So I'm really desperate here .. is there any way to tell my system to completly ignore loader.conf when booting so that I at least can access the system and edit loader.conf? Please CC to me if you reply. -- Daniel Johansson - [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: Disable loader.conf when booting? Can't boot because of it ..
On Thursday 31 March 2005 08:36 am, Daniel Johansson wrote: Hi, I really need some help here. I'm running a raid0, with vinum, and read the errata about adding geom_vinum_load=YES to loader.conf because vinim_start=YES in rc.conf paniced my system when booting. I'm running 5.3-RELEASE and the errata mentioned that one too. So I added gvinum to loader.conf and now I can't boot. All I get is a lot of scrolling text that says something about gvinum error, can't remember the exact message but it can't boot anyway. Tried single mode to delete this line but can't boot into single mode either. Tried disable-module geom_vinum in the loader but that didn't help either. It loaded the module anyway. So I'm really desperate here .. is there any way to tell my system to completly ignore loader.conf when booting so that I at least can access the system and edit loader.conf? Please CC to me if you reply. I'm not sure if you can disable loader.conf during boot (would be a cool thing to know, though). The only thing I know to do is boot from a live filesystem or from the install floppies and ttyv2(?) to get a shell. You can then mount your slices/partitions and comment the vinum_start line out. HTH, WizLayer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sound works with kldload, but not /boot/loader.conf?
Hi, I just tried playing a WAV file using xmms (this is the first time I've tried anything with sound on my installation). It issued a very generic error message, telling me things like make sure your device is installed. I did some research (mostly in the FreeBSD handbook), and eventually got my sound working by doing a kldload snd_driver. I then changed /boot/loader.conf to contain the line: snd_driver_load=YES So that I wouldn't have to kldload snd_driver every time. After rebooting, xmms acted like it was playing the song - no error message, equalizer lights happily jumping around, et cetera - but no sound came out. If I try kldload snd_driver at this point, it says that snd_driver is already loaded. If I comment out the line from /boot/loader.conf, reboot and do a kldload snd_driver, the sound works fine (as it did before). So, am I doing something wrong? Is there a way to get the /boot/loader.conf line to work? Is there anything else I could investigate? If it's just screwed up and that's all there is to it, could I just manually put kldload snd_driver into some automatic startup script? If so, what is the appropriate script? Thanks, Bob Vesterman. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound works with kldload, but not /boot/loader.conf?
On Sun, Dec 12, 2004 at 08:28:32PM -0500, Robert William Vesterman said: Hi, I just tried playing a WAV file using xmms (this is the first time I've tried anything with sound on my installation). It issued a very generic error message, telling me things like make sure your device is installed. I did some research (mostly in the FreeBSD handbook), and eventually got my sound working by doing a kldload snd_driver. I then changed /boot/loader.conf to contain the line: snd_driver_load=YES So that I wouldn't have to kldload snd_driver every time. After rebooting, xmms acted like it was playing the song - no error message, equalizer lights happily jumping around, et cetera - but no sound came out. You may need to adjust your mixer settings. Run 'mixer' and have a look at the output. You can modify any of the settings there by running, for example: mixer pcm 90 mixer vol 90 (for me to get any sound at all, I need to have both of these turned up). You can then store those settings somehow but I can't remember how to do that off the top of my head. -- Adam Smith Internode : http://www.internode.on.net Phone : (08) 8228 2999 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound works with kldload, but not /boot/loader.conf?
On Sun, Dec 12, 2004 at 05:39:02PM -0800, Michael C. Shultz said: I use /usr/local/etc/rc.d/START.sh taht conatins the following: echokldload snd_driver kldload snd_driver Or you could put it in your kernel, and then it would all work the way it's supposed to! -- Adam Smith Internode : http://www.internode.on.net Phone : (08) 8228 2999 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound works with kldload, but not /boot/loader.conf?
On Sunday 12 December 2004 08:10 pm, Adam Smith wrote: On Sun, Dec 12, 2004 at 05:39:02PM -0800, Michael C. Shultz said: I use /usr/local/etc/rc.d/START.sh taht conatins the following: echokldload snd_driver kldload snd_driver Or you could put it in your kernel, and then it would all work the way it's supposed to! For you mixer comment you can also add mixer vol 100:100 to usr/local/etc/rc.d/START.sh though there is probably a better way to do that as well. -Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound works with kldload, but not /boot/loader.conf?
On Sunday 12 December 2004 05:28 pm, Robert William Vesterman wrote: Hi, I just tried playing a WAV file using xmms (this is the first time I've tried anything with sound on my installation). It issued a very generic error message, telling me things like make sure your device is installed. I did some research (mostly in the FreeBSD handbook), and eventually got my sound working by doing a kldload snd_driver. I then changed /boot/loader.conf to contain the line: snd_driver_load=YES So that I wouldn't have to kldload snd_driver every time. After rebooting, xmms acted like it was playing the song - no error message, equalizer lights happily jumping around, et cetera - but no sound came out. If I try kldload snd_driver at this point, it says that snd_driver is already loaded. If I comment out the line from /boot/loader.conf, reboot and do a kldload snd_driver, the sound works fine (as it did before). So, am I doing something wrong? Is there a way to get the /boot/loader.conf line to work? Is there anything else I could investigate? If it's just screwed up and that's all there is to it, could I just manually put kldload snd_driver into some automatic startup script? If so, what is the appropriate script? Thanks, Bob Vesterman. I use /usr/local/etc/rc.d/START.sh taht conatins the following: echokldload snd_driver kldload snd_driver -Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/boot/loader.conf not fixing vinum issue
I have two vinum volumes on my system; one, a mirrored volume, is /usr, and the other is mounted to /usr/storage. After updating to 5.3-RELEASE, boot into multi-user mode fails with a dangling vnode panic. According to the Errata: (31 Oct 2004, updated on 12 Nov 2004) The vinum(4) subsystem works on 5.3, but it can cause a system panic at boot time. As a workaround you can add vinum_load=YES to /boot/loader.conf. So I did that. And it doesn't fix it. Using gvinum seems like a really bad idea at the moment, given that it's only about half-done. What should I try next? Thanks! --Mac -- Julian Mac Mason[EMAIL PROTECTED] Computer Science '06 (909)-607-3129 Harvey Mudd College ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Vinum-devel] loader.conf variables for vinum
[EMAIL PROTECTED] with FreeBSD 4.x] As Bob Van Valzazh wrote: Short answer: don't set vinum.autostart Long answers: 5.x contains code to discover all attached disk drives whereas 4.x does not. Hence 4.x needs to be told were to look for disks (that's the vinum.drives setting). Vinum.autostart just tells 5.x to run the discovery code. Addition: the code to parse the name of the root device in 4.x is too narrow-minded to parse a string like /dev/vinum/root, it can only parse [/dev/]DDU[sS]P-style root device names (DD - driver name, U - unit number, sS - slice number, P - partition letter). Thus you need to set the vinum.root variable so the vinum subsystem pre-determines the name of the root device, and the parser for the root device name will be bypassed. FreeBSD 5.x contains a much more flexible parser for the root device name, which allows each subsystem to place hooks into it, and try translating a name like /dev/vinum/root into the respective major/minor device number. That's why vinum.root is no longer needed under 5.x either. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
loader.conf variables for vinum
Dear list, I am using 4.10R and want to set up a mirrored / using vinum. I am confused by the note in section 17.9.1 of the handbook stating that the following paragraphs only apply to 5.x and refer to 17.9.5 for 4.x configuration. Do I have to set just vinum_load, vinum.drives, and vinum.root in 4.x? Or do I have to set vinum.autoload, too? TIA Zheyu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Vinum-devel] loader.conf variables for vinum
Short answer: don't set vinum.autostart Long answers: 5.x contains code to discover all attached disk drives whereas 4.x does not. Hence 4.x needs to be told were to look for disks (that's the vinum.drives setting). Vinum.autostart just tells 5.x to run the discovery code. Bob On Thu, 2004-09-02 at 02:34, FreeBSD Daemon wrote: Dear list, I am using 4.10R and want to set up a mirrored / using vinum. I am confused by the note in section 17.9.1 of the handbook stating that the following paragraphs only apply to 5.x and refer to 17.9.5 for 4.x configuration. Do I have to set just vinum_load, vinum.drives, and vinum.root in 4.x? Or do I have to set vinum.autoload, too? TIA Zheyu ___ Vinum-devel mailing list [EMAIL PROTECTED] http://www.auug.org.au/mailman/listinfo/vinum-devel Hosted by AUUG (http://www.auug.org.au/). Join AUUG at http://www.auug.org.au/info#join. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Corrupted 'loader.conf' file
Hi Has anyone noticed that the '/boot/defaults/loader.conf' on '5.2.1-RELEASE-i386-disc1.iso' is corrupted ? At the some moment It doesnt look like the *.iso itself got corrupted. I've downloaded that from www.bigpond.com.au site. Sincelery Henry __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
