On 15 Sep 2016 03:21, "Patrick Williams" <patr...@stwcx.xyz> wrote:
> 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
> > issue not handling hardlinks correctly:
> > 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.
Mine too. I don't really care, soft links are surely more obvious, though.
Openembedded-core mailing list