Paul Raines <[EMAIL PROTECTED]> wrote:
> When one runs /bin/pwd (using coreutils 5.97) on an autofs mounted
> volume, it causes an fstat to be run on all autofs mounted volumes
> on that automount's mount point. THis is not only a big waste but
> if a NFS mount server down it causes /bin/pwd to ha
Ondřej Vašík <[EMAIL PROTECTED]> wrote:
> Thanks for review and suggested/requested changes. Here is amended patch
> with all of your changes(and similar changes for runcon).
Thanks, but your new patch would have actually reverted some of
my changes, so I've adjusted it and made some more.
Here's
césar beleño d. wrote:
> Hi, I recently installed kubuntu 8.10 beta in my computer from internet.
> Previously I had ubuntu 8.04 and I had downloaded some applications from KDE
> such as kile and k3b, but these applications was not working. This were the
> mean reason for I decided install kubunt
Hi, I recently installed kubuntu 8.10 beta in my computer from internet.
Previously I had ubuntu 8.04 and I had downloaded some applications from KDE
such as kile and k3b, but these applications was not working. This were the
mean reason for I decided install kubuntu, but any sesion is not opening
When one runs /bin/pwd (using coreutils 5.97) on an autofs mounted
volume, it causes an fstat to be run on all autofs mounted volumes
on that automount's mount point. THis is not only a big waste but
if a NFS mount server down it causes /bin/pwd to hang. /bin/pwd
in perfectly working NFS mount
Ondřej Vašík <[EMAIL PROTECTED]> wrote:
...
> Thanks for review and suggested/requested changes. Here is amended patch
> with all of your changes(and similar changes for runcon).
Thanks!
Looking at it now.
One quick note; please don't add trailing blanks.
It's easy for me to remove them, but I sho
Nicholas Leippe <[EMAIL PROTECTED]> wrote:
> On Tuesday 07 October 2008 05:58:19 am you wrote:
>> Nicholas Leippe <[EMAIL PROTECTED]> wrote:
>> > Currently, du -x properly excludes other filesystems that are mounted.
>> > But if the same filesystem is mounted again with -o bind (linux,
> possibly
Hello,
as documented in NEWS and as written in test cp-a-selinux, cp -a should
try to preserve selinux context, if possible. The activation boolean
preserve_security_context was missing in this branch. Also cp -a is not
really equivalent to -dpR, but to -dR --preserve-all , as it tries(or at
least
Hi,
HggdH <[EMAIL PROTECTED]> wrote:
...
> I noticed there is https://savannah.gnu.org/support/?group=coreutils
> where we could submit downstream issues. But it seems this is not much
> used.
>
> So the question: is the BTS to be used at all, or should one just email
> bug-coreutils?
Whichever y
Hello,
I have been following the bug-coreutils mailist for a while, in order to
get myself adjusted to the expected processes and procedures.
I noticed there is https://savannah.gnu.org/support/?group=coreutils
where we could submit downstream issues. But it seems this is not much
used.
So the q
Hi,
Jim Meyering wrote:
> Ondřej Vašík <[EMAIL PROTECTED]> wrote:
> > as those commands were not documented in info documentation, I wrote
> > basic info documentation for runcon and chcon command (and related
> > SELinux context menu section). It is completely based on man
> > documentation, I wo
Nicholas Leippe <[EMAIL PROTECTED]> wrote:
> Currently, du -x properly excludes other filesystems that are mounted.
> But if the same filesystem is mounted again with -o bind (linux, possibly
> other oses), it still includes them in the count.
>
> An option to exclude them from the count as well wo
Giuseppe Scrivano wrote:
> Hello,
>
> what do you think about the following way to remove the sigs_to_ignore
> hack in the timeout.c file?
> It ignores temporarily the signal inside the `send_sig' function instead
> of using the `sigs_to_ignore' array.
I'll test this tonight, as this stuff is tri
Ondřej Vašík <[EMAIL PROTECTED]> wrote:
> as those commands were not documented in info documentation, I wrote
> basic info documentation for runcon and chcon command (and related
> SELinux context menu section). It is completely based on man
> documentation, I would say just the first step to have
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
...
>> s/is/may be/
>> Early reader termination may still deserve a diagnostic.
>> Or it could be that POSIX requires the application to diagnose EPIPE,
>> regardless ;-)
>
> I disagree here. If early reader termination leads to a diagno
15 matches
Mail list logo