Tiny Core Base > Micro Core

Core install with 32 MB RAM on 486

<< < (5/5)

neonix:
What is the purpose of this file?
http://repo.tinycorelinux.net/16.x/x86/release/distribution_files/rootfs.gz

Rich:
Hi neonix
Just what it says. It's the root file system. It contains:

--- Code: ---tc@E310:~$ tree -d TinycoreISOs/Rootfs64TC14
TinycoreISOs/Rootfs64TC14
|-- bin
|-- dev
|   |-- fd -> /proc/self/fd
|   |-- input
|   |-- net
|   |-- pts
|   |-- shm
|   `-- usb
|-- etc
|   |-- init.d
|   |   `-- services
|   |-- pcmcia
|   |-- profile.d
|   |-- skel
|   |-- sysconfig
|   `-- udev
|       `-- rules.d
|-- home
|-- lib
|   |-- modules
|   `-- udev
|-- mnt
|-- opt
|-- proc
|-- root
|-- run
|   `-- udev
|-- sbin
|-- sys
|-- tmp
|-- usr
|   |-- bin
|   |-- lib
|   |   `-- gconv
|   |-- local
|   |   |-- bin
|   |   |-- lib
|   |   |   `-- modules
|   |   `-- tce.installed
|   |-- sbin
|   `-- share
|       |-- doc
|       |   |-- License
|       |   `-- tc
|       |-- i18n
|       |   `-- charmaps
|       |-- kmap
|       |-- locale
|       |-- misc
|       |-- syslinux
|       |-- tabset
|       |-- terminfo
|       |   |-- a
|       |   |-- l
|       |   |-- r
|       |   |-- v
|       |   `-- x
|       `-- udhcpc
`-- var
    |-- cache
    |-- lib
    |-- lock
    |-- log
    |-- run
    |-- spool
    |   |-- cron
    |   |   `-- crontabs
    |   `-- lpd
    `-- tmp -> /tmp

69 directories
--- End code ---

I only listed the directories. There are also about 600 files in there.

If you wish to see all of the contents yourself:

--- Code: ---mkdir tempdir
cd tempdir
zcat /path/to/existing/rootfs.gz | sudo cpio -i
--- End code ---

neonix:
Why I can't unpack core.gz? If TinyCore was was not designed to run that way, then why rootfs.gz was placed in repo?

Leee:

--- Quote from: neonix on December 26, 2025, 01:58:28 PM ---Why I can't unpack core.gz? If TinyCore was was not designed to run that way, then why rootfs.gz was placed in repo?

--- End quote ---
There's no reason you can't unpack core.gz using the same method as for rootfs.gz.

As I understand it, core.gz is literally just rootfs.gz appended to modules.gz.  This is part of a modular approach to building software.  The existence of core.gz just makes it so that you can put together a system with two files (vmlinuz and core.gz) instead of three (vmlinuz, rootfs.gz and modules.gz).

Rich:
Hi neonix

--- Quote from: neonix on December 26, 2025, 01:58:28 PM --- ... then why rootfs.gz was placed in repo?
--- End quote ---
Here's a couple of reasons.

If you do this:

--- Code: ---cat rootfs.gz modules64.gz > core64.gz
--- End code ---
and then boot vmlinuz64 along with core64.gz.
It allows you to run 32 bit programs under a 64 bit kernel.

This gives you a kernel that can manage a large amount of RAM and
allocate up to 4 Gig of RAM to each 32 bit program you are running.

You can not run 64 bit programs in this type of environment.

If you don't want or need any of the included drivers, you can use
rootfs.gz instead of core.gz for your initrd.

Navigation

[0] Message Index

[*] Previous page