public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Randy Zagar <zagar@arlut.utexas.edu>
To: linux-audit@redhat.com
Subject: Re: Linux-audit Digest, Vol 47, Issue 12
Date: Thu, 14 Aug 2008 09:35:43 -0500	[thread overview]
Message-ID: <48A442BF.6050204@arlut.utexas.edu> (raw)
In-Reply-To: <20080814140427.18C0861A30F@hormel.redhat.com>


On Wednesday 13 August 2008 13:02:05 Steve Grub wrote:
> On Wednesday 13 August 2008 12:25:09 Klaus Heinrich Kiwi wrote:
>> > I like Mathew's idea of having a binary format though. Maybe it's
>> > possible to carry the legacy format for some time while we have a more
>> > robust (and extensible) binary format in parallel? And then having a
>> > binary format version tag within each record?
>>     
>
> Yes, there would have to be a migration path. I think we talked about XDR as a 
> possibility 4 years ago because its already inside the kernel. The kernel 
> guys at the time wanted to re-use something already inside or something that 
> was compact in its representation.
>
> What I believe lead to text based was the general feeling that logs should be 
> human readable with less, tail, or vi if need be.
>
> A problem with binary representations will be what happens with aggregated 
> big-endian and little-endian system logs?
>   
Aggregated logs from big-endian and little-endian systems should not be 
a problem if you use XDR...  the endian-ness of the cpu is completely 
irrelevant.

IMHO, text would be preferable, but I don't have a dog in this fight...

-RZ

-- 
Randy Zagar                               Sr. Unix Systems Administrator
E-mail: zagar@arlut.utexas.edu            Applied Research Laboratories
Phone: 512 835-3131                       Univ. of Texas at Austin

           reply	other threads:[~2008-08-14 14:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20080814140427.18C0861A30F@hormel.redhat.com>]

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=48A442BF.6050204@arlut.utexas.edu \
    --to=zagar@arlut.utexas.edu \
    --cc=linux-audit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox