From owner-freebsd-questions@FreeBSD.ORG Sun Feb 13 08:30:55 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 798CB16A4CE for ; Sun, 13 Feb 2005 08:30:55 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAE2C43D1F for ; Sun, 13 Feb 2005 08:30:54 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id 214C91C0008A for ; Sun, 13 Feb 2005 09:30:54 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id E619B1C00086 for ; Sun, 13 Feb 2005 09:30:53 +0100 (CET) X-ME-UUID: 20050213083053942.E619B1C00086@mwinf1106.wanadoo.fr Date: Sun, 13 Feb 2005 09:30:53 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1466272619.20050213093053@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: References: <200502112313.28082.hindrich@worldchat.com> <200502121141.07311.bulliver@badcomputer.org> <1443267912.20050212215132@wanadoo.fr> <200502121359.53523.bulliver@badcomputer.org> <992422833.20050213024853@wanadoo.fr> <00c101c51170$19af5ee0$4300a8c0@ostros> <909006882.20050213085459@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Freebsd vs. linux X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 08:30:55 -0000 Chad Leigh -- Shire.Net LLC writes: > I have not used that, but I doubt it beats using a real openssh client > inside a unix based terminal emulator in terms of terminal emulation > and shell compatibility. SecureCRT emulates a terminal, and does so in a way that is particularly compatible with UNIX systems (with which it is very heavily used--the vendor caters to UNIX users). It emulates eleven different types of terminal, including VTxxx, Xterm, Vshell (proprietary, I think), WYSE, SCO ANSI, and so on. You can set the desired base emulation and then modify the details to get a terminal emulation that exactly suits you. > As I said, I have not used this one, but all the other windows ones I > have tried sucked royally. This one was recommended by an ISP to me years ago, and it was so good that I've never tried anything else. See http://www.vandyke.com. > They exist. A friend of mine had one running on w2000 several years > ago logging into hi BSD and Linux boxes using xterm. It worked > reasonably well. How much did he pay for it? Many of the ones I saw cost hundreds or thousands of dollars, and there was still no guarantee that they'd work well. The few free ones I tried did not work well at all. I'm still interested in learning more, though. However, I won't run x-anything on my FreeBSD system unless it will run without destabilizing changes to the OS (no change in securelevel, no kernel reconfiguration, no special system software modules or daemons). > I do everything else on my Mac(s) including bookkeeping/accounting for > a couple of businesses, credit card authorizations, software > development, email, browsing, netnews, Terminal and ssh into my FreeBSD > and lone Linux servers, database admin, word processing, presentations, > graphics/photo and video editing (not a lot of the latter > unfortunately), and many other things. Having UNIX underneath surely helps, although it has broken some classic Mac applications. > And I am not a magnet for viruses, spyware, adware ... The target is too small, few kiddies are interested in attacking it. > ... I do not pay a MS tax anymore ... You pay a double tax to Apple instead, for both software and hardware. > And yes, Windows rots and decays, most likely from > registry corruptions -- the registry is the dumbest thing they could do > -- a single massive point of failure ... No, they've done even worse: Active Directory. I don't like those single points of failure, either. And even though the advantage of a registry is supposed to be that it provides "one-stop shopping" for configuration data, it turns out that the same data is often stored in a dozen different places in the registry ... sometimes by different releases of the same software (and some of that software is from Microsoft, so they're just as guilty of it as anyone else). -- Anthony