Dyne Software Development Kit

The dynesdk script provides you with functional commands to make modifications to your current dyne system and pack them back into an iso; of course you need to be root on your machine in order to use it, plus you need some generic experience with GNU/Linux systems.

If you're there, just type dynesdk -h into an xterm to get this little help: 

[*] dyne:bolic SDK version 2.0 - software development kit
 .  Copyleft 2003-2005 by jaromil - RASTASOFT
[*] SYNOPSIS: dynesdk [-hv] [-p prefix] [-u user -h host] COMMAND
 .  -h     print this help
 .  -v     print out the version of this tool
 .  -p     path to the SDK directory (default /vol/hd5/dyne/SDK)
 .  -m     additional modules to add in ramdisk
 .  -q     be quick and skip checksums and crypto sigs
[*] MODULE DEVELOPMENT COMMANDS:
 .  mksdk      create an SDK environment inside the harddisk dock
 .  mount      re/mount all SDK/modules in /opt
 .  squash     packs all the add-on modules into the SDK/cdrom
 .  mkiso      packs the SDK/cdrom directory into a bootable iso
[*] CORE DEVELOPMENT COMMANDS:
 .  mkinitrd   packs the initrd.gz into the SDK/cdrom
 .  mkusr      packs the dyne.sys in the SDK/cdrom

Establish an SDK

Before starting modifying the system, you need to create an SDK.

In order to have an SDK you first need to create a DOCK on your harddisk: this is very simple, just copy the dyne/ directory from the CD in the root of one of your partitions and then reboot. For further information about docking please refer to the User's manual and to the Docking page on wiki.

Optionally, you can also add an entry to your lilo or grub bootloader, then you won't need a CD anymore to boot dyne:II.

Once you make sure you are running a docked dyne, you can proceed creating an SDK. As root, type in a shell: 

[d:b] ~ # dynesdk mksdk

you'll be prompted with two questions: it is safe to answer no in both cases, unless you want to change things in the dyne:II core:

  • [?] do you want to uncompress the dyne.sys (y/N) ?
  • [?] do you want to download the kernel sources (y/N) ?

in case you don't give an answer, it will default to NO after 10 seconds and go on.

this procedure will create an SDK directory inside $DYNE_SYS_MNT/dyne, then populate it with development files that are downloaded from the http://dev.dynebolic.org subversion repository, in particular, you'll find:

  • SDK/startup - with all latest startup files that belong to /etc
  • SDK/devel - with the latest dynesdk script, from now on use this dynesdk'''
  • SDK/cdrom - where all the files needed to do a bootable cdrom are downloaded

There you go! now you have an SDK :) but what to do with it?

Using an SDK

With the SDK you can pack all the modifications to your running system inside a new CD ISO.

This means that, if you have a nest, then all the contents of your system, including your changes and additions to it, will be included as a default setup in the ISO that you create, with a simple command: 

[d:b] ~ # dynesdk mkiso

You can use the SDK to create new .dyne modules: that's the best way to add new applications to dyne:II so that you can share them with other users and add them into new ISO files, just dropping a file into a directory.

To know how to do that proceed now to DyneModules documentation.

And in case you really want to change the core system, here are some instructions, but be aware you can break the functionality of your running dyne

Pack a new RAMDISK

  • dynesdk mkinitrd (when prompted, answer YES)
    • packs the contents of /etc /bin /sbin and the root filesystem structure
    • include the latest startup scripts from SDK/startup (update from online repository)
    • will create a compressed RamDisk inside SDK/cdrom/dyne/initrd.gz

Pack a new /USR

  • dynesdk mkusr
    • packs the contents of /usr into a squashed filesystem in SDK/cdrom/dyne/dyne.sys