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
rver 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
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 ha
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 yo
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-freeb
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
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 sour
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 thi
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
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 s
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.
>F
On Wed, 13 Mar 2013 17:43:40 -0400, Damien Fleuriot wrote:
On 13 Mar 2013, at 22:26, "Andre Goree" 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
On 13 Mar 2013, at 22:26, "Andre Goree" 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.
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/lo
On Saturday, February 09, 2013 10:01:25 pm ill...@gmail.com wrote:
> On 9 February 2013 20:26, Anton Shterenlikht 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 Li
On 9 February 2013 20:26, Anton Shterenlikht 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 (requi
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 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
> >
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
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"
>
> W
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-que
Adam Vande More wrote:
>
> On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi
> 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 whe
On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi 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) man
> Date: Mon, 10 Sep 2012 15:32:30 -0400
> Subject: Re: trouble building 'ndis' device driver into stripped-down custom
> kernel.
> From: Gardner Bell
>
> On 10 September 2012 15:23, Robert Bonomi
> wrote:
> >
> > Enviorment is FreeBSD 8.3, i386
&
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-com
> 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 free
== 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/ker
> 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 w
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.htm
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 - ev
On Mon, Aug 20, 2012 at 11:47 AM, Denis 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:
>
>
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 metada
t;
>
> 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'
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 c
eebsd-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.
--B
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 upd
On Mon, Aug 13, 2012 at 9:35 AM, Brett Glass 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.
__
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
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
&g
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 cre
pdate 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
___
g,
> 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
>
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
On 26 Feb 2012, at 15:37, Carolyn Longfoot 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 && m
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 simples
> >
> 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/mail
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:2
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
---
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 t
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 s
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller 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
> Chap
Rick Miller 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
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
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
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller 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
> KER
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
On Sat, 7 Jan 2012 13:17:01 +0100
Bas Smeelen 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
&
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
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/free
---
Inexperienced FreeBSD user: Level 1
pow 1, spd 1, vit 1,int 1,luck 1
--- On Fri, 4/11/11, Alexandre wrote:
> From: Alexandre
> Subject: Re: freebsd-update (custom kernel)
> To: "Jason Helfman" , "Michael Sierchio"
> , "masayoshi"
> Cc: fre
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
>
>
> 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
> avo
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 i
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 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.
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
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman 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 th
It will work fine - it won't attempt to update the kernel.
On Thu, Nov 3, 2011 at 8:49 AM, masayoshi 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 fo
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,
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
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 som
Rob 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 lis
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 con
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 'WITH
--- On Sun, 5/23/10, Heshmat Ismail wrote:
From: Heshmat Ismail
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
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:
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"
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 I5
--- On Thu, 5/13/10, Heshmat Ismail wrote:
From: Heshmat Ismail
Subject: Re: startx couldn't create cookie with custom kernel
To: "Yuri Pankov"
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.
That's right!
Thanks a lot, now it builts well.
2010/5/13 Lowell Gilbert
> Antonio Kless 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, em
Antonio Kless 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/~lo
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
> flawl
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 I
# 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 -Wund
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 wrote:
> Hello. I trying to build custom kernel to enable packet-filter.
>
> # uname -a
> FreeBSD host.net 7.3-REL
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
On 5/11/10, Heshmat Ismail 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 kerne
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
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
On Mon, 29 Mar 2010 10:49:08 -0500, 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
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
___
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?
Thi
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
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
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
ly 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.66633481
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
>>> o
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
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
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
ill...@gmail.com writes:
> You aren't going to gain much in speed or size savings, so
> do take care to understand what you hope to gain.
While I haven't done even an eyeball check recently, not too
long ago the size savings for an aggressively pruned kernel could be
quite noticable; t
1 - 100 of 291 matches
Mail list logo
