search for: tc502rt32

On 2014?03?07? 23:05, Ady wrote: > I understand that these remarks might seem not the main issue, but I > tend to think that once you are successful while using only "default" > > values and in a minimalistic case, you could add complexity > (different paths, multiple firmwares, additional kernels, multiple > cfg files...). Ady, Thanks. I will follow your advice to

...is a symlink to a directory containing whatever version I'm testing (say sl603p7/ for 6.03-pre7) since I have about 20 versions prepped for use at the moment, half of which I built for testing various patches. e6/b/ is a symlink to ../b/ and contains tck3810i64.bz (TinyCore 5.0 x86-64 kernel), tc502rt32.gz (TinyCore 5.0.2 root-only 32bit), tc502rt32m64.gz (TinyCore 5.0.2 modules for the x86-64 kernel) and tckscsi64.cgz (A CPIO.GZ containing the SCSI modules for the x86-64 kernel and a file to mark it as loaded on boot). The LABEL stanza I use is: LABEL tc MENU LABEL TC LINUX b/tck3810i64...

...gt; containing whatever version I'm testing (say sl603p7/ for 6.03-pre7) > since I have about 20 versions prepped for use at the moment, half of > which I built for testing various patches. > > e6/b/ is a symlink to ../b/ and contains tck3810i64.bz (TinyCore 5.0 > x86-64 kernel), tc502rt32.gz (TinyCore 5.0.2 root-only 32bit), > tc502rt32m64.gz (TinyCore 5.0.2 modules for the x86-64 kernel) and > tckscsi64.cgz (A CPIO.GZ containing the SCSI modules for the x86-64 > kernel and a file to mark it as loaded on boot). > > The LABEL stanza I use is: > > LABEL tc >...