Just for fun, I tried running it with the latest CVS of Wine. It installs fine (which is most of the problem with Wine these days.) It also launches fine. I wasn't able to get too far since I don't have an Australian tax ID number, but it was enough to launch the program. The help screens were written using the old MS help system and not the newer CHM, so you can use Wine's internal winhelp viewer to view it all. The controls seem to be pretty old, so I imagine the app runs fine with Wine.
I'd give their website a C- for usability. It seems way too technical for the average user to download the app in the first place. They have 4 links before the app download about patches, the description of which would be meaningless to most users and not obvious that they don't need them.
The first question you may need to answer is whether learning is your favorite hobby. If so, then go get a challenging job and join the corporate rat race. Keep in mind that the larger your company and division, the more backstabbing and politics you'll deal with.
If learning isn't your favorite hobby, then put together a list of all the stuff you like to do. Do you like to travel? Mountain bike? Scuba dive? If that's what you enjoy, then go work in that field. Believe it or not, you can find good-paying tech jobs (or just about anything else) in each of those areas. If you like to travel, look on Lonely Planet's web site for jobs. If you like to ride bikes, then check out the website of a bike manufacturer to see if they're hiring.
I worked for a small company for about 3 years and had a lot of fun doing sys admin work. It was a great learning experience and at that point in my life I enjoyed learning just about more than anything.
Then I decided I'd go skiing. Now I get paid to work for a ski resort doing IT work. In the winter I get anywhere between 40 - 100 days of skiing in. I'm actually sort of getting bored of skiing now, so I'm thinking sitting on a beach in Thailand is what I'll do. I just need to get paid for it.
You'll also need to weigh whether the greed of $$$ will override where you want to live. Ideally you'll live and work exactly where you want to. However, you might be tempted to move across the country to a place you hate just to make money.
I've thought long and hard about this since graduating from college. I've seen a lot of people do some extraordinary things. The person who runs the division I work in (with about 15,000 people) never went to college, and I'm not sure he graduated from high school. He does happen to be a genius and I suspect he would have went to college if it wasn't for the fact he was successful by the age of 18.
If I interviewed two people for a job I'd always choose the one who had ambition, creativity and a great work ethic. College degrees and intelligence would be secondary. There is a place for that, but with good leadership you can get an ambitious person to do amazing things.
The other factor that counts is common sense. Understanding the requirements of a job and relating to customers is very important. In a sense, everyone works for customers - our bosses are customers of sorts.
For anyone still in school, don't get wrapped up in your GPA but don't drop out of college either.
If you don't like the way you're being treated, this may qualify as harassment. 1. Document each instance of things he's done to you and others that you consider 'nuts'. 2. Tell him publically you don't like the way you're being treated. 3. Document each instance someone else has observed such behavior directed at you.
You then have two options. Take this to your state labor board, which may be completely ineffective if you're a salaried employee. Or, take it to a lawyer. With your hefty settlement you'll be able to afford to work on open source software full time and make the world a better place.
Your bridges are already burnt - if you can't absolutely guarantee he'll give you a positive recommendation then you have no reason to maintain playing his games.
I think there's three reasons, two of which are undeniable. First, there's a lot of legacy apps out there that are unsupported and won't be updated because the vendor went out of business. Personally I support 3 applications like that. So it becomes a matter of finding a native replacement which may not exist or be worth switching too if works with Wine. Second, there's a phenomenal amount of software that's been created for Windows. All kinds of odd little apps for doing things like interior design and such that don't exist on Linux. Finally, and this is the item a lot of people will disagree with, many commercial applications are just plain better on Windows. More effort has been put into designing UI's and such. (For the record, I personally use free software always as my first choice based on the principle of free, as in libre, software.)
I'm sure someone else has already pointed it out, but fuck Adobe. They've flexed their IP muscle onto more than enough people, they deserve to get screwed over. (fontforge, et al)
But why would not having contact with DSN have anything to do with losing attitude? Voyager has a working sun sensor and star tracker, so there shouldn't be a problem reestablishing a link in a year or five. Sure.. not monitoring it may mean a problem that lingers could go from bad to worse, but that could easily happen now as well.
I'm usually of the opinion that removing anything from NASA's budget was awful. Especially in this day and age when DoD and DARPA programs often waste more money on less productive research that's not even open to the public. (Those among us who've used Linux for a long time will remember the reason Linux had excellent network drivers even in early versions was because of Don Becker. Likewise with Beowulf.)
However, in this case I don't think it's a bad thing to slash $4 million. There's only a questionable amount of useful data coming from the telemetry equipment of Voyager. The only useful stuff might come when Voyager hits the heliopause. Anyway, it's not like this program will permanently disappear. Maybe in the future it'll get added back in. More likely, an engineer will find a few spare minutes on the DSN and schedule some time for an uplink.
Stop thinking purely as a techie/develper for a second, will you? THINK for a second about the whole, big picture, not just implications for developers.
IBM is pushing Linux, has it's own line of pretty nice processors and just sold off it's PC division. And now they want native ports of applications to thier chosen OS and platform. Hmmmmm...
That was thinking wihtout techie hat on. They're basically saying that the way to get an app on Power is to rewrite it from scratch. IBM will save the first few hours of frustration by showing people how to get started. The idea of that scares the hell out of any ISV and it's sort of a tactic of last resort.
If I was an ISV with an app that could be ported to an OS with second-tier priority on an architecture that has almost neglible marketshare, I doubt I'd do it. The payoff just isn't there.
I don't get it. IBM seems to have some massive aversion to Wine. It seems to me the easiest thing they could do would be to port Wine to the Power architecture. It would consume a little time, but surely nothing as suggesting every application developer rewrite massive parts of their Win32 app. These articles basically suggest an app needs to be rewritten from scratch, which will immediately make any ISV laugh at Linux on Power. (Why would you bother porting a Win32 app to Power? Why not just keep using a cheap Intel box running Linux?)
Winelib was specifically designed to help with porting and you can do it tiny controlled steps: 1. Port from MSVC++ to the MinGW compiler and develop things like a Makefile. 2. Test the app. 3. Port the code from Windows to Linux (not as trivial as you'd think - there are problems with case sensitivity, etc.) 4. Test compiling. 5. Finish compiling using the custom Wine tools, such as winegcc (a wrapper around gcc that makes it behave like MinGW). 6. Test your Winelib app. 7. Begin ripping out chunks of Win32 specific code and replace them with native equivalents - Wine dialogs for KDE/GNOME ones. 8. Test
That's a valid and controlled migration path. Asking developers to basically rewrite massive chunks of code involving threading, memory management, and other such exciting things is a nightmare. Oh, and after rewriting you get to debug it all. Would you trust an enterprise app that just had it's whole threading model replaced?
The part I find amazing though, is just how much they haven't addressed. What do you do when your app relies on COM? What about Windows common controls? What about networking?
Anyway, it looks like IBM missed the ball - a few engineers porting Wine to Power could have solved many of their migration issues. It certainly would have solved every single one mentioned in these articles. Instead they want the software developers of the world to take on the task of rewriting their apps.
Okay, if you're the cool admin dude who's into building his own servers and installing his favorite distribution (with most packages custom compiled from scratch, of course) you're NOT the person most enterprise IT departments want to hire. PHB's like cookie-cutter OS installations that anyone can walk in and admin. (That's because they're scared to death you're going to quit and they want to hire someone off the street as soon as possible to replace you.)
It's also because you and your staff can't be available each and every second of each and every day. Okay, well, I'm sure you think you can. But when your Tech I guy gets drunk, you're on vacation, and the website goes down because a janitor tripped over the ethernet connection, what happens?
That's right - your boss gets to field the phone call. He's gonna be one pissed off asshole if he doesn't have tech support to call - he's probably the type of guy who has no clue what Apache is or how it's running. Instead, he wants to pick up the phone and call someone like Red Hat to walk him through it. So my advice is:
When your boss picks up the phone to call tech support on your Linux distribution, what do you want them to say?
If you're lucky, your support agreement gives you direct access to a tech. Not just any tech, one you know by name. In turn, that tech knows you, where you live, and what color your car is. He'll watch your back for you when you're gone. If you can build a relationship like that with a distribution, that's the one you want to buy.
Everything else is cake - any good admin can make any Linux distribution do anything.
Having worked in the telco industry for about 4.5 years, I can attest that every dealing I've had with AT&T is truly an awful experience. Whereas SBC seems pretty decent. Having read about SBC's business practices, they seem smarter than this. Is this the inverse of the Qwest/USWest merger? (Another truly awful deal that I imagine Qwest regrets). Here we have the baby Bell buying the long haul carrier. Now, in this case I think it will work better than Qwest/USWest because SBC won't be inheriting a local loop cable plant. Now, everyone start counting how many times they hear the phrase, "consumers will benefit because.."
(..because we'll give the megacorporation more cash to brainwash us with.)
Anyway, what I was really wondering is what impact, if any, this might have on Linux. If I recall correctly, SBC has used Linux heavily for multiple installations. And I heard AT&T is known for having a pretty strong Unix heritage too as well as being known for developing some hardware that uses it. I wonder if there's a chance we'll see anything benefit Linux. Anyone know if SBC has ever released stuff back to the community?
Oh, and congratulations to all the workers who got to read on Slashdot about the new company they'll end up working for.
A really interesting split to study is what happened to Wine a few years ago. In 2002, Wine was under the X11/BSD license. A lot of people wanted to move to LGPL and a pretty big debate occurred. In the end, a vote was taken and the decision to move to LGPL was made.
Obviously that's not a concern you had, but we'll assume you guys did do some kind of vote for forking the project and that it was a fairly civil process. If you didn't - well, that was the start of your problems and unfortunately it's not that easy to go back.
Now, if the fork you're talking about has multiple developers, what you should do is something similar to what Wine (actually Wine's X11 fork, ReWind) did - contact each developer individually and ask them for permission to use their patches. You seem to have one person who disagrees and it doesn't seem like you'll get their consent, but shouldn't you at least ask the other developers? Then, make it easy for people to submit patches against your project as well as the one they regularly submit to.
So that's the nice thing to do. Keep in mind what you're probably doing is only a short-term solution. Eventually your codebases will diverge enough that it may not be worth trying to integrate patches. At that point, you're going to have to realize that two teams are duplicating each others work and figure out whether or not that's productive.
Try to keep in mind why you guys chose the GPL in the first place. If it's a license you truly believe in, then it's pretty hard to argue against people reusing bits of code.
Okay, so I live in a weird part of the country. We have 4 world class ski resorts within 20 minutes of my front door: A Basin, Keystone, Breckenridge, Copper Mtn. Side jobs are extremely common up here. So what do I do for a side job? Last year I worked Competition Services for Breckenridge - we put on huge events, like X Games qualifiers. I've also worked in ski rental and tune shops.
Oh, and since my main job is telecom, I get asked to run cabling for friends. At various times I've had my entire refrigerator full of beer because of it.
Simple solution for me - I'm just not going to buy Intel wireless products. Fortunately it's a big enough market that it's fairly easy not to care about them. In my own little world I can pretend my purchasing power actually means something to a giant, multinational corporation.
First off, this stuff isn't hard. Anyone with a PBX and some voice circuits (such as ISDN PRI's) can do this. However, what they can't spoof is ANI since that's configured on the telco side.
More distressing is if they allow calls to somewhere like 911. Most 911 centers are configured to receive ANI (which again, is different than caller ID as well as the billed telephone number), so they would definitely receive the ANI of where these voice circuits terminate. However, they may receive caller ID and may even base location on it. In that case I would think the public utilities commissions would immediately take interest in this.
Of course, these folks probably aren't that dumb, so they probably don't allow 911 calls. One thing I didn't consider is that these guys might have connections (such as, they might be their own CLEC) and can really spoof the ANI too.. not sure what happens there.. all bets are off and the chance they'll get in trouble is pretty high.
Everyone has a lesson to teach you. Maybe it's a woman who'll show you what heartbreak is. Maybe it's a bum on the street who shows you poverty. Take time to learn people's stories.
Use rigid conduit. Flexible conduit is an absolute nightmare to pull through after the ground settles, to the point of being impossible. Use multiple 3" conduits between the home with underground vaults to serve as splice points. Place pull boxes in appropriate locations if you need to change direction. Don't forget to run mule tape through the conduits before you seal it up.
Then, lay in only what you need. Outside plant cat5 is just becoming available. With HDSL you can easily get several miles out of out. (Hell, you could easily get several miles out of cat3 & HDSL too and save a ton of money.) You'll probably want to pull RG6 coax at the same time. Leave one conduit completely empty for something to pull later. I've yet to see a viable fiber for the home.
Well Jer, I'd love to ask you about the CXO 3.0 release, but I'm afraid in this crowd the questions would never get modded up high enough. So...
At WineConf you were really interested in Jan Kratochvil's Captive NTFS project to run the native NT filesystem driver under Linux using ReactOS' ntoskrnl.exe and Wine. Are you guys considering development of any products that integrate Wine and Linux at a lower level with Windows drivers? In theory a similar mechanism could support Windows printer drivers under Linux as well as many other specialized areas. Or, is Linux hardware support sufficient that no value would be added? If you were interested, how much would you have to bribe Alexandre?
I asked Jeremy a similar question at WineConf. The exact answer to your question is "no". They are not working with tax software publishers.
However, that leads to the next question of, "has Codeweavers ever considered supporting the tax software themselves?" While personally I've always thought it was a good idea, I get the impression that it would be a difficult product category for them. And personally, I'd be scared as hell supporting an application that needed to ensure things such as accurate accounting and electronic filing. It's one thing if a Word document gets corrupted, but not having your taxes in on the deadline is another matter. I don't blame Jeremy for being hesitant about that.
Slashdot Mirror
Just for fun, I tried running it with the latest CVS of Wine. It installs fine (which is most of the problem with Wine these days.) It also launches fine. I wasn't able to get too far since I don't have an Australian tax ID number, but it was enough to launch the program. The help screens were written using the old MS help system and not the newer CHM, so you can use Wine's internal winhelp viewer to view it all. The controls seem to be pretty old, so I imagine the app runs fine with Wine.
I'd give their website a C- for usability. It seems way too technical for the average user to download the app in the first place. They have 4 links before the app download about patches, the description of which would be meaningless to most users and not obvious that they don't need them.
The first question you may need to answer is whether learning is your favorite hobby. If so, then go get a challenging job and join the corporate rat race. Keep in mind that the larger your company and division, the more backstabbing and politics you'll deal with.
If learning isn't your favorite hobby, then put together a list of all the stuff you like to do. Do you like to travel? Mountain bike? Scuba dive? If that's what you enjoy, then go work in that field. Believe it or not, you can find good-paying tech jobs (or just about anything else) in each of those areas. If you like to travel, look on Lonely Planet's web site for jobs. If you like to ride bikes, then check out the website of a bike manufacturer to see if they're hiring.
I worked for a small company for about 3 years and had a lot of fun doing sys admin work. It was a great learning experience and at that point in my life I enjoyed learning just about more than anything.
Then I decided I'd go skiing. Now I get paid to work for a ski resort doing IT work. In the winter I get anywhere between 40 - 100 days of skiing in. I'm actually sort of getting bored of skiing now, so I'm thinking sitting on a beach in Thailand is what I'll do. I just need to get paid for it.
You'll also need to weigh whether the greed of $$$ will override where you want to live. Ideally you'll live and work exactly where you want to. However, you might be tempted to move across the country to a place you hate just to make money.
I'm less amazed that Be's still alive than I am that you have a graphic for it.
I've thought long and hard about this since graduating from college. I've seen a lot of people do some extraordinary things. The person who runs the division I work in (with about 15,000 people) never went to college, and I'm not sure he graduated from high school. He does happen to be a genius and I suspect he would have went to college if it wasn't for the fact he was successful by the age of 18.
If I interviewed two people for a job I'd always choose the one who had ambition, creativity and a great work ethic. College degrees and intelligence would be secondary. There is a place for that, but with good leadership you can get an ambitious person to do amazing things.
The other factor that counts is common sense. Understanding the requirements of a job and relating to customers is very important. In a sense, everyone works for customers - our bosses are customers of sorts.
For anyone still in school, don't get wrapped up in your GPA but don't drop out of college either.
The Wine project has put together a list of resources to help someone thinking about this figure out a project. You might find the following helpful:
If you don't like the way you're being treated, this may qualify as harassment.
1. Document each instance of things he's done to you and others that you consider 'nuts'.
2. Tell him publically you don't like the way you're being treated.
3. Document each instance someone else has observed such behavior directed at you.
You then have two options. Take this to your state labor board, which may be completely ineffective if you're a salaried employee. Or, take it to a lawyer. With your hefty settlement you'll be able to afford to work on open source software full time and make the world a better place.
Your bridges are already burnt - if you can't absolutely guarantee he'll give you a positive recommendation then you have no reason to maintain playing his games.
I think there's three reasons, two of which are undeniable. First, there's a lot of legacy apps out there that are unsupported and won't be updated because the vendor went out of business. Personally I support 3 applications like that. So it becomes a matter of finding a native replacement which may not exist or be worth switching too if works with Wine. Second, there's a phenomenal amount of software that's been created for Windows. All kinds of odd little apps for doing things like interior design and such that don't exist on Linux. Finally, and this is the item a lot of people will disagree with, many commercial applications are just plain better on Windows. More effort has been put into designing UI's and such. (For the record, I personally use free software always as my first choice based on the principle of free, as in libre, software.)
I'm sure someone else has already pointed it out, but fuck Adobe. They've flexed their IP muscle onto more than enough people, they deserve to get screwed over. (fontforge, et al)
But why would not having contact with DSN have anything to do with losing attitude? Voyager has a working sun sensor and star tracker, so there shouldn't be a problem reestablishing a link in a year or five. Sure.. not monitoring it may mean a problem that lingers could go from bad to worse, but that could easily happen now as well.
I'm usually of the opinion that removing anything from NASA's budget was awful. Especially in this day and age when DoD and DARPA programs often waste more money on less productive research that's not even open to the public. (Those among us who've used Linux for a long time will remember the reason Linux had excellent network drivers even in early versions was because of Don Becker. Likewise with Beowulf.)
However, in this case I don't think it's a bad thing to slash $4 million. There's only a questionable amount of useful data coming from the telemetry equipment of Voyager. The only useful stuff might come when Voyager hits the heliopause. Anyway, it's not like this program will permanently disappear. Maybe in the future it'll get added back in. More likely, an engineer will find a few spare minutes on the DSN and schedule some time for an uplink.
Stop thinking purely as a techie/develper for a second, will you? THINK for a second about the whole, big picture, not just implications for developers.
IBM is pushing Linux, has it's own line of pretty nice processors and just sold off it's PC division. And now they want native ports of applications to thier chosen OS and platform. Hmmmmm...
That was thinking wihtout techie hat on. They're basically saying that the way to get an app on Power is to rewrite it from scratch. IBM will save the first few hours of frustration by showing people how to get started. The idea of that scares the hell out of any ISV and it's sort of a tactic of last resort.
If I was an ISV with an app that could be ported to an OS with second-tier priority on an architecture that has almost neglible marketshare, I doubt I'd do it. The payoff just isn't there.
I don't get it. IBM seems to have some massive aversion to Wine. It seems to me the easiest thing they could do would be to port Wine to the Power architecture. It would consume a little time, but surely nothing as suggesting every application developer rewrite massive parts of their Win32 app. These articles basically suggest an app needs to be rewritten from scratch, which will immediately make any ISV laugh at Linux on Power. (Why would you bother porting a Win32 app to Power? Why not just keep using a cheap Intel box running Linux?)
Winelib was specifically designed to help with porting and you can do it tiny controlled steps:
1. Port from MSVC++ to the MinGW compiler and develop things like a Makefile.
2. Test the app.
3. Port the code from Windows to Linux (not as trivial as you'd think - there are problems with case sensitivity, etc.)
4. Test compiling.
5. Finish compiling using the custom Wine tools, such as winegcc (a wrapper around gcc that makes it behave like MinGW).
6. Test your Winelib app.
7. Begin ripping out chunks of Win32 specific code and replace them with native equivalents - Wine dialogs for KDE/GNOME ones.
8. Test
That's a valid and controlled migration path. Asking developers to basically rewrite massive chunks of code involving threading, memory management, and other such exciting things is a nightmare. Oh, and after rewriting you get to debug it all. Would you trust an enterprise app that just had it's whole threading model replaced?
The part I find amazing though, is just how much they haven't addressed. What do you do when your app relies on COM? What about Windows common controls? What about networking?
Anyway, it looks like IBM missed the ball - a few engineers porting Wine to Power could have solved many of their migration issues. It certainly would have solved every single one mentioned in these articles. Instead they want the software developers of the world to take on the task of rewriting their apps.
It's also because you and your staff can't be available each and every second of each and every day. Okay, well, I'm sure you think you can. But when your Tech I guy gets drunk, you're on vacation, and the website goes down because a janitor tripped over the ethernet connection, what happens?
That's right - your boss gets to field the phone call. He's gonna be one pissed off asshole if he doesn't have tech support to call - he's probably the type of guy who has no clue what Apache is or how it's running. Instead, he wants to pick up the phone and call someone like Red Hat to walk him through it. So my advice is:
When your boss picks up the phone to call tech support on your Linux distribution, what do you want them to say?
If you're lucky, your support agreement gives you direct access to a tech. Not just any tech, one you know by name. In turn, that tech knows you, where you live, and what color your car is. He'll watch your back for you when you're gone. If you can build a relationship like that with a distribution, that's the one you want to buy.
Everything else is cake - any good admin can make any Linux distribution do anything.
I give up! I hope you are being sarcastic.
And you would be correct.
Having worked in the telco industry for about 4.5 years, I can attest that every dealing I've had with AT&T is truly an awful experience. Whereas SBC seems pretty decent. Having read about SBC's business practices, they seem smarter than this. Is this the inverse of the Qwest/USWest merger? (Another truly awful deal that I imagine Qwest regrets). Here we have the baby Bell buying the long haul carrier. Now, in this case I think it will work better than Qwest/USWest because SBC won't be inheriting a local loop cable plant. Now, everyone start counting how many times they hear the phrase, "consumers will benefit because.."
(..because we'll give the megacorporation more cash to brainwash us with.)
Anyway, what I was really wondering is what impact, if any, this might have on Linux. If I recall correctly, SBC has used Linux heavily for multiple installations. And I heard AT&T is known for having a pretty strong Unix heritage too as well as being known for developing some hardware that uses it. I wonder if there's a chance we'll see anything benefit Linux. Anyone know if SBC has ever released stuff back to the community?
Oh, and congratulations to all the workers who got to read on Slashdot about the new company they'll end up working for.
A really interesting split to study is what happened to Wine a few years ago. In 2002, Wine was under the X11/BSD license. A lot of people wanted to move to LGPL and a pretty big debate occurred. In the end, a vote was taken and the decision to move to LGPL was made.
Obviously that's not a concern you had, but we'll assume you guys did do some kind of vote for forking the project and that it was a fairly civil process. If you didn't - well, that was the start of your problems and unfortunately it's not that easy to go back.
Now, if the fork you're talking about has multiple developers, what you should do is something similar to what Wine (actually Wine's X11 fork, ReWind) did - contact each developer individually and ask them for permission to use their patches. You seem to have one person who disagrees and it doesn't seem like you'll get their consent, but shouldn't you at least ask the other developers?
Then, make it easy for people to submit patches against your project as well as the one they regularly submit to.
So that's the nice thing to do. Keep in mind what you're probably doing is only a short-term solution. Eventually your codebases will diverge enough that it may not be worth trying to integrate patches. At that point, you're going to have to realize that two teams are duplicating each others work and figure out whether or not that's productive.
Try to keep in mind why you guys chose the GPL in the first place. If it's a license you truly believe in, then it's pretty hard to argue against people reusing bits of code.
Okay, so I live in a weird part of the country. We have 4 world class ski resorts within 20 minutes of my front door: A Basin, Keystone, Breckenridge, Copper Mtn. Side jobs are extremely common up here. So what do I do for a side job? Last year I worked Competition Services for Breckenridge - we put on huge events, like X Games qualifiers. I've also worked in ski rental and tune shops.
Oh, and since my main job is telecom, I get asked to run cabling for friends. At various times I've had my entire refrigerator full of beer because of it.
Simple solution for me - I'm just not going to buy Intel wireless products. Fortunately it's a big enough market that it's fairly easy not to care about them. In my own little world I can pretend my purchasing power actually means something to a giant, multinational corporation.
By the way, that "someone else" was Jeremy White - the CEO of CodeWeavers.
First off, this stuff isn't hard. Anyone with a PBX and some voice circuits (such as ISDN PRI's) can do this. However, what they can't spoof is ANI since that's configured on the telco side.
More distressing is if they allow calls to somewhere like 911. Most 911 centers are configured to receive ANI (which again, is different than caller ID as well as the billed telephone number), so they would definitely receive the ANI of where these voice circuits terminate. However, they may receive caller ID and may even base location on it. In that case I would think the public utilities commissions would immediately take interest in this.
Of course, these folks probably aren't that dumb, so they probably don't allow 911 calls. One thing I didn't consider is that these guys might have connections (such as, they might be their own CLEC) and can really spoof the ANI too.. not sure what happens there.. all bets are off and the chance they'll get in trouble is pretty high.
Everyone has a lesson to teach you. Maybe it's a woman who'll show you what heartbreak is. Maybe it's a bum on the street who shows you poverty. Take time to learn people's stories.
Gotcha. I'll submit a patch now, but it may take a week for Newman to get it changed.
Use rigid conduit. Flexible conduit is an absolute nightmare to pull through after the ground settles, to the point of being impossible. Use multiple 3" conduits between the home with underground vaults to serve as splice points. Place pull boxes in appropriate locations if you need to change direction. Don't forget to run mule tape through the conduits before you seal it up.
Then, lay in only what you need. Outside plant cat5 is just becoming available. With HDSL you can easily get several miles out of out. (Hell, you could easily get several miles out of cat3 & HDSL too and save a ton of money.) You'll probably want to pull RG6 coax at the same time. Leave one conduit completely empty for something to pull later. I've yet to see a viable fiber for the home.
Well Jer, I'd love to ask you about the CXO 3.0 release, but I'm afraid in this crowd the questions would never get modded up high enough. So...
At WineConf you were really interested in Jan Kratochvil's Captive NTFS project to run the native NT filesystem driver under Linux using ReactOS' ntoskrnl.exe and Wine. Are you guys considering development of any products that integrate Wine and Linux at a lower level with Windows drivers? In theory a similar mechanism could support Windows printer drivers under Linux as well as many other specialized areas. Or, is Linux hardware support sufficient that no value would be added? If you were interested, how much would you have to bribe Alexandre?
I asked Jeremy a similar question at WineConf. The exact answer to your question is "no". They are not working with tax software publishers.
However, that leads to the next question of, "has Codeweavers ever considered supporting the tax software themselves?" While personally I've always thought it was a good idea, I get the impression that it would be a difficult product category for them. And personally, I'd be scared as hell supporting an application that needed to ensure things such as accurate accounting and electronic filing. It's one thing if a Word document gets corrupted, but not having your taxes in on the deadline is another matter. I don't blame Jeremy for being hesitant about that.