- fix 229870 - bug in fadvise(2)

- fix 229204 - bug in passwd(5)
This commit is contained in:
Ivana Varekova 2007-02-27 11:33:31 +00:00
parent 69d5a27a3b
commit c05e3f4348
3 changed files with 212 additions and 2 deletions

View File

@ -0,0 +1,178 @@
--- man-pages-2.43/man2/fadvise.2.pom 2007-02-27 11:08:29.000000000 +0100
+++ man-pages-2.43/man2/fadvise.2 2007-02-27 11:24:26.000000000 +0100
@@ -1,90 +1,85 @@
-.\" Copyright (C) 2004 IBM Corporation
-.\" This file is distributed according to the GNU General Public License.
-.\" See the file COPYING in the top level source directory for details.
-.\"
-
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "FADVISE64,FADVISE64_64" 2 "2004-March-12" "Linux 2.6" "Linux Programmer's Guide"
-.SH NAME
-fadvise64,fadvise64_64 \- Give advice about file access
-.SH "SYNOPSIS"
-.ad l
-.hy 0
-.HP 44
-long\ \fBfadvise64_64\fR
-(int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR, int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR);
-.HP 19
-long\ \fBsys_fadvise64\fR\
-(int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR, int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR);
-.ad
-.hy
-
-.SH "DESCRIPTION"
-
-.PP
-Allows an application to to tell the kernel how it expects to use a file handle, so that the kernel can choose appropriate read-ahead and caching techniques for access to the corresponding file. This is similar to the POSIX version of the \fBmadvise\fR system call, but for file access instead of memory access. The sys_fadvise64() function is obsolete and corresponds to a broken glibc API, sys_fadvise64_64() is the fixed version.
-The following are the values for the \fIadvice\fR parameter:
-
-.TP
-FADV_NORMAL
-No special treatment.
-
-.TP
-FADV_RANDOM
-Expect page references in random order.
-
-.TP
-FADV_SEQUENTIAL
-Expect page references in sequential order.
-
-.TP
-FADV_WILLNEED
-Expect access in the near future.
-
-.TP
-FADV_DONTNEED
-Do not expect access in the near future. Subsequent access of pages in this range will succeed, but will result either in reloading of the memory contents from the underlying mapped file or zero-fill-in-demand pages for mappings without an underlying file.
-
-.TP
-FADV_NOREUSE
-Access data only once.
-
-.SH "RETURN VALUE"
-
-.PP
-\fBdelete_module\fR returns 0 on success; otherwise, it returns one of the errors listed in the "Errors" section.
-
-.SH "ERRORS"
-
-.TP
--EBADF
-An invalid file descriptor was specified. to modify the modules.
-
-.TP
--EINVAL
-An invalid \fIf_mapping\fR of \fIfile\fR, \fIlen\fR value smaller than 0 or \fIadvice\fR value unknown.
-
-.SH "SEE ALSO"
-.BR madvise(2)
-\fB\fR
-
-
-.SH AUTHOR
-Niki Rahimi
+.\" Copyright (C) 2004 IBM Corporation
+.\" This file is distributed according to the GNU General Public License.
+.\" See the file COPYING in the top level source directory for details.
+.\"
+
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "FADVISE64,FADVISE64_64" 2 "2004-March-12" "Linux 2.6" "Linux Programmer's Guide"
+.SH NAME
+fadvise64,fadvise64_64 \- Give advice about file access
+.SH "SYNOPSIS"
+.ad l
+.hy 0
+.HP 44
+long\ \fBfadvise64_64\fR
+(int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR, int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR);
+.HP 19
+long\ \fBsys_fadvise64\fR\
+(int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR, int\ \fIfs\fR, loff_t\ \fIoffset\fR, loff_t\ \fIlen\fR, int\ \fIadvice\fR);
+.ad
+.hy
+
+.SH "DESCRIPTION"
+
+.PP
+Allows an application to to tell the kernel how it expects to use a file handle, so that the kernel can choose appropriate read-ahead and caching techniques for access to the corresponding file. This is similar to the POSIX version of the \fBmadvise\fR system call, but for file access instead of memory access. The sys_fadvise64() function is obsolete and corresponds to a broken glibc API, sys_fadvise64_64() is the fixed version.
+The following are the values for the \fIadvice\fR parameter:
+
+.TP
+FADV_NORMAL
+No special treatment.
+
+.TP
+FADV_RANDOM
+Expect page references in random order.
+
+.TP
+FADV_SEQUENTIAL
+Expect page references in sequential order.
+
+.TP
+FADV_WILLNEED
+Expect access in the near future.
+
+.TP
+FADV_DONTNEED
+Do not expect access in the near future. Subsequent access of pages in this range will succeed, but will result either in reloading of the memory contents from the underlying mapped file or zero-fill-in-demand pages for mappings without an underlying file.
+
+.TP
+FADV_NOREUSE
+Access data only once.
+
+.SH "ERRORS"
+
+.TP
+-EBADF
+An invalid file descriptor was specified. to modify the modules.
+
+.TP
+-EINVAL
+An invalid \fIf_mapping\fR of \fIfile\fR, \fIlen\fR value smaller than 0 or \fIadvice\fR value unknown.
+
+.SH "SEE ALSO"
+.BR madvise(2)
+\fB\fR
+
+
+.SH AUTHOR
+Niki Rahimi

