Date: Tue, 22 Mar 2005 10:25:14 +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: <1688160068.20050322102514@wanadoo.fr> In-Reply-To: <eeef1a4c050322010021fd8eb4@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Freminlins writes: > On a different OS. Exactly. With _identical_ hardware. So if the hardware ran under the other OS, but not under this OS, where do you look first for the problem? If your car runs perfectly for years with one brand of oil, and then you change brands and the engine seizes, where do you look for the source of the problem? > Don't try and put your words in my mouth. I'm just pointing out the unavoidable implication of what you said. NT ran on this hardware for eight years without a hitch; FreeBSD cannot do the same. It's not the hardware. > On your ancient hardware with an ancient OS you didn't have problems. UNIX is twenty years older than NT. > Why not stick with it if it's been so reliable? I wanted to try FreeBSD. Is that what you tell people who have trouble getting FreeBSD to work? "Reinstall your old OS"? -- Anthony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1688160068.20050322102514>