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
Building amd64 kernel problems (missing kernel configuration files)
Hello, I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64 kernel. I have copied /usr/src/sys/amd64/conf/GENERIC to /usr/src/sys/amd64/conf/JERRY Then, I run make buildkernel KERNCONF=JERRY in /usr/src and get the following error: ERROR: Missing kernel configuration file(s) (JERRY). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It seems to want JERRY to be in i386/conf. If I copy JERRY to i386/conf and run make buildkernel KERNCONF=JERRY, I get the following error: -- Kernel build for JERRY started on Wed Jun 9 20:50:30 EDT 2010 -- === JERRY mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/JERRY /usr/src/sys/i386/conf/JERRY /usr/src/sys/i386/conf/JERRY: unknown option HAMMER *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I know I'm missing something simple, but can't quite figure out what it is. Thanks, Jerry ___ 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: Building amd64 kernel problems (missing kernel configuration files)
On Wed, Jun 9, 2010 at 8:38 PM, Jerry Bell jerry.b...@gmail.com wrote: I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64 kernel. I have copied /usr/src/sys/amd64/conf/GENERIC to /usr/src/sys/amd64/conf/JERRY Then, I run make buildkernel KERNCONF=JERRY in /usr/src and get the following error: ERROR: Missing kernel configuration file(s) (JERRY). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It seems to want JERRY to be in i386/conf. If I copy JERRY to i386/conf and run make buildkernel KERNCONF=JERRY, I get the following error: -- Kernel build for JERRY started on Wed Jun 9 20:50:30 EDT 2010 -- === JERRY mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/JERRY /usr/src/sys/i386/conf/JERRY /usr/src/sys/i386/conf/JERRY: unknown option HAMMER *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I know I'm missing something simple, but can't quite figure out what it is. I think you have to set TARGET_ARCH=amd64 -- Adam Vande More ___ 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: Building amd64 kernel problems (missing kernel configuration files)
I am have a fresh install of FreeBSD 8.0 i386 and need to install an amd64 kernel. I have copied /usr/src/sys/amd64/conf/GENERIC to /usr/src/sys/amd64/conf/JERRY Support for cross-building is limited in the FreeBSD base system. /usr/src/Makefile states: # If TARGET=machine (e.g. ia64, sparc64, ...) is specified you can # cross build world for other machine types using the buildworld target, # and once the world is built you can cross build a kernel using the # buildkernel target. but there are unwritten limitations, and this requires some care. See, for example, developers running into problems even with i386 -- amd64: http://bsdimp.blogspot.com/2006/09/cross-building-freebsd.html The fact that you are asking how to do this on the freebsd-questions list probably means that you should _not_ be cross-building. _Don't_ try to run an amd64 kernel with i386 world, or vice versa. With some patches and tweaking you may get a few things to work, but you're asking for trouble. It would be better to get an amd64 installation disk, back up your data, and do a re-installation from scratch, or at least a binary upgrade of the existing base system, and then build a custom kernel and world, if that's what you want to do. b. ___ 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
Info on DOS mitigation, kernel configuration for DOS mitigation
Hello everyone! First of all i would like to apologize to anyone who finds my appeal a lazy man's choice, actually it's indeed lazy but it's the best way to get an answer from a valid source. My problem is a potential DOS/DDOS... i know a forever talked about issue... i've already searched the freebsd's mailing lists and found some mitigation techniques, to bad that google ain't that familiar with FreeBSD, and searchin' for guides is a pain... I recall finding a mitigation technique that involved bandwidth shaping and other ... I'm using a FreeBSD 7.2-p7 with ipfw and upon testing the rules in those guides it alerted me that bandwidth modules weren't included in the bsd's kernel... Anyway could anyone provide me with a good BSD walk trough for DOS mitigation and if needed kernel modules and kernel module integration, mabe other firewall (but with extended howto..) ... (basically anything regarded to floods) Thanks in advance! ___ 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: Info on DOS mitigation, kernel configuration for DOS mitigation
On Mon, Mar 15, 2010 at 2:50 PM, Bogdan Webb bog...@pgn.ro wrote: i've already searched the freebsd's mailing lists and found some mitigation techniques, to bad that google ain't that familiar with FreeBSD, and searchin' for guides is a pain... http://www.google.com/bsd -- Adam Vande More ___ 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: Info on DOS mitigation, kernel configuration for DOS mitigation
Bogdan Webb wrote: Hello everyone! First of all i would like to apologize to anyone who finds my appeal a lazy man's choice, actually it's indeed lazy but it's the best way to get an answer from a valid source. My problem is a potential DOS/DDOS... i know a forever talked about issue... i've already searched the freebsd's mailing lists and found some mitigation techniques, to bad that google ain't that familiar with FreeBSD, and searchin' for guides is a pain... I recall finding a mitigation technique that involved bandwidth shaping and other ... I'm using a FreeBSD 7.2-p7 with ipfw and upon testing the rules in those guides it alerted me that bandwidth modules weren't included in the bsd's kernel... Anyway could anyone provide me with a good BSD walk trough for DOS kldload dummynet, see loader.conf(5) mitigation and if needed kernel modules and kernel module integration, mabe other firewall (but with extended howto..) ... (basically anything regarded to floods) As you probably guess, a) this is a complex problem because one man's DOS is another's regular traffic - it's complex even to detect something like that, and b) most of the general solutions are not platform-specific but can apply to any operating system, so you can learn it from many sources. First, you need to define what your outgoing network connection is (e.g. 10 mbit/s) and then see what kinds of tradeoffs you are prepared to make to protect yourself. The general advice is: - read ipfw(5), especially sections on dummynet and the limit rule - study software like http://codee.pl/cband.html ___ 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 : freebsd-update with MYKERNEL kernel configuration
Hi again! During FreeBSD 7.1 installation, I made some changes to my BSD partitions. I didn't touch ad0s1h (/home), so there is still my data. Installation went good, but I see disk boot failure... error message when trying to boot OS. Using Fixit liveCD I see: #fdisk /dev/ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=119705 heads=16 sectors/track=255 (4080 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=119705 heads=16 sectors/track=255 (4080 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 209729457 (102406 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) start 209729520, size 10508400 (5131 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 The data for partition 3 is: sysid 15 (0x0f),(Extended DOS (LBA)) start 220237920, size 268153200 (130934 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 The data for partition 4 is: UNUSED #bsdlabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 1048576 63 4.2BSD 1024 8192 46248 b: 2097152 1048639 swap c: 209729457 63 unused 0 0 # raw part, don't edit d: 1048576 3145791 4.2BSD 1024 8192 46248 e: 20230144 4194367 4.2BSD 1024 8192 46248 f: 2097152 24424511 4.2BSD 512 4096 22424 g: 4194304 26521663 4.2BSD 8192 65536 8 h: 179013553 30715967 4.2BSD 0 0 0 partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition h: partition extends past end of unit So, slice ad0s1 is active, partitions can be mounted and viewed, all seems OK. boot0cfg -B /dev/ad0 and fdisk -B /dev/ad0 doesn't solve the problem. What did I mess? What does the last strings of bsdlabel output mean? How do I manage this? Thank's in advance for any advice. 2009/11/27 S4mmael s4mm...@gmail.com: Thank you. 2009/11/26 Alexandre L. axel...@ymail.com: Hi, I paste this link where Colin Percival explain who to use the tool freebsd-update with custom kernel. But I think that same thing as been written in the handbook. http://forums.freebsd.org/showpost.php?p=30920postcount=9 --- En date de : Jeu 26.11.09, S4mmael s4mm...@gmail.com a écrit : De: S4mmael s4mm...@gmail.com Objet: freebsd-update with MYKERNEL kernel configuration À: freebsd-questions@freebsd.org Date: Jeudi 26 Novembre 2009, 13h32 Hi all! I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 - FreeBSD 8.0-RELESE with freebsd-update(8). First of all I made a copy of the most configuration files. Then I made: # freebsd-update -r 8.0-RELEASE upgrade All went good, except the message, that because of MYKERNEL kernel configuration I should upgrade my kernel before freebsd-upgrade install. Then I was looking for the way of kernel upgrade, but found nothing. How could I build 8.0 kernel in FreeBSD 7.2? Of course, there were 7.2 sources in /usr/src and I didn't find any sources in /var/db/freebsd-update/. It's the first my question. Thus I decided to upgrade all except the kernel and then rebuild the kernel (that worked good while upgrading 7.1 - 7.2). I made as mentioned in hanbook: # freebsd-upgrade install # shutdown -r now # freebsd-upgrade install There were many errors bad sistem call on th last command. After all I discovered that much files from / were lost (I didn't find any grep, bzcat and so on). On boot kernel can't find fsck_ufs, so automatic mounting fails. If mounted by hand, there is no way to login because of some init error. Single user mode works. freebsd-update roolback can't find any backup. Shell scripts can't find test (it really doesn't exists in /bin/[ ) and fails. How can I restore the system? I've FreeBSD 7.1 CD. Thank's in advance for your help. ___ 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
freebsd-update with MYKERNEL kernel configuration
Hi all! I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 - FreeBSD 8.0-RELESE with freebsd-update(8). First of all I made a copy of the most configuration files. Then I made: # freebsd-update -r 8.0-RELEASE upgrade All went good, except the message, that because of MYKERNEL kernel configuration I should upgrade my kernel before freebsd-upgrade install. Then I was looking for the way of kernel upgrade, but found nothing. How could I build 8.0 kernel in FreeBSD 7.2? Of course, there were 7.2 sources in /usr/src and I didn't find any sources in /var/db/freebsd-update/. It's the first my question. Thus I decided to upgrade all except the kernel and then rebuild the kernel (that worked good while upgrading 7.1 - 7.2). I made as mentioned in hanbook: # freebsd-upgrade install # shutdown -r now # freebsd-upgrade install There were many errors bad sistem call on th last command. After all I discovered that much files from / were lost (I didn't find any grep, bzcat and so on). On boot kernel can't find fsck_ufs, so automatic mounting fails. If mounted by hand, there is no way to login because of some init error. Single user mode works. freebsd-update roolback can't find any backup. Shell scripts can't find test (it really doesn't exists in /bin/[ ) and fails. How can I restore the system? I've FreeBSD 7.1 CD. Thank's in advance for your help. ___ 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: freebsd-update with MYKERNEL kernel configuration
On Thursday 26 November 2009 14:32:01 S4mmael wrote: Hi all! I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 - FreeBSD 8.0-RELESE with freebsd-update(8). First of all I made a copy of the most configuration files. Then I made: # freebsd-update -r 8.0-RELEASE upgrade All went good, except the message, that because of MYKERNEL kernel configuration I should upgrade my kernel before freebsd-upgrade install. That message should probably be more strongly worded. It is absolutely *imperative* that the custom kernel is upgraded before continuing with freebsd-upgrade install. For more information about how to upgrade to freebsd 8 see http://www.freebsd.org/doc/en/books/handbook/updating-upgrading- freebsdupdate.html Then I was looking for the way of kernel upgrade, but found nothing. How could I build 8.0 kernel in FreeBSD 7.2? Of course, there were 7.2 sources in /usr/src and I didn't find any sources in /var/db/freebsd-update/. It's the first my question. Use csup(1) to upgrade the sources to RELENG_8_0. Thus I decided to upgrade all except the kernel and then rebuild the kernel (that worked good while upgrading 7.1 - 7.2). As you found out, you should never do that. Always make sure the kernel is the same or newer as world (userland) especially when upgrading to a new major version. I made as mentioned in hanbook: # freebsd-upgrade install # shutdown -r now # freebsd-upgrade install At this point most userland utilities (because they all use libc.so) depend on features only available in the 8.0 kernel, while the installed kernel is still at 7.1. Essentially the system is bricked. There were many errors bad sistem call on th last command. After all I discovered that much files from / were lost (I didn't find any grep, bzcat and so on). On boot kernel can't find fsck_ufs, so automatic mounting fails. If mounted by hand, there is no way to login because of some init error. Single user mode works. freebsd-update roolback can't find any backup. Shell scripts can't find test (it really doesn't exists in /bin/[ ) and fails. How can I restore the system? I've FreeBSD 7.1 CD. You can try reinstalling 7.1 taking care not to repartition the HDD. If all went well the system runs a GENERIC kernel, which is upgradeable by freebsd- upgrade. You can then retry the upgrade process. This process (the reinstall from cdrom) will revert any changes to /etc, so you will need to restore that from backup. Perhaps others know a better/easier way. Thank's in advance for your help. Good luck! -- Pieter de Goeje ___ 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 : freebsd-update with MYKERNEL kernel configuration
Hi, I paste this link where Colin Percival explain who to use the tool freebsd-update with custom kernel. But I think that same thing as been written in the handbook. http://forums.freebsd.org/showpost.php?p=30920postcount=9 --- En date de : Jeu 26.11.09, S4mmael s4mm...@gmail.com a écrit : De: S4mmael s4mm...@gmail.com Objet: freebsd-update with MYKERNEL kernel configuration À: freebsd-questions@freebsd.org Date: Jeudi 26 Novembre 2009, 13h32 Hi all! I've got a problem while upgrading FreeBSD 7.2-RELEASE-p3 - FreeBSD 8.0-RELESE with freebsd-update(8). First of all I made a copy of the most configuration files. Then I made: # freebsd-update -r 8.0-RELEASE upgrade All went good, except the message, that because of MYKERNEL kernel configuration I should upgrade my kernel before freebsd-upgrade install. Then I was looking for the way of kernel upgrade, but found nothing. How could I build 8.0 kernel in FreeBSD 7.2? Of course, there were 7.2 sources in /usr/src and I didn't find any sources in /var/db/freebsd-update/. It's the first my question. Thus I decided to upgrade all except the kernel and then rebuild the kernel (that worked good while upgrading 7.1 - 7.2). I made as mentioned in hanbook: # freebsd-upgrade install # shutdown -r now # freebsd-upgrade install There were many errors bad sistem call on th last command. After all I discovered that much files from / were lost (I didn't find any grep, bzcat and so on). On boot kernel can't find fsck_ufs, so automatic mounting fails. If mounted by hand, there is no way to login because of some init error. Single user mode works. freebsd-update roolback can't find any backup. Shell scripts can't find test (it really doesn't exists in /bin/[ ) and fails. How can I restore the system? I've FreeBSD 7.1 CD. Thank's in advance for your help. ___ 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: kernel configuration
Chuck Swiger wrote: [snip] While it is true that you can comment out all but i686 and get a working kernel, you will experience reduced performance. There are a number of low-level assembly routines (cf sys/i386/i386/support.s such as i586_bcopy) that are conditionalized off of I586_CPU only, even though they provide an advantage on i686 platforms also. Thank you very kindly for this info tidbit. In my ignorance I had routinely built my kernels with only I686_CPU. Since the few boxen I have are all downlevel every niche I can squeak out some performance is sought after. Thanks indeed! -Mike ___ 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
In the last episode (Jan 15), Michael Powell said: Chuck Swiger wrote: While it is true that you can comment out all but i686 and get a working kernel, you will experience reduced performance. There are a number of low-level assembly routines (cf sys/i386/i386/support.s such as i586_bcopy) that are conditionalized off of I586_CPU only, even though they provide an advantage on i686 platforms also. Thank you very kindly for this info tidbit. In my ignorance I had routinely built my kernels with only I686_CPU. Since the few boxen I have are all downlevel every niche I can squeak out some performance is sought after. Thanks indeed! Actually, those functions are only enabled if the CPU is truly a 586-class processor. See /sys/i386/isa/npx.c , the npx_attach() function. There is a test for cpu_class==CPUCLASS_586, while most modern CPUs are CPUCLASS_686. -- 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
Re: kernel configuration
On Jan 15, 2009, at 11:31 AM, Dan Nelson wrote: Actually, those functions are only enabled if the CPU is truly a 586-class processor. See /sys/i386/isa/npx.c , the npx_attach() function. There is a test for cpu_class==CPUCLASS_586, while most modern CPUs are CPUCLASS_686. Thanks for the additional feedback, Dan. I remember some weirdness around things like the VIA C3 Centaur processors, which had CMOV feature and claimed to be a 686, but lacked SSE...not that those were an especially common case, but I still have one floating around. I see 686- and SSE2-optimized pagezero routines in support.s, but I don't see equivalents for bzero, bcopy, and copyin/copyout. Is something like generic_bzero() faster on a 686-class CPU than i586_bzero() would be? Regards, -- -Chuck ___ 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
hello, i am going through the kernel configuration file to build a custom kernel and am not quite sure i understand this part correctly. my cpu is an athlon 64 x2 but i am running i386, so i am assuming that in the config file i state that my cpu is i386, not athlon 64. i ran frebsd amd64 previously, and it had HAMMER i think as the cpu in the config file. this i386 version has cpu I486_CPU cpu I586_CPU cpu I686_CPU Is this correct, and do i need all three? 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: kernel configuration
On Wed, Jan 14, 2009 at 04:37:53PM +0100, icemaca wrote: this i386 version has cpu I486_CPU cpu I586_CPU cpu I686_CPU Basically you can comment all but I686_CPU since the others are for earlier x86 architectures. -ewald ___ 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
On Jan 14, 2009, at 10:15 AM, Ewald Jenisch wrote: On Wed, Jan 14, 2009 at 04:37:53PM +0100, icemaca wrote: this i386 version has cpu I486_CPU cpu I586_CPU cpu I686_CPU Basically you can comment all but I686_CPU since the others are for earlier x86 architectures. While it is true that you can comment out all but i686 and get a working kernel, you will experience reduced performance. There are a number of low-level assembly routines (cf sys/i386/i386/support.s such as i586_bcopy) that are conditionalized off of I586_CPU only, even though they provide an advantage on i686 platforms also. -- -Chuck ___ 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
On Wed, Jan 14, 2009 at 9:18 PM, Chuck Swiger cswi...@mac.com wrote: On Jan 14, 2009, at 10:15 AM, Ewald Jenisch wrote: On Wed, Jan 14, 2009 at 04:37:53PM +0100, icemaca wrote: this i386 version has cpu I486_CPU cpu I586_CPU cpu I686_CPU Basically you can comment all but I686_CPU since the others are for earlier x86 architectures. While it is true that you can comment out all but i686 and get a working kernel, you will experience reduced performance. There are a number of low-level assembly routines (cf sys/i386/i386/support.s such as i586_bcopy) that are conditionalized off of I586_CPU only, even though they provide an advantage on i686 platforms also. -- -Chuck so in any case it doesn't hurt to leave all 3. right? I have one last question though, is makeoptions DEBUG=g necessary if i am not debugging or is it always necessary to build the kernel properly? can i safely comment it out? ___ 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
On Jan 14, 2009, at 12:44 PM, t-u-t wrote: While it is true that you can comment out all but i686 and get a working kernel, you will experience reduced performance. There are a number of low-level assembly routines (cf sys/i386/i386/support.s such as i586_bcopy) that are conditionalized off of I586_CPU only, even though they provide an advantage on i686 platforms also. -- -Chuck so in any case it doesn't hurt to leave all 3. right? Certainly it doesn't hurt. As far as I can tell, leaving 486 option increases the kernel size (very) slightly but there doesn't seem to be many things optimized for 486 which don't have better equivalents coded for 586 or 686. Leaving out the 586 option would not be desirable AFAICT I have one last question though, is makeoptions DEBUG=g necessary if i am not debugging or is it always necessary to build the kernel properly? can i safely comment it out? It can be commented out safely, yes. Regards, -- -Chuck ___ 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 files
I had such mistake several days ago. In my case the reson was that I forgot that I`m usin amd64 arch, and I placed config to /usr/src/sys/i386/conf, but the right place was /usr/src/sys/amd64/conf PS: Ну если не говоришь ты хорошо по английски, то хоть не позорь родной союз :-). Тему письма надо указывать. JSCB Alokabank пишет: Please help me I'am beginer in FreeBSD I try to rebuild kernel files for optimizations system. Whate i gona do? sorry but i dont speake englash language wery well. look to include files this is my build kernel. I'am talk on russian. make buildkernel KERNCONF=KERNEL ERROR: Missing kernel configuration file(s) (KERNEL) *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src # Лидер бывает только один - UzNet www.uznet.net ___ 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: Missing kernel configuration files
I had such mistake several days ago. In my case the reson was that I forgot that I`m usin amd64 arch, and I placed config to /usr/src/sys/i386/conf, but the right place was /usr/src/sys/amd64/conf PS: Ну если не говоришь ты хорошо по английски, то хоть не позорь родной союз :-). Тему письма надо указывать. JSCB Alokabank пишет: Please help me I'am beginer in FreeBSD I try to rebuild kernel files for optimizations system. Whate i gona do? sorry but i dont speake englash language wery well. look to include files this is my build kernel. I'am talk on russian. make buildkernel KERNCONF=KERNEL ERROR: Missing kernel configuration file(s) (KERNEL) *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src # Лидер бывает только один - UzNet www.uznet.net ___ 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: kernel configuration failure
coriolinus wrote: I'm new to kernel building, so I followed the handbook's advice: cd to /usr/src, then make buildkernel KERNCONF=MYKERNEL. The kernel build process is failing mysteriously. The file it claims not to be able to find, /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c, is sitting in my filesystem exactly where it should be. I'm not even sure why exactly it's trying to build that, as I'm pretty sure that I disabled the modules in the kernel configuration file which use that source. Actually, that's not the problem. The file which is not found is the compiler itself: gcc34:No such file or directory Maybe you've installed gcc 4.3 from ports, linked /usr/bin/cc to /usr/local/bin/gcc43 and then upgrade gcc? Any help getting this to work would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: kernel configuration failure
Actually, that's not the problem. The file which is not found is the compiler itself: gcc34:No such file or directory Maybe you've installed gcc 4.3 from ports, linked /usr/bin/cc to /usr/local/bin/gcc43 and then upgrade gcc? That doesn't seem right: [EMAIL PROTECTED] /usr/src]$ which gcc34 /usr/local/bin/gcc34 [EMAIL PROTECTED] /usr/src]$ su Password: [EMAIL PROTECTED] /usr/src]# which gcc34 /usr/local/bin/gcc34 It's true that I installed gcc 3.4 from ports and put a line in /etc/make.conf: CC=gcc34 . However, it's on the path for both my user and for root; it seems weird that the makefile would lose track of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration failure
coriolinus wrote: Actually, that's not the problem. The file which is not found is the compiler itself: gcc34:No such file or directory Maybe you've installed gcc 4.3 from ports, linked /usr/bin/cc to /usr/local/bin/gcc43 and then upgrade gcc? That doesn't seem right: [EMAIL PROTECTED] /usr/src]$ which gcc34 /usr/local/bin/gcc34 [EMAIL PROTECTED] /usr/src]$ su Password: [EMAIL PROTECTED] /usr/src]# which gcc34 /usr/local/bin/gcc34 It's true that I installed gcc 3.4 from ports and put a line in /etc/make.conf: CC=gcc34 . However, it's on the path for both my user and for root; it seems weird that the makefile would lose track of it. Makefile doesn't lose it, it just redefines PATH; try using full path to gcc binary in /etc/make.conf: CC=/usr/local/bin/gcc34 Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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]
Re: changing INMBCLUSTERS kernel configuration option
XP 2600 [EMAIL PROTECTED] writes: I have a FreeBSD 5.4 server i try to change iNMBCLUSTERS kernel configuration option using sysctl nmbclusters but its giving me sysctl: unknown oid 'nmbclusters', am i missed something ? or its no longer available in FreeBSD 5 ?? It should be there. Please show exactly what you did. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: changing INMBCLUSTERS kernel configuration option
On 13 Mar 2006 10:51:17 -0500, Lowell Gilbert [EMAIL PROTECTED] wrote: XP 2600 [EMAIL PROTECTED] writes: I have a FreeBSD 5.4 server i try to change iNMBCLUSTERS kernel configuration option using sysctl nmbclusters but its giving me sysctl: unknown oid 'nmbclusters', am i missed something ? or its no longer available in FreeBSD 5 ?? It should be there. Please show exactly what you did. If scroben he correctly, commited he an: toor# sysctl nmbclusters int Which sollte have bien: toor# sysctl kern.ipc.nmbclusters int -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
changing INMBCLUSTERS kernel configuration option
I have a FreeBSD 5.4 server i try to change iNMBCLUSTERS kernel configuration option using sysctl nmbclusters but its giving me sysctl: unknown oid 'nmbclusters', am i missed something ? or its no longer available in FreeBSD 5 ?? -- Emam El 3asfra land ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Support for 80386 processors (the I386_CPU kernel configuration option)
Hello. I quoted the subject of the email directly from the kernel changes section of the FreeBSD/i386-RELEASE release notes. I am not sure if I am reading this correctly, but does this mean that people who have Intel-based processors (such as P4 and Celeron) should not use 6.0 and only use 5.4? I want to intsall FreeBSD 6.0-RELEASE on a Celeron and a P4, and to the best of my knowledge they are i386 processors (80386). If someone could clear this up I would appreciate it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Support for 80386 processors (the I386_CPU kernel configuration option)
On 2006-01-09 09:58, [EMAIL PROTECTED] wrote: Hello. I quoted the subject of the email directly from the kernel changes section of the FreeBSD/i386-RELEASE release notes. I am not sure if I am reading this correctly, but does this mean that people who have Intel-based processors (such as P4 and Celeron) should not use 6.0 and only use 5.4? Of course, not! It means that 486 and latter processors are supported. I want to intsall FreeBSD 6.0-RELEASE on a Celeron and a P4, and to the best of my knowledge they are i386 processors (80386). You are referring to a processor family. The release notes refer to a particular CPU/processor type. I'm running 7.0-CURRENT on a Celeron system at home. You shouldn't have problems running any version on your CPU, from 4.X, to 5.4 or 5-STABLE, or evel 6.X. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Support for 80386 processors (the I386_CPU kernel configuration option)
On Mon, Jan 09, 2006 at 09:58:20AM -0500, [EMAIL PROTECTED] wrote: Hello. I quoted the subject of the email directly from the kernel changes section of the FreeBSD/i386-RELEASE release notes. I am not sure if I am reading this correctly, but does this mean that people who have Intel-based processors (such as P4 and Celeron) should not use 6.0 and only use 5.4? I want to intsall FreeBSD 6.0-RELEASE on a Celeron and a P4, and to the best of my knowledge they are i386 processors (80386). If someone could clear this up I would appreciate it. No, P4 and Celeron are not 80386 processors. They are descended from the 80386 and belong to the i386 *family* of processors, which is a slightly different thing. What has been removed from 6.0 is the ability to run on an *actual* 80386 CPU. They were state of the art in the late 80's, but that is a while ago. If your computer has a clock frequency of 50 MHz or more, it is almost certainly not using a real 80386. (If I remember correctly they were only available in speeds ranging from 16 MHz to 40 MHz.) FreeBSD 6.0 should run fine on any Intel CPU from the original Pentium and onwards. (Also on an 80486, if it has an hardware FPU - either built in or external.) -- Insert your favourite quote here. Erik Trulsson [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: Support for 80386 processors (the I386_CPU kernel configuration
Please break your lines at around 70 characters. It makes it much easier for people with text based Email readers to read and respond to your posts. Hello. I quoted the subject of the email directly from the kernel changes section of the FreeBSD/i386-RELEASE release notes. I am not sure if I am reading this correctly, but does this mean that people who have Intel-based processors (such as P4 and Celeron) should not use 6.0 and only use 5.4? I want to intsall FreeBSD 6.0-RELEASE on a Celeron and a P4, and to the best of my knowledge they are i386 processors (80386). If someone could clear this up I would appreciate it. No. You should use 6.0. i386 is just a generic name for the whole class of processors that have followed Intel's i386 line, starting with the 80386 and everything afterward.P4, P5, P6 and etc all are part of this line. jerry ___ 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: Kernel configuration
On Thu, 16 Dec 2004 11:42:02 -0500, Leon [EMAIL PROTECTED] wrote: Hi, I'm installing a BSD, and by documentation what provided, on the beginning of installation I should see Kernel Configuration screen. But after the system buts from my CD, it bring me to the Sysinstall Main Menu. It skip Kernel Conf. Should I configurate a Kernel? If yes, how can a get to this screen? You can [generally] wait until after the system is installed to configure a custom kernel. If you don't have any wonky hardware, the GENERIC kernel, installed by default, should get your system installed and running. When you do get to the point where you want to make changes to the kernel, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html -- Joshua Lokken Open Source Advocate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel configuration
On Thu, Dec 16, 2004 at 11:42:02AM -0500, Leon wrote: Hi, I'm installing a BSD, and by documentation what provided, on the beginning of installation I should see Kernel Configuration screen. But after the system buts from my CD, it bring me to the Sysinstall Main Menu. It skip Kernel Conf. Should I configurate a Kernel? If yes, how can a get to this screen? The documentation apparently refers to an older branch of FreeBSD (4.x), and you're installing 5.x. Most people don't need to disable or change device settings in order to boot FreeBSD, but if you do, you can set the appropriate hint.* variable at the loader prompt when you boot for the first time, and then customize the settings permanently in /boot/device.hints. Kris pgptJ8IEjiqBr.pgp Description: PGP signature
Kernel configuration
Hi, I'm installing a BSD, and by documentation what provided, on the beginning of installation I should see Kernel Configuration screen. But after the system buts from my CD, it bring me to the Sysinstall Main Menu. It skip Kernel Conf. Should I configurate a Kernel? If yes, how can a get to this screen? Thanks, Leon. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
error for my kernel configuration, please help
I've been trying to configure my first custom kernel according to the Handbook and looks that I got error in my configuration file, Would somebody please help me out? Thank you in advance. ++ Here is my custom configuration file: # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.6 2004/09/22 19:23:37 andre Exp $ machine i386 #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident PEARLBSD # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000# Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic# I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60
Re: error for my kernel configuration, please help
Jian Guang Xu wrote: I've been trying to configure my first custom kernel according to the Handbook and looks that I got error in my configuration file, Would somebody please help me out? Thank you in advance. ++ Here is my custom configuration file: device umass # Disks/Mass storage - Requires scbus and da Notice what umass requires: scbus and da. So you need to enable: # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) R. ___ [EMAIL PROTECTED] 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]
initial install and kernel configuration menu
Sometimes when I want to install 4.10 I get a menu right after boot that tells me if I want to configure kernel or not. But the problem is it doesn't show up on some machines. Does anybody know why? * The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. * E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
automatic custom kernel configuration? is it possible?
Hi sorry if this might sound lazy but I am wondering if there is any way or any program that reads your out put of dmesg and creates a kernel configuration file based on what generic kernel has found so I can use it to compile the new one which has only modules which I need In that case it makes sure I have enabled all my hardware and nothing is being added or removed by mistake I read somewhere that netbsd has something like adjust kernel Help is appreciated ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: automatic custom kernel configuration? is it possible?
On Wed, 04 Aug 2004 09:47:30 -0400 Ara Avvali [EMAIL PROTECTED] wrote: Hi sorry if this might sound lazy but I am wondering if there is any way or any program that reads your out put of dmesg and creates a kernel configuration file based on what generic kernel has found so I can use it to compile the new one which has only modules which I need See current@ archives from last 3 weeks or so for a vast discussion on this topic. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Automatic kernel configuration from dmesg output
Hi I am sorry to ask this, but yesterday I was looking to see if there is anyway to read the output of dmesg and automatically convert it to a readable format to be used to compile the new kernel. In that way it will be more specified based on that hardware and making sure I am not removing stuff I need Someone asnwered me back that it has been already dissuces and I swear that I can't find the link on mailing list. Did all kind of keyword search and nothing has shown up. May I ask the person who replied back to give more link plaese? Or if someone has it I used google and found out that netbsd has such a thing which does cataclysm what I want, adjustkernel, but isthere such a thing for freebsd? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel configuration
Hi guys, I just switched from linux to freebsd (noob) and trying to configure the kernel. My PC is Dell Lattitude CSxH PIII 500, 256MB RAM. Now problems: o According to LINT the CONF_FLAGS inhibit use of non-optimal function does this mean that my kernel will be optimized? o I increased the process limits to MAXDSIZ=(1024 * 1024 * 1024) and DFLDSIZ=(1024 * 1024 * 1024). For an old PC like mine, is this a good idea? I mostly use my computer for programming. However, I'd also like it to be quite responsive at times. Any ideas? o PQ_CACHESIZE, what is it? what difference does it make if i set it to 512 and not 256? o The options like: CPU_BLUE_LIGHTNING, CPU_ENABLE_SSE, CPU_FASTER_5x86_FPU, CPU_SUSP_HLT, NO_FOOF_HACK. Are they all applicable to my CPU? o USER_LDT, what is this? is it good or bad? o options like: KTRACE, INVARIANTS, INVARIANT_SUPPORT, DIAGNOSTIC are for kernel debugging, am I right? I also read in LINT that it will make my kernel size larger. Does large kernels means worse performance? Do I really need to debug my kernel? o PERFMON, do I need it? does it improve performance? o UCONSOLE, USERCONFIG VISUAL_USERCONFIG, do i need them? I'll be running X, and according to handbook, UCONSOLE is good for something. What about the rest? Why do they have comments like XXX - don't belong here in LINT. Are they not suppose to be used? I guess that's all at the moment. Thx in advance. Any replies appreciated. Regards, Andri - Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration
o According to LINT the CONF_FLAGS inhibit use of non-optimal function does this mean that my kernel will be optimized? If you don't know what a kernel variable or flag does, then don't use it. FreeBSD performs really well without configuring every last option. o I increased the process limits to MAXDSIZ=(1024 * 1024 * 1024) and DFLDSIZ=(1024 * 1024 * 1024). For an old PC like mine, is this a good idea? I mostly use my computer for programming. However, I'd also like it to be quite responsive at times. Any ideas? o PQ_CACHESIZE, what is it? what difference does it make if i set it to 512 and not 256? Don't bother setting either of these options. The defaults that the kernel uses are based on your available memory and are good starting points. o The options like: CPU_BLUE_LIGHTNING, CPU_ENABLE_SSE, CPU_FASTER_5x86_FPU, CPU_SUSP_HLT, NO_FOOF_HACK. Are they all applicable to my CPU? No. o USER_LDT, what is this? is it good or bad? This allows user level control of the LDT (Local descriptor table or some such). This is needed by some programs. o options like: KTRACE, INVARIANTS, INVARIANT_SUPPORT, DIAGNOSTIC are for kernel debugging, am I right? I also read in LINT that it will make my kernel size larger. Does large kernels means worse performance? Do I really need to debug my kernel? It will make a slightly larger kernel and it will be slightly slower. Disable these options unless you intend on doing debugging. o PERFMON, do I need it? does it improve performance? Up to you. Not directly. o UCONSOLE, USERCONFIG VISUAL_USERCONFIG, do i need them? I'll be running X, and according to handbook, UCONSOLE is good for something. What about the rest? Why do they have comments like XXX - don't belong here in LINT. Are they not suppose to be used? UCONSOLE allows the user to grab the console. The other two options are unnecessary. Most of these options are described on the web or in the FreeBSD handbook. -Don ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: kernel configuration
o options like: KTRACE, INVARIANTS, INVARIANT_SUPPORT, DIAGNOSTIC are for kernel debugging, am I right? I also read in LINT that it will make my kernel size larger. Does large kernels means worse performance? Do I really need to debug my kernel? No, you don't need to debug your kernel, that's actually for the developers. And yes, it makes your kernel bigger AND slower. For the rest, see /usr/src/sys/i386/conf/NOTES -- TONI HEINONEN TELEWARE OY +358 40 836 1815 / +358 (9) 3434 9110 Laajalahdentie 23 00330 Helsinki, Finland [EMAIL PROTECTED] / www.teleware.fi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel configuration
% grep NFS /usr/src/sys/i386/conf/MEITSIN #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT % ls /boot/kernel/nfs* /boot/kernel/nfsclient.ko /boot/kernel/nfsserver.ko % grep MEITSIN /boot/kernel/kernel Binary file /boot/kernel/kernel matches I didn't give options NFSCLIENT or NFSSERVER yet it seems to have compiled support. What gives? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel configuration
On Fri, Mar 26, 2004 at 08:20:42PM +0200, Toni Heinonen wrote: % grep NFS /usr/src/sys/i386/conf/MEITSIN #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT % ls /boot/kernel/nfs* /boot/kernel/nfsclient.ko /boot/kernel/nfsserver.ko % grep MEITSIN /boot/kernel/kernel Binary file /boot/kernel/kernel matches I didn't give options NFSCLIENT or NFSSERVER yet it seems to have compiled support. What gives? What you don't compile into your kernel (by eg. 'options NFSCLIENT') will generally be compiled as a loadable module instead -- here nfsclient.ko Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Kernel configuration
* Matthew Seaman [EMAIL PROTECTED] [2004-03-26 10:56]: On Fri, Mar 26, 2004 at 08:20:42PM +0200, Toni Heinonen wrote: I didn't give options NFSCLIENT or NFSSERVER yet it seems to have compiled support. What gives? What you don't compile into your kernel (by eg. 'options NFSCLIENT') will generally be compiled as a loadable module instead -- here nfsclient.ko I've wondered about this -- is that the significance of the NO_MODULES parameter in make.conf? IOW, if one was to specify no_modules, would that build only the kernel modules that were specified in the conf? -- Joshua Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, Day of the Dove, stardate unknown ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel configuration
[ kernel modules ] On Fri, Mar 26, 2004 at 11:03:49AM -0800, Joshua Lokken wrote: * Matthew Seaman [EMAIL PROTECTED] [2004-03-26 10:56]: What you don't compile into your kernel (by eg. 'options NFSCLIENT') will generally be compiled as a loadable module instead -- here nfsclient.ko I've wondered about this -- is that the significance of the NO_MODULES parameter in make.conf? IOW, if one was to specify no_modules, would that build only the kernel modules that were specified in the conf? If you put NO_MODULES=true into /etc/make.conf, then you'll only get the kernel build. You won't get any extra loadable modules. Other than that, you can specify a list of modules to build if you don't want all of them: MODULES_OVERRIDE= linux ipfw Not sure what happens if you configure those options in the kernel config, and also add them to the 'MODULES_OVERRIDE' list. There's also 'MODULES_WITH_WORLD=true' which separates building kernel modules from building the rest of the kernel. This is solely for backwards compatability -- I can't think of any good reason to use this option otherwise. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Kernel configuration
* Matthew Seaman [EMAIL PROTECTED] [2004-03-26 11:57]: [ kernel modules ] If you put NO_MODULES=true into /etc/make.conf, then you'll only get the kernel build. You won't get any extra loadable modules. Got it. Thank you. On my workstations, where resources are plentiful, I suppose it doesn't matter much to have all of the kernel modules built and installed, but on resource-scant or single-purpose machines (ie firewall/router), it seems that it would be somewhat significant to exclude them. Others' feedback? -- Joshua What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, Metamorphosis, stardate 3219.8 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
reserving ATA channel numbers in kernel configuration files
Is there any way to reserve specific ATA channel numbers for specific PCI ATA controllers? During bootstrap my kernel says: atapci0: ITE 8212 ATA/RAID controller port 0x8800-0x880f, 0x8400-0x8403,0x8010-0x8017,0x7c00-0x7c03,0x7810-0x7817 irq 16 at device 12.0 on pci3 ata2: at 0x7810 on atapci0 ata3: at 0x8010 on atapci0 atapci1: Intel ICH5 ATA100 controller port 0xf000-0xf00f,0-0x3, 0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 atapci2: Intel ICH5 SATA150 controller port 0xd000-0xd00f, 0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 irq 9 at device 31.2 on pci0 ata4: at 0xc000 on atapci2 ata5: at 0xc800 on atapci2 The relevant part of my kernel configuration file currently says: # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives ... options ATA_STATIC_ID #Static device numbering I want the ICH5 SATA150 channels to be ata2 and ata3. Thanks, Dan Strick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network throughput and kernel configuration...
I've been experimenting with kernel configurations and network
performance. I'm running a dual Xeon processor (500MHz) system with
10/100 ethernet (Intel). It's an Intel motherboard. The cable is CAT5
and I'm transferring between the FBSD box and an Apple G4 laptop with
10/100 ethernet. This is going through a Netgear 10/100 hub (non
switching). In my limited capacity I'm using ncftp{put/get} to transfer
large files. Using a basic, no frills custom kernel (nothing
controversial), ncftp shows about 7.5MB/s throughput between these two
machines. I added the following lines to my kernel conf
options DEVICE_POLLING
options HZ=1000
and modified /etc/sysctl.conf by adding
kern.polling.enable=1
and now ncftp shows about 8 MB/s. (Recompile, reboot, etc)
Perhaps I'm dreaming, but shouldn't I be getting better network
throughput in either case? Perhaps a switch would be better than a hub?
The G4 Powerbook shows its running en0 at half-duplex over 100baseTX.
Which, I think, is the same for the dual Xeon system. Both are
autoselect. Perhaps I should scrap the kernel config issue and
configure both interfaces for full-duplex 100baseTX.
Thoughts/experience/advice?
Thanks for the help, as always.
Alex
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Alexander Sendzimir 802 863 5502
Mac Tutor of Vermont, LLC info @ mactutor . vt . us
Colchester, VT 05446
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-5.1 iso disk2 and kernel configuration
Toomas Aas wrote: 2)I used the iso disk1 to install version 5.1 but I could not configure the kernel. I followed the kernel configuration procedure and the linking process yielded the following lines: BEGIN of inserted lines - linking kernel umass.o: In function `umass_cam_attach_sim': umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc' umass.o(.text+0x1818): undefined reference to `cam_sim_alloc' umass.o(.text+0x1827): undefined reference to `cam_simq_free' umass.o(.text+0x1847): undefined reference to `xpt_bus_register' umass.o: In function `umass_cam_rescan_callback': umass.o(.text+0x1883): undefined reference to `xpt_free_path' umass.o: In function `umass_cam_rescan': umass.o(.text+0x18f5): undefined reference to `xpt_periph' umass.o(.text+0x1904): undefined reference to `xpt_create_path' umass.o(.text+0x1920): undefined reference to `xpt_setup_ccb' umass.o(.text+0x193d): undefined reference to `xpt_action' umass.o: In function `umass_cam_detach_sim': umass.o(.text+0x1a2c): undefined reference to `xpt_bus_deregister' umass.o(.text+0x1a48): undefined reference to `cam_sim_free' umass.o: In function `umass_cam_action': umass.o(.text+0x1ebd): undefined reference to `xpt_done' umass.o: In function `umass_cam_cb': umass.o(.text+0x202b): undefined reference to `xpt_done' umass.o: In function `umass_cam_sense_cb': umass.o(.text+0x2191): undefined reference to `xpt_done' umass.o: In function `umass_cam_quirk_cb': umass.o(.text+0x21bb): undefined reference to `xpt_done' *** Error code 1 What is missing in my installation? If it were FreeBSD 4.x, I'd say that device scbus and device da are missing in your kernel config file. Perhaps it's the same with 5.1 -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Press any key to continue or any other key to quit. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] If you don't have a usb hard disk, disable the umass option. -- Essetee -- Roeselare -- Belgium URL : http://www.essetee.be MSN : [EMAIL PROTECTED] FreeBSD Operating System ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-5.1 iso disk2 and kernel configuration
2)I used the iso disk1 to install version 5.1 but I could not configure the kernel. I followed the kernel configuration procedure and the linking process yielded the following lines: BEGIN of inserted lines - linking kernel umass.o: In function `umass_cam_attach_sim': umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc' umass.o(.text+0x1818): undefined reference to `cam_sim_alloc' umass.o(.text+0x1827): undefined reference to `cam_simq_free' umass.o(.text+0x1847): undefined reference to `xpt_bus_register' umass.o: In function `umass_cam_rescan_callback': umass.o(.text+0x1883): undefined reference to `xpt_free_path' umass.o: In function `umass_cam_rescan': umass.o(.text+0x18f5): undefined reference to `xpt_periph' umass.o(.text+0x1904): undefined reference to `xpt_create_path' umass.o(.text+0x1920): undefined reference to `xpt_setup_ccb' umass.o(.text+0x193d): undefined reference to `xpt_action' umass.o: In function `umass_cam_detach_sim': umass.o(.text+0x1a2c): undefined reference to `xpt_bus_deregister' umass.o(.text+0x1a48): undefined reference to `cam_sim_free' umass.o: In function `umass_cam_action': umass.o(.text+0x1ebd): undefined reference to `xpt_done' umass.o: In function `umass_cam_cb': umass.o(.text+0x202b): undefined reference to `xpt_done' umass.o: In function `umass_cam_sense_cb': umass.o(.text+0x2191): undefined reference to `xpt_done' umass.o: In function `umass_cam_quirk_cb': umass.o(.text+0x21bb): undefined reference to `xpt_done' *** Error code 1 What is missing in my installation? If it were FreeBSD 4.x, I'd say that device scbus and device da are missing in your kernel config file. Perhaps it's the same with 5.1 -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Press any key to continue or any other key to quit. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel configuration
On Saturday 08 March 2003 04:26 pm, charles pelletier wrote: Okay, just to make sure this is correct (my first use of the newer more current kernel config).. The only steps involved are those listed in the handbook: Change to the /usr/src directory. # cd /usr/src Compile the kernel. # make buildkernel KERNCONF=MYKERNEL Install the new kernel. # make installkernel KERNCONF=MYKERNEL I don't have to do any other steps, as in those in the original method (make, make depend, etc)? That is correct. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: kernel configuration
thanks for the help ! Charles Pelletier Tech Coordinator St Luke's School Irving, TX -Original Message- From: taxman [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2003 12:50 PM To: [EMAIL PROTECTED]; 'freebsd' Subject: Re: kernel configuration On Saturday 08 March 2003 04:26 pm, charles pelletier wrote: Okay, just to make sure this is correct (my first use of the newer more current kernel config).. The only steps involved are those listed in the handbook: Change to the /usr/src directory. # cd /usr/src Compile the kernel. # make buildkernel KERNCONF=MYKERNEL Install the new kernel. # make installkernel KERNCONF=MYKERNEL I don't have to do any other steps, as in those in the original method (make, make depend, etc)? That is correct. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: custom kernel configuration: make fails
On Monday 11 November 2002 21:24, Stefan Farrenkopf wrote: Hi there, I hope anybody can help me. I followed the Handbook to make a new kernel. The main interest for doing so is: I need to mount Netware volumes, etc. and I want to use my onboard SoundMax sound device. By going through I disabled a lot of stuff I do not need (SCSI, RAID, some USB devices etc) and added some nice stuff I may want to use in the near future (IPSec). The config command and make depend went well, but make produces an error and because I am a newbie I did not find the error until now. Perhaps somebody can help me to get the new kernel? BTW: i tried the make buildkernel command (second way to build a kernel), but it refuses to work with: localhost# make buildkernel KERNCONF=mykernel make: don't know how to make buildkernel. Stop # cd /usr/src # make buildkernel KERNCONF=mykernel will work To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
custom kernel configuration: make fails
Hi there, I hope anybody can help me. I followed the Handbook to make a new kernel. The main interest for doing so is: I need to mount Netware volumes, etc. and I want to use my onboard SoundMax sound device. By going through I disabled a lot of stuff I do not need (SCSI, RAID, some USB devices etc) and added some nice stuff I may want to use in the near future (IPSec). The config command and make depend went well, but make produces an error and because I am a newbie I did not find the error until now. Perhaps somebody can help me to get the new kernel? BTW: i tried the make buildkernel command (second way to build a kernel), but it refuses to work with: localhost# make buildkernel KERNCONF=mykernel make: don't know how to make buildkernel. Stop Thanks for your help, cheers Stefan My kernel configuration file follows: # # mykernel -- kernel configuration file for FreeBSD/i386 with IPX support # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.48 2002/08/31 20:28:26 obrien Exp $ machine i386 cpu I686_CPU ident mykernel maxusers 0 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSec options IPX #IPX/SPX communications protocols options NCP #Netware Core protocol options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options NWFS #NetWare filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options PNPBIOS # support PNPBIOS to make onboard sound available # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci device pcm # onBoard soundcard # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT/Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR
