Tiny Core Base > Release Candidate Testing
Core v4.2rc1
caminati:
--- Quote from: bmarkus on December 12, 2011, 06:29:37 AM ---
--- Quote from: Guy on December 12, 2011, 06:06:59 AM ---If you use an Ext2 filesystem, what happens?
--- End quote ---
Do not want to use ext2. It is working fine in TC 4.1 and no reason to drop this functionality.
--- End quote ---
+1
(even though this is not an answer to the original question)
Guy:
Testing it with Ext2 is just a way of narrowing down the cause.
If it works ok with Ext2, something has malfunctioned as a result of fat32.
If it does not work ok with Ext2, that is not the cause of the problem.
Knowing this may help resolve it.
bmarkus:
You are free to make such test if you are interested in result :)
roberts:
With a common foundation, being core.gz, base norestore will result in a command prompt.
As noted in the announcement post is xbase.lst, i.e., using lst=xbase.lst norestore will result in a base X/GUI system.
xbase.lst is delivered in the TinyCore iso and should be copied to your working tce directory. Of course it is editable and therefore as a benefit "base" can mean Xorg & jwm as an example, or even, Xorg/XFCE. Whatever is "your" base X/GUI.
roberts:
--- Quote from: bmarkus on December 12, 2011, 04:22:36 AM ---I'm using TC 4.1 on a notebook. There are three partitions, /dev/sda1 is ext4 others or NTFS (for Vista). There is a /tce directory on sda1. TC is booted from USB stick created with Unetbootin. Works fine, this setup is used for extension building, testing, etc.
Now created a stick on the same way with 4.2rc1
Starting tc with base norestore brings up the system with usual tc look and works.
Starting with norestore ends up in infinite 'Checking for extensions... ' with rotating chars.
Doesn't like my collection of extensions.
--- End quote ---
Use boot option showapps to display each extension as it is being loaded should help in resolving this issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version