Re: Remove TMPDIR support from sendbug(1) and newfs(8) manpages

2016-02-18 Thread Jason McIntyre
On Thu, Feb 18, 2016 at 03:11:16PM -0700, Rafael Neves wrote:
> Hi,
> 
> The TMPDIR enviroment support was removed from sendbug(1) and newfs(8),
> but the manpages still document them. The inlined patches remove these
> leftovers.
> 
> Regards,
> Rafael Neves
> 

fixed, thanks.
jmc

> 
> Patch:
> 
> Index: sbin/newfs/newfs.8
> =======
> RCS file: /cvs/src/sbin/newfs/newfs.8,v
> retrieving revision 1.71
> diff -u -p -r1.71 newfs.8
> --- sbin/newfs/newfs.829 Aug 2014 12:09:04 -  1.71
> +++ sbin/newfs/newfs.818 Feb 2016 20:57:39 -
> @@ -301,14 +301,6 @@ If the
>  .Fl P Ar file
>  option is not used, the owner and mode of the created mfs file
>  system will be the same as the owner and mode of the mount point.
> -.Sh ENVIRONMENT
> -.Bl -tag -width TMPDIR
> -.It Ev TMPDIR
> -Directory in which to create temporary mount points for use by
> -.Nm mount_mfs Fl P
> -instead of
> -.Pa /tmp .
> -.El
>  .Sh SEE ALSO
>  .Xr disktab 5 ,
>  .Xr fs 5 ,
> Index: usr.bin/sendbug/sendbug.1
> ===
> RCS file: /cvs/src/usr.bin/sendbug/sendbug.1,v
> retrieving revision 1.26
> diff -u -p -r1.26 sendbug.1
> --- usr.bin/sendbug/sendbug.1 11 Oct 2015 21:23:15 -  1.26
> +++ usr.bin/sendbug/sendbug.1 18 Feb 2016 20:57:48 -
> @@ -103,10 +103,6 @@ the default is
>  Filename of PR form to use instead of using the built-in form.
>  Such a PR form can be partially pre-completed to make the
>  process faster.
> -.It Ev TMPDIR
> -Specifies a directory for temporary files to be created.
> -The default is
> -.Pa /tmp .
>  .El
>  .Sh FILES
>  .Bl -tag -width "/tmp/p.XX" -compact
> 



Remove TMPDIR support from sendbug(1) and newfs(8) manpages

2016-02-18 Thread Rafael Neves
Hi,

The TMPDIR enviroment support was removed from sendbug(1) and newfs(8),
but the manpages still document them. The inlined patches remove these
leftovers.

Regards,
Rafael Neves


Patch:

Index: sbin/newfs/newfs.8
===
RCS file: /cvs/src/sbin/newfs/newfs.8,v
retrieving revision 1.71
diff -u -p -r1.71 newfs.8
--- sbin/newfs/newfs.8  29 Aug 2014 12:09:04 -  1.71
+++ sbin/newfs/newfs.8  18 Feb 2016 20:57:39 -
@@ -301,14 +301,6 @@ If the
 .Fl P Ar file
 option is not used, the owner and mode of the created mfs file
 system will be the same as the owner and mode of the mount point.
-.Sh ENVIRONMENT
-.Bl -tag -width TMPDIR
-.It Ev TMPDIR
-Directory in which to create temporary mount points for use by
-.Nm mount_mfs Fl P
-instead of
-.Pa /tmp .
-.El
 .Sh SEE ALSO
 .Xr disktab 5 ,
 .Xr fs 5 ,
Index: usr.bin/sendbug/sendbug.1
===
RCS file: /cvs/src/usr.bin/sendbug/sendbug.1,v
retrieving revision 1.26
diff -u -p -r1.26 sendbug.1
--- usr.bin/sendbug/sendbug.1   11 Oct 2015 21:23:15 -  1.26
+++ usr.bin/sendbug/sendbug.1   18 Feb 2016 20:57:48 -
@@ -103,10 +103,6 @@ the default is
 Filename of PR form to use instead of using the built-in form.
 Such a PR form can be partially pre-completed to make the
 process faster.
-.It Ev TMPDIR
-Specifies a directory for temporary files to be created.
-The default is
-.Pa /tmp .
 .El
 .Sh FILES
 .Bl -tag -width "/tmp/p.XX" -compact



Re: newfs.8

2014-08-29 Thread Jason McIntyre
On Fri, Aug 29, 2014 at 12:13:58AM -0400, Navan Carson wrote:
 disklabel is not required for mount_mfs
 
 Index: newfs.8
 ===
 RCS file: /cvs/src/sbin/newfs/newfs.8,v
 retrieving revision 1.70
 diff -u -p -r1.70 newfs.8
 --- newfs.8   23 May 2011 10:56:17 -  1.70
 +++ newfs.8   29 Aug 2014 04:10:54 -
 @@ -72,9 +72,7 @@
  .Ek
  .Sh DESCRIPTION
  Before running
 -.Nm
 -or
 -.Nm mount_mfs ,
 +.Nm ,
  the disk must be labeled using
  .Xr disklabel 8 .
  .Nm
 

