The collected works of miod - Page 6

jammaster wrote: So, the transfer via the "ethernet restore" on tadpole is successfully ... (transfer DONE !!! god) ...
But after...

NOTHING!

I must see a restore menu/options ... But here ... NOTHING
DAMN!

Now that you have transferred the recovery image to the swap partition, you need to boot off it. Have you tried to boot it afterwards?
:Indigo: R3000 (alas, dead) :Indigo: R4000 x4 :Indigo2: R4400 :Indigo2IMP: R4400 x2 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4400SC :Indy: R4600 :Indy: R5000SC :O2: R5000 x3 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
kjaer wrote: If "minifs" contains a miniroot filesystem, which you have written to partition 1, I rate it unlikely that the name of the file within that miniroot filesystem which contains the kernel you are meant to boot is also "minifs". it may be called 'munix' though. have a look at minifs in a hex editor, you'll be able to find the root directory and filenames pretty easily.

Indeed. According to the SPARCbook 2 documentation, which probably applies to the SPARCbook 1 as well in this case:

tadpole wrote: When the minifs has been loaded onto the SPARCbook successfully, the following menu will be displayed:

Code: Select all

1> Boot Default File
2> Boot Alternate File
3> Change Default File

Enter Choice> 2
Select the option to boot an alternate file and then, from the next menu, select the option to boot from the hard disk:

Code: Select all

New Source for Boot File
1> Hard Disk
2> Ethernet
3> SCSI

Enter Choice> 1
Then when prompted, enter the following file specification:

Code: Select all

Enter file spec> 0 1 vmunix

:Indigo: R3000 (alas, dead) :Indigo: R4000 x4 :Indigo2: R4400 :Indigo2IMP: R4400 x2 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4400SC :Indy: R4600 :Indy: R5000SC :O2: R5000 x3 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
jammaster wrote: I think it's a RSH, RLOGIN problem.
these services are activated in inetd.conf.
Not sure about my hosts???

Restoration of the filesystem is likely done using rcp, thus it requires the server to accept rsh connections as root. You might want to temporarily put a .rhosts file with "+" in the root's home directory on the server, for the time of the restoration process.
:Indigo: R3000 (alas, dead) :Indigo: R4000 x4 :Indigo2: R4400 :Indigo2IMP: R4400 x2 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4400SC :Indy: R4600 :Indy: R5000SC :O2: R5000 x3 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Why not boot single user ("stop for maintainance" on powerup, then get a prompt and enter "single"), mount your disks, and cp from the single-user shell?
:Indigo: R3000 (alas, dead) :Indigo: R4000 x4 :Indigo2: R4400 :Indigo2IMP: R4400 x2 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R4400SC :Indy: R4600 :Indy: R5000SC :O2: R5000 x3 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: 2xR12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :O3x0: 4xR16000 :A350:
among more than 150 machines : Apollo, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...