On Sat, 2010-02-13 at 18:41 +0200, Makis Tsimaras wrote: > > > 2010/2/13 Bob Gustafson <[email protected]> > > On Sat, 2010-02-13 at 17:24 +0200, Makis Tsimaras wrote: > > > > > > 2010/2/13 Bob Gustafson <[email protected]> > > > > > > On Sat, 2010-02-13 at 16:21 +0200, Makis Tsimaras > wrote: > > > Hello > > > > > > Am a sysadmin but am not a programmer. > > > I just tried to do an embedded build with no > changes at all > > into > > > the ./scripts/Config script except to print the > output to > > the screen. > > > > > > An error occurred during the building of the > "gatling" > > package and > > > the building was aborted. > > > I disabled it from the "target/embedde/config.in" > file and > > the build > > > continued......an error occurred again in the > "strongswan" > > package > > > build,... i disabled it again and the building > > continued,....an error > > > then occurred in the "mininet" package > building,... i > > disabled it but > > > the building then stopped after the "Searching for > old > > lingering > > > files ..." section. > > > Something was missing.... > > > > > > > > > As a sysadmin and not a programmer is there > anything i can > > do to > > > survive by continue using the T2 project to build > custom > > linux > > > distributions? > > > > > > > > > Thanks in advance > > > > > > Did you do a ./scripts/Config after disabling each > time? > > > > You could also forcibly delete ... > > > > rm -rf package/<dir>/<offending package> > > > > And then do a ./scripts/Config > before ./scripts/Build-Target > > > > --- > > > > Have fun > > > > > > > > > ----------------------------------------------------------- > > If you wish to unsubscribe from this mailing, send > mail to > > [email protected] with a subject of: unsubscribe > t2 > > > > > > > > > > Thank you for the tip. > > > > What if i need the package? > > > > Am having fun.. > > > > > > > When you get to the 'end' - meaning that you are booting a new > ISO built > with as many packages as you can, if something doesn't work > that you > need, you can go to the mailing-list with your symptoms of > that package > failure. > > In my case, building minimal-xorg - wdm didn't build (among > other > packages) and is needed to move to level 5 - but everything > 'else' seems > to work. I can concentrate on getting wdm to cross compile. > > Bob G > > > > Cross-compile from the building host into the directories in > "build/*"..., or boot from the ISO download and compile from there? >
Everything is controlled from the ./scripts/Config settings. You don't worry about the build/* directories, they just get built automatically by the build system. After the ./scripts/Build-Target has completed successfully, you then do a ./scripts/Create-ISO <myname> After this completes successfully, you just fish around for a completed .iso file with the right name (<myname>.iso) and a reasonable date. Move this file out to somewhere you can burn a CD (or somewhere you can access the file when you build a new virtual machine) Use this CD to install into a new machine - at the end of the initial boot, you may have to hit return to get a prompt. As I recall, you then go into 'stone' to create new partitions (I usually do /, swap, /boot with whatever file systems you have in your new image. For some reason, I only had xfs, and reiserfs - I used xfs and boot/grub worked fine). After partitions, I think you have an opportunity to add a network connection - add level 2 to the active levels and start the network. Then add sshd and add levels 2,3,4,5 and start this daemon. Then install the rest (still working within the initial ncurses interface). Write grub and the master boot record. You can do this several times - it doesn't hurt. Not doing it at all or unsuccessfully is not so good. You should be to the point where you can reboot into your new image - to see what is missing.. I may have left something out. These instructions are all in the handbook though. Good Luck. Bob G > and some more.... > > Which is the best way to modify the target system,... from ISO OS when > boot with it,... or during the build? > I don't know what you mean by 'modify'. If it is new package related, you can do it in either spot as long as you have subversion in your new iso build. > Thanks for your support. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
