Subhro,
On Sat, 28 May 2005, Subhro wrote:
> This is not something new or unexpected. Windows are Linux run happily
> on a lot of garbage grade hardware. But FreeBSD is very fussy about
> hardware. Thats the reason why a Linux box CAN create strange situations
> due to hardware. But a FreeBSD box
Hi Doug,
On Fri, May 20, 2005 at 01:14:51PM -0700, Doug White wrote:
> On Wed, 18 May 2005, Bruce Burden wrote:
> >
> >Hi Doug,
> >
> > well, pulling cards demonstrated where the problem lie, but it
> >was not a hardware problem. By chance, I happened upon the "options
> >A
On Sat, May 28, 2005 at 10:54:16PM +0200, K?vesd?n G?bor wrote:
> It is a single processor system. Those cron scripts are to verify
> whether my processes are run. So, there isn't such simultaneous runs.
> They are small scripts, that send a SIGCHLD to the processes they are
> responsible for, a
Hi!
What do you think in minor change to /etc/rc.d/var:
--- var.origSun May 29 01:05:47 2005
+++ var Sun May 29 01:06:12 2005
@@ -28,7 +28,7 @@
#
# PROVIDE: var
-# REQUIRE: mountcritlocal
+# REQUIRE: mountcritremote
. /etc/rc.subr
If there are no NFS mountpoints at /etc/fstab, both
It is a single processor system. Those cron scripts are to verify
whether my processes are run. So, there isn't such simultaneous runs.
They are small scripts, that send a SIGCHLD to the processes they are
responsible for, and if they don't find the processes running, they
restarts them. I've b
Hi!
This PR is about one year old. I've just submit a patch to
FreeBSD-5.4-RELEASE, which worked just fine for me.
Could anybody look at this PR? The patch is very simple but helpful:
--- clone_root.orig Sat May 28 18:20:09 2005
+++ clone_root Sun May 29 00:12:28 2005
@@ -79,7 +79,7 @@
SY
> Im currently running fedora core 2. I was informed about this list by a
> friend running freebsd. Now what I wanted to ask is whether any one of you
> has used any redhat flavours, if so, what is the distinct advantage of
> moving to freebsd ( i have never used it), i cant just migrate because th
TB --- 2005-05-28 18:15:55 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-28 18:15:55 - starting RELENG_5 tinderbox run for i386/i386
TB --- 2005-05-28 18:15:55 - cleaning the object tree
TB --- 2005-05-28 18:16:30 - checking out the source tree
TB --- 2005-05-28 18:16:30 - cd
TB --- 2005-05-28 16:33:16 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-28 16:33:16 - starting RELENG_5 tinderbox run for amd64/amd64
TB --- 2005-05-28 16:33:16 - cleaning the object tree
TB --- 2005-05-28 16:33:47 - checking out the source tree
TB --- 2005-05-28 16:33:47 - c
On 5/28/2005 22:15, Remi Degruson wrote:
Hello,
my problem was due to a bad ide cable. I replace it and all work well.
I am surprised , this cable was ok with linux.
This is not something new or unexpected. Windows are Linux run happily
on a lot of garbage grade hardware. But FreeBSD is ve
On Sat, May 28, 2005 at 07:10:58PM +0200, K?vesd?n G?bor wrote:
> Hello,
>
> since I upgraded to 5.3-p15 from 5.3 the cron daemon sometimes send me
> an e-mail, that contains "Abort trap". Nothing seems to go wrong anyway,
> but it might be a source of troubles, if my cron scripts can't run norm
Phares Kariuki wrote:
> Hi,
>
> Im currently running fedora core 2. I was informed about this list by a
> friend running freebsd. Now what I wanted to ask is whether any one of you
> has used any redhat flavours, if so, what is the distinct advantage of
> moving to freebsd ( i have never used i
Hello,
since I upgraded to 5.3-p15 from 5.3 the cron daemon sometimes send me
an e-mail, that contains "Abort trap". Nothing seems to go wrong anyway,
but it might be a source of troubles, if my cron scripts can't run normally.
Do You know anything about this effect?
Cheers,
Gábor Kövesdán
_
Hello,
my problem was due to a bad ide cable. I replace it and all work well.
I am surprised , this cable was ok with linux.
On Sat, May 21, 2005 at 06:03:01PM +0200, Remi Degruson wrote:
> Hello,
>
> On one of my computers, the 5.4 RELEASE bootonly disc don't want to write on
> my hdd.
> The
TB --- 2005-05-28 15:17:55 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-28 15:17:55 - starting RELENG_5 tinderbox run for alpha/alpha
TB --- 2005-05-28 15:17:55 - cleaning the object tree
TB --- 2005-05-28 15:18:24 - checking out the source tree
TB --- 2005-05-28 15:18:24 - c
Please don't send mailing list messages to postmaster. Many of us filter that
as a magic address and therefore find spurious messages outside of where
they're supposed to be.
Thanks!
pgpaIASkkjKSU.pgp
Description: PGP signature
Torfinn Ingolfsen wrote:
On Sat, 28 May 2005 11:43:14 +0300
Phares Kariuki <[EMAIL PROTECTED]> wrote:
Im currently running fedora core 2. I was informed about this list by
a friend running freebsd. Now what I wanted to ask is whether any one
of you has used any redhat flavours, if so, wh
Oh, something else to try:
I checked through my notes and discovered that I had gotten UDP to work in
a similar configuration before. What I did was bind the IP address to
fxp0 instead of em0. By doing this, the kernel seems to send the data at
a pace suitable for the slow interface.
-Jon
On
Scott Long wrote:
Yeah, and what I'm trying to do is smooth the bumps for the long term.
The 4.x->5.x transition was simply a gigantic mess for users, and it was
largely a function of it being 4+ years in the making.
It still _is_ a gigantic mess. My hosted 5.3-stable server just
crapped it
Today, I decided to merge two machines into one ... faster CPU, double the
RAM, etc ... but, seem to having a problem when trying to enable the SATA
drives ...
Namely, there are 4 drives in this box .. two IDE (ad0 and ad1) and two
SATA (ad2 and ad3) ...
When I try and boot with just the 2
On Sat, 28 May 2005 10:29:17 +0300
Daniel <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Here are some links about the BitDefender for FreeBSD Mail Servers line.
>
> http://www.bitdefender.com/bd/site/products.php?p_id=52
>
> ftp://ftp.bitdefender.com/pub/freebsd/mailserver/RELEASE_NOTES
>
> As a s
TB --- 2005-05-27 17:42:52 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 17:42:52 - starting RELENG_5 tinderbox run for amd64/amd64
TB --- 2005-05-27 17:42:52 - cleaning the object tree
TB --- 2005-05-27 17:43:30 - checking out the source tree
TB --- 2005-05-27 17:43:30 - c
On Sunday 22 May 2005 06:24 pm, Kirk Strauser wrote:
> On Friday 20 May 2005 10:20 pm, John Baldwin wrote:
> > I have a patch to make the PIR code trust the BIOS in this case over the
> > $PIR table that you can test if you want. Actually, I committed the
> > patch finally a while ago. It is rev
Hi all,
Here are some links about the BitDefender for FreeBSD Mail Servers line.
http://www.bitdefender.com/bd/site/products.php?p_id=52
ftp://ftp.bitdefender.com/pub/freebsd/mailserver/RELEASE_NOTES
As a side note, BitDefender is a Romanian brand/product. It is
developed by Softwin. The link
On Friday 27 May 2005 23:22, Matthias Buelow wrote:
> Scott Long wrote:
> > Yeah, and what I'm trying to do is smooth the bumps for the long
> > term. The 4.x->5.x transition was simply a gigantic mess for users,
> > and it was largely a function of it being 4+ years in the making.
>
> It still _is
On Sat, 28 May 2005 11:43:14 +0300
Phares Kariuki <[EMAIL PROTECTED]> wrote:
> Im currently running fedora core 2. I was informed about this list by
> a friend running freebsd. Now what I wanted to ask is whether any one
> of you has used any redhat flavours, if so, what is the distinct
> advant
TB --- 2005-05-27 23:38:56 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 23:38:56 - starting RELENG_5 tinderbox run for sparc64/sparc64
TB --- 2005-05-27 23:38:56 - cleaning the object tree
TB --- 2005-05-27 23:39:20 - checking out the source tree
TB --- 2005-05-27 23:39:20
Hi folks,
I have sinned, I have forgotten to configure a dump device. I do have
a debug kernel compiled though (I think), so maybe someone can help
me figure out what's happening here. Nothing in particular going on,
server has been up for a few weeks. Dual opteron machine, running
FreeBS
On 5/26/05, Matthias Buelow <[EMAIL PROTECTED]> wrote:
>
> >> Others don't see this though, and in other cases it was *definitively
> >> proven* to be caused by the issue I mentioned. I'll have to think
> >> more about what to try next..thanks for running the tests.
> >
> > Perhaps it's something
Scott Long wrote:
No, 4.x is stale enough. If you need help debugging your computer,
please let me know and I will personally fix it for you.
Sorry for letting some steam out.. I guess I shouldn't answer directly
after a crash. Frankly, I don't know what caused it, so just ignore my
rant.
Hi,
Im currently running fedora core 2. I was informed about this list by a
friend running freebsd. Now what I wanted to ask is whether any one of you
has used any redhat flavours, if so, what is the distinct advantage of
moving to freebsd ( i have never used it), i cant just migrate because th
On Friday 27 May 2005 02:48 pm, you wrote:
> The patch should change the IRQ numbers and also print out a line about how
> it is trusting your BIOS over the $PIR, so I think you didn't backport the
> patch correctly or boot the patched kernel somehow.
Here's what I did:
1) Install 5.4 to an empt
> I temporarily moved the disk to a recent 5.4 desktop machine equipped
> with the same chipset and the timeouts stopped, so it appears that the
> problem is not with the disk.
So the problem exists on 5.S and not on 5.4-RELEASE? or is it vice versa?
___
Matthias Buelow wrote:
Scott Long wrote:
Yeah, and what I'm trying to do is smooth the bumps for the long term.
The 4.x->5.x transition was simply a gigantic mess for users, and it was
largely a function of it being 4+ years in the making.
It still _is_ a gigantic mess. My hosted 5.3-stab
TB --- 2005-05-27 19:25:14 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 19:25:14 - starting RELENG_5 tinderbox run for i386/i386
TB --- 2005-05-27 19:25:14 - cleaning the object tree
TB --- 2005-05-27 19:25:55 - checking out the source tree
TB --- 2005-05-27 19:25:55 - cd
On 5/27/05, Jovan Ross <[EMAIL PROTECTED]> wrote:
> I am experiencing problems keeping FreeBSD 5.4 connected. I have uptimes of
> 5 or 6 days - sometimes 10 or 11, then, without freezing the machine
> totally, it stops responding to network traffic. I get DOS attacked every
> once and a while and m
Hi, Jovan,
在 2005-05-27五的 13:16 -0400,Jovan Ross写道:
> I am experiencing problems keeping FreeBSD 5.4 connected. I have uptimes of
> 5 or 6 days - sometimes 10 or 11, then, without freezing the machine
> totally, it stops responding to network traffic. I get DOS attacked every
> once and a while
Ignore ... just figured it out ... had UDMA turned off for those drives in
the BIOS :( Turned it back on, and all four drives come up as expected
again ...
Thanks ...
On Sat, 28 May 2005, Marc G. Fournier wrote:
Today, I decided to merge two machines into one ... faster CPU, double the
TB --- 2005-05-27 22:05:15 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 22:05:15 - starting RELENG_5 tinderbox run for ia64/ia64
TB --- 2005-05-27 22:05:15 - cleaning the object tree
TB --- 2005-05-27 22:05:40 - checking out the source tree
TB --- 2005-05-27 22:05:40 - cd
Oh, something else to try:
I checked through my notes and discovered that I had gotten UDP to work in
a similar configuration before. What I did was bind the IP address to
fxp0 instead of em0. By doing this, the kernel seems to send the data at
a pace suitable for the slow interface.
-Jon
On
TB --- 2005-05-27 20:47:12 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 20:47:12 - starting RELENG_5 tinderbox run for i386/pc98
TB --- 2005-05-27 20:47:12 - cleaning the object tree
TB --- 2005-05-27 20:47:43 - checking out the source tree
TB --- 2005-05-27 20:47:43 - cd
TB --- 2005-05-27 16:27:09 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-05-27 16:27:09 - starting RELENG_5 tinderbox run for alpha/alpha
TB --- 2005-05-27 16:27:09 - cleaning the object tree
TB --- 2005-05-27 16:27:40 - checking out the source tree
TB --- 2005-05-27 16:27:40 - c
42 matches
Mail list logo