[DNG] Our servers are unreachable (Current outage at OVH)

2017-11-09 Thread KatolaZ 
Dear Dev1rs,

just to let you know that due to an OVH outage most of our services
are currently unreachable. We will post updates here in due course.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] [SOLVED] Re: Our servers are unreachable (Current outage at OVH)

2017-11-09 Thread John Hughes 

On 09/11/17 13:08, KatolaZ wrote:

just to let you know that the outage at OVH has been resolved, and all
our services are now back online. None of the machines was actually
rebooted, so it seems it was just a network issue on the OVH site.


Lucky you.  Mine is still in some kind of routing maze -- packets get to 
TATA in London then get lost in the wilderness.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] [SOLVED] Re: Our servers are unreachable (Current outage at OVH)

2017-11-09 Thread KatolaZ 
On Thu, Nov 09, 2017 at 09:01:23AM +, KatolaZ wrote:
> Dear Dev1rs,
> 
> just to let you know that due to an OVH outage most of our services
> are currently unreachable. We will post updates here in due course.
> 

Dear Dev1rs,

just to let you know that the outage at OVH has been resolved, and all
our services are now back online. None of the machines was actually
rebooted, so it seems it was just a network issue on the OVH site.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] / on lvm2 volume (was Re: WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable)

2017-11-09 Thread Olaf Meeuwissen 
Hi Rick,

Rick Moen writes:

