I had this exact issue a few days ago, I just re-partitioned to a bigger size 
so not have to face the issue again as was a new install anyway. But, sure 
would be nice to see this added. Thanks

> -------- Original Message --------
> Subject: Re: syspatch question
> Local Time: August 8, 2017 4:20 PM
> UTC Time: August 8, 2017 3:20 PM
> From: marko.cu...@mimar.rs
> To: Antoine Jacoutot <ajacou...@bsdfrog.org>
> misc@openbsd.org, Igor Falcomata' <k...@cioccolatai.it>
> On Tue, 08 Aug 2017 13:14:43 +0200
> Antoine Jacoutot <ajacou...@bsdfrog.org> wrote:
>> I"ll have a look at it thanks.
> I"m aware that noone is going to optimize syspatch for my corner case,
> but here are a few observations regarding my experience with it:
> - at the moment of writing this, there are 025 patches. If applying
> them all at once, they (perhaps needlessly) need quite some space
> in /tmp (my mfs for /tmp is 256m, and it got filled already at 012),
> as a result of (I guess) deleting /tmp/syspatch.XXXXXXXXXX only
> after all the patches are applied, or after /tmp gets filled up.
> Perhaps it is possible to flush /tmp earlier in the process (maybe
> after each patch is applied successfully)?
> - syspatch silently fails if it cannot contact installurl server.
> Perhaps some warning could be added?
> Best regards,
> --
> Before enlightenment - chop wood, draw water.
> After enlightenment - chop wood, draw water.
> Marko Cupać
> https://www.mimar.rs/

Reply via email to