| 1 |
Duncan wrote: |
| 2 |
|
| 3 |
> All that dealt with, there's only one possibly valid reason I'm aware of, |
| 4 |
> for those already splitting out the portage tree onto its own partition, |
| 5 |
> why they might /not/ wish to use reiserfs. Those that only have ext2/3 |
| 6 |
> configured in their kernel may not wish to bother configuring reiserfs for |
| 7 |
> just the portage tree. |
| 8 |
|
| 9 |
I'd better tell you my reason then - I've been using Partition Magic to |
| 10 |
manipulate my partitions for several years now, and it doesn't do Reiser. |
| 11 |
|
| 12 |
> Peter Humphrey posted <43F20505.3040207@××××××××××.uk>, excerpted below, |
| 13 |
> on Tue, 14 Feb 2006 16:27:49 +0000: |
| 14 |
> |
| 15 |
>> Don't combine systems' /var/log directories - you will end up with |
| 16 |
>> deeply troubled emerge.log and PORT_LOGDIR records. |
| 17 |
> |
| 18 |
> "Deeply troubled" is an apt description. <g> In any case, combining |
| 19 |
> /var/log dirs makes no sense, |
| 20 |
|
| 21 |
Agreed. |
| 22 |
|
| 23 |
>> I'm not yet sure of the wisdom of combining /var/tmp from different |
| 24 |
>> systems: I haven't yet sorted out the consequences for the portage work |
| 25 |
>> directories. Watch this space. |
| 26 |
> |
| 27 |
> In any case, there's no damage to portage by combining those dirs, or |
| 28 |
> removing the contents at boot, either. If you have something set up |
| 29 |
> locally that saves data across reboots to either /var/tmp or /tmp, |
| 30 |
> consider changing it, as that's not what those dirs are for, and expecting |
| 31 |
> them to be safe for that could get broken at some point. |
| 32 |
|
| 33 |
That's more-or-less what I thought - thanks. |
| 34 |
|
| 35 |
-- |
| 36 |
Rgds |
| 37 |
Peter. |
| 38 |
-- |
| 39 |
gentoo-amd64@g.o mailing list |
Archives