Hello,
Just to confirm my suspicions, while compiling apache 2.0.55 on a fresh
install of FreeBSD 5.4 with fresh cvsup'd ports tree I got an error, the
error stated : Bus error.
This is a hardware fault is it not? or is it some other error? It had
been compiling for a fair few minutes before t
On Wed, Nov 02, 2005 at 08:06:59PM -0800, Sean McNeil wrote:
> Was this pulled from the release? Was autofs support suppose to go in
> (and was actually built at one point), then removed from 6-stable?
An incomplete autofs was briefly in the tree and then removed.
-- Brooks
--
Any statement of
This is very confusing:
I have a mount_autofs man page that is installed. I do not know when it
was placed in there, but it has a date of Nov 9, 2004
on /usr/share/man/man8/mount_autofs.8.gz.
The history, however, says "The mount_autofs utility first appeared in
FreeBSD 6.0." which is not true.
On 03/11/2005, at 9:09 AM, David Wolfskill wrote:
On Wed, Nov 02, 2005 at 04:39:30PM -0500, Ken Menzel wrote:
...
If I include GENERIC can I comment out the following?
#cpuI486_CPU
#cpuI586_CPU
Well, it's your (copy of) the file; I suppose you can do whatever you
wan
I have recently purchased a number HP DX5150 SFF desktops with idea of
using them as basic infrastructure servers (e.g. DNS, DHCP, and
firewall). I prefer to use -stable versions of FreeBSD and OpenBSD.
Following are the specs on the boxes:
HP dx5150
AMD Sempron 3000+
ATI Radeon Xpress 200 ch
Ken Menzel wrote:
options INVARIANT_SUPPORT
nooptions WITNESS
nooptions WITNESS_SKIP_SPIN
If I include GENERIC can I comment out the following?
#cpuI486_CPU
#cpuI586_CPU
Does this make any difference? I have always done this out of habit.
would it become
in
On Wed, Nov 02, 2005 at 04:39:30PM -0500, Ken Menzel wrote:
> ...
> If I include GENERIC can I comment out the following?
> #cpuI486_CPU
> #cpuI586_CPU
Well, it's your (copy of) the file; I suppose you can do whatever you
want to with it. :-)
> Does this make any differ
options INVARIANT_SUPPORT
nooptions WITNESS
nooptions WITNESS_SKIP_SPIN
If I include GENERIC can I comment out the following?
#cpuI486_CPU
#cpuI586_CPU
Does this make any difference? I have always done this out of habit.
would it become
nocpu I486_CPU ?
Or
* rihad, 2005-10-08 :
> Now I want to do a binary upgrade to FreeBSD 5.4, but the new
> sysinstall's disklabel editor only recognizes the IDE disks and does not
> consider the GEOM mirror (mentioned in /etc/fstab, btw). How do I go
> about this? Thanks.
Did you try "gmirror load" from a sysins
On Nov 2, 2005, at 2:43 AM, Rob wrote:
My point is then to follow this strategy also for X:
instead of a DEFAULTS file, have a /etc/rc.d/xdm
script, which starts X and loads the modules io/mem
if needed.
but these devices are also needed for things like netstat. you
pretty much need to lo
On Wed, 2 Nov 2005, Rob wrote:
Kris Kennaway wrote:
You missed the part where I said that the error is commonly reported by
people who have chosen not to build modules.
The DEFAULTS construction is put in place to help 'novices' not to do
stupid things (as removing io/mem).
However, doe
Kris Kennaway wrote:
>
> You missed the part where I said that the error is
> commonly reported by people who have chosen not to
> build modules.
The DEFAULTS construction is put in place to help
'novices' not to do stupid things (as removing
io/mem).
However, does 'building a kernel without mod
On Tue, 1 Nov 2005 23:43:29 -0800 (PST)
Rob <[EMAIL PROTECTED]> wrote:
> My point is then to follow this strategy also for X:
> instead of a DEFAULTS file, have a /etc/rc.d/xdm
> script, which starts X and loads the modules io/mem
> if needed.
Not everybody uses xdm, some use the KDE vers
On Tue, Nov 01, 2005 at 11:43:29PM -0800, Rob wrote:
> Kris Kennaway wrote:
> >
> > You've clearly never spent much time on the FreeBSD
> > support forums, where every few days someone posts
> > for help
> >
> > 1) with an error caused by removing one of those
> > "Do not remove this!" lines, and
2005/11/1, Scott Long <[EMAIL PROTECTED]>:
> The future direction is that FreeBSD will continue to be friendly to
> novice users while still affording power users the control that they
> seek.
Scott, that's right.
but: we can have our personal way to shoot in the foot, we can use
big, BIG, advic
15 matches
Mail list logo
