| 1 |
Apparently, though unproven, at 20:19 on Tuesday 02 November 2010, Volker |
| 2 |
Armin Hemmann did opine thusly: |
| 3 |
|
| 4 |
> On Tuesday 02 November 2010, Stroller wrote: |
| 5 |
> > On 2/11/2010, at 10:46am, Alan McKinnon wrote: |
| 6 |
> > > ... |
| 7 |
> > > hard links will only work if /etc/portage and /var/lib/portage are on |
| 8 |
> > > the same filesystem. Frequently, they are not. |
| 9 |
> > |
| 10 |
> > For small values of frequently. |
| 11 |
> > |
| 12 |
> > Stroller. |
| 13 |
> |
| 14 |
> for every sane system out there. |
| 15 |
> |
| 16 |
> /var is a candidate for surprisingly filling up / to 100% so it is a smart |
| 17 |
> and sane choice to put it on its own partition where damage will be |
| 18 |
> reduced to some log files or an aborted emerge. |
| 19 |
|
| 20 |
|
| 21 |
You're both right, but for different reasons. It'd done less often on a laptop |
| 22 |
or personal machine than on a server for instance. And on embedded stuff, |
| 23 |
almost never. Example: Any junior of mine who doesn't make /var separate is |
| 24 |
liable to be served his own testicles for dinner, and they know it. But my |
| 25 |
laptop is one big filesystem. One case definitely needs it, the other one |
| 26 |
doesn't really. |
| 27 |
|
| 28 |
You're probably looking at the same question from entirely different needs and |
| 29 |
viewpoints. |
| 30 |
|
| 31 |
-- |
| 32 |
alan dot mckinnon at gmail dot com |
Archives