From 3c5d1872306a4a3c6b026cd09a8d8cc6fed3dddd Mon Sep 17 00:00:00 2001 From: Pascal Rigaux Date: Thu, 9 Oct 2008 07:50:55 +0000 Subject: - get rid of old obsolete doc. to build use rpmbuild (or bm) on packages drakx-installer-binaries, drakx-installer-images and drakx-installer-stage2 - update README --- docs/HACKING | 126 ----------------------------------------------------------- docs/README | 75 +++++++++-------------------------- 2 files changed, 18 insertions(+), 183 deletions(-) delete mode 100644 docs/HACKING diff --git a/docs/HACKING b/docs/HACKING deleted file mode 100644 index cf6d2e3b6..000000000 --- a/docs/HACKING +++ /dev/null @@ -1,126 +0,0 @@ --=-=-- -DrakX is a very big project, and it needs special setups to work. -The purpose of this file is to explain how you can setup your box to make it -compile and run. --=-=-- - -Beware, don't try this on a production machine with important data. - - --------------------------------------------------------------------------- -Sources installation: - -First grab the gi.tar.bz2 archive and untar it in your home directory, for -example from DrakX-*.src.rpm on your Mandrakelinux distribution. - -Fix a few things: -% find gi -name "*/CVS/root/*" | xargs perl -pi -e 's/prigaux/anoncvs/' - -Then, log yourself into the cvs: -% export CVS_RSH=ssh -% export CVSROOT=:ext:anoncvs@cvs.mandrakesoft.com:/cooker -% cvs checkout gi -        (the passwd is: 'cvs') - -And update the gi package: -% cvs update -P -d gi - - --------------------------------------------------------------------------- -Preparing the compilation process: - -(1) target directory - -Create a top level directory called /export and give write permissions to -the user/group that will be compiling DrakX.  It is also suggested that you -copy a recent Mandrakelinux CD in there. (You don't have to put have all -the RPMS...) ; you'll need roughly 1.5 Gbytes for a full install. (It is -possible to not have a copy of Mandrakelinux there, if all you desire is to -compile gi) - - -(2) support directories - -You will need to create a top level /RPMS directory.  This directory needs -to be populated with the following RPMS: -locales-ja locales-ko locales-zh - -GI needs to be informed about which kernel(s) is/are to be used. -Most of the time, no manual install is needed. Just be sure to -have the kernel(s) in /RPMS, and typing make later on will -extract the package(s) and build stuff from it. - -FYI, for each kernel, directories will be populated as follows: - -gi/kernel/all.kernels/2.6.0 - special files containing - - vmlinuz - - modules.dep, modules.alias, modules for stage1 (*.tar) - - -(3) required rpm packages - -You need quite a number of rpm packages installed on your system -to build gi properly. You should install this package to pull the -requirements: - task-drakx-devel - -You may need a few others I forgot to mention. If the compilation fails, try -to understand the message and install any necessary remaining package. - - -(4) - -NEVER build or run Drakx as root.  Install sudo and setup the following -permissions in /etc/sudoers: - -user ALL=(root) -NOPASSWD:/usr/bin/patch,NOPASSWD:/bin/rpm,NOPASSWD:/bin/mount,NOPASSWD:/bin/cp,NOPASSWD:/bin/umount,NOPASSWD:/usr/bin/install,NOPASSWD:/bin/rm,NOPASSWD:/bin/mv,NOPASSWD:/bin/tar,NOPASSWD:/bin/cpio,NOPASSWD:/bin/chown,NOPASSWD:/bin/mkdir,NOPASSWD:/usr/bin/strip,NOPASSWD:/bin/mknod - - -(5) - -pray - -[gc@obiwan ~/cvs/gi] make - - ---------------------------------------------------------------------------- -The comments written with #- are automatically stripped out at install. - - ---------------------------------------------------------------------------- -testing all: - -  go to the perl-install directory and execute ./install2 --testing - -  NEVER execute DrakX as root! You might need to allow all users -  to read the block devices of your hard-disks, though (chmod a+w -  /dev/hda* for example). - - - -Here is how I (dams) made it work on my computer. -------------------------------------------------- - -- get the sources -- install the librairies needed included newt-devel gtk+-devel popt-devel popt gtk-engines -- cd path/to/gi -- make -- mkdir /usr/share/gtk -- ln -s path/to/gi/perl-install/share/themes /usr/share/gtk -- ln -s path/to/gi/perl-install/share/step-* /usr/share -- ln -s path/to/gi/perl-install/share/help.xpm /usr/share -- ln -s path/to/gi/perl-install/share/isdn* /etc/sysconfdir/network-scripts -- have a cd architecture linked on /export -- ln -s /export /tmp/rhimage -- export PERL_INSTALL_TEST=1 -- cd path/to/gi/perl-install -- gendistrib --noclean --distrib /export -- ./install2 in root (dangerous) or chmod a+r /dev/hd* and ./install2 in user - - - -address all bugreports to dave@null.com - -info has been added by sunny@opencurve.org diff --git a/docs/README b/docs/README index 67179a981..54320919f 100644 --- a/docs/README +++ b/docs/README @@ -1,8 +1,7 @@ -Well here is a little description of what DrakX needs to work in comparison -to the RH newt install. +Well here is a little description of what DrakX needs to work ******************************************************************************** -* CVS ************************************************************************** +* VCS ************************************************************************** ******************************************************************************** Like all good free software, DrakX is in SVN :) @@ -15,32 +14,18 @@ svn co http://svn.mandriva.com/svn/soft/drakx/trunk drakx This is only read-only access. If you want more, tell me (pixel@mandriva.com) -Please note that redoing *all* the stuff is not for the faint of heart. I myself -sometimes wonder what the whole make does :-% -Instead, changing some .pm files is quite easy (nice interpreted language) - ******************************************************************************** * Making your custom install *************************************************** ******************************************************************************** If you have your own rpms you want to add, or make your own updated cdrom, you just have to issue: -% gendistrib --noclean --distrib - -Where is the root of all the media that the install will see, this first -one is the main one : +% gendistrib --noclean --distrib -(1) network or 1-cdrom installs - DIRS == the root directory of the Distribution +Where is the root of all the distribution. -(2) multi-cdrom install - DIRS == the root directories of all the media that the install will see - -``gendistrib'' will scan the file media/media_info/hdlists in the main root -directory (the first one in DIRS) to search for all media used. Typically you -use media/main for RPM packages repository. -For multi-cd, please use media/main or media/foo, etc. -For one CD or a network/hd volume, please use media/main. +``gendistrib'' will scan the file media/media_info/media.cfg to search for all +media used. Typically you use media/main for RPM packages repository. Optionnally, you can modify ``media/media_info/rpmsrate''; this file manages the relative importance of the files, and thus their installation or not. @@ -60,12 +45,12 @@ media/media_info/media.cfg cf MDV::Distribconf(3) media/media_info/hdlist*.cz - table of rpm's headers, referred by ``hdlists'' + table of rpm's headers, referred by ``media.cfg'' their contents can be listed using ``packdrake -l '' or or ``parsehdlist ''. ! Need to be remade when media/main changes (with ``gendistrib'') ! -media/media_info/compssUsers +media/media_info/compssUsers.pl media/media_info/rpmsrate ranks and classify packages, so that the installer will know which @@ -74,19 +59,15 @@ media/media_info/rpmsrate where is a symbolic name used in media/media_info/compssUsers* files, and defines importance level as described below : - 5 must have + 5 mandatory 4 important - 3 very nice + 3 interesting 2 nice 1 maybe - installer selects packages for level 4 (important) and 5 (must have). + installer selects packages for level 4 (important) and 5 (mandatory). packages in other level (3, 2, 1) can only be selected using individual package selection. -install/stage2/live - live system used on certain installs. See ``Ramdisk or not'' below for - more. - install/stage2/mdkinst.clp for the compressed loopback of install. generated from install/stage2/live tree using misc/mdkinst_stage2_tool @@ -96,27 +77,22 @@ install/stage2/rescue.clp this is the ramdisk loaded when typing rescue on boot prompt. install/images/all.img - USB image enabling any install + fat16 image to dd on a partition (hint: sda1) install/images/boot.iso iso image to burn enabling any install (cdrom/hd/nfs/ftp) - Boot from cdrom: - - boot.iso : iso image to burn - - Boot from hd (esp. usb key): - - all.img : fat16 image to dd on a partition (hint: sda1) + To boot from cdrom, use boot.iso + To boot from network, use isolinux/alt0/all.rdz + vmlinuz via pxe + To boot from hd (esp. usb key), use all.img. + + NB for usb boot: - it seems some bioses don't use the code on MBR (sda), or at least skip it when it's blanked (eg: "dd if=/dev/zero of=/dev/sda bs=1 count=446") - some bioses need it. I had some luck using dd if=/usr/lib/extipl/aldebaran.bin of=/dev/sda (install package extipl first) - - Boot from network: - - all.rdz + vmlinuz via pxe - - dd for windows: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm ******************************************************************************** * logs ************************************************************************* @@ -150,27 +126,12 @@ install. For example, French can be the default language with a qwerty keyboard, the auto-partitionning partitions can be changed, the default user class can be set to developer (!)... -******************************************************************************** -* po translation files ********************************************************* -******************************************************************************** -DrakX uses .po files for its translation. A script takes the different -strings out of the .pm files. It generates the DrakX.pot file which contains -all the english strings to translate. - -******************************************************************************** -* PCMCIA install *************************************************************** -******************************************************************************** -If the media you use to install is a pcmcia device, use the pcmcia boot disk. - ******************************************************************************** * modules ********************************************************************** ******************************************************************************** -Modules can be found in /modules. - To manually install a module during install, switch to console #2 and type "modprobe ". The modprobe program is a perl -wrapper around /usr/bin/insmod. It uses the dependencies found in -/modules/modules.dep (stage1). +wrapper around /usr/bin/insmod. ******************************************************************************** * Making screenshots *********************************************************** -- cgit v1.2.1