Oh, I was just reading the manual for silo. What I wrote was not entirely
correct:
The program /sbin/silo <http://swoolley.org/man.cgi/silo> is
used to install <http://swoolley.org/man.cgi/1/install> the first
stage loader by
copying the right first stage loader into the bootblock (unless the
correct first stage is already installed and the -f option
<http://swoolley.org/man.cgi/n/option> is not used
to force it), writes the block number
<http://swoolley.org/man.cgi/6/number> of the first block of the
second
stage loader (usually /boot
<http://swoolley.org/man.cgi/7/boot>/second.b) into it and into the
second stage
loader it records all the block numbers of second.b and the name and
location of the configuration file. The configuration file
<http://swoolley.org/man.cgi/file> itself is
parsed by the boot <http://swoolley.org/man.cgi/7/boot> loader
at <http://swoolley.org/man.cgi/1/at> boot
<http://swoolley.org/man.cgi/7/boot> time. See silo.conf
<http://swoolley.org/man.cgi/5/silo>(5) for
<http://swoolley.org/man.cgi/n/for> details.
This means that the /sbin/silo
<http://swoolley.org/man.cgi/silo> program must be run only if
<http://swoolley.org/man.cgi/if> you install
<http://swoolley.org/man.cgi/1/install>
a new version <http://swoolley.org/man.cgi/version> of SILO
<http://swoolley.org/man.cgi/8/silo> or if
<http://swoolley.org/man.cgi/if> you move
<http://swoolley.org/man.cgi/move> the second stage loader on the
disk. Unlike the LILO bootloader on the Intel platform, you don't have
to rerun it every time <http://swoolley.org/man.cgi/time> you
make <http://swoolley.org/man.cgi/1/make> a change into
/etc/silo.conf <http://swoolley.org/man.cgi/5/silo> or when
you install <http://swoolley.org/man.cgi/1/install> new kernels.
[...]
(if <http://swoolley.org/man.cgi/if> the second
stage loader is moved away or is crippled it might actually
print less <http://swoolley.org/man.cgi/less>
letters from that string
<http://swoolley.org/man.cgi/string> and die).
<http://swoolley.org/man.cgi/1/builtins>
If you recently modified the layout of the disks, perhaps you need to
just run 'silo' again to make sure that 'second.b' can be found?
On Mon, Jul 21, 2014 at 4:26 PM, Jeremy Kister <
[email protected]> wrote:
> On 7/21/2014 4:59 PM, Patrick Baggett wrote:
>
>> please correct me if I am mistaken!] In that case, perhaps you could
>> backup the old `silo` binary and replace it with the newest one? I would
>> think that if you had a USB port you could do this pretty easily using a
>> flash drive (perhaps PCI USB card + flash drive, like I had in my Ultra
>> 10), but if not, you might be able to utilize tftp and pull it from a
>> server using BusyBox.
>>
>
> Worth a shot. I don't have local access to the machine at the moment
> (just network+console). it does have network, though. do you happen to
> know where the newest silo binary is? i'm searching now.
>
>
> --
>
> Jeremy Kister
> http://jeremy.kister.net./
>
>
