the CDE directory

[waslit]

  Im just trying to understand something real simple. I noticed that in 4.3x there is a cde directory where extecnsions are located. But in 3.x, and I assume lower, the directory is not there. Is that because it was added later? And then how were the extensions located? I did find this in the wiki but not really sure if I'm just barking up the wrong tree. Man that diidnt make any sense, I meant looking in the wrong direction not barking up wrong tree 

cat microcore.gz Xlibs.gz Xprogs.gz Xvesa.gz > my_xcore.gz

[Rich]

Hi waslit
For most users, the tce directory is where all of your extensions are kept, and it must be writable.
Somewhere in the 4.x series, a CDE (CD Extensions) directory was added, this is a read only
directory to allow extensions to be included on read only media. That's the simple explanation,
if you want more details, you'll have to search the forum.

cat microcore.gz Xlibs.gz Xprogs.gz Xvesa.gz > my_xcore.gz

That command simply combines those files basically creating tinycore.gz. Most users have no
need to do this type of thing.

[bmarkus]

tce directory is where all of your extensions are kept, and it must be writable.

... and your backup file kept there too.

[waslit]

hmmmm I see. That would explain why when using the 2.6.xx kernel it doesnt see that directory or hangs. I will have to do further looking then but that does help ty.

[waslit]

hmm dont seem to really be getting anywhere. Is there something specific I need to do to make a 2.6.xx kernel to look for the cde directory? Or will  a sipmle tce= option work?

[gerald_clark]

It has nothing to do with the kernel.

[waslit]

weird? Cause it worked fine on kernel 3.0.3 but since I went down to 2.6 its not..... Maybe Im just getting side tracked because it appears to freeze around that area. More test I guess

[bmarkus]

weird? Cause it worked fine on kernel 3.0.3 but since I went down to 2.6 its not..... Maybe Im just getting side tracked because it appears to freeze around that area. More test I guess

Which TC version have you been using with 2.6 kernel?

[waslit]

been using the latest one, but needed to use an older kernel like 2.6. So I tried to use the kernel from the src tree in the TC repo and it appears to just halt. At first always at loop module loaded but after more trials it is pretty random. Initially I remembered the extensions loading next and that what made me thought that but then it should just go to prompt. Am I reaching to far trying the older kernel with the latest release maybe?

[Rich]

Hi waslit
If you need to run an older kernel, try running Tinycore 3.8.4.
It's quite possible that some of the files in the TC4.3 distribution were compiled to run on the 3.x kernel and won't
run with a 2.6 kernel.

[roberts]

Do not mix 3.x and 4.x systems. Obviously there is a reason why there are separate repositories.

[hiro]

Is there a list or something which wouldn't work anymore if used with older kernels?
I assume glibc for example won't work with older kernels because it was compiled against newer kernel headers.

[hiro]

Obviously there is a reason why there are separate repositories.

Obviously some things don't have a reason.

[waslit]

Yea its no biggie. Oh well

[curaga]

Is there a list or something which wouldn't work anymore if used with older kernels?
I assume glibc for example won't work with older kernels because it was compiled against newer kernel headers.

udev and glibc mainly, and by extension of glibc, everything compiled on 4.x.