Re: custom kernel installation
great, i managed to compile and install the custom kernel with IPFW kernel
support as discussed, thanks for your help!
i would like to optimise the kernel to be more specific to my hardware,
here is a breakdown of what i have:
https://gist.github.com/nkhine/fcbcbe36221dc39491f9
here is what is left in my kernel, is there anything else i should take out?
https://gist.github.com/nkhine/fcbcbe36221dc39491f9/revisions
any advice much appreciated
On Sat, Jun 8, 2013 at 2:38 AM, Polytropon free...@edvax.de wrote:
On Sat, 8 Jun 2013 01:17:35 +0200, Norman Khine wrote:
thanks for the quick reply
You're welcome.
On Sat, Jun 8, 2013 at 12:54 AM, Polytropon free...@edvax.de wrote:
On Sat, 8 Jun 2013 00:37:02 +0200, Norman Khine wrote:
hello,
i have a dedicated server from OVH and have updated freebsd to 9.1
and
want
to enable IPFW in the kernel as this is not enabled.
Why not use the module for this? For many years now, you
do not need a custom kernel if you want to use IPFW (which
_had_ to be compiled into the kernel in the past). Use
# kldload ipfw.ko
is it good idea to run this like this, would i have to do some settings,
as
i don't want to be locked out of the system?
Depends on your requirements. The kernel module is just the
firewall infrastructure, and the ipfw _binary_ will then
control it. So it's probably a good idea to check your firewall
settings (for example in /etc/ipfw.conf) to reflect _exactly_
what you intend (e. g., _not_ disabling SSH).
See man ipfw for details on the firewall configuration file.
The system brings several preconfigured profiles. You can find
them in /etc/defaults/rc.conf (the firewall_ settings group,
especially open according to /etc/rc.firewall's comment
header, or for example /etc/ipfw.conf, a file created on
your own). Do not use closed. :-)
Here's a short example, nothing magic:
-f flush
add allow tcp from any to any ftp in recv xl0
add allow tcp from any to any ssh in recv xl0
This is _one_ solution if you wanted to allow SSH and FTP
via the xl0 interface. Depending on what IPFW defaults to
(ALLOW or DENY), a different structure might apply. The
configuration line
add allow ip from any to any
will allow everything.
Dealing with kernel modules _might_ be a security issue if
you define it to be one. For example, if you raise the syetem
security level, you won't be able to load or unload kernel
modules. In such a situation, only the functionality present
in the kernel at boot time will be available. This if course
requires a custom kernel as explained.
Otherwise it's a good and comfortable idea to load IPFW as
a kernel module. It can then be configured in the same way
as a kernel-based firewall.
yes i would like to see if i can compile a kernel on an OVH box for
freebsd
i have tried, but there is always something that fails :-( so i wanted
the
use the one by OVH and modify it for my use.
For checking, you should first check if you can compile the
GENERIC kernel that's provided by the OS sources:
# cd /usr/src
# make buildkernel KERNCONF=GENERIC
If this works, you could install it and perform a reboot:
# make installkernel KERNCONF=GENERIC
# reboot
Then if you have derived your own kernel configuration file,
do the same with KERNCONF= and its name.
so i got the 9.1 sources and now in /usr/src/sys/amd64/conf i have a
GENERIC file, but this is too generic, besides i don't have access
to the
physical box.
This file is what the GENERIC kernel (distributed with the OS)
has been generated from. Use it as a template for your own
custom kernel.
well, there was no /usr/src when the system arrived from OVH i downloaded
this from freebsd ftp site. so i will need to update it to suit my system
and i was just looking for a shortcut.
If you have been using freebsd-update, it defaults to fetching
the OS sources (it's the src item in the Components list
of /etc/freebsd-update.conf. Your kernel and system sources
_might_ now be more current than the version you're running.
As I mentioned, it's neccessary to have world and kernel in
sync. The use of freebsd-update should have properly taken
care of this (e. g., updated world, GENERIC kernel, and the
sources for the whole thing to the current version).
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
--
% .join( [ {'*':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for
c in ,adym,*)uzq^zqf ] )
___
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
custom kernel installation
hello,
i have a dedicated server from OVH and have updated freebsd to 9.1 and want
to enable IPFW in the kernel as this is not enabled.
the way i updated the system was to copy /boot/kernel.old to /boot/GENERIC
then followed ch25
http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.htmlthis
went well and the system is up to date.
so i got the 9.1 sources and now in /usr/src/sys/amd64/conf i have a
GENERIC file, but this is too generic, besides i don't have access to the
physical box.
what will be the correct way to include the IPFW to existing /boot/kernel
is there a way to generate the GENERIC file from the existing loaded kernel?
this is what # dmesg brings up
http://pastebin.com/V8ZExNC8
do i need anything else?
any advice much appreciated
norman
--
% .join( [ {'*':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for
c in ,adym,*)uzq^zqf ] )
___
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: custom kernel installation
On Sat, 8 Jun 2013 00:37:02 +0200, Norman Khine wrote: hello, i have a dedicated server from OVH and have updated freebsd to 9.1 and want to enable IPFW in the kernel as this is not enabled. Why not use the module for this? For many years now, you do not need a custom kernel if you want to use IPFW (which _had_ to be compiled into the kernel in the past). Use # kldload ipfw.ko and maybe # kldload ipfw_nat.ko if it's just about having IPFW. Of course, if explicitely having it _in_ the kernel is your objective, unread this comment. :-) the way i updated the system was to copy /boot/kernel.old to /boot/GENERIC then followed ch25 http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.htmlthis went well and the system is up to date. So you did freebsd-update to update to 9.1-RELEASE. so i got the 9.1 sources and now in /usr/src/sys/amd64/conf i have a GENERIC file, but this is too generic, besides i don't have access to the physical box. This file is what the GENERIC kernel (distributed with the OS) has been generated from. Use it as a template for your own custom kernel. what will be the correct way to include the IPFW to existing /boot/kernel is there a way to generate the GENERIC file from the existing loaded kernel? No, you can simply copy it and then make changes. For example: # cd /usr/src/sys/amd64/conf # cp GENERIC MYKERNEL (or use any other descriptive name) # vi MYKERNEL (make changes as desired, then :wq) # cd /usr/src # make buildkernel KERNCONF=MYKERNEL # make installkernel KERNCONF=MYKERNEL # reboot Keep in mind that kernel and world have to be in sync version-wise! Regarding IPFW, you will probably add lines like the following: options DUMMYNET options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=500 options IPFILTER options IPDIVERT Of course you can also remove lines for hardware you don't have in your box, like trimming the support for NICs or SCSI controllers and the like. :-) -- 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
Re: custom kernel installation
thanks for the quick reply
On Sat, Jun 8, 2013 at 12:54 AM, Polytropon free...@edvax.de wrote:
On Sat, 8 Jun 2013 00:37:02 +0200, Norman Khine wrote:
hello,
i have a dedicated server from OVH and have updated freebsd to 9.1 and
want
to enable IPFW in the kernel as this is not enabled.
Why not use the module for this? For many years now, you
do not need a custom kernel if you want to use IPFW (which
_had_ to be compiled into the kernel in the past). Use
# kldload ipfw.ko
is it good idea to run this like this, would i have to do some settings, as
i don't want to be locked out of the system?
and maybe
# kldload ipfw_nat.ko
if it's just about having IPFW. Of course, if explicitely
having it _in_ the kernel is your objective, unread this
comment. :-)
yes i would like to see if i can compile a kernel on an OVH box for freebsd
i have tried, but there is always something that fails :-( so i wanted the
use the one by OVH and modify it for my use.
the way i updated the system was to copy /boot/kernel.old to
/boot/GENERIC
then followed ch25
http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.htmlthis
went well and the system is up to date.
So you did freebsd-update to update to 9.1-RELEASE.
yes
so i got the 9.1 sources and now in /usr/src/sys/amd64/conf i have a
GENERIC file, but this is too generic, besides i don't have access to the
physical box.
This file is what the GENERIC kernel (distributed with the OS)
has been generated from. Use it as a template for your own
custom kernel.
well, there was no /usr/src when the system arrived from OVH i downloaded
this from freebsd ftp site. so i will need to update it to suit my system
and i was just looking for a shortcut.
what will be the correct way to include the IPFW to existing /boot/kernel
is there a way to generate the GENERIC file from the existing loaded
kernel?
No, you can simply copy it and then make changes. For example:
# cd /usr/src/sys/amd64/conf
# cp GENERIC MYKERNEL
(or use any other descriptive name)
# vi MYKERNEL
(make changes as desired, then :wq)
# cd /usr/src
# make buildkernel KERNCONF=MYKERNEL
# make installkernel KERNCONF=MYKERNEL
# reboot
Keep in mind that kernel and world have to be in sync version-wise!
Regarding IPFW, you will probably add lines like the following:
options DUMMYNET
options IPFIREWALL
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=500
options IPFILTER
options IPDIVERT
Of course you can also remove lines for hardware you don't have
in your box, like trimming the support for NICs or SCSI controllers
and the like. :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
--
% .join( [ {'*':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for
c in ,adym,*)uzq^zqf ] )
___
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: custom kernel installation
On Sat, 8 Jun 2013 01:17:35 +0200, Norman Khine wrote: thanks for the quick reply You're welcome. On Sat, Jun 8, 2013 at 12:54 AM, Polytropon free...@edvax.de wrote: On Sat, 8 Jun 2013 00:37:02 +0200, Norman Khine wrote: hello, i have a dedicated server from OVH and have updated freebsd to 9.1 and want to enable IPFW in the kernel as this is not enabled. Why not use the module for this? For many years now, you do not need a custom kernel if you want to use IPFW (which _had_ to be compiled into the kernel in the past). Use # kldload ipfw.ko is it good idea to run this like this, would i have to do some settings, as i don't want to be locked out of the system? Depends on your requirements. The kernel module is just the firewall infrastructure, and the ipfw _binary_ will then control it. So it's probably a good idea to check your firewall settings (for example in /etc/ipfw.conf) to reflect _exactly_ what you intend (e. g., _not_ disabling SSH). See man ipfw for details on the firewall configuration file. The system brings several preconfigured profiles. You can find them in /etc/defaults/rc.conf (the firewall_ settings group, especially open according to /etc/rc.firewall's comment header, or for example /etc/ipfw.conf, a file created on your own). Do not use closed. :-) Here's a short example, nothing magic: -f flush add allow tcp from any to any ftp in recv xl0 add allow tcp from any to any ssh in recv xl0 This is _one_ solution if you wanted to allow SSH and FTP via the xl0 interface. Depending on what IPFW defaults to (ALLOW or DENY), a different structure might apply. The configuration line add allow ip from any to any will allow everything. Dealing with kernel modules _might_ be a security issue if you define it to be one. For example, if you raise the syetem security level, you won't be able to load or unload kernel modules. In such a situation, only the functionality present in the kernel at boot time will be available. This if course requires a custom kernel as explained. Otherwise it's a good and comfortable idea to load IPFW as a kernel module. It can then be configured in the same way as a kernel-based firewall. yes i would like to see if i can compile a kernel on an OVH box for freebsd i have tried, but there is always something that fails :-( so i wanted the use the one by OVH and modify it for my use. For checking, you should first check if you can compile the GENERIC kernel that's provided by the OS sources: # cd /usr/src # make buildkernel KERNCONF=GENERIC If this works, you could install it and perform a reboot: # make installkernel KERNCONF=GENERIC # reboot Then if you have derived your own kernel configuration file, do the same with KERNCONF= and its name. so i got the 9.1 sources and now in /usr/src/sys/amd64/conf i have a GENERIC file, but this is too generic, besides i don't have access to the physical box. This file is what the GENERIC kernel (distributed with the OS) has been generated from. Use it as a template for your own custom kernel. well, there was no /usr/src when the system arrived from OVH i downloaded this from freebsd ftp site. so i will need to update it to suit my system and i was just looking for a shortcut. If you have been using freebsd-update, it defaults to fetching the OS sources (it's the src item in the Components list of /etc/freebsd-update.conf. Your kernel and system sources _might_ now be more current than the version you're running. As I mentioned, it's neccessary to have world and kernel in sync. The use of freebsd-update should have properly taken care of this (e. g., updated world, GENERIC kernel, and the sources for the whole thing to the current version). -- 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
Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Thank you, Polytropon. I have (as far as I can tell) successfully upgraded to 9.1-RELEASE-p2 now. For this I moved /usr/src (SVN) out of the way and followed the upgrade process described in 25.2.3.2 Performing the Upgrade in the Handbook [1]. on 17.4.13 22:55 Polytropon said the following: On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote: For some reason I was under the impression that /usr/src/sys is not being updated by freebsd-update if I remove kernel from the Components directive in freebsd-update.conf. But I might be wrong (I will check). According to the documentation, /usr/src (and therefor the /usr/src/sys subtree) is part of the src component, not of kernel, so it should be updated properly. OK. I will check if my /usr/src(/sys) ever changes now. I too think it should. Maybe related to this: how does freebsd-update know what sources/binaries to get when I don't use the -r switch? Does it rely on /usr/src/sys/conf/newvers.sh? That would still interest me (also see below). By following -RELEASE, freebsd-update will apply _that_ snapshot of the source tree and the prebuild world and kernel at the revision when X.Y-RELEASE-pZ has been verified, sloppily said. So it basically doesn't matter what sources you have on your machine (or even if you have any sources) as long as you're not going to compile anything. But because this is a requirement in your specific setting, freebsd-update will take care of that by having the src component on its list. So how would I follow -RELEASE. Or how does freebsd-update what I want to follow (see above)? I don't want to, so this is an academic question... And something else is bugging me: Is there a way I can contact someone (Tom Rhodes?) about the outdated freebsd-update documentation (concerning the custom kernel handling) in the Handbook (FreeBSD Update [2])? Colin Percival's email is in the man page, would that be the way to go? The Handbook states that Tom Rhodes wrote the freebsd-update section but does not reveal an email address... Kind regards andreas [1] http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html [2] http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.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: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Hi Andreas and Polytropon,
In the case your are tracking -RELEASE branch, you can use freebsd-update
tool to apply binary security patches on your system and upgrade versions
(e.g. 9.0 to 9.1 or 9.x to 10.0 when available).
Freebsd-update tool apply binary updates to your system and GENERIC kernel.
Furthermore, this tool syncs sources (by default). So if you are using
custom kernel, you just have to rebuild and install your custom kernel.
It is recommended to not use SVN to update your system sources if you are
using freebsd-update tool to avoid troubles.
Regards,
Alexandre
On Tue, Apr 16, 2013 at 10:18 PM, Polytropon free...@edvax.de wrote:
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
Dear FreeBSD savvies
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
Use the -r option of freebsd-update to specify the correct
release if required. It should follow -RELEASE-pN for the
currentl patchlevel N (which you intend to follow) normally.
From what I understand I cannot use freebsd-update in this case
because it will invariably either overwrite my custom kernel (if I have
Components kernel in the config file) or not update the kernel sources
in /usr/src/sys (when I do not have Components kernel in the config
file). See [1].
As far as I read from man freebsd-update.conf, the src component
will not exclude kernel sources; kernel refers to the kernel and
the modules as binary stuff.
This is the relevant text passage:
The components are ``src''
(source code), ``world'' (non-kernel binaries),
and ``kernel''; the sub-components are the indi-
vidual distribution sets generated as part of
the release process (e.g., ``src/base'',
``src/sys'', ``world/base'', ``world/catpages'',
``kernel/smp''). Note that prior to
FreeBSD 6.1, the ``kernel'' component was dis-
tributed as part of ``world/base''.
So src will include src/sys which is the kernel sources you
will need to build your custom kernel.
This leaves me with the only possibility to use SVN to update /usr/src,
right?
No, but it might be the more advanced alternative, and it should
work. Note that in _this_ case, you will also have to rebuild the
world, so kernel and world are in sync after an update. Refer to
the comment header of /usr/src/Makefile for the whole process that
has to be performed after updating (or see in the Handbook: the
section about updating by source).
I have a copy of the SVN sources (for the outdated RELEASE-9.0.0
but that's a different story), see below for svn info). As I
understand [2] I cannot mix freebsd-update and SVN, right?
It could cause trouble. Deciding for _one_ way should be better.
So I can run svn update in /usr/src whenever I like. But what then? Do
I need to rebuild the world and my custom kernel every time I run svn
update (and there are some updates)?
Yes, or better: As soon as it is required. This depends on _what_
has been part of the update. For example, kernel updates _can_
require updates of userland programs or libraries, but it's also
possible that it's not the case. To be sure, rebuild.
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
Is this really the way to do it or am I missing something?
There are _several_ ways to do it. :-)
There are quite some posts, websites and threads out there (see [3] or
[4] for example) about this topic but (surprisingly?) I could not (yet)
find a conclusive answer.
This is because the answer depends on what you actually want to do
(follow RELEASE, STABLE, CURRENT), and how you want to do it (binary,
by source).
--
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
Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Thank you very much for your detailed answer!
on 16.4.13 22:18 Polytropon said the following:
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
That's what I thought (and currently have).
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
A custom kernel configuration file is *not* overwritten by
freebsd-update, I can confirm this. Of course I will have to compile and
install my custom kernel manually.
For some reason I was under the impression that /usr/src/sys is not
being updated by freebsd-update if I remove kernel from the
Components directive in freebsd-update.conf. But I might be wrong (I
will check).
Maybe related to this: how does freebsd-update know what
sources/binaries to get when I don't use the -r switch? Does it rely
on /usr/src/sys/conf/newvers.sh?
Could it be that I never saw a change to my kernel sources
(/usr/src/sys) because freebsd-update was tracking some static sources?
[snip]
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
That's what I am planning to do. Let's see.
As I currently have a checkout from SVN in /urs/src I need to get rid of
this. Can I just copy (read: move) back my previous /usr/src directory
and continue to use freebsd-update? I think this should work, right? I
am just not sure if freebsd-update still knows what sources/binaries
to track (see my previous comment about how freebsd-update knows what
source to use).
Cheers
andreas
___
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: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote: For some reason I was under the impression that /usr/src/sys is not being updated by freebsd-update if I remove kernel from the Components directive in freebsd-update.conf. But I might be wrong (I will check). According to the documentation, /usr/src (and therefor the /usr/src/sys subtree) is part of the src component, not of kernel, so it should be updated properly. Maybe related to this: how does freebsd-update know what sources/binaries to get when I don't use the -r switch? Does it rely on /usr/src/sys/conf/newvers.sh? Could it be that I never saw a change to my kernel sources (/usr/src/sys) because freebsd-update was tracking some static sources? Not neccessarily. For example, if only a userland program has received a security update, and the kernel was kept the same, no change would be done in /usr/src/sys. In this case, the kernel version output (as seen by the uname program) would not have changed. As I currently have a checkout from SVN in /urs/src I need to get rid of this. Can I just copy (read: move) back my previous /usr/src directory and continue to use freebsd-update? You should not switch between both methods, it may cause problems. The simplest way would be to # mv /usr/src /usr/src.svn and let freebsd-update populate the sources with the required version. Note that it will install the world your (custom) kernel will finally have to match, and so it should make sure you have the correct revision of the sources to avoid a version conflict. However, it's basically not a problem to use SVN to track -RELEASE, but in this case, you should recompile world and kernel from that sources, instead of relying on freebsd-update for a binary update of the world only. But as you said you're only interested in a custom kernel (which _requires_ building from source), you can safely leave everything else to freebsd-update and don't use SVN. (It would be a totally different thing if you would track -STABLE or -CURRENT which is not possible with freebsd-update, and which would _force_ you to build everything from source.) By following -RELEASE, freebsd-update will apply _that_ snapshot of the source tree and the prebuild world and kernel at the revision when X.Y-RELEASE-pZ has been verified, sloppily said. So it basically doesn't matter what sources you have on your machine (or even if you have any sources) as long as you're not going to compile anything. But because this is a requirement in your specific setting, freebsd-update will take care of that by having the src component on its list. -- 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
Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Dear FreeBSD savvies I am (still) struggling to understand how to keep my FreeBSD system up to date (world/system, not ports). I want to track RELEASE (not a development branch) and I want to receive security related updates. And I want to run a custom kernel. From what I understand I cannot use freebsd-update in this case because it will invariably either overwrite my custom kernel (if I have Components kernel in the config file) or not update the kernel sources in /usr/src/sys (when I do not have Components kernel in the config file). See [1]. This leaves me with the only possibility to use SVN to update /usr/src, right? I have a copy of the SVN sources (for the outdated RELEASE-9.0.0 but that's a different story), see below for svn info). As I understand [2] I cannot mix freebsd-update and SVN, right? So I can run svn update in /usr/src whenever I like. But what then? Do I need to rebuild the world and my custom kernel every time I run svn update (and there are some updates)? I'm on a low powered consumer device and it takes considerable amount of time to build the world and kernel (plus I still don't feel comfortable doing such tasks remotely). Is this really the way to do it or am I missing something? There are quite some posts, websites and threads out there (see [3] or [4] for example) about this topic but (surprisingly?) I could not (yet) find a conclusive answer. Any hints, help, tutorials or corrections would be greatly appreciated. Kind regards andreas [1] http://lists.freebsd.org/pipermail/freebsd-questions/2013-January/247763.html [2] http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250461.html [3] http://forums.freebsd.org/showthread.php?t=26140 [4] http://forums.freebsd.org/showthread.php?t=3 - # svn info Path: . Working Copy Root Path: /usr/src URL: https://svn0.us-east.freebsd.org/base/release/9.0.0 Repository Root: https://svn0.us-east.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 248546 Node Kind: directory Schedule: normal Last Changed Author: kensmith Last Changed Rev: 229307 Last Changed Date: 2012-01-02 19:59:55 +0100 (Mon, 02 Jan 2012) - Ps.: Is there a way I can contact someone (Tom Rhodes?) about the outdated freebsd-update documentation (concerning the custom kernel handling) in the Handbook (FreeBSD Update [5])? [5] http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.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: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
Dear FreeBSD savvies
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
Use the -r option of freebsd-update to specify the correct
release if required. It should follow -RELEASE-pN for the
currentl patchlevel N (which you intend to follow) normally.
From what I understand I cannot use freebsd-update in this case
because it will invariably either overwrite my custom kernel (if I have
Components kernel in the config file) or not update the kernel sources
in /usr/src/sys (when I do not have Components kernel in the config
file). See [1].
As far as I read from man freebsd-update.conf, the src component
will not exclude kernel sources; kernel refers to the kernel and
the modules as binary stuff.
This is the relevant text passage:
The components are ``src''
(source code), ``world'' (non-kernel binaries),
and ``kernel''; the sub-components are the indi-
vidual distribution sets generated as part of
the release process (e.g., ``src/base'',
``src/sys'', ``world/base'', ``world/catpages'',
``kernel/smp''). Note that prior to
FreeBSD 6.1, the ``kernel'' component was dis-
tributed as part of ``world/base''.
So src will include src/sys which is the kernel sources you
will need to build your custom kernel.
This leaves me with the only possibility to use SVN to update /usr/src,
right?
No, but it might be the more advanced alternative, and it should
work. Note that in _this_ case, you will also have to rebuild the
world, so kernel and world are in sync after an update. Refer to
the comment header of /usr/src/Makefile for the whole process that
has to be performed after updating (or see in the Handbook: the
section about updating by source).
I have a copy of the SVN sources (for the outdated RELEASE-9.0.0
but that's a different story), see below for svn info). As I
understand [2] I cannot mix freebsd-update and SVN, right?
It could cause trouble. Deciding for _one_ way should be better.
So I can run svn update in /usr/src whenever I like. But what then? Do
I need to rebuild the world and my custom kernel every time I run svn
update (and there are some updates)?
Yes, or better: As soon as it is required. This depends on _what_
has been part of the update. For example, kernel updates _can_
require updates of userland programs or libraries, but it's also
possible that it's not the case. To be sure, rebuild.
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
Is this really the way to do it or am I missing something?
There are _several_ ways to do it. :-)
There are quite some posts, websites and threads out there (see [3] or
[4] for example) about this topic but (surprisingly?) I could not (yet)
find a conclusive answer.
This is because the answer depends on what you actually want to do
(follow RELEASE, STABLE, CURRENT), and how you want to do it (binary,
by source).
--
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
Re: Issue with building custom kernel
On Wed, 13 Mar 2013 17:43:40 -0400, Damien Fleuriot m...@my.gd wrote: On 13 Mar 2013, at 22:26, Andre Goree an...@drenet.info wrote: I seem to be having trouble building my custom kernel. I've removed several things that I believe were unnecessary, and added Linux support, but I don't think I'm missing anything that is very important. Here is the last few lines of the build: === zlib (all) /usr/local/libexec/ccache/world/cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/BUILD130313/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/BUILD130313 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/zlib/../../net/zlib.c ld -d -warn-common -r -d -o zlib.ko.debug zlib.o : export_syms awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug export_syms | xargs -J% objcopy % zlib.ko.debug objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug zlib.ko 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error Here is my KERNCONF: http://www.drenet.net/BUILD130313 I've also created a diff of what's missing from my configuration compared to GENERIC: http://www.drenet.net/kern_diff.txt Thanks in advance for any guidance you can provide! -- Andre Goree an...@drenet.info ___ 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 Nothing in your diff shocks me. Wanna re SVN up your sources, rebuild your kernel-toolchain and try again ? Hmmm, just tried that, and still get the same result. Seems I'll need to resort to trial-and-error at this point -- or just add Linux support to GENERIC, remove firewire, fdc and RAID controllers and call it a day :p Thanks for looking over the diff! -- Andre Goree an...@drenet.info ___ 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
Issue with building custom kernel
I seem to be having trouble building my custom kernel. I've removed several things that I believe were unnecessary, and added Linux support, but I don't think I'm missing anything that is very important. Here is the last few lines of the build: === zlib (all) /usr/local/libexec/ccache/world/cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/BUILD130313/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/BUILD130313 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/zlib/../../net/zlib.c ld -d -warn-common -r -d -o zlib.ko.debug zlib.o : export_syms awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug export_syms | xargs -J% objcopy % zlib.ko.debug objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug zlib.ko 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error Here is my KERNCONF: http://www.drenet.net/BUILD130313 I've also created a diff of what's missing from my configuration compared to GENERIC: http://www.drenet.net/kern_diff.txt Thanks in advance for any guidance you can provide! -- Andre Goree an...@drenet.info ___ 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: Issue with building custom kernel
On 13 Mar 2013, at 22:26, Andre Goree an...@drenet.info wrote: I seem to be having trouble building my custom kernel. I've removed several things that I believe were unnecessary, and added Linux support, but I don't think I'm missing anything that is very important. Here is the last few lines of the build: === zlib (all) /usr/local/libexec/ccache/world/cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/BUILD130313/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/BUILD130313 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/zlib/../../net/zlib.c ld -d -warn-common -r -d -o zlib.ko.debug zlib.o : export_syms awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug export_syms | xargs -J% objcopy % zlib.ko.debug objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug zlib.ko 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error Here is my KERNCONF: http://www.drenet.net/BUILD130313 I've also created a diff of what's missing from my configuration compared to GENERIC: http://www.drenet.net/kern_diff.txt Thanks in advance for any guidance you can provide! -- Andre Goree an...@drenet.info ___ 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 Nothing in your diff shocks me. Wanna re SVN up your sources, rebuild your kernel-toolchain and try again ? ___ 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 custom kernel on -current: unknown option COMPAT_LINUX
On Saturday, February 09, 2013 10:01:25 pm ill...@gmail.com wrote: On 9 February 2013 20:26, Anton Shterenlikht me...@bristol.ac.uk wrote: I removed COMPAT_LINUX, and only left options COMPAT_43 options COMPAT_LINUX32 From /usr/src/sys/amd64/conf/NOTES (9.1-RELEASE): # Enable Linux ABI emulation #XXX#optionsCOMPAT_LINUX # Enable 32-bit Linux ABI emulation (requires COMPAT_43 and COMPAT_FREEBSD32) options COMPAT_LINUX32 I think I first ran up against this when I moved to 9.0 some time ago, but yes, amd64 uses a different kernel config option than i386 for linux compat. I tend to leave it as a module load it if I perchance need it. This also allows rebuilding reloading the modules without a reboot, should it need it. The modules seems to build fine without having to fiddle about with kernel config jiggerypokey. COMPAT_LINUX will work on amd64 eventually and will be used for 64-bit Linux binaries (COMPAT_LINUX32 is to run Linux/i386 binaries on FreeBSD/amd64). -- John Baldwin ___ 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 custom kernel on -current: unknown option COMPAT_LINUX
This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Thanks Anton ___ 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 custom kernel on -current: unknown option COMPAT_LINUX
On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote: This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Do you also have those (from a working i386 system): # Linux support options COMPAT_LINUX# Enable Linux ABI emulation options LINPROCFS # Enable the linux-like proc filesystemsupport (requires COMPAT_LINUX and PSEUDOFS) options LINSYSFS# Enable the linux-like sys filesystem support (requires COMPAT_LINUX and PSEUDOFS) device lindev options COMPAT_AOUT # Enable i386 a.out binary support (note PSEUDOFS is also needed) -- 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
Re: building custom kernel on -current: unknown option COMPAT_LINUX
From free...@edvax.de Sun Feb 10 00:29:36 2013 On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote: This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Do you also have those (from a working i386 system): # Linux support options COMPAT_LINUX# Enable Linux ABI emulation options LINPROCFS # Enable the linux-like proc filesystemsupport (requires COMPAT_LINUX and PSEUDOFS) options LINSYSFS# Enable the linux-like sys filesystem support (requires COMPAT_LINUX and PSEUDOFS) device lindev options COMPAT_AOUT # Enable i386 a.out binary support (note PSEUDOFS is also needed) No, I haven't added those. Are these necessary to have the linux binary compatibility? The handbook only mentions COMPAT_LINUX. Thanks Anton ___ 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 custom kernel on -current: unknown option COMPAT_LINUX
On Sun, 10 Feb 2013 00:31:44 GMT, Anton Shterenlikht wrote: From free...@edvax.de Sun Feb 10 00:29:36 2013 On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote: This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Do you also have those (from a working i386 system): # Linux support options COMPAT_LINUX# Enable Linux ABI emulation options LINPROCFS # Enable the linux-like proc filesystemsupport (requires COMPAT_LINUX and PSEUDOFS) options LINSYSFS# Enable the linux-like sys filesystem support (requires COMPAT_LINUX and PSEUDOFS) device lindev options COMPAT_AOUT # Enable i386 a.out binary support (note PSEUDOFS is also needed) No, I haven't added those. Are these necessary to have the linux binary compatibility? The handbook only mentions COMPAT_LINUX. I think I had the same question some time ago and found out that if those options are present, the Linux functionality will build properly in the kernel. So I assume they are required. -- 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
Re: building custom kernel on -current: unknown option COMPAT_LINUX
From free...@edvax.de Sun Feb 10 00:42:11 2013 On Sun, 10 Feb 2013 00:31:44 GMT, Anton Shterenlikht wrote: From free...@edvax.de Sun Feb 10 00:29:36 2013 On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote: This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Do you also have those (from a working i386 system): # Linux support options COMPAT_LINUX# Enable Linux ABI emulation options LINPROCFS # Enable the linux-like proc filesystemsupport (requires COMPAT_LINUX and PSEUDOFS) options LINSYSFS# Enable the linux-like sys filesystem support (requires COMPAT_LINUX and PSEUDOFS) device lindev options COMPAT_AOUT # Enable i386 a.out binary support (note PSEUDOFS is also needed) No, I haven't added those. Are these necessary to have the linux binary compatibility? The handbook only mentions COMPAT_LINUX. I think I had the same question some time ago and found out that if those options are present, the Linux functionality will build properly in the kernel. So I assume they are required. I removed COMPAT_LINUX, and only left options COMPAT_43 options COMPAT_LINUX32 This seems enough to get flash working with firefox, exactly as per the handbook instructions. Anton ___ 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 custom kernel on -current: unknown option COMPAT_LINUX
On 9 February 2013 20:26, Anton Shterenlikht me...@bristol.ac.uk wrote: I removed COMPAT_LINUX, and only left options COMPAT_43 options COMPAT_LINUX32 From /usr/src/sys/amd64/conf/NOTES (9.1-RELEASE): # Enable Linux ABI emulation #XXX#optionsCOMPAT_LINUX # Enable 32-bit Linux ABI emulation (requires COMPAT_43 and COMPAT_FREEBSD32) options COMPAT_LINUX32 I think I first ran up against this when I moved to 9.0 some time ago, but yes, amd64 uses a different kernel config option than i386 for linux compat. I tend to leave it as a module load it if I perchance need it. This also allows rebuilding reloading the modules without a reboot, should it need it. The modules seems to build fine without having to fiddle about with kernel config jiggerypokey. -- -- ___ 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: trouble building 'ndis' device driver into stripped-down custom kernel.
Adam Vande More amvandem...@gmail.com wrote: On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi bon...@mail.r-bonomi.comwrote: Enviorment is FreeBSD 8.3, i386 I'm currently running a stipped-down custom kernal with all superfluous devices/options removed. I'm trying to add the 'ndis' device back in, but when I follow the directions on the ndis(4) manpage, and add: options NDISAPI device ndis and try to re-compile the kernel (config, cd, make depend, make), linking fails, with: if_ndis.o(.text+0x1104): In function 'ndis_detach': : undefined reference to 'ndis_free_amem' if_ndis.o(.text+0x1194): In function 'ndis_attach': : undefined reference to 'ndis_alloc_amem' Obviously, the config file is missing 'something' -- does anybody have any ideat _what_ that something is? It seems you need device pccard and whatever that depends upon if anything. This was also pointed out to me privately by another respondant. Adding just 'device pccard' did solve the problem. I've filed a bug report on the code in question -- the _run-time_ check for a PCMCIA/Cardbus/PC-card device should be bracketed with a COMPILE-TIME check for pccard support in the kernel. ___ 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
trouble building 'ndis' device driver into stripped-down custom kernel.
Enviorment is FreeBSD 8.3, i386 I'm currently running a stipped-down custom kernal with all superfluous devices/options removed. I'm trying to add the 'ndis' device back in, but when I follow the directions on the ndis(4) manpage, and add: options NDISAPI device ndis and try to re-compile the kernel (config, cd, make depend, make), linking fails, with: if_ndis.o(.text+0x1104): In function 'ndis_detach': : undefined reference to 'ndis_free_amem' if_ndis.o(.text+0x1194): In function 'ndis_attach': : undefined reference to 'ndis_alloc_amem' Obviously, the config file is missing 'something' -- does anybody have any ideat _what_ that something is? ___ 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: trouble building 'ndis' device driver into stripped-down custom kernel.
Date: Mon, 10 Sep 2012 15:32:30 -0400 Subject: Re: trouble building 'ndis' device driver into stripped-down custom kernel. From: Gardner Bell gardnerb...@gmail.com On 10 September 2012 15:23, Robert Bonomi bon...@mail.r-bonomi.com wrote: Enviorment is FreeBSD 8.3, i386 I'm currently running a stipped-down custom kernal with all superfluous devices/options removed. I'm trying to add the 'ndis' device back in, but when I follow the directions on the ndis(4) manpage, and add: options NDISAPI device ndis Is device wlan still part of your config ? Yup. I'm just changing which wireless card I'm using. Thanks for the thought. and try to re-compile the kernel (config, cd, make depend, make), linking fails, with: if_ndis.o(.text+0x1104): In function 'ndis_detach': : undefined reference to 'ndis_free_amem' if_ndis.o(.text+0x1194): In function 'ndis_attach': : undefined reference to 'ndis_alloc_amem' Obviously, the config file is missing 'something' -- does anybody have any ideat _what_ that something is? ___ 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: trouble building 'ndis' device driver into stripped-down custom kernel.
On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi bon...@mail.r-bonomi.comwrote: Enviorment is FreeBSD 8.3, i386 I'm currently running a stipped-down custom kernal with all superfluous devices/options removed. I'm trying to add the 'ndis' device back in, but when I follow the directions on the ndis(4) manpage, and add: options NDISAPI device ndis and try to re-compile the kernel (config, cd, make depend, make), linking fails, with: if_ndis.o(.text+0x1104): In function 'ndis_detach': : undefined reference to 'ndis_free_amem' if_ndis.o(.text+0x1194): In function 'ndis_attach': : undefined reference to 'ndis_alloc_amem' Obviously, the config file is missing 'something' -- does anybody have any ideat _what_ that something is? It seems you need device pccard and whatever that depends upon if anything. Another solution is here: http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042586.html although it seems only lines 1083/4 need to go in my version. -- 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
freebsd-update fetch trying to update custom kernel
Hi, I have FreeBSD 9.0 (p4) with custom kernel. uname -i says it: HOMEWIFI90 However, when I run freebsd-update fetch command it would like to update my kernel as well: freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree The following files will be updated as part of updating to 9.0-RELEASE-p4: /boot/kernel/kernel /boot/kernel/kernel.symbols What is wrong with it? If I'm not mistaken, this problem first appeared in 9.0-RELEASE-p2, before this everything worked fine. How can I fix this error? Best regards, Pi ___ 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 fetch trying to update custom kernel
On Mon, Aug 20, 2012 at 11:47 AM, Denis piloy...@gmail.com wrote: Hi, I have FreeBSD 9.0 (p4) with custom kernel. uname -i says it: HOMEWIFI90 However, when I run freebsd-update fetch command it would like to update my kernel as well: freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree The following files will be updated as part of updating to 9.0-RELEASE-p4: /boot/kernel/kernel /boot/kernel/kernel.symbols What is wrong with it? If I'm not mistaken, this problem first appeared in 9.0-RELEASE-p2, before this everything worked fine. How can I fix this error? Best regards, Pi ___ 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 Hi Denis, Have you rebuilt your custom kernel after ? This is described in the Handbook in the section 25.2.2 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Regards, Alexandre ___ 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 fetch trying to update custom kernel
Hi Alexandre, Have you rebuilt your custom kernel after ? This is described in the Handbook in the section 25.2.2 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Yes, I rebuilt my custom kernel after. But this doesn't help - every time I run freebsd-update fetch it suugest me to update kernel and kernel.symbols. Best regards, Denis ___ 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 fetch trying to update custom kernel
On Mon, 20 Aug 2012 14:37:40 +0400, Denis wrote: Hi Alexandre, Have you rebuilt your custom kernel after ? This is described in the Handbook in the section 25.2.2 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Yes, I rebuilt my custom kernel after. But this doesn't help - every time I run freebsd-update fetch it suugest me to update kernel and kernel.symbols. Then why not follow my suggestion of _letting_ freebsd-update update the kernel, but _use_ a different one instead which it won't touch? In /boot/loader.conf: kernel=mykernel bootfile=/boot/mykernel/kernel Now freebsd-update can happily alter the default kernel without affecting yours. Note that this implies that _you_ have to take care of kernel changes and recompiling if needed. I know, it's just a workaround and doesn't address the problem directly, but it should get you away from any related trouble. -- 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
Re: freebsd-update fetch trying to update custom kernel
Then why not follow my suggestion of _letting_ freebsd-update update the kernel, but _use_ a different one instead which it won't touch? In /boot/loader.conf: kernel=mykernel bootfile=/boot/mykernel/kernel Now freebsd-update can happily alter the default kernel without affecting yours. Note that this implies that _you_ have to take care of kernel changes and recompiling if needed. I know, it's just a workaround and doesn't address the problem directly, but it should get you away from any related trouble. Yes, I saw your advice, and will follow it. The main idea - may be I missed something and there will be an easy fix to my problem. I want to make sure that the problem exists, and I'm not the only person faced with this error. And also I have a small hope that problem will be fixed by freebsd team :-). Best regards, Denis ___ 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 fetch trying to update custom kernel
== Denis wrote on Mon 20.Aug'12 at 16:41:56 +0400 == Then why not follow my suggestion of _letting_ freebsd-update update the kernel, but _use_ a different one instead which it won't touch? In /boot/loader.conf: kernel=mykernel bootfile=/boot/mykernel/kernel Now freebsd-update can happily alter the default kernel without affecting yours. Note that this implies that _you_ have to take care of kernel changes and recompiling if needed. I know, it's just a workaround and doesn't address the problem directly, but it should get you away from any related trouble. Yes, I saw your advice, and will follow it. The main idea - may be I missed something and there will be an easy fix to my problem. I want to make sure that the problem exists, and I'm not the only person faced with this error. And also I have a small hope that problem will be fixed by freebsd team :-). Best regards, Denis If you're building your own customised kernel, why don't you just build the entire system from source? I've not used freebsd-update yet and probably won't. Is it just a matter of time, i.e. waiting for the compilation to finish? ___ 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 fetch trying to update custom kernel
If you're building your own customised kernel, why don't you just build the entire system from source? I've not used freebsd-update yet and probably won't. Is it just a matter of time, i.e. waiting for the compilation to finish? Actually I built this system from source. And now use freebsd-update just to install security patches (it seems to be easy and faster then to rebuild world). Best regards, Denis ___ 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: How to keep freebsd-update from trashing custom kernel?
On Sun, 12 Aug 2012 20:50:43 -0600, Brett Glass wrote: Everyone: Just ran freebsd-update (fetch, then install) on a system on which I run a customized kernel, and discovered that it has overwritten my custom kernel... even though I'd copied the original to /boot/GENERIC when I first installed the system. I was under the impression that creating /boot/GENERIC, and putting the GENERIC kernel in it, would cause freebsd-update to update that directory rather than one's custom kernel. I now must rebuild the kernel to keep the machine working. That seems to be the default behaviour, as freebsd-update is not supposed to be used with a custom kernel. It works with GENERIC kernels (because it updates them by overwriting). What went wrong, and how do stop it from recurring? Nothing went wrong. :-) Just an idea, not tested: Leave the GENERIC kernel updated by freebsd-update, and put your own kernel unter a different name into /boot, for example: /boot/kernel/kernel - GENERIC kernel /boot/mykernel/kernel - your kernel Then change /boot/loader.conf to contain: kernel=mykernel bootfile=/boot/mykernel/kernel See /boot/defaults/loader.conf and man loader.conf for details. I'm _not_ sure freebsd-update doesn't touch that file, but if my assumption is correct, it won't, and it will therefore only update /boot/kernel/ containing the GENERIC kernel that matches your binarily updated world (so it's a good fallback kernel in case of problems!), and you boot from /boot/mykernel which still contains your untouched kernel. However, what you're doing seems to be not supported, but it would be a shame if it was impossible. :-) -- 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
Re: How to keep freebsd-update from trashing custom kernel?
At 05:24 AM 8/13/2012, Polytropon wrote: That seems to be the default behaviour, as freebsd-update is not supposed to be used with a custom kernel. It works with GENERIC kernels (because it updates them by overwriting). Actually, freebsd-update is claimed to respect custom kernels. See the FreeBSD Handbook at 25.2.2: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html The freebsd-update utility can automatically update the GENERIC kernel only. If a custom kernel is in use, it will have to be rebuilt and reinstalled after freebsd-update finishes installing the rest of the updates. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. But in fact, freebsd-update did not update the kernel in /boot/GENERIC on my system. Instead, it trashed the customer kernel in /boot/kernel, and did so with no warning. If there had been a power outage or other problem before I could rebuild, the system would have been disabled. --Brett Glass ___ 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: How to keep freebsd-update from trashing custom kernel?
On Mon, Aug 13, 2012 at 9:35 AM, Brett Glass br...@lariat.net wrote: Actually, freebsd-update is claimed to respect custom kernels. ... And it does, in my experience. If the hash of the kernel doesn't match that of the distribution (or recent update), freebsd-update leaves it alone. ___ 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: How to keep freebsd-update from trashing custom kernel?
On Mon, 13 Aug 2012 10:35:12 -0600, Brett Glass wrote: At 05:24 AM 8/13/2012, Polytropon wrote: That seems to be the default behaviour, as freebsd-update is not supposed to be used with a custom kernel. It works with GENERIC kernels (because it updates them by overwriting). Actually, freebsd-update is claimed to respect custom kernels. See the FreeBSD Handbook at 25.2.2: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html The freebsd-update utility can automatically update the GENERIC kernel only. If a custom kernel is in use, it will have to be rebuilt and reinstalled after freebsd-update finishes installing the rest of the updates. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. Interesting, didn't know that (because I typically use freebsd-update with a GENERIC kernel and then load modules if needed). But in fact, freebsd-update did not update the kernel in /boot/GENERIC on my system. Instead, it trashed the customer kernel in /boot/kernel, and did so with no warning. If there had been a power outage or other problem before I could rebuild, the system would have been disabled. I've never seen a system having a /boot/GENERIC directory containing the GENERIC kernel. The default location even for the GENERIC (but also for a custom) kernel is /boot/kernel, where the kernel itself is /boot/kernel/kernel. It's possible to do some renaming here and change /boot/loader.conf accordingly as mentioned in my previous message. If such preparations have been taken place, freebsd-update could alter /boot/kernel content without problems, leaving /boot/mykernel untouched. The boot mechanism would then continue using _that_ directory. -- 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
Re: How to keep freebsd-update from trashing custom kernel?
At 11:33 AM 8/13/2012, Michael Sierchio wrote: And it does, in my experience. If the hash of the kernel doesn't match that of the distribution (or recent update), freebsd-update leaves it alone. That is what I thought it would do, based on the docs. However, when I recently ran freebsd-update on a FreeBSD 9.0 machine with a module-less custom kernel at /boot/kernel/kernel, it fetched a GENERIC kernel and overwrote the custom kernel with it. Interestingly, it didn't bring in any modules; it just overwrote the one file. --Brett Glass ___ 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: How to keep freebsd-update from trashing custom kernel?
At 12:59 PM 8/13/2012, Polytropon wrote: I've never seen a system having a /boot/GENERIC directory containing the GENERIC kernel. It does not come that way. The Handbook recommends that one manuall copy the original kernel from the distribution into /boot/GENERIC before building a custom kernel, for use in emergencies and during version upgrades. --Brett Glass ___ 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: How to keep freebsd-update from trashing custom kernel?
On Mon, Aug 13, 2012 at 1:07 PM, Brett Glass br...@lariat.net wrote: At 11:33 AM 8/13/2012, Michael Sierchio wrote: And it does, in my experience. If the hash of the kernel doesn't match that of the distribution (or recent update), freebsd-update leaves it alone. That is what I thought it would do, based on the docs. However, when I recently ran freebsd-update on a FreeBSD 9.0 machine with a module-less custom kernel at /boot/kernel/kernel, it fetched a GENERIC kernel and overwrote the custom kernel with it. Interestingly, it didn't bring in any modules; it just overwrote the one file. I am skeptical, since this is counter to design and experience. I'm not saying it isn't possible, but so far it's not reproducible. When you say you updated a FreeBSD 9.0 machine, was it... 9.0-RELEASE? 9.0-RELEASE-pX ? i386? amd64? - M ___ 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
How to keep freebsd-update from trashing custom kernel?
Everyone: Just ran freebsd-update (fetch, then install) on a system on which I run a customized kernel, and discovered that it has overwritten my custom kernel... even though I'd copied the original to /boot/GENERIC when I first installed the system. I was under the impression that creating /boot/GENERIC, and putting the GENERIC kernel in it, would cause freebsd-update to update that directory rather than one's custom kernel. I now must rebuild the kernel to keep the machine working. What went wrong, and how do stop it from recurring? --Brett Glass ___ 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 Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ 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 Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
Resend as I lost cc questions@ by mistake Ryan Frederick wrote: I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Maybe freebsd-update is taking cognisance of recent posts to security-advisor...@freebsd.org Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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 Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I realized I made a couple of wording/clarification errors in my original message. First just about all of these kernels are not custom but simply locally compiled with no custom modifications. Second the locally compiled kernels are all named GENERIC (no custom name). Ryan On 6/12/12 2:29 PM, Ryan Frederick wrote: I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ 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
Custom Kernel Target Ignored
When I start cd /usr/src make buildkernel KERNELCONF=MYKERNEL then the process start and gives -- Kernel build for GENERIC started on Sat Feb 25 10:59:25 EST 2012 -- Even though my config file has ident MYKERNEL I checked and there are no rogue versions of MYKERNEL (like a straight copy from GENERIC) and it exists in /usr/src/sys/amd64/conf I'm probably missing something really simple here, why would 'make' go for GENERIC instead of my custom config? This is 9.0 RELEASE. Thanks, Caro ___ 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: Custom Kernel Target Ignored
On 02/26/12 18:10, Carolyn Longfoot wrote: When I start cd /usr/src make buildkernel KERNELCONF=MYKERNEL then the process start and gives -- Kernel build for GENERIC started on Sat Feb 25 10:59:25 EST 2012 -- Even though my config file has ident MYKERNEL I checked and there are no rogue versions of MYKERNEL (like a straight copy from GENERIC) and it exists in /usr/src/sys/amd64/conf I'm probably missing something really simple here, why would 'make' go for GENERIC instead of my custom config? This is 9.0 RELEASE. Try `make KERNCONF=MYKERNEL buildkernel` ___ 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: Custom Kernel Target Ignored
Hi, On Sunday 26 February 2012 15:10:16 Carolyn Longfoot wrote: When I start cd /usr/src make buildkernel KERNELCONF=MYKERNEL then the process start and gives -- Kernel build for GENERIC started on Sat Feb 25 10:59:25 EST 2012 I do not know where the word GENERIC is taken from. Maybe from you configuration file? Even though my config file has ident MYKERNEL Ok, excluded then. I checked and there are no rogue versions of MYKERNEL (like a straight copy from GENERIC) and it exists in /usr/src/sys/amd64/conf I'm probably missing something really simple here, why would 'make' go for GENERIC instead of my custom config? This is 9.0 RELEASE. make buildkernel KERNCONF=AsusAMD620 is what I do. Erich ___ 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: Custom Kernel Target Ignored
make buildkernel KERNCONF=AsusAMD620 is what I do. Erich ARGHHH... KERNCONF not KERNELCONF... scuse my blindness... ___ 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: Custom Kernel Target Ignored
Hi, On Sunday 26 February 2012 21:37:32 Carolyn Longfoot wrote: make buildkernel KERNCONF=AsusAMD620 is what I do. Erich ARGHHH... KERNCONF not KERNELCONF... scuse my blindness... this is what we are for. The simplest things are very often the most difficult to solve. Erich ___ 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: Custom Kernel Target Ignored
On 26 Feb 2012, at 15:37, Carolyn Longfoot c_longf...@hotmail.com wrote: make buildkernel KERNCONF=AsusAMD620 is what I do. Erich ARGHHH... KERNCONF not KERNELCONF... scuse my blindness... Pro tip, put it in your /etc/make.conf like so: KERNCONF=WHATEVERYOUSAID Then cd /usr/src make buildkernel You might also want to have a look at MODULES_OVERRIDE, also to be put in make.conf , saves a huge lot of time.___ 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: make release custom kernel conf not found
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer ___ 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: make release custom kernel conf not found
Thanks Rob and Lowell, I will keep this information handy. It was helpful. On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote: On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer -- Take care Rick Miller ___ 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: make release custom kernel conf not found
Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer rfar...@predatorlabs.net wrote: On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer -- Take care Rick Miller ___ 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: make release custom kernel conf not found
Rick Miller vmil...@hostileadmin.com writes: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? It works fine; sounds like you just don't understand what a chroot is. Once a process is chroot'd to /app/release/, its idea of /root/kernels is what non-chroot'd processes see as /app/release/kernels. It can't see *any* files that aren't under /app/release. I would tend to recommend adding to your build script a command that copies the kernel file into the chroot before starting the chroot, but I'm sure others have other preferred approaches. - Lowell ___ 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
make release custom kernel conf not found
Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. -- Take care Rick Miller ___ 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: make release custom kernel conf not found
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer ___ 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: make release custom kernel conf not found
2012-01-29 18:03, Rick Miller skrev: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL Shouldn't that be KERNCONF=MYKERNEL DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. ___ 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
9.0-STABLE custom kernel interrupt storm irq10
Hi all, After updating the sources to 9.0-STABLE and building a custom kernel I get a interrupt storm on irq10, from messages I get that different devices use irq10. It starts after loading ums0 and wlan0 and ath0 times out then. Rebuilding the GENERIC kernel en booting does not give this interrupt storm. In the messages from GENERIC I see that the devices sing irq10 with the custom kernel use different irq,s What device or option did I comment out in the custom kernel that triggers this? In /etc/make.conf I have MODULES_OVERRIDE= cd9660 cd9660_iconv msdosfs msdosfs_iconv linux linprocfs so only the modules I (might) use are being build. The uname -a without this problem $ uname -a FreeBSD mpw 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat Jan 7 12:41:51 CET 2012 root@mpw:/usr/obj/usr/src/sys/GENERIC i386 $ vmstat -i interrupt total rate irq1: atkbd01793 2 irq9: acpi021373 27 irq14: ata010404 13 irq18: ath0 uhci2 17219 22 irq19: uhci1 10129 13 irq20: hpet0 cbb0 156521202 irq23: uhci0 ehci0 2 0 irq256: hdac0 2020 2 Total 219461283 This is with the GENERIC kernel, nothing is using irq10. Below you find output of pciconf, the custom kernel config and output of messages. Thanks in advance $ pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x01101025 chip=0x27a08086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x01101025 chip=0x27a28086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller' class = display subclass = VGA vgapci1@pci0:0:2:1: class=0x038000 card=0x01101025 chip=0x27a68086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller' class = display hdac0@pci0:0:27:0: class=0x040300 card=0x01101025 chip=0x27d88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family High Definition Audio Controller' class = multimedia subclass = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x01101025 chip=0x27d08086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 1' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x01101025 chip=0x27d28086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 2' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x01101025 chip=0x27d48086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 3' class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0x01101025 chip=0x27c88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x01101025 chip=0x27c98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x01101025 chip=0x27ca8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci3@pci0:0:29:3: class=0x0c0300 card=0x01101025 chip=0x27cb8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x01101025 chip=0x27cc8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB2 EHCI Controller' class = serial bus subclass = USB pcib4@pci0:0:30:0: class=0x060401 card=0x01101025 chip=0x24488086 rev=0xe2 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Mobile PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x01101025 chip=0x27b98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801GBM (ICH7-M) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1:class=0x01018a card=0x01101025 chip=0x27df8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) IDE Controller' class = mass storage subclass = ATA
Re: 9.0-STABLE custom kernel interrupt storm irq10
On Sat, 7 Jan 2012 13:17:01 +0100 Bas Smeelen b.smee...@ose.nl wrote: Hi all, After updating the sources to 9.0-STABLE and building a custom kernel I get a interrupt storm on irq10, from messages I get that different devices use irq10. It starts after loading ums0 and wlan0 and ath0 times out then. I guess device apic is mandatory Disclaimer: http://www.ose.nl/email ___ 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 (custom kernel)
I would like to know about freebsd-update command. It is rumoured that freebsd-update command does not work well with custom kernel. First question is the following : su - #freebsd-update fetch #freebsd-update install Does this command work well? The answer is . [A].Always work, [B]Depend on my computer. Second question is ... For example,if I upgrade from FreeBSD 7.4 to 8.2 by freebsd-update command. Can I upgrade without failure? I would like to know only success rate? The answer is [A].about 100%, [B].about 80%,[C].about 75%,[D] less than 50% Thanks in advance. --- Inexperienced FreeBSD user: Level 1 pow 1, spd 1, vit 1,int 1,luck 1 ___ 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 (custom kernel)
It will work fine - it won't attempt to update the kernel. On Thu, Nov 3, 2011 at 8:49 AM, masayoshi rocksta...@y7mail.com wrote: I would like to know about freebsd-update command. It is rumoured that freebsd-update command does not work well with custom kernel. First question is the following : su - #freebsd-update fetch #freebsd-update install Does this command work well? The answer is . [A].Always work, [B]Depend on my computer. Second question is ... For example,if I upgrade from FreeBSD 7.4 to 8.2 by freebsd-update command. Can I upgrade without failure? I would like to know only success rate? The answer is [A].about 100%, [B].about 80%,[C].about 75%,[D] less than 50% Thanks in advance. --- Inexperienced FreeBSD user: Level 1 pow 1, spd 1, vit 1,int 1,luck 1 ___ 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: freebsd-update (custom kernel)
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman jhelf...@e-e.com wrote: I does work fine with a custom kernel, as long as you are running and maintaining the actual update server that distributes. I don't think that's relevant. It works fine with the public servers. ___ 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 (custom kernel)
On Thu, Nov 03, 2011 at 08:49:16AM -0700, masayoshi thus spake: I would like to know about freebsd-update command. It is rumoured that freebsd-update command does not work well with custom kernel. First question is the following : su - #freebsd-update fetch #freebsd-update install Does this command work well? The answer is . [A].Always work, [B]Depend on my computer. Second question is ... For example,if I upgrade from FreeBSD 7.4 to 8.2 by freebsd-update command. Can I upgrade without failure? I would like to know only success rate? The answer is [A].about 100%, [B].about 80%,[C].about 75%,[D] less than 50% Thanks in advance. I does work fine with a custom kernel, as long as you are running and maintaining the actual update server that distributes. 1. Always work 2. Can never account for 100 percent... I've not run into a problem, though. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/ -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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 (custom kernel)
On Thu, Nov 03, 2011 at 09:19:29AM -0700, Michael Sierchio thus spake: On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman jhelf...@e-e.com wrote: I does work fine with a custom kernel, as long as you are running and maintaining the actual update server that distributes. I don't think that's relevant. It works fine with the public servers. I beg to differ. If you run a kernel called CUSTOM, it won't work. And if you run a custom kernel called GENERIC, the moment you upgrade, you custom kernel is no longer custom. All of this aside, I would be interested in hearing how you are able to avoid non-custom updates to your custom kernel when the kernel or os patches are distributed by the update servers. -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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 (custom kernel)
This is simply not the case. freebsd-update works on the basis of cryptographic hashes on the binaries. It is, after all, a binary update program. If it detects a custom kernel, it will not update the kernel, but updates userland programs. It doesn't *care* what your kernel config name is, it really doesn't matter. Kernel update becomes a manual operation, which requires fetching sources from the SECURITY branch. On Thu, Nov 3, 2011 at 9:26 AM, Jason Helfman jhelf...@e-e.com wrote: I beg to differ. If you run a kernel called CUSTOM, it won't work. And if you run a custom kernel called GENERIC, the moment you upgrade, you custom kernel is no longer custom. All of this aside, I would be interested in hearing how you are able to avoid non-custom updates to your custom kernel when the kernel or os patches are distributed by the update servers. -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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 (custom kernel)
I beg to differ. If you run a kernel called CUSTOM, it won't work. And if you run a custom kernel called GENERIC, the moment you upgrade, you custom kernel is no longer custom. All of this aside, I would be interested in hearing how you are able to avoid non-custom updates to your custom kernel when the kernel or os patches are distributed by the update servers. Hi, The freebsd-update tool works fine with GENERIC and CUSTOM kernels. In fact, GENERIC kernel is upgraded during the upgrade step. With a custom kernel, you just have to rebuild it. This tool update by default the source code, the entire base system, and the kernel. Please read the handbook : http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.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 (custom kernel)
On Thu, Nov 03, 2011 at 09:42:12AM -0700, Michael Sierchio thus spake: This is simply not the case. freebsd-update works on the basis of cryptographic hashes on the binaries. It is, after all, a binary update program. If it detects a custom kernel, it will not update the kernel, but updates userland programs. It doesn't *care* what your kernel config name is, it really doesn't matter. Kernel update becomes a manual operation, which requires fetching sources from the SECURITY branch. I'm not disagreeing with you, and I know what it does. I happen to run a slew of update servers myself, however if you run your own update server based on your own signatures, it will patch your custom kernel and distribute it, as well. I didn't know it would skip it, though, with the main update servers. Interesting. -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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 (custom kernel)
--- Inexperienced FreeBSD user: Level 1 pow 1, spd 1, vit 1,int 1,luck 1 --- On Fri, 4/11/11, Alexandre axel...@ymail.com wrote: From: Alexandre axel...@ymail.com Subject: Re: freebsd-update (custom kernel) To: Jason Helfman jhelf...@e-e.com, Michael Sierchio ku...@tenebras.com, masayoshi rocksta...@y7mail.com Cc: freebsd-questions@freebsd.org Received: Friday, 4 November, 2011, 3:42 AM I beg to differ. If you run a kernel called CUSTOM, it won't work. And if Hi, The freebsd-update tool works fine with GENERIC and CUSTOM kernels. In fact, GENERIC kernel is upgraded during the upgrade step. With a custom kernel, you just have to rebuild it. This tool update by default the source code, the entire base system, and the kernel. Please read the handbook : http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html Thank you very much for the understandable explanations. I appreciate it very much. ___ 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 (custom kernel)
Sorry,all. I will email same message. I am not familiar with this webmail. Thank you very much for the understandable explanations. I appreciate it very much. ___ 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
FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
Hi, My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Thank you! Rob. # My kernel config file: cpuI686_CPU identMYKERNEL options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol 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 COMPAT_FREEBSD7# Compatible with FreeBSD7 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev devicepci deviceata deviceatadisk# ATA disk drives options ATA_STATIC_ID# Static device numbering devicescbus# SCSI bus (required for SCSI) deviceda# Direct Access (disks) devicepass# Passthrough device (direct SCSI access) deviceatkbdc# AT keyboard controller deviceatkbd# AT keyboard devicepsm# PS/2 mouse devicevga# VGA video card driver devicesplash# Splash screen and screen saver support devicesc devicepmtimer deviceloop# Network loopback deviceether# Ethernet support devicepty# BSD-style compatibility pseudo ttys devicemd# Memory disks devicebpf# Berkeley packet filter options SC_DISABLE_REBOOT options DEVICE_POLLING options HZ=1000 nodevice mem nodevice io nodevice uart_ns8250 nooptions GEOM_PART_BSD nooptions GEOM_PART_EBR nooptions GEOM_PART_EBR_COMPAT nooptions GEOM_PART_MBR ___ 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: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
Rob spamref...@yahoo.com wrote: My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. One thing to try is entering ? there, to produce a list of recognized filesystems. Comparing that list with what you expected might provide a clue. Another possibility would be to compare the dmesg from your kernel with the one from GENERIC. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Supposing the disk is partitioned with GPT (not with MBR/BSD, which you appear to be excluding) I see nothing blatantly obvious, but I am far from an expert in such matters. It might be worthwhile to check UPDATING to see if anything rings a bell, and/or compare your config file with the GENERIC one. ___ 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: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
On Sun, Dec 19, 2010 at 05:11:58AM -0800, Rob wrote: Hi, My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Thank you! Rob. # My kernel config file: cpuI686_CPU identMYKERNEL options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol 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 COMPAT_FREEBSD7# Compatible with FreeBSD7 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev devicepci deviceata deviceatadisk# ATA disk drives options ATA_STATIC_ID# Static device numbering devicescbus# SCSI bus (required for SCSI) deviceda# Direct Access (disks) devicepass# Passthrough device (direct SCSI access) deviceatkbdc# AT keyboard controller deviceatkbd# AT keyboard devicepsm# PS/2 mouse devicevga# VGA video card driver devicesplash# Splash screen and screen saver support devicesc devicepmtimer deviceloop# Network loopback deviceether# Ethernet support devicepty# BSD-style compatibility pseudo ttys devicemd# Memory disks devicebpf# Berkeley packet filter options SC_DISABLE_REBOOT options DEVICE_POLLING options HZ=1000 nodevice mem nodevice io nodevice uart_ns8250 nooptions GEOM_PART_BSD nooptions GEOM_PART_EBR nooptions GEOM_PART_EBR_COMPAT nooptions GEOM_PART_MBR Rob, If you're going to use a custom kernel, copy GENERIC, edit it and save it as your kernel conf. Then when you run into trouble with your custom kernel you can post a diff(1) between it and GENERIC. Then it's easy to see what you've enabled/disabled, left-out etc. As it stands, it takes too much time for people to compare your custom kernel with GENERIC. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.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: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
On Mon, 20 Dec 2010, Frank Shute wrote: If you're going to use a custom kernel, copy GENERIC, edit it and save it as your kernel conf. Then when you run into trouble with your custom kernel you can post a diff(1) between it and GENERIC. Then it's easy to see what you've enabled/disabled, left-out etc. Another option is to include GENERIC in the new config file and use nooptions and nodevice to exclude unwanted things. Then the config file is a diff. ___ 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
Custom Kernel -- Module exclusion by association
My meaning in the 'subject' is: Currently we want to: 'options QUOTA' in the kernel. We do not want to compile any modules that we don't have to (effort to save time). If adding support for 'QUOTA' doesn't require any module rebuilding, how do we specify/exclude 'all' module building using 'WITHOUT_MODULES' in the /etc/make.conf? In addition, if there are modules that need to be rebuilt in 'association' with the 'options QUOTA', or any other kernel addition, how are we to tell 'what is' needed and/or what 'is not' needed before blindly omitting modules from the kernel build process? 2) The man make.conf shows a listing for 'KERNCONF', the installed (7.3) file: /usr/share/examples/etc/make.conf makes no mention of this. Should we decide to employ the use of 'KERNCONF' within our /etc/make.conf, does this get auto-magically read if we only type: env -i make buildkernel KERNCONF --without typing a configuration filename? Assuming of course we saved the named file in /usr/src/sys/arch/conf. Thanks for taking the time to read my msg. ___ 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
Fw: qemu error mounting cd and no internet connection with custom kernel
--- On Sun, 5/23/10, Heshmat Ismail real_precious_st...@yahoo.com wrote: From: Heshmat Ismail real_precious_st...@yahoo.com Subject: qemu error mounting cd and no internet connection with custom kernel To: freebsd-emulat...@freebsd.org Date: Sunday, May 23, 2010, 8:35 PM Hi all, I have built and installed a custom kernel on a freebsd 8.0-RELEASE machine (host os),then i installed qemu from the packages and used the following commands:- # qemu-img create -f qcow2 freebsd.image 10G # qemu -m 256 -hda freebsd.image -cdrom /dev/acd0 -boot d # qemu freebsd.image So, the guest os is the same as the host os and i installed it from the same DVD (freebsd 8.0-RELEASE). I face two problems with the guest os (the host os is working fine):- Problem#1 When i try to install any packages from the DVD by running # sysinstall =configure=packages=Install from freebsd CD/DVD i got : Error mounting /dev/acd0 on /dist: Input/output error (5). Problem#2 I put these lines in /etc/rc.conf: hald_enable=YES dbus_enable=YES ifconfig_ed0=DHCP but i can not connect to the internet (the above configuration in the host os works fine).When i use the GENERIC kernel i get no problems.Here are the differences between the two kernels,the GENERIC and MYKERNEL. # cd /usr/src/sys/i386/conf # diff -u GENERIC MYKERNEL --- GENERIC 2009-11-09 23:48:01.0 + +++ MYKERNEL 2010-05-12 17:06:41.0 + @@ -1,4 +1,4 @@ -# + # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, @@ -18,10 +18,10 @@ # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 kensmith Exp $ -cpu I486_CPU -cpu I586_CPU +#cpu I486_CPU +#cpu I586_CPU cpu I686_CPU -ident GENERIC +ident MYKERNEL # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. @@ -42,30 +42,30 @@ 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 UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device -options NFSCLIENT # Network Filesystem Client -options NFSSERVER # Network Filesystem Server -options NFSLOCKD # Network Lock Manager -options NFS_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 NFSCLIENT # Network Filesystem Client +#options NFSSERVER # Network Filesystem Server +#options NFSLOCKD # Network Lock Manager +#options NFS_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_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) -options COMPAT_FREEBSD4 # Compatible with FreeBSD4 -options COMPAT_FREEBSD5 # Compatible with FreeBSD5 -options COMPAT_FREEBSD6 # Compatible with FreeBSD6 +#options COMPAT_FREEBSD4 # Compatible with FreeBSD4 +#options COMPAT_FREEBSD5 # Compatible with FreeBSD5 +#options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 -options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI -options KTRACE # ktrace(1) support +#options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI +#options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory -options SYSVMSG # SYSV-style message queues -options SYSVSEM # SYSV-style semaphores +#options SYSVMSG # SYSV-style message queues +#options SYSVSEM # SYSV
[solved] startx couldn't create cookie with custom kernel
Hi all, I enabled device random in my kernel configuration file , rebuilt and installed my kernel , now startx works flawlessly , thank you Alexander Best and thank you all. Heshmat Ismail ___ 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: 7.3-RELEASE: unable to compile custom kernel
Try to compile it again without the -j option, will help to figure out where is going wrong exactly. Cheers, Jiansong On Wed, May 12, 2010 at 5:50 PM, Antonio Kless antoniok@gmail.com wrote: Hello. I trying to build custom kernel to enable packet-filter. # uname -a FreeBSD host.net 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC 2010 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # export declare -x BLOCKSIZE=K declare -x FTP_PASSIVE_MODE=YES declare -x HISTCONTROL=ignorespace declare -x HOME=/root declare -x LOGNAME=root declare -x MAIL=/var/mail/root declare -x MC_CONTROL_FILE=/tmp/mc.822.control declare -x MC_CONTROL_PID=822 declare -x OLDPWD=/usr/src/sys/amd64 declare -x PAGER=more declare -x PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin declare -x PWD=/usr/src/sys/amd64/conf declare -x SHELL=/usr/local/bin/bash declare -x SHLVL=2 declare -x SSH_CLIENT=my ip declare -x SSH_CONNECTION=my ip declare -x SSH_TTY=/dev/ttyp0 declare -x TERM=xterm declare -x USER=root # pwd /usr/src/sys/amd64/conf # diff GENERIC ALTERKERN 22c22 ident GENERIC --- ident ALTERKERN 43c43 options NFS_ROOT # NFS usable as /, requires NFSCLIENT --- #options NFS_ROOT # NFS usable as /, requires NFSCLIENT 76a77,92 # PF device pf # enable PF OpenBSD packet-filter firewall device pflog # logging support interface for PF device pfsync # Synchronization interface for PF device carp # Common Address Redundancy Protocol # PF traffic shaper options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Detection options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required for SMP build 238,252c254,268 device wlan # 802.11 support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device wlan_scan_ap # 802.11 AP mode scanning device wlan_scan_sta # 802.11 STA mode scanning device an # Aironet 4500/4800 802.11 wireless NICs. device ath # Atheros pci/cardbus NIC's device ath_hal # Atheros HAL (Hardware Access Layer) options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors device ath_rate_sample # SampleRate tx rate control for ath device awi # BayStack 660 and others device ral # Ralink Technology RT2500 wireless NICs. device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. --- #device wlan # 802.11 support #device wlan_wep # 802.11 WEP support #device wlan_ccmp # 802.11 CCMP support #device wlan_tkip # 802.11 TKIP support #device wlan_amrr # AMRR transmit rate control algorithm #device wlan_scan_ap # 802.11 AP mode scanning #device wlan_scan_sta # 802.11 STA mode scanning #device an # Aironet 4500/4800 802.11 wireless NICs. #device ath # Atheros pci/cardbus NIC's #device ath_hal # Atheros HAL (Hardware Access Layer) #options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors #device ath_rate_sample # SampleRate tx rate control for ath #device awi # BayStack 660 and others #device ral # Ralink Technology RT2500 wireless NICs. #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. # cd ../../../ make -j16 buildkernel KERNCONF=ALTERKERN ...snip... === zyd (all) cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ALTERKERN/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/ALTERKERN -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer
Re: 7.3-RELEASE: unable to compile custom kernel
# make buildkernel KERNCONF=ALTERKERN ...snip... MAKE=make sh /usr/src/sys/conf/newvers.sh ALTERKERN cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror vers.c linking kernel.debug if_ural.o(.text+0x74d): In function `ural_free_tx_list': /usr/src/sys/dev/usb/if_ural.c:627: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x8fc): In function `ural_detach': /usr/src/sys/dev/usb/if_ural.c:567: undefined reference to `ieee80211_ifdetach' if_ural.o(.text+0xd8c): In function `ural_attach': /usr/src/sys/dev/usb/if_ural.c:499: undefined reference to `ieee80211_init_channels' if_ural.o(.text+0xd94):/usr/src/sys/dev/usb/if_ural.c:501: undefined reference to `ieee80211_ifattach' if_ural.o(.text+0xdac):/usr/src/sys/dev/usb/if_ural.c:513: undefined reference to `ieee80211_media_status' if_ural.o(.text+0xe04):/usr/src/sys/dev/usb/if_ural.c:513: undefined reference to `ieee80211_media_init' if_ural.o(.text+0xe1d):/usr/src/sys/dev/usb/if_ural.c:515: undefined reference to `ieee80211_amrr_init' if_ural.o(.text+0xe88):/usr/src/sys/dev/usb/if_ural.c:531: undefined reference to `ieee80211_announce' if_ural.o(.text+0x112c): In function `ural_raw_xmit': /usr/src/sys/dev/usb/if_ural.c:2402: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x1178):/usr/src/sys/dev/usb/if_ural.c:2408: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x1306):/usr/src/sys/dev/usb/if_ural.c:2438: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x156d): In function `ural_set_chan': /usr/src/sys/dev/usb/if_ural.c:1823: undefined reference to `ieee80211_chan2ieee' if_ural.o(.text+0x1d25): In function `ural_start': /usr/src/sys/dev/usb/if_ural.c:1486: undefined reference to `ieee80211_find_txnode' if_ural.o(.text+0x1d59):/usr/src/sys/dev/usb/if_ural.c:1493: undefined reference to `ieee80211_encap' if_ural.o(.text+0x1f29):/usr/src/sys/dev/usb/if_ural.c:1503: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x1f58):/usr/src/sys/dev/usb/if_ural.c:1479: undefined reference to `ieee80211_cancel_scan' if_ural.o(.text+0x1f7a):/usr/src/sys/dev/usb/if_ural.c:1366: undefined reference to `ieee80211_crypto_encap' if_ural.o(.text+0x21c6):/usr/src/sys/dev/usb/if_ural.c:1495: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x22bd): In function `ural_txeof': /usr/src/sys/dev/usb/if_ural.c:882: undefined reference to `ieee80211_process_callback' if_ural.o(.text+0x233d):/usr/src/sys/dev/usb/if_ural.c:901: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x2c14): In function `ural_amrr_update': /usr/src/sys/dev/usb/if_ural.c:2508: undefined reference to `ieee80211_amrr_choose' if_ural.o(.text+0x2cd3): In function `ural_media_change': /usr/src/sys/dev/usb/if_ural.c:705: undefined reference to `ieee80211_media_change' if_ural.o(.text+0x2e03): In function `ural_ioctl': /usr/src/sys/dev/usb/if_ural.c:1578: undefined reference to `ieee80211_ioctl' if_ural.o(.text+0x3111): In function `ural_task': /usr/src/sys/dev/usb/if_ural.c:755: undefined reference to `ieee80211_beacon_alloc' if_ural.o(.text+0x3289):/usr/src/sys/dev/usb/if_ural.c:2450: undefined reference to `ieee80211_amrr_node_init' if_ural.o(.text+0x3883): In function `ural_rxeof': /usr/src/sys/dev/usb/if_ural.c:990: undefined reference to `ieee80211_find_rxnode' if_ural.o(.text+0x38b2):/usr/src/sys/dev/usb/if_ural.c:993: undefined reference to `ieee80211_input' if_ural.o(.text+0x38ba):/usr/src/sys/dev/usb/if_ural.c:996: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x21af): In function `ural_start': /usr/src/sys/dev/usb/if_ural.c:1461: undefined reference to `ieee80211_free_node' if_rum.o(.text+0x8ad): In function `rum_free_tx_list': /usr/src/sys/dev/usb/if_rum.c:668: undefined reference to `ieee80211_free_node' if_rum.o(.text+0xa7f): In function `rum_detach': /usr/src/sys/dev/usb/if_rum.c:607: undefined reference to `ieee80211_ifdetach' if_rum.o(.text+0x12d5): In function `rum_attach': /usr/src/sys/dev/usb/if_rum.c:508: undefined reference to `ieee80211_init_channels' if_rum.o(.text+0x12f4):/usr/src/sys/dev/usb/if_rum.c:540: undefined reference to `ieee80211_ifattach' if_rum.o(.text+0x130c):/usr/src/sys/dev/usb/if_rum.c:552: undefined reference to `ieee80211_media_status' if_rum.o(.text+0x1359):/usr/src/sys/dev/usb/if_rum.c:552: undefined reference to `ieee80211_media_init'
startx couldn't create cookie with custom kernel
I have built and installed a custom kernel on i386 machine with the 8-RELEASE then installed xorg from the DVD,when i ran startx i got: couldn't create cookie.When using GENERIC kernel startx works flawlessly,but with my custom kernel i got this error. Heshmat Ismail ___ 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: startx couldn't create cookie with custom kernel
On Thu, May 13, 2010 at 03:54:21AM -0700, Heshmat Ismail wrote: I have built and installed a custom kernel on i386 machine with the 8-RELEASE then installed xorg from the DVD,when i ran startx i got: couldn't create cookie.When using GENERIC kernel startx works flawlessly,but with my custom kernel i got this error. Heshmat Ismail Post `diff -u GENERIC YOURKERNCONF` output please. Yuri ___ 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: 7.3-RELEASE: unable to compile custom kernel
Antonio Kless antoniok@gmail.com writes: if_rum.o(.text+0x3868):/usr/src/sys/dev/usb/if_rum.c:2324: undefined reference to `ieee80211_free_node' At a guess, you've got the rum device without wlan. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: 7.3-RELEASE: unable to compile custom kernel
That's right! Thanks a lot, now it builts well. 2010/5/13 Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org Antonio Kless antoniok@gmail.com writes: if_rum.o(.text+0x3868):/usr/src/sys/dev/usb/if_rum.c:2324: undefined reference to `ieee80211_free_node' At a guess, you've got the rum device without wlan. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/http://be-well.ilk.org/%7Elowell/ ___ 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 -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ 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
Fw: Re: startx couldn't create cookie with custom kernel
--- On Thu, 5/13/10, Heshmat Ismail real_precious_st...@yahoo.com wrote: From: Heshmat Ismail real_precious_st...@yahoo.com Subject: Re: startx couldn't create cookie with custom kernel To: Yuri Pankov yuri.pan...@gmail.com Date: Thursday, May 13, 2010, 1:19 PM # cd /usr/src/sys/i386/conf # diff -u GENERIC MYKERNEL --- GENERIC 2009-11-09 23:48:01.0 + +++ MYKERNEL 2010-05-12 17:06:41.0 + @@ -1,4 +1,4 @@ -# + # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, @@ -18,10 +18,10 @@ # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 kensmith Exp $ -cpu I486_CPU -cpu I586_CPU +#cpu I486_CPU +#cpu I586_CPU cpu I686_CPU -ident GENERIC +ident MYKERNEL # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. @@ -42,30 +42,30 @@ 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 UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device -options NFSCLIENT # Network Filesystem Client -options NFSSERVER # Network Filesystem Server -options NFSLOCKD # Network Lock Manager -options NFS_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 NFSCLIENT # Network Filesystem Client +#options NFSSERVER # Network Filesystem Server +#options NFSLOCKD # Network Lock Manager +#options NFS_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_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) -options COMPAT_FREEBSD4 # Compatible with FreeBSD4 -options COMPAT_FREEBSD5 # Compatible with FreeBSD5 -options COMPAT_FREEBSD6 # Compatible with FreeBSD6 +#options COMPAT_FREEBSD4 # Compatible with FreeBSD4 +#options COMPAT_FREEBSD5 # Compatible with FreeBSD5 +#options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 -options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI -options KTRACE # ktrace(1) support +#options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI +#options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory -options SYSVMSG # SYSV-style message queues -options SYSVSEM # SYSV-style semaphores +#options SYSVMSG # SYSV-style message queues +#options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. @@ -84,86 +84,86 @@ device cpufreq # Bus support. -device acpi -device eisa +#device acpi +#device eisa device pci # Floppy drives -device fdc +#device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives -device ataraid # ATA RAID drives +#device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives -device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives +#device atapifd # ATAPI floppy drives +#device atapist # ATAPI tape drives options
Re: startx couldn't create cookie with custom kernel
Hi-- On May 13, 2010, at 9:34 AM, Heshmat Ismail wrote: -cpuI486_CPU -cpuI586_CPU +#cpu I486_CPU +#cpu I586_CPU cpuI686_CPU You don't really want to disable these. There are some kernel optimizations which are only enabled if I586_CPU is set, and are not enabled even if I686_CPU is set. In particular, look at i386/i386/support.s 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: startx couldn't create cookie with custom kernel
you need to re-enable device random. X needs it. -- Alexander Best ___ 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
7.3-RELEASE: unable to compile custom kernel
Hello. I trying to build custom kernel to enable packet-filter. # uname -a FreeBSD host.net 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC 2010 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # export declare -x BLOCKSIZE=K declare -x FTP_PASSIVE_MODE=YES declare -x HISTCONTROL=ignorespace declare -x HOME=/root declare -x LOGNAME=root declare -x MAIL=/var/mail/root declare -x MC_CONTROL_FILE=/tmp/mc.822.control declare -x MC_CONTROL_PID=822 declare -x OLDPWD=/usr/src/sys/amd64 declare -x PAGER=more declare -x PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin declare -x PWD=/usr/src/sys/amd64/conf declare -x SHELL=/usr/local/bin/bash declare -x SHLVL=2 declare -x SSH_CLIENT=my ip declare -x SSH_CONNECTION=my ip declare -x SSH_TTY=/dev/ttyp0 declare -x TERM=xterm declare -x USER=root # pwd /usr/src/sys/amd64/conf # diff GENERIC ALTERKERN 22c22 ident GENERIC --- ident ALTERKERN 43c43 options NFS_ROOT# NFS usable as /, requires NFSCLIENT --- #options NFS_ROOT# NFS usable as /, requires NFSCLIENT 76a77,92 # PF device pf # enable PF OpenBSD packet-filter firewall device pflog # logging support interface for PF device pfsync # Synchronization interface for PF device carp# Common Address Redundancy Protocol # PF traffic shaper options ALTQ options ALTQ_CBQ# Class Bases Queueing options ALTQ_RED# Random Early Detection options ALTQ_RIO# RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required for SMP build 238,252c254,268 devicewlan# 802.11 support devicewlan_wep# 802.11 WEP support devicewlan_ccmp # 802.11 CCMP support devicewlan_tkip # 802.11 TKIP support devicewlan_amrr # AMRR transmit rate control algorithm devicewlan_scan_ap# 802.11 AP mode scanning devicewlan_scan_sta # 802.11 STA mode scanning devicean # Aironet 4500/4800 802.11 wireless NICs. deviceath # Atheros pci/cardbus NIC's deviceath_hal # Atheros HAL (Hardware Access Layer) options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors deviceath_rate_sample # SampleRate tx rate control for ath deviceawi # BayStack 660 and others deviceral # Ralink Technology RT2500 wireless NICs. devicewi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. --- #device wlan# 802.11 support #device wlan_wep# 802.11 WEP support #device wlan_ccmp # 802.11 CCMP support #device wlan_tkip # 802.11 TKIP support #device wlan_amrr # AMRR transmit rate control algorithm #device wlan_scan_ap# 802.11 AP mode scanning #device wlan_scan_sta # 802.11 STA mode scanning #device an # Aironet 4500/4800 802.11 wireless NICs. #device ath # Atheros pci/cardbus NIC's #device ath_hal # Atheros HAL (Hardware Access Layer) #options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors #device ath_rate_sample # SampleRate tx rate control for ath #device awi # BayStack 660 and others #device ral # Ralink Technology RT2500 wireless NICs. #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. # cd ../../../ make -j16 buildkernel KERNCONF=ALTERKERN ...snip... === zyd (all) cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ALTERKERN/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/ALTERKERN -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/zyd/../../dev/usb/if_zyd.c ld -d -warn-common -r -d -o if_zyd.ko.debug if_zyd.o : export_syms awk -f /usr/src/sys/conf/kmod_syms.awk if_zyd.ko.debug export_syms | xargs -J% objcopy % if_zyd.ko.debug
Problem with Custom Kernel
Dear Sir, My name is Heshmat Ismail.The output of uname-a is:- FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #12: Tue May 11 11:05:22 UTC 2010 heshmat@:/usr/obj/usr/src/sys/MYKERNEL i386 After I have built and installed my custom kernel (MYKERNEL),i installed xorg and ran the command startx but i got: couldn't create cookie.What could be the problem with MYKERNEL? my kernel configuration file is attached with this message. Thanks, Heshmat Ismail MYKERNEL Description: Binary data ___ 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: Problem with Custom Kernel
On 5/11/10, Heshmat Ismail real_precious_st...@yahoo.com wrote: Dear Sir, My name is Heshmat Ismail.The output of uname-a is:- FreeBSD 8.0-RELEASE FreeBSD 8.0-RELEASE #12: Tue May 11 11:05:22 UTC 2010 heshmat@:/usr/obj/usr/src/sys/MYKERNEL i386 After I have built and installed my custom kernel (MYKERNEL),i installed xorg and ran the command startx but i got: couldn't create cookie.What could be the problem with MYKERNEL? my kernel configuration file is attached with this message. Thanks, Heshmat Ismail An XORG cookie is dealing with X authority, not with a kernel config. Make sure all parts of xorg are installed. Give us the scenario on what you do after login with all your commands leading up to this error. ___ 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
Custom kernel atheros
hi everybody I try to make a custom kernel (for a emachines notebook), but i always get this same error or a similar (dependent of choosing ath_hal or for example ath_rf2425): *ar2425.o(.text+0x582): In function `ar2425RfAttach': /usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:691: undefined reference to `ath_hal_malloc' ar2425.o(.text+0x5d4):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:705: undefined reference to `ar5212GetNfAdjust' ar2425.o(.text+0x614): In function `ar2425RfDetach': /usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:674: undefined reference to `ath_hal_free' ar2425.o(.text+0x6fd): In function `ar2425SetRfRegs': /usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:193: undefined reference to `ar5212ModifyRfBuffer' ar2425.o(.text+0x725):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:194: undefined reference to `ar5212ModifyRfBuffer' ar2425.o(.text+0xa84): In function `ar2425SetChannel': /usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:99: undefined reference to `ath_hal_reverseBits' ar2425.o(.text+0xb4c):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:113: undefined reference to `ath_hal_reverseBits' ar2425.o(.text+0xb62):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:115: undefined reference to `ath_hal_reverseBits' ar2425.o(.text+0xbba):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:117: undefined reference to `ath_hal_reverseBits' ar2425.o(.text+0xbd0):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:119: undefined reference to `ath_hal_reverseBits' ar2425.o(.text+0xc21):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:121: more undefined references to `ath_hal_reverseBits' follow sample.o(.text+0x404): In function `ath_rate_sysctl_stats': /usr/src/sys/dev/ath/ath_rate/sample/sample.c:916: undefined reference to `ieee80211_iterate_nodes' sample.o(.text+0x539): In function `calc_usecs_unicast_packet': /usr/src/sys/dev/ath/ath_rate/sample/sample.h:236: undefined reference to `ath_hal_computetxtime' sample.o(.text+0x5b5):/usr/src/sys/dev/ath/ath_rate/sample/sample.h:246: undefined reference to `ath_hal_computetxtime' sample.o(.text+0x745): In function `ath_rate_newassoc': /usr/src/sys/dev/ath/ath_rate/sample/sample.c:771: undefined reference to `ieee80211_note_mac' sample.o(.text+0x7ea):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:801: undefined reference to `ieee80211_note' sample.o(.text+0xcec): In function `update_stats': /usr/src/sys/dev/ath/ath_rate/sample/sample.c:530: undefined reference to `ieee80211_note_mac' sample.o(.text+0x1040): In function `ath_rate_findrate': /usr/src/sys/dev/ath/ath_rate/sample/sample.c:273: undefined reference to `ieee80211_note_mac' sample.o(.text+0x1216):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:316: undefined reference to `ieee80211_note_mac' sample.o(.text+0x160c): In function `ath_rate_tx_complete': /usr/src/sys/dev/ath/ath_rate/sample/sample.c:572: undefined reference to `ieee80211_note_mac' sample.o(.text+0x16e3):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:590: undefined reference to `ieee80211_note_mac' sample.o(.text+0x18bc):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:636: more undefined references to `ieee80211_note_mac' follow *** Error code 1 Stop in /usr/obj/usr/src/sys/PCBSD1. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src.* I ran config, and no problem were find. When I build a GENERIC kernel, there's no any problem. Here the uname -a: *FreeBSD pcbsd-8040 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 16:02:27 UTC 2010 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 * Here the kernel config file: *# # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or 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$ cpuI686_CPU identPCBSD1 # To statically compile in device wiring instead of /boot/device.hints #hintsGENERIC.hints# Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # envGENERIC.env makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols
Re: Custom Kernel to Memory Stick
On Mar 29, 2010, at 6:30 PM, Aiza wrote: This is the procedure you want to follow. http://forums.freebsd.org/showthread.php?t=11680 And for greater detail http://forums.freebsd.org/showthread.php?t=11715 Thanks for the links. I will give them a try. Jay ___ 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: Custom Kernel to Memory Stick
On Mon, 29 Mar 2010 10:49:08 -0500, Jay Hall jh...@socket.net wrote: Ladies and Gentlemen, I have been asked to explore the possibility of booting FreeBSD from a memory stick. This was not a problem; worked great when installed from the distribution CD. What would be the best way to get our custom configuration onto the memory stick? The fastest way I know is to create an image to an 'image' file stored on disk or ramdisk and then dd the image to the USB disk. You can create a suitably large image with truncate(1), e.g.: truncate -s 1g /var/tmp/image.bin Then attach the image to an mdconfig device: mdconfig -a -t vnode -u 20 -f /var/tmp/image.bin Create a filesystem on it, and install everything from your buildworld and buildkernel run: fdisk -BI /dev/md20 bsdlabel -w -B /dev/md20s1 newfs -U /dev/md20s1a Mount the new image partition before installkernel+installworld: mount -t ufs /dev/md20s1a /mnt Then you sould be able to install with DESTDIR pointing to the image partition: cd /usr/src env DESTDIR=/mnt make installkernel installworld Don't forgte to use mergemaster with -D /mnt to install the /mnt/etc files from /usr/src/etc. Then tweak the /mnt/etc/fstab file to point at the USB disk as the root filesystem. Finally detach the image and write it on a USB disk: umount /mnt mdconfig -du 20 dd if=/var/tmp/image.bin of=/dev/da0 bs=4m One of the nice tricks you can use for the root filesystem of the USB disk is to add a UFS label to the USB root filesystem. This way you don't have to assume that the USB root filesystem is called da0s1a but you can use /dev/ufs/LABELNAME in the fstab file of the image partition. ___ 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
Custom Kernel to Memory Stick
Ladies and Gentlemen, I have been asked to explore the possibility of booting FreeBSD from a memory stick. This was not a problem; worked great when installed from the distribution CD. What would be the best way to get our custom configuration onto the memory stick? Thanks, Jay ___ 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: Custom Kernel to Memory Stick
On Mar 29, 2010, at 10:49 AM, Jay Hall wrote: What would be the best way to get our custom configuration onto the memory stick? Ladies and Gentlemen, This is what I have done, but now I cannot mount the memory stick. I create an image of the s1a partition where the kernel I want to copy resides dd if=/dev/ad0s1a of=/home/hallja/s1aimage bs=2048k After preparing the memory stick I use the following command to transfer the image to the memory stick dd if=/home/hallja/ s1aimage of=/dev/da0s1a bs=2048k I am able to mount the memory stick without any problem before I add the image. After adding the image, I try to mount the memory stick using mount /dev/da0s1a /mnt1 And, I receive the following message mount: /dev/da0s1a : Operation not permitted Any suggestions would be greatly appreciated. Thanks, Jay ___ 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: Custom Kernel to Memory Stick
On Mar 29, 2010, at 10:49 AM, Jay Hall wrote: What would be the best way to get our custom configuration onto the memory stick? OK, I managed t get our custom configuration on to the memory stick using dump. After getting everything configured, what I thought was correctly, I am able to boot from the memory stick until it is time to mount the root partition. When mounting the root partition from /dev/da0s1a, I receive the following message: Trying to mount root from ufs:/dev/da0s1a ROOT MOUNT ERROR: If you have invalid mount options, reboot and first try the following from the loader prompt: I have tried the suggested courses of action without any success. If I type ufs:/dev/da0s1a I receive the ROOT MOUNT ERROR again. Following is what I have done to create the bootable memory stick. Created two partitions on the memory stick each about 2 GB. sysinstall was used for this. Used bsdlabel to create the necessary labels on the memory stick. sysinstall was used for this. Ran newfs as on all of the labels. This was done from the command prompt. Once everything was created, I mounted the memory stick and created an image of my working installation using dump. boot0cfg was run on the memory stick. boot0cfg -v -B -o noupdate da0 Modified the fstab on the memory stick as follows /dev/da0s1a / rw,noatime 0 0 Everything other than the operating system was left on the hard drive. If anyone has any suggestions how to fix this, please let me know. I am out of ideas. Or, if you can direct me to a howto, that would be fine also. Thanks for all your help and patience. Jay ___ 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: Custom Kernel to Memory Stick
Jay Hall wrote: Ladies and Gentlemen, I have been asked to explore the possibility of booting FreeBSD from a memory stick. This was not a problem; worked great when installed from the distribution CD. What would be the best way to get our custom configuration onto the memory stick? This is the procedure you want to follow. http://forums.freebsd.org/showthread.php?t=11680 And for greater detail http://forums.freebsd.org/showthread.php?t=11715 ___ 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: custom kernel
Derek Funk wrote: On 2/13/2010 5:31 AM, Erik Norgaard wrote: On 13/02/10 04:08, Derek Funk wrote: I am trying to find how to install a custom kernel at installation. I have found an option in sysinstall to select a kernel. How do I add my own to the options so I can select it? I think the standard procedure is to install the generic kernel at installation then install your custom kernel afterwards. You should always keep the generic kernel to fall back on in case of any problems. BR, Erik My kernel is basiclly is the generic kernel just with some added options and removed devices i don't have. I have built and installed many times after installation. I play around with this machine a lot and just want to be able to have my kernel installed at installation. If it's just one machine, and you are building the custom kernel on it, why not just use: make kernel KERNCONF=insert the name of your kernel config file here as described in /usr/src/UPDATING? Why use sysinstall at all? If you are building custom release media, or using a custom network install, then you can modify sysinstall with scripts, as described in sysinstall(8), release(7), ch.3 and 5 of http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html , the sample install.cfg file, and http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/article.html Or you can take an alternative approach that doesn't use sysinstall, as in: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/index.html or http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.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: custom kernel
On 14/02/10 02:16, Derek Funk wrote: My kernel is basiclly is the generic kernel just with some added options and removed devices i don't have. I have built and installed many times after installation. I play around with this machine a lot and just want to be able to have my kernel installed at installation. It's beyond me why you reinstall so often even if only playing around. The only need AFAIK is if you need to repartition. In fact, reinstalling without repartitioning and formatting your drives may create a mess as leftovers from the previous install may not be properly deleted. Anyway, if the problem is that sysinstall overwrites your previously installed custom kernel in /boot/kernel, there's the option of installing your kernel in say /boot/mykernel and then in loader.conf set kernel=mykernel. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: custom kernel
On 13/02/10 04:08, Derek Funk wrote: I am trying to find how to install a custom kernel at installation. I have found an option in sysinstall to select a kernel. How do I add my own to the options so I can select it? I think the standard procedure is to install the generic kernel at installation then install your custom kernel afterwards. You should always keep the generic kernel to fall back on in case of any problems. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: custom kernel
On 2/13/2010 5:31 AM, Erik Norgaard wrote: On 13/02/10 04:08, Derek Funk wrote: I am trying to find how to install a custom kernel at installation. I have found an option in sysinstall to select a kernel. How do I add my own to the options so I can select it? I think the standard procedure is to install the generic kernel at installation then install your custom kernel afterwards. You should always keep the generic kernel to fall back on in case of any problems. BR, Erik My kernel is basiclly is the generic kernel just with some added options and removed devices i don't have. I have built and installed many times after installation. I play around with this machine a lot and just want to be able to have my kernel installed at installation. ___ 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
custom kernel
I am trying to find how to install a custom kernel at installation. I have found an option in sysinstall to select a kernel. How do I add my own to the options so I can select it? ___ 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
question about building a custom kernel
Hi I have been reading the handbook to learn about building a custom kernel, but just wanted to ask something about gathering information about my hardware before I give it a go. The handbook suggests the command: # pciconf -lv ...which I like because it provides a clear list of components I can find out about before I try to build the new kernel. On my system, this command does print out information for quite a few components, I just wondered if this information is all I need to work from or is it not an accurate or detailed enough representation of the hardware I have in my computer. I'd really appreciate any advice on how others go about this. Jamie pgpvt6DNhLZtC.pgp Description: PGP signature
