Hu folks

I just ordered a athlon64 3000 etc. Just wondered if any 64 bit slack
available in uk. No luck on google / linuxemporium / maxtux etc.
Recently I tried gentoo. Good distro but I felt pretty dumb when it
started to pull and compile stuff without asking me. Also the init
system of slack is what I am most comfortable with. In gentoo it seemed
more complex than it should be. It was faster but was also slightly
unstable unfortunately.

Story is I am back to my slack10, and prefer to stick with it for amd64
as well. At the moment I am doing some compute intensive stuff and could
do with the boost 64bits give.

Hence , any one has any idea if there is a slack for 64 bit! If not I
suppose I could use slack sources and follow the LFS route to make a
slack similar system with slack sources. But if someone has already
tried it I would greatly appreciate the pointers.

Thanks
sreekant

sreekant wrote:

> Hu folks
>
> I just ordered a athlon64 3000 etc. Just wondered if any 64 bit slack
> available in uk. No luck on google / linuxemporium / maxtux etc.
> Recently I tried gentoo. Good distro but I felt pretty dumb when it
> started to pull and compile stuff without asking me. Also the init
> system of slack is what I am most comfortable with. In gentoo it seemed
> more complex than it should be. It was faster but was also slightly
> unstable unfortunately.
>
> Story is I am back to my slack10, and prefer to stick with it for amd64
> as well. At the moment I am doing some compute intensive stuff and could
> do with the boost 64bits give.
>
> Hence , any one has any idea if there is a slack for 64 bit! If not I
> suppose I could use slack sources and follow the LFS route to make a
> slack similar system with slack sources. But if someone has already
> tried it I would greatly appreciate the pointers.
>
I can't imagine somebody not already doing that, 'cos it sounds like a
way fun project. First, you compile the compiler....

Hello!
Zuzej Maaya

> I can't imagine somebody not already doing that, 'cos it sounds like a
> way fun project. First, you compile the compiler....
>
> Hello!
> Zuzej Maaya
>

My thoughts exactly. Looking at the slack sources online there are
slackbuild scripts in each folder. May be I can build the whole thing
just by runnng slackbuild scripts from a running slack install and
create packages for amd64. Ofcourse the nice stuff like installation
system will obviously be missing but I don't mind doing that manually.

But if someone has any ideas, which are likely to be better than mine
please tell me.

Ta
sreekant

On Sat, 25 Sep 2004 21:05:53 +0000, sreekant wrote:
> Hence , any one has any idea if there is a slack for 64 bit!

This has been discussed very recently. E.g.:

http://groups.google.com/groups?hl=e...%2540 4ax.com

With kind regards,
Daniel de Kok

sreekant wrote :

> I just ordered a athlon64 3000 etc.

There has been several threads about the Athlon64 vs Slackware issue:
<URL: http://groups.google.com/groups?q=Athlon64&meta=group%3Dalt.os.linux.slackw are>
--
Thomas O.

This area is designed to become quite warm during normal operation.

On Sun, 26 Sep 2004 09:13:23 +0000 (UTC), skodela@lithium.com wrote:

>
>> I can't imagine somebody not already doing that, 'cos it sounds like a
>> way fun project. First, you compile the compiler....
[..]
> My thoughts exactly. Looking at the slack sources online there are
> slackbuild scripts in each folder. May be I can build the whole thing
> just by runnng slackbuild scripts from a running slack install and
> create packages for amd64.

It's a bit more involved than that :-)

You need to build yourself a working toolchain or two, or three
(different versions of gcc because different versions produce different
results; sometimes a version of gcc will build a working kernel
whilst some produce one that breaks in strange ways, and not all
source will build with gcc 3.4 (which you'd probably want to use))
and if it's a large program you're compiling then it's usually easier
to switch to a gcc 3.3 release than it is to patch the source).

Then you try to compile the software and find it breaks.
You then proceed to either patch it yourself or look around for
the relevant patches.
Debian is usually a good source of patches but unless it's something
like X, glibc or gcc then the patch is one big file which patches
everything -- you then need to work out which bit of the patch is actually
required and separate that from the rest of the Debian stuff.

It's a fun project but in the beginning it will take a considerable
amount of time to get used to building stuff, anticipating problems
and fixing some of the more common build problems.
You also need to know how Slackware's packaging system works
and why certain things are as they are. These are the undocumented
things. This is made easier by various Slackware ports having comments
in their build scripts and stuff like that.
If you don't know what I mean now, then you will do if you start on the
project :-)

--
Stuart Winter
www.interlude.org.uk & www.armedslack.org

> It's a bit more involved than that :-)

> If you don't know what I mean now, then you will do if you start on the
> project :-)
>

Ummmmm. I think I will wait till pat does it. :-)

Ta for the enlightenment.

I alsmost scared my self :-). Let pat do it for us /relief/

Cheers
sreekant