Sorry if this is a repost. Just subscribed and not sure if the first one went or not.
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
Cheers,
Travis Bullock Systems Administrator Avmax Group Inc.
On Wednesday 21 February 2007 12:41, Travis Bullock wrote:
Sorry if this is a repost. Just subscribed and not sure if the first one went or not.
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
Cheers,
Travis Bullock Systems Administrator Avmax Group Inc.
For FC5 my tzdata is tzdata-2006p-1.fc5
FC2, 4 are in fedora-legacy so I have no idea if they have been updated or not.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Terry Polzin wrote:
On Wednesday 21 February 2007 12:41, Travis Bullock wrote:
Sorry if this is a repost. Just subscribed and not sure if the first one went or not.
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
Cheers,
Travis Bullock Systems Administrator Avmax Group Inc.
For FC5 my tzdata is tzdata-2006p-1.fc5
FC2, 4 are in fedora-legacy so I have no idea if they have been updated or not.
Legacy is officially closed; so, there is no updates. There may be others though re-spinning updates just have to look for them.
- -James
Terry Polzin wrote:
On Wednesday 21 February 2007 12:41, Travis Bullock wrote:
Sorry if this is a repost. Just subscribed and not sure if the first one went or not.
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
Cheers,
Travis Bullock Systems Administrator Avmax Group Inc.
For FC5 my tzdata is tzdata-2006p-1.fc5
FC2, 4 are in fedora-legacy so I have no idea if they have been updated or not.
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
On Thu, Feb 22, 2007 at 03:42:34PM -0400, Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
Although, as mentioned, you are not okay in a variety of other ways. If your system is important enough that it needs to have the correct time, it's important enough to not leave running an unmaintained distribution.
Matthew Miller wrote:
On Thu, Feb 22, 2007 at 03:42:34PM -0400, Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
Although, as mentioned, you are not okay in a variety of other ways. If your system is important enough that it needs to have the correct time, it's important enough to not leave running an unmaintained distribution.
There is a distinction between "unmaintained" and "unsupported".
Mike
Mike McCarty wrote:
Matthew Miller wrote:
On Thu, Feb 22, 2007 at 03:42:34PM -0400, Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
Although, as mentioned, you are not okay in a variety of other ways. If your system is important enough that it needs to have the correct time, it's important enough to not leave running an unmaintained distribution.
There is a distinction between "unmaintained" and "unsupported".
What's the difference? The bugs that were always there become known and exploitable by easily obtained scripts. You need updates to keep the known bugs fixed.
Les Mikesell wrote:
Mike McCarty wrote:
There is a distinction between "unmaintained" and "unsupported".
What's the difference? The bugs that were always there become known and exploitable by easily obtained scripts. You need updates to keep the known bugs fixed.
They are independent activities, though maintenance is easier with a distro which is supported. Upgrading from one update of, say FC6, to a later update is a maintenance activity which may or may not take place, even though FC6 is supported. Replacement of a version of Firefox with a later one on an FC2 machine is also a maintenance activity. Doing backups is a maintenance activity. Opening the box and vacuuming out the dust bunnies is a maintenance activity.
They are not the same thing. One may have a well-maintained but unsupported machine. I have a well-maintained MSDOS machine, for example.
One may also have an unmaintained but well-supported machine. Just don't do anything, even click the up-to-date icon or run yum, and don't do any backups.
Mike
Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
$ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux $ locate "tzdata*" [no output]
Mike
Mike McCarty wrote:
Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
$ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux $ locate "tzdata*" [no output]
It's a package, not a file. Try rpm -q tzdata
Les Mikesell wrote:
Mike McCarty wrote:
Patrick Boutilier wrote:
For FC2, if you have tzdata-2006a-2.fc2.1 you are OK.
$ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux $ locate "tzdata*" [no output]
It's a package, not a file. Try rpm -q tzdata
Thanks for the clarification.
Mike
Terry Polzin wrote:
On Wednesday 21 February 2007 12:41, Travis Bullock wrote:
Sorry if this is a repost. Just subscribed and not sure if the first one went or not.
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
Cheers,
Travis Bullock Systems Administrator Avmax Group Inc.
For FC5 my tzdata is tzdata-2006p-1.fc5
FC2, 4 are in fedora-legacy so I have no idea if they have been updated or not.
$ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux $ /usr/sbin/zdump -v US/Central|grep 2007 US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600
I dunno whether this mean that FC2 will change properly, but this is what my machine has on it. It is not completely in "sync" with Fedora Legacy, as FCL and I have some differences of opinion of what constitutes unacceptable QA policy.
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Mike
On Thu, 2007-02-22 at 22:56 -0600, Mike McCarty wrote:
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
Mike
taharka
Lexington, Kentucky U.S.A.
taharka wrote:
On Thu, 2007-02-22 at 22:56 -0600, Mike McCarty wrote:
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Mike
On Fri, 2007-02-23 at 10:14 -0600, Mike McCarty wrote:
taharka wrote:
On Thu, 2007-02-22 at 22:56 -0600, Mike McCarty wrote:
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Don't get the wrong idea, it's not you're emails in particular. Actually, the question is in regards to any person's email sent after the time change in March. Will the information on emails still be correct after the time change in March? I assume you're referring to the headers?
Mike
taharka
Lexington, Kentucky U.S.A.
taharka wrote:
On Fri, 2007-02-23 at 10:14 -0600, Mike McCarty wrote:
taharka wrote:
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Don't get the wrong idea, it's not you're emails in particular. Actually, the question is in regards to any person's email sent after the time change in March. Will the information on emails still be correct after the time change in March? I assume you're referring to the headers?
I don't understand your question very well. You are the one who brought up the subject. What time are *you* referring to, if not the one in headers?
Mike
On Fri, 2007-02-23 at 11:14 -0600, Mike McCarty wrote:
taharka wrote:
On Fri, 2007-02-23 at 10:14 -0600, Mike McCarty wrote:
taharka wrote:
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Don't get the wrong idea, it's not you're emails in particular. Actually, the question is in regards to any person's email sent after the time change in March. Will the information on emails still be correct after the time change in March? I assume you're referring to the headers?
I don't understand your question very well. You are the one who brought up the subject. What time are *you* referring to, if not the one in headers?
Yes, the time in the headers *after* the new DST changes take effect next month. Also, do you live in a U.S. time zone that observes DST?
Mike
taharka
Lexington, Kentucky U.S.A.
taharka wrote:
On Fri, 2007-02-23 at 11:14 -0600, Mike McCarty wrote:
I don't understand your question very well. You are the one who brought up the subject. What time are *you* referring to, if not the one in headers?
Yes, the time in the headers *after* the new DST changes take effect next month. Also, do you live in a U.S. time zone that observes DST?
The time in the headers is GMT.
Why do you care what the times are on *my* messages? You seem to have a particular interest in my messages. Time zones do not observe DST, States do. I live in Texas.
Mike
On Fri, 2007-02-23 at 13:37 -0600, Mike McCarty wrote:
taharka wrote:
On Fri, 2007-02-23 at 11:14 -0600, Mike McCarty wrote:
I don't understand your question very well. You are the one who brought up the subject. What time are *you* referring to, if not the one in headers?
Yes, the time in the headers *after* the new DST changes take effect next month. Also, do you live in a U.S. time zone that observes DST?
The time in the headers is GMT.
I'm aware of that.
Why do you care what the times are on *my* messages? You seem to have a particular interest in my messages. Time zones do not observe DST, States do. I live in Texas.
No need to get snippy, as I stated before, it's not *your* messages in particular. I'll just wait till the time change comes to get my answer. Also, I believe Les Mikesell answered part of what I'm asking.
Mike
taharka
Lexington, Kentucky U.S.A.
taharka wrote:
On Fri, 2007-02-23 at 13:37 -0600, Mike McCarty wrote:
taharka wrote:
On Fri, 2007-02-23 at 11:14 -0600, Mike McCarty wrote:
I don't understand your question very well. You are the one who brought up the subject. What time are *you* referring to, if not the one in headers?
Yes, the time in the headers *after* the new DST changes take effect next month. Also, do you live in a U.S. time zone that observes DST?
The time in the headers is GMT.
I'm aware of that.
Then I don't understand your confusion. If the time in the header is GMT, then it doesn't matter what time my machine displays on its screen, GMT is what is in the header.
Why do you care what the times are on *my* messages? You seem to have a particular interest in my messages. Time zones do not observe DST, States do. I live in Texas.
No need to get snippy, as I stated before, it's not *your* messages in
I'm not being snippy. Sorry if I seemed so.
particular. I'll just wait till the time change comes to get my answer. Also, I believe Les Mikesell answered part of what I'm asking.
The answer is: The only time your machine sees from my machine is GMT.
Mike
On Fri, 2007-02-23 at 15:54 -0600, Mike McCarty wrote:
The answer is: The only time your machine sees from my machine is GMT.
From your message header: Date: Fri, 23 Feb 2007 15:54:58 -0600
Your local time being 3:54 pm, at that time, which is -6 hours from GMT. That date isn't written in GMT. If you had day light savings in effect, the offset would be different. Recipients would use the two together to correlate to their own time. Programs which sort mails in date order would believe the dates, regardless. People start to see replies sorted before original postings. It gets confusing.
Because of large numbers of people with mis-set clocks, I used to sort my mail in order of reception. That can also misorder things, but tended to do it less.
These days, because I have a mail client that supports threading, and so do most people on this list, I sort using threads. I still get some things out of order (e.g. numerous replies to the same original post), but the order of replies to replies is usually right. Unless someone mangled the threading headers, didn't reply properly, or replied to one of those (simple) digest posts.
On Sat, Feb 24, 2007 at 03:45:02PM +1030, Tim wrote:
The answer is: The only time your machine sees from my machine is GMT. From your message header: Date: Fri, 23 Feb 2007 15:54:58 -0600
Your local time being 3:54 pm, at that time, which is -6 hours from GMT. That date isn't written in GMT. If you had day light savings in effect, the offset would be different. Recipients would use the two together to correlate to their own time. Programs which sort mails in date order would believe the dates, regardless. People start to see replies sorted before original postings. It gets confusing.
But the time would also be different by the exact amount of the offset. It would be "Fri, 23 Feb 2007 16:54:58 -0500". So, remote programs will do the right thing. This is exactly the same as when Indiana didn't recognize daylight saving time -- messages from Indiana and from New York still got sorted right.
Tim wrote:
On Fri, 2007-02-23 at 15:54 -0600, Mike McCarty wrote:
The answer is: The only time your machine sees from my machine is GMT.
From your message header: Date: Fri, 23 Feb 2007 15:54:58 -0600
Your local time being 3:54 pm, at that time, which is -6 hours from GMT. That date isn't written in GMT. If you had day light savings in effect, the offset would be different. Recipients would use the two together to correlate to their own time. Programs which sort mails in date order would believe the dates, regardless. People start to see replies sorted before original postings. It gets confusing.
That's broken software you are talking about. The time which is computed is GMT, period, full stop, end of story. My local time, plus offset, is GMT, always. Any program which mis-sorts is broken.
Mike
Alan wrote:
That's broken software you are talking about. The time which is computed is GMT, period, full stop, end of story. My local time, plus offset, is GMT, always. Any program which mis-sorts is broken.
<pedant>
GMT has not existed for many many years, instead we have UT and UTC.
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig
Resist One World Governments like the UN.
Mike
On Mon, Feb 26, 2007 at 09:13:17PM -0600, Mike McCarty wrote:
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig Resist One World Governments like the UN.
I can't help but notice the ISO-8859-1 charset you sent this message in. Please resend in us-ascii. Thanks.
Matthew Miller wrote:
On Mon, Feb 26, 2007 at 09:13:17PM -0600, Mike McCarty wrote:
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig Resist One World Governments like the UN.
I can't help but notice the ISO-8859-1 charset you sent this message in. Please resend in us-ascii. Thanks.
I wish it were an option on my mailer. I have to live in the world as it is.
Mike
Mike McCarty wrote:
Matthew Miller wrote:
On Mon, Feb 26, 2007 at 09:13:17PM -0600, Mike McCarty wrote:
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig Resist One World Governments like the UN.
I can't help but notice the ISO-8859-1 charset you sent this message in. Please resend in us-ascii. Thanks.
I wish it were an option on my mailer. I have to live in the world as it is.
Resist right up to the point of changing e-mail clients, huh? :-)
On Monday 26 February 2007, Matthew Miller wrote:
On Mon, Feb 26, 2007 at 09:13:17PM -0600, Mike McCarty
wrote:
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig Resist One World Governments like the UN.
I can't help but notice the ISO-8859-1 charset you sent this message in. Please resend in us-ascii. Thanks.
What are you seeing? I see regular text.
linuxmaillists@charter.net wrote:
On Monday 26 February 2007, Matthew Miller wrote:
On Mon, Feb 26, 2007 at 09:13:17PM -0600, Mike McCarty
wrote:
Certainly GMT exists, and that name is still used in Greenwich, for example. It just isn't the World Stater's name for it. UTC is an ISO (i.e. UN) thing. See my .sig Resist One World Governments like the UN.
I can't help but notice the ISO-8859-1 charset you sent this message in. Please resend in us-ascii. Thanks.
What are you seeing? I see regular text.
The ISO adopted and expanded the ASCII character set. Just like they did with the Standard C Language.
Mike
Mike McCarty wrote:
taharka wrote:
On Thu, 2007-02-22 at 22:56 -0600, Mike McCarty wrote:
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Most of the business world revolves around meetings and conference calls scheduled with calendar entries sent by email. These are automatically converted to the recipient's local time and may include alarms that pop up ahead of time. As I understand it, outlook does the adjustment when the mail is received and the DST fix isn't included in normal windows updates and was only available separately recently. That means anyone who received a calendar entry before applying the fix will have the wrong offset stored for their meeting time. There may be a fix for that too, but I haven't followed the details or whether Evolution (which can sort-of interoperate) has a similar issue. But anyway, don't underestimate the importance of being able to schedule things correctly across timezones - and expect a lot of screwups from people who rely on those popup alarms.
Les Mikesell wrote:
Mike McCarty wrote:
taharka wrote:
On Thu, 2007-02-22 at 22:56 -0600, Mike McCarty wrote:
I really don't care. I don't observe DST anyway, and would prefer that the machine not change the time it displays. I don't change my clocks.
Question, will this non-observance be reflected in sent emails/calender software, etc when the change goes into effect?
I don't understand why you would care what time/date etc. are on my e-mails. But, if you will look carefully at the information on e-mails, you'll see that they use GMT anyway, along with an offset.
Most of the business world revolves around meetings and conference calls scheduled with calendar entries sent by email. These are automatically
I am aware of this.
converted to the recipient's local time and may include alarms that pop up ahead of time. As I understand it, outlook does the adjustment when
As I stated, the time is given in GMT along with an offset. So, who cares how my system displays its local time?
[snip]
sort-of interoperate) has a similar issue. But anyway, don't underestimate the importance of being able to schedule things correctly across timezones - and expect a lot of screwups from people who rely on those popup alarms.
This is not affected by how I have my local time display set up.
Mike
"TB" == Travis Bullock tbullock@avmax.ca writes:
TB> Does anyone have a procedure that describes the process for TB> updating my Fedora Core 2, 4 and 5 implemenations in regards to TB> the DST changes in US/Canada?
FC4 and 5 should not need any fixes.
zdump -v US/Central|grep 2007
US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600
FC2, well, I just overwrote /usr/share/zoneinfo/CST6CDT with one from a newer machine and at least zdump shows the proper info. Of course, you'll have to do what's appropriate for your time zone. Unfortunately I'm not really sure if this will actually do the right thing when March 11 comes around.
- J<
Jason L Tibbitts III wrote:
"TB" == Travis Bullock tbullock@avmax.ca writes:
TB> Does anyone have a procedure that describes the process for TB> updating my Fedora Core 2, 4 and 5 implemenations in regards to TB> the DST changes in US/Canada?
FC4 and 5 should not need any fixes.
zdump -v US/Central|grep 2007
US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600
FC2, well, I just overwrote /usr/share/zoneinfo/CST6CDT with one from a newer machine and at least zdump shows the proper info. Of course, you'll have to do what's appropriate for your time zone. Unfortunately I'm not really sure if this will actually do the right thing when March 11 comes around.
That will only work if you explicitly set TZ=CST6CDT in your environment. You need to copy the appropriate timezone file to /etc/timezone for the default.
On Wed, 2007-02-21 at 12:12 -0600, Jason L Tibbitts III wrote:
"TB" == Travis Bullock tbullock@avmax.ca writes:
TB> Does anyone have a procedure that describes the process for TB> updating my Fedora Core 2, 4 and 5 implemenations in regards to TB> the DST changes in US/Canada?
FC4 and 5 should not need any fixes.
zdump -v US/Central|grep 2007
US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600
FC2, well, I just overwrote /usr/share/zoneinfo/CST6CDT with one from a newer machine and at least zdump shows the proper info. Of course, you'll have to do what's appropriate for your time zone. Unfortunately I'm not really sure if this will actually do the right thing when March 11 comes around.
- J<
fedora legacy rpms for FC2 can be found at the mirrors given here:
http://fedoralegacy.org/download/fedoralegacy-mirrors.php
On Wed, Feb 21, 2007 at 10:41:22AM -0700, Travis Bullock wrote:
Does anyone have a procedure that describes the process for updating my Fedora Core 2, 4 and 5 implemenations in regards to the DST changes in US/Canada? I am having no luck finding a valuable guide via the Web.
If your Fedora Core 2 and 4 systems are important enough that you care about the timezone they think they're in, they need to be upgraded to a supported release immediately. FC2 and FC4 are both dead.
In article 20070221184052.GA5566@jadzia.bu.edu, Matthew Miller fedora-list@redhat.com wrote:
If your Fedora Core 2 and 4 systems are important enough that you care about the timezone they think they're in, they need to be upgraded to a supported release immediately.
That's sure easy to say. I have an FC3 machine that's hosted in Texas. I'd love to update it but that's not something easily done.
-
Aaron Konstam -
Alan Cox -
ellis＠spinics.net -
James Kosin -
Jason L Tibbitts III -
Les Mikesell -
linuxmaillists＠charter.net -
Matthew Miller -
Mike McCarty -
Patrick Boutilier -
taharka -
Terry Polzin -
Tim -
Travis Bullock -
William Hooper