> Quoting Olaf Meeuwissen (paddy-h...@member.fsf.org):
>
>> I used to mount /usr read-only on my server machines but that quickly
>> becomes a bore when you need to install security upgrades every so
>> often.
>
> Suggestion:  Make remounting an automatic part of package operations.
>
> /etc/apt/apt.conf:
>
> DPkg {
> // Auto re-mounting of a read-only /usr
> Pre-Invoke { "mount -o remount,rw /usr"; };
> Post-Invoke { "test ${NO_APT_REMOUNT:-no} = yes || mount -o remount,ro 
> /usr || true"; };
> };

I don't know how long this has been available but had I been aware of
it, I would have used it way back when I used to mount /usr read-only.
That's been a while ... maybe 10 years or so ;-)

Actually, staring at this, I may have done something like that and was
not quite happy with how it worked (or not) and just stopped mounting
/usr read-only.  Or maybe I just stopped putting /usr on a file system
of its own (when I started using LVM).  I honestly cannot remember why
and what.

Thanks anyway,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OT: MX-Linux 17 Beta1

2017-11-09 Thread KatolaZ 
On Thu, Nov 09, 2017 at 04:54:17PM +, leloft wrote:
> On Wed, 8 Nov 2017 19:11:13 +
> KatolaZ  wrote:
> 
> > If you are on Devuan Jessie you can just simply *upgrade* to Devuan
> > Ascii. There is no need to start from another distribution. Just
> > replace "jessie" with "ascii" in your sources.list, and then
> > 
> >   apt-get update && apt-get dist-upgrade
> > 
> > My2cents
> > 
> > KatolaZ
> 
> Worked like a charm (~1500 packages, 750mb, less than a couple of hours
> downtime).  One observation: although the dist-upgrade was
> performed over ssh, the installation of glibc was halted because xdm
> was active; the option to continue was ignored and the interrupted
> upgrade process had to be resumed with an 'apt-get install -f ' to fix
> broken dependencies before re-issuing the 'apt-get dist-upgrade' which
> ran to completion without a hitch.
> 

Hi leloft,

if you have a log of the upgrade, we can have a look into it. It is
not too unusual to have to issue an "apt-get -f install" during a
dist-upgrade, depending on how much up-to-date your distro was and on
how many releases had passed since you did your first fresh install (I
am sure I am not alone in having had a server with a Sarge/testing,
which got all the way through Wheezy/stable over 7 or 8 years).

HH

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Problem with xorg on 6th gen Intel cpus

2017-11-09 Thread KatolaZ 
On Thu, Nov 09, 2017 at 04:41:11PM +, jack da wrote:
> hello Joel,
> 
> thanks for your reply.  I have moved on to Salix, which, unlike its
> Slackware parent, has apt-like dependency resolution and is as [un]reliable
> as any of the non-systemd distros that I have evaluated/used on my travels.
> 
> Suffice to say that I have tried different devuan-based distros, and
> compiled my own recent module-free, custom kernel - nothing I tried
> worked.  Since this matter was registered as a bug/issue with the devuan
> project, I received little feedback.  When my 6th-gen intel boxes start to
> die and be replaced by amd/arm [losing faith in intel], I may give devuan
> another try.
> 

Hi Jack,

I have been using devuan on a i5-6200U for almost two years now, and
without any problem. It was first a jessie, which was later upgraded
to an ascii. Everything works. I must note that I am using the Intel
video card (I don't remember if you had anything else instead). With
kernel 4.5, 4.7, 4.9, 4.11, everything works fine, even the HDMI
output port (that I use quite a lot).

Hope this helps.

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] / on lvm2 volume (was Re: WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable)

2017-11-09 Thread Rick Moen 
Quoting Olaf Meeuwissen (paddy-h...@member.fsf.org):

> I don't know how long this has been available but had I been aware of
> it, I would have used it way back when I used to mount /usr read-only.
> That's been a while ... maybe 10 years or so ;-)
> 
> Actually, staring at this, I may have done something like that and was
> not quite happy with how it worked (or not) and just stopped mounting
> /usr read-only.  Or maybe I just stopped putting /usr on a file system
> of its own (when I started using LVM).  I honestly cannot remember why
> and what.
> 
> Thanks anyway,

You're very welcome.  For interested parties, there's more here:
https://lists.debian.org/debian-devel/2001/11/msg00212.html

(That's a comprehensive mail on the subject by Anthony Towns.)

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Problem with xorg on 6th gen Intel cpus

2017-11-09 Thread jack da 
hello Joel,

thanks for your reply.  I have moved on to Salix, which, unlike its
Slackware parent, has apt-like dependency resolution and is as [un]reliable
as any of the non-systemd distros that I have evaluated/used on my travels.

Suffice to say that I have tried different devuan-based distros, and
compiled my own recent module-free, custom kernel - nothing I tried
worked.  Since this matter was registered as a bug/issue with the devuan
project, I received little feedback.  When my 6th-gen intel boxes start to
die and be replaced by amd/arm [losing faith in intel], I may give devuan
another try.

JackSprat

ps:  I have never been sucessful in getting a vesa driver to work, either
with a template /etc/X11/xorg.conf or fragments in xorg.conf.d/.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] AMD: Was Problem with xorg on 6th gen Intel cpus

2017-11-09 Thread Rick Moen 
Quoting Steve Litt (sl...@troubleshooters.com):

> After Rick's posted Minix on Intel article, I'm going to stick with AMD
> even if it's more expensive, slower and hotter (and I'm not saying any
> of those things are true).

I'm honestly not sure that AMD CPUs are a substantial improvement in
this particular area, given that they sport a competitor to Intel ME &
AMT called Platform Security Processor (PSP), which is an ARM core with
TrustZone technology, built onto the main CPU die.  See:
https://libreboot.org/faq.html#amd

AMD have been looking into ways to permit users/admins to disable the
PSP in ways analogous to how Intel ME version 11 can be disabled at the
end of boot-up.

https://www.reddit.com/r/Amd/comments/5x4hxu/we_are_amd_creators_of_athlon_radeon_and_other/def5h1b/

Pick your own poison, but one might argue that you're better off with
Intel where most CPUs have the ME firmware in the Memory Controller Hub
or Platform Controller Hub circuitry but not the AMT code (in
'vPro'-branded CPUs only) without which the ME firmware is inert, and
where even when Intel's AMT code is there it's usually not enabled.
_And_ disabling ME version 11 is now possible using me_cleaner.

(For more, I recommend a close reading of Matthew Garrett's pice about
ME/AMT.)

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OT: MX-Linux 17 Beta1

