1 |
On 10/09/2013 18:57, gottlieb@×××.edu wrote: |
2 |
>> I'm curious as to why you do that, I can't see any benefit at all. |
3 |
>> > |
4 |
>> > The "var" filesystem is an LV and is only useful if it is mounted at |
5 |
>> > /var where packages expect it to be. Why add the extra complexity of |
6 |
>> > mounting it somewhere else and then bind mounting it to the pnly place |
7 |
>> > it can be useful? |
8 |
> An old habit/belief that mounts go in /mnt. Since both revdep-rebuild |
9 |
> and you believe this is a bad habit, I now mount directly on /var /opt. |
10 |
|
11 |
Ah, OK. |
12 |
|
13 |
Technically a mount can go anywhere. Permanent mounts just go where they |
14 |
are supposed to go, and /mnt was a throwback to the bad old days where |
15 |
everything else was mounted at /mnt/<something>, including cdroms, |
16 |
filesystems you wanted to access quickly, windows partitions on a dual |
17 |
boot machine etc etc. or the gentoo partition during install before your |
18 |
chroot |
19 |
|
20 |
Then removeable media started being mounted in /media where the GUI |
21 |
could manage it and not have to deal with root-only permissions in /mnt |
22 |
|
23 |
Nowadays media goes in /run/media.... |
24 |
|
25 |
All very confusing and hard to keep up with. It's like trying to figure |
26 |
out what politicians and your boss happen to be talking about today :-) |
27 |
|
28 |
|
29 |
|
30 |
> |
31 |
>> > There's rules of thumb about this that will always work: |
32 |
>> > |
33 |
>> > No object in /tmp can be expected to survive successive invocations of |
34 |
>> > the program that created the object, and never survive a reboot; |
35 |
>> > No object in /var/tmp can be expected to survive a reboot |
36 |
>> > |
37 |
>> > The best place for temp files, ironically, is ~ |
38 |
> I set tmpwatch and wipe_tmp so that files survive in /tmp and /var/tmp |
39 |
> for a month. |
40 |
> |
41 |
> I don't like ~ for temp files since on some, admittedly rare, occasions |
42 |
> I actually use the gnome gui file manager and don't want a huge ~. I |
43 |
> have long ago created ~/tmp (also cleaned after a month by tmpwatch) so |
44 |
> the only problem is breaking the habit of placing short-term files in |
45 |
> /tmp instead of ~/tmp. |
46 |
|
47 |
OK, I get it. I'd write all that temp stuff to /var/tmp so it doesn't |
48 |
get nuked by something cleverly trying to manage /tmp. |
49 |
|
50 |
I often feel the same way about ~/.xsession-errors. |
51 |
I have to restrain myself from symlinking it to /dev/null :-) |
52 |
|
53 |
> I realize that habit is bad for my (system's) health, but still find it |
54 |
> hard to break. I shall try again. Perhaps this is very mild form of |
55 |
> what intelligent smokers feel :-). |
56 |
|
57 |
There is no such thing as an intelligent smoker; there are only stupid |
58 |
smokers :-) |
59 |
|
60 |
I'm a two-packs-a-day man myself, I speak from many years experience! |
61 |
|
62 |
|
63 |
-- |
64 |
Alan McKinnon |
65 |
alan.mckinnon@×××××.com |