Hi,
I am wondering how one would add support for additional options in the
kernel configuration files. I have found the config(8) program and the
related files '/sys/conf/file' '/sys/conf/options', but am having
trouble finding any documentation leading me beyond there. When I
specify
=yes statement in my kernel config file
and the blanktime and warp_saver load modules don't get created.
I need the options statements for those items so I can compile then into
the kernel.
Thanks
___
freebsd-questions@freebsd.org mailing list
http
.
I have makeoptions NO_MODULES=yes statement in my kernel config file
and the blanktime and warp_saver load modules don't get created.
I need the options statements for those items so I can compile then into
the kernel.
Would it be /usr/src/sys/conf/NOTES ?
%grep warp_saver /usr/src/sys/conf
helpful.
I have makeoptions NO_MODULES=yes statement in my kernel config file
and the blanktime and warp_saver load modules don't get created.
Have a look at man src.conf for dealing with the creation
of modules.
I need the options statements for those items so I can compile
Hi,
what controls how parts of kernel are built, that is, built-in or modular ?
For example, I want to:
- build a kernel that has eveything built in
- build a kernel that has everything possible (what controls the impossible ?)
built as modules
- build a kernel that has mixed support, e.g.
Hi,
On Thu, 25 Oct 2012 06:41:44 + (UTC)
jb jb.1234a...@gmail.com wrote:
Hi,
what controls how parts of kernel are built, that is, built-in or
modular ? For example, I want to:
- build a kernel that has eveything built in
this is normally not possible as some thing conflict which each
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
Just check how a custom kernel is build. You can then build three
versions of it. One with nothing, one with the modules you want and one
with the non-conflicting modules build-in.
Just read the handbook regarding custom
Hi,
On Thu, 25 Oct 2012 07:26:27 + (UTC)
jb jb.1234a...@gmail.com wrote:
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
Just check how a custom kernel is build. You can then build three
versions of it. One with nothing, one with the modules you want and
one with the
Erich Dollansky erichfreebsdlist at ovitrap.com writes:
...
What decides about that (built-in or module) ?
# kldstat -v |grep cd9660
414 cd9660
# kldstat -v |grep ext2fs
151 0xc9911000 11000ext2fs.ko (/boot/kernel/ext2fs.ko)
538 ext2fs
jb
On Thu, 25 Oct 2012 14:51:38 +0700, Erich Dollansky wrote:
The modules are always build, at least to my knowledge. So, you do not
need any options for this. You just need to load them later.
The means of /etc/src.conf can be used to skip certain things
during a kernel + world build. For
jb jb.1234abcd at gmail.com writes:
...
What decides about that (built-in or module) ?
# kldstat -v |grep cd9660
414 cd9660
# kldstat -v |grep ext2fs
151 0xc9911000 11000ext2fs.ko (/boot/kernel/ext2fs.ko)
538 ext2fs
That was already clarified.
jb
I think it's likely that it is a 64-bit installation.
Not sure about that. How could the amd64 OS be installed
and run on a i386 machine?
it cannot.
___
freebsd-questions@freebsd.org mailing list
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an
i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So
I tried both:
you've got into wrong directory
/usr/src/sys/i386/conf is right
/usr/src/sys/amd64/conf is wrong, unless you have 64-bit
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an i686
CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So I
tried both:
you've got into wrong directory
/usr/src/sys/i386/conf is right
/usr/src/sys/amd64/conf is wrong, unless you have 64-bit
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on your
nonsense. 64-bit distribution doesn't run on 32-bit computer.
___
freebsd-questions@freebsd.org mailing list
set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on your
nonsense. 64-bit distribution doesn't run on 32-bit computer.
*PRECISELY* why the OP is having problems. He _is_ trying to build amd64
kernel
...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit distribution on
your
nonsense. 64-bit distribution doesn't run on 32-bit computer
To: Chris Hill ch...@monochrome.org
Cc: RW rwmailli...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may have installed the 64-bit
distribution on your
: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Chris Hill ch...@monochrome.org
Cc: RW rwmailli...@googlemail.com, freebsd-questions@freebsd.org
Subject: Re: Why can't I set my cpu type in kernel config ?
That's the amd64 (64-bit) GENERIC
Jason: It looks like you may
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an i686
CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So I
tried both:
cpu I586_CPU
and:
cpu I686_CPU
(I also tried them both lowercase, like i686_cpu)
But all of these fail:
GENERIC:
make LINT
vi LINT
On Mon, Aug 6, 2012 at 4:53 PM, Jason Usher jushe...@yahoo.com wrote:
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's an
i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working. So I
tried both:
cpu I586_CPU
and:
cpu
On Mon, 6 Aug 2012 16:53:04 -0700 (PDT)
Jason Usher wrote:
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's
an i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working.
So I tried both:
That's the amd64 (64-bit) GENERIC
On Tue, 7 Aug 2012, RW wrote:
On Mon, 6 Aug 2012 16:53:04 -0700 (PDT)
Jason Usher wrote:
I am installing 8.3-RELEASE on an old 900mhz pentium laptop ... it's
an i686 CPU.
By default, GENERIC has HAMMER as the cpu, and that isn't working.
So I tried both:
That's the amd64 (64-bit) GENERIC
I've been wondering for a while now about the accuracy of some of the
comments in /sys/conf/NOTES re: the various COMPAT_* options, and now,
with 9.0-RELEASE already out the door and 10.0-CURRENT as the current
development branch, it seems even more relevant to ask just how
necessary or useful
Hi,
Conrad J. Sabatier wrote:
I've been wondering for a while now about the accuracy of some of the
comments in /sys/conf/NOTES re: the various COMPAT_* options, and now,
with 9.0-RELEASE already out the door and 10.0-CURRENT as the current
development branch, it seems even more relevant to
Hi users!
I`ve got some trouble in the kernel configuration. I think,there is
somebody able to help me
See the attached files.
Many thanks for attention.
dmesg.boot
Description: Binary data
newkernel.2011-10-12
Description: Binary data
___
On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote:
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but
will it make things
Now I think I'll try to rebuild the kernel with options ATA_CAM and drop
device atapicam.
This question needs to be better resolved in time for FreeBSD 9.0-RELEASE.
I cross-post this message to freebsd-curr...@freebsd.org so the developers
will see it. FreeBSD users want to be able to burn
b. f. bf1...@googlemail.com writes:
The handbook does contain some oblique and scattered references to the
new code, or at least to constructs that are common to both the old
and the new code, but the addition of a brief discussion of the
differences between the new and old ATA code in the
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will
it make things go awry? Is ATA_CAM deprecated?
They are redundant and incompatible. atapicam is deprecated, and
ATA_CAM
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will
it make things go awry? Is ATA_CAM deprecated?
They are redundant and incompatible
On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote:
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but
will it make things go
Thomas Mueller mueller6...@bellsouth.net writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
Lowell Gilbert freebsd-questions
Thomas Mueller mueller6...@bellsouth.net writes:
What is the role of options atapicam and device ATA_CAM in kernel config
file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
As far as I can see, ATA_CAM isn't
What is the role of options atapicam and device ATA_CAM in kernel config
file?
Are they redundant? Kernel will build with both these options, but will it
make things go awry? Is ATA_CAM deprecated?
I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools don't
work.
Also, how
On May 30, 2011, at 4:53 PM, Warren Block wrote:
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it
On Mon, 30 May 2011, Warren Block wrote:
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it seems
Warren Block wrote:
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it seems
removal of those
Some time back, there was a post on one of the mailing lists that
suggested it was better to leave either I486_CPU or I586_CPU enabled in
a kernel config even for much newer processors. For performance
reasons, AFAIR. Naturally I didn't save that post or a link to it.
Can anyone find
in a
kernel config even for much newer processors. For performance reasons,
AFAIR. Naturally I didn't save that post or a link to it.
Can anyone find that message, or explain why it would be good to keep
either of those cpu options in a kernel that will only run on much newer
CPUs?
Um, I don't
On Mon, May 30, 2011 at 9:50 AM, Warren Block wbl...@wonkity.com wrote:
Some time back, there was a post on one of the mailing lists that suggested
it was better to leave either I486_CPU or I586_CPU enabled in a kernel
config even for much newer processors. For performance reasons, AFAIR
On Mon, 30 May 2011, Adam Vande More wrote:
Perhaps this is the one you meant?
http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html
That's the one! Thanks!
Actually the two threads touch on the same subject, and it seems
removal of those options is still desirable
On Mon, May 30, 2011 at 6:53 PM, Warren Block wbl...@wonkity.com wrote:
sys/i386/i386/support.s is mentioned, but doesn't seem to have anything
explicitly specific for 586. There are some i686 entries.
A test for cpu_class==CPUCLASS_586 in /sys/i386/isa/npx.c is mentioned in
the thread, but
This feels like a really dumb (as in, the answer should be obvious)
question, but so far it has eluded me: Given an option name in the
kernel configuration file, how -- exactly -- does the directive to
include or exclude that option get translated into particular code
(source lines, .o files,
On 01/02/2011 03:07 AM, per...@pluto.rain.com wrote:
This feels like a really dumb (as in, the answer should be obvious)
question, but so far it has eluded me: Given an option name in the
kernel configuration file, how -- exactly -- does the directive to
include or exclude that option get
In freebsd-questions Digest, Vol 342, Issue 9, Message: 1
On Sat, 25 Dec 2010 04:38:08 -0800 Rob spamref...@yahoo.com wrote:
I read the guidelines in the man pages of config(5) on how to make a
customized
kernel config file:
nooption name [, name [...]]
nooptions name
On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Arguably unforgiving parsing and/or imprecise description. Try eg:
nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT
with no space[s] before comma[s], as is generally conventional.
That doesn't work either.
On Sun, 26 Dec 2010, Bruce Cran wrote:
On Mon, 27 Dec 2010 00:29:47 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Arguably unforgiving parsing and/or imprecise description. Try eg:
nooptions NFSCLIENT, NFSSERVER, NFSLOCKD, NFS_ROOT
with no space[s] before comma[s], as
On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Probably should be easy, but from trying to parse that and lang.l I
get the vague impression (at best) that Rob's original should have
worked?
Too much partying probably .. care to enlighten us?
The NOOPTION
On Sun, 26 Dec 2010, Bruce Cran wrote:
On Mon, 27 Dec 2010 01:50:45 +1100 (EST)
Ian Smith smi...@nimnet.asn.au wrote:
Probably should be easy, but from trying to parse that and lang.l I
get the vague impression (at best) that Rob's original should have
worked?
Too much
Hi,
I read the guidelines in the man pages of config(5) on how to make a customized
kernel config file:
nooption name [, name [...]]
nooptions name [, name [...]]
Remove the specified kernel options from the list of previously
defined options
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
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
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
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,
On Fri, 9 Apr 2010, per...@pluto.rain.com wrote:
Ian Smith smi...@nimnet.asn.au wrote:
http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
rant
This is absolutely the worst section of an otherwise great
handbook ... Nothing short of a rewrite from scratch could
fix it ...
your earlier mail that you wanted to use in-kernel NAT?
If so, rather than divert sockets (using ipfw's divert action) you want:
ipfw_nat_load=YES
libalias_load=YES
2) in the kernel config:
#options IPFIREWALL #firewall
#options IPFIREWALL_VERBOSE #enable logging
libalias=YES # for in-kernel ipfw nat
check.
and in the kernel config:
#options IPFIREWALL #firewall
#options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
options IPFIREWALL_FORWARD
#options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
#options
.
This machine has a custom kernel, so that's not a an issue.
And in /boot/loader.conf:
ipfw_load=YES
ipfw_nat=YES # in-kernel ipfw nat
libalias=YES # for in-kernel ipfw nat
ipfw_nat_load=YES
libalias_load=YES
check.
and in the kernel config:
#options
Ian Smith smi...@nimnet.asn.au wrote:
http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
rant
This is absolutely the worst section of an otherwise great
handbook ... Nothing short of a rewrite from scratch could
fix it ...
As always, I'm sure a patch -- to provide that rewrite --
Adam Vande More writes:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?
Logging is compiled into the modules and there are a few sysctl's.
. AFAIK,
everything else is the same.
http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
So ... double-checking I'm doing this right:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
2) in the kernel config:
#options IPFIREWALL #firewall
#options
On Thu, Apr 8, 2010 at 7:10 AM, Robert Huff roberth...@rcn.com wrote:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
2) in the kernel config:
#options IPFIREWALL #firewall
#options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
#options
On Thu, 8 Apr 2010 08:10:34 -0400 Robert Huff roberth...@rcn.com wrote:
So ... double-checking I'm doing this right:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
yes; see NAT HB 31.9.3
2) in the kernel config:
IMHO, and according to Adam Vandr More, kernel options
IMHO, and according to Adam Vandr More, kernel options are no
longer required.
The original reason I asked was:
30.6.2 Kernel Options
It is not a mandatory requirement to enable IPFW by
compiling the following options into the FreeBSD
I am setting up a router to share one Wi-Fi link between a few computers that
only support CAT-5. Like a wireless access point except wired and wireless
sides are reversed. My question is about the ipfw packet filter. From the
handbook section on NAT, 31.9.3, I can achieve what I need with boot
On Wed, Apr 7, 2010 at 9:51 PM, Gary Dunn o...@aloha.com wrote:
I am setting up a router to share one Wi-Fi link between a few computers
that only support CAT-5. Like a wireless access point except wired and
wireless sides are reversed. My question is about the ipfw packet filter.
From the
Adam Vande More writes:
I am setting up a router to share one Wi-Fi link between a few computers
that only support CAT-5. Like a wireless access point except wired and
wireless sides are reversed. My question is about the ipfw packet filter.
From the handbook section on NAT, 31.9.3,
On Wed, Apr 7, 2010 at 11:28 PM, Robert Huff roberth...@rcn.com wrote:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?
Logging is compiled into the
2009/4/12 Robert Huff roberth...@rcn.com:
As to libusb:
-CURRENT does not need (actually needs to not have)
devel/libusb since its functionality(?) is part of the base system
now (post feb09).
What I did:
This is after installing the new kernel+world, right?
Indeed. I
[posted here because could affect people who don't read curr...@]
I'm about to update a -CURRENT box, and came across this in
src/UPDATING:
GEOM_PART has become the default partition slicer for storage
devices, replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT
2009/4/12 Robert Huff roberth...@rcn.com:
With respect to the changes in the USB stack:
The old system was built in early February, before the new code
went in. The config file has:
device uhci
device ohci
device ehci
device usb
device
On 1/11/09, Aryeh M. Friedman aryeh.fried...@gmail.com wrote:
For the last year I have been using IPI_PREEMPTION in my kernel config
and I know back then it helped quite a bit on the performence of my dual
core... now I am setting a 4 core machine using 7.1pl1 (i386) [on the
dual core I
For the last year I have been using IPI_PREEMPTION in my kernel config
and I know back then it helped quite a bit on the performence of my dual
core... now I am setting a 4 core machine using 7.1pl1 (i386) [on the
dual core I {and will continue} to use -current] and was just wondering
enough to look through /var/run/dmesg.boot, and many devices make
themselves obvious (a DVD-ROM drive is a DVD-ROM drive is a ...) but how
do I identify my motherboard, for example, so I know which lines to
comment out (or conversely, leave in) in the kernel config file?
If there is a good
a little bit lost.
I know enough to look through /var/run/dmesg.boot, and many devices make
themselves obvious (a DVD-ROM drive is a DVD-ROM drive is a ...) but how
do I identify my motherboard, for example, so I know which lines to
comment out (or conversely, leave in) in the kernel config file
Hello All:
I've spent my entire FreeBSD life in /sys/i386 using Intel chips. We
have a new server with the AMD processor listed below and I'm wondering
if:
1) I should stay in /sys/i386 with different configuration variables; or
2) Compile out of /sys/amd64
Any insights would be greatly
On Thursday, January 11, 2007, at 10:20AM, Michael K. Smith - Adhost [EMAIL
PROTECTED] wrote:
Hello All:
I've spent my entire FreeBSD life in /sys/i386 using Intel chips. We
have a new server with the AMD processor listed below and I'm wondering
if:
1) I should stay in /sys/i386 with
im building a system with the amd64, version of freebsd, but the system is a
xeon nacona. the GENERIC kernel config files reads:
machine amd64
cpu HAMMER
ident GENERIC
does cpu HAMMER have a bad effect on a EM64 cpu? should that line be changed,
and if so
Using 6.1, is MAXFILES still honored in the kernel config?
I know I can adjust this via sysctl, but setting it in the kernel config
is more conducive to our deployment methodology.
--
Bill Moran
Collaborative Fusion Inc.
___
freebsd-questions
On 2006-05-16 11:35, Bill Moran [EMAIL PROTECTED] wrote:
Using 6.1, is MAXFILES still honored in the kernel config?
I know I can adjust this via sysctl, but setting it in the kernel config
is more conducive to our deployment methodology.
Yes. The option is still valid even in CURRENT
On Tue, 16 May 2006 19:06:45 +0300
Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2006-05-16 11:35, Bill Moran [EMAIL PROTECTED] wrote:
Using 6.1, is MAXFILES still honored in the kernel config?
I know I can adjust this via sysctl, but setting it in the kernel config
is more conducive
On 2006-05-16 13:28, Bill Moran [EMAIL PROTECTED] wrote:
On Tue, 16 May 2006 19:06:45 +0300
Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2006-05-16 11:35, Bill Moran [EMAIL PROTECTED] wrote:
Using 6.1, is MAXFILES still honored in the kernel config?
I know I can adjust this via sysctl
Could someone please give me a url to a text listing of this file? I
don't have access to fbsd right now.
Thanks.
Steve.
--
___
Play 100s of games for FREE! http://games.mail.com/
___
On Mon, 2006-03-06 at 14:26 -0500, Steve P. wrote:
Could someone please give me a url to a text listing of this file? I
don't have access to fbsd right now.
Thanks.
Steve.
I don't have a specific URL for you, but a suggestion: what about the
CVS interface on freebsd.org? I _assume_ that
On 6/3/06 19:26, Steve P. [EMAIL PROTECTED] wrote:
Could someone please give me a url to a text listing of this file? I
don't have access to fbsd right now.
http://cvsweb.FreeBSD.org/src/sys/i386/conf/GENERIC - click download
Ceri
--
That must be wonderful! I don't understand it at all.
I am trying to Install 6.0 following the procedure in the handbook.
It says the kernel config menu should appear immediately after booting.
I don't see that. For me it goes directly to sysinstall.
How do get to the kernel config menu?
Thanks. John
On Fri, 02 Dec 2005 05:05:41 -0500
John Cox Christine Armond [EMAIL PROTECTED] wrote:
I am trying to Install 6.0 following the procedure in the handbook.
It says the kernel config menu should appear immediately after
booting. I don't see that. For me it goes directly to sysinstall.
How do
On Fri, 2005-12-02 at 10:05, John Cox Christine Armond wrote:
I am trying to Install 6.0 following the procedure in the handbook.
It says the kernel config menu should appear immediately after booting.
I don't see that. For me it goes directly to sysinstall.
How do get to the kernel config
Hi,
In the kernel config file there is a line
options KBD_INSTALL_CDEV # install a CDEV entry in
/dev
I do have this line in my kernel config, but no
such thing as 'CDEV' in the /dev directory.
There is /dev/devctl and /dev/devstat, but I don't
think that is related, or is it?
Can I remove
I was wondering if anyone could provide me an answer to the following
questions. Please keep in mind that by default I learned Unix on a Linux
system, so... please no flames :(.
1) Is there any sort of configuration interface (ncurses, X, etc), or am I
'stuck' with 'manually configuring' a
Hello,
I was wondering if anyone could provide me an answer to the
following questions. Please keep in mind that by default I learned Unix
on a Linux system, so... please no flames :(.
I was a Slackware devotee for about 4 years and a SuSe user for 2
before moving to FreeBSD. Nothing wrong with
On 6/23/2005 20:24, Daniel Gonzalez wrote:
Hello,
I was wondering if anyone could provide me an answer to the
following questions. Please keep in mind that by default I learned Unix
on a Linux system, so... please no flames :(.
Flames??!! What for? Buddy we have better work to do than say My
Hello,
I was wondering if anyone could provide me an answer to the
following questions. Please keep in mind that by default I learned Unix
on a Linux system, so... please no flames :(.
1) Is there any sort of configuration interface (ncurses, X, etc),
or am I 'stuck' with 'manually
On Wed, 22 Jun 2005, Garrett Cooper wrote:
I was wondering if anyone could provide me an answer to the following
questions. Please keep in mind that by default I learned Unix on a Linux
system, so... please no flames :(.
1) Is there any sort of configuration interface (ncurses, X, etc), or
On 2005-06-22 18:04, Garrett Cooper [EMAIL PROTECTED] wrote:
Hello,
I was wondering if anyone could provide me an answer to the
following questions. Please keep in mind that by default I learned Unix
on a Linux system, so... please no flames :(.
That's ok. I was also a Linux user for a
://bob.jonx.com/MYKERNEL.txt is my kernel config
http://bob.jonx.com/MYKERNEL-ERROR.txt is the error I get (sorry for the lack
of line wrap)
Any help would be greatly appreciated!
Cheers!
-Alex
Alex McGeorge Network Security Engineer
Robbins-Gioia, LLC 703-548-7006 x4101
in the body or as
attachments, but I've provided them on the web.
http://bob.jonx.com/MYKERNEL.txt is my kernel config
http://bob.jonx.com/MYKERNEL-ERROR.txt is the error I get (sorry for the lack
of line wrap)
Any help would be greatly appreciated!
googling for this error would have given you
Up untill 1 week ago i have been able to compile my kernel perfectly fine.
However after running a CVSUP i am no longer able to compile my kernel and i
have not changed anything it since i did it quite a few mnths ago. I do not
have sound loaded in my kernel anywhere but rather in a different
Warren [EMAIL PROTECTED] writes:
Up untill 1 week ago i have been able to compile my kernel perfectly fine.
However after running a CVSUP i am no longer able to compile my kernel and i
have not changed anything it since i did it quite a few mnths ago. I do not
have sound loaded in my
1 - 100 of 166 matches
Mail list logo
