On Mi, 29.08.18 12:24, Wojtek Swiatek (w...@swtk.info) wrote:
> Some of these are existing directories, some new ones and then there are
> files (new, but possibly existing as well).
>
> *How should I create a filesystem which has only the files required by the
> packages (= the ones it brings
On 29 August 2018 at 16:14, Wojtek Swiatek wrote:
> Le mer. 29 août 2018 à 17:11, Steve Dodd a écrit :
>> Shouldn't be that hard to adapt one of the above for nspawn?
> nspawn is not the problem - portable services are. I use a minimal image
> with nspawn which is OK but portable services are
Le mer. 29 août 2018 à 17:11, Steve Dodd a écrit :
> On 29 August 2018 at 15:43, Steve Dodd wrote:
>
> Shouldn't be that hard to adapt one of the above for nspawn?
>
>
nspawn is not the problem - portable services are. I use a minimal image
with nspawn which is OK but portable services are
On 29 August 2018 at 15:43, Steve Dodd wrote:
> I'm kind of surprised a tool for this hasn't crossed my path already, [..] I
> also wonder if there might be any
> Docker based tools that do this sort of inspection.
Bingo:
- https://github.com/djosephsen/skinnywhale/blob/master/skinnywhale.sh
I know that this is not the usual answer to that sort of question but
you should try buildroot, rather than base yourself on debian.
When you deactivate the kernel and busybox (it's done through a
menuconfig type interface) you will get the minimal type of system you want.
On
