|
⇤ ← Revision 1 as of 2003-12-08 15:38:41
Size: 1519
Comment:
|
Size: 1686
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| '''dbspac''' reads an ISO image from a file or from a raw CD device, and unpacks it into a directory tree on your hard disk, into which you can chroot and, to a certain extent, test. | '''dbspac''' reads an ISO image from a file or from a raw CD device, and unpacks it into a directory tree on your hard disk. You can chroot into this tree and, to a certain extent ti will run. It won't be exactly the same as a true running dynebolic because the hardware setup and initial environment will be that of you system, not of dynebolic. |
| Line 9: | Line 9: |
| '''dbpacc''' is the opposite - it packs up a runnable tree and creates a dyne:bolic ISO image for burning to CDs. | '''dbpacc''' is the opposite - it packs up a dynebolic tree and creates a dyne:bolic ISO image for burning to CDs. |
| Line 19: | Line 19: |
| If you want to compile programs to include in dyne:bolic, your system must compile against GLIBC 2.2 or earlier - GLIBC2.3 is not yet included in dyne:bolic (and may never be if we pass to using uclibc in the next release... watch this space!). You can find out if you have a compatible GLIBC on your system by compiling a simple C program, copying the binary executable onto a running dyne:bolic system and trying to run it. If you have GLIBC2.3 it will say so. | If you want to compile programs to include in dyne:bolic, your system must compile against GLIBC_2.2 or earlier - GLIBC_2.3 is not yet included in dyne:bolic (and may never be if we pass to using uclibc in the next release... watch this space!). You can find out if you have a compatible GLIBC on your system by compiling a simple C program, copying the binary executable into a running dyne:bolic system and trying to run it. If you have GLIBC_2.3 it will say so. |
This is a page dedicated to people who want to get their hands inside dyne:bolic and modify it.
Modify the ISO with dbspac and dbpacc
Two shell scripts
dbspac reads an ISO image from a file or from a raw CD device, and unpacks it into a directory tree on your hard disk. You can chroot into this tree and, to a certain extent ti will run. It won't be exactly the same as a true running dynebolic because the hardware setup and initial environment will be that of you system, not of dynebolic.
dbpacc is the opposite - it packs up a dynebolic tree and creates a dyne:bolic ISO image for burning to CDs.
You need lots of disk space: dyne:bolic's 444MB CDROM unpacks to 1.8GB of data, and the packing process requires a further 444MB of temporary space as well as the 444MB for the new ISO image it is creating.
System requirements
You will need a pentium computer running Linux kernel 2.4.19 or later, with the squashfs kernel patches applied to the kernel and the squashfs tools installed.
If you want to compile programs to include in dyne:bolic, your system must compile against GLIBC_2.2 or earlier - GLIBC_2.3 is not yet included in dyne:bolic (and may never be if we pass to using uclibc in the next release... watch this space!). You can find out if you have a compatible GLIBC on your system by compiling a simple C program, copying the binary executable into a running dyne:bolic system and trying to run it. If you have GLIBC_2.3 it will say so.
Whence?
These scripts are available under http://freaknet.org/martin/dynebolic
Further help is available in the comments at the top of the scripts themselves.