2017-11-09 Thread leloft 
On Wed, 8 Nov 2017 19:11:13 +
KatolaZ  wrote:

> If you are on Devuan Jessie you can just simply *upgrade* to Devuan
> Ascii. There is no need to start from another distribution. Just
> replace "jessie" with "ascii" in your sources.list, and then
> 
>   apt-get update && apt-get dist-upgrade
> 
> My2cents
> 
> KatolaZ

Worked like a charm (~1500 packages, 750mb, less than a couple of hours
downtime).  One observation: although the dist-upgrade was
performed over ssh, the installation of glibc was halted because xdm
was active; the option to continue was ignored and the interrupted
upgrade process had to be resumed with an 'apt-get install -f ' to fix
broken dependencies before re-issuing the 'apt-get dist-upgrade' which
ran to completion without a hitch.

Respect to the devs.



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Planned manintainance on dev1galaxy.org -- Thu. 9th Nov. 2017 -- 21:00 (UTC) - 23:00 (UTC)

2017-11-09 Thread KatolaZ 
On Thu, Nov 09, 2017 at 12:12:35AM +, KatolaZ wrote:
> Dear Dev1rs,
> 
> this email is to announce that the Devuan web forum on dev1galaxy.org
> will be unreachable due to planned manintainance in the following time
> slot:
> 
>     Thu. 9th Nov. 2017 -- 21:00 (UTC) - 23:00 (UTC) 
> 


Dear Dev1rs,

just to confirm that the maintainance on dev1galaxy.org will happen as
planned. As a consequence the service will *not* be available in the
following time slot:

  ** TODAY Thu. 9th Nov. 2017 -- 21:00 (UTC) - 23:00 (UTC) **

We will send an email here as soon as the maintainance task will be
completed.

HND

KatolaZ


-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] AMD: Was Problem with xorg on 6th gen Intel cpus

2017-11-09 Thread Steve Litt 
On Thu, 9 Nov 2017 16:41:11 +
jack da  wrote:

> When my 6th-gen intel
> boxes start to die and be replaced by amd/arm [losing faith in
> intel], I may give devuan another try.

After Rick's posted Minix on Intel article, I'm going to stick with AMD
even if it's more expensive, slower and hotter (and I'm not saying any
of those things are true).

SteveT

Steve Litt 
October 2017 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] AMD: Was Problem with xorg on 6th gen Intel cpus

2017-11-09 Thread Steve Litt 
On Thu, 9 Nov 2017 09:58:24 -0800
Rick Moen  wrote:

> Quoting Steve Litt (sl...@troubleshooters.com):
> 
> > After Rick's posted Minix on Intel article, I'm going to stick with
> > AMD even if it's more expensive, slower and hotter (and I'm not
> > saying any of those things are true).  
> 
> I'm honestly not sure that AMD CPUs are a substantial improvement in
> this particular area, given that they sport a competitor to Intel ME &
> AMT called Platform Security Processor (PSP), which is an ARM core
> with TrustZone technology, built onto the main CPU die.  See:
> https://libreboot.org/faq.html#amd
> 
> AMD have been looking into ways to permit users/admins to disable the
> PSP in ways analogous to how Intel ME version 11 can be disabled at
> the end of boot-up.
> 
> https://www.reddit.com/r/Amd/comments/5x4hxu/we_are_amd_creators_of_athlon_radeon_and_other/def5h1b/
> 
> Pick your own poison, but one might argue that you're better off with
> Intel where most CPUs have the ME firmware in the Memory Controller
> Hub or Platform Controller Hub circuitry but not the AMT code (in
> 'vPro'-branded CPUs only) without which the ME firmware is inert, and
> where even when Intel's AMT code is there it's usually not enabled.
> _And_ disabling ME version 11 is now possible using me_cleaner.

Oh I give up!

 
SteveT

Steve Litt 
October 2017 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Different philosophies

2017-11-09 Thread Steve Litt 
Hi all,

I ran across this in the Dia mailing list:

https://mail.gnome.org/archives/dia-list/2017-November/msg6.html

Unfortunately, everyone top posted, so time sequence goes bottom to
top. But it's pretty clear what happened. One guy sees no email,
questions or announcements, and pronounces the project dead. Another
guy sees the same thing and pronounces it stable. Sound familiar?

Every day of my life, 480 times per day, I use fetchmail. Penned by
Eric Raymond (yes, he's a real programmer) in the 20th century, it does
one thing and does it well, exactly like it did in the 20th century, so
unless Unix changes radically or someone discovers a vulnerability
other than the theoretical ones postulated by its detractors, it will
work forever. I don't care if fetchmail is still "maintained." It's
probably simple enough that if things go south, *I* could maintain it.

I have the "if it works, don't fix it" mentality. Others wait in line
for hours to spend $600 replacing their perfectly functioning phones
with a phone 1 year newer and a couple features more encumbered. If
Apple failed to market a new phone for 2 years, these people would
probably figure Apple's dead and go with a more technology-churning
competitor.

There's a divergence of philosophies here. One side asks "is it fit for
the purpose", while the other side exudes "wow, look at all these new
features I can have fun with."

Even when the current thing arguably is no longer fit for the purpose,
these philosophies diverge in their actions. The fit for purpose crowd
finds the simplest, easiest solution fit for the purpose (runit or s6,
for instance), while the "cool new features" crowd picks up the
shiniest alternative most bejewelled with irrelevant features, and if
this shiny alternative isn't fit for the purpose, they argue that it is.

SteveT

Steve Litt 
October 2017 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OT: MX-Linux 17 Beta1

2017-11-09 Thread leloft 
On Thu, 9 Nov 2017 17:07:35 +
KatolaZ  wrote:
 
> not too unusual to have to issue an "apt-get -f install" during a
> dist-upgrade, depending on how much up-to-date your distro was and on
> how many releases had passed since you did your first fresh install


last fresh install on that machine was debian
Jessie about 24 months ago, upgraded that to devuan jessie about 6
months ago and to ascii today. Everything here gets updated within a 
day of a relevant security notification from debian.  

> if you have a log of the upgrade, we can have a look into it.

I've extracted bits of /var/log/auth.log /var/log/apt/history.log
and /var/log/dpkg.log and stuck them together in chronological order in
one text file (166 KB) if that's any use to you, and i'm happy to
include more if you tell me where to look.  But the machine is happy
(and more importantly, so's the boss...).






___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] [SOLVED] Planned manintainance on dev1galaxy.org -- Thu. 9th Nov. 2017

2017-11-09 Thread KatolaZ 
Dear Dev1rs,

just to let you know that the maintainance on dev1galaxy.org is now
complete (Thu. 9th Nov 2017 22:08). The server is up and running
again.

Thanks for your patience.

The Dev1Devs

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Different philosophies

2017-11-09 Thread Nate Bargmann 
Well stated, Steve.

I've been using Fetchmail for almost 19 years. Rock solid reliability,
day after day, several times per hour.  I've also used Procmail for an
equal length of time and it is now claimed to be "unmaintained".  Oh
well, it works for me to sort my mail into Maildir "mailboxes" for Mutt.

It all "works like a hose" as one electronics instructor was fond of
saying years back.

I like Devuan and Slackware for the same reasons.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Virtualbox?

2017-11-09 Thread Olaf Meeuwissen 
Hi,

Following up on my own post.

Olaf Meeuwissen writes:

> Hi,
>
> Gregory Nowak writes:
>
>> On Mon, Nov 06, 2017 at 05:44:17PM -0500, zap wrote:
>
> # Actually, none of the quoted stuff was written by zap ;-)
>
>>> > I do have one question though, what ascii/stretch package name(s) should
>>> > I pass to `apt-get install`?  Here's what I get for APT sources that
>>> > only reference `ascii{,-security,-updates,-backports}`.
>>> >
>>> >   $ apt-cache search virtualbox-guest
>>> >   virtualbox-guest-dkms - x86 virtualization solution - guest addition 
>>> > module source for dkms
>>> >   virtualbox-guest-source - x86 virtualization solution - guest addition 
>>> > module source
>>> >   virtualbox-guest-utils - x86 virtualization solution - non-X11 guest 
>>> > utilities
>>> >   virtualbox-guest-x11 - x86 virtualization solution - X11 guest utilities
>>
>> At the very least, you want virtualbox-guest-dkms, and
>> virtualbox-guest-utils.
>
> And linux-headers-amd64 if you use APT::Install-Recommends=false ;-)
>
>> If your guest has x installed, then you'll want virtualbox-guest-x11
>> as well.
>
> It's a headless server, no X.
>
>>> > # There is no virtualbox-guest-additions-iso for ascii/stretch, only for
>>> > # jessie, buster and sid.  The virtualbox-guest-additions package for
>>> > # wheezy just transitions to virtualbox-guest-additions-iso.
>>
>> They way I see it, one advantage of not using the iso is that the
>> packages will automatically be pulled in when upgraded versions are
>> available. So no need to mount a new iso, and upgrade by hand.
>
> Not so sure after my experience today because vagrant was complaining
> about a version mismatch for the guest additions (4 point something in
> the VM) and the Virtualbox version on the host OS (5.1.something).  I'm
> not sure this matters (the vagrant message claims that "usually" things
> are okay) but it *is* a major version mismatch.

I nuked the VM, reprovisioned it and manually installed a matching
version of the guest additions.  Vagrant no longer complained on start
up but the clock issue did not go away.

I did notice, though, that checking the VM after it had been running for
a couple of hours (> 5), there was only an approximate two minute clock
skew.  Somewhat later it had increased to about six minutes.  That does
not jive with my earlier statements of loosing 20 seconds to the minute.

I'm not sure if this has anything to do with the version of the guest
additions (I doubt it) or whether it is just that I never noticed that
the same thing was happening before.

>>> > From what I read in the package descriptions, virtualbox-guest-utils and
>>> > virtualbox-guest-x11 provide "stuff" to install in the guest.  How does
>>> > that jive with installing these on the host?  Or should I install these
>>> > on the guest?  Does that mean the guest also needs virtualbox-guest-dkms
>>> > (and the toolchain required to build)?  That would suck pretty badly,
>>> > IMO.
>>
>> All of these are installed in the guest, not in the host. Yes, the
>> virtualbox-guest-dkms is the source part of the kernel modules that
>> would be built by using dkms. The toolchain parts aren't that big.
>
> The VM is a fairly minimized server (stripped of anything that is not
> explicitly depended on).  The toolchain etc added about 20%, IIRC.

It went from 826MB to 985MB, after cleaning out /var/{cache,lib}/apt/.
BTW, it meant to be used as a Jenkins slave for builds from git.  Hence
the "bloat".

>> If you have another system with a toolchain and an identical running
>> kernel, you should be able to install virtualbox-guest-dkms there,
>> build the modules, and copy them over into your guest's
>> lib/modules. The system the modules would be built on doesn't need to
>> be a virtualbox guest as far as I know.
>
> That'd be an option but only if really necessary.  It'd become a bit
> cumbersome if you use guests with lots of different kernels.
>
> Now back to me trying to get the host and guest to agree (and keep
> agreeing) on what time it is, I tried installed the guest additions (in
> the guest as well as the host), restarted and reprovisioned the image
> but to no avail.  I keep losing 20 seconds per minute on the guest.
>
> I'll have another look again tomorrow and will try a matching version of
> the additions (if available).  Failing that, I guess I'll have to take a
> look at the various virtualbox settings and command-line options.

See above.

> I did see something mentioning power management interfering and causing
> erratic behaviour.  This may be a factor because the battery of the
> laptop that I'm testing on is close to dying (but I test when on AC
> power).  Given that, I guess I could give Virtualbox a go on the target
> system(s) and see what happens.
>
> Anyway, the purpose is to keep my VMs on time, one way or another.  It
> is just that a lot of the virtualization/containerization software out
> there comes with, and often defaults to using, Virtualbox