Date: Tue, 20 Nov 2001 15:25:37 +0100 From: "Anthony Atkielski" <anthony@atkielski.com> To: "setantae" <setantae@submonkey.net> Cc: <questions@FreeBSD.ORG> Subject: Re: home pc use Message-ID: <001f01c171cf$430e8ac0$0a00000a@atkielski.com> References: <3BF9B12B.3D521A4D@nycap.rr.com> <0111191831240Q.60958@chip.wiegand.org> <20011119220243.A268@prayforwind.com> <009a01c171a9$4eedbee0$0a00000a@atkielski.com> <20011120023948.A92409@xor.obsecurity.org> <00df01c171b0$2a938be0$0a00000a@atkielski.com> <20011120105642.GA75918@rhadamanth> <012d01c171b6$96b5adc0$0a00000a@atkielski.com> <20011120114236.GA76431@rhadamanth> <005f01c171bf$c4d06b10$0a00000a@atkielski.com> <20011120131850.GA77414@rhadamanth>
next in thread | previous in thread | raw e-mail | index | archive | help
Ceri writes: > Who said anything about cloning Windows ? I did. A realistic GUI environment for me would have to be a virtual clone of Windows, because virtually all the applications I use are Windows-only applications. > According to the archives, you installed > FreeBSD on 31st Oct, 2001. Yes, but I first worked on an operating system considerably prior to that date. > You then proceeded to ask what portmap was. > You were amazed that one needs a different kernel > to enable SMP. You never heard of the rehash > command in csh. Yes. So? > These are not FreeBSD specific problems. They are characteristic of UNIX, or of some other OSes in isolation (multiprocessor support). > All of these are things that one could expect > from someone with only 3 weeks experience of an > OS, but I honestly think that you would benefit > from doing some background reading. Thank you for your suggestion. I was hoping that you might offer more information on FreeBSD, instead of your armchair evaluation of my competence in IT. If all responses to my questions and comments were similar, I should indeed be restricted to reading elsewhere to obtain the information I require. This illustrates to some extent my comments about support being difficult to get for FreeBSD (and other open-source products). > You come here and basically say ``All window > managers suck.'' In a world dominated by Microsoft Windows, any window manager that does not replicate Windows functionality effectively sucks, from the standpoint of the average end user. This may not be a pleasant thought, but it is a hard reality. I may not like everything about Windows, but I do accept that it is the standard against which all other window systems must be measured. > I suggest a window manager that doesn't suck, > and you say ``I've had my fill''. I heard great things about KDE, too, but it turned out to be a disappointment. So did the default window manager. I can't devote my life to trying to make UNIX look like Windows. There are lots of other things that UNIX is good for, and I have no pressing desire to prove that UNIX can be "just as good" as Windows. The OS wasn't meant for that, anyway. > If you seriously wish to use FreeBSD in a > production environment, then it's even more > important that you familiarise yourself with > the system : how to upgrade it, how to install > new software, how to get the sources, how it is > different from other systems, how it is similar > to other systems. You don't seem prepared to > do this. That's what I'm doing, although I've discovered that this list, at least, is nearly useless for that purpose. One need only read your own post, and others like it, and distill the real, useful information they contain, if any, to see how poorly this list fulfills its nominal role. > There is a handbook that a good body of people > have spent and so spend a considerable amount > of manhours writing. I *know* that you haven't > taken the time to read it. I've read parts of it that are relevant to what I need to know. It is not the best-written document I've ever seen, but the alternatives seem to be worse. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001f01c171cf$430e8ac0$0a00000a>