On Thursday 21 July 2005 16:42, caleb wrote:
The port is definitely sio1/cuaa1. I tried to run ircomm while irs was
still running and got;
Why?
No offence but it's always worth trying something different when stuff isn't
working :)
cannot open pty
I killed irs and used;
ircomm -d
On Jul 21, 2005, at 7:00 AM, Kris Kennaway wrote:
On Mon, Jul 18, 2005 at 11:58:54AM +0200, Eirik ?verby wrote:
Hi,
I reported this before, but I am very surprised that it is still the
case:
(This is from the last time it happened; this time the box rebooted
and cleared the serial console
Eirik ?verby wrote:
...
However, since I seem to be the only one who has noticed this,
perhaps I'm the last person on earth to routinely use serial terminal
switches instead of KVM switches to do my admin work?
No, I recently installed 3 5.4-R production machines that do not have
video cards,
On Thu, Jul 21, 2005 at 10:56:54AM +0200, Eirik verby wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 00
fault virtual address = 0x1c
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0620b5f
stack pointer =
Hi.
Having enough opportunities to do crash recovery with kern/83375 open
and some of my services not yet moved back to FreeBSD 4, I noticed that
often it crashes just after (or perhaps during) mirroring of a directory
tree. The mirroring involves creating a directory with in it 80
subdirectories
On Wed, Jul 20, 2005 at 08:43:33PM -0700, Alexey Yakimovich wrote:
My advice to FreeBSD release engineering team:
- do more testing;
- have it tested with hardware what was published in Hardware Notes;
- do not release it for production if it is not in production quality;
- reread again what
On Thu, 21 Jul 2005, Eirik Øverby wrote:
The above panic will show up occasionally when logging out from a
serial console (i.e. ctrl-D, logout, exit, whatever). This is
EXTREMELY BAD, as it will crash an otherwise perfectly healthy box at
random - and renders the serial console useless.
On Wed, 20 Jul 2005, Steve wrote:
I've found tons of emails, news messages, listserv messages, and even
some bug reports of this seemingly common error.
So, I had been running 5.2 on a server, and, updated to 5.3. Got the
READ_DMA and WRITE_DMA error and retries. So, figuring it might be a
On Wed, 20 Jul 2005, Alexey Yakimovich wrote:
My advice to FreeBSD release engineering team:
- do more testing;
- have it tested with hardware what was published in Hardware Notes;
- do not release it for production if it is not in production quality;
- reread again what was written by
On Thursday 21 July 2005 19:27, Marc Olzheim wrote:
Thank you for expressing my exact same sentiments. I'm still a huge
FreeBSD fan and switching to anything else (well, perhaps DragonFly)
seems out of the question, but my faith is being tested a lot lately.
Having switched some of my
On Jul 21, 2005, at 12:16 PM, Robert Watson wrote:
On Thu, 21 Jul 2005, Eirik Øverby wrote:
The above panic will show up occasionally when logging out from a
serial console (i.e. ctrl-D, logout, exit, whatever). This is
EXTREMELY BAD, as it will crash an otherwise perfectly healthy
box
On Thu, 21 Jul 2005, Eirik Øverby wrote:
I've only seen the issue when logging out of a serial console session,
and had previously hypothesized that it had to do with the simultaneous
timing of a console message from syslog and the opening/closing of the
console's tty due to logging out and
On Thu, Jul 21, 2005 at 08:29:47PM +0930, Daniel O'Connor wrote:
I think the best way to rectify this is to test RC candidates on YOUR
hardware.. This finds the bugs you need fixed at a time when people are very
receptive to fixing them.
It's not realistic for the release engineer to test
Robert,
First, thank you for your clear reply.
90% of useful FreeBSD testing happens when large FreeBSD consumers take
release of FreeBSD and deploy them in their testbeds and real-world
environments, and find the bugs through the application of high levels of
load and obscure hardware
Marc Olzheim wrote:
but I'd like a clear answer on
what to do now in regard to taking FreeBSD 5 into 'real' production...
I'd have to second this request. We rely heavily on the stability and
performance of FreeBSD in our business.
We've only had the occasional stupid hang on our
Hej All,
I upgraded to RELENG_6 to help testing.
Everything went smooth so far, but my scroll wheel in X isn't working
anymore. I didn't changed anything regarding the configuration from
FreeBSD RELENG_5 to RELENG_6 ...
some details:
[EMAIL PROTECTED] ~ $ uname -a
FreeBSD beastie.mobile.rz
On Jul 21, 2005, at 1:04 PM, Robert Watson wrote:
On Thu, 21 Jul 2005, Eirik Øverby wrote:
I've only seen the issue when logging out of a serial console
session, and had previously hypothesized that it had to do with
the simultaneous timing of a console message from syslog and the
On Thu, 21 Jul 2005, Marc Olzheim wrote:
Indeed. That's why my company started taking FreeBSD 5.3 in use for
production servers when it was out. Since then numerous bugs were fixed,
some of which reported by us. Now that we're X bug fixes later in time
and started to get a good feeling about
On Thu, Jul 21, 2005 at 02:19:23PM +0200, Eirik verby wrote:
If you cause syslogd not to send any output to /dev/console, does
the
problem go away?
I'm afraid to say it doesn't
Please, could you add:
options DDB #Enable the kernel debugger
options DDB_NUMSYM
On Thu, 21 Jul 2005, Nicklas B. Westerlund wrote:
Although I havn't seen any major problems on our servers, all using u320
scsi and smp - I don't feel as secure about my choice of upgrading to
5.x. We still have some 4.x servers in production, and judging by how
this is evolving, I think I'll
Hi,
at this point i musttail my paint with you and the other's.
I have really made a few tests on one big issue or RELENG_5.
At the time as it was early enough to change things, but the guys they
have me telled someone else have to fast machines to test ( in my eyes
they should test on some
Hi all,
Robert,
I was hopping for you to mention user's feedback.
I started this thread
http://lists.freebsd.org/pipermail/freebsd-current/2005-July/052288.html
back with SNAP004. The problem is still present in BETA1.
I haven't seen any more advances in the thread, and I know this must
be a
On 7/21/2005 at 8:29 PM Daniel O'Connor wrote:
|On Thursday 21 July 2005 19:27, Marc Olzheim wrote:
| Thank you for expressing my exact same sentiments. I'm still a huge
| FreeBSD fan and switching to anything else (well, perhaps DragonFly)
| seems out of the question, but my faith is being
On Thu, 21 Jul 2005, Joao Barros wrote:
I was hopping for you to mention user's feedback. I started this thread
http://lists.freebsd.org/pipermail/freebsd-current/2005-July/052288.html
back with SNAP004. The problem is still present in BETA1. I haven't seen
any more advances in the thread,
On Tue, Apr 19, 2005 at 10:38:08AM +0200, Marc Olzheim wrote:
The problem is with the periodic SMM interrupt and the bios.
The attached program (ich-periodic-smm-disable.c) will fix the problem.
For more information on what it does, see the Intel ICH3 datasheet.
compile as 'gcc
On 7/21/05, Robert Watson [EMAIL PROTECTED] wrote:
On Thu, 21 Jul 2005, Joao Barros wrote:
I was hopping for you to mention user's feedback. I started this thread
http://lists.freebsd.org/pipermail/freebsd-current/2005-July/052288.html
back with SNAP004. The problem is still present in
Hello,
I've (accidentally, because of a broken pidfile) noticed yesterday that
root can kill [acpi_task1] (PID 8 on my system, FreeBSD 5.4-p5/i386).
Killing it resulted in an immediate and total lockup of the system.
I gather that processes with [ ] around their name are parts of the
kernel.
On Thu, 21 Jul 2005, MikeM wrote:
Your comment presupposes that most of the bugs are specific to one piece
of hardware, I doubt that is a valid assertion. I would offer that most
of the bugs are not present in source code specific to a certain piece
of hardware, but are present in source
eManager Notification *
The following mail was blocked since it contains sensitive content.
Source mailbox: [EMAIL PROTECTED]
Destination mailbox(es): MikeM;freebsd-stable@freebsd.org
Rule/Policy: NOC fun
Action: Quarantine to
At 09:23 AM 21/07/2005, Joao Barros wrote:
John started debugging this with another person with similar problems
on 5 and the debugging never got to 6 (no feedback from the other
person):
http://lists.freebsd.org/pipermail/freebsd-current/2005-July/052727.html
Yes, The other person is me :)
Hello,
While tracking an issue with a jail I run, the interface to which the
jail aliases it's IP to suddenly became unresponsive.
My script starts the jail, then runs ifconfig alias. After starting and
stopping the jail about 20 times, the interface basically froze.
Ifconfig reported it as up
On Thu, Jul 21, 2005 at 01:20:49PM +0100, Robert Watson wrote:
I know FreeBSD 5 was a strange exception in the relase scheduling and
that a lot has been learned from it for the future and I'm certainly not
unthankful for all the work that's done, but I'd like a clear answer on
what to do
On 7/21/05, Mike Tancsa [EMAIL PROTECTED] wrote:
At 09:23 AM 21/07/2005, Joao Barros wrote:
John started debugging this with another person with similar problems
on 5 and the debugging never got to 6 (no feedback from the other
person):
In the past I'm sure that we supported the mixing of audio in the kernel
so that multiple applications could open /dev/dsp at the same time. Was
this a function of the audio card driver, or of the audio subsystem?
Currently on my new machine I don't get any mixing, and applications
fail to open
Josef,
On Thu, 21 Jul 2005, Josef Karthauser wrote:
In the past I'm sure that we supported the mixing of audio in the kernel
so that multiple applications could open /dev/dsp at the same time. Was
this a function of the audio card driver, or of the audio subsystem?
Currently on my new
On Thu, 21 Jul 2005, Benjamin Lutz wrote:
While tracking an issue with a jail I run, the interface to which the
jail aliases it's IP to suddenly became unresponsive.
My script starts the jail, then runs ifconfig alias. After starting and
stopping the jail about 20 times, the interface
On 7/21/2005 at 2:29 PM Robert Watson wrote:
|Some of us have actually spent quite a bit of time looking at the
defect
|sets reported for 5.x. Depending on the release they fall into a
number
|of categories, but here are the major ones I've identified:
| [snip]
|- Network stack stability under
I tried to build tiny freebsd a 6.0 version,
which currently works on my laptop ( cvs checked out to day)
did a build/install world + kernel
The image build doesn't exit somewhere or errors...
burned an image to my cf-card
cat my.img /dev/ad4
Then booted
the image boot stops : can't load
On Wed, 2005-07-20 at 23:54 -0500, Steve wrote:
I've found tons of emails, news messages, listserv messages, and even
some bug reports of this seemingly common error.
So, I had been running 5.2 on a server, and, updated to 5.3. Got the
READ_DMA and WRITE_DMA error and retries. So, figuring
On Thu, 21 Jul 2005, MikeM wrote:
Thank you for the clear answer. For the record, I am very pleased with
the overall quality of FreeBSD, my comments were only meant in the sense
of everything has room for improvement, even something as excellent as
FreeBSD.
I think everyone agrees there's
Hello Marten,
Thanks for your input.
Yesterday sysutils/tinybsd was updated to reflect fetching the new 0.2
TinyBSD which has some improvements related to lib depends, specially
pam as it was not functional on tinybsd (opie related problems) in
FreeBSD 6 like it was in RELENG_5 before.
Robert Watson wrote:
- ATA problems. Many of these, while a symptom of bugs in the ATA code
running without Giant, were very specific to timing, or divergent/poor
ATA hardware. As a result, they were difficult to reproduce in any
environment but the original reporting environment. The
At 09:23 AM 21/07/2005, Joao Barros wrote:
On 7/21/05, Robert Watson [EMAIL PROTECTED] wrote:
On Thu, 21 Jul 2005, Joao Barros wrote:
I was hopping for you to mention user's feedback. I started this thread
http://lists.freebsd.org/pipermail/freebsd-current/2005-July/052288.html
There
Paul Mather wrote:
One common thread in my case is that
all ran some kind of software RAID (gvinum or gmirror), though not all
of my software RAIDed machines exhibited the DMA problems leading me to
think perhaps it was a hardware/load/disk combination problem.
I do not use RAID at all,
Robert Watson wrote:
6.0 contains a significant re-write and update of the ATA driver, and
corrects a number of known problems with timeouts and reliability.
This rewrite is available as patches against 5.x, but has not been
committed because ATA is a very sensitive thing (lots of very
Hello, All;
I recently CVSUP'd from 5.4 to 6.0BETA1. I used the instructions in
UPDATING to build/install world and used GENERIC unmodified to build the
kernel. The whole procedure went without a single hitch. My question
concerns the meaning of a debug message which appears when I remove my
Agreed.
I have a PR open on the ATA issues, particularly with SATA drives, and
have had it open since before 5.4-RELEASE.
It remains open.
Careful selection of what's where can avoid major trouble, but this is
hardware that worked properly on 4.x for a LONG time - its definitely NOT
defective.
First of all thank you very much all for your replies.
I just want to add some comments based on previous mails.
- I completely agree with MikeM - any kind of complex software could be
tested with right prepared test cases, specially if they are going to be
reused in the next release;
- if those
On Thu, Jul 21, 2005 at 10:56:54AM +0200, Eirik ?verby wrote:
You might have to wait until 6.0-R since fixing it seems to require
infrastructure changes that cannot easily be backported to 5.x.
With all due respect - if this is (and I'm assuming it is, because it
happens on all the
Hi!
I have got a pair of very strange panics today.
I didn't saw the exact panic message for the firs one, as the X was running
at the time it has halted, and all I can say about it is that it was unable
to reboot and there are no coredump.
For the second one I saw a message (approximate -- I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
Am 21.07.2005 um 13:00 schrieb Robert Watson:
Have you tried, and do you plan to try, our 6.0 test releases before
6.0-RELEASE goes out the door? Specifically, on the hardware you
know
you're having problems with 5.4 on?
Hi all!
I have read this thread with a lot of interest and I have to
congratulate each of you for bringing calm, clever and interesting
answers.
I too felt that the quality of 5.x is not what I was used to but there
are new nice and promising features.
Having read most of all the emails it
On Thu, 21 Jul 2005, Alexey Yakimovich wrote:
First of all thank you very much all for your replies.
I just want to add some comments based on previous mails.
- I completely agree with MikeM - any kind of complex software could be
tested with right prepared test cases, specially if they are
On Jul 21, 2005, at 4:56 AM, Eirik Øverby wrote:
However, since I seem to be the only one who has noticed this,
perhaps I'm the last person on earth to routinely use serial
terminal switches instead of KVM switches to do my admin work?
no, there are plenty of us out here... i have two
All,
Does anyone have a good handle on how to replicate (read: image) a
freebsd machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd (Slow, not usefull if the hardware isn't identical?)
tar
Ok, Robert, but then here's the question
How come the ATA code which was very stable in 4.x was screwed with in a
production release, breaking it, with no path backwards to the working
code?
This is a perfectly valid thing to do in -HEAD, where its heh, you know
this might go BOOM on you!
On Thu, Jul 21, 2005 at 12:20:34PM -0700, Eli K. Breen wrote:
All,
Does anyone have a good handle on how to replicate (read: image) a
freebsd machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd
On Thu, 21 Jul 2005, Eli K. Breen wrote:
All,
Does anyone have a good handle on how to replicate (read: image) a
freebsd machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd(Slow, not usefull
At 15:20 7/21/2005, Eli K. Breen wrote:
All,
Does anyone have a good handle on how to replicate (read: image) a freebsd
machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd(Slow, not usefull if the
At 03:20 PM 21/07/2005, Eli K. Breen wrote:
All,
Does anyone have a good handle on how to replicate (read: image) a freebsd
machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd (Slow, not usefull
At 03:26 PM 21/07/2005, Karl Denninger wrote:
Ok, Robert, but then here's the question
How come the ATA code which was very stable in 4.x was screwed with in a
production release, breaking it, with no path backwards to the working
code?
I understand your frustration, but others would
On Thu, 21 Jul 2005, Eli K. Breen wrote:
All,
Does anyone have a good handle on how to replicate (read: image) a freebsd
machine from one machine to an ostensibly similar machine?
So far I've used countless variations and combinations of the following:
dd (Slow, not usefull if
[EMAIL PROTECTED] writes:
My main problem, and to others after seeing the question from times to
times, is to know which is a good (not necessarly the best) hardware to
run FreeBSD on?
When I buy a new motherboard, which chipset to choose/avoid, which controllers
?
Maybe some website like it is
On Thu, 2005-07-21 at 14:26 -0500, Karl Denninger wrote:
Ok, Robert, but then here's the question
How come the ATA code which was very stable in 4.x was screwed with in a
production release, breaking it, with no path backwards to the working
code?
Not to mention that this happened
Just as a point of note, I'm not trying to roll out squeeky-clean new
machines. Let's say I've got ten-fifteen sets of clusters, I need to be
able to just rip a copy and blast it to another machine.
Thanks for all the responses so far.
-E-
Dan Mack wrote:
On Thu, 21 Jul 2005, Eli K. Breen
On Thu, Jul 21, 2005 at 03:51:13PM -0400, Mike Tancsa wrote:
At 03:26 PM 21/07/2005, Karl Denninger wrote:
Ok, Robert, but then here's the question
How come the ATA code which was very stable in 4.x was screwed with in a
production release, breaking it, with no path backwards to the
I had a shell script that would replicate a machine when I ran my ISP; you
put the loader and partition table, plus a minimal system on the new machine,
then ran the script and pointed it at the source.
UUUPPP! In about 20 minutes it was done.
Not hard to do at all with a simple
On Thu, Jul 21, 2005 at 04:12:47PM -0400, Paul Mather wrote:
On Thu, 2005-07-21 at 14:26 -0500, Karl Denninger wrote:
Ok, Robert, but then here's the question
How come the ATA code which was very stable in 4.x was screwed with in a
production release, breaking it, with no path
At 8:50 AM -0400 7/21/05, MikeM wrote:
On 7/21/2005 at 8:29 PM Daniel O'Connor wrote:
|
| I think the best way to rectify this is to test RC candidates
| on YOUR hardware.. This finds the bugs you need fixed at a
| time when people are very receptive to fixing them.
|
| It's not realistic for
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eli K. Breen
Sent: Thursday, July 21, 2005 3:21 PM
To: freebsd-stable@freebsd.org
Subject: Machine Replication
All,
Does anyone have a good handle on how to replicate (read: image) a
freebsd machine from one machine to an
On Thu, Jul 21, 2005 at 12:20:34PM -0700, Eli K. Breen wrote:
Does anyone have a good handle on how to replicate (read: image) a
freebsd machine from one machine to an ostensibly similar machine?
[...]
Now whether my details are a bit off, that's fine, I don't want this to
be diluted in
On Thu, Jul 21, 2005 at 08:00:40PM +0100, Robert Watson wrote:
[original poster wrote:]
- I completely agree with MikeM - any kind of complex software could be
tested with right prepared test cases, specially if they are going to be
reused in the next release;
For static problems -- yes. For
Hello,
I've never debugged FreeBSD, but now I've decided to help the testing
process of FreeBSD 6. I installed it, and then I had a panic. I got a
debugger prompt, but I don't know what to do with that. I don't know the
debugger commands. Please let me know what should I do when I have an
Hi,
I've installed FreeBSD 6.0-BETA1 and if I use more consoles I have a
silent crash. The cursor won't move and I can't change back to another
console. It has happened three times so far when I was using two
consoles. (I was using make + ee in the first two cases and in the third
case cvsup
I should point out, this is for replication in a running production
environment. Machines cannot be taken down, and swapping hardware is not
an option.
I'm currently experimenting with a copy of the MBR, and the root
partition on a CD, with enough tools to attach to the network to
retrieve
On Thu, Jul 21, 2005 at 03:04:01PM -0500, Dan Mack wrote:
snip
Is there a jumpstart (solaris), kickstart (redhat linux), roboinst (irix),
or ignite (hpux) like auto-installer for BSD?
No. g4u and a script might do a good job for you if your hardware is
mostly similar.
If there was, then I
On 7/21/05, Kövesdán Gábor [EMAIL PROTECTED] wrote:
FreeBSD 6. I installed it, and then I had a panic. I got a
debugger prompt, but I don't know what to do with that. I don't know the
debugger commands. Please let me know what should I do when I have an
another panic. What should I type and
Yep. Pretty much what I used to do with my ISP.
--
--
Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist
http://www.denninger.netMy home on the net - links to everything I do!
http://scubaforum.org Your UNCENSORED place to talk about DIVING!
On Thu, Jul 21, 2005 at 03:04:01PM -0500, Dan Mack wrote:
Is there a jumpstart (solaris), kickstart (redhat linux), roboinst (irix),
or ignite (hpux) like auto-installer for BSD?
If there was, then I wouldn't image the disk at all, I'd instead setup up
custom network images that I could
Even for dynamic problems you can have your code generating detailed logs,
including time, pid, thread id, cpu, function, memory ..., and have them
analyzed later by some script.
But this not my main point here, in this thread.
All thoughts in the mails of this thread, developers as well as
On Thu, 21 Jul 2005, Karl Denninger wrote:
ATA-NG (Soren's new code) is not (from what I understand) in the 5.x
codebase. One bone of contention is that apparently it IS in -HEAD, but
there are no plans to MFC it to 5.x.
Then you misunderstand. Soren has asked to MFC it, and we've asked
On Thu, 21 Jul 2005, Alexey Yakimovich wrote:
Even for dynamic problems you can have your code generating detailed
logs, including time, pid, thread id, cpu, function, memory ..., and
have them analyzed later by some script. But this not my main point
here, in this thread.
Instrumentation
On Fri, Jul 22, 2005 at 12:45:03AM +0100, Robert Watson wrote:
On Thu, 21 Jul 2005, Karl Denninger wrote:
ATA-NG (Soren's new code) is not (from what I understand) in the 5.x
codebase. One bone of contention is that apparently it IS in -HEAD, but
there are no plans to MFC it to 5.x.
On Thu, 21 Jul 2005, Karl Denninger wrote:
If Soren BELIEVES (2) is the case, I'll test against -BETA1, IF I can
have confirmation that -BETA1 has the ATA-NG code in it.
Its trivially easy for me to reproduce this problem on my sandbox
machine.
As has already been stated, Soren's changes
On Thu, 21 Jul 2005, Matthias Schuendehuette wrote:
Am 21.07.2005 um 13:00 schrieb Robert Watson:
Have you tried, and do you plan to try, our 6.0 test releases before
6.0-RELEASE goes out the door? Specifically, on the hardware you know
you're having problems with 5.4 on?
Yes, I did
On Thu, Jul 21, 2005 at 12:20:34PM -0700, Eli K. Breen wrote:
dd(Slow, not usefull if the hardware isn't identical?)
I use dd a lot for this type of thing and don't see how it could
possibly be slower than any other method that duplicates the entire raw
drive. Make sure to give it a
Marian Hettwer wrote:
Hej All,
I upgraded to RELENG_6 to help testing.
Everything went smooth so far, but my scroll wheel in X isn't working
anymore. I didn't changed anything regarding the configuration from
FreeBSD RELENG_5 to RELENG_6 ...
some details:
[EMAIL PROTECTED] ~ $ uname -a
FreeBSD
On Fri, Jul 22, 2005 at 01:38:40AM +0100, Robert Watson wrote:
On Thu, 21 Jul 2005, Karl Denninger wrote:
If Soren BELIEVES (2) is the case, I'll test against -BETA1, IF I can
have confirmation that -BETA1 has the ATA-NG code in it.
Its trivially easy for me to reproduce this problem on
I've been a BSD user since the mid-90s, and a FreeBSD user since the
days 4.0 became STABLE.
Right now, I have 2 collocated servers, one home server, and a laptop
all running 5.4 without any serious problems. I've watched 5.x since
its creation, and while there have been some rocky times, I
On 21 Jul, Dan Mack wrote:
Is there a jumpstart (solaris), kickstart (redhat linux), roboinst (irix),
or ignite (hpux) like auto-installer for BSD?
If there was, then I wouldn't image the disk at all, I'd instead setup up
custom network images that I could blast to any system just by
On 7/21/05, Matthias Buelow [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
My main problem, and to others after seeing the question from times to
times, is to know which is a good (not necessarly the best) hardware to
run FreeBSD on?
When I buy a new motherboard, which chipset to
91 matches
Mail list logo
