Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Sharing a Heterogeneous Local Network

timothy posted more than 12 years ago | from the then-get-a-blood-test-remember dept.

Linux 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.

cancel ×


Sorry! There are no comments related to the filter you selected.

First goatse (-1)

Klerck (213193) | more than 12 years ago | (#3303341) []

Heterogeneous Local Network? (-1)

ringbarer (545020) | more than 12 years ago | (#3303342)

Isn't that a euphamism for unprotected (and unlubricated) anal sex between consenting male adults and unconsenting male children?

Fist Sport!

Re:Heterogeneous Local Network? (0, Flamebait)

MindStalker (22827) | more than 12 years ago | (#3303959)

No he said Heterogeneous, not Homogeneous, dumbass.

I'm not one to judge (0)

Anonymous Coward | more than 12 years ago | (#3303675)

But you should always use a clean needle if you're going to share like that.

Interesting & informative atricle (0)

Anonymous Coward | more than 12 years ago | (#3304003)

You expect slashbots to have anything to do HETERO-anything?

There are some fairly good ones (3, Informative)

infonography (566403) | more than 12 years ago | (#3307682)

Sorry, but I am compelled to respond to a badly done article.

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.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?