View File

@ -0,0 +1,24 @@
--- man-pages-2.43/man5/passwd.5.pom 2006-07-05 14:45:41.000000000 +0200
+++ man-pages-2.43/man5/passwd.5 2007-02-27 12:23:27.000000000 +0100
@@ -45,11 +45,20 @@
basic assumption used to be that of a friendly user-community. These days
many people run some version of the shadow password suite, where
.I /etc/passwd
-has asterisks (*) instead of encrypted passwords,
+has "x" instead of encrypted passwords,
and the encrypted passwords are in
.I /etc/shadow
which is readable by the superuser only.
.PP
+If the encrypted password, whether in /etc/passwd or in /etc/shadow, is
+an empty string, login is allowed without even asking for a password.
+Note that this functionality may be intentionally disabled in applications,
+or configurable (for example using the "nullok" or "nonull" arguments to
+pam_unix.so).
+.PP
+If the encrypted password in /etc/passwd is "*NP*" (without the quotes),
+the shadow record should be obtained from a NIS+ server.
+.PP
Regardless of whether shadow passwords are used, many sysadmins
use an asterisk in the encrypted password field to make sure
that this user can not authenticate him- or herself using a

View File

@ -1,7 +1,7 @@
Summary: Man (manual) pages from the Linux Documentation Project
Name: man-pages
Version: 2.43
Release: 7%{?dist}
Release: 8%{?dist}
License: distributable
Group: Documentation
URL: http://www.kernel.org/pub/linux/docs/manpages/
@ -43,6 +43,8 @@ Patch40: man-pages-2.39-mmap2.patch
Patch41: man-pages-2.43-rt_spm.patch
Patch42: man-pages-2.43-swapon.patch
Patch43: man-pages-2.43-rand.patch
Patch44: man-pages-2.43-fadvise.patch
Patch45: man-pages-2.43-passwd.patch
Buildroot: %{_tmppath}/%{name}-%{version}-root
Autoreq: false
@ -92,6 +94,8 @@ tar xzf %{SOURCE11}
%patch41 -p1
%patch42 -p1
%patch43 -p1
%patch44 -p1
%patch45 -p1
%build
@ -235,7 +239,11 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/en/man*
%changelog
* Thu Feb 15 2007 Ivana Varekova <varekova@redhat.com> 2.43-5
* Tue Feb 27 2007 Ivana Varekova <varekova@redhat.com> 2.43-8
- fix 229870 - bug in fadvise(2)
- fix 229204 - bug in passwd(5)
* Thu Feb 15 2007 Ivana Varekova <varekova@redhat.com> 2.43-7
- fix rand.3 man page (#228662)
thanks Mark Summerfield