1 |
maillog: 25/03/2004-12:01:32(+0100): Paul de Vrieze types |
2 |
> On Thursday 25 March 2004 08:52, Georgi Georgiev wrote: |
3 |
> > and have vim on my laptop. However, if I chroot to /remote/laptop, I'd |
4 |
> > end up making all communication over NFS and using the hard disk of |
5 |
> > the laptop for compiling as well, which is not very fast. I was doing |
6 |
> > something with |
7 |
> |
8 |
> Isn't this /remote/laptop partition local to the server? using chroot or |
9 |
> not does not in any significant way change the performance of access to |
10 |
> this location. |
11 |
|
12 |
/remote/laptop is mounted over NFS. /remote/laptop is the / of my laptop and it |
13 |
is physically on the laptop. The desktop is compiling and hopefully, using |
14 |
"ROOT=/remote/laptop" is emerging the software remotely to the laptop. |
15 |
|
16 |
> |
17 |
> > mount -o bind /var/tmp/portage/ /remote/laptop/var/tmp/portage/ |
18 |
> |
19 |
> Using a fast disc for /var/tmp/portage is allways advantageous. |
20 |
> |
21 |
> > which speeds up things a bit, but it is still slower and too annoying |
22 |
> > to do every time. |
23 |
> |
24 |
> Then do it automatically from fstab |
25 |
|
26 |
I don't have /remote/laptop always mounted (only when the laptop is powered on |
27 |
and I want to emerge packages there), and I'd need to do the mount -o bind |
28 |
commands after I mount /remote/laptop. I agree that this is not much of an |
29 |
issue. A proper shell script would do the mounts right when I need them. |
30 |
|
31 |
There is still the problem of using the slow disk of the laptop (for all |
32 |
headers, libraries, etc. while compiling) over NFS, if I chroot to |
33 |
/remote/laptop. |
34 |
|
35 |
-- |
36 |
/\ Georgi Georgiev /\ Cropp's Law: The amount of work done varies /\ |
37 |
\/ chutz@×××.net \/ inversly with the time spent in the office. \/ |
38 |
/\ +81(90)6266-1163 /\ /\ |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |