Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 18.119.135.231
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
appadmin
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
base-files /
[ HOME SHELL ]
Name
Size
Permission
Action
FAQ
4.58
KB
-rw-r--r--
README
4.58
KB
-rw-r--r--
README.FHS
1.13
KB
-rw-r--r--
changelog.gz
1.22
KB
-rw-r--r--
copyright
1.2
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.FHS
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 <sanvila@debian.org>
Close