Date: Sun, 6 Dec 1998 16:37:19 -0500 (EST) From: "Woodchuck" <djv@bedford.net> To: mpoulin@honk.org (M. Poulin) Cc: freebsd-newbies@FreeBSD.ORG Subject: Re: What to do with new hardware... Message-ID: <199812062137.QAA08466@castor.chuck> In-Reply-To: <3.0.3.32.19981204101933.0090cda0@spectre.honk.org> from "M. Poulin" at "Dec 4, 98 10:19:33 am"
next in thread | previous in thread | raw e-mail | index | archive | help
M. Poulin wrote:
>
> I would like a nice X workstation running KDE or another nice-looking window manager (I've tried FVWM2, and will probably also try Enlightenment and AfterStep) - the 486 is just a little too slow for graphic-intensive X sessions.
>
Oh? This may be more a problem of video cards rather than CPU. Of course, it
depends on what you mean by "slow". With a lightweight window manager
(fvwm 1.x or maybe icewm) it is tolerable with mostly text applications.
The prob. will probably be that the monitor is too small or too low
resolution. X on a 680x480 vanilla VGA really sucks. (I've actually
run X on a Hercules monochrome monitor and on mono VGA on 386SX-16
machines, which is, er, "interesting").
> What I am thinking is to set up my machines as follows:
>
>
> - Install FreeBSD on the 486 500MB HD. (no X)
>
> - Network the two, using NFS if needed, and when I get the cable modem, I will turn the 486 into a firewall / proxy server.
>
> Any thoughts?
Definitely network the two, it's a piece of cake. With two machines,
you can get away with a "null modem" (crossover) cable for twisted
pair ethernet, or use coax. NFS performance is adequate even over
coax. If you're buying new cards, look for Tulip cards or Intel
Etherexpress depending on budget. Avoid coax for new installations.
I say that even though I run about 6 machines here, 5 of them on
coax, and have had no problems. I routinely run an X over 10MHz
coax (to an old DECStation), with very satisfactory results.
Re X on the 486... if you have the two boxes netted, there is no
problem to "install" X on the 486; the /usr/X11R6 directory may be
exported, and symbolic links to configuration files (recommend
/etc/X or something local to each machine) used.
Of course, the rational way to run things is as you have suggested:
run the 486 headless and networked, and use rlogin/xterm/and so on
to access that machine.
Also, /usr/src and /usr/obj are naturals to export: you can keep
current on the bigger box with cvsup, and easily update the wee
box.
Of course, the entire /usr fs can be exported to the 486, possibly
(probably) readonly.
I'm running a more-or-less similar setup, a couple of PPro's hiding
behind a 486. Once set up, this is a "foolproof --hands off -- it
runs itself" situation. Look for posts by Dan Langille (?) on -questions,
he has a web page with some very useful info about small home networking
setups.
Dave
--
Strangers know your loved ones' phone numbers!!!!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-newbies" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812062137.QAA08466>