howto connect piCore to tinycore netbook

[lmart]

Need a step-by-step to connect Raspberry Pi running piCore to a netbook running tinycore+.
My objective is to use the run the RPi using the netbook's display and keyboard.

[bmarkus]

Need a step-by-step to connect Raspberry Pi running piCore to a netbook running tinycore+.
My objective is to use the run the RPi using the netbook's display and keyboard.

Use SSH which is enabled by default. If you need remote GUI access, install x11vnc on piCore from the repo and use a VNC client on the netbook.

[lmart]

Thanks for your reply.
Perhaps I asked my question incorrectly.
    #1, On piCore, what must I do to connect to tinycore+ to be able to use the monitor and keyboard?
    #2. On tinycore+. what must I do to enable piCore to connect?

[bmarkus]

Unplug monitor and keyboard from the TC machine and connect  cables to Raspberry Pi.

[lmart]

Thanks again for your reply.

#1. I am using a Netbook laptop with tinycore+ installed, directly from the LiveCD. The laptop can connect to the Internet via
Ethernet or Wireless. OpenSSh is installed.
#2. I am using a RPi with piCore, connected to an external monitor and keyboard, both of which I am trying to eliminate.
#3. Direct Ethernet connection between Netbook and RPi.

Assuming the Netbook is the ssh server and the RPi is the ssh client, what must I do to enable them to communicate with one another, step-by-step, on each end?

After reading multiple articles on the Internet about using ssh to connect two Linux computers via Ethernet, I am left with more questions than answers. Thus, my post.

[Greg Erskine]

#1. I am using a Netbook laptop with tinycore+ installed, directly from the LiveCD. The laptop can connect to the Internet via
Ethernet or Wireless. OpenSSh is installed.

Good.

#2. I am using a RPi with piCore, connected to an external monitor and keyboard, both of which I am trying to eliminate.

That is called "headless", a very common configuration.

#3. Direct Ethernet connection between Netbook and RPi.

Do you mean the Netbook and RPi are physically connect together or via a router (easiest option)?

Assuming the Netbook is the ssh server and the RPi is the ssh client, what must I do to enable them to communicate with one another, step-by-step, on each end?

I look at the "headless" device as the server and the controlling device (monitor/keyboard) as the client.

There is really nothing to do!

Connect Netbook to LAN - Ethernet cable or wireless to router.
Connect RPi to LAN  - Ethernet cable or wireless to router.

Both have ssh running by default. Type $ssh 192.168.1.xxx on Netbook terminal where 192.168.1.xxx is the IP of the RPi. You can use scp to copy files between computers.

If you have Windows PC use "putty" to connect to RPi. winSCp is a handy tool on PC. There are similar clients for MAC, iPad, etc. Anything on your LAN can control the RPi using the appropriate client software.

regards
Greg

[lmart]

Greg,

Thanks for your reply and explanations.

I want to direct connect the laptop to the RPi, via an Ethernet cable, rather than connect to a router. Lastly, I want to eliminate the current external monitor and keyboard connected to the RPi, using instead, the laptop's video and keyboard.


 

[Misalf]

If you're not using a Router / Switch / Hub and if your NICs don't support Auto MDI-X, then you will need a crossover cable.
https://en.wikipedia.org/wiki/Ethernet_crossover_cable
Not needed for most modern NICs (I don't know about the RaspberryPI's NIC).

You need to set a static IP address for your RaspberryPI if you're not running a DHCP server on your Netbook.
Assuming your RaspberryPI's IP address shall be:
192.168.0.3

Code: [Select]

sudo pkill udhcpc
sudo ifconfig eth0 192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255 up
This is without internet access.

Then from your Netbook:

Code: [Select]

ssh tc@192.168.0.3

Also see: https://www.raspberrypi.org/documentation/remote-access/ssh/unix.md

[Rich]

Hi lmart
If you want to direct connect the two machines you might need to use a crossover cable. Using a network switch (or hub)
to connect the two machines would allow you to use standard cables. Once the two machines are connected, use the
ping command from each machine to make sure it can see the other machine. Result should be similar to this:

Code: [Select]

tc@box:~$ sudo ping -c4 192.168.1.47
PING 192.168.1.47 (192.168.1.47): 56 data bytes
64 bytes from 192.168.1.47: icmp_seq=0 ttl=64 time=0.259 ms
64 bytes from 192.168.1.47: icmp_seq=1 ttl=64 time=0.215 ms
64 bytes from 192.168.1.47: icmp_seq=2 ttl=64 time=0.214 ms
64 bytes from 192.168.1.47: icmp_seq=3 ttl=64 time=0.217 ms
--- 192.168.1.47 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.214/0.226/0.259/0.000 ms
tc@box:~$Once the machines can ping each other, you can try the ssh command Greg Erskine posted.

[lmart]

Misalf & Rich,

Thank you for your replies.

Rich, I will try your recommendation first. If unable to ping successfully, I will pick up a cross-over cable and try again.

Assuming a successful ping, I will then try Misalf's recommendations.

Thanks. Will keep you posted on results.

[Greg Erskine]

Lastly, I want to eliminate the current external monitor and keyboard connected to the RPi, using instead, the laptop's video and keyboard.

I KNOW!! I CAN READ!!

[lmart]

Did not mean to offend.
It is best to just close this post.

[Misalf]

Well, writing in fat or capital is often considered shouting.
However, it might be helpful for future readers to tell if you got it working with the info provided here.