Tiny Core Base > Release Candidate Testing

tinycore_v2.9rc4

<< < (5/8) > >>

jls:

--- Quote from: jur on February 18, 2010, 06:51:27 AM ---I think I have found the problem.

In both the aforementioned cases, once I moved the booting files to a directory called /boot, booting proceeds fine. Permissions for /dev/shm are also correct.

So the difference between tc-2.8 and tc-2.9rc4 is, the booting files cannot be in /tce in 2.9rc4, while with 2.8.1 (and prior versions) this presents no problem.

--- End quote ---
I also moved bzimage and tinycore.gz from tce to boot and now chromium shows the pages

jls:

--- Quote from: curaga on February 18, 2010, 09:08:05 AM ---@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.

--- End quote ---
so this menas that using this rc4, the apps only start in english?

bmarkus:

--- Quote from: jls_legalize on February 18, 2010, 11:32:31 AM ---
--- Quote from: curaga on February 18, 2010, 09:08:05 AM ---@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.

--- End quote ---
so this menas that using this rc4, the apps only start in english?

--- End quote ---

Yes

jur:

--- Quote from: Juanito on February 18, 2010, 08:30:18 AM ---
--- Quote from: jur on February 18, 2010, 06:51:27 AM ---once I moved the booting files to a directory called /boot, booting proceeds fine.

--- End quote ---

By "booting files", do you mean bzImage and tinycore.gz/microcore.gz and/or Xlibs.gz, XProgs.gz and Xvesa.gz?

--- End quote ---
Yes.

curaga:
I see now, the core gz code had picked up your tinycore.gz/microcore.gz images.

Navigation

[0] Message Index

[#] Next page

[*] Previous page