Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: bradhansen1 on October 14, 2021, 12:01:24 AM
-
Hello all, Setting up my new A1200 and trying to get on the net. I am installing
the latest version of AmiTCP 30 something, and at one point as I am going through the install
a window pops up and wants to know my "Root" login information, name and password.
I ignore this cause I have no idea what that is. So then I finish the install, "Install complete"
and so I restart my Amiga. First thing that pops up is a window wanting my Root login
information. Huh??? I never had any, never saw any place to set that up and I am running
OS 3.2 with the new ROMs. I try to restart with the 3.2 Workbench floppy same result.
Does anyone know the standard information it's looking for or how to break this to get
to a Shell command? Any help is much appreciated.
Brad Hansen
-
AmigaOS, including OS3.2, doesn't have any concept of different users. I would suggest reading the AmiTCP documentation, it should explain exactly what it is expecting in this field.
-
https://grimore.org/amiga/install_amitcp
This might help. It is probably from your s:user-startup file. So do the last part of those instructions.
btw, you guys never had multi-user? It was easy - multiple Workbench disks = multiuser :)
(yeah, not quite the same)
-
AmiTCP (and Miami, Roadshow..) is a very minimal BSD unix kernel running on top of AmigaOS, and as such it has concept of users and groups. Similar concept of users and groups was also in the native LAN package Envoy (but with the unfortunate difference that root uid 0 for posix was “nobody” in envoy, iirc).
OS 3.2 has updates that deals owner and group flags in the filesystem - why this suddenly had become relevant one can only speculate.
-
AmiTCP 3.x is really, really old and its Unix roots, as kolla notes, are very apparent and - in my opinion - extremely difficult to configure. What's happening during the installation is that it's asking you to define the root account, not provide unknowable credentials for a hitherto unknown root account. With that information undefined, that's probably why the login system is getting confused post-installation. The documentation should explain this, but I recall the AmiTCP 3.x documentation to be lacking, so perhaps it doesn't. I highly recommend any other TCP/IP stack. Roadshow is the newest one and its author, Olaf Barthel, is one of the best documentation writers on the planet.
@ kolla
The user/group stuff added to 3.2 is likely related to Envoy, which is where C:Owner and C:Group originally come from. If you're using the machine as an Envoy server you can allow/restrict files based on the client's username/group. These extensions have been semi-official for decades, so it's good they're finally formalized. Now if we could just get the rest of Envoy integrated into the OS...
-
If so, I really hope the uid issue can finally be fixed, so 0 is “root” for both Roadshow and Envoy.
(and where is the DOS/7 patch to MuFS?! (kidding, sort of))
-
I used it with my A500 and a Raspberry as a PPP server.
You must specify a username and a password during the installation and choose not to autostart at boot.