Is there any docs anywhere on building a complete slackware system from
scratch? Sure I could use gentoo or follow the LFS docs, but I like
slackware, I just want to completely optimise my system for my hardware. I
googled a bit and found a couple links, but nothing particularly useful.

Martin

Martin J. Green a écrit :
> Is there any docs anywhere on building a complete slackware system from
> scratch? Sure I could use gentoo or follow the LFS docs, but I like
> slackware, I just want to completely optimise my system for my hardware. I
> googled a bit and found a couple links, but nothing particularly useful.
>
> Martin
>
>

Hello there is this doc in french

http://www.lea-linux.org/install/LFSlack.html

"Julien" <julien.poulalion-linux@laposte.net> wrote in message
news:42fdab82$0$27265$8fcfb975@news.wanadoo.fr...

> Hello there is this doc in french
>
> http://www.lea-linux.org/install/LFSlack.html

any chance of a translation? :P

"Julien" <julien.poulalion-linux@laposte.net> wrote in message
news:42fdab82$0$27265$8fcfb975@news.wanadoo.fr...

> Hello there is this doc in french
>
> http://www.lea-linux.org/install/LFSlack.html

Just took a look at that link. Whilst I understand very little of the
french - I can just about make sense of it in places from good old high
school french - but the commands I do understand, and from what I can see
that document describes installing a slackware system from scratch using the
standard slackware packages, which of course wasn't what I was asking about.
I was asking about building it yourself from source.

Martin J. Green wrote:
> Is there any docs anywhere on building a complete slackware system from
> scratch? Sure I could use gentoo or follow the LFS docs, but I like
> slackware, I just want to completely optimise my system for my hardware. I
> googled a bit and found a couple links, but nothing particularly useful.

you're not the first one to ask this in this NG. go to google's advanced
group search, and search specifically in aols, that should turn up a few
threads.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

On 2005-08-13, Martin J. Green
<martin.green@NOSPAM.firstinternetservices.com> wrote:
> Is there any docs anywhere on building a complete slackware system from
> scratch? Sure I could use gentoo or follow the LFS docs, but I like
> slackware, I just want to completely optimise my system for my hardware. I
> googled a bit and found a couple links, but nothing particularly useful.

You get the sources and build scripts with the CD-ROMs. You can do your
own optimizations and build your own packages.

--
The night is just the shadow of the Earth.

On Sat, 13 Aug 2005 07:44:35 -0300, Martin J. Green
<martin.green@NOSPAM.firstinternetservices.com> wrote:

> Just took a look at that link. Whilst I understand very little of the
> french - I can just about make sense of it in places from good old high
> school french - but the commands I do understand, and from what I can see
> that document describes installing a slackware system from scratch using
> the
> standard slackware packages, which of course wasn't what I was asking
> about.
> I was asking about building it yourself from source.

slide some options into the slackbuild scripts.

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

"jim dorey" <skaar@ns.sympatico.ca> wrote in message
newsp.svglbplyfr5e9h@trebuchet...

> slide some options into the slackbuild scripts.

"William Hamblen" <wrhamblen@comcast.net> wrote in message
news:deKdnXONz-ifuWPfRVn-1g@comcast.com...

> You get the sources and build scripts with the CD-ROMs. You can do your
> own optimizations and build your own packages.

I have source already - I build the biggies like apache, mysql, openssl,
openssh and various other from source with my own config options in places,
however the problem with the above responses is that such a solution is only
good for building one or two packages. Building an entire system requires a
specific build order. It also requires a certain amount of work to ensure
that the vanilla slack toolchain etc doesn't end up in the newly built
packages (probably resulting on a broken toolchain). Most likely I'd also
change from i486-slackware-linux to i686-slackware-linux,
athlon-slackware-linux (not sure this one is valid, some links on google
seem to suggest it is, but others such as the gentoo docs suggest it should
be i686) or x86_64-slackware linux (no, I know this one probably isn't quite
correct but u get the idea), which makes the build order and method
especially important.

"Joost Kremers" <joostkremers@yahoo.com> wrote in message
news:slrndfrlqt.rdg.joostkremers@j.kremers4.news.a rnhem.chello.nl...

> you're not the first one to ask this in this NG. go to google's advanced
> group search, and search specifically in aols, that should turn up a few
> threads.

Thanks Joost. I'll take a look

"Martin J. Green" <martin.green@NOSPAM.firstinternetservices.com> writes:

> "jim dorey" <skaar@ns.sympatico.ca> wrote in message
> newsp.svglbplyfr5e9h@trebuchet...
>
>> slide some options into the slackbuild scripts.
>
> "William Hamblen" <wrhamblen@comcast.net> wrote in message
> news:deKdnXONz-ifuWPfRVn-1g@comcast.com...
>
>> You get the sources and build scripts with the CD-ROMs. You can do your
>> own optimizations and build your own packages.
>
> I have source already - I build the biggies like apache, mysql, openssl,
> openssh and various other from source with my own config options in places,
> however the problem with the above responses is that such a solution is only
> good for building one or two packages. Building an entire system requires a
> specific build order. It also requires a certain amount of work to ensure
> that the vanilla slack toolchain etc doesn't end up in the newly built
> packages (probably resulting on a broken toolchain). Most likely I'd also
> change from i486-slackware-linux to i686-slackware-linux,
> athlon-slackware-linux (not sure this one is valid, some links on google
> seem to suggest it is, but others such as the gentoo docs suggest it should
> be i686) or x86_64-slackware linux (no, I know this one probably isn't quite
> correct but u get the idea), which makes the build order and method
> especially important.


Actually, if I have this correct, it doesn't really matter about build
order in this case. Assuming you are using an existing slack
distribution to rebuild itself you are just replacing the packages
with themselves and therefore, getting from a vanilla slack, to an
optimised vanilla slack will cause very few problems. It is a problem
in LFS because you are essentially using one system to install another
(different) system, and so you don't want anything from the older
system to be left on the new system. When rebuilding an existing system
you don't have those problems.

Besides, if you read the documentation you shouldn't optimise much, if
any, of the tool chain anyhow. Your best bet will be to leave at least
the tool chain in tact and use the source and build scripts to rebuild
everything else. From what I remember from my dabbling, not even
Gentoo optimises the tool chain and LFS certainly doesn't.

Only if you are thinking of upgrading or replacing various parts of
the system do you need to worry about build order. It shouldn't be
hard to work this out anyway. Check out a recent copy of LFS (and BLFS
for later) on and use it as a template -- that book tells you the build
order. Then all you need to do is use the Slackware source, and the
existing build scripts -- with editions made -- to build slack from source
in a blank environment. It's quite possible that you'll need to build
the base system first through (or just perform a /very/ minimal
install of Slack and go from there) in order to run pkgtools so that
you can register the created packages.

Still I think your best bet would be to start with Slack and use it to
rebuild itself. Leaving the basic tool chain completely in tact as to
avoid any problems.

Hope this is of some help,
Jon

In article <42fd59f2$1@news1.homechoice.co.uk>, Martin J. Green wrote:

> Is there any docs anywhere on building a complete slackware system from
> scratch? Sure I could use gentoo or follow the LFS docs, but I like
> slackware, I just want to completely optimise my system for my hardware.

Follow LFS as a guide to what order to get started in, but use the
Slackware source packages and SlackBuild scripts to actually build the
packages. That's what I've done to get a project going to properly port
Slackware to one of my non-Intel systems, and though I'm not finished
that project, I have a good head-start on it.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------