Wow is this going to be a long initial post.
So having grown tired of using OS 8.6 on my trusty 1400c, especially with programs being sooo outdated for it, I decided to check into installing Linux on it. The docs/tutorials/howtos are sparse but theyre around, and before too long at all 'check into' turned into 'must succed...' I think I hit the hay at like 7AM last night after quite a few hours into trying to get it to work. (And yes, I do know it's like practically impossible to get working on a 1400...)
The general plan of attack? To combine an mklinux kernal and installer and Debian 3.0r2 into a working system, as in:
(with the exception of installing from CD, see below)
Here's a brief recap of what I've done so far (or as brief as I can be:)
Found out NuPowr 233MHz G3 was probably causing the hang I was getting trying to boot Linux. Grabbed a few tools and threw the original proc back in (actually I dont even know which it is, the machine is just labeled "PowerBook 1400c" so I'd guess possibly a 117?) and success! Tux smiled at me and I ended up in an installer. (I may be selling the upgrade if I get this to work, original box, floppy disk and instructions included, no tools though. Anyone interested?)
Problem was, didnt have access to my CD-ROM (the "internal"/expbay one) and dont have an external SCSI drive, or enough room on the 1GB internal to stick the ISOs on a partition, so I really need to get to the expansion bay. I switch the kernel over to the ancient EXPBAY (MKLINUX) one, and boot it... w00t! I alter MkLinux's config and tell it the root is the CD-ROM (/dev/hdc) and the light flickers before it tells me /mach_servers/ isnt on there.
As you can see the two problems compliment each other, in the worst of ways... one has each of what I need, either access to the expansion bay, or the installer, but not both.
Here's what Ive done to try and get around THAT:
*Used ramdisk.img.gz, vmlinux, vmlinux2.4, and everything else i could think of that might be a RAM disk from the Debian installer CD #1 and fed it to MkLinux and bootstrap.conf by renaming it "vmlinux+installer" (or something REALLY close to that) and putting it in mach_servers. One of these ALMOST worked (like it started to load it, spit a few messages off, then terminated rather than wouldnt load) although i dont remember for the life of me which.
I'm thinking I need a new kernel+installer, one that has support for the 1400 expbay, or I need to make the expbay kernel + an installer into my own custom kernel+installer? I may not though, because I will admit that while this will be the fourth machine Ive installed Linux on, I'm still very much a novice with Linux so I may actually NOT know what I need.
Do the newer MkLinux kernels (maybe I should snag the most recent) have support for my expansion bay? Anyone know?
Here's the web pages Ive been looking at that have worked me thru the task so far, perhaps a gem of info will appear to someone that I overlooked (which I bet Ive done, it was waaaay late:)
http://www.icedtrip.net/guides/woody_1400.txt , of course
Anyone with more knowledge than me care to take a stab at helping me? I have an OS X box should its Unix underpinnings come in handy.