On Sun, Apr 19, 2015 at 03:38:57PM +0300, Vadim Zhukov wrote: > This paragraph should talk about prebinding instead of prelinking, > shouldn't it? > > Also, it seems "prebind data" sounds more correct than "prebinding > data", but I could easily get wrong here. > > -- > WBR, > Vadim Zhukov >
ah, can of worms... the options talk about "prebind information", while the prebinding section talks about "prebinding information". it seems logical to stick to one. anyone? comments inline: > > Index: ldconfig.8 > =================================================================== > RCS file: /cvs/src/libexec/ld.so/ldconfig/ldconfig.8,v > retrieving revision 1.27 > diff -u -p -r1.27 ldconfig.8 > --- ldconfig.8 10 Jul 2013 06:43:38 -0000 1.27 > +++ ldconfig.8 19 Apr 2015 12:35:58 -0000 > @@ -113,11 +113,11 @@ List the current contents of > on the standard output. > The hints file will not be modified. > .It Fl S > -Perform prelinking operations in a safe mode; always copies the binaries > -when prelinking data is added to a file. > +Perform prebinding operations in a safe mode; always copies the binaries not your fault, but the semicolon would be better as a colon. i also wonder whether we'd be better writing "in a safe mode" to just "safely". > +when prebind data is added to a file. maybe better to stick to "information" rather than "data" jmc > Use this to eliminate the possibility that > .Dv ETXTBUSY > -will occur when attempting to run a binary while prelinking > +will occur when attempting to run a binary while prebinding > is running. > .It Fl s > Do not scan the built-in system directory >
