Send plug mailing list submissions to
plug@lists.phillylinux.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.netisland.net/mailman/listinfo/plug
or, via email, send a message with subject or body 'help' to
plug-request@lists.phillylinux.org
You can reach the person managing the list at
plug-owner@lists.phillylinux.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of plug digest..."
------------------------------------------------------------------------
Today's Topics:
1. OT: SRE @ Google (Cosmin Nicolaescu)
2. Re: Verizon blacklist? (Eugene Smiley)
3. Re: Linux-Mac connections (Eugene Smiley)
4. Re: OT: SRE @ Google (Toby DiPasquale)
5. OT: domains/registrars (Ronald Mansolino)
6. Re: OT: SRE @ Google (Joshua Karstendick)
7. Re: OT: domains/registrars (gyoza@comcast.net)
8. Re: OT: SRE @ Google (John Von Essen)
9. Re: OT: domains/registrars (Doug Crompton)
10. Re: Verizon blacklist? (George A. Theall)
------------------------------------------------------------------------
Subject:
[PLUG] OT: SRE @ Google
From:
Cosmin Nicolaescu <cos@camelot.homelinux.com>
Date:
Tue, 30 Aug 2005 19:08:46 -0400 (EDT)
To:
plug@lists.phillylinux.org
To:
plug@lists.phillylinux.org
------------------------- Original Message ----------------------------
From: "Jeff Polo" <jpolo@google.com>
-----------------------------------------------------------------------
The group I'm supporting is Google.com Engineering (a.k.a. Site
Reliability Engineering, or SRE) This multi-talented group of engineers
all have some mix of Linux/Unix systems administration experience, solid
scripting/coding skills, and a firm understanding of networking. They are
responsible for ensuring the quality, speed, and uptime of Google's
services and tools and managing the production systems and network they
run on. From code-level troubleshooting of traffic anomalies to
maintenance of our most cutting edge services; from monitoring and alerts
to building new automation
infrastructure, our SRE engineers are in the thick of everything related
to keeping Google.com running at peak.
The guy is interestred in full-time positions, so just email him with a
resume if you'd like to.
-Cos
------------------------------------------------------------------------
Subject:
Re: [PLUG] Verizon blacklist?
From:
Eugene Smiley <eug+plug@esmiley.net>
Date:
Tue, 30 Aug 2005 19:33:37 -0400
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
George A. Theall wrote:
On Tue, Aug 30, 2005 at 11:40:02AM -0400, gyoza@comcast.net wrote:
All SPF would do is ensure that the spam is
sent from an approved server!
Exactly. And thus, getting back to my original message, the notion
of using SPF for whitelisting addresses is foolish if that's what
AOL and Earthlink are truly doing.
<I don't recall details of how AOL uses their whitelist, but it's
been disussed in general terms on the SPF mailinglist (which I've
been off of for6 months or so)
http://postmaster.aol.com/tools/dynamic_guidelines.html.>
How would a whitelist be of any use if you weren't sure that the MAIL
FROM hasn't been faked? I could get around the whitelist by finding a
message that gets through and then use that address in the MAIL FROM
of all my outgoing spam to that service until it gets blocked and I
start all over again. Mean while Aunt Sally is wondering why all
these people are flaming her for spam she didn't send and asking you
why.
Hardly foolish.
The best visual and written explanation can be found at:
http://spf.pobox.com/2dimensions.html
http://spf.pobox.com/for-mit-spam-conference.html
It shows how SPF is simply one piece of an evolving puzzle.
For AOL, Earthlink, Google, etc it makes sense to publish SPF to
protect their Trademarks. It hurts their reputation when their domain
name is forged. It makes sense for them to check SPF records because
it's possible to reduce the load on their mail infrastructure. It's
sound business either way.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQxTsyOkD7QKn7f0vEQJ+TACg+4FKs5WvYDcPl8kcZadS/OB6SooAnjaj
KySDBFGOK0WEIkKjaKiiKNq+
=pHtC
-----END PGP SIGNATURE-----
------------------------------------------------------------------------
Subject:
Re: [PLUG] Linux-Mac connections
From:
Eugene Smiley <eug+plug@esmiley.net>
Date:
Tue, 30 Aug 2005 19:49:48 -0400
To:
art.alexion@verizon.net, Philadelphia Linux User's Group Discussion
List <plug@lists.phillylinux.org>
To:
art.alexion@verizon.net, Philadelphia Linux User's Group Discussion
List <plug@lists.phillylinux.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Art Alexion wrote:
That is what I thought also. What was most puzzling was the fact
that the windows client was working. Then I noticed that the
Windows client was also exhibiting the same behavior. I fixed it
by uninstalling dhcp3-server, rebooting (because uninstalling
didn't seem to help) and going back to relying on hard coded
internal IP addresses. I think the problem was with dhcpd.conf,
but I couldn't figure out what it was.
Actually, I read something recently that may apply. IIRC, DHCPD
removes resolve.conf and replaces it with a link to it's own file
elsewhere. Unless you edit the new file it won't resolve properly.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQxTwhOkD7QKn7f0vEQIa7gCgsXlGekcOr4WL/bdZku34pkj4lkMAoN70
nYEMdQVjyfj63MR4lYqUni4w
=3btr
-----END PGP SIGNATURE-----
------------------------------------------------------------------------
Subject:
Re: [PLUG] OT: SRE @ Google
From:
Toby DiPasquale <toby@cbcg.net>
Date:
Tue, 30 Aug 2005 21:37:14 -0400
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
On Tue, Aug 30, 2005 at 07:08:46PM -0400, Cosmin Nicolaescu wrote:
------------------------- Original Message ----------------------------
From: "Jeff Polo" <jpolo@google.com>
-----------------------------------------------------------------------
The group I'm supporting is Google.com Engineering (a.k.a. Site
Reliability Engineering, or SRE) This multi-talented group of engineers
all have some mix of Linux/Unix systems administration experience, solid
scripting/coding skills, and a firm understanding of networking. They are
responsible for ensuring the quality, speed, and uptime of Google's
services and tools and managing the production systems and network they
run on. From code-level troubleshooting of traffic anomalies to
maintenance of our most cutting edge services; from monitoring and alerts
to building new automation
infrastructure, our SRE engineers are in the thick of everything related
to keeping Google.com running at peak.
The guy is interestred in full-time positions, so just email him with a
resume if you'd like to.
Might want to check out the situation there; I've heard from some people
on the West Coast that they pay very poorly for this type of position
(e.g. $35K for sysadmin around SF).
-- T
------------------------------------------------------------------------
Subject:
[PLUG] OT: domains/registrars
From:
Ronald Mansolino <rmsolino@netaxs.com>
Date:
Tue, 30 Aug 2005 22:08:11 -0400
To:
plug@lists.phillylinux.org
To:
plug@lists.phillylinux.org
I have a handful of domains coming up for renewal in the next few months
and I really can't afford to pay verisign a premium fee. So I'm looking
for recommendations on someone clueful to renew/transfer them to.
------------------------------------------------------------------------
Subject:
Re: [PLUG] OT: SRE @ Google
From:
Joshua Karstendick <joshdick@gmail.com>
Date:
Tue, 30 Aug 2005 22:11:56 -0400
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
Who needs money when you're working for the almightly Google? You're
supposed to simply love the work and the free food. And just try the
Kool-Aid!</sarcasm>
On 8/30/05, *Toby DiPasquale* <toby@cbcg.net <mailto:toby@cbcg.net>>
wrote:
On Tue, Aug 30, 2005 at 07:08:46PM -0400, Cosmin Nicolaescu wrote:
> ------------------------- Original Message
----------------------------
> From: "Jeff Polo" < jpolo@google.com <mailto:jpolo@google.com>>
>
-----------------------------------------------------------------------
>
> The group I'm supporting is Google.com <http://Google.com>
Engineering (a.k.a. Site
> Reliability Engineering, or SRE) This multi-talented group of
engineers
> all have some mix of Linux/Unix systems administration
experience, solid
> scripting/coding skills, and a firm understanding of
networking. They are
> responsible for ensuring the quality, speed, and uptime of Google's
> services and tools and managing the production systems and
network they
> run on. From code-level troubleshooting of traffic anomalies to
> maintenance of our most cutting edge services; from monitoring
and alerts
> to building new automation
> infrastructure, our SRE engineers are in the thick of everything
related
> to keeping Google.com <http://Google.com> running at peak.
>
> The guy is interestred in full-time positions, so just email him
with a
> resume if you'd like to.
>
Might want to check out the situation there; I've heard from some
people
on the West Coast that they pay very poorly for this type of position
(e.g. $35K for sysadmin around SF).
-- T
___________________________________________________________________________
Philadelphia Linux Users Group
-- http://www.phillylinux.org
Announcements -
http://lists.phillylinux.org/mailman/listinfo/plug-announce
<http://lists.phillylinux.org/mailman/listinfo/plug-announce>
General Discussion --
http://lists.phillylinux.org/mailman/listinfo/plug
--
Joshua Karstendick
------------------------------------------------------------------------
Subject:
Re: [PLUG] OT: domains/registrars
From:
gyoza@comcast.net
Date:
Tue, 30 Aug 2005 22:22:48 -0400
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
To:
Philadelphia Linux User's Group Discussion List
<plug@lists.phillylinux.org>
Ronald Mansolino wrote:
I have a handful of domains coming up for renewal in the next few months
and I really can't afford to pay verisign a premium fee. So I'm looking
for recommendations on someone clueful to renew/transfer them to.
I've always used GoDaddy.
------------------------------------------------------------------------
Subject:
Re: [PLUG] OT: SRE @ Google
From:
John Von Essen <john@essenz.com>
Date:
Tue, 30 Aug 2005 22:28:34 -0400
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
Tony,
When the Google guy posted this on the list a month or so a go, I
immediately followed-up with a remark about google offering far below
average salaries. His response was a very canned answer - and of
course he didn't acknowledge if Google pays competitive wages.
So when you say $35k, I'm not suprized at all.
Screw google. 5 years from now Microsoft will have swallowed up some
of their top disgruntled engineers, and voila, tables are turned.
Just like AMD did against Intel in the late 90's.
-john
On Aug 30, 2005, at 9:37 PM, Toby DiPasquale wrote:
On Tue, Aug 30, 2005 at 07:08:46PM -0400, Cosmin Nicolaescu wrote:
------------------------- Original Message
----------------------------
From: "Jeff Polo" <jpolo@google.com>
----------------------------------------------------------------------
-
The group I'm supporting is Google.com Engineering (a.k.a. Site
Reliability Engineering, or SRE) This multi-talented group of
engineers
all have some mix of Linux/Unix systems administration experience,
solid
scripting/coding skills, and a firm understanding of networking.
They are
responsible for ensuring the quality, speed, and uptime of Google's
services and tools and managing the production systems and network
they
run on. From code-level troubleshooting of traffic anomalies to
maintenance of our most cutting edge services; from monitoring and
alerts
to building new automation
infrastructure, our SRE engineers are in the thick of everything
related
to keeping Google.com running at peak.
The guy is interestred in full-time positions, so just email him
with a
resume if you'd like to.
Might want to check out the situation there; I've heard from some
people
on the West Coast that they pay very poorly for this type of position
(e.g. $35K for sysadmin around SF).
-- T
_______________________________________________________________________
____
Philadelphia Linux Users Group --
http://www.phillylinux.org
Announcements -
http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion --
http://lists.phillylinux.org/mailman/listinfo/plug
------------------------------------------------------------------------
Subject:
Re: [PLUG] OT: domains/registrars
From:
Doug Crompton <doug@crompton.com>
Date:
Tue, 30 Aug 2005 22:45:36 -0400 (EDT)
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
I have about 12 with GoDaddy that I nameserve. It is easy to maintain, I
have no complaints and the price is right. Why anyone would pay verisigns
fees I don't know. You get much more for less with GoDaddy. It is $10/year
or less.
Doug
Ronald Mansolino wrote:
I have a handful of domains coming up for renewal in the next few months
and I really can't afford to pay verisign a premium fee. So I'm looking
for recommendations on someone clueful to renew/transfer them to.
****************************
* Doug Crompton *
* Richboro, PA 18954 *
* 215-431-6307 *
* *
* doug@crompton.com *
* http://www.crompton.com *
****************************
------------------------------------------------------------------------
Subject:
Re: [PLUG] Verizon blacklist?
From:
"George A. Theall" <theall@tifaware.com>
Date:
Tue, 30 Aug 2005 22:48:39 -0400
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
To:
"Philadelphia Linux User's Group Discussion List"
<plug@lists.phillylinux.org>
On Tue, Aug 30, 2005 at 07:33:37PM -0400, Eugene Smiley wrote:
George A. Theall wrote:
Exactly. And thus, getting back to my original message, the notion
of using SPF for whitelisting addresses is foolish if that's what
AOL and Earthlink are truly doing.
...
How would a whitelist be of any use if you weren't sure that the MAIL
FROM hasn't been faked?
Let me turn that around... What good are such whitelists when spammers
are on one hand publishing SPF records and on the other injecting mail
through means that SPF records claim are acceptable?
For AOL, Earthlink, Google, etc it makes sense to publish SPF to
protect their Trademarks. It hurts their reputation when their domain
name is forged. It makes sense for them to check SPF records because
it's possible to reduce the load on their mail infrastructure. It's
sound business either way.
If only things were so black and white.
George
------------------------------------------------------------------------
_______________________________________________
plug mailing list
plug@lists.phillylinux.org
http://lists.netisland.net/mailman/listinfo/plug