I was looking through http://www.kernel.org when I found a "Historic" directory in http://www.kernel.org/pub/linux/kernel/, after going into that I find...linux-0.0.1.tar.bz2.

So obviously I download it and compile it (well try to anyway...) I tried the usual "make menuconfig", "make config" etc. But none worked, so I used "make" on it's own which produced an error.

So I check the checked the Makefile, which seemed normal.

Any ideas on whats going on? I think it might be because Slackware with Kernel 2.6.14.3 is too new

Thanks,

Kourosh

(P.S. Sorry if this is in the wrong section of the forums, I was going to post in Linux General but I forgot because I usually go to Slackware forum)

Back then, kernel configuration was accomplished using the Makefile, I believe. None of those fancy configs.

I honestly wouldn't expect it to compile with any gcc other than 2.95 or lower. I also would not expect it to run on your hardware: it likely won't understand a BIOS as new as yours, support most of your hardware, etc. (Though, it might boot with something like qemu).

Take not that 0.0.1 was pretty much a 'demonstration'/'proof-of-concept'. I'm not sure it really did much of anything.

Good point but it still would have been interesting.

0.0.1 probably printed "Linus Rulez!" and exited.

Heh heh...

In the words of linus at the time:

This is a free minix-like kernel for i386(+) based AT-machines. Full
source is included, and this source has been used to produce a running
kernel on two different machines. Currently there are no kernel
binaries for public viewing, as they have to be recompiled for different
machines. You need to compile it with gcc (I use 1.40, don't know if
1.37.1 will handle all __asm__-directives), after having changed the
relevant configuration file(s).

As the version number (0.01) suggests this is not a mature product.
Currently only a subset of AT-hardware is supported (hard-disk, screen,
keyboard and serial lines), and some of the system calls are not yet
fully implemented (notably mount/umount aren't even implemented). See
comments or readme's in the code.

This version is also meant mostly for reading - ie if you are interested
in how the system looks like currently. It will compile and produce a
working kernel, and though I will help in any way I can to get it
working on your machine (mail me), it isn't really supported. Changes
are frequent, and the first "production" version will probably differ
wildly from this pre-alpha-release.

Hardware needed for running linux:
- 386 AT
- VGA/EGA screen
- AT-type harddisk controller (IDE is fine)
- Finnish keyboard (oh, you can use a US keyboard, but not
without some practise :-)

The Finnish keyboard is hard-wired, and as I don't have a US one I
cannot change it without major problems. See kernel/keyboard.s for
details. If anybody is willing to make an even partial port, I'd be
grateful. Shouldn't be too hard, as it's tabledriven (it's assembler
though, so ...)

Although linux is a complete kernel, and uses no code from minix or
other sources, almost none of the support routines have yet been coded.
Thus you currently need minix to bootstrap the system. It might be
possible to use the free minix demo-disk to make a filesystem and run
linux without having minix, but I don't know...

And while it's compiling you can put on your cap, goggles, and your duster and take a spin in your Pope Toledo. :-)

Kent

I think it'll be too...undeveloped for me to even use it at some degree and I don't think I would try and go through that much just to get this kernel working that probably wouldn't run any good on my system anyway.

Can i be able to compile the 0.0.1 linuz kernel in vmware.
My hardware configuration is like:-
Intel(R)Pentium(R) D CPU 3.00 GHz
SATA IDE
SyncMaster 740 N - VGA Screen

Regards,
Rodrex lee

Who cares? Now go away. There is no need to wake a 3 year-old thread from the dead.

Eric

It's a regular occurrence on the LQ forums.
Reviving old threads, reviving old Slackware, reviving old kernels - what next?

It seems like a Dracula's movie =v_v=
Hehehehe, let me look for any oldest threads and let it wake up :-P (joking)

FYI Eric,Learning few things from scratch is much better,thats make me to wake up the old thread,which wont have the solution,me i am able to help others with my efforts,but for that i need ur helps also.

so i request to post ur ideas related to that instead of posting the bogus comments.

Start by compiling gcc-2.95.3 and installing that in such a way that it doesn't mess with your regular compiler -there are other threads which discuss this, so search for them. Once you have gcc-2.95.3 working, you may be able to compile an old linux kernel with that. If not, you'll need to use gcc-2.95.3 to compile an even older version of gcc(actually egcs) and use that.
But I wouldn't place much hope in getting 0.0.1 to compile -better to try the 0.0.99 release -it was actually used and known to work.
If you want a good example of how to make it work and scripts to compile it -look for the 'woaf' or '1-disk-X' or 2-disk-X projects.

My post wasn't entirely sarcastic. I was struck by the coincidence of this thread being revived at the same time as this one, about early Slackware versions:
http://www.linuxquestions.org/questi...re-3.5-674477/

8.1 has gcc-2.95.3.