is this correct? i'm not a user myself, but the text states that
special, for mount_mfs, is typically that of the primary swap area.
how would you even define the swap area without a disklabel?

jmc



Re: newfs.8

2014-08-29 Thread Mike Belopuhov
On 29 August 2014 08:19, Jason McIntyre j...@kerhand.co.uk wrote:

 is this correct? i'm not a user myself, but the text states that
 special, for mount_mfs, is typically that of the primary swap area.
 how would you even define the swap area without a disklabel?

 jmc


sort of yes.  mount_mfs(8) says this:

 [...] The special file is only used
 to read the disk label which provides a set of configuration parameters
 for the memory based file system.  The special file is typically that of
 the primary swap area, since that is where the file system will be backed
 up when free memory gets low and the memory supporting the file system
 has to be paged.  If the keyword ``swap'' is used instead of a special
 file name, default configuration parameters will be used.  (This option
 is useful when trying to use mount_mfs on a machine without any disks.)

in reality it fakes up a disklabel and proceeds.  number of XXX's
around this code is also mildly amusing...



Re: newfs.8

2014-08-29 Thread Jason McIntyre
On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
 On 29 August 2014 08:19, Jason McIntyre j...@kerhand.co.uk wrote:
 
  is this correct? i'm not a user myself, but the text states that
  special, for mount_mfs, is typically that of the primary swap area.
  how would you even define the swap area without a disklabel?
 
  jmc
 
 
 sort of yes.  mount_mfs(8) says this:
 
  [...] The special file is only used
  to read the disk label which provides a set of configuration parameters
  for the memory based file system.  The special file is typically that of
  the primary swap area, since that is where the file system will be backed
  up when free memory gets low and the memory supporting the file system
  has to be paged.  If the keyword ``swap'' is used instead of a special
  file name, default configuration parameters will be used.  (This option
  is useful when trying to use mount_mfs on a machine without any disks.)
 
 in reality it fakes up a disklabel and proceeds.  number of XXX's
 around this code is also mildly amusing...
 

so the diff posted was correct and should be committed?
jmc



Re: newfs.8

2014-08-29 Thread Mike Belopuhov
On 29 August 2014 13:44, Jason McIntyre j...@kerhand.co.uk wrote:
 On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
 On 29 August 2014 08:19, Jason McIntyre j...@kerhand.co.uk wrote:
 
  is this correct? i'm not a user myself, but the text states that
  special, for mount_mfs, is typically that of the primary swap area.
  how would you even define the swap area without a disklabel?
 
  jmc
 

 sort of yes.  mount_mfs(8) says this:

  [...] The special file is only used
  to read the disk label which provides a set of configuration parameters
  for the memory based file system.  The special file is typically that of
  the primary swap area, since that is where the file system will be 
 backed
  up when free memory gets low and the memory supporting the file system
  has to be paged.  If the keyword ``swap'' is used instead of a special
  file name, default configuration parameters will be used.  (This option
  is useful when trying to use mount_mfs on a machine without any disks.)

 in reality it fakes up a disklabel and proceeds.  number of XXX's
 around this code is also mildly amusing...


 so the diff posted was correct and should be committed?
 jmc


yes, i believe so.  OK mikeb



Re: newfs.8

2014-08-29 Thread Jason McIntyre
On Fri, Aug 29, 2014 at 01:48:15PM +0200, Mike Belopuhov wrote:
 On 29 August 2014 13:44, Jason McIntyre j...@kerhand.co.uk wrote:
  On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
  On 29 August 2014 08:19, Jason McIntyre j...@kerhand.co.uk wrote:
  
   is this correct? i'm not a user myself, but the text states that
   special, for mount_mfs, is typically that of the primary swap area.
   how would you even define the swap area without a disklabel?
  
   jmc
  
 
  sort of yes.  mount_mfs(8) says this:
 
   [...] The special file is only used
   to read the disk label which provides a set of configuration 
  parameters
   for the memory based file system.  The special file is typically that 
  of
   the primary swap area, since that is where the file system will be 
  backed
   up when free memory gets low and the memory supporting the file system
   has to be paged.  If the keyword ``swap'' is used instead of a special
   file name, default configuration parameters will be used.  (This 
  option
   is useful when trying to use mount_mfs on a machine without any 
  disks.)
 
  in reality it fakes up a disklabel and proceeds.  number of XXX's
  around this code is also mildly amusing...
 
 
  so the diff posted was correct and should be committed?
  jmc
 
 
 yes, i believe so.  OK mikeb
 

ok, committed. thanks for the diff, navan.
jmc



newfs.8

2014-08-28 Thread Navan Carson
disklabel is not required for mount_mfs

Index: newfs.8
===
RCS file: /cvs/src/sbin/newfs/newfs.8,v
retrieving revision 1.70
diff -u -p -r1.70 newfs.8
--- newfs.8 23 May 2011 10:56:17 -  1.70
+++ newfs.8 29 Aug 2014 04:10:54 -
@@ -72,9 +72,7 @@
 .Ek
 .Sh DESCRIPTION
 Before running
-.Nm
-or
-.Nm mount_mfs ,
+.Nm ,
 the disk must be labeled using
 .Xr disklabel 8 .
 .Nm