tinycore_2.4rc5

[jpeters]

I note that it's loading flwm and you removed the post?  (I use tinycore with jwm, as you probably know).
Sorry if perhaps I neglected praise.

I did not delete any post. Sarcasm not necessasy!

my apologies......thought perhaps you were sick of posts about jwm not loading, since we just went through this last release (albeit different reasons).   

[Juanito]

Could you remind me as to what extension you are referring to.

pci-utils and libpci

[tclfan]

Are there any factual bugs noticed by anyone in RC5 so far, or it is pretty much ready for gold release? This is if I can humbly ask this question at all, considering hard work that others have put into this, which is greatly appreciated by many users like me...
So far it seems to me it is just minor wrinkles...

[bigpcman]

The Fifth Release Candidate of v2.4 (tinycore_2.4rc5.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/

Change log for v2.4 Release Candidate 5

* Dropped pci.ids. Use extension

Could you remind me as to what extension you are referring to.

http://forum.tinycorelinux.net/index.php?topic=1715.msg16891#msg16891

What is the significance of dropping pci.ids? Why was it in the base in the first place?

[roberts]

It was a carry over from stats pci tab, Not useful in any way for booting to the minimal desktop, the goal of Tiny Core.

[roberts]

Thank you jls! Please provide as much detail as possible.
As I need to be able to reproduce in order to fix.
 
1. Post the output of showbootcodes command
2. Post your extension list.
3. Post .flg or .lst if used in tce directory.
4. Post details about device being loaded from type and filesystem

I believe it is a corrupt extension, but then you would think .md5.txt would have caught it..

[roberts]

I can't reproduce with my extension collection set and any combination of flags and lists.

But mounting is much different than trying to read each and every file inside an extension.
I believe we hit this once before and some corrupt extensions were found Possibly the md5s were created on the corrupt extension and so not caugut.

Please provide your extension list, or possibly look at what was loaded and try to determine the next one that was to be loaded, or missing.

[roberts]

As a test, I just downloaded, mounted, cpio'ed, unmounted, each and every tcz in the repository and had no errors, no dangling loops or /mnt/test sill mounted.

Anyone else have such?

[jls]

do u want me to try mc or tc ?
in the meantime I can tell u that I tried with mc and everything is in a fat formatted pendrive (hdd mode) using your usbinstall script.
append line:

Code: [Select]

APPEND initrd=/tce/tinycore.gz quiet waitusb=5 tce=UUID="DCD8-4898" settime TZ=CET-1CEST-2,M3.5.0,M10.5.0 noutcthe extension were the core ones including xvesa and jwm.
If I remeber well I also tried booting only wiht the core ones.
core2ram.flg tcz2ram.flg

[Vegeta]

Try adding "echo 1024 > /proc/sys/dev/rtc/max-user-freq" to your system startup scripts.

[jpeters]

jwm loading now.  Thanks !!

   

[roberts]

Update.
Because of apparent anomalies starting with the change to cpio, it has been decided to drop cpio in the extension loading routine and return to the use of rsync. I have produced a cut with such change for internal team review..

[perthie]

Which rc versions are using cpio?

[roberts]

4 & 5

[bigpcman]

Update.
Because of apparent anomalies starting with the change to cpio, it has been decided to drop cpio in the extension loading routine and return to the use of rsync. I have produced a cut with such change for internal team review..

As an educational question, what were the benefits of using cpio instead of rsync?