From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>,
Daniel J Walsh <dwalsh@redhat.com>,
SELinux <SELinux@tycho.nsa.gov>,
Colin Walters <walters@redhat.com>
Subject: Re: Proposed patch for libselinux
Date: Tue, 26 Oct 2004 19:05:23 +0100 [thread overview]
Message-ID: <20041026180523.GE8652@lkcl.net> (raw)
In-Reply-To: <20041026142126.GC8053@lkcl.net>
On Tue, Oct 26, 2004 at 03:21:26PM +0100, Luke Kenneth Casson Leighton wrote:
> i find frequently that ext3 filesystem damage results in fsck.ext3
correction: found.
correction: ext2.
> going "the extended attributes aren't valid: truncating".
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-10-26 17:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 21:35 Proposed patch for libselinux Daniel J Walsh
2004-10-22 12:48 ` Stephen Smalley
2004-10-22 13:22 ` Daniel J Walsh
2004-10-22 13:44 ` Stephen Smalley
2004-10-22 14:22 ` Daniel J Walsh
2004-10-22 15:56 ` Luke Kenneth Casson Leighton
2004-10-22 19:55 ` Daniel J Walsh
2004-10-22 20:22 ` Daniel J Walsh
2004-10-25 14:52 ` Stephen Smalley
2004-10-25 15:31 ` Colin Walters
2004-10-25 18:00 ` Daniel J Walsh
2004-10-26 14:21 ` Luke Kenneth Casson Leighton
2004-10-26 14:13 ` Stephen Smalley
2004-10-26 15:21 ` Luke Kenneth Casson Leighton
2004-10-26 18:05 ` Luke Kenneth Casson Leighton [this message]
2004-10-29 23:28 ` Proposed patch for libselinux -- xdr ??? Nifty Hat Mitch
2004-10-22 13:23 ` Proposed patch for libselinux Stephen Smalley
2004-10-22 13:45 ` Daniel J Walsh
2004-10-22 14:15 ` Stephen Smalley
2004-10-22 14:24 ` Daniel J Walsh
2004-10-22 14:30 ` Stephen Smalley
2004-10-22 18:01 ` Daniel J Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041026180523.GE8652@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=sds@epoch.ncsc.mil \
--cc=walters@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.