From: Patrick Williams <patrick@stwcx.xyz>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] e2fsprogs: configure with enable-symlink
Date: Wed, 14 Sep 2016 21:21:02 -0500 [thread overview]
Message-ID: <20160915022102.GA25351@heinlein.lan> (raw)
In-Reply-To: <CA+chaQfb_L2VZUXiK07rd4aBUn508CjtWp1R1R8weYHUaJHRSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Wed, Sep 14, 2016 at 11:23:47PM +0200, Martin Jansa wrote:
> It was also proposed and discussed some 15 months ago and it was packaging
> issue not handling hardlinks correctly:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/103939.html
>
> I believe this was fixed then, but maybe it got broken again?
Sorry, this is my fault. I didn't think about hard-links. I was just
skimming the cpio extract for parts that could be trimmed out and
noticed it.
$ ls -i *fsck*
19455718 e2fsck
19455671 fsck
19455718 fsck.ext2
19455718 fsck.ext3
19455718 fsck.ext4
19455718 fsck.ext4dev
19455679 fsck.minix
19455695 fsck.minix.util-linux
19455675 fsck.util-linux
Is there a reason to prefer hardlinks over softlinks, for my own
education? My desktop system used softlinks for fsck.
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-09-15 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 16:25 [PATCH] e2fsprogs: configure with enable-symlink Patrick Williams
2016-09-14 19:50 ` André Draszik
2016-09-14 21:23 ` Martin Jansa
2016-09-15 2:21 ` Patrick Williams [this message]
2016-09-15 7:11 ` André Draszik
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=20160915022102.GA25351@heinlein.lan \
--to=patrick@stwcx.xyz \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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