Re: [Hackmeeting] Zen Room

Poista viesti

Vastaa
Lähettäjä: c1cc10@ecn.org
Päiväys:  
Vastaanottaja: hackmeeting
Aihe: Re: [Hackmeeting] Zen Room
fine
:^)
.\" $Id: buildSDK.5,v 1.1 2005/02/01 11:41:06 Rome Exp $
.\" Copyright (c) 2005 Francesco Rana (c1cc10@???)
.\" Fri Apr  2 11:32:09 MET DST 1993
.\"
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
.\" License along with this manual; if not, write to the Free
.\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
.\" USA.
.\"
.TH BUILDSDK 5 "2 febbraio 2005" "Linux" "buildSDK project 2005"
.SH NAME
buildSDK \- multimedia linux live cd from scratch
.SH SYNOPSIS
.TP 8
.B buildSDK
.RB [-acfixd]
.SH DESCRIPTION
the shell script to create a live multimedia distro all compiled from scratch
and completely customable. It downloads a 
.BR gentoo stage1 
and recompiles first the SDK system which will run chrooted when buildSDK 
launches a subshell script called 
.BR createbasesystem 
(it's included into the buildSDK script code). 
.BR createbasesystem 
accepts most of the option passed to buildSDK and it compiles 
the whole dyne::bolic in 
.I home/the_root/ 
into the chrooted SDK system. So you 
have a first stage install which chroots and recompiles itself. Then compiles 
and install into a subdir (using emerge and the ROOT env variable) the 
selected system.
.PP
.SH OPTIONS
buildSDK actually works with no argument given (just options). Thus you have 
standard path fixed, but still can change them in the first lines of the 
script itself.
.sp
.RS
.TP 1.0in
.I -a
will start from the download of the first stage and will perform the 
whole installation steps 
.TP
.I -c
give to the user a chrooted shell into the SDK system. Usefull for adding 
parts and general debugging 
.TP
.I -f
just modify the compilation flags and exit
.TP
.I -i
start the compiling from the base dynebolic system (the initrd one)
.TP
.I -x
start the compiling from the X11 and general /usr/ system (squashedfs)
.TP
.I -d
install only the dynebolic configuration part (/etc/ files mostly)
.RE
.SH NOTES
What you need before to start:
.sp
.RS
.TP 1.0in
* Must be root
    $ su - 
.TP
* Have the squashfs support in your running kernel
    (refer to the kernel documentation: http://www.kernel.org)
.TP
* Have the squashfs user space programs
    refer to the proper site: http://squashfs.sourceforge.net
.TP
* Have 4 GigaByte of free disk space
    # df -h
.TP
* You need a broadband connection. A *DSL connection or better
.TP
* Must create a new working directory:
    # mkdir sdk
.RE
.SH GETTING STARTED
.TP
First download (or copy) buildSDK into the working directory:
    # cp <where_is_the_buildSDK_file> sdk/
.TP
change your working dir to 'sdk'
    # cd /PATH_TO_THE_PARENT_DIR/sdk
.PP
Usually to start a new installation you need to launch 
.I ./buildSDK -a 
into the working directory. The script will work until t finishes the 
dynebolic compilation, which will be installed into
.I ./dynebolic/home/the_root/
.
.PP
After the buildSDK has done its job, you can use 
.BR mkinitrdgz 
to extract into the 
.I <workingdir>/cdrom
the necessary initrd.gz and the squashedfs files. Actually you need to compile 
the kernel on your own. The config file is avalaible from the dynebolic csv 
page: 
.BR http://cvs.dyne.org .
.PP
Copy your kernel into the ./cdrom directory. Launch 
.BR dynesdk 
(follow the instruction you can read with the -h option). You should have your 
iso ready to test'n'burn!  


.SH FILE
.I buildSDK, dynesdk
.SH "SEE ALSO"
.BR dynesdk (5),
.BR mkinitrdgz(5),
.BR createbasesystem (5)