mc slow extension loading at boot

[uggla]

Under 3.x/archive/version/distribution_files.

Any change wrt copy2fs? Enabling it would have this effect.

Not sure what you mean, how can I check this?

[curaga]

List the files in your tce dir. If there exists either copy2fs.flg or copy2fs.lst, some or all extensions are copied to ram instead of mounting.

[quanpin]

Where can I get the previous version of wbar, Xlibs and Xprogs?

go to there http://wiki.tinycorelinux.net/wiki:mirrors
and take a mirror, a lot of  mirrors  have not update! you can take the old version.

what's about they?  just update to 06-07?
2011-06-07       nvidia-texture-tools.tcz   nvidia-texture-tools.tcz.info    2011/06/07 - Original   
2011-06-06       pinfo-doc.tcz   pinfo-doc.tcz.info    2011/05/27   
2011-06-06       pinfo.tcz   pinfo.tcz.info    2011/05/27

[uggla]

I've finally had some progress!

I had neither copy2fs.flg or copy2fs.lst in my tce dir.

When I once again tried mc3.6 I still had the same slow boot as introduced with 3.7. That made me think I've perhaps gone mad or that there's been strange stuff going on with the space time. Then I decided I would test for persistent system settings by renaming my home folder and rebooting with a totally clean home. That did wonders! Boot time is now back to normal (very fast).

Any ideas where to find the cause of this?

[bmarkus]

What is about the size of your backup file? Restoring a large backup may take some time.

[uggla]

mydata.tgz = 1,96 KB

[jackson.lee]

Hi uggla

You could take a look at the output of  dmesg  and see if maybe your hard drive is being put
into PIO instead of DMA mode.

Rich,
Am using code you suggested on the forum.    Good thinking    
Along the lines of this thread,     Have been making timed bootups, listed below.

HP motherboard, 2.8 GHz speed, 1 GB RAM.
Booting from a USB pendrive, partitioned EXT2 and VFAT32.

Have TCL installed in USB sdb1,         with /tce on sdb1 and sdb2.
sdb1 is EXT1,     sdb2 is vFAT (of course /tce is internally formated to EXT2).
Found that it is necessary to use the UUID,
otherwise TCL will scan for Hard-Drive installation of /tce (and if there WILL find and LOAD it).

On USB bootup,
Select bootcode (1) in order to load  sdb1/tce 
Select bootcode (2) in order to load  sdb2/tce 

Then,   start the clock !
 
(1)
title =1={ TINY-CORE : Rich-TCL ( loads sda1/tce/optional/apps.tcz  \n (find(MARK)-kernal(uuid)-initd)
   find --set-root --ignore-floppies --ignore-cd  /LG-MARK
   kernel  /tc-sys/bzImage  psubdir=/tc-sys  quiet  waitusb=10:UUID="074e2d15-9ac0-4466-8d4c-9650d908c101" tce=UUID="074e2d15-9ac0-4466-8d4c-9650d908c101"
   initrd  /tc-sys/tinycore.gz

(2)
title =2={ TINY-CORE : Rich-TCL ( loads sda2/tce/optional/apps.tcz  \n (find(MARK)-kernal(uuid)-initd)
   find --set-root --ignore-floppies --ignore-cd  /LG-MARK
   kernel  /tc-sys/bzImage  psubdir=/tc-sys  quiet  waitusb=10:UUID="074e2d15-9ac0-4466-8d4c-9650d908c101" tce=UUID="07DB-A20C" TYPE="vfat"
   initrd  /tc-sys/tinycore.gz

Table of results:
------------------------------------------------------------------------------------
SDB. . . ColorBg. . .Read-USB. . .Load-RAM. . .Load-Ext. . .Exit-Save. . .
.1          Yellow             30s              4s               1              80s
.2          Purple             30s              4s               1               1s
-----------------------------------------------------------------------------------

No complaints, just noting times, along the lines of this thread.

Your bootcode was researched as best as I can.  
TCL Docs are terse.
grub4dos docs are not complete.

jackson.lee
 

[coreplayer2]

On reboot after 3.7 install I too experienced this anomaly.   The progress bar (if you call it that) never stopped spinning during loading of extensions in fact never completed the boot.  This was on a FAT32 drive.  Had to wipe the drive, reinstall using ext2.  Was able to boot again however have not since been able to install any apps.

But am going to drop in version 3.7.1 to see if this provides a relief to the issue.

[Guy]

You can expect filesystem corruption when using fat16 or fat32, and malfunctions as a result.

Use ext2 on usb drives and ext4 on hard drives.

[coreplayer2]

Really? oh my!   must have been a misread article somewhere, because I would have bet money on reading somewhere that FAT32 was an acceptable format for USB.   If not, for sure there is a core wiki which describes installing tinycore to a USB using ext2 with a FAT32 partition for sharing files, this I'm having great trouble with.  Whenever the USB drive is plugged into a windows machine the FAT32 partition is unreadable.

Back to the drawing board I guess

[gerald_clark]

If you cannot access your fat32 partition from windows, it is probably not really fat32.
The partition flag is just a hint for the OS and does not guarantee filesystem type.
Run a mount command from TC and see what it is mounted as.

[Guy]

http://wiki.tinycorelinux.net/wiki:install_with_partition_for_sharing

fat32 is ok for the usb.

It is not ok for the tinycore tce, home, or opt directories.


Some people use fat32, but they are much more likely to experience filesystem corruption.

[Juanito]

Whenever the USB drive is plugged into a windows machine the FAT32 partition is unreadable.

I seem to remember that windows can only read the first partition on a usb stick, is the fat partition the first one?

[uggla]

This is getting stranger.

It seems the more I put into my home/tce directory, the slower extension loading at boot I get. After I realized this I timed my boot, created a new, empty home/tc, and timed once more. The time difference was 13 seconds! What is going on? Do I have to save all my files somewhere else to keep the boot time down? 

[curaga]

That is very weird. What are your bootcodes?

Do you have any custom scripts, or things autostarting?