OK, so I went out and bought a crossover cable which is just a piece of wire, costing more than 60% of the rPi complete computer.
So the slak-boys say I must do `netconfig`, which I obviously skipped during installation because I don't want to KNOW about ethernet, because it's like kiddies who should have a bicycle, but want to have their own airliner. It's absurd to have 2 devices on either end of ONE piece of wire, where each has its unique 6-byte address !!
AFAICS netconfig only sets-up-the addressing between these 2 clowns in a rowing-boat in the middle of the Pacific who can't talk to each other because their names are mutually unknown?
But what commands exchange data between the rPi & slak-PC?
Everything is a file, so see if/what where the latest /dev/* was created:
-> ls -tl /dev/* | head == crap!
Perhaps /dev/*et* was created at boot time == crap !
rPi: `ifplugd -c` shows the pid-running, and slak's `lsof | grep ` would show what 'device was open' perhaps.
How do I test if the PC's ethernet hardware is not bust? `dmesg` shows the 6-byte IP as per the eth-socket label. I can't remember how/why but sometimes the eth-socket used to flash; but not lately.
What a load of crap, for such a simple task. It's like the wintel systems which need an airconditioner on their back.