I have a running 5.3-RELEASE system that needs a BGE driver upgrade so that
packets with VLAN tags aren't stripped. Is there any way to do this without
upgrading the entire OS? This feature was just added to the driver a month ago.
Thanks,
James
James Kilton [EMAIL PROTECTED] writes:
I have a running 5.3-RELEASE system that needs a BGE driver upgrade so that
packets with VLAN tags aren't stripped. Is there any way to do this without
upgrading the entire OS? This feature was just added to the driver a month
ago.
It's *possible
All I had to do was to disable Kernel Security in /etc/rc.conf..
-V
On Fri, 2005-10-14 at 18:03, Vincent Ngundi wrote:
Objective
-
I'm trying to install native jdk 1.5.0 on a box running FreeBSD
5.3-RELEASE.
Problem
---
When I run make install clean, I'm getting
Hi all
How use this modem in FreeBSD
I have read HandBook, as well as HARDWARE.TXT on Install CD,
but don't find necessary information.
I will be grateful for the help !
Sukharew Andrew
System Administrator
State institution Research of Yamal
Tel.(work) +7(34922)7-16-05
(Internal)
Objective
-
I'm trying to install native jdk 1.5.0 on a box running FreeBSD
5.3-RELEASE.
Problem
---
When I run make install clean, I'm getting a message telling me that I
should mount LINPROCFS before starting to build jdk 1.5.0 and that the
commands kldload linprocfs and
mount
Hi,
I have a problem with updating an FreeBSD 5.3 RELEASE to the latest
version. Everything goes as normal (cvsup (ports standard), make
buildworld, adjusted the kernel and after that an buildkernel and an
installkernel), but at the end the make installworld command fails with
the following
On Monday 10 October 2005 12:55 am, Justin Suyk wrote:
Hi,
I have a problem with updating an FreeBSD 5.3 RELEASE to the latest
version. Everything goes as normal (cvsup (ports standard), make
buildworld, adjusted the kernel and after that an buildkernel and an
installkernel), but at the end
Hi Kent,
Thanx, a wrong system date was indeed the problemen.
Justin.
Kent Stewart wrote:
On Monday 10 October 2005 12:55 am, Justin Suyk wrote:
Hi,
I have a problem with updating an FreeBSD 5.3 RELEASE to the latest
version. Everything goes as normal (cvsup (ports standard), make
Hi list,
I´m using FreeBSD 5.3 - Release in servers (Postfix,
Apache, pf, squid, etc)
I´d like to update for 5.4, but I don´t know how to
do. Is it safe ?
Aguiar
___
Yahoo! Acesso Grátis - Internet
On 07/25/05 11:53 AM, Aguiar Magalhaes sat at the `puter and typed:
Hi list,
I´m using FreeBSD 5.3 - Release in servers (Postfix,
Apache, pf, squid, etc)
I´d like to update for 5.4, but I don´t know how to
do. Is it safe ?
Worked for me. It should be safe.
So long as you follow
Tuc at T-B-O-H wrote:
I assume there are no other messages obvious errors in /var/log/messages?
Nope, I have debug turned all the way up... And just out of the blue
on the 9th at 3am I see :
Jul 9 03:01:30 himinbjorg kernel: pid 49967 (mailwrapper), uid 0: exited on sig
nal 11
However, if you run ktrace on a simple program like ls: ktrace ls
then do a kdump | less, you will see that after finding ls,
/libexec/ld-elf.so.1 is the first thing accessed. So, when things start
working again, /libexec/ld-elf.so.1 is magically fixed, which just makes
no sense.
If the problem is intermittent then I would suspect the hardware (I
know, everyone always says that, but I really have used a brand new
server which segfaulted randomly and it really was a memory problem).
Try building a memtest86 CD from the ports (from a different machine
perhaps) and
Tuc at T-B-O-H wrote:
*If* there are intermittent memory errors, then it could be that SETI
always happens to get them in the data it is dealing with, in which case
it might run perfectly happily but just produce the wrong results.
Memtest is dull, and stops you using your PC, but like
I did the standard tests for 24 hours (21 passes) and it didn't fail.
I ran the 90 minute fading one for 24 hours (8 runs) and it too didn't fail.
It's almost a shame when a test like this passes. It's much easier to
just replace some memory and get on with things than be stuck with an
Tuc at T-B-O-H wrote:
The only pattern I see is that it starts all of a sudden, goes for
a little while, EVERYTHING you try to do fails, I get the
/libexec/ld-elf.so.1: top: Shared object has no run-time symbol table
type errors, and then all of a sudden it goes about its merry way.
On Tuesday 21 June 2005 08:34, Tuc at T-B-O-H wrote:
If you have upgraded to 5.3-RELEASE-p15 why not just upgrade to
5.4-RELEASE-p*?
I'm always nervous going up a release due to my NVIDIA card
Thanks, Tuc
I use the nvidia-driver port with xorg for my nvidia card
Yes. I have a 2 part process I run :
[process elided]
I guess I could re-run it and see if it continues.
I took the plunge and am now at 5.4-RELEASE-p2 I
upgraded my Nvidia driver too.
So far I saw :
Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0:
Tuc at T-B-O-H wrote:
Yes. I have a 2 part process I run :
[process elided]
I guess I could re-run it and see if it continues.
I took the plunge and am now at 5.4-RELEASE-p2 I
upgraded my Nvidia driver too.
So far I saw :
Jun 21 01:24:17 himinbjorg
Pentium II / 433 MHz, VIA 693 chipset
At kernel booting system regulary crashes followed with spontaneous restart.
After many experiments I've figured out it was caused by absence of connected
PS/2 mouse. It's very strange, but when I plug it in, system normaly boots and
is working.
It's very
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run
Tuc at T-B-O-H wrote:
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time symbol
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time symbol table
Sometimes if I wait a few minutes, it'll
Hi all,
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer
rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB/s
when I run
#dd if=/dev/zero of=/usr/junk bs=8192
then do
#iostat 1
Amandeep wrote:
Hi all,
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer
rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB/s
when I run
#dd if=/dev/zero of=/usr/junk bs=8192
then do
#iostat 1
You should probably provide
5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2391.14-MHz 686-class CPU)
Origin = GenuineIntel Id = 0xf29 Stepping = 9
Features=0xbfebfbffFPU,VME,DE,PSE,TSC
Eric Anderson wrote:
Amandeep wrote:
Hi all,
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the
transfer rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB/s
when I run
#dd if=/dev/zero of=/usr/junk bs=8192
then do
In the last episode (May 09), Eric Anderson said:
Eric Anderson wrote:
Amandeep wrote:
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the
transfer rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB/s
when I run
#dd
Dan Nelson wrote:
In the last episode (May 09), Eric Anderson said:
Eric Anderson wrote:
Amandeep wrote:
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the
transfer rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB
Amandeep wrote:
Dan Nelson wrote:
In the last episode (May 09), Eric Anderson said:
Eric Anderson wrote:
Amandeep wrote:
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the
transfer rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate
In the last episode (May 09), Amandeep said:
Amandeep wrote:
The transfer rate is about 15MB/s
when I run
#dd if=/dev/zero of=/usr/junk bs=8192
OK with the above dd
dd if=/dev/ad0 of=/dev/null bs=64k
it gives me 56MB/s. from the start.
So how does the block size makes the
At 03:50 PM 5/9/2005, you wrote:
So how does the block size makes the difference?? What is the
true transfer rate.?
FWIW, there's a nice little disk IO benchmark Bonnie available in the
ports packages. Tests several variations of sequential and random IO. I
don't know how accurate its
Amandeep wrote:
Hi all,
I am using Tyan S2098 MB with 160GB Maxtor ATA Drive and the transfer
rate is very low. FreeBSD 5.3-Release.
Any ideas what is going on here.
The transfer rate is about 15MB/s
when I run
#dd if=/dev/zero of=/usr/junk bs=8192
then do
#iostat 1
'
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.3-RELEASE-p7 #3: Thu Apr 21 13:24:51 EDT 2005
Justin R. Pessa wrote:
On Apr 21 05 06:22PM, Chris McGee wrote:
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual
2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The
usually run
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual
2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The
usually run for a day, give or take, and then they crash. The just
deadlock
On Apr 21, 2005, at 4:22 PM, Chris McGee wrote:
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and
dual 2.4 Ghz Xeons. Both of these machines are running
5.3-Release-p8. The usually run for a day, give
On Thu, Apr 21, 2005 at 06:22:12PM -0400, Chris McGee wrote:
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual
2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The
usually run
Chad Leigh -- Shire.Net LLC wrote:
On Apr 21, 2005, at 4:22 PM, Chris McGee wrote:
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and
dual 2.4 Ghz Xeons. Both of these machines are running
5.3-Release-p8
. Both of these machines are running
5.3-Release-p8. The usually run for a day, give or take, and then
they crash. The just deadlock, no console response, no nothing.
The get power cycled and they are fine for a little while again.
These are configured to be mysql database servers. I can
On Apr 21 05 06:22PM, Chris McGee wrote:
I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR
adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual
2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The
usually run for a day, give or take
Hello all,
My HP ScanJet 3300C will not scan due to being busy. I followed the
steps of the FreeBSD manual and will show its output below in the event
that it may help. I should note that the configuration is as follows:
FreeBSD 5.3-RELEASE // GENERIC KERNEL
Pentium III, 450 MHz
If I had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I copied a sample ports-supfile and edit as follows (just changed
my host)
However I got this message and I cannot figure out what Release
means. In
http://www.freebsd.org/doc
changed it to 5.3-RELEASE. I'd probably check there,
another thing I'll do is try a couple other cvsup sites.
On Apr 7, 2005 1:58 PM, Tetsuji Maverick Rai [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I copied a sample ports-supfile and edit as follows (just changed
my host)
However I got this message and I cannot figure out what Release
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I copied a sample ports-supfile and edit as follows (just changed
my host)
However I got this message and I cannot figure out what Release
On Thu, 7 Apr 2005, Chris wrote:
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I copied a sample ports-supfile and edit as follows (just changed
my host)
However I got this message and I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris wrote:
On Thu, 7 Apr 2005, Chris wrote:
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I copied a sample ports-supfile
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris wrote:
On Thu, 7 Apr 2005, Chris wrote:
On Fri, 8 Apr 2005, Tetsuji Maverick Rai wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I want to keep my ports up to date. in 5.3-release (i386)
So I
Tetsuji Maverick Rai wrote:
*default host=cvsup.jp.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
src-all
I don't think you want tag=. as the default. That would put you the
most current sources for the OS, which may have plenty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Trelvik wrote:
Tetsuji Maverick Rai wrote:
*default host=cvsup.jp.FreeBSD.org *default base=/var/db *default
prefix=/usr *default release=cvs tag=. *default delete
use-rel-suffix
src-all
I don't think you want tag=. as the default.
On Thu, 7 Apr 2005, Tom Trelvik wrote:
Tetsuji Maverick Rai wrote:
*default host=cvsup.jp.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
src-all
I don't think you want tag=. as the default. That would put you
the most current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris wrote:
On Thu, 7 Apr 2005, Tom Trelvik wrote:
Tetsuji Maverick Rai wrote:
*default host=cvsup.jp.FreeBSD.org *default base=/var/db
*default prefix=/usr *default release=cvs tag=. *default delete
use-rel-suffix
src-all
I don't think
On Monday 28 March 2005 16:46, you wrote:
I just upgraded a test machine from 5.3-RELEASE-p5 to
5.3-RELEASE-p6. The make buildworld went fine. When I tried to
make buildkernel it kept saying that: kernel build for GENERIC
complete on xx.xx.xx time
I tried using the old way of bulding
I just upgraded a test machine from 5.3-RELEASE-p5 to 5.3-RELEASE-p6.
The make buildworld went fine. When I tried to make buildkernel it
kept saying that: kernel build for GENERIC complete on xx.xx.xx time
I tried using the old way of bulding a kernel and that went without
issue. I'm
On Mon, Mar 28, 2005 at 04:46:31PM -0600, Josh Paetzel wrote:
I just upgraded a test machine from 5.3-RELEASE-p5 to 5.3-RELEASE-p6.
The make buildworld went fine. When I tried to make buildkernel it
kept saying that: kernel build for GENERIC complete on xx.xx.xx time
I tried using
check http://groups.google.com/groups?q=+5.3-release-i386-disc2.iso+burn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
I'm having trouble building a jail under 5.3 (RELENG_5_3).
I'm following the process in the jail man page and it dies trying to
compile on of the bootstrap tools.
Google and the freebsd-questions archives show several other people
reporting the problem, but I havn't seen anyone post a
George Hartzell wrote:
Can anyone suggest a way forward?
I think I did only make world without DESTDIR and specified it of
course afterwards when doing make installworld.
Greetings,
Robert!
___
freebsd-questions@freebsd.org mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-03-22, Robert Gogolok scribbled these
curious markings:
I think I did only make world without DESTDIR and specified it of
course afterwards when doing make installworld.
make world builds and installs the world onto your current system,
Christopher Nehren wrote:
I think I did only make world without DESTDIR and specified it of
course afterwards when doing make installworld.
make world builds and installs the world onto your current system,
leaving a /usr/obj intact. Unless you specified a DESTDIR for the
installworld, it was
George Hartzell wrote:
=== games/fortune/strfile
/usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for
/usr/src/games/fortune/strfile
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include
/usr/src/games/fortune/strfile/strfile.c
echo
repository via the web
interface, just after the fix for this problem. I moved them into
/usr/src and they seem to work fine. The functional Makefile is
version 1.306.2.1 and Makefile.inc1 is version 1.438.2.5.
I'm including a shar file containing the diffs between my
5.3-RELEASE-p5 system and those
Hello,
I have have downloaded the 5.3-RELEASE four iso set from four
different ftp sites including ftp.freebsd.org. Disc 2 does not
burn, but the others do. The process hangs immediately when
trying. I have tried this on both FreeBSD using burncd on an
Acer CD-RW and Windows 2000 using Nero
I recently setup a box with 5.3 release and enabled PF in order to do
NAT and eventually firewalling and bandwidth control when I become
more acustom to the workings of PF. Regardless of which however, I'm
having tremendous speed issues with the box currently.
Here is my pf.conf:
ext_if=rl1
: Tomas Quintero [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Sent: Sunday, March 20, 2005 11:36 AM
Subject: Slow Performance with OpenBSD's PF on 5.3-RELEASE
I recently setup a box with 5.3 release and enabled PF in order to do
NAT and eventually firewalling and bandwidth control when I become
]
To: freebsd-questions@freebsd.org
Sent: Sunday, March 20, 2005 11:36 AM
Subject: Slow Performance with OpenBSD's PF on 5.3-RELEASE
I recently setup a box with 5.3 release and enabled PF in order to do
NAT and eventually firewalling and bandwidth control when I become
more acustom
Géczi Szabolcs wrote:
after I made a cvsup and buildworld my pptp doesn't work well.
the clients can authenticate succesfully but they cannot reach subnet
except the tunnel's endpoint ip which is 192.168.1.1.
naturally my ppp/pptp configuration are unchanged.
What version were you upgrading
I have had odd behavior like you are describing with cheap
motherboards. I ran all of the memory tests etc, and everything
passed with flying colors. Despite passing all of the tests I could
throw at the hardware, windows 2000 was very unstable. We ultimately
ended up replacing the board.
On
On Wed, Mar 16, 2005 at 07:29:43PM -0800, Jean Lagarde wrote:
Thanks to all who replied. So it seems the consensus is a likely
hardware issue, and I am leaning that way as well now. I will try the
suggestion about disabling ACPI however.
To address some of the other comments, that exact
re,
after I made a cvsup and buildworld my pptp doesn't work well.
the clients can authenticate succesfully but they cannot reach subnet
except the tunnel's endpoint ip which is 192.168.1.1.
naturally my ppp/pptp configuration are unchanged.
any idea?
sz
Géczi Szabolcs wrote:
after I made a cvsup and buildworld my pptp doesn't work well.
the clients can authenticate succesfully but they cannot reach subnet
except the tunnel's endpoint ip which is 192.168.1.1.
naturally my ppp/pptp configuration are unchanged.
any idea?
It's just that you didn't
Hello,
Our fileserver with a raid cabinet attached reboots about every two
weeks. What could be causing this?
OS Version: FreeBSD 5.3-RELEASE-p5
Server brand: Supermicro 6018-P8
Server purpose: Hosting files using Samba 3 and NFS with 400 clients.
SCSI cabinet: 2U EonStore A08-G1410. A RAID5+1
although different scsi adapter and driver. You both ought to compare
notes.
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Leroy van
Logchem
Sent: Wednesday, March 16, 2005 2:36 AM
To: freebsd-questions@freebsd.org
Subject: 5.3-RELEASE-p5 reboots
Sorry for the previous linewrapped question
Hello,
Our fileserver with a raid cabinet attached reboots about every two
weeks. What could be causing this?
OS Version: FreeBSD 5.3-RELEASE-p5
Server brand: Supermicro 6018-P8
Server purpose: Hosting files using Samba 3 and NFS with 400
enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying to run with 1.5GB vice 512MB of RAM.
The system has not had problems so far when I only leave the 512MB stick
in. When I add the 1GB stick
Jean Lagarde wrote:
I have been troubleshooting reboots over the last weekend, I think I
might have enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying to run with 1.5GB vice 512MB of RAM.
The system has
On Wed, Mar 16, 2005 at 12:45:07PM -0800, Jim Pazarena wrote:
I too have a similar problem. I have 7 identical systems. all with
identical MoBo's SCSI hard drives and RAM.
One machine reboots frequently with 5.3 where with 4.9 it never
rebooted. 6 machines are fine. 1 reboots. I changed
On Wednesday 16 March 2005 03:10, Jean Lagarde wrote:
I have been troubleshooting reboots over the last weekend, I think I
might have enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying to run
Thanks to all who replied. So it seems the consensus is a likely
hardware issue, and I am leaning that way as well now. I will try the
suggestion about disabling ACPI however.
To address some of the other comments, that exact CPU-mobo-memory
configuration worked fine running Win2000 for many
I have been troubleshooting reboots over the last weekend, I think I
might have enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying to run with 1.5GB vice 512MB of RAM.
The system has not had problems so
On Tue, Mar 15, 2005 at 07:10:27PM -0800, Jean Lagarde wrote:
I have been troubleshooting reboots over the last weekend, I think I
might have enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying
On 03/15/05 22:10:27, Jean Lagarde wrote:
I have been troubleshooting reboots over the last weekend, I think I
might have enough clues now to get some useful hints from an expert.
FreeBSD 5.3-release (see dmesg below for details)
The problem seems to be with trying to run with 1.5GB vice 512MB
$uname -a
FreeBSD twinmp.tcbug.org 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Wed
Feb 9 16:54:40 CST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TWINMP i386
I am following the directions in man jail to set up a jail on my
system:
D=/here/is/the/jail
cd /usr/src
mkdir -p $D
make world
it was said:
I am following the directions in man jail to set up a jail on
my
system:
D=/here/is/the/jail
cd /usr/src
mkdir -p $D
make world DESTDIR=$D
^
Try changing this line to env DESTDIR=$D make world
cd etc
make distribution DESTDIR=$D
mount_devfs devfs $D/dev
cd $D
On Fri, 11 Mar 2005 22:29:24 -0500, Madhusudan Singh
[EMAIL PROTECTED] wrote:
Anyways, where are the certs installed in FreeBSD ?
There are no default certificates in FreeBSD. They are easy to create
however. Look in the Handbook here:
strongly recommended simply
looking for a Debian-9 or SuSe-9 system. I think I'll simply try that...
I'm looking somewhat into the support for NPTL under FreeBSD 5.3
release i386, and I have come across the following URL:
http://www.unobvious.com/bsd/freebsd-threads.html From this, it
sounds like
Hi
I am trying to set up bincimap with ssl support as a part of a wider qmail
setup for a mailserver.
I have openssl installed (man openssl opens up the right manpage). I want
to know where are the certs installed. The reason is that the FAQ on
bincimap's webpage states :
SSL in Binc IMAP is
for this, is that the platform requires
the NPTL (Native Posix Threads Library).
I'm looking somewhat into the support for NPTL under FreeBSD 5.3 release
i386, and I have come across the following URL:
http://www.unobvious.com/bsd/freebsd-threads.html
From this, it sounds like the LinuxThreads (i.e.
/usr
on FreeBSD.
I'm looking somewhat into the support for NPTL under FreeBSD 5.3
release i386, and I have come across the following URL:
http://www.unobvious.com/bsd/freebsd-threads.html From this, it
sounds like the LinuxThreads (i.e.
/usr/ports/devel/linuxthreads) should do the trick.
That page is 2
Hi,
I am trying to install and configure qmail on FreeBSD 5.3-RELEASE.
I manage to start qmail automatically upon reboot, but whenever I
start another daemon through /usr/local/etc/rc.d/daemonname.sh, I
get this:
%sudo sh /usr/local/etc/rc.d/samba.sh restart
[1] 13163
Starting qmail
%sudo sh
After nearly a week of fighting the dual problem of OpenBSD 3.6 release
freezing on my hardware, and some rather odious personalities on the
[EMAIL PROTECTED] mailing list, I decided to install FreeBSD 5.3-RELEASE on the
web server I am deploying and stick to it.
I went through the webpage
On Tuesday 01 March 2005 10:44 am, Madhusudan Singh wrote:
After nearly a week of fighting the dual problem of OpenBSD 3.6
release freezing on my hardware, and some rather odious personalities
on the [EMAIL PROTECTED] mailing list, I decided to install FreeBSD
5.3-RELEASE on the web server I
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Anthony
Atkielski
Sent: Sunday, February 27, 2005 2:10 PM
To: freebsd-questions@freebsd.org
Subject: Re: WRITE_DMA errors on SATA drive under 5.3-RELEASE
Mike Tancsa writes:
Could be a bad sector
Ted Mittelstaedt writes:
Rule of thumb on IDE hard drives, if they show more than a few errors
with a tool like smartmon, they need to be thrown in the garbage.
Seems prudent to me, but right now I don't have the budget to replace
this drive (yes, 40 GB IDE drives are cheap, but I don't have
I've gotten two messages like the ones below today on my production server
(5.3-RELEASE):
messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying (2
retries left) LBA=4848803
messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out
What do these messages
On Sun, Feb 27, 2005 at 03:53:30PM +0100, Anthony Atkielski wrote:
messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying
(2 retries left) LBA=4848803
messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out
[...]
Is there a way to work backwards
1 - 100 of 366 matches
Mail list logo
