| 1 |
On Thursday 13 February 2014 11:41 PM, J. Roeleveld wrote: |
| 2 |
> On 13 February 2014 17:55:19 CET, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
>> On 13/02/2014 18:35, Edward M wrote: |
| 4 |
>>> On Thu, 13 Feb 2014 02:44:02 +0200 |
| 5 |
>>> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 6 |
>>> |
| 7 |
>>>> On 13/02/2014 02:40, Edward M wrote: |
| 8 |
>>>>> Howdy, |
| 9 |
>>>>> |
| 10 |
>>>>> Been busy learning Linux :-) got new email other was getting |
| 11 |
>>>>> crowded. I'm planing on installing Gentoo on a few systems and I |
| 12 |
>>>>> was wondering to save bandwidth, i could install portage to the |
| 13 |
>>>>> other Gentoo installs from my system instead downloading from |
| 14 |
>>>>> mirrors? |
| 15 |
>>>>> |
| 16 |
>>>>> Thanks in advance! |
| 17 |
>>>>> |
| 18 |
>>>> |
| 19 |
>>>> Yes. |
| 20 |
>>>> |
| 21 |
>>>> The stage are just tarballs, download them once, copy to the new |
| 22 |
>>>> location and unpack. |
| 23 |
>>>> Same with the portage snapshots. |
| 24 |
>>>> Same with the distfiles. |
| 25 |
>>>> they are just files, copy them to where they need to be and use |
| 26 |
>> them, |
| 27 |
>>>> or let emerge find them. |
| 28 |
>>>> |
| 29 |
>>>> Read the install docs first and learn more about how Linux works on |
| 30 |
>>>> the command line. Pretty soon you'll find the bits where the manual |
| 31 |
>>>> says "download such-and-such from this place" and you'll spot that |
| 32 |
>> if |
| 33 |
>>>> you already have the downloadable file you can just use it already. |
| 34 |
>>>> |
| 35 |
>>>> |
| 36 |
>>>> |
| 37 |
>>> |
| 38 |
>>> Alan, |
| 39 |
>>> |
| 40 |
>>> I want to apologized I did not thanked you for the great advice you |
| 41 |
>>> gave me. I noticed this this morning when I re-read my emails. |
| 42 |
>>> |
| 43 |
>>> Best Regards. |
| 44 |
>> |
| 45 |
>> |
| 46 |
>> No problem. Come check my inbox sometime, any given mail stands a 1 in |
| 47 |
>> 3 |
| 48 |
>> chance of being answered at all :-) |
| 49 |
>> |
| 50 |
>> I see earlier in the thread someone mentioned sharing the portage tree |
| 51 |
>> over NFS. Now this is by far the best solution of all in terms of |
| 52 |
>> outright performance; but be warned up front - there are pitfalls. |
| 53 |
>> |
| 54 |
>> NFS is nothing like setting up a Windows share, and there's nothing |
| 55 |
>> about it that just magically works. Folks new to Linux often have heaps |
| 56 |
>> of trouble with it (mostly because NFS assumes you are going to do a |
| 57 |
>> whole lot of heavy lifting yourself and you have already dealt with the |
| 58 |
>> tricky issue of keeping user accounts in sync, and permission woes). So |
| 59 |
>> by all means use NFS, just know upfront the learning curve is steepish, |
| 60 |
>> and the good folks on this list can give tons of good advice as well as |
| 61 |
>> get you through the arcane basics :-) |
| 62 |
> |
| 63 |
> If you want to do NFS. Let us know. |
| 64 |
> It can be done easier then Alan makes out. But you then need to ensure only your machines are connected to the network. |
| 65 |
> |
| 66 |
> In simple terms: |
| 67 |
> Configure NFS to allow every user from any machine (or network ip range) has access to the files. The NFS server can be told to replace any connecting user with a single user on the server. |
| 68 |
> |
| 69 |
> That is what I do. With a good firewall preventing non wired owned machines to have any access. |
| 70 |
> |
| 71 |
> -- |
| 72 |
> Joost |
| 73 |
> |
| 74 |
|
| 75 |
My favorite firewall rule to do this don't restrict any kind of traffic |
| 76 |
between own network and filter the rest. |
| 77 |
Use ipset. Very easy. |
Archives