Date: Wed, 19 Feb 2020 13:06:28 -0500 From: Jerry <jerry@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Message-ID: <20200219130628.457f8953@scorpio> In-Reply-To: <CAPyFy2CwY4t7Syf8oXtFPzWQqjdy9iY%2B1EkhZjuuoVzvW2sZGQ@mail.gmail.com> References: <20200217231452.717FA1E820@freefall.freebsd.org> <CAFYkXjmZi1-MB6W0HsMx9gHek7Xg5heoSKKWkNTnw74dxRTwAw@mail.gmail.com> <85E7C97E-EF8B-4FC7-8EF1-758B7BCBAE90@kreme.com> <20200218183010.5a52441f.freebsd@edvax.de> <CAFYkXjm%2Bav5Ky5dVV9vuuSpW%2Bpw2AcpzhC1aWfHP=iKNmuWXVA@mail.gmail.com> <20200218205940.04917783.freebsd@edvax.de> <20200219052643.7bd90d3c@scorpio> <CAPyFy2CwY4t7Syf8oXtFPzWQqjdy9iY%2B1EkhZjuuoVzvW2sZGQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Feb 2020 11:31:18 -0500, Ed Maste stated: >That's an unfortunate issue, but it's very hard to make progress >without getting an affected machine to an appropriate developer. Personally, Ed, I think your suggestion is absurd. For years I heard the often-repeated statement, “Lock-In,” when referring to MS Products. The far more common, though less mentioned statement of, “Locked Out” was conveniently bypassed. I cannot begin to tell you how many times I wanted to use a piece of equipment or advanced technology but was not able to do so when outside an MS environment. Now, I find that FBSD 12.x will not even install and run on my PC. This cannot be because the technology is too new. 11.x runs just fine. This is obviously a problem with the programming. I have been told by you and others that they need a machine to work on to discover the problem. Seriously, that is BS. It worked before; they broke it when updating. If it had never worked, I might have considered donating a piece of equipment to assist them, but this is obviously not that sort of problem. I have consulted Dell, including a voice conversation with a technician. He, himself, said that he uses Linux on one of his machines. They have never received a problem like I am experiencing on any other OS other then FBSD. I have confidence that the problem will be fixed eventually, either when the problem has evolved to be a nuisance to a much larger audience or by dumb luck. In either case, since it did once work, it is obviously not beyond the scope of the engineers to correct the problem. -- Jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200219130628.457f8953>