• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Klinux Update

K

Kilowatt

Golden Member
Well folks,

After scraping half what I had started for Klinux-v.3 because of the new Linux kernel 2.4 being released, and the updated dnet clients coming out, I finally found some time this weekend to mess with Klinux-v.4 🙂
/me and a few local friends are running Klinux-v.3, so I'm starting anew at v.4 😎

After messing with the new kernel, and reading everything I could about it, I finally got a floppy to boot and run the dnet client 8012-466 for Linux.

This is only a development version mind you.
I think I'll work on including module support to reduce the kernel size.
I've only included nic drivers for a few cards I have on hand, and the dang kernel is HUGE at 544k. :Q
(the older one I used before was only 445k)
I had to yank most of my scripts, a few cool features, and include my own "ifconfig" in the setup.
BUT, it now has 16384k for a ramdisk size. 😎

There are some pretty cool things in the new kernel, like a kernel based http server, routing and firewall, wireless nics, and a host of others.

This is just to keep you all updated, and to know I'm not just sitting on my butt.
You can keep an eye on the new devel Klinux at my stats generator page.
Look for (what else) Klinux-v.4 😀 (more stats!) It's running on my CII@893.

Tomorrow is almost a holiday for me, with Racing (Daytona) taking center stage, so "no worky mañana".

I do need some input on the differnet Linux dnet clients, and how fast they'll run OGR, as all I do is run RC5.
 
I have a K6-2 with mobo and case that's not being used for anything. I also have an ISA vid card, 64MB RAM, a keyboard, and a monitor laying around. So, if I go get a floppy drive, and a NIC off the list, is this all I need to run Klinux? Would I need to make a boot disk to copy Klinux on? Is there a TA_SETI for OGR? I'm not that familiar with Linux, I'm one step below a Newbie, uh, I'm a linux virgin 😱 so keep it slow and simple 😉

thanx
 
Kilowatt or anyone else. I have a few old Pentium boards/CPU's sitting around so I decided to put together a few more systems cracking RC5. I made the Klinux floppie for my network card which in this machine is a 3Com Eitherlink II. All boots and it does find the card and the DCHP does find my main system on the network. I can ping back and forth between the main Win 2k Pro system and the Klinux box but when I configure and run the Dnet client it can't find the dnet server and the light on the NIC does not blink either. Would anyone know what is going on? The network is for sure working and on all the other machines running 98, ME and 2k dnet works fine and finds the dnet host. Any help would be appreciated. I have not messed with networking and Linux in a long time.

😱

Opps, Figured it out. All it needed was to go into netconfig in Klinux and configure the gateway and DNS. Now it works like a champ. Thanks for the readme Kilowatt!

 
my network card which in this machine is a 3Com Eitherlink II.

:Q

Man.. when you said old, you meant OLD! 😉
 
Spookyfish:

Yes, the ta_seti@hotmail.com address will submit work to the Seti Cavalry mini team in both RC5 and OGR.
 
Killowatt,

One quick question that I'm sure has been answered before. Was there a specific reason to drop the 2.1 non-DHCP version of the client? Just wondering because I needed a quick fix on Friday last week to keep a cow running in the lab at work but had to setup DHCP on my linux server as well. No great hastle and the cow is running nicely but it just threw me not having version 2.1 available.
 
Speaking of old parts (I said parts, not farts, Engineer, so watch it..😛),

What's the chance of there being an SMP capable Klinux version for pentiums? I have a dual P100 sitting here just begging for a Klinux SMP version and it doesn't even have to be DHCP capable. 🙂
 
CLL Sr, I said "a few local friends", how did you get it? :Q
Just kidding You know where it is. 😀

Dougal, 2.1 was corrupt, so instead of setting everything back up to do version 2 over again, I just yanked it off the site.

Ray, Chances are good. 😎

Klinux-v.4 will have a kernel capable of running on a 486, but be able to handle SMP mobos on anything above.
While it's not the optimized way to do a kernel, it is a generic kernel that will work on the majority of machines.
Seeing as the kernel really only needs to boot the machine, it doesn't have to be fast since it'll only be used to run the Dnet client.

I've managed to get the kernel down to 504k so far, but still it's a little bigger that I'd like, as I still want to include some of the neato features I was working on for version 3.

