Patrick wrote:
For as long as I can remember I've set up a /boot partition with 15MB.
Recently, however, routine kernel security updates (Suse 10.2) need slightly
more space on /boot to perform the updates. What would be the safest way to
get around this?
I've thought of moving some symlinked files to another partition, performing
update and then returning file to /boot. For example, vmlinuz points to
vmlinuz-2.6.18.8-0.1-default which is on /boot.
vmlinuz -> vmlinuz-2.6.18.8-0.1-default
If I move vmlinuz-2.6.18.8-0.1-default to root "/", update and move it back
then I should be OK. Is there something I might be overlooking that could
lead to a catastrophe?
Also, this process is an awkward workaround. Is there a better approach?
TIA, Patrick
I always thought Suse would complain if you made a boot partition less
than 75MB?!
Can't you just do away with the partition? Unmount it move everything to
the root filesystem but still under /boot, re-install grub & use Fdisk
to change the boot flag over. Linux has not needed /boot on a separate
partition for a long time now and using symlinks is messy.
Matthew
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
