vtcqa@shamash.cdc.com ( VTC) (06/04/90)
First: I am knew to 'the wonderful world of Apollo' - someone gave me a DN300. Hopefully I will make sense here..... I lost the registry ( rgyd won't execute ), so I figure I will just run rgy_create and start from scratch. Since it wasnt on the machine, I ftp'd rgy_create from a machine at work to a pc. Then I used KA9Q NOS to ftp this from a pc at my house to the DN300. When I try to run rgy_create, stuff like this comes up: ( ??? denotes graphic characters) /install/tools/rgy_create:???: not found /install/tools/rgy_create:???: not found .. .. .. /install/tools/rgy_create:??? ??? ???: not found /install/tools/rgy_create: syntax error at line 1: `end of file' unexpected .. .. I have also seen a message like 'unexpected control character in line 1' come up. After screwing around abit, I found that almost any executable that I transfer to the DN300 does pretty much the same thing. How do you get an executable to one of these if it is not on the network ? What is going on here? Also, if one of you kind people would offer to help me get the registry problem fixed, I would greatly appreciate it. Right now I can't add accounts or change passwords etc. This is going to be used for public access unix via Amateur Packet Radio - .ampr.org . Oh yeah - I am using SR10.1 and BSD4.3 for an environment. Jeff Comstock 44.94.3.12 nr0d.ampr.org 44.94.3.23 at386.nr0d.ampr.org 44.94.3.28 brainiac.nr0d.ampr.org <-- This is the DN300
thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) (06/04/90)
> First: I am knew to 'the wonderful world of Apollo' - someone gave me a > DN300. Hopefully I will make sense here..... Welcome to the best computers around (my biased opinion. No flames please.) > I lost the registry ( rgyd won't execute ), so I figure I will just run > rgy_create and start from scratch. Since it wasnt on the machine, I ftp'd > rgy_create from a machine at work to a pc. Then I used KA9Q NOS to ftp this > from a pc at my house to the DN300. When I try to run rgy_create, stuff > like this comes up: ( ??? denotes graphic characters) > /install/tools/rgy_create:???: not found > /install/tools/rgy_create:???: not found > .. > .. > .. > /install/tools/rgy_create:??? ??? ???: not found > /install/tools/rgy_create: syntax error at line 1: `end of file' unexpected > .. > .. > > I have also seen a message like 'unexpected control character in line 1' > come up. After screwing around abit, I found that almost any executable > that I transfer to the DN300 does pretty much the same thing. How do you > get an executable to one of these if it is not on the network ? What is > going on here? I'm surprised it's "almost any" executable, and not "all executables." It sounds like you're losing your file-type when going across the ftp link. The shell is trying to interpret the program as a set of shell commands. You can either play around with "obty" (in /etc) to modify the type, and hope that you aren't missing any header-info, or you can wbak the file(s) you want into an ascii file, ftp that, and then rbak from the ascii file at your destination: wbak filenames -l -pdtu -to /tmp/backup_file <ftp from machine A to machine B> rbak -from /tmp/backup_file -all -l -dacl -pdt That should protect the COFF format from ftp corruption. > Also, if one of you kind people would offer to help me get the registry > problem fixed, I would greatly appreciate it. Right now I can't add > accounts or change passwords etc. This is going to be used for public > access unix via Amateur Packet Radio - .ampr.org . Oh yeah - I am using > SR10.1 and BSD4.3 for an environment. I've had problems changing accounts etc (no rights to database) now that I changed from sr9 master to sr10 master (we run a mixed network). Other administrators _can_ make changes, so I think that it's something that I messed up. You can (almost) always get around that problem by logging in as 'root' or '%.locksmith' on the node that holds the master registry (this is documented in "Managing Aegis System Software", in the chapter on 'Creating and Maintaining the Registry' -- page 4-9. Hope this all helps John Thompson Honeywell, SSEC thompson@pan.ssec.honeywell.com thompson@pan.ssec.honeywell.com@cim-vax.honeywell.com