Tiny Core Base > Release Candidate Testing
tinycore_2.4rc3
jpeters:
Robert, is there a non-hastle way of including a visible boot option? If not, I can live with it. Thanks
roberts:
--- Quote from: meo on October 03, 2009, 08:20:07 AM ---Hi again Robert!
Thanks for your response but I still think there is something that isn't well with the Refresh Menu option, The screen went black when pressing it. All was made from scratch with no backup or restore. I usually test this out when there is a new cut. After that (if nothing dramatically has changed) I just use tce=hda6 and restore=hda1. Those contain the apps I need and the files that have to be restored to make tinycore 2.4.x work on my 8,5 years old laptop. So I really find tinycore very swift and comfortable to use in my daily use of a computer. Thanks a lot to all of you who are making tinycore progress.
Have fun with tinycore,
meo
--- End quote ---
Booting tinycore with base norestore and selecting Refresh Menu still works fine for me.
I wonder why there is a need to be selecting Refresh Menu, the extension loader handles menu, icons and desktop update. You are using flwm and tinycore?
A black screen and with a large X typically means no window manager was found. If you boot your system and then first select a shell and then Refresh Menu, you should be able to use the Shell window to see if you can type flwm& to restart the window manager.
But at this point I still cannot reproduce your error.
roberts:
--- Quote from: jpeters on October 03, 2009, 04:09:42 PM ---
Robert, is there a non-hastle way of including a visible boot option? If not, I can live with it. Thanks
--- End quote ---
I am still tyring a few concepts. I want the average use to see a cleaner consistent boot screen. I do not like hundreds of files being printed to screen. I do not do that with the files being restored, which is very similar. Some my argue that seeing files being restored is more important than extension names being displayed during boot. Some want only a GU curtain like Slim. I do however, wish to provide a way for developer types to see more information as extensions load. Still in progress.
roberts:
--- Quote from: bmarkus on October 03, 2009, 12:09:31 AM ---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.
--- End quote ---
This has already been addressed. The umount command did not free loop device when tcz was temporarily mounted to copy to ram. Using the busybox umount -d will and does free the loop device.
So, it was already brought to my attention and is solved in the next cut.
jpeters:
I noticed that "zcat $BOOTDIR/tinycore.gz | sudo cpio -i -H newc -d" doesn't seem to work; are we using something different now? (sorry if this is already posted somewhere...)
I just saw that busybox cpio was dropped ; I'll check out GNU
I'm not sure what docs to be looking at regarding remastering. gnutils?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version