From: support@eggplantsd.com
To: linux-kernel@vger.kernel.org
Subject: utmp Format
Date: Thu, 01 Aug 2024 12:41:48 -0400 [thread overview]
Message-ID: <54294c74eaa90ba149089c6aa49dd798@eggplantsd.com> (raw)
I've noticed a difference in the size of the `utmp` struct between Linux
6.1.0-22-amd64 and 6.1.0-23-cloud-arm64. No doubt there are differences
between other unices as well. Is there a reason this is still a binary
log? On 6.1.0-22-amd64, it seems to be 384 bytes long, while the
average line length from `utmpdump` is only 125 bytes, so it's not a
space savings.
My primary concern is forensics. There is no consistent and reliable
way to read wtmp/btmp outside of the installation that created it.
JS
reply other threads:[~2024-08-01 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54294c74eaa90ba149089c6aa49dd798@eggplantsd.com \
--to=support@eggplantsd.com \
--cc=linux-kernel@vger.kernel.org \
/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