Re: kernel configuration file
Bernt Hansson b...@bananmonarki.se wrote: 2012-05-06 20:23, Robert Bonomi skrev: Including *every* loadable module, whether or not you actually use it. That's not really true, at least not for me, and I have not made any changes to the build environment. The loadable module that I actually use is bktr.ko, that one among others does not get built. I'd guess that bktr.ko is a 'third-party' module, found in a port, and not part of the base system. I found that every loadable kernel module in the base system is, or at least was, rebuilt. I haven't used make buildkernel in several years -- I use a 'monolithic' kernel, with everything compiled in, and loadable modules disabled. That way I always know _exactly_ what cabilities exist, and what security holes I _don't_ have to worry about. ___ 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: kernel configuration file
On Mon, 7 May 2012 15:01:31 -0500 (CDT), Robert Bonomi wrote: Bernt Hansson b...@bananmonarki.se wrote: 2012-05-06 20:23, Robert Bonomi skrev: Including *every* loadable module, whether or not you actually use it. That's not really true, at least not for me, and I have not made any changes to the build environment. The loadable module that I actually use is bktr.ko, that one among others does not get built. I'd guess that bktr.ko is a 'third-party' module, found in a port, and not part of the base system. No, it's part of the base system. I've been using bktr _in_ kernel for many years (FreeBSD 5 and 7), but since 8.0, it does not build anymore. However, the module _does_ correctly build. The documentation is in man 4 bktr. A typical use (with the PAL option, because I don't have Never The Same Color here), did work in the past like this: device bktr options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL options BKTR_USE_PLL options BKTR_GPIO_ACCESS options BKTR_USE_FREEBSD_SMBUS Today, I need to use /boot/loader.conf with those entry bktr_load=YES Works for my Haupauge WinTV PCI video + tuner card, even the options (PAL) seem to magically work! :-) I found that every loadable kernel module in the base system is, or at least was, rebuilt. That's correct so far. Additionally, all components specified by the kernel configuration file will be rebuilt, which in case of _no_ alteration is the content of GENERIC. As I said, there may be parts that one can safely drop (e. g. WLAN, floppy, ISDN or sound for a server). -- 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
kernel configuration file
In the Generic kernel configuration file for FreeBSD/amd64, if I do not have a floppy drive, is it safe to comment out this entry? # Floppy drives device fdc Are there any other entries that I could eliminate if I do not have a floppy drive? Also, according the the webcamd documentation, I need to have this in the loader.conf file. webcamd requires the cuse4bsd(3) kernel module. To load the driver as a module at boot time, place the following line in loader.conf(5): cuse4bsd_load=YES Is there a way that I can simply compile it into the kernel? Would a: device cuse4bsd# Required by webcamd entry in the kernel file work? I cannot find any documentation on that. -- Carmel ✌ carmel...@hotmail.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
Re: kernel configuration file
Carmel carmel...@hotmail.com wrote; In the Generic kernel configuration file for FreeBSD/amd64, if I do not have a floppy drive, is it safe to comment out this entry? # Floppy drives device fdc Definitely, yes. Are there any other entries that I could eliminate if I do not have a floppy drive? device atapifd obviouly. :) Also, according the the webcamd documentation, I need to have this in the loader.conf file. webcamd requires the cuse4bsd(3) kernel module. To load the driver as a module at boot time, place the following line in loader.conf(5): cuse4bsd_load=YES Is there a way that I can simply compile it into the kernel? Would a: device cuse4bsd# Required by webcamd entry in the kernel file work? I cannot find any documentation on that. The simplest approach for this is 'try it and find out'. If you use the traditional kernel-huild 'Configure/make depend/make' sequence, to rebuild the kernel -only-, its a matter of one minute or so on a _slow_ (486-class) machine. you'll either get a Configure error, a linker error, or it 'just works'. ___ 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: kernel configuration file
On Sun, 6 May 2012 08:08:31 -0500 (CDT) Robert Bonomi articulated: Carmel carmel...@hotmail.com wrote; In the Generic kernel configuration file for FreeBSD/amd64, if I do not have a floppy drive, is it safe to comment out this entry? # Floppy drives device fdc Definitely, yes. Are there any other entries that I could eliminate if I do not have a floppy drive? device atapifd obviouly. :) Thanks, I had not noticed that one. Also, according the the webcamd documentation, I need to have this in the loader.conf file. webcamd requires the cuse4bsd(3) kernel module. To load the driver as a module at boot time, place the following line in loader.conf(5): cuse4bsd_load=YES Is there a way that I can simply compile it into the kernel? Would a: device cuse4bsd# Required by webcamd entry in the kernel file work? I cannot find any documentation on that. The simplest approach for this is 'try it and find out'. If you use the traditional kernel-huild 'Configure/make depend/make' sequence, to rebuild the kernel -only-, its a matter of one minute or so on a _slow_ (486-class) machine. you'll either get a Configure error, a linker error, or it 'just works'. OK, now you lost me. I use the following basic sequence: make buildworld make buildkernel KERNCONF=CARMEL make installkernel KERNCONF=CARMEL make installworld I am sorry, but I am not fully comprehending what commands you want me to enter. -- Carmel ✌ carmel...@hotmail.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
Re: kernel configuration file
On Sunday 06 May 2012 10:34:12 Carmel wrote: On Sun, 6 May 2012 08:08:31 -0500 (CDT) Robert Bonomi articulated: Carmel carmel...@hotmail.com wrote; In the Generic kernel configuration file for FreeBSD/amd64, if I do not have a floppy drive, is it safe to comment out this entry? # Floppy drives device fdc Definitely, yes. Are there any other entries that I could eliminate if I do not have a floppy drive? device atapifd obviouly. :) Thanks, I had not noticed that one. Also, according the the webcamd documentation, I need to have this in the loader.conf file. webcamd requires the cuse4bsd(3) kernel module. To load the driver as a module at boot time, place the following line in loader.conf(5): cuse4bsd_load=YES Is there a way that I can simply compile it into the kernel? Would a: device cuse4bsd# Required by webcamd entry in the kernel file work? I cannot find any documentation on that. The simplest approach for this is 'try it and find out'. If you use the traditional kernel-huild 'Configure/make depend/make' sequence, to rebuild the kernel -only-, its a matter of one minute or so on a _slow_ (486-class) machine. you'll either get a Configure error, a linker error, or it 'just works'. OK, now you lost me. I use the following basic sequence: make buildworld make buildkernel KERNCONF=CARMEL make installkernel KERNCONF=CARMEL make installworld I am sorry, but I am not fully comprehending what commands you want me to enter. Carmel; You don't need to build the whole world if you only need a kernel rebuild. just edit your kernel file and issue: cd /usr/src make kernel KERNCONF=CARMEL the 2nd line builds AND installs the new kernel. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: kernel configuration file
On 06/05/2012 14:34, Carmel wrote: Is there a way that I can simply compile it into the kernel? Would a: device cuse4bsd# Required by webcamd entry in the kernel file work? I cannot find any documentation on that. cuse4bsd is a third party module. This means that the sources aren't available as part of the base system, so making work as compiled-in code in the kernel will require you to create patches for your kernel source tree. Not impossible, but not trivial either. I don't know if hps@ has any plans to import it into the base system (I doubt it though), but it would only appear a few releases down the line even if he did. OK, now you lost me. I use the following basic sequence: make buildworld make buildkernel KERNCONF=CARMEL make installkernel KERNCONF=CARMEL make installworld I am sorry, but I am not fully comprehending what commands you want me to enter. If you don't update the system sources, then you can try a new kernel config without rebuilding world all the time. Like so: make buildkernel KERNCONF=CARMEL make installkernel KERNCONF=CARMEL shutdown -r now Just (re)building the kernel takes a lot less time than rebuilding the entire base system. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: kernel configuration file
On Sun, 06 May 2012 14:58:39 +0100 Matthew Seaman articulated: cuse4bsd is a third party module. This means that the sources aren't available as part of the base system, so making work as compiled-in code in the kernel will require you to create patches for your kernel source tree. Not impossible, but not trivial either. I don't know if hps@ has any plans to import it into the base system (I doubt it though), but it would only appear a few releases down the line even if he did. Thanks Matthew, that answered my question. It would seem that importing that module in the base system would be a wise idea; however, that decision is not mine to make. -- Carmel ✌ carmel...@hotmail.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
Re: kernel configuration file
From owner-freebsd-questi...@freebsd.org Sun May 6 08:36:52 2012
Date: Sun, 6 May 2012 09:34:12 -0400
From: Carmel carmel...@hotmail.com
To: FreeBSD freebsd-questions@freebsd.org
Subject: Re: kernel configuration file
On Sun, 6 May 2012 08:08:31 -0500 (CDT)
Robert Bonomi articulated:
If you use the traditional kernel-huild 'Configure/make depend/make'
sequence, to rebuild the kernel -only-, its a matter of one minute or
so on a _slow_ (486-class) machine.
you'll either get a Configure error, a linker error, or it 'just
works'.
OK, now you lost me. I use the following basic sequence:
make buildworld
make buildkernel KERNCONF=CARMEL
make installkernel KERNCONF=CARMEL
make installworld
I am sorry, but I am not fully comprehending what commands you want me
to enter.
That's the 'modern' way.
Note: make buildkernel forcibly rebuilds everything, *EVERY* time.
Including *every* loadable module, whether or not you actually use it.
Which can be *really* painful on slow hardware (like 20+ *hours*, on a
486-class machine).
The 'traditional' custom kernel-construction sequence is:
cd /sys/{architecture}/conf
$EDIT {kernelname}C
config {kernelname}
cd ../../compile/{kernelname}
make depend
make
Then, 'make install', to install it as the defalt kernel to boot from,
or copy it to /boot/kernel/{foo} if you just want to test it by manually
selecting it at boot time..
For 'minor' kernel-only changes -- _I_ use custom kernels with =everything=
I need 'compiled in', *no* loadable modules, I'm in no mood to wait for all
the never used modules to be re-built -- The 'traditional' method is
_far_ faster. On a 700 mhz PIII, it is circa 90 seconds when I make a
simple configuration change -- e.g., add a 'device', change an 'option',
change a 'value'. *MOST* of which is the 'make depend' stage. the actual
'make' is under 10 seconds on _that_ hardware.
'make buildkernel' always works for every configuration. It does it by
being extremely pessimistic about what needs to be re-built. i.e., it
=always= assumes everything is out-of-date. This subverts one of the major
reasons 'make' exists -- to rebuild only the -minimal- set of things that
are affected by a given set of changes. It is 'foolproof', but the
skilled kernel builder pays an *incredible* performance penalty for
using something that attemptss to outwit the classical 'sufficiently
determined fool'.
I don't object (well, 'much', that is, see below) to 'make buildkernel',
or even to it being promoted in the Handbook as the 'preferred' means of
kernel building. It _really_ annoys that it is listed therein as the
-only- way. The 'traditional' methodology is fast becoming 'lost art',
along with the related knowledge of _how_ the process works,
'make buildkernel' is a black box, reminiscent of MS Windows 'magic'.
When it works, all is fine. when it breaks, you've got essentially no
information to work with about 'what went wrong'.
With the 'traditional' method, at least all the commands have manpages,
that tell you -what- each command does, in a fair amount of detail.
/rant
___
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: kernel configuration file
On Sun, 6 May 2012 13:23:08 -0500 (CDT), Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Sun May 6 08:36:52 2012 Date: Sun, 6 May 2012 09:34:12 -0400 From: Carmel carmel...@hotmail.com To: FreeBSD freebsd-questions@freebsd.org Subject: Re: kernel configuration file On Sun, 6 May 2012 08:08:31 -0500 (CDT) Robert Bonomi articulated: If you use the traditional kernel-huild 'Configure/make depend/make' sequence, to rebuild the kernel -only-, its a matter of one minute or so on a _slow_ (486-class) machine. you'll either get a Configure error, a linker error, or it 'just works'. OK, now you lost me. I use the following basic sequence: make buildworld make buildkernel KERNCONF=CARMEL make installkernel KERNCONF=CARMEL make installworld I am sorry, but I am not fully comprehending what commands you want me to enter. That's the 'modern' way. The /usr/src/Makefile contains a comment header which explains the purpose of the make targets the current way supports. One should read it before starting, because it's quite informative on _that_ way of doing things (e. g. make kernel = make buildkernel installkernel). Note: make buildkernel forcibly rebuilds everything, *EVERY* time. Including *every* loadable module, whether or not you actually use it. Which can be *really* painful on slow hardware (like 20+ *hours*, on a 486-class machine). Maybe it's worth mentioning /etc/src.conf and /etc/make.conf and the man src.conf manpage. That is a comfortable means to avoid building (and therefore also installing) modules one does not need. The approach to configure all and _only_ the stuff I need in a custom kernel can be followed this way, and it will even work with the current make target way. Have no WLAN? So why bother building it? No ISDN? Omit it! For minor kernel changes (e. g. if you want to try some compile-time settings), this approach is really handy as it minimizes the time required. This consideration should _boost_ build+install times on current plentycore multiprocessors with tons of RAM! :-) -- 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
Missing kernel configuration file(s)
I have upgrade src to Revision: 234068 # cd /usr/src # make -j 8 buildkernel KERNCONF=KES_KERN_v10 ERROR: Missing kernel configuration file(s) (KES_KERN_v10). *** Error code 1 1 error *** Error code 2 1 error # cd /usr/src/sys/amd64/conf # ls .cvsignore GENERIC.hints Makefile DEFAULTSKESOPTS LINTNOTES GENERIC KES_KERN_v10LINT-VIMAGE XENHVM I always do this steps, but now I get errors. I can not find what was changed. How I must compile my kernel now? ___ 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: Missing kernel configuration file(s)
КЕ I have upgrade src to Revision: 234068 КЕ # cd /usr/src КЕ # make -j 8 buildkernel KERNCONF=KES_KERN_v10 КЕ ERROR: Missing kernel configuration file(s) (KES_KERN_v10). КЕ *** Error code 1 КЕ 1 error КЕ *** Error code 2 КЕ 1 error КЕ # cd /usr/src/sys/amd64/conf КЕ # ls КЕ .cvsignore GENERIC.hints Makefile КЕ DEFAULTSKESOPTS LINTNOTES КЕ GENERIC KES_KERN_v10LINT-VIMAGE XENHVM КЕ I always do this steps, but now I get errors. КЕ I can not find what was changed. КЕ How I must compile my kernel now? Foget, that I install freebsd from CD with i386 so I need make -j 8 buildkernel KERNCONF=KES_KERN_v10 TARGET=amd64 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
saving kernel configuration file into the kernel itself
I remember that in FreeBSD 4 there was a way to include configuration file in the kernel being compiled, but I could not remember what it was and I could not find it in the handbook. Is there such feature in FreeBSD 6 ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: saving kernel configuration file into the kernel itself
On Sat 31 Mar 2007 20:03, [EMAIL PROTECTED] wrote: I remember that in FreeBSD 4 there was a way to include configuration file in the kernel being compiled, but I could not remember what it was and I could not find it in the handbook. Is there such feature in FreeBSD 6 ? From /usr/src/sys/conf/NOTES : # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: #strings -n 3 /boot/kernel/kernel | sed -n 's/^___//p' MYKERNEL # options INCLUDE_CONFIG_FILE # Include this file in kernel Also check out /usr/src/sys/i386/conf/NOTES Replace i386 with your arch. -- Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel configuration file
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html where do i put this ? device sound i am using freebsd 5.3b7 Can you please at to the manual the path of the kernel configuration file thx Do i need to recompile the kernel ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration file
On Sat, Oct 23, 2004 at 06:09:56AM +0200, Gert Cuykens wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html where do i put this ? device sound i am using freebsd 5.3b7 The easier option is to put: snd_driver_load=YES in /boot/loader.conf. -- Jonathan Chen | To do is to be -- Nietzsche [EMAIL PROTECTED] | To be is to do -- Sartre | Scooby do be do -- Scooby ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration file
did that doesnt work for me ? asus SK8N onboard sound acl850 if i am not mistaken. On Sat, 23 Oct 2004 17:21:30 +1300, Jonathan Chen [EMAIL PROTECTED] wrote: On Sat, Oct 23, 2004 at 06:09:56AM +0200, Gert Cuykens wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html where do i put this ? device sound i am using freebsd 5.3b7 The easier option is to put: snd_driver_load=YES in /boot/loader.conf. -- Jonathan Chen | To do is to be -- Nietzsche [EMAIL PROTECTED] | To be is to do -- Sartre | Scooby do be do -- Scooby ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration file
[Please don't top post, it's really hard to read] On Sat, Oct 23, 2004 at 06:52:56AM +0200, Gert Cuykens wrote: i dont have any snd_*.ko files and the sound chip is suported by freebsd If you're running 5.3b7, they should be there; it comes with the default install. -- Jonathan Chen [EMAIL PROTECTED] -- When all else fails, RTFM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration file
i did custom install :P On Sat, 23 Oct 2004 18:12:20 +1300, Jonathan Chen [EMAIL PROTECTED] wrote: [Please don't top post, it's really hard to read] On Sat, Oct 23, 2004 at 06:52:56AM +0200, Gert Cuykens wrote: i dont have any snd_*.ko files and the sound chip is suported by freebsd If you're running 5.3b7, they should be there; it comes with the default install. -- Jonathan Chen [EMAIL PROTECTED] -- When all else fails, RTFM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration file
So i guess this mean kernel compilation from src ? Or can i install them separately ? On Sat, 23 Oct 2004 07:13:47 +0200, Gert Cuykens [EMAIL PROTECTED] wrote: i did custom install :P On Sat, 23 Oct 2004 18:12:20 +1300, Jonathan Chen [EMAIL PROTECTED] wrote: [Please don't top post, it's really hard to read] On Sat, Oct 23, 2004 at 06:52:56AM +0200, Gert Cuykens wrote: i dont have any snd_*.ko files and the sound chip is suported by freebsd If you're running 5.3b7, they should be there; it comes with the default install. -- Jonathan Chen [EMAIL PROTECTED] -- When all else fails, RTFM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
