I'd buy that for $778 less than you paid for it :P

It's probably fun until the handlebars play footsie with your man bits
during an "unexpected deceleration event".

On Sep 1, 2016 4:47 PM, "Adam Moffett" <dmmoff...@gmail.com> wrote:

I never really had a moped...but I had one of these until somebody stole it:
http://goped.com/sport/


------ Original Message ------
From: "Josh Reynolds" <j...@kyneticwifi.com>
To: af@afmug.com
Sent: 9/1/2016 5:34:52 PM
Subject: Re: [AFMUG] FYI: Perl error in bind9 with webmin


LOL :)

On Sep 1, 2016 4:33 PM, "Adam Moffett" <dmmoff...@gmail.com> wrote:

> He apologized for running webmin in his original post and still people
> gotta hate on him.
> Sheesh.
>
> *drives away on moped*
>
>
> ------ Original Message ------
> From: "Eric Kuhnke" <eric.kuh...@gmail.com>
> To: "af@afmug.com" <af@afmug.com>
> Sent: 9/1/2016 4:23:56 PM
> Subject: Re: [AFMUG] FYI: Perl error in bind9 with webmin
>
>
> Just say no to webmin. You would not believe the number of misconfigured
> servers I've seen where people left webmin running on their public facing
> ipv4 address/httpd for the world to see, and not even any self signed
> certificate https. Just plaintext auth.
>
> And they happily login to it from random places.
>
> On Thu, Sep 1, 2016 at 12:55 PM, That One Guy /sarcasm <
> thatoneguyst...@gmail.com> wrote:
>
>> If you are like me and like webmin on your linux stuff and are running
>> bind 9, the current webmin version will generate perl errors if you go to
>> update any records.
>> The work around is to go
>> webmin - webmin configuration - upgrade webmin
>> check the upgrade even if new version is same or older
>> run it
>> it will say there is one update, run it it is a bind8 update but it fixes
>> it
>>
>> I know, running webmin and admitting it is probably alot like riding
>> mopeds and nailing fat chics and telling your friends about it
>> --
>> If you only see yourself as part of the team but you don't see your team
>> as part of yourself you have already failed as part of the team.
>>
>
>

Reply via email to