Hi, On Fri, Sep 13, 2002 at 10:05:58AM +0300, Muli Ben-Yehuda wrote: > On Fri, Sep 13, 2002 at 12:25:25AM +0300, Yedidyah Bar-David wrote: > > > > I think the main difference is that ML answers are given late at night, > > with late-at-night moods (and tiredness), for better or worse :-). > > I disagree. I often do email at the early hours of the morning :) > But you're certainly right that a mailing list answer carries with it > no explicit[1] responsibility and no warranty, unlike something you > paid for. > > [1] explicit, unlike implicit. I *hate* being wrong in public, and > therefore will usually check my facts three times before > posting. Usually.
I of course agree. I also intended to mean they are less formal, have higher tendency to go to non-strictly-relevant directions, etc., as long as the author thinks there are enough people on the list that will enjoy reading (I personally think that many Israeli Linux users (the audience here) tends to have similar interests even off-topic, such as where to buy good, cheap hardware, that noone ever found inappropriate here even though off-topic). > > > > ObLinux: how do I share easily an entire machine's hard disk with > > > other machines? NFS sharing / led to all sorts of nastiness. Pointers > > > to FMs welcome. > > > > Can you give more details? What is the exact need? For example, > > I run some machines with nfsroot, so exporting their *physical* > > disk is trivial. Do you refer to a physical disk, all the local > > partitions, all mounted FSs (including /proc, nfs)? > > Ok, setup: one small LAN, one server (fwall + outside services), one > development machine and two test machines. Test machines should be > running differnt distributions from time to time, so a shared nfs root > is not a good option. Ideally, the development machine's '/' and all > regular file systems mounted on it should be nfs mounted (or otherwise > accesible) on the test machines. Not as their "/"? Simply accesible? Assuming you exported with the options you need (probably "(rw,no_root_squash)"), I see no problem with that. Having them mount it rootnfs is more problematic, of course. > > > What problems did NFS exporting / cause? > > it was a combination of NFS exporting / and trying to access things as > root, I suppose. Missing directories, inaccessible files, strange > errors from programs that deal with the file system (mv, cp, etc). Again, this sounds like missing no_root_squash. > > > Did you try the usermode nfs server? (from > > <ftp://linux.mathematik.tu-darmstadt.de/pub/linux/people/okir>. > > Not maintained for a long time, but still might be useful). > > How might it be useful? The big difference is that exporting (and mounting) "/" will take with it all mounted FSs, unlike the kernel server which exports a single FS at a time. The other difference is lower performance. > > > Did mount --bind somewhere and NFS exporting it didn't work either? > > Note I didn't try this myself, but writing this answer makes me > > want to try (for diskless machines' server - I currently do not > > share its "/"). > > I am not aware of mount --bind. I'll RTFM. > > Thanks, > Muli. > > -- > Muli Ben-Yehuda > syscalltrack hacker-at-large > Didi ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
