SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Life beats me again offering tasks which I never done before(and honestly anticipated any possibility to do them) and have not anybody experienced to teach me.
So task is to setup environment to crossbuild software to specified platform(including building kernel, coreutils and whole minimal bunch of software required to boot-up system).
So seeking for any modern information of what, how, in which order to build in order to produce well working result.
Have Googled for ready made tools, scripts, strict descriptions, but nothing suitable found. Most of verbal descriptions are highly outdated(>5 year old). Some of them are stick to limited number of platforms. Most of them explains nothing. Some of them are just inconsistent(writing one, running other). LFS is not suitable either.
I have used http://fedorapeople.org/cgit/djdelor...bootstrap.git/ as inspiration to create my own bootstrapping framework which creates a cross-compiler and a mini rootfs for my ARM port (which has been abandoned since april and which I re-started a few weeks ago). I was never in favour of using someone else's binaries to bootstrap a new port or even cross-compile Slackware packages, I needed to learn how to create this myself.
The intention is to publish all that work when I have the full Slackware 14 package set compiled for an ARM target with hardware FPU support (i.e. modern CPU's as found in tablets and the chromebook), my port won't run on a Raspberry Pi for instance.
Thanks everybody for answers.
@Alien Bob, I'll try it as soon as find HDD space to instantiate fedora. But I have not any real expectations of it, because it is one of hundreds ARM architecture locked solutions.
For now I going to postpone this task, since platform vendor provides pre-built cross-compiling kit(RH5 compatible, works on 13.37). But it is 64-bit only, so task still here.
For now my task is to determine right sequence of Slackware's packages to crossbuild them.