Tiny Core Base > Release Candidate Testing

tinycore_2.4rc3

<< < (3/9) > >>

bmarkus:

--- Quote from: roberts on October 02, 2009, 06:09:47 PM ---
I no longer display extensions as they are  being loaded, with upwards of 100 or so, it takes too much time to write to screen. Besides, I do not display each file as it is being restored, nor do I display each boot codes as it is being checked. So we now have a more consistent and cleaner boot screen.


--- End quote ---

What is about a number of loaded extensions instead of rotating -|=\ or a simple progress bar?

roberts:
Because rotdash is and has been the standard indicator that processing is occuring as shown above with udev and below with restore. Any other interaction will only slow down the boot process.

bmarkus:
On a clean system the first loop device is /dev/loop0. Installing extensions in RAM is consuming a loop device for each extensions. For example after installing Midnight Commander and its 3 dependencies first loop device is /dev/loop4 according to 'losetup -f'

It means, that after loading 320 extensions to RAM in my case no any free loop device available even when no any mounted loop.

Just for checking mounting and unmounting an extension manually as a loop device next free loop device remains the same after.

EDIT: Extensions at the end of the list (in alphabetic order) are not installed as no free loop device available.

MikeLockmoore:
As excited as I am to get started using 2.4... I'm having problems with 2.4rc3.  I had a bunch of .tcz's in my hdc4/tce directory.  I have been boothing 2.3.1 with the options:

  tce=hdc4 noswap laptop

In my menu.lst, I copied the 2.3.1 section for 2.4rc3, pointed it to the new bzImage and tincycore.gz files, and used the same boot options listed above.  2.4rc3 boots right up and displays the flwm desktop, but no extensions are loaded, and if I go to the status window in the control panel, the extensions list is empty.  I can can use AppBrowser to install extensions, but they get stored in the home folder (/home/tc), and if I reboot, they will not be automatically reloaded.  

I tried to boot with the option tce=hdc4/tce_2_4, to create a new 2.4-specific tce directory, but booting like this does not create the hdc4/tce_2_4 directory, nor does installing apps from appbrowser.   ???  What am I doing wrong?

My restored files are ok that come from mydata.gz.  I tried to reset .xsession and .profile from /etc/skel to make sure those files where not causing a problem, but I did not see any change in the tce/ situation.  Is there something else I can do to troubleshoot this?  Or do differently to set up a tce/ that works?  Thanks for any help.
--
Mike L.

bmarkus:
How to identify version of running system? I do not find a solution. A simple text file like /etc/tcversion with 2.4rc3 in would be sufficient.

Navigation

[0] Message Index

[#] Next page

[*] Previous page