Hi jshorthouse
I came across that option when searching, but doesn't the tce directory also contain the files for the kernel and base system? ...
Not necessarily. Here is the layout on one of my machines:
Root directory of the boot drive:
tc@E310:~/info$ ls -l /mnt/sda1/
total 44
drwxr-xr-x 3 tc staff 4096 Jan 31 13:42 boot/
drwxrwxr-x 3 root staff 4096 Apr 22 08:19 home/
drwx------ 2 tc staff 16384 Jul 12 2019 lost+found/
drwxrwsr-x 3 root staff 4096 Apr 2 22:06 opt/
drwxrwxr-x 5 tc staff 4096 May 3 20:55 tce/
drwxrwxr-x 4 tc staff 4096 Mar 31 15:57 tce64/
drwxrwxr-x 4 tc staff 4096 Mar 21 00:57 tce64TC11b1/
drwxrwxr-x 4 tc staff 4096 Feb 20 14:28 tce64TC11b1.bak/
tc@E310:~/info$
As you can see, it has multiple TCE directories, both 32 and 64 bit.
boot sub-directory of the boot drive:
tc@E310:~/info$ ls -l /mnt/sda1/boot/
total 65980
-rw-r--r-- 1 tc staff 9131528 Jul 12 2019 core.gz
-rw-r--r-- 1 tc staff 9627207 Oct 16 2019 core64.gz
-rw-r--r-- 1 tc staff 10407852 Nov 28 20:01 corepure64.gz
-rw-r--r-- 1 tc staff 11059939 Jan 14 12:05 corepure64TC11beta1.gz
drwxr-xr-x 2 tc staff 4096 Jul 18 2019 grub/
-rw-r--r-- 1 tc staff 6826959 Oct 16 2019 modules64.gz
-rw-r--r-- 1 tc staff 2800248 Oct 16 2019 rootfs.gz
-rw------- 1 tc staff 3587966 Jun 11 2019 rootfs64.gz
-rw-r--r-- 1 tc staff 4295328 Jul 12 2019 vmlinuz
-rw-r--r-- 1 tc staff 4721024 Oct 16 2019 vmlinuz64
-rw-r--r-- 1 tc staff 5084544 Dec 17 19:06 vmlinuz64TC11beta1
tc@E310:~/info$
Here you find multiple kernel (vmlinuz) and initrd (corexxx) files.
Here is the config file for grub-0.97-splash:
tc@E310:~/info$ cat /mnt/sda1/boot/grub/menu.lst
default 0
timeout 10
title TC10.1_32bit
root (hd0,0)
kernel /boot/vmlinuz quiet tce=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" home=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" opt=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" printk.time=1 syslog nodhcp vmalloc=256MB noisapnp nozswap
initrd /boot/core.gz
title TC10.1_32bit_backup
root (hd0,0)
kernel /boot/vmlinuz quiet tce=UUID="22559ae7-7e12-4a3b-9efa-6f8c8a9a8a6a" home=UUID="22559ae7-7e12-4a3b-9efa-6f8c8a9a8a6a" opt=UUID="22559ae7-7e12-4a3b-9efa-6f8c8a9a8a6a" printk.time=1 syslog nodhcp nozswap vmalloc=256MB noisapnp
initrd /boot/core.gz
title TC10.1_Core64
root (hd0,0)
kernel /boot/vmlinuz64 quiet tce=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" home=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" opt=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" printk.time=1 syslog nodhcp noisapnp
initrd /boot/core64.gz
title TC10.1_CorePure64
root (hd0,0)
kernel /boot/vmlinuz64 quiet tce=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8"/tce64 home=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" opt=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" printk.time=1 syslog nodhcp noisapnp norestore
initrd /boot/corepure64.gz
title TC11.0beta1_CorePure64
root (hd0,0)
kernel /boot/vmlinuz64TC11beta1 quiet tce=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8"/tce64TC11b1 home=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" opt=UUID="543cac60-3224-4cab-b1d5-008407dd9ce8" printk.time=1 syslog nodhcp noisapnp norestore
initrd /boot/corepure64TC11beta1.gz
title TC9_Core64
root (hd0,0)
kernel /tce/boot/vmlinuz64 quiet waitusb=5:UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" tce=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" home=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" opt=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" printk.time=1 syslog enable_mtrr_cleanup
initrd /tce/boot/core64.gz
tc@E310:~/info$
If you look at title TC10.1_32bit_backup you'll see its TCE directory is on a different partition (different UUID) from the other entries.
If you look at title TC10.1_CorePure64 you can see the TCE directory is listed by UUID/path because those extensions are 64 bit.