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.
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
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
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
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
.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
.
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
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
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
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
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
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
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
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
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
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
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
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
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
:
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
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
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
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
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
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
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
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
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
-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-
-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
-
___
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
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
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
-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 -
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?
___
-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?
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
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
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
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
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
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
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
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
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
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
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
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
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
* 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
) 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
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
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
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
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
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
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
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
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
. 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
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
[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).
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
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,
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
95 matches
Mail list logo
