João Carlos Mendes Luís wrote:
Instead of block compression, wouldn't it be better (and maybe easier)
to use file compresion, in a VFS layer (and a threaded daemon)?
Better, yes. Easier very much not, since I know something about GEOM
(actually, ggate), and nothing about VFS and kernel
I have had this problem now with at least 3 FreeBSD servers over a period of
about 2 years. I had put it down to some hardware problem but it seems to be
too much of a coincidence with 3 different machines doing the same thing.
The first time was when I put 4.5-RELEASE on a brand new Dell
Hi,
I'd like to use the SigmaTel USB IrDA dongle to connect my
computer (FreeBSD 4.10-STABLE) and my mobile phone (Samsung X600).
According to my log, the dongle is recognized:
/kernel: ugen0: Sigmatel Inc IrDA/USB Bridge, rev 1.10/0.08, addr 2
So what do I do now? I've searched everywhere and
In the last episode (Sep 30), ALeine said:
I'd like to use the SigmaTel USB IrDA dongle to connect my computer
(FreeBSD 4.10-STABLE) and my mobile phone (Samsung X600). According
to my log, the dongle is recognized:
/kernel: ugen0: Sigmatel Inc IrDA/USB Bridge, rev 1.10/0.08, addr 2
So
Jim Durham writes:
| I have had this problem now with at least 3 FreeBSD servers over a period of
| about 2 years. I had put it down to some hardware problem but it seems to be
| too much of a coincidence with 3 different machines doing the same thing.
|
| The first time was when I put
Could there be some more elaboration on these memory issues.
From the way you described it, it sounds like if you have two machines
serving the same function with the same load, and one machine has 512Mb
and the other has 2.5Gb, the one with more memory might be prone to be
more problems.
Why
On Thu, Sep 30, 2004 at 10:03:00AM -0400, Jim Durham wrote:
I have had this problem now with at least 3 FreeBSD servers over a period of
about 2 years. I had put it down to some hardware problem but it seems to be
too much of a coincidence with 3 different machines doing the same thing.
On Friday 01 October 2004 12:36 pm, Doug Ambrisko wrote:
Jim Durham writes:
| I have had this problem now with at least 3 FreeBSD servers over a period
| of about 2 years. I had put it down to some hardware problem but it seems
| to be too much of a coincidence with 3 different machines doing
On Friday 01 October 2004 06:38 pm, Kris Kennaway wrote:
On Thu, Sep 30, 2004 at 10:03:00AM -0400, Jim Durham wrote:
I have had this problem now with at least 3 FreeBSD servers over a period
of about 2 years. I had put it down to some hardware problem but it seems
to be too much of a
On Fri, Oct 01, 2004 at 08:23:04PM -0400, Jim Durham wrote:
Actual spontaneous reboots are very rare
These are very rare except they seem to happen about once a day for a
while and then stop... very strange..
and usually caused by hardware problems (e.g. faulty power supply,
On Friday 01 October 2004 06:38 pm, Kris Kennaway wrote:
Do you have ddb enabled?
I just recompiled the kernel (4.10 patchlevel 3) and installed it. It's in use
right now and I can't reboot it, but it may do so for me! 8- ). If not,
I'll do it early tommorow AM. I used options DDB and
On Fri, Oct 01, 2004 at 08:37:34PM -0400, Jim Durham wrote:
On Friday 01 October 2004 06:38 pm, Kris Kennaway wrote:
Do you have ddb enabled?
I just recompiled the kernel (4.10 patchlevel 3) and installed it. It's in use
right now and I can't reboot it, but it may do so for me! 8- ).
Jim Durham writes:
[ Charset ISO-8859-1 unsupported, converting... ]
| On Friday 01 October 2004 12:36 pm, Doug Ambrisko wrote:
| Jim Durham writes:
| | I have had this problem now with at least 3 FreeBSD servers over a period
| | of about 2 years. I had put it down to some hardware problem but
I just want to drop a line to you folks (and to Bill Paul in particular)
to express my appreciation for your work. I received my new laptop today
after my old one finally succumbed to a combination of old age and ancient
coffee spills. I installed 5.3-BETA6 on it immediately, no trouble, it
knew
On Oct 1, 2004, at 7:23 PM, Jim Durham wrote:
These are very rare except they seem to happen about once a day
for a
while and then stop... very strange..
and usually caused by hardware problems (e.g. faulty power supply,
overheating CPU, bad RAM).
Possible, but if so, the hardware fixed
Hi, re:
The odd thing was that it was happening at virtualy
the same time every morning
[...]
Then, they both just *stopped doing it by themselves* with no apparent
correlation to anything installed software-wise. Neither server has had any
problem for over a year now.
* What was the
On Friday 01 October 2004 11:34 pm, Bruce R. Montague wrote:
Hi, re:
The odd thing was that it was happening at virtualy
the same time every morning
[...]
Then, they both just *stopped doing it by themselves* with no apparent
correlation to anything installed software-wise. Neither
17 matches
Mail list logo