Date: Tue, 22 Mar 2005 11:26:13 +0100 From: Anthony Atkielski <atkielski.anthony@wanadoo.fr> To: freebsd-questions@freebsd.org Subject: Re: Anthony's drive issues.Re: ssh password delay Message-ID: <1404322406.20050322112613@wanadoo.fr> In-Reply-To: <eeef1a4c050322014420d89861@mail.gmail.com> References: <423E116D.50805@usmstudent.com> <423EEE60.2050205@dial.pipex.com> <18510151385.20050321193911@wanadoo.fr> <eeef1a4c0503211224572d64e4@mail.gmail.com> <1975192207.20050322041925@wanadoo.fr> <eeef1a4c050322010021fd8eb4@mail.gmail.com> <1688160068.20050322102514@wanadoo.fr> <eeef1a4c050322014420d89861@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Freminlins writes: > So stick with NT. Why would you change from something that runs > perfectly for 8 years? I was able to retire the legacy applications on the machine and I wanted to try something new. > That doesn't mean nothing has changed in 20 years, does it? It means that the age of the OS is not an issue. > And your hardware seems to not work very well with FreeBSD. Move on. No, FreeBSD doesn't work very well with the hardware. As a matter of fact, it doesn't work very well with the hardware on my production server, either. It seems that as soon as you install FreeBSD on a machine, the "hardware" fails. > That's not what has been said. Having read this thread (and others by > you previously) you have no intention of helping yourself. What would you suggest that I do? It takes a very long time to wade through OS source code. -- Anthony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1404322406.20050322112613>