antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
You left out some devices that are required by other devices in your
configuration. for
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
Or just stay with
Jamie Paul Griffin ja...@kode5.net writes:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never
got such a one; here is my kernel configuration file and the
building
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ]
Jamie Paul Griffin ja...@kode5.net writes:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I have a problem when I try to build my own kernel. I had never
got
On Thu, 23 Aug 2012 17:23:59 +0100, Jamie Paul Griffin wrote:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ]
Jamie Paul Griffin ja...@kode5.net writes:
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
antonin tessier antonintess...@live.fr writes:
I
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
On Sun, 19 Aug 2012 19:43:14 -0400
Michael Powell articulated:
{snip}
Keep in mind whenever you install a new kernel your present kernel
(and its matching modules) get moved to kernel.old. What this means
is that the GENERIC you have with a base install will be moved to
kernel.old and can be
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
Keep in mind whenever you install a new kernel your present kernel (and its
matching modules) get moved to kernel.old. What this means is that the
GENERIC you have with a base install will be moved to kernel.old and can be
used
== Jerry wrote on Mon 20.Aug'12 at 8:11:17 -0400 ==
I inquired several years ago about the possibility of changing the
renaming format into something like: kernel_##_YY-MM-DD.old. The ##
would be incremented with each successive build on a given day. I
thought it would alleviate just the
On Mon, 20 Aug 2012 14:13:44 +0100, Jamie Paul Griffin wrote:
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
Keep in mind whenever you install a new kernel your present kernel (and its
matching modules) get moved to kernel.old. What this means is that the
GENERIC you have
Polytropon writes:
Very good point! I'd clear the /usr/src/obj directory as pointed out,
then build a generic kenel, install it and boot from it. Then you
know you've got a working kernel to fall back on.
You could then make a copy of that kernel, e. g. from its initial
On Mon, 20 Aug 2012 09:46:30 -0400, Robert Huff wrote:
Polytropon writes:
Very good point! I'd clear the /usr/src/obj directory as pointed out,
then build a generic kenel, install it and boot from it. Then you
know you've got a working kernel to fall back on.
You could then
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
antonin tessier wrote:
Hi,
I have a problem when I try to build my own kernel. I had never got such a
one; here is my kernel configuration file and the building errors that it
makes.
[snip]
# make kernel KERNCONF=GOLLUM
MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM
Stop in
14 matches
Mail list logo
