The acronym "FUD" does not mean "saying bad things about a program". FUD stands for "Fear, Uncertainty and Doubt".
Almost correct. Taken purely as an acronym, that is what FUD means. However the definition has grown to include tactics including half-truths and downright wrong information. Your statements could have been taken as FUD as you were saying that PostgreSQL is notoriously slow. That's just like "Linux is is useless compared to Windows on the desktop," or "MySQL doesn't support transactions." These things may have been true in the past but are not now, so they are considered statements of FUD. Back to my particular statment: you're casting doubt over the performance of the system.
The word "notorious" does not mean extreme. It means "well noted".
That is exactly correct. Your well-noted observation that PostgreSQL is slow is dated and unsubstantiated. Even older versions of PostgreSQL fare much better than MySQL when you start doing more than one update to a table at a time or involve anything but trivial inserts and selects. Earlier versions also had synchronous disk access defaulted on which hurt performance signficantly. Both of these facts are well-noted as well, but you did not bring them up, which to me also helps the FUD claim: you're only telling half the story.
I'm not really a passionate defender of all things Postgres; I just hate seeing the same old tired and dated arguments brought up again and again as they simply don't apply anymore.
I know what the words mean; don't try to cast uncertainty and doubt over my English proficiency, please.
So, you agree that postgres is slower, but it's FUD when I say it's slower. Whatever, dude.
Read your comment again:
Postgres is rock solid, but notoriously slow.
"Nortoriously slow" is where I have the problem. It's not notoriously slow. MySQL is marginally faster than PostgreSQL on simple insert/select statements, but that's it. So yes, you are spreading fud, dude.
Postgres is rock solid, but notoriously slow. MySQL is wicked fast, but doesn't scale well.
Oh puh-lease. That old "postgres is slow" arguement is ancient. While mysql may be faster for simple insert/selects, that's where it stops, and compared to today's postgres it's not that much faster. Update your FUD, please.
I've been using the full-size Palm keyboard for a year and it rocks.
The biggest problem I've found with my folding keyboard and Vx is that it the keyboard seems "slow" -- I can easily out-type it. Is there a driver fix or OS upgrade which addresses this?
My birthday is 5/5. I found out after marrying my wife that her birthday is 8/8. My firstborn's birthday is 11/11 (which if you add 5 and 8 you get 13, is octal for 11). It's too bad my other kids didn't follow pattern, as my stepson's birthday is 5/24 (May 2-4, a big drinking party day for you non-Canadians), and my youngest son's birthday is 2/7, which really isn't special other than that is his birthday.:-)
My age in hex, I hadn't thought of that before... 1a this year...
I wonder if your hardware isn't going bad. I too run DPT SmartRAID controllers. A 2654U2 to be exact (2-channel version) in a 440LX P2/266 (we're network bound, not CPU bound) which is used for fileserving about 50 people in a file-heavy office environment. Before that, it was a SmartRAID V with the hardware cache/RAID card (which is in use ino another, heavier-hit webserver).
Zero stability issues on both. The 2654U2 has a 5-drive RAID5 + hot spare (UW2 SCA drives) on one channel and a 6x24 DDS-3 on another. I've done some pretty I/O intense things on this controller (including rebuilding the array during office hours) with no problems at all. This is on kernel 2.4.17. The SmartRAID V is on a 2.2.14 system which has about 50 colocated web and mail sites (it does a pretty good job of keeping the T1 busy). It runs a RAID1+0 array with really old Seagate Baracuda SCSI-1 drives and a single external DDS-3 for backup. Again, zero stability issues. I'd buy these again without hesitating.
Perhaps you need to delve deeper into the problem. The 2654U2 did not like the original P90 system the server used to be; we had bad issues there and the tech basically said that the original PCI spec was not good enough for the card. Upgrade the motherboard and all was fine. If you're running 2.4, make sure you're in the.16/.17 kernels, as earlier 2.4 kernels had issues with all manner of things, but not specifically the DPT I2O drivers, IIRC.
Both of these systems run the kernel drivers and use the dptutil software that DPT used to have (which you're right, has gone the way of the dodo after Adaptec's assimilation of DPT); what specifically can you do to cause problems? I don't think it's the card/drivers in general but if you give me a test or two I can run to see if I'm affected as well we might be able to fix this.
Slashdot's braindead lameness filter is not letting me post my dptutil -L output. Sorry.
Do any Canadians (perhaps only Ontarians) remember the ICON computers they used to have in elementary and high schools?
Yup. Used 'em in Grade 7/8 IIRC at Stanley Park Senior Public in Kitchener, ON. (Grade 7 would have been '89?) -- I got booted out of the room after a while for dicking around at the command prompt they boot up with, trying to get in to something I had no idea about at the time.
I've got one now (had two) -- they cut off the keyboard though, and I've got to figure out what pins go where (the connector's gone) but I'd love to boot it up again. You've got the specifications exactly right: 80186 (basically a controller version of the 8086, it includes the PIC, DMA, PIT and a few other of the 82xx-series of support chips in the processor package itself), I think about 640k of memory (weird staggered-SIPP package), arcnet, EGA or VGA display. Gray case that boots up blue and spends 99% of its time displaying blue background.:-)
I bet you could get something like ELKS running on it without much trouble.
Man... I remember the *sound* of the room they were in. the server(s) (I believe we had two, one for each double row of ICONs, about 20-24 ICONs per server) with physically ENORMOUS hard drives and fans and fans and fans... in a room with no sound suppression. It sounded like a large colo facility does today, I bet.
Exactly what I wanted to edit...:-) Yeah I know kmenuedit works fine for the app menu but I wasn't interested in that. Oh well, I thought I may have had the problem solved.
AFAIK, the bridging code is loaded to the PCMCIA card each boot. Did they manage to keep the file and just replay it or did they reverse-engineer the bridging code?
Not that I am really concerned, bridging a wireless LAN to your wired LAN is bad news unless there is zero need for security (aka my home).
What you're saying is equivalent to one of the many post on using VI when the discussion's topic is IDEs. fine if it does the job for you but 90% of people out there want the fully integrated DEs like GNOME and KDE.
If you can tell me how to alter the menus for right-click (on desktop) and middle button click on desktop with KDE I'll use it (Kwin). Eliminate the panel and give me desktop menus; so far nobody has been able to tell me how to do so (including the gurus in #kde on openprojects), so until then WindowMaker has the features I need and KWin is the slow one with the lack of features.
Eventually I got tired of it crapping out on me and switched over to KDE, which, although not as pretty, seems to run much faster and with fewer hiccups.
I agree for the most part. I'm running KDE3.0b1 (well WindowMaker 0.80.0 with a lot of KDE apps) but I've run across an annoying problem with multi-line edit boxes (not all of 'em, but most) -- QT3 has a HORRIBLY slow repeat rate in most of those boxes! It's quicker for me to mouse over and click and return to the keyboard than it is to cursor. Acutally this/. window is one of them (Konqueror) that has this problem. y Psi message window is another one (which isn't KDE at all, just QT3). qtconfig doesn't help since it doesn't have any way to change the repeat rates.
I have to agree, 2.4.17 is rock solid in my opinion.
I'll third that.:-) I have had no trouble with.16 or.17 with or without the preemptable kernel patch. Win4Lin has some issues which occassinally lock up my notebook good and hard but when I'm not running with their kernel "enhancements" I have yet to experience a crash here.
My server, however, seems to be showing its age... Abit BP6, dual Celeron 466 (not overclocked) -- I get good solid hangs that even kdb doesn't let me investigate when I have heavy traffic on the HPT366 interface. Disabling DMA on the drives on those controllers seems to help but I've bought a HPT370 PCI card to try and eliminate the problem. I've gotten addicted to dual processor computing on the desktop and can't afford a nice Athlon MP system yet.:-/
Re:I resent the underlying sexism of your comment.
on
The Ultimate S.U.V.
·
· Score: 2
Its next to impossible to see around the average SUV, creating problems when someone is trying to maneaver around you, but you probably have never experienced this, so you wouldn't know.
So how do you deal with the 18-wheelers on the highways? Good lord, if you can't see, you don't manouvre. And you can almost always peek around any vehicle to see past it. Failing that, BACK OFF! Your visibility increases when you don't have your fiat's hood under my Jeep's ass-end.
Re:I resent the underlying sexism of your comment.
on
The Ultimate S.U.V.
·
· Score: 2
Get a minivan. I honestly believe that SUVs should require a separate license, and hefty registration fees. And automatic liability in any accident situation.
I'll take my Jeep, thanks. We have both, a Pontiac Transport and a Jeep Grand Cherokee. I drive the Jeep because I often drag around equipment that won't fit in a trunk and don't require the extreme size of the minivan with the seats out, and I also do a lot of northern Ontario driving in winter. And the odd time I have to do so with a couple other people. My wife transports 3 kids around and flips a couple seats up for groceries and stuff.
From your next post:
If you're specifically driving a vehicle that's designed to resist damage, and I'm driving one that's designed to write itself off, on impact, for safety reasons, then yes, you should have automatic liability. Oh, and all vehicles should come with cell phone jammers that are on when the car is running.:-)
So if you jump out in front of me at an intersection when I have the right of way, it's my fault just because I paid more for a vehicle that won't crumble? Blow me. Double that for the phone jammer comment. If you can't handle driving in decent weather with light traffic and talk on a cell phone, that is your problem, not mine. I happen to be able to control my vehicle when I'm distracted, and I also have the presence of mind to ignore/drop the cellphone when things happen.
Anyway (desperately trying to find the original thread), SUVs aren't just for offroad. Trucks and cars can only get you so far, and minivans definately have advantages in medium-size people movers. But SUVs are idea for people like me.
I've always liked the idea behind PAM but the implementation blew chunks. I can't get through to either of the links in the article but can someone in the know explain how this is different from PAM?
Yeah, KWord works halfassed with.doc, but I can't get it to read an.rtf for the life of me. This is unfortunate because I believe that.rtf would work a lot better for getting formatting and such correct.
Also, it is useful to recall that microwave ovens operate on 2400 MHz because this is the most efficient frequency for heating water. One watt is enough to cause some RF heating and potentially be hazardous to you health. Don't look at the business end of that yagi!
While I don't condone pointing a highly-directional antenna through you to test, 1W is nowhere near the power of even the smallest microwave ovens. I believe my old beastor is a 750W microwave, and the little'uns are 100-150W.
Aside: Having 1W at the output of the RF amp is not the same as what's coming out of that yagi; highly directional antennas focus that 1W into something (potentially) much, much higher. Is that 1W ERP or 1W at the amp? Remember that LED-communications system on/. a week or so ago? by using fresnel lenses the effective optical power was 10kW from a 650mW LED! Directional antennas can do some pretty serious amplification!
Totally agree. BTW: xwc has been supersceeded by foXcommander by the looks of it. It's snappy, it's almost exploder-like but it's got some nasties, the first and foremost being NO KEYBOARD CONTROL!! I wonder how hard that will be to add. And since there's no keyboard control, there's no F2 to rename, F5 refresh, etc. <sigh>
Still and all, it's fast, snappy and clean. I bound win-E to it from WindowMaker. Konq is far too slow to bring up when I need to do something. Maybe now I won't have to alt-~ and type "mc -c" as often.:-)
The filemanager he mentions seems to be bitroting.
I think it has been taken over and brought into foXdesktop -- I searched high and low for xwc, got it, tried to compile, found out that the fox libs changed enough that it won't compile, cursed, and hit google some more.
I found foXcommander because it mentioned it was based on xwc. It still uses the fox libs but seems to be at least under new management. You need fox and foXdesktoplibs (or sommat like that, it's on that sf.net link) to get it running. There are two lines you have to change in the main.cpp for foXcommander; it complains about not knowing what MENU_DEFAULT is; just remove the reference to it (basically chop off the last argument to the function call in both instances). That's it. It is FAST, looks almost identical to the windows exploder and did I mention it was fast?
It also appears to support some kind of plugin architecture if I'm seeing things clearly. I wonder how much work it would be to port to KDE/qt; both fox and qt seem to be trying for the "write once, compile everywhere" goal, and it's a worthy one. However fox seems to be trying even harder to bring Windows to Linux (API and all, ewwwwww...) so I'd like to keep everything qt if I can.:-)
You can find the english/french correspondance for some things at [gouv.qc.ca]
I Knew this blind-enforcement of gotta-be-French was braindead Quebec Separatist groupthink. I'm not accusing you of being one of those head-up-their-arse separatists, but the first post I read about enforcing French words no matter how permeated the English term was sounded like something to come out of la belle province's brainiac political leaders.
Uhh, where I come from a megabit is 1048576 bits. i.e. a 1 megabit FLASH or EPROM actually contains 1048576 cells, usually arranged into an 8 x 131072 array, giving you 128 kilobytes.
Hmm, but now that I think of it, the raw throughput of a DS1 is 1.544megabits per second but that is 1544000 bits per second...
The SI prefix Mega has always meant 10e6, which is why HD manufacturers use its true definition to sell their wares.
Oh puh-lease.
HD manufacturers use 10e6 because it makes their capacities sound bigger, just like monitor manufacturers use the tube size instead of the viewable area because it makes their wares sound bigger. Correctness has absolutely nothing to do with it.
Slashdot Mirror
<sigh>
The acronym "FUD" does not mean "saying bad things about a program". FUD stands for "Fear, Uncertainty and Doubt".
Almost correct. Taken purely as an acronym, that is what FUD means. However the definition has grown to include tactics including half-truths and downright wrong information. Your statements could have been taken as FUD as you were saying that PostgreSQL is notoriously slow. That's just like "Linux is is useless compared to Windows on the desktop," or "MySQL doesn't support transactions." These things may have been true in the past but are not now, so they are considered statements of FUD. Back to my particular statment: you're casting doubt over the performance of the system.
The word "notorious" does not mean extreme. It means "well noted".
That is exactly correct. Your well-noted observation that PostgreSQL is slow is dated and unsubstantiated. Even older versions of PostgreSQL fare much better than MySQL when you start doing more than one update to a table at a time or involve anything but trivial inserts and selects. Earlier versions also had synchronous disk access defaulted on which hurt performance signficantly. Both of these facts are well-noted as well, but you did not bring them up, which to me also helps the FUD claim: you're only telling half the story.
I'm not really a passionate defender of all things Postgres; I just hate seeing the same old tired and dated arguments brought up again and again as they simply don't apply anymore.
I know what the words mean; don't try to cast uncertainty and doubt over my English proficiency, please.
So, you agree that postgres is slower, but it's FUD when I say it's slower. Whatever, dude.
Read your comment again:
"Nortoriously slow" is where I have the problem. It's not notoriously slow. MySQL is marginally faster than PostgreSQL on simple insert/select statements, but that's it. So yes, you are spreading fud, dude.
Postgres is rock solid, but notoriously slow. MySQL is wicked fast, but doesn't scale well.
Oh puh-lease. That old "postgres is slow" arguement is ancient. While mysql may be faster for simple insert/selects, that's where it stops, and compared to today's postgres it's not that much faster. Update your FUD, please.
Obviously this security thing is just a cover for the real reason for the work stoppage -- they're packing up and moving to Canada.
oh Gods, I hope not. There goes the neighbourhood.
I've been using the full-size Palm keyboard for a year and it rocks.
The biggest problem I've found with my folding keyboard and Vx is that it the keyboard seems "slow" -- I can easily out-type it. Is there a driver fix or OS upgrade which addresses this?
My birthday is 5/5. I found out after marrying my wife that her birthday is 8/8. My firstborn's birthday is 11/11 (which if you add 5 and 8 you get 13, is octal for 11). It's too bad my other kids didn't follow pattern, as my stepson's birthday is 5/24 (May 2-4, a big drinking party day for you non-Canadians), and my youngest son's birthday is 2/7, which really isn't special other than that is his birthday. :-)
My age in hex, I hadn't thought of that before... 1a this year...
I wonder if your hardware isn't going bad. I too run DPT SmartRAID controllers. A 2654U2 to be exact (2-channel version) in a 440LX P2/266 (we're network bound, not CPU bound) which is used for fileserving about 50 people in a file-heavy office environment. Before that, it was a SmartRAID V with the hardware cache/RAID card (which is in use ino another, heavier-hit webserver).
Zero stability issues on both. The 2654U2 has a 5-drive RAID5 + hot spare (UW2 SCA drives) on one channel and a 6x24 DDS-3 on another. I've done some pretty I/O intense things on this controller (including rebuilding the array during office hours) with no problems at all. This is on kernel 2.4.17. The SmartRAID V is on a 2.2.14 system which has about 50 colocated web and mail sites (it does a pretty good job of keeping the T1 busy). It runs a RAID1+0 array with really old Seagate Baracuda SCSI-1 drives and a single external DDS-3 for backup. Again, zero stability issues. I'd buy these again without hesitating.
Perhaps you need to delve deeper into the problem. The 2654U2 did not like the original P90 system the server used to be; we had bad issues there and the tech basically said that the original PCI spec was not good enough for the card. Upgrade the motherboard and all was fine. If you're running 2.4, make sure you're in the .16/.17 kernels, as earlier 2.4 kernels had issues with all manner of things, but not specifically the DPT I2O drivers, IIRC.
Both of these systems run the kernel drivers and use the dptutil software that DPT used to have (which you're right, has gone the way of the dodo after Adaptec's assimilation of DPT); what specifically can you do to cause problems? I don't think it's the card/drivers in general but if you give me a test or two I can run to see if I'm affected as well we might be able to fix this.
Slashdot's braindead lameness filter is not letting me post my dptutil -L output. Sorry.
Do any Canadians (perhaps only Ontarians) remember the ICON computers they used to have in elementary and high schools?
Yup. Used 'em in Grade 7/8 IIRC at Stanley Park Senior Public in Kitchener, ON. (Grade 7 would have been '89?) -- I got booted out of the room after a while for dicking around at the command prompt they boot up with, trying to get in to something I had no idea about at the time.
I've got one now (had two) -- they cut off the keyboard though, and I've got to figure out what pins go where (the connector's gone) but I'd love to boot it up again. You've got the specifications exactly right: 80186 (basically a controller version of the 8086, it includes the PIC, DMA, PIT and a few other of the 82xx-series of support chips in the processor package itself), I think about 640k of memory (weird staggered-SIPP package), arcnet, EGA or VGA display. Gray case that boots up blue and spends 99% of its time displaying blue background. :-)
I bet you could get something like ELKS running on it without much trouble.
Man... I remember the *sound* of the room they were in. the server(s) (I believe we had two, one for each double row of ICONs, about 20-24 ICONs per server) with physically ENORMOUS hard drives and fans and fans and fans... in a room with no sound suppression. It sounded like a large colo facility does today, I bet.
Well, I don't know about the custom menus
Exactly what I wanted to edit... :-) Yeah I know kmenuedit works fine for the app menu but I wasn't interested in that. Oh well, I thought I may have had the problem solved.
AFAIK, the bridging code is loaded to the PCMCIA card each boot. Did they manage to keep the file and just replay it or did they reverse-engineer the bridging code?
Not that I am really concerned, bridging a wireless LAN to your wired LAN is bad news unless there is zero need for security (aka my home).
Adobe however, does make the worlds best tools for authoring PDF from a variety of sources...
I don't know about that; ps2pdf13 makes far nicer screen-optimized documents (smaller too) than I could get Acrobat 4.06 to make under Win32.
Dude: Control Center -> LookNFeel -> Desktop -> Clicks on the desktop. Choose what you want for each mouse click
Dude:
Okay, select to pull up a menu. Now where do I go to configure the menu that pops up?
What you're saying is equivalent to one of the many post on using VI when the discussion's topic is IDEs. fine if it does the job for you but 90% of people out there want the fully integrated DEs like GNOME and KDE.
If you can tell me how to alter the menus for right-click (on desktop) and middle button click on desktop with KDE I'll use it (Kwin). Eliminate the panel and give me desktop menus; so far nobody has been able to tell me how to do so (including the gurus in #kde on openprojects), so until then WindowMaker has the features I need and KWin is the slow one with the lack of features.
Eventually I got tired of it crapping out on me and switched over to KDE, which, although not as pretty, seems to run much faster and with fewer hiccups.
I agree for the most part. I'm running KDE3.0b1 (well WindowMaker 0.80.0 with a lot of KDE apps) but I've run across an annoying problem with multi-line edit boxes (not all of 'em, but most) -- QT3 has a HORRIBLY slow repeat rate in most of those boxes! It's quicker for me to mouse over and click and return to the keyboard than it is to cursor. Acutally this /. window is one of them (Konqueror) that has this problem. y Psi message window is another one (which isn't KDE at all, just QT3). qtconfig doesn't help since it doesn't have any way to change the repeat rates.
has anyone run across this before
I have to agree, 2.4.17 is rock solid in my opinion.
I'll third that. :-) I have had no trouble with .16 or .17 with or without the preemptable kernel patch. Win4Lin has some issues which occassinally lock up my notebook good and hard but when I'm not running with their kernel "enhancements" I have yet to experience a crash here.
My server, however, seems to be showing its age... Abit BP6, dual Celeron 466 (not overclocked) -- I get good solid hangs that even kdb doesn't let me investigate when I have heavy traffic on the HPT366 interface. Disabling DMA on the drives on those controllers seems to help but I've bought a HPT370 PCI card to try and eliminate the problem. I've gotten addicted to dual processor computing on the desktop and can't afford a nice Athlon MP system yet. :-/
Its next to impossible to see around the average SUV, creating problems when someone is trying to maneaver around you, but you probably have never experienced this, so you wouldn't know.
So how do you deal with the 18-wheelers on the highways? Good lord, if you can't see, you don't manouvre. And you can almost always peek around any vehicle to see past it. Failing that, BACK OFF! Your visibility increases when you don't have your fiat's hood under my Jeep's ass-end.
Get a minivan. I honestly believe that SUVs should require a separate license, and hefty registration fees. And automatic liability in any accident situation.
I'll take my Jeep, thanks. We have both, a Pontiac Transport and a Jeep Grand Cherokee. I drive the Jeep because I often drag around equipment that won't fit in a trunk and don't require the extreme size of the minivan with the seats out, and I also do a lot of northern Ontario driving in winter. And the odd time I have to do so with a couple other people. My wife transports 3 kids around and flips a couple seats up for groceries and stuff.
From your next post:
If you're specifically driving a vehicle that's designed to resist damage, and I'm driving one that's designed to write itself off, on impact, for safety reasons, then yes, you should have automatic liability. Oh, and all vehicles should come with cell phone jammers that are on when the car is running. :-)
So if you jump out in front of me at an intersection when I have the right of way, it's my fault just because I paid more for a vehicle that won't crumble? Blow me. Double that for the phone jammer comment. If you can't handle driving in decent weather with light traffic and talk on a cell phone, that is your problem, not mine. I happen to be able to control my vehicle when I'm distracted, and I also have the presence of mind to ignore/drop the cellphone when things happen.
Anyway (desperately trying to find the original thread), SUVs aren't just for offroad. Trucks and cars can only get you so far, and minivans definately have advantages in medium-size people movers. But SUVs are idea for people like me.
I've always liked the idea behind PAM but the implementation blew chunks. I can't get through to either of the links in the article but can someone in the know explain how this is different from PAM?
Yeah, KWord works halfassed with .doc, but I can't get it to read an .rtf for the life of me. This is unfortunate because I believe that .rtf would work a lot better for getting formatting and such correct.
Also, it is useful to recall that microwave ovens operate on 2400 MHz because this is the most efficient frequency for heating water. One watt is enough to cause some RF heating and potentially be hazardous to you health. Don't look at the business end of that yagi!
While I don't condone pointing a highly-directional antenna through you to test, 1W is nowhere near the power of even the smallest microwave ovens. I believe my old beastor is a 750W microwave, and the little'uns are 100-150W.
Aside: Having 1W at the output of the RF amp is not the same as what's coming out of that yagi; highly directional antennas focus that 1W into something (potentially) much, much higher. Is that 1W ERP or 1W at the amp? Remember that LED-communications system on /. a week or so ago? by using fresnel lenses the effective optical power was 10kW from a 650mW LED! Directional antennas can do some pretty serious amplification!
I hate two pane. I need a tree.
Totally agree. BTW: xwc has been supersceeded by foXcommander by the looks of it. It's snappy, it's almost exploder-like but it's got some nasties, the first and foremost being NO KEYBOARD CONTROL!! I wonder how hard that will be to add. And since there's no keyboard control, there's no F2 to rename, F5 refresh, etc. <sigh>
Still and all, it's fast, snappy and clean. I bound win-E to it from WindowMaker. Konq is far too slow to bring up when I need to do something. Maybe now I won't have to alt-~ and type "mc -c" as often. :-)
The filemanager he mentions seems to be bitroting.
I think it has been taken over and brought into foXdesktop -- I searched high and low for xwc, got it, tried to compile, found out that the fox libs changed enough that it won't compile, cursed, and hit google some more.
I found foXcommander because it mentioned it was based on xwc. It still uses the fox libs but seems to be at least under new management. You need fox and foXdesktoplibs (or sommat like that, it's on that sf.net link) to get it running. There are two lines you have to change in the main .cpp for foXcommander; it complains about not knowing what MENU_DEFAULT is; just remove the reference to it (basically chop off the last argument to the function call in both instances). That's it. It is FAST, looks almost identical to the windows exploder and did I mention it was fast?
It also appears to support some kind of plugin architecture if I'm seeing things clearly. I wonder how much work it would be to port to KDE/qt; both fox and qt seem to be trying for the "write once, compile everywhere" goal, and it's a worthy one. However fox seems to be trying even harder to bring Windows to Linux (API and all, ewwwwww...) so I'd like to keep everything qt if I can. :-)
You can find the english/french correspondance for some things at [gouv.qc.ca]
I Knew this blind-enforcement of gotta-be-French was braindead Quebec Separatist groupthink. I'm not accusing you of being one of those head-up-their-arse separatists, but the first post I read about enforcing French words no matter how permeated the English term was sounded like something to come out of la belle province's brainiac political leaders.
1 megabyte (8,338,608 bits) != 8 megabit (8,000,000 bits)
Uhh, where I come from a megabit is 1048576 bits. i.e. a 1 megabit FLASH or EPROM actually contains 1048576 cells, usually arranged into an 8 x 131072 array, giving you 128 kilobytes.
Hmm, but now that I think of it, the raw throughput of a DS1 is 1.544megabits per second but that is 1544000 bits per second...
The SI prefix Mega has always meant 10e6, which is why HD manufacturers use its true definition to sell their wares.
Oh puh-lease.
HD manufacturers use 10e6 because it makes their capacities sound bigger, just like monitor manufacturers use the tube size instead of the viewable area because it makes their wares sound bigger. Correctness has absolutely nothing to do with it.