Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Nov 2001 11:15:50 -0500 (EST)
From:      Kenneth Wayne Culver <culverk@wam.umd.edu>
To:        Anthony Atkielski <anthony@atkielski.com>
Cc:        setantae <setantae@submonkey.net>, questions@FreeBSD.ORG
Subject:   Re: home pc use
Message-ID:  <Pine.GSO.4.21.0111201109140.27830-100000@sun08pg2.wam.umd.edu>
In-Reply-To: <001f01c171cf$430e8ac0$0a00000a@atkielski.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.

Not everyone wants their systems to look like and feel like windows. I for
one would never have installed FreeBSD on my computers 5 or 6 years ago if
it had looked like windows.
 
> > 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).

Support is not difficult to get, but most FreeBSD users expect the user
who is asking questions on this list to read the manpages and search the
list archives before emailing the list.
 
> > 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.

That is largly personal opinion. Personally if the desktop system
functions and I can get work done, I don't care if it looks like and acts
like windows, and the less it looks like windows, the better.
 
> > 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.

What were you disappointed by? I was very impressed by KDE2 when I first
tried it out, and stopped using windowmaker to use KDE2. I'm glad it
doesn't act like windows, and I'm glad that FreeBSD can't be configured by
pointing and clicking. That's what windows is for; people who don't want
to learn how to edit config files.
 
> > 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.

What exactly do you want to know how to do, I didn't read your original
post, but I'll read your response to this mail, I'm sure I can help you
with most of your problems; as I still remember the problems I had when
I made the switch (And never went back)
 
> > 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.
> 
I thought it was pretty good, it's how I learned most of what I know about
FreeBSD, and that was about 5 years ago, the docs now are much better now
than they were when I first started.

Ken


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?Pine.GSO.4.21.0111201109140.27830-100000>