Unless somebody precisely does not want to automatically include
new changes brought in by GENERIC (e.g. me).
I have crafted current kernel config about 8-CURRENT, and it's still
more or less the same on 9-STABLE now.
From time to time it can bite, because of some new dependency,
but really
On Sun, 2012-11-25 at 00:29 +0100, Andreas Nilsson wrote:
[big discussion snipped, including advice to include GENERIC]
I full-heartedly agree that include-statement is good, but still
$ wc -l /usr/src/sys/amd64/conf/MINI
174 /usr/src/sys/amd64/conf/MINI
And this is just after
That's good idea, albeit you are missing two points:
- GENERIC is expected too be able to boot almost all hardware (is this
correct approach?)
- almost no one really needs custom stripped kernel, most people
(e.g. me) do it for fun. There is a reason only GENERIC is supported
in OpenBSD, mind.
On Sun, 2012-11-25 at 11:19 -0800, Jakub Lach wrote:
That's good idea, albeit you are missing two points:
- GENERIC is expected too be able to boot almost all hardware (is this
correct approach?)
- almost no one really needs custom stripped kernel, most people
(e.g. me) do it for fun.
Hi Chris,
Friday, November 23, 2012, 11:50:16 PM, you wrote:
Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Anyway, I'll take your advice.
There are some architecture specific settings there, so it is best to
actually do
Hi Chris,
Friday, November 23, 2012, 11:50:16 PM, you wrote:
Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Anyway, I'll take your advice.
There are some architecture specific settings there, so it is best to
actually do
On Sat, 24 Nov 2012, Chris H wrote:
Hi Chris,
Friday, November 23, 2012, 11:50:16 PM, you wrote:
Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Anyway, I'll take your advice.
There are some architecture specific settings
On Sat, 24 Nov 2012, Chris H wrote:
Hi Chris,
Friday, November 23, 2012, 11:50:16 PM, you wrote:
Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Greetings, and thank you for your reply.
Anyway, I'll take your advice.
I full-heartedly agree that include-statement is good, but still
$ wc -l /usr/src/sys/amd64/conf/MINI
174 /usr/src/sys/amd64/conf/MINI
And this is just after removing network cards ( (usb)ethernet, (usb)wlan,
raid drivers and firewire) for my pretty standard lenovo t510. There is so
much in
Greetings,
I've been running a RELENG_* box for some time now. I recently slipped the
same CD into an older AMD k7 box, and performed an install cvsup.
I then promptly cd /usr/src/sys/amd64/conf cp GENERIC CUSTOM.
edited CUSTOM to taste, cd /usr/src make buildworld; wait _hours_.
Then
Sorry, that _should_ have read:
RELENG_8
Greetings,
I've been running a RELENG_* box for some time now. I recently slipped the
same CD into an older AMD k7 box, and performed an install cvsup.
I then promptly cd /usr/src/sys/amd64/conf cp GENERIC CUSTOM.
edited CUSTOM to taste, cd
Hello Chris,
I can sell you one :)
Anyway, I belive what's happening is that you should copy GENERIC not
in /usr/src/sys/amd64 directory, but in /usr/src/sys/i386
k7 is a 32 bit CPU so it is i386.
Perhaps you could also try building FreeBSD on your faster box, I did
that when I had 2 32bit
hrm..
Isn't k7 i386?
-alfred
On 11/23/12 11:23 PM, Chris H wrote:
Sorry, that _should_ have read:
RELENG_8
Greetings,
I've been running a RELENG_* box for some time now. I recently slipped the
same CD into an older AMD k7 box, and performed an install cvsup.
I then promptly cd
Thank you! Yes, I _did_ know k7 was actually i(x)86, but figured config(8)
would throw me a bone if it were wrong.
Anyway, I'll take your advice.
Thanks again! MUCH appreciated!
Hello Chris,
I can sell you one :)
Anyway, I belive what's happening is that you should copy GENERIC not
in
14 matches
Mail list logo
