James, > 1) For me more and less work on the server, and consequently do work on my > hardy clients. More works in the initrd image. > It certainly won't work for you on the clients (try - text shell console instead of any XDMCP/LDM) > 2) Why would you want any NFS on the client ? Hardy works with a squashfs > image so NFS in not applicable to the client in any way UNLESS you were doing > local apps and I don't know the status of local apps on LTSP5 > I do not use squasfs. I use NFS root / bind mounts. It is because: - boot speed is not so much important for me. - NFS root is much better manageable (I do not need to rebuild the squashfs root every time I change something) > 3) For local media ?? Where ? Why ? > - I need to allow users to ssh from the server back to the clients. Their homes are on NFS so hence automounter is necessary. - some legacy X clients we use relies on fonts rendered by the X server - X server need to have access to these fonts and fonts are on NFS storage.
Be it as it could, NFS should be fully supported on the clients - I can not help myself. And beside I believe it is not much deal to fix it - just the mount.nfs command is broken (and hey, it works with Redhat diskless machine so why should not it work here?) and the console kit needs to be fixed anyway. And regarding Michaels question: I have filed the problem with the mount command already on Gutsy and nobody cared... :-( Ondrej ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