I still need to see about loading modules, instead of having everything in the kernel itself.
I believe modules will compress better than a huge kernel will, thus letting me include more.

I still need input on whether the 466 Linux client runs OGR better or not.
I don't see a difference between 463, 465 or 466 doing RC5.
 
I LOVE Klinux. One of my nodes just hit 97,000 blocks and several others are over 80K since last boot. All overclocked, all just running in RAM, and all running the King of single floppy distros; Klinux!😀

If it were not for the great vacuum cleaner crash, several would be well over 100K.😱

Russ, NCNE
 
Narzy,

Let's just say that one should never plug a vacuum cleaner in to an already overloaded circuit.🙂 I have since split the load between two breakers.

Russ, NCNE
 
<Let's just say that one should never plug a vacuum cleaner in to an already overloaded circuit>

Ouch, that sucks....










Leave it to me to state the obvious &quot;pun&quot; 😛
😉
😀
 
I still haven't had any input on the 466 Linux client and OGR, so I don't want to hear any compliants later.

Update
After playing around with the 2.4 kernel for the last week, I've decided to forget about it.
It's just too big to include on a singe floppy.
Even with just one nic driver, it's still over 510k.
I'll continue using 2.2.18 instead.
2.2.18 will include 1/3rd of the nic drivers and still be under 450k.

I've been working on a different &quot;termcap&quot; to show a little more on the screen, but I'll need to see if it'll work with some older 512k ISA video cards.
 
Dougal and Kilowatt,

I was able to use Klinux 2.1D on a network without a DHCP server running.
What I did was to let it boot up(it timed out trying to find a DHCP server) to root as usual...
Then I simply typed the 'netconfig' command and entered the IP address, host mask, gateway IP address and DNS server IP address. I then did the dnet extraction, entered the configuration parameters and now she's cracking away.

That same version of Klinux is running on a quad ppro-200 box, it sees all four processors and is communicating through a Netgear FA310TX 10/100 NIC. It is doing about 2.25 Mkeys/sec, although at the moment it is doing OGR and RC5 simultaneously.

Sooooo........ Kilowatt, Thanks for Klinux!

HeavyIron
 
Thanks for the &quot;endorsement&quot; HeavyIron 🙂

Klinux-v.4 will have the DHCP search enabled as default.
It'll let me just make 3 different images, instead of 6 to cover most all the network cards.

3 is alot easier for me than making sure 6 different images zip-up, upload, download and then will uncompress in Win32 and Linux and not be corrupted.

If you aren't running a DHCP server, no big deal, just let it time out, and run &quot;netconfig&quot; manually.
it's not that hard

Since the 2.4 kernel is just too big to use, and Dnet just pulled their 8012 clients (what a deal :|) I'm pretty much back to what I was originally going to do with Klinux-v.3
I'm going to be using the Linux kernel 2.2.18, and the Dnet client 463b for Linux.

Klinux-v.4 WILL let you save your dnetc.ini file to a different floppy for use on a different node.
You will have to setup your other node's &quot;netconfig&quot; as there is no way for Klinux to save it, and not be the same as the last node you had setup.
You can't have two IP's the same on one LAN, so I see no point.
You CAN have the same dnetc.ini setup on different nodes, so I'll let people save it by running a simple &quot;save&quot; command after originally setting up their client.
 
Kilowatt,
<Ray, Chances are good.>

<Klinux-v.4 will have a kernel capable of running on a 486, but be able to handle SMP mobos on anything above.>

I understood that with the 2.4 kernel you were including SMP support for everything above a 486.

Then later:
<After playing around with the 2.4 kernel for the last week, I've decided to forget about it.>
<I'll continue using 2.2.18 instead.>

That's why my SMP for Pentiums question. I didn't know if going back to the older kernel would mean you would have to drop SMP capabilities for pentiums or not. I don't have a clue about Linux, so consider it a stupid user question, as I read the entire post and didn't find a good answer. 😛

🙂
 
Hi HeavyIron,

Thanks for the reply. I must admit I never thought to try. I guessed the netconfig pogram wouldn't be needed for DHCP so would be missing. Silly me for not trying. DOH!!!

Kilowatt, you are indeed, Da Man. KLinux just keeps on getting better 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top