Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...

How do I fix it !!!

What I always did on my old system was to re-emerge the modules.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

What else can I do?

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:

Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...

How do I fix it !!!

What I always did on my old system was to re-emerge the modules.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

What else can I do?

You could try 'emerge @x11-module-rebuild'.

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I’d recommend emerging Virtualbox again. It should just work with emerge @module-rebuild unless Virtualbox isn’t compatible with the newer version
of kernel.

On Sat, Nov 27, 2021 at 8:00 AM Wols Lists <antlists@youngman.org.uk> wrote:

On 27/11/2021 12:41, Peter Humphrey wrote:

On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:

Simple problem, after a kernel upgrade, virtualbox no longer works. This >> is to be expected, of course, BUT ...

How do I fix it !!!

What I always did on my old system was to re-emerge the modules.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

What else can I do?

You could try 'emerge @x11-module-rebuild'.

Same result - nothing to rebuild :-(

Cheers,
Wol

<div dir="auto">I’d recommend emerging Virtualbox again. It should just work with emerge @module-rebuild unless Virtualbox isn’t compatible with the newer version of kernel.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On
Sat, Nov 27, 2021 at 8:00 AM Wols Lists &lt;<a href="mailto:antlists@youngman.org.uk">antlists@youngman.org.uk</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 27/11/2021 12:
41, Peter Humphrey wrote:<br>
&gt; On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:<br>
&gt;&gt; Simple problem, after a kernel upgrade, virtualbox no longer works. This<br>
&gt;&gt; is to be expected, of course, BUT ...<br>
&gt;&gt;<br>
&gt;&gt; How do I fix it !!!<br>
&gt;&gt;<br>
&gt;&gt; What I always did on my old system was to re-emerge the modules.<br> &gt;&gt;<br>
&gt;&gt; The docu says &quot;emerge @module-rebuild&quot;.<br>
&gt;&gt;<br>
&gt;&gt; Both of these terminate with &quot;nothing to rebuild&quot;.<br> &gt;&gt;<br>
&gt;&gt; What else can I do?<br>
&gt; <br>
&gt; You could try &#39;emerge @x11-module-rebuild&#39;.<br>
&gt; <br>
Same result - nothing to rebuild :-(<br>

Cheers,<br>
Wol<br>

</blockquote></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Saturday, 27 November 2021 12:59:49 GMT Wols Lists wrote:

On 27/11/2021 12:41, Peter Humphrey wrote:

On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:

Simple problem, after a kernel upgrade, virtualbox no longer works. This >> is to be expected, of course, BUT ...

How do I fix it !!!

What I always did on my old system was to re-emerge the modules.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

What else can I do?

You could try 'emerge @x11-module-rebuild'.

Same result - nothing to rebuild :-(

Cheers,
Wol

It may be worth mentioning ... I've noticed my MSWindows VirtualBox VMs are malfunctioning when I launch them from within Plasma Wayland. I can login,
but then lose the ability to click on anything or interact with the Windows desktop. Things work fine when I run them within Plasma in Xorg instead of Wayland.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmGiLLkACgkQseqq9sKV ZxkCJg//UD4EWKugNvhAMkZKhGonxglQLKWYlxm327LWFF/mlLM7dTGeAswwMMKY AGhoH3gH8SVd9QOEOkkAGg2ciLZKfxzJI+Ghk6aPQn0m7gBHw2+AEWStUALVHE9k /2YUmwG2vjUFIbJclPlOQ3IaZ089cXsZTXef4s9qbIonkCQvG+8QIjB72QXOId2s qY12/gc3x6ylTPPnsimbdDB37DxUwzsMFeQ8uyn6i755cjnE8PvYSXFnvIUOTkic 7MK5ohj5dyk4pAOuZcRvqiCdkGuiAJcXIJhX+agl7pii3V2SBhZxxOoi0O8tlHw3 Ae0GUyRkUihTMdTtWDmPsUFly++/QsOxmlxgg/OLqmV82de7yFopbrdoJopv6NCX 5j4QPxF//aVlCG0ExiOHH/ldUW1Y07lN38Q4Rq4edF0oPT1BzY6/0I87AjiOMSwz TCTAzLmKl6OWxYjReIoGz4zWunF9CF8hDz/77BVBTXi4qkRTCzXyJR1MJnmQe4Pb LPChrr3KMKleWCrZoW9hzPtRDfv9SW3YA/BjMVU2ATztxc0dcammNT3bHq2ZzwFA YX94c6AC6obXq1vPUOntR1cSnLnMSC22EnvOxZBay4ruC6NenG/EwxzbsGECRgb7 qljmA9M+38zbeiZO6xCntgtu8Voe4DhrCdx+TUkrBtrW0kez74Y=
=a2pz
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 27/11/2021 12:41, Peter Humphrey wrote:

On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:

Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...

How do I fix it !!!

What I always did on my old system was to re-emerge the modules.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

What else can I do?

You could try 'emerge @x11-module-rebuild'.

Same result - nothing to rebuild :-(

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 27/11/2021 13:03, Jeremy Hendricks wrote:

I’d recommend emerging Virtualbox again. It should just work with emerge @module-rebuild unless Virtualbox isn’t compatible with the newer
version of kernel.

HOW !?!?

The problem is that they are already installed, so any attempt to emerge
them fails with "nothing to emerge".

Unless I do an "emerge -C", but that of course will then break the old
kernel (assuming I might want to go back to it ...)

Cheers,
Wol

On Sat, Nov 27, 2021 at 8:00 AM Wols Lists <antlists@youngman.org.uk <mailto:antlists@youngman.org.uk>> wrote:

On 27/11/2021 12:41, Peter Humphrey wrote:
> On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:
>> Simple problem, after a kernel upgrade, virtualbox no longer
works. This
>> is to be expected, of course, BUT ...
>>
>> How do I fix it !!!
>>
>> What I always did on my old system was to re-emerge the modules.
>>
>> The docu says "emerge @module-rebuild".
>>
>> Both of these terminate with "nothing to rebuild".
>>
>> What else can I do?
>
> You could try 'emerge @x11-module-rebuild'.
>
Same result - nothing to rebuild :-(

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I mean that as: just reinstall Virtualbox as a first troubleshooting step.
If that works, great. If it doesn’t, then that can be marked off the list
as something that was tried.

On Sat, Nov 27, 2021 at 8:21 AM Wols Lists <antlists@youngman.org.uk> wrote:

On 27/11/2021 13:03, Jeremy Hendricks wrote:

I’d recommend emerging Virtualbox again. It should just work with emerge @module-rebuild unless Virtualbox isn’t compatible with the newer
version of kernel.

HOW !?!?

The problem is that they are already installed, so any attempt to emerge
them fails with "nothing to emerge".

Unless I do an "emerge -C", but that of course will then break the old
kernel (assuming I might want to go back to it ...)

Cheers,
Wol

On Sat, Nov 27, 2021 at 8:00 AM Wols Lists <antlists@youngman.org.uk <mailto:antlists@youngman.org.uk>> wrote:

On 27/11/2021 12:41, Peter Humphrey wrote:
> On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:
>> Simple problem, after a kernel upgrade, virtualbox no longer
works. This
>> is to be expected, of course, BUT ...
>>
>> How do I fix it !!!
>>
>> What I always did on my old system was to re-emerge the modules.
>>
>> The docu says "emerge @module-rebuild".
>>
>> Both of these terminate with "nothing to rebuild".
>>
>> What else can I do?
>
> You could try 'emerge @x11-module-rebuild'.
>
Same result - nothing to rebuild :-(

Cheers,
Wol

<div dir="auto">I mean that as: just reinstall Virtualbox as a first troubleshooting step. If that works, great. If it doesn’t, then that can be marked off the list as something that was tried.</div><div><br><div class="gmail_quote"><div dir="ltr"
class="gmail_attr">On Sat, Nov 27, 2021 at 8:21 AM Wols Lists &lt;<a href="mailto:antlists@youngman.org.uk">antlists@youngman.org.uk</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:
1ex">On 27/11/2021 13:03, Jeremy Hendricks wrote:<br>
&gt; I’d recommend emerging Virtualbox again. It should just work with emerge <br>
&gt; @module-rebuild unless Virtualbox isn’t compatible with the newer <br> &gt; version of kernel.<br>

HOW !?!?<br>

The problem is that they are already installed, so any attempt to emerge <br> them fails with &quot;nothing to emerge&quot;.<br>

Unless I do an &quot;emerge -C&quot;, but that of course will then break the old <br>
kernel (assuming I might want to go back to it ...)<br>

Cheers,<br>
Wol<br>
&gt; <br>
&gt; On Sat, Nov 27, 2021 at 8:00 AM Wols Lists &lt;<a href="mailto:antlists@youngman.org.uk" target="_blank">antlists@youngman.org.uk</a> <br>
&gt; &lt;mailto:<a href="mailto:antlists@youngman.org.uk" target="_blank">antlists@youngman.org.uk</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;     On 27/11/2021 12:41, Peter Humphrey wrote:<br>
&gt;      &gt; On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:<br>
&gt;      &gt;&gt; Simple problem, after a kernel upgrade, virtualbox no longer<br>
&gt;     works. This<br>
&gt;      &gt;&gt; is to be expected, of course, BUT ...<br>
&gt;      &gt;&gt;<br>
&gt;      &gt;&gt; How do I fix it !!!<br>
&gt;      &gt;&gt;<br>
&gt;      &gt;&gt; What I always did on my old system was to re-emerge the modules.<br>
&gt;      &gt;&gt;<br>
&gt;      &gt;&gt; The docu says &quot;emerge @module-rebuild&quot;.<br> &gt;      &gt;&gt;<br>
&gt;      &gt;&gt; Both of these terminate with &quot;nothing to rebuild&quot;.<br>
&gt;      &gt;&gt;<br>
&gt;      &gt;&gt; What else can I do?<br>
&gt;      &gt;<br>
&gt;      &gt; You could try &#39;emerge @x11-module-rebuild&#39;.<br> &gt;      &gt;<br>
&gt;     Same result - nothing to rebuild :-(<br>
&gt; <br>
&gt;     Cheers,<br>
&gt;     Wol<br>
&gt; <br>


</blockquote></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Nov 27, 2021 at 7:29 AM Wols Lists <antlists@youngman.org.uk> wrote:

Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...

I can't offer any VirtualBox-specific solutions but I would try
reinstalling it as others have suggested (emerge -1
virtualbox-modules).

Some more general suggestions:

1. I use Virtualbox on Windows as there aren't a lot of good free
alternatives that I'm aware of. I stopped using it on Linux ages ago
because KVM/libvirt are generally much better these days. app-emulation/virt-manager is a nice front-end for libvirt which will
be reminiscent of Virtualbox, but it uses the kernel's built-in KVM as
the engine and libvirt for management. You can use the nice gui of
course, but everything is also manageable via the command line and is
easily scriptable, or turned into services.

2. Anytime I'm using either out-of-kernel modules or more experimental
features in the kernel (zfs, nvidia binary drivers, btrfs, etc) I tend
to carefully control what kernel series I'm running. I pick an LTS
that is supported and stable for everything I'm doing, and stick with
it until the next LTS is stable and seems ok to me, and then I do some
testing before migrating. I just switched to 5.10 a few weeks ago.

In general you're unlikely to get regressions or issues with
out-of-tree drivers between minor releases (eg 5.10.81 to 5.10.82),
but depending on the software you can get them between major releases
(eg 5.4.162 to 5.10.82). Also, updates between minor releases tend to
be really trivial to build since the config files almost never change,
or at most a make oldconfig rarely gives you a single prompt to
answer.

Gentoo doesn't really manage kernel QA around out-of-tree modules.
Other distros will pick and choose - for example, if the distro wants
to support zfs as an option then it will only release stable kernels
that work with zfs. It is pretty easy though on Gentoo to just manage
your own kernel, so you don't have to worry about what out-of-tree
modules are/aren't supported officially. Of course you're still at
the mercy of upstream - if Nvidia doesn't want to release a driver for
your 20 year old GPU that works with a kernel that still gets security
updates then you're up the creek. That's just the price of using
out-of-tree modules.

This is just another reason to run KVM - everything it uses in kernel
space is built into the kernel, and basically "just works." The
userspace stuff doesn't care so much about kernel versions since the
syscall interface is stable.

--
Rich

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format.

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

Strange. try: emerge virtualbox-modules
That should be rebuild after everuy kernel upgrade and that happens normally with emerge @module-rebuild


<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt;The docu says &quot;emerge @module-rebuild&quot;.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt;Both of these terminate with &quot;nothing to rebuild&quot;.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Strange. try: emerge virtualbox-modules</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">That should be rebuild after everuy kernel upgrade and that happens normally with emerge @module-rebuild</p>
<br /></body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 27/11/2021 22:15, Kees wrote:

The docu says "emerge @module-rebuild".

Both of these terminate with "nothing to rebuild".

Strange. try: emerge virtualbox-modules

That should be rebuild after everuy kernel upgrade and that happens
normally with emerge @module-rebuild

"nothing to rebuild"

It always USED to work ...

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

quickpg the existing  modules then try the remove/reinstall fix. You can
then use "emerge -K =package" or even a manually reinstall (by coping
them over the newer ones) to replace the modules if things don't work out.

I would think in your case needing to keep kernel specific modules
around this would be an attractive task to script keeping matching
modules with a kernel and swapping them in and out as necessary.

BillK


On 28/11/21 08:11, Wols Lists wrote:

On 27/11/2021 22:15, Kees wrote:

;The docu says "emerge @module-rebuild".

;Both of these terminate with "nothing to rebuild".

Strange. try: emerge virtualbox-modules

That should be rebuild after everuy kernel upgrade and that happens
normally with emerge @module-rebuild

"nothing to rebuild"

It always USED to work ...

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 28 Nov 2021 00:11:57 +0000, Wols Lists wrote:

Strange. try: emerge virtualbox-modules

That should be rebuild after everuy kernel upgrade and that happens normally with emerge @module-rebuild

"nothing to rebuild"

emerge pkg should always emerge it, whether it is installed or not. Have
you added anything to EMERGE_DEFAULT_OPTS to alter this behaviour?


--
Neil Bothwick

"Fascinating," said Spock, watching Kirk's lousy acting.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmGjNMkACgkQ92eFu0QS MJju7BAAhf0whquChx4lXSALqz1cLIZXukavAmuw/zfGGX7CFSHoYhchSRrY+a8G m3VpSpJXchUFzw3j3BlLyKIc/JdHGVP0SsHUMspIZGP/G0mjLYRWtu9+X6waS/aV /HdrrohZ6JCU/Y1boE/g7g7Fgj1kpVJohVYMATVb6tB7pEemOXzNFXgcKRyCOouE sNFMoIcwM19JSiElcGPn03Oa/dGBYzVMcgwoPQ3cmo9eRI67oWIssiRUXDL0zLCE qR33KvmmWcPnfs0VY7s4b1lSxEOpVmND+70D1T6j+WKA3XANw5Xdpw1UDSVtJuGy 19JNr9xei6OL1uefVwNokJWRNiwO8sRuSWjekA4uE288F3zl6zfL70VnyidJvltL oJ4r1JJJeN3KKa7/Ueo/BpZjDuDbWQDBUKAR97/HQrneteY288lr6YroNtUTaouf GdsTcs8YdpuXPnoQ4Y4/4ZUZ2gJuHEQYuUa90tJ+KzDWRoomuw0fnXZulg85nQw3 i/uFqfi03/0T1tWLshOcNbhQqLNn4SaP340vVUxqpDcRi6hvaFi5W0zrOJEUUzEN 9yKbWlfXP1/ePXWbPN/ADtEyF0qVWaC1Bqej3k1CNf74cDR37OLVmtaqg/jCRA6+ AUoc8Je5Dr+11JjsKIw2qW/LdVwWsYmkKJ8qmfN+srkBp0hE1BE=
=fOX5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/11/2021 07:50, Neil Bothwick wrote:

On Sun, 28 Nov 2021 00:11:57 +0000, Wols Lists wrote:

Strange. try: emerge virtualbox-modules

That should be rebuild after everuy kernel upgrade and that happens
normally with emerge @module-rebuild

"nothing to rebuild"

emerge pkg should always emerge it, whether it is installed or not. Have
you added anything to EMERGE_DEFAULT_OPTS to alter this behaviour?

That *could* alter it, yes. That I think *would* alter it, no.

--buildpkg --deep --newuse --oneshot --usepkg


Comment that line out, and it works! I'll need to remember that.

Thanks. But why?

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 28 November 2021 08:53:07 GMT Wols Lists wrote:

On 28/11/2021 07:50, Neil Bothwick wrote:

On Sun, 28 Nov 2021 00:11:57 +0000, Wols Lists wrote:

Strange. try: emerge virtualbox-modules

That should be rebuild after everuy kernel upgrade and that happens
normally with emerge @module-rebuild

"nothing to rebuild"

emerge pkg should always emerge it, whether it is installed or not. Have you added anything to EMERGE_DEFAULT_OPTS to alter this behaviour?

That *could* alter it, yes. That I think *would* alter it, no.

--buildpkg --deep --newuse --oneshot --usepkg

Comment that line out, and it works! I'll need to remember that.

Thanks. But why?

Cheers,
Wol

Because of "--newuse".
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmGjVA8ACgkQseqq9sKV ZxmszhAAqRpTcMCzPmC/8XYzQhCIGunQhteu/9SmtgB/O+1/CSYxBNBuKoMjCACa 3QFJtDHo9i8le+jrkgq58v3eCB6FUXvIe7/4lLYAOAaDRmzcUb4if7s02aq6RDmR Y75lEmP2UcP1lDQVWQNHo/uCxHd3KHv8qKkAPxfxQYq6rHMt4HCdWHvkNKit33sb QkEaETdDcb41NWNSCgGvcvfGL3QY8QbZ20b338a03cx2E0ntE1wZVlnzClydUGIe xhU1N5PSWbQQfW9rEkMezG1Adr7MwsW3mmQVYCaut1uOpu83V/YkN3EpZyp79KVx JWpYPlJjzbE6QJxSi/3gDoZCdloQKSXyIrZmhyZOVvQVmP3PXD/NqyQ3IOtz+Y1R xoC0fc3dK5xwRBWU2UMX261oVmzWX+mK3OhoiYjnnXjpsbu7C937FMnwQmCsr+Lb 5ytcIGkcGDCEUD8zCJYcdXfLabG4Soff106BSyQm3f9EyLw5VAU4kmKcNlRYIEBF zBmfgUsknitmm8SgwwiUdOsbyT/tf47bsGdCc9IoMxPtoBT1cX5oCsK/+AiLqM3U p5lIBUTvYpnHpxAoVi5nbdDOFnYYbnp9zZPnLEAThcE+rb34BD98a0+VSM0uSy2W /ym8obRGRS320vOafOQ/j9ihVU01WXkJPT1K9gH+YGmuV9TEeCA=
=RwzM
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 28 Nov 2021 10:03:59 +0000, Michael wrote:

emerge pkg should always emerge it, whether it is installed or not.
Have you added anything to EMERGE_DEFAULT_OPTS to alter this
behaviour?

That *could* alter it, yes. That I think *would* alter it, no.

--buildpkg --deep --newuse --oneshot --usepkg

Comment that line out, and it works! I'll need to remember that.

Because of "--newuse".

--usepkg will also cause it to fail because it will re-emerge the files
for the previous kernel version.


--
Neil Bothwick

What do you do when you see an endangered animal eating an endangered
plant?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmGj6VQACgkQ92eFu0QS MJjcsg/9GNSAFzQm09VLg3yT3+t/dzimcYIehFXvWOWgJhm/9VG6bE7nnzzNz/4I ONP+ob2k9M2fXMWbjQ96RpR3L2HlWClGO5sZVUw5iErPl92ky8ydB+VTO5hiJfv1 yG9q2cdffdBPwyslf1gWy7byobBAQ3MRFcIYvwBwZYsLGfEgiejLe2ZOTrOxrNtx jBO2fZp97SIuCuCd0MiGY67KFRWqaV1MYpYvxYs2CJUc1ODZ2/DlVh/EuaAcKU68 euVIZnpq3/HflPhOyt7VPNU0zo6zQCpoZolta9uN43oIZ3agr0dPoDNZq25KfWu7 uIYW6K2inZ1aj3EwZg+3uPCFExNMGDL4wnxMHhr/4vc2Akjc9nR1hnmbnL6WSMLQ whhsSL+Gon8X6o12R1IYgECAM6qZlMephM8pyPNVncoOEYCLjzHbgLdzrmdkBxBm 8YoCS8pzKi31wg/3dBTODns4VAQNEQ/2lKA37KOZB6YE/09UQF4O0su7JDdxO9Go Yxd/9v44abpLjARD4ephwFvbU+d4Qf/8MJJn6OX4078EWTwiyacaC3DB36R/dDrC Dn1swXTCTE/oBbpMMA4ZDehZi0PSzv81MiS8JZBk66iTQZTlS0VhWdI9MwJ487Tl 1q5nqR7zgFmQMMgQFz3vM46PDsY7y7HXAAz91exl4zS8oOeOg5k=
=g2NK
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)