1 |
On Wed, Nov 12, 2003 at 04:16:42PM +0000, Toby Dickenson wrote: |
2 |
> On Wednesday 12 November 2003 14:18, Paul de Vrieze wrote: |
3 |
> |
4 |
> > > With that in mind, why is there a /var? use /tmp ;-) |
5 |
> > |
6 |
> > Because /tmp is for shortlived temporary files. /var is for files that |
7 |
> > can be regenerated, but that regeneration is allowed to be expensive. |
8 |
|
9 |
/var is the compliment to /usr and /etc, not /tmp. |
10 |
|
11 |
> That description applies to /var/cache. but not all of /var. |
12 |
> http://www.pathname.com/fhs/2.2/fhs-5.5.html |
13 |
> |
14 |
> /var isnt only for things that can be regenerated. |
15 |
|
16 |
It should be for files that are dynamically generated, as opposed to static |
17 |
configuration and binary files. |
18 |
|
19 |
> The content of /var/mail in particular is irreplaceable. |
20 |
|
21 |
To users, maybe, but it's hardly critical to the operation of the system. |
22 |
|
23 |
> http://www.pathname.com/fhs/2.2/fhs-5.1.html |
24 |
> |
25 |
> > tmp must not contain such caches. On /tmp one is able to run a tmp |
26 |
> > reaper, on /var it would be less than desirable. |
27 |
|
28 |
You should be able to run: |
29 |
|
30 |
$ find /var -type f -exec cp /dev/null {} \; |
31 |
$ reboot -f |
32 |
|
33 |
and still have a bootable system. Consider doing that with /usr or /etc |
34 |
to see the distinction. |
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |