Matthew wrote: > Yeah it can be a problem that X needs the network ALL the time. > An alternative is to use local X and use network shares which > don't need to be connected continuously.
I use your approach Matthew with Samba or NFS depending on client. Its less prone to complete downtime. Jeff Wrote: > You'll find that most corporates with Windows-based desktops use > roaming profiles, and network authentication / storage /printing for > just about (if not absolutely) everything. It's a central part of the > policy, support,service equation. IMHE(xperience) Some do, some don't. For most of the ones I know network authentication does not lock the user from the desktop systems on their own machine. Failure to logon might stop them accessing network drives however. Simon wrote: > And given the continually dclining IT market I woiuld think that a lot > of companies are interested in saving $ on hardware and software - or > else they would still be out there buying, and from my education > viewpoint it is essential to get every ounce of use out of every $ > spent. I guess the point on cost of hardware vs losing 1600 person-hours @ say $20/hour (plus on-costs) was lost somewhere in the telling. Anyway, the point was - that's a lot of hardware $ for one failure! It's all how you see the risk/reward I guess. I'm glad X has that feature (remote X) but surely the days of the minicomputer and it's requisite single point of failure problems are over? I used to get a cold shiver down my spine as an IT Manager when someone said 'has the (ie one) computer gone down'. Stu On Fri, 2002-11-15 at 14:20, Matthew Hannigan wrote: > Yeah it can be a problem that X needs the network ALL the time. > An alternative is to use local X and use network shares which > don't need to be connected continuously. > > I'm not sure about NFS (is there a caching nfs client side > for Linux?) but there are things like afs, codafs, intermezzo. > (Anyone care to comment on their maturity under linux?) > > If the clients are windows, it will let you write locally > while the network is down and sync later. Works fine with > samba -- you can even redirect "My Documents" etc to the samba > home share to have a reasonably user-friendly and network > fault tolerant environment. > > Matt -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
