Ok, if it's just going to be a server, i guess it's a lot easier. I find Xorg the most difficult to install. It needs a ton of libraries and I never seem to understand the font setup. Perhaps next holiday when I got some spare time

But I can actually recommend you to do the same thing with a desktop system. I find it quite fun, interesting and you learn a lot by doing it.

It is X that use most of the space, so for a server you should be able to get a working system in less then 100MB. Depending on what you need of course. If it's a full LAMP, ldap, dhcpd, dns, and more you will probably need more, but definitely less then 1.3GB.

Good luck, and just ask if you get stuck

Im having trouble installing gcc, to get other packages to compile.

I go to /mnt/cdrom/source/d/gcc and do ./gcc.Slackbuild but then it says:

Searching for symbolic links.

No symbolic links were found, so we won't make a installation script. You can make your own later in ./install/doinst.sh and rebuild the package. but it makes a txz in /gcc-<nr>/gcc-obc<nr>.txz and I can install that, but gcc isnt installed anyway.. hmmm... What am I missing?

Install the binary gcc package from the /d series.
You can't compile gcc without having gcc :-)
You'll need other packages as well in order to compile anything.

I did install it. using the slackbuild. but the message there comes up. If I go to /var/log/packages it says that gcc is installed. but I cant find the command and still get the same error.

or maybe I misunderstood what you were saying now

Maybe this one will help you out

http://www.linuxquestions.org/questi...ckware-445118/

I guess the title say it all and its not big at all. Might take 5 minutes to read an another 5 to get the point.

Cheers Zhjim

Hi,

I'll leap in here for a moment to add that you could look at 'Slackware® rc init tour' to aid your understanding. This document is dated but will help you too understand the 'init'.

The above link and others are available from 'Slackware-Links'. More than just Slackware® links!

After talking to a friend that knows a lot about slackware I got the gcc binary installed. I have install glibc2,glib2,make,autoconf,automake,gcc,gcc-g++. but I get c compiler cannot create executables. see the config.log for more information. but where is the config.log? when I try to install it from the dvd? hmm.

And binutils

The config.log will be available in the same directory where the configure script is - usually this is the toplevel directory of the sources you are trying to compile.

That "c compiler cannot create executables" can either mean you did not install enough of D/ and L/ series to have a working developer too chain, or that your ARCH variable is set to the wrong machine architecture (say, you run Slackware for x86_64 but you are trying to compile a 32bit binary).

Eric

Alien_Bob: But when I try to install it from dvd. It cant write the config.log to the cd? That is the problem I think?

I found the problem anyway. I was missing the mpfr packages. And a lot others afterwards But that I can figure out.

So Alien
when I install things from the dvd. where do I find the config.log then?

You need to learn the difference between installing a binary Slackware package (using installpkg) and compiling binaries from source code (which you do using gcc compiler and friends).

You do not have to compile a Slackware package - it is already there for you in the /slackware directory of theat DVD.
If you compile source code, you first extract the source code directory from the archive it is distributed as (as .tar.gz , tar.bz2 etc... ), and then typically run "./configure" in the toplevel directory of the extracted source code. The configure program configures the sources for your hardware and software environment, so that the next step (running "make") will build binaries for you.
The configure command logs it's activity in a file "config.log" in that same directory. That log file is huge, but you should search for the error string that you see on your console, the same text should be present in the logfile and the context will make it clear why configuration failed.

Eric

Hehe. I know the difference, I just thought that the config.log was in the slackbuild error too. But I found the problem, and I am trying to install other packages. I learn a lot from this.
The openssh.Slackbuild just failed without any other messages then the c compiler could not create executables.
A friend of my gave me a line that checked c compiler. Then it gave me the message about the libmpfr.so.1 was missing. I just installed the mpfr package and it worked.

Had a hard time finding out what was missing, since the compiler didnt give me any clues about it. That's why I asked about the config.log so that maybe could me give me some more clues

But I will use time and get to know Slackware.
I just ordered the Slackware Essentials, 2nd Edition
So I will read a lot too.

Roar

Hello all,

I would like something like this: http://www.slackware.com/~alien/slackboot/mini/

My goal is to make it as small as possible, but leave hardware detection and networking intact.
I intend to use it as a template for future custom slackware 13 installs, which will be expanded via slackpkg (I won't compile stuff so no need for GCC).

So, what I'm looking for is a very basic (but easily expandable) slackware system.

Right now I used Samac's method: http://www.linuxquestions.org/questi...ckware-704866/
but it's still 480Mb after installed.
Is it possible to make it smaller?

When I get home I'll post the packages I'm using (they are sightly different from Samac's)

Did you follow it all the way? I used the guide as well, and with a working x environment (fluxbox, firefox, pidgin, etc) i think it was just above 200MB if I remember correctly. KDE will probably need a lot more tho.

Hi,

You did look at the script ; create_miniiso.sh which would allow some tweaking. But you could use the version of choice for the miniso then either have a tag file or select the packages from the setup for the version.