Felix Miata <[EMAIL PROTECTED]> writes: > Guillaume Cottenceau wrote: > > > Felix Miata <[EMAIL PROTECTED]> writes: > > > > Eventually I got set up for NFS install, and that won't even get out of > > > text mode. Each time, right after entering server IP and directory it > > > just sits there, and on tty3, last line I see is 'preparing nfsmount for > > > [IP]:[dir]', and no evidence that SCSI ever loaded. Has SCSI support > > > When there is no response, it's often linked to a bug in the > > kernel driver. Maybe you have a long timeout that you didn't > > The problem turned out to be the server was in runlevel 2 the whole > time. There should be some message from the installer that the server is > not available.
There are of course messages. You probably have some sort of firewall as well, or something. If I try to connect network.img/NFS to a machine on which the nfs server was shut down, it immediately (1 or 2 seconds delay) errors out with: I can't mount the directory from the NFS server. > > > been deleted from the boot floppies? I can't remember when the previous > > > versions asked for SCSI support confirmation. > > > What's the connection between SCSI support and starting an NFS > > install? There is no need for SCSI driver when starting an NFS > > install, of course, and thus no SCSI driver is loaded at that > > point. > > You mean my install to a SCSI HD target doesn't require any SCSI > support? ;-) After I got the server in proper gear I remembered when Yes. Starting the NFS install doesn't need any SCSI support of course. SCSI support is enabled when the install has been loaded and started up (from NFS in your case). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
