Ok so in what follows I am aware of the security implications. Don't need to tell me about them. Thats generally been my day job for the last 10 years.
I want to accomplish the following.
I would like to to be able to sit at a PC and pull code from Git and build it on my Amiga.
I would like to be able to telnet to my Amiga and get a CLI.
My Amiga is running an 060 and has an ethernet card thats running Roadshow.
Essentially i want to run a telnetd and bind it to my ethernet card.. and use git if possible.
Network Tools needed (Remote Amiga Login)
Moderators: terriblefire, Terriblefire Moderator
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Network Tools needed (Remote Amiga Login)
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Network Tools needed
Looks like there is a git implementation for Amiga
https://github.com/sba1/simplegit
EDIT: ah apparently OS4.. so not really for Amiga.
https://github.com/sba1/simplegit
EDIT: ah apparently OS4.. so not really for Amiga.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Network Tools needed
One suggestion (since I think you'll never get a practical implementation of git on AmigaOS classic - crypto and filesystem limitations) would be to use CVS on the Amiga side and a git-cvs server on a linux machine.
Other workarounds would be to nfs or samba mount the code from a linux machine, and commit on linux.
As for telnetd, a bit of googling shows telnetd server for MiamiDX - I have no idea about roadshow.
Sounds like a pretty out there plan you have going
Other workarounds would be to nfs or samba mount the code from a linux machine, and commit on linux.
As for telnetd, a bit of googling shows telnetd server for MiamiDX - I have no idea about roadshow.
Sounds like a pretty out there plan you have going
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Network Tools needed
I just want to write code on visual studio code and deploy and run it on a real amiga via a script.
Build, Deploy, Test.... really simple with anything except an Amiga.
WinUAE doesnt cut it when hardware dev is involved too.
Build, Deploy, Test.... really simple with anything except an Amiga.
WinUAE doesnt cut it when hardware dev is involved too.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Network Tools needed
So cross-compiling locally and then just sending the binary over the network isn't what you're after?
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Network Tools needed
how do i run the code and see the output without a cli? No i need the remote CLI.
Well i dont understand why its so hard. I just wanna start newshell on a telnetd and git pull my code. Its exceptionally basic computing.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Network Tools needed
CLI part should be easy enough with telnetd from aminet as a "server" in roadshow - I downloaded the demo version and the config seems straightforward - assuming the same for ftpd.
From there it's just a matter of git post-commit hooks to trigger an expect script that "logs in" to the amiga to do whatever you can imagine.
From there it's just a matter of git post-commit hooks to trigger an expect script that "logs in" to the amiga to do whatever you can imagine.
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Network Tools needed
OK this is the bit i dont get with roadshow. It doesnt create a AmiTCP: assign so i have no idea where to add the inetd lines and i cant find any mention of it easily in the docs.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Network Tools needed
Aaargh I see what you mean! I gave up with (the demo version of) roadshow. I got this far:
In DEVS:Internet/servers:
telnet stream DH0:serv/telnetd
In DEVS:Internet/users:
NAME=root UID=0 GID=0 PASSWORD=root DIR="S:" SHELL="*newshell * from s:remote-startup"
Took me a while to work out things aren't configured in AmiTCP:db/passwd after all, and that the password in "users" is in plain text.
But it just hangs after successful login (SHIFT+ALT+F8 brings up the network log).
Maybe it works in the registered version? Failing that back to amitcp...
EDIT: this is with telnetd2.0
In DEVS:Internet/servers:
telnet stream DH0:serv/telnetd
In DEVS:Internet/users:
NAME=root UID=0 GID=0 PASSWORD=root DIR="S:" SHELL="*newshell * from s:remote-startup"
Took me a while to work out things aren't configured in AmiTCP:db/passwd after all, and that the password in "users" is in plain text.
But it just hangs after successful login (SHIFT+ALT+F8 brings up the network log).
Maybe it works in the registered version? Failing that back to amitcp...
EDIT: this is with telnetd2.0
Re: Network Tools needed
Actually just tried ttyhandler and it works with the roadshow demo.
Same DEVS:internet/users file.
In DEVS:internet/users:
NAME=root UID=1 GID=1 PASSWORD=root
In DEVS:internet/servers:
telnet stream AmiTCP:serv/ttyhandler
Haven't tried compiling anything though.
Same DEVS:internet/users file.
In DEVS:internet/users:
NAME=root UID=1 GID=1 PASSWORD=root
In DEVS:internet/servers:
telnet stream AmiTCP:serv/ttyhandler
Code: Select all
Login: root
Password:
TTY0
New Shell process 7
Directory: "Workbench:" Read/Write
C | Classes | Devs |
Expansion | Fonts | L |
Libs | Locale | MUI |
Prefs | Rexxc | S |
Storage | System | Tools |
Trashcan | Utilities | WBStartup |
.backdrop 14 | Devs.info 628 | Disk.info 652 |
Expansion.info 632 | MUI.info 1233 | Prefs.info 724 |
Storage.info 628 | System.info 628 | Tools.info 628 |
Trashcan.info 1172 | Utilities.info 628 | WBStartup.info 628 |
Files: 12 Dirs: 18 Size: 8195
Disk Size: 52427776 Disk Used: 17451520 Disk Free: 34976256
7>