I just discoverd that on a machine I recently rebuilt, I have a dead link
to /usr/share/doc/handbook. Is this not installed now?
same problem. and i am a religious cvsupper.
randy
___
[EMAIL PROTECTED] mailing list
but /usr/share/doc/handbook IS the link,
right? The book's real path is:
/usr/share/doc/en_US.ISO8859-1/books/handbook
yep, if you like antiques. which is the problem.
randy
___
[EMAIL PROTECTED] mailing list
I just discoverd that on a machine I recently rebuilt, I have a dead link
to /usr/share/doc/handbook. Is this not installed now?
same problem. and i am a religious cvsupper.
cvsup won't help, unless you build the whole thing from sources
that is what i do.
in which case you would
one basic question is where is the normal place for the
handbook? is is /usr/doc or /usr/share/doc? an iso
install puts in in /usr/share/doc, and a 'normal' cvsup
puts it in /usr/doc because one normally (yes, there
is no normal:-) has
*default base=/usr
randy
/usr/doc is the canonical place for the sources, which should get
installed into /usr/share/doc after a cd /usr/doc;make install.
close to bottom line:
doc is not made with buildworld. i guess it's off-planet.
or maybe just outta this world.
one needs to
cd /usr/ports/textproc/docproj
Suddenly, after upgrading of my FreeBSD-Stable box I got message from
VMWare: VMware Workstation PANIC: BUG F(571):1607 bugNr=2302.
portupgrade -fR emulators/vmware2
randy
___
[EMAIL PROTECTED] mailing list
Soft updates are disable on / by default because of the chicken
and egg problem of runing tunefs on /.
If that's the problem, then why doesn't sysinstall enable it by default
when partitioning for a new install?
Oliver Stone said it was because there's a conspiracy.
it's the downdraft from
I just finished upgrading a freebsd 4.6 machine to the newest
RELEASE using CVSUP and the whole buildworld procedure.
the compiling went ok ..and the system is up ,,,however there
are a few problems...
...
apache is giving me an error saying shared library libmm.so.12
can not be found.
i
386 very current
i have been unable to get apache not to segv on one server for a while now.
i tried the php rebuild
i tried clearing obj, full system build, full ports force rebuild, ...
i just tried
If you have a backup of php/extensions.ini from before you did your
updates, it would be
did you ever try comment out the three extensions I mentioned in my
previous email? That fixed it right up for me.
i did not have those extensions at all. or maybe i did not understand
where they are.
randy
___
freebsd-questions@freebsd.org mailing
Could you guys google for fixphpextorder.sh and see if that would help.
It did help me last year when I had this problem and I always rely on it
during upgrade, but I'm not saying I guarantee it will:-)
still cores
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22 configuration:
Segmentation fault (core dumped)
Starting apache22.
Segmentation fault (core dumped)
Apache (1.3) would core dump when pgsql (from php 5.2.5) was loaded as
a module. Commenting this module out from
I'm pretty fed up with Intel's ICH9R interface too so I'm hoping
(crosses fingers) that I'll be able to afford an Adaptec card of some
flavor that's compatible with -CURRENT.
If you are looking to move up, look at the 3ware RAID cards. Not sure
which models work with FreeBSD, but these card
FreeBSD isn't much used within the University (I understand) and has a
(comparatively) poor security record.
unlike linux or windoze, rofl
randy
___
freebsd-questions@freebsd.org mailing list
but i look in syslogs of some FreeBSD internet server and there is a great
evidence that some botnets are (again) tryng simple combination of
uid/pwd.
/usr/ports/security/sshguard-*
randy
___
freebsd-questions@freebsd.org mailing list
15 matches
Mail list logo
