> > and HTTP require 52 MB - who picked that number?? ;-) ), and a first
>
> We. Ramdisk takes RAM.
>
Cool. You got 4 meg of RAM, a soldering iron and a hammer? I think that
should do it to get this system up to spec. ;-)
> Are you sure you have nothing on log console?
>
Absolutely positive. Even got it to a point where NFS wasn't working for
anything (more on this later), and on the cooker machine I get "mount: RPC:
Timeout", but definitely nothing in the install. Just the message on
console 1 "I couldn't mount the directory" (or whatever it says).
> Also, pleasy try to nfs mount from a valid host.
Here's where I thought you had me! "Ah," I thought, "I'm a moron". I
checked the exports file and it turns out the IP I picked for this machine
didn't have rights. So I redid the exports so there were no restrictions on
the export, and now NFS is just hooped on the server machine. This happens
often. It's a 7.2 machine, and after a reboot or after I change something
in exports (usually through linuxconf) and reload NFS, it often just stops
working. This morning after I redid the export through linuxconf it
wouldn't work. Couldn't even mount from the local machine to itself. So I
rebooted (I think I need a 12 step program to help end that M$-induced
habit), and was able to mount locally on the 7.2 machine to itself. Tried
it from the cooker machine, and it timed out. Same from the install. Went
back to the 7.2 machine and tried again, and it timed out too. Something
crashed it? Or a better question: What is it with NFS on 7.2? ;-) Then I
had to leave for work (where I write this - shhh!), so I couldn't play
anymore.
> This nfs mount stuff
> should do it. Please also try to have a 2.4 kernel on the nfs server,
> there are some weird incompatibilities between different kernels for
> server and client sometimes.
>
I thought of that. The 7.2 machine is the stock 2.2.17-21mdk kernel. But
the cooker machine is 2.4.3-5mdk, and I tried exporting something from that
machine (not doing anything stupid like restricting access) and directing
the installer to that, and that wouldn't mount either. But I didn't try
that one too hard, so I could have messed that up too.
> They don't have a graphical install -- do they? ;-)
>
No, they have an evil install that makes you partition and format the hard
drive before you do anything else at all, including setting up your network
card, so if your NIC isn't BSD compatible, you don't get to find out until
you've completely trashed the system. I like the Mandrake way better for
that. :-)
> Please try with an alternatives/network.img to have a 2.2.19 kernel, so we
> can understand if it's incompatibility between kernels.
>
> > Oh, ya, and I tried all three network boot disks (the main network.img
> > and the two "alternatives"), and it didn't help any.
>
> Argh. Well.
>
Ya, that's what I said too.
> --
> Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
>
Eaon
