From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: denyhosts quandry
Date: Fri, 20 Mar 2009 12:04:50 -0600 [thread overview]
Message-ID: <FC2659E9B1BB4B85B3D1175295C8AEAD@tdsdev> (raw)
In-Reply-To: <20090320180135.GA2903@localhost.localdomain>
modern hardware makes a huge difference, which is why I was looking for a
place to host the mud.
I went from 3 minutes compile time to 20 seconds or so, if that.
Thanks,
Tyler Littlefield
Web: tysdomain.com
email: tyler@tysdomain.com
My programs don't have bugs, they're called randomly added features.
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, March 20, 2009 12:01 PM
Subject: Re: denyhosts quandry
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, Mar 20, 2009 at 08:49:05AM -0600, Tyler Littlefield wrote:
>> Then I wouldn't be at the
>> mercy of the package maintainers.
>
> Huh? Just because you're using a distro with a package manager that
> tracks dependencies, and has a bunch of stuff already built as
> packages, doesn't mean you're at the mercy of the package
> maintainer. If you don't like how a certain package is built, there's
> nothing stopping you from using something like apt-build, or apt-src,
> to build your own local copy of the package, which is what I've done
> in a couple instances.
>
> As for the comment that recompiling is fun, I would have agreed in the
> past, but don't agree with that now. When I first got into gnu/linux,
> I thought compiling my own software was fun, but it started being a
> hassle after about 3 years or so, which is why I went from slackware
> to debian. I thought I'd prefer the convenience of just being able to
> install a built binary, and that turns out to have been the
> case. That's my own opinion of course, and I'm sure there are folks
> out there who would enjoy compiling their own software 20 years later,
> as much as they enjoyed it on day one. Also, when compiling, it does help
> too have modern hardware to
> do it on, which I don't have currently.
>
> Greg
>
>
> - --
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAknD2f8ACgkQ7s9z/XlyUyAF8wCeIcdcbS2ih9zO8jQRRnssKhoo
> OqwAoJBQCZD6gs8iObUag3lfz25/HIvx
> =+Kb3
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Chris Brannon
` Tyler Littlefield
` James Homuth
` Kirk Reiser
` Tom Moore
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` farhan
` Gregory Nowak
` Gregory Nowak
` Tyler Littlefield [this message]
` Tyler Littlefield
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` Jayson Smith
` Tyler Littlefield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FC2659E9B1BB4B85B3D1175295C8AEAD@tdsdev \
--to=tyler@tysdomain.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).