Dirk Heinrichs wrote: > Am Freitag, den 23.01.2009, 01:53 -0600 schrieb ext Dale: > > >> I'll show this just in case it will give someone ides. >> > > Here's another approach: > > % ll /boot > insgesamt 9644 > lrwxrwxrwx 1 root root 1 17. Jan 2006 boot -> ./ > drwxr-xr-x 2 root root 1024 21. Mai 2008 grub/ > drwx------ 2 root root 12288 11. Okt 2005 lost+found/ > -rw-r--r-- 1 root root 4892720 22. Jan 14:25 vmlinux-2.6.28.1.gz > -rw-r--r-- 1 root root 4892272 16. Jan 15:32 vmlinux-2.6.28.gz > lrwxrwxrwx 1 root root 19 22. Jan 14:26 vmlinux.gz -> > vmlinux-2.6.28.1.gz > lrwxrwxrwx 1 root root 17 22. Jan 14:26 vmlinux.old.gz -> > vmlinux-2.6.28.gz > > No System.map (what's it good for, anyway?) > No .config (it's in /proc/config.gz). > No need to edit grub.conf as the symlinks are updated using a small > script (which also removes old module directories from /lib/modules). > No initrd as an embedded initramfs is used (hence the size of the > kernels). > > Bye... > > Dirk >
But if a kernel gets corrupted or accidentally deleted, there will be no /proc/config.gz since the kernel won't boot. I have that turned on here to but I'm not going to put all my eggs in that one basket. I couldn't write a script anyway plus I only update kernels once in a blue moon anyway. I'm still running 2.6.23 right now. The new one is compiled and ready but I just haven't rebooted in a while. I was wondering about that system.map thing. It's been there a long while. I just redone my install and I only saved /boot, make.conf, world and a couple other files, plus my /home naturally. Dale :-) :-)
