Sharing a Heterogeneous Local Network 7
PeterMAN writes: "If you want to learn how to share your systems on a heterogeneous local network and how to use it to compare and test applications on different operating systems and architectures, then take a look at these two articles that compare SSH, remote X, VNC, and other technologies as ways of remotely running applications." That link is to the second part of the series; here's the first installlment.
There are some fairly good ones (Score:3, Informative)
In most of the networks I have worked/setup/etc the underlying hardware isn't the issue. Any UNIX will mount a user's home directory and with minimal tweaking you can customize the env variables.
Sadly the article is reinventing the old ways of doing stuff, better methods such has this example from my (admittedly customized) /etc/profile
if [ "$DISPLAY" = "" ]; then if [ "`tty`" != "/dev/console" -o "$TERM" != "console" ]; then
REMOTEHOSTNAME="`who am i | cut -d'(' -f2,2 | cut -d')' -f1,1`" DISPLAY="$REMOTEHOSTNAME:0"
export DISPLAY
This fixed that display problem automagikly
This outputs my ip address to show this in an ENV command
DISPLAY=swras5-68-229. [BLOCKED-IP] .net:0
the 'who' command being fairly common will have flags 'am' 'i' and output this;
infonography pts/1 Apr 8 19:40 (swras5-68-229.[BLOCKED-IP] .net)
Don't get me wrong, its a good baby step into a lot of what's out there, but it has glaring distortions and bad practices. A Professional Sysadmin will have fixed most of the issues mentioned.
Over all there are too many subjects touched on too lightly. This article lacks a central focus. Who wrote this? David Mertz or someone else? The wording indicated it might be both.
who knows, this may start a flame war about the practices of Programmer/Admins and Professional SysAdmins. But this is a good example of why you never want to hire a Ph.D to run your network.