On Thu, Jun 04, 2020 at 05:48:34AM +0700, Robert Elz wrote:
> And of course, I should have really read mtree(1) before replying,
> so the suggested method would just be
>
> grep whatever original-spec-file [ | grep otherstuff ] | mtree
I ended up not using mtree for this, as it was getting
Date:Thu, 04 Jun 2020 05:45:01 +0700
From:Robert Elz
Message-ID: <1215.1591224...@jinx.noi.kre.to>
| If a change/addition to mtree is desirable, [...]
And of course, I should have really read mtree(1) before replying,
so the suggested method would just be
Date:Tue, 2 Jun 2020 16:14:20 +0200
From:Martin Husemann
Message-ID: <20200602141420.ga5...@mail.duskware.de>
| I would like to create directory hierachies from mtree spec files, but
| restrict this to selected hierachies (where the mtree files contain a
| bit m
On Wed, Jun 03, 2020 at 05:22:39PM +, nia wrote:
> While trying to accurately replicate NetBSD's struct addrinfo for
> crystal[0], I noticed this pattern occurs twice in netdb.h...
>
> #if defined(__alpha__) || (defined(__i386__) && defined(_LP64))
> int __ai_pad0; /*
While trying to accurately replicate NetBSD's struct addrinfo for
crystal[0], I noticed this pattern occurs twice in netdb.h...
#if defined(__alpha__) || (defined(__i386__) && defined(_LP64))
int __ai_pad0; /* ABI compatibility */
#endif
This was added in 2004 in response
On Tue, Jun 02, 2020 at 04:14:20PM +0200, Martin Husemann wrote:
> So in above example I could create a "onlyfile" containing something like:
>
> ./var
> ./var/*
> ./var/*/*
> ./var/*/*/*
> ./var/*/*/*/*
> ./var/*/*/*/*/*
>
> or so I thought - but (a) it does n
