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 use exactly the same setup. I'm on 10.2, kernel 2.6.18.8-0.3 using a little over 8Mb of the boot partition. One of the things you might like to check, is whether you have an accretion of files from older kernels that you no longer use. There is little point in keeping them around if you don't have the corresponding /lib/modules files - which in any event, get cleaned out and replaced after each update. (The directories may be there, but they are emptied.)