Re: SILO on ss20
On Tue, Apr 09, 2002 at 05:20:33PM -0500, Matthew Twomey wrote:
> Quandary: On my ss20 (prom >2.0) SILO can only see files on the 1st gig of
> the drive. I wanted a root partition larger than 1 gig. My solution was to
> create a 10 meg partition (at the beginning of the drive) and mount /boot
> to it.
I have something similar, a separate /boot fs.
> This works, but the silo.conf file also has to be in /boot and I have to
> call the silo binary with the '-c' option to specify where the silo.conf
> file resides.
OK...
> For all practical unix/linux purposes this is file with me, but I don't
> like that it 'breaks' Debian or at least deviates from the /etc/[conffile]
> standard, I have have to take extreme care when updating the kernel
> package so I don't leave myself not booting. After an upgrade I have to
> manually edit silo.conf and rerun the binary with the '-c'.
I have placed silo.conf in the /boot fs and made a symbolic link from
/etc/silo.conf to /boot/silo.conf. Why do you rerun silo after an
upgrade? It's not lilo you know... look for example in the silo man
pages. Or am I missing a point here?
Cheers,
/ChJ
--
To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: