LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware from Scratch? (http://www.linuxquestions.org/questions/slackware-14/slackware-from-scratch-286503/)

dhave 02-05-2005 07:11 AM

Slackware from Scratch?
 
As I've been recovering from the flu, I've distracted myself by trying to build a Linux from Scratch system on a spare machine. It's a lot of fun and tremendously educational. However, I'm still partial to the Slackware way of organizing and configuring a system. Which raises this question:

Has anybody put together instructions to build from scratch a basic Slackware system? I'd like to try to build a Slack system myself so I can really see inside the insides.

The way the LFS book is set up is superb. If anyone has done this, or is willing to do this, for Slackware, I think there'd be a more than a few of us who'd like to work through it.

Or maybe this already exists and I've somehow missed it.

keefaz 02-05-2005 07:45 AM

To build slackware from scratch, I just would install a minimalistic slackware on a partition
with paying attention to install all software developement tools from d/ then I would use
the slackbuild scripts available in slackware sources, creating the packages and install them
with installpkg -root /mnt/target_partition, of course this will require a lot of try to getting it to
work but not so hard with the scripts automation.

xushi 02-05-2005 07:54 AM

I've finished LFS 2 weeks ago on a Slack current host, and working on BLFS at the moment.

Keefaz' idea sounds alright, but it still doesnt have the essance of 'from scratch'. I'd rather compile the C compiler from scratch enabling i686, etc.. And then use that to start building the Slack system.

I'm guessing here, that since slackware is teh closest to unix in standards, therefore directory and file heirachy (however you spell that), and since LFS also tries its best to follow such standards (except for /usr/local/games), then it shouldn't be difficault.

All you need to worry about should be the slight differences in file and directory heirichy Slack might have, as well as where it chooses to install certain apps different than any other distro. Like KDE being in /opt/kde instead of the KDE recommended /usr (and so on)

What i'm interested in seing, is a BFS (BSD From Scratch) =)

EDIT!
==============
This is what i mean by the hierarchy
Quote:

The directory tree is based on the Filesystem Hierarchy Standard (FHS) standard (available at http://www.pathname.com/fhs/). Besides the tree created above, this standard stipulates the existence of /usr/local/games and /usr/share/games. We do not recommend these for a base system, however, feel free to make the system FHS-compliant. The FHS is not precise as to the structure of the /usr/local/share subdirectory, so we created only the directories that are needed.
If you really are going to do this, it wouldnt hurt to ask Pat himself a few questions regarding the matter. I'm sure he's more than willing to help.

keefaz 02-05-2005 08:02 AM

You could edit the glibc and gcc slackbuild scripts to enable i686 but I find xushi's ideas
interesting (especially BSD From Scratch)

ringwraith 02-05-2005 08:05 AM

There is Debian from Scratch program now, so who knows. Kind of like the live cds, now everyone has one.

xushi 02-05-2005 08:17 AM

Quote:

Originally posted by keefaz
You could edit the glibc and gcc slackbuild scripts to enable i686 but I find xushi's ideas
interesting (especially BSD From Scratch)

Out of curiosity keefaz, i am quite interested in transforming the current slack i have into i686. Do i just have to recompile GCC and Glibc? or are there any more issues i should keep a note of?

clawhead, i forgot to mention. Its not a bad idea to go through LFS and BLFS once or twice to get the hang of it, as well as a very good understanding of how everything works, before customizing it the way you want (slack from scratch thing)

keefaz 02-05-2005 08:22 AM

Xushi, look at the glibc slackbuild script:
http://ftp.scarlet.be/pub/slackware/...ibc.SlackBuild

Although Pat suggest that $ARCH should be i486, I would think you can change it to i686
but then you're responsible for compatibility problems (eg, set all packages ARCH to
i686 to make sure they will be compatible)

xushi 02-07-2005 04:19 PM

On a side note, to anyone who'se interested.

I've managed to successfully setup slackware's 'pkgtool', as well as 'checkinstall' successfully on a fresh LFS / BLFS system. (good bye paco ...)

So rest asure that if one makes his/her own LFS system, they will have the ability to manage, install, update, remove packages with ease.

I'm still thinking about this thread, and it got my attention. I'll be looking into how similar both slackware and lfs base systems are.. I'm assuming they will be very similar if not identical if slack truely does follow the FHS standard discussed above.

If they do, then i'll continue with that, making sure to install programs in the same paths as slackware does (eg, kde being in /opt instead of /usr/local) so that i can use precompiled slackware packages (linuxpackages.net anyone?) on my LFS OS.

If anyone's interested, i'll keep a note on everything i'll do.

__J 02-07-2005 04:42 PM

I use pkgtools anytime I build a LFS system. It makes it pretty easy, and in the end you get more or less Slackware from scratch. for anyone who wants to try this method, just make sure you get everything checkinstall depends on in the temporary system and it all goes pretty smoothly.

dhave 02-07-2005 04:43 PM

Quote:

Originally posted by xushi
On a side note, to anyone who'se interested.

I've managed to successfully setup slackware's 'pkgtool', as well as 'checkinstall' successfully on a fresh LFS / BLFS system. (good bye paco ...)

So rest asure that if one makes his/her own LFS system, they will have the ability to manage, install, update, remove packages with ease.

I'm still thinking about this thread, and it got my attention. I'll be looking into how similar both slackware and lfs base systems are.. I'm assuming they will be very similar if not identical if slack truely does follow the FHS standard discussed above.

If they do, then i'll continue with that, making sure to install programs in the same paths as slackware does (eg, kde being in /opt instead of /usr/local) so that i can use precompiled slackware packages (linuxpackages.net anyone?) on my LFS OS.

If anyone's interested, i'll keep a note on everything i'll do.

Yes, I'd like to see your notes if you release them. I just went through LFS and I tried to be aware of times when LFS and Slackware diverged. However, I realized that, although I've tinkered a lot with Slackware in the short time I've been using it, my familiarity didn't descend very deeply into system design, organization and rationale. So any observations you might have would be welcome. I'd especially like to see a chart or table showing the divergences at various structural levels.

When I get some more time, I'm going to move from LFS, which is purring nicely now, on to BLFS. Then I'd like to try to reconstruct Slackware, or at least work on a deeper understanding of it. Maybe by then your notes will be available.

Thanks for sharing this interest. I'm glad people have worked on this kind of thing.

__J 02-07-2005 05:04 PM

check out the LFS hints for some good tips. especially the one about BSD style init scripts which is what slackware uses ( although now there is some sysvinit stuff for some applications that do require it).


All times are GMT -5. The time now is 04:01 AM.