2008/2/25, Don Jackson <[EMAIL PROTECTED]>: > The issue is that when building and installing new kernels (eg, when a > new security patch is released), it is not totally obvious to the > (automated) build script what the file /bsd really is, is it the > uniprocessor kernel, or a link to the multiprocessor kernel? > If the latter, than blindly copying the new uniprocessor kenel to /bsd > is probably not what you want to do. > > With my proposal, new kernels can be safely copied to /, since they > have unique and distinct names.
Just use links. Works great for me. # ls -1i /flash/bsd* 6 /flash/bsd 5 /flash/bsd.old 5 /flash/bsd_large_42_PCENGINES_CUST2_vrpatch_err05_cvs24-01-2008 6 /flash/bsdl42_PCENGINES_err08_cvs25-02-2008-patch_vr-pach_ike P.K.
