besides ease of installation issues (for the average user), commercial win32 games, and lib version problems with the packagers, i see no reason to stay with windows.
I'd love to see Microchip MPLAB-ICE support for Linux... or even enough of a compatibility to work with WINE. The IDE works just fine but it can't talk out the parallel ports no matter what I try. Same with a lot of chip programmers (for either BP-1200 or the old Harrison Electronics' EMP-20). So close, yet so far for electronic development.
Sure, Eagle works but there needs to be a completed sim and maybe some more fully-featured VHDL compilers. Or any kind of FPGA compiler for that manner.
So close, yet so far for the electronics people.:-)
God I hate that. Why should we have to pay to get the latest updates to our FREE software?
Blow it out your ear. Redhat needs to make money and I can't think of a better service to provide to achieve that. If you don't want to pay, take your place in queue. They're not saying no, they're saying wait, we're taking care of those who are trying to keep us afloat.
I don't use Redhat, and I don't particularly like them, but there is absolutely nothing wrong with what they're doing here.
We run it with Postgres (run away from MySQL, but GNU-RADIUSD can use it) -- it's fast for us (6k+ customers), under active development and stable as hell.
I hate to break it to you but that is what rsync does. If the file already exits where is is copying to it will send the delta (think diff but more efficant and works with binary files.) and only update the changes.
You didn't read carefully enough. and have the backing-up end copy the file and apply the changes -- I don't want one snapshot, I want a base snapshot and then any changes to be saved in an entirely new tree structure.
Basically this: Take your snapshot normally. Now ask for all the files that changed between the snapshot and today. rsync sends the diff. Now for each file mentioned in the diff, copy the entire file from the snapshot to another directory and apply the diff to that copy. Now your new directory has full files that are up to date, but only the diffs were sent over. That is not what rsync does.
'm a proud Canadian, but I have to say that the Americans are totally correct when they say Canada's military is a joke.
We're horribly underfunded but that doesn't seem to stop us from achieving international recognition as some of the best trained and highest respected soldiers on the planet.
I'd love to have our military better funded. But a joke? Give your fucking head a shake. A proud Canadian would understand where the problem comes from and not assign blame/ridicule to the military itself.
In order to own a gun you must have a licence, it is not a difficult process to go through but it stops some of the "bad people" from getting guns.
That is such utter bullshit. If you want a gun you can get one illegally very easily in Canada. I'm all for proper training and annual evaluation to keep your FAC but don't for one second believe that it keeps it out of the hands of the baddies. If you want a gun bad enough you'll go around any roadblocks.
Care to explain the difference for the uninitiated? Why can't a "snapshot" serve the same function as a backup?
I didn't say it couldn't serve as a backup, but it's not a backup in the sense that I can keep the last 6 months' worth of changes and pull from any of them. With snapshots I need to either keep 6 months of full daily backups or postprocess the daily snapshots and turn them in to differential backups.
An example might help. I do daily backups of our servers. Let's call the daily backups level 3 backups. Now each week I do a level 2 backup. Each month I do a level 1 backup, and every quarter I do a level 0 backup. Let's analyze:
Level 0 - full backup, every quarter
Level 1 - Monthly backup, just changes from the last month's backup
Level 2 - weekly, just changes from last week's backup
Level 3 - daily, just changes from yesterday
I store the Level 0 backups on DVD-(+?)RW, and the rest on two 6-tape magazines. Level 1&2 on DDS3 IIRC, and Level 3 on DDS. I can pull back any file changed in the last quarter, just like someone could pull back a file from a particular day in CVS.
With full snapshot backups this would take an insane amount of disk space. As I said earlier I could postprocess the snapshots and create differential backups but why do the extra work when tar/afio does this automatically? RSync isn't that special, and with an incredible script like Flexbackup it's even less special.
It would be great if rsync could tell the other end "this file has changed, here are the changes" and have the backing-up end copy the file and apply the changes -- i.e. allowing the creation of differential backups. That's not what it's designed for, though.
you may be interested in this [bentlogic.net]. it does backups via rsync over ssh. its still in development so i'm sure features can be added if users request them.
It's got the exact same basic problem that the backup method featured in this article has -- they're snapshots, not multi-level backups. Each "pull" is a complete copy; I can't say "Give me all the files which have changed since my last levelx backup." That's what Flexbackup (well tar or afio) allows me to do. That's exactly what rsync isn't designed to do, as far as I can tell (I've used it before but I'm not an expert at it).
I don't consider snapshot backups backups; they're snapshots.
I've been using a utility called Flexbackup -- it's a perl script which will do multi-level backups (i.e. incremental), spew to tape or file, use tar, afio or dump and compression. Oh yes, and it will use rsh/ssh for network backups. I wish I could buy the author a beer or few but it seems to be unsupported now. Oh well.
Email me if you want a copy and can't find it. I've also got a patch to fix a minor table of contents bug with modern versions of mt.
If you replace the mirror, how will you handle a malfunction on the interstate, in rush-hour traffic??? What happens if a connection goes out, or the screen just up and dies?
You'd do the exact same thing that every trucker and RVer does -- do without. It's not that critical.
I don't know about you, but I don't expect the idiot who can't understand what a latte is to properly configure a LAN firewall.
I set up and maintain firewalls and wireless networks, but I don't know what a latte is... Mind you I could find out fast enough, I'm just not the coffee type.:-)
But I think 15kv is a little high for power on the residential poles. At that voltage one would think the phone cable would experience a lot of arcing during the rain...:-)
I can't find the same link I managed to find last time, but this PowerPoint presentation has the same numbers -- 7200V to 13.2kV are present on the local distribution lines and get stepped down to your nominal 240VAC single phase and 208, 3-something (Asia), 460 and 575VAC (in Canada) three-phase used in most buildings.
I've watched many a rainstorm but I've never seen towers arc in the rain. I'm going to have to keep a closer eye out, that does sound like something to see.:-)
It's not clear to me that a good ISA power supply would avoid destroying the mb or itself in this case. Your glib, willfully ignorant advice, then, will have the effect of encouraging Dell owners that vaguely remember it to spend more money and have it go up in smoke. What they probably won't remember is the name of the jerk that gave them the bad advice. Too bad.
Yeah, especially since he's a power electronics designer and knows absolutely nothing about this kind of thing.
I have two final points: One, I'd be willing to put a good ATX power supply and a Dell motherboard up to the test -- six +5V vs three +5V only matters at rated current -- the power-up sequencing on a decent power supply would foldback instead of surging.
And two: if some random/. reader goes to do this without knowing anything about what he's tinkering with he damn-well deserves to fry his motherboard and/or power supply -- you've got your own brain and can make your own judgements, especially when you're reworking the connector and realize that there are more/fewer pins of a specific voltage than what the power supply provides.
But then again what do I know; you're the power electronics expert. Or at least the faultless detector of such.
No, what was stupid was not just running all wires to both connectors. The only difference between the two is that the keyboard clock and data are run to two pins on the keyboard (and not connected on the mouse) connector, and the same thing for the mouse. Just run all the traces to both and you can plug either in to either port.
Oh... and one more think I can't understand about UK power. They let you guys have a whole bunch of houses on a single transformer. ACH! Dangerous to your and/or your equipment depending on how stupid your neighbours are...
Power must cost a fortune where you live -- damned near every subdivision in the North America that I've been in has anywhere from 2300 to 15kv on the poles and then a pole pig for every x houses, where x is anywhere from 1 to 30 or so. Mind you the bigger ones are either underground or in those ground-level green enclosures. But one per house is certainly not the majority in NA.
I take it you've never needed to reach under a desk to plug a computer into a power strip that you can't see? Try it sometime. You can do it safely with a UK plug.
If you're not a total moron you can do it with a US (well North American) plug too. I've done it hundreds of times. You have to be a total imbecille to get a shock that will do anything more than tingle. I'm a card-carrying proponent of the "stupidity should be painful" crowd.
For instance, US explosion-risk standards are a joke compared to Australian ones. US standards are just metal to metal mating, while Aus ones have gaskets and all conduits and boxes are pressurized with nitrogen, making sparking impossible.
Interesting -- in Canada at least explosion proof is just one insanely costly box with gas-tight gaskets and connectors and (IIRC) no fewer than 1 bolt per inch along every seam. No nitrogen, mind you, but I don't recall reading about many explosions due to faulty enclosures in the natural gas and oil business we provide equipment to.
There's safe, and there's stupid-safe. The nitrogen-filled conduit et al maybe gives you an extra 9 on an already 6-nine's case... is it worth the cost? Depends on the situation I suppose. It's the same as US plugs -- sure if you ham-hand it you can get a mild shock across a finger and thumb but if you know you're reaching for a live circuit wouldn't you take the extra time to feel around for the plug head first? Or better yet get a light down there so you can see?
(e.g. the swapping of +12V with ground). The result is that upgrading or replacing the power supply with a non ($$$) Dell model will result in a short, and possibly a fire.
Or, if you buy decent power supplies, something like a sharp ticking noise or a high pitched whine as the power supply went in to current foldback in order to protect itself (and whatever it was connected to).
Seriously; spend $30 on a power supply instead of $19.99. Dell will knock you down, but they won't destroy your equipment.
The fact that there are so many clients, none of which is polished, is jabber's biggest weakness.
Yes, Jabber suffers SourceForge Syndrome but two clients in particular stand out: Gabber and my personal favourite, Psi. Both are highly polished and robust clients. Psi's even multiplatform.
Trillian is a good idea done the wrong way. Why put all that code in one application which needs to be constantly updated as the big two (especially AOL) shift their protocol around and block non-sanctioned servers? It's the wrong approach. The smaller Jabber servers don't get blocked since they're well below AOL's radar and the end user gets a much smaller application with far less code to worry about keeping updated.
he only issues I've have with PSI are general problems locating stable transport servers.
How is Psi the cause of your transport problems? That would be a jabber server issue. I compiled my own server and don't have these troubles, although I'd love to get the IRC and Yahoo transports working.
I do agree with you though, Psi is the best damned jabber client out there. I think I went through every single Linux and Java server until I settled on Psi. The others were either too MSN-ish (who the hell can work when a new message not only pops up but takes focus?!) or too new-ICQish. Psi brings the best of the old Mirabilis ICQ client to Jabber. With luck it will become standard with KDE3.1 and be fully DCOP-accessible.
XWT is the way to go these days. OS-agnostic, clear and simple separation of UI and business logic and totally, wholly extensible. I love this software.
Maybe this is a bit obvious, but maybe your ISO download has a bit wrong someplace, or burned improperly.
burned wrong or drive reading it wrong (DMA/PIO, etc.) but definately not downloaded wrong. Both HTTP and FTP are TCP, which ensures the message got across correctly. MSIE is known to bugger up downloads for extensions it doesn't know how to handle but as far as the data getting across, it's what I'd consider a six-9's certainty.
Slashdot Mirror
Win4Lin works just fine for serial/parallel access (my MPLAB-ICE works fine with it, which is more than I can say for Wine, unfortunately :-()
besides ease of installation issues (for the average user), commercial win32 games, and lib version problems with the packagers, i see no reason to stay with windows.
I'd love to see Microchip MPLAB-ICE support for Linux... or even enough of a compatibility to work with WINE. The IDE works just fine but it can't talk out the parallel ports no matter what I try. Same with a lot of chip programmers (for either BP-1200 or the old Harrison Electronics' EMP-20). So close, yet so far for electronic development.
Sure, Eagle works but there needs to be a completed sim and maybe some more fully-featured VHDL compilers. Or any kind of FPGA compiler for that manner.
So close, yet so far for the electronics people. :-)
God I hate that. Why should we have to pay to get the latest updates to our FREE software?
Blow it out your ear. Redhat needs to make money and I can't think of a better service to provide to achieve that. If you don't want to pay, take your place in queue. They're not saying no, they're saying wait, we're taking care of those who are trying to keep us afloat.
I don't use Redhat, and I don't particularly like them, but there is absolutely nothing wrong with what they're doing here.
We run it with Postgres (run away from MySQL, but GNU-RADIUSD can use it) -- it's fast for us (6k+ customers), under active development and stable as hell.
I hate to break it to you but that is what rsync does. If the file already exits where is is copying to it will send the delta (think diff but more efficant and works with binary files.) and only update the changes.
You didn't read carefully enough. and have the backing-up end copy the file and apply the changes -- I don't want one snapshot, I want a base snapshot and then any changes to be saved in an entirely new tree structure.
Basically this: Take your snapshot normally. Now ask for all the files that changed between the snapshot and today. rsync sends the diff. Now for each file mentioned in the diff, copy the entire file from the snapshot to another directory and apply the diff to that copy. Now your new directory has full files that are up to date, but only the diffs were sent over. That is not what rsync does.
'm a proud Canadian, but I have to say that the Americans are totally correct when they say Canada's military is a joke.
We're horribly underfunded but that doesn't seem to stop us from achieving international recognition as some of the best trained and highest respected soldiers on the planet.
I'd love to have our military better funded. But a joke? Give your fucking head a shake. A proud Canadian would understand where the problem comes from and not assign blame/ridicule to the military itself.
In order to own a gun you must have a licence, it is not a difficult process to go through but it stops some of the "bad people" from getting guns.
That is such utter bullshit. If you want a gun you can get one illegally very easily in Canada. I'm all for proper training and annual evaluation to keep your FAC but don't for one second believe that it keeps it out of the hands of the baddies. If you want a gun bad enough you'll go around any roadblocks.
Care to explain the difference for the uninitiated? Why can't a "snapshot" serve the same function as a backup?
I didn't say it couldn't serve as a backup, but it's not a backup in the sense that I can keep the last 6 months' worth of changes and pull from any of them. With snapshots I need to either keep 6 months of full daily backups or postprocess the daily snapshots and turn them in to differential backups.
An example might help. I do daily backups of our servers. Let's call the daily backups level 3 backups. Now each week I do a level 2 backup. Each month I do a level 1 backup, and every quarter I do a level 0 backup. Let's analyze:
With full snapshot backups this would take an insane amount of disk space. As I said earlier I could postprocess the snapshots and create differential backups but why do the extra work when tar/afio does this automatically? RSync isn't that special, and with an incredible script like Flexbackup it's even less special.
It would be great if rsync could tell the other end "this file has changed, here are the changes" and have the backing-up end copy the file and apply the changes -- i.e. allowing the creation of differential backups. That's not what it's designed for, though.
you may be interested in this [bentlogic.net]. it does backups via rsync over ssh. its still in development so i'm sure features can be added if users request them.
It's got the exact same basic problem that the backup method featured in this article has -- they're snapshots, not multi-level backups. Each "pull" is a complete copy; I can't say "Give me all the files which have changed since my last levelx backup." That's what Flexbackup (well tar or afio) allows me to do. That's exactly what rsync isn't designed to do, as far as I can tell (I've used it before but I'm not an expert at it).
I don't consider snapshot backups backups; they're snapshots.
I've been using a utility called Flexbackup -- it's a perl script which will do multi-level backups (i.e. incremental), spew to tape or file, use tar, afio or dump and compression. Oh yes, and it will use rsh/ssh for network backups. I wish I could buy the author a beer or few but it seems to be unsupported now. Oh well.
Email me if you want a copy and can't find it. I've also got a patch to fix a minor table of contents bug with modern versions of mt.
If you replace the mirror, how will you handle a malfunction on the interstate, in rush-hour traffic??? What happens if a connection goes out, or the screen just up and dies?
You'd do the exact same thing that every trucker and RVer does -- do without. It's not that critical.
[xwt] ?and slow as molasses.
I don't know what systems you're running it on but it's as fast as any win32 or linux app I run...
I don't know about you, but I don't expect the idiot who can't understand what a latte is to properly configure a LAN firewall.
I set up and maintain firewalls and wireless networks, but I don't know what a latte is... Mind you I could find out fast enough, I'm just not the coffee type. :-)
But I think 15kv is a little high for power on the residential poles. At that voltage one would think the phone cable would experience a lot of arcing during the rain... :-)
I can't find the same link I managed to find last time, but this PowerPoint presentation has the same numbers -- 7200V to 13.2kV are present on the local distribution lines and get stepped down to your nominal 240VAC single phase and 208, 3-something (Asia), 460 and 575VAC (in Canada) three-phase used in most buildings.
I've watched many a rainstorm but I've never seen towers arc in the rain. I'm going to have to keep a closer eye out, that does sound like something to see. :-)
It's not clear to me that a good ISA power supply would avoid destroying the mb or itself in this case. Your glib, willfully ignorant advice, then, will have the effect of encouraging Dell owners that vaguely remember it to spend more money and have it go up in smoke. What they probably won't remember is the name of the jerk that gave them the bad advice. Too bad.
Yeah, especially since he's a power electronics designer and knows absolutely nothing about this kind of thing.
I have two final points: One, I'd be willing to put a good ATX power supply and a Dell motherboard up to the test -- six +5V vs three +5V only matters at rated current -- the power-up sequencing on a decent power supply would foldback instead of surging.
And two: if some random /. reader goes to do this without knowing anything about what he's tinkering with he damn-well deserves to fry his motherboard and/or power supply -- you've got your own brain and can make your own judgements, especially when you're reworking the connector and realize that there are more/fewer pins of a specific voltage than what the power supply provides.
But then again what do I know; you're the power electronics expert. Or at least the faultless detector of such.
UHF (PL-259 / SO-239) - Ancient, gives an impedance spike on the line, fucking impossible to solder with anything less than a 150 watt iron.
<snort> !! hahahhahahahahahahaaha yes you've made my evening, thank you. :-) PREACH IT BROTHER!
Making mouse and keyboard identical was stupid.
No, what was stupid was not just running all wires to both connectors. The only difference between the two is that the keyboard clock and data are run to two pins on the keyboard (and not connected on the mouse) connector, and the same thing for the mouse. Just run all the traces to both and you can plug either in to either port.
Oh... and one more think I can't understand about UK power. They let you guys have a whole bunch of houses on a single transformer. ACH! Dangerous to your and/or your equipment depending on how stupid your neighbours are...
Power must cost a fortune where you live -- damned near every subdivision in the North America that I've been in has anywhere from 2300 to 15kv on the poles and then a pole pig for every x houses, where x is anywhere from 1 to 30 or so. Mind you the bigger ones are either underground or in those ground-level green enclosures. But one per house is certainly not the majority in NA.
I take it you've never needed to reach under a desk to plug a computer into a power strip that you can't see? Try it sometime. You can do it safely with a UK plug.
If you're not a total moron you can do it with a US (well North American) plug too. I've done it hundreds of times. You have to be a total imbecille to get a shock that will do anything more than tingle. I'm a card-carrying proponent of the "stupidity should be painful" crowd.
For instance, US explosion-risk standards are a joke compared to Australian ones. US standards are just metal to metal mating, while Aus ones have gaskets and all conduits and boxes are pressurized with nitrogen, making sparking impossible.
Interesting -- in Canada at least explosion proof is just one insanely costly box with gas-tight gaskets and connectors and (IIRC) no fewer than 1 bolt per inch along every seam. No nitrogen, mind you, but I don't recall reading about many explosions due to faulty enclosures in the natural gas and oil business we provide equipment to.
There's safe, and there's stupid-safe. The nitrogen-filled conduit et al maybe gives you an extra 9 on an already 6-nine's case... is it worth the cost? Depends on the situation I suppose. It's the same as US plugs -- sure if you ham-hand it you can get a mild shock across a finger and thumb but if you know you're reaching for a live circuit wouldn't you take the extra time to feel around for the plug head first? Or better yet get a light down there so you can see?
(e.g. the swapping of +12V with ground). The result is that upgrading or replacing the power supply with a non ($$$) Dell model will result in a short, and possibly a fire.
Or, if you buy decent power supplies, something like a sharp ticking noise or a high pitched whine as the power supply went in to current foldback in order to protect itself (and whatever it was connected to).
Seriously; spend $30 on a power supply instead of $19.99. Dell will knock you down, but they won't destroy your equipment.
The fact that there are so many clients, none of which is polished, is jabber's biggest weakness.
Yes, Jabber suffers SourceForge Syndrome but two clients in particular stand out: Gabber and my personal favourite, Psi. Both are highly polished and robust clients. Psi's even multiplatform.
Trillian is a good idea done the wrong way. Why put all that code in one application which needs to be constantly updated as the big two (especially AOL) shift their protocol around and block non-sanctioned servers? It's the wrong approach. The smaller Jabber servers don't get blocked since they're well below AOL's radar and the end user gets a much smaller application with far less code to worry about keeping updated.
A little off-topic, but did anyone else notice this item on the PSI page?
Yup, and slashdot rejected the story last week:
- 2002-08-25 19:44:26 [name withheld] ripping off GPL code (articles,news) (rejected)
Name removed at Justin's (Psi developer) request -- he doesn't want hordes of angry people attacking the ass who did this...yet.he only issues I've have with PSI are general problems locating stable transport servers.
How is Psi the cause of your transport problems? That would be a jabber server issue. I compiled my own server and don't have these troubles, although I'd love to get the IRC and Yahoo transports working.
I do agree with you though, Psi is the best damned jabber client out there. I think I went through every single Linux and Java server until I settled on Psi. The others were either too MSN-ish (who the hell can work when a new message not only pops up but takes focus?!) or too new-ICQish. Psi brings the best of the old Mirabilis ICQ client to Jabber. With luck it will become standard with KDE3.1 and be fully DCOP-accessible.
XWT is the way to go these days. OS-agnostic, clear and simple separation of UI and business logic and totally, wholly extensible. I love this software.
Maybe this is a bit obvious, but maybe your ISO download has a bit wrong someplace, or burned improperly.
burned wrong or drive reading it wrong (DMA/PIO, etc.) but definately not downloaded wrong. Both HTTP and FTP are TCP, which ensures the message got across correctly. MSIE is known to bugger up downloads for extensions it doesn't know how to handle but as far as the data getting across, it's what I'd consider a six-9's certainty.