Gentoo is the Mandrake of Slashdot... You don't learn how to do anything besides run emerge. May as well run apt or urmpi, IMO.
LFS is pretty cool but time-consuming. Slackware seems to strike a very happy medium. Using CheckInstall to make Slackware packages for anything I compile by hand, I get every benefit of Debian or pretty much all the RPM based distros without all the overhead and central control.
Something you forgot (I too do engineering) is that FETs have practically no resistance while on, and practically infinite resistance when off. All of the current flow (and thus heat) is generated during the transition of off to on, and vice-versa.
In much the same way that SRAM draws next to no current when maintaining state, your processor's FETs draw next to no power when they're not changing state.
Honestly though, I don't know why it's not possible to use the temp-sensing diode built in to the processor and an internal (die) capacitor to build a little 1-bit ADC. Use two of them -- one run from the system clock and one from the output of the multiplied clock. E=dV^e-(t/RC) IIRC, throw the output of the cap to a comparator with the "right" voltage modified by the temperature of the die and you should have an (accurate enough) indicator that the chip is not running at the right frequency.
Or even easier than that, integrate a dead-simple temperature-stabilized frequency-to-voltage convertor (basically what I did above, but there are other methods) and use the output of that to give a go/no go signal. I mean honestly, why use (another) on-chip clock? If you've already got a clock on chip, why not use that instead of requiring the motherboard to supply a clock? Use the on-chip clock to clock the system instead of vice-versa.
I went through practically every Linux client I could find before finding one that I was happy with. Psi is a Qt-based client that acts and feels very much like the original ICQ client. No ads, sidebars, topbars, navbars, barbars... just a regular clean and simple IM client. There is an extensive client list for Win32, Linux and MacOSX which lists the features of each. Psi works on all three, which is another reason I chose it. That, and the fact that, at the time, it was the only NON-Gtk client that looked half assed presentable and the ONLY Linux client that didn't take up a lot of screen real estate, and the ONLY Linux client that did NOT pop up the incoming message, stealing focus from whatever I was typing into.
Psi's Jabber client lib (and ssl comms) have been adopted by KDE for their IM clients too, which is a nice bonus.
What about number of weapons per capita? If you take that into account, you Canadians might quiet down a bit...:) (not to mention what that hot air in Texas does to a man's brain, there's a reason fundamentalist christian sects are popular in Texas)
Well a high weapons per capita ratio isn't something I'd personally brag about. Hot air may affect Texans but just think of what frozen nuts do up here... Chretien just won't leave!
If someone can get root permission inside a chroot you can break out [bpfh.net]
Sure, but then again who in their right mind runs a web browser, ftp server, cvs site, news server, name server or practically any server as root anymore?
If you're thinking of buying StarOffice for the database, don't bother. Adabas sucks ass. OpenOffice can contact practically any database, including MySQL or Postgres. Personally I suggest the latter.
You should be using afio -- compresses each file individually so if you hit an unrecoverable error it won't zap all the data from that point on to the next compression key table. No I am not making this up.
I'll start selling modchips for Lexmark printers that always report the ink as full, or decrement the counter as usual but have a reset button. Same idea as the PS2 modchips.
Speaking of Jeode -- the damn thing (evm, that is) is almost perfect for XWT -- The only class I've found that doesn't exist with evm's AWT implementation is BufferedImage. So close...
Maybe if the first db you used was MySQL things seem "harder" because Postgres is a little different,
Little different? How about it's doing it the right way since it is conforming to SQL95 specifications? The goddamned '*' autoincrement is but one more blight on MySQL's arse.
other than that, what does PostgreSQL still have on MySQL?
Uh... Performance? IIRC MySQL's benchmarks are horrible for anything other than simple selects. Even its network performance is weak compared to Postgres. If I can find the benchmarks I'll reply here, but IIRC it was even in a previous/. story.:-)
I got around the replication issue (mirror only) by putting a insert/update/delete trigger on the table I wished to replicate. The function simply logged the action into an "audit" table.
That audit table had a delete trigger on it which wrote the deleted tuple to a third table. A cron job ran every five minutes which executed 'DELETE * FROM table_audit;', pg_dump to a textfile and finally 'TRUNCATE TABLE table_audit_copy;'. The resultant textfile was compressed and sent over to the other database, where some postprocessing turned the audit logs into proper queries again and executed them on the mirror DB.
This "double-buffering" is necessary in order to eliminate consistency problems in the database audit log. (e.g. if we just dumped the audit table we wouldn't be able to easily tell which entires were successfully dumped on the most recent pull since new data is coming in all the time, and locking the table while dumping it causes access delays on the table I wanted to replicate.) Using triggers and letting the DB handle it itself is a very clean and efficient way of handling this kind of data consistency problem.
And yeah, I know this isn't the best for performance and doesn't suit everyone, but it does seem to work well. I could have written a function to just log the tuple that changed in the main table to disk directly, but just like perl, TMTOWTDI.:-)
As it turns out, I am not even using this anymore, since it was easier to modify the client that was doing the database work and have it just log the transactions to disk instead. (They were insert/update only.)
Something is also nagging at me that there were some transaction problems with the default transaction isolation level, but I have since forgotten the issue.
Zero-G is not an ideal environment for construction/repair.
I dunno.. the chance of the nut falling down into some inaccessible place sure seems a lot smaller... Of course the bigger problem becomes keeping things put.:-)
Thanks for the link... I do believe that the word "uses" in that text refers to use which allows you to distribute and/or sell your works, which would not be otherwise possible without the patented work.
Example -- the infamous cat excersizer patents -- so long as I'm not making money at it (selling cat excercizers or excercising cats for money with the patented device) there really isn't anything bad to come of it.
It's a matter of semantics and business logic perhaps, but I honestly don't think any company is going to bother wasting their time and money going after someone who's using their patent for personal use -- there's simply no money to gain from it.
Doesn't make it exactly right, perhaps, but with all the bullshit we put up with corporations, it's an edge I'll play.
I don't think there was any 'FUD' in that statement.
The FUD was that Linux (well any OS utilizing ELF-based libraries) has the same DLL hell as Windows.
I completely agree that requiring a specific version of a lib and not any further releases is a design flaw in the application (or perhaps just not a maintained one, if the library API has changed), but that is a far far cry from DLL hell.
It explains exactly what I usually tell everyone that notices that "insecurity". What's next, ls -l reads/etc/passwd?;-)
Actually, everyone _does_ need to be able to read/etc/passwd. That's where the uid/gid and home directory information is stored. It's also why/etc/shadow was created, which has root.root and 600 perms, and actually holds the passwords.:-)
Actually I think the reason XP takes up so much ram is because it is loading up a ton of USELESS DLL's and COM objects into ram so that IE will load faster and Word XYZ will open immediately,
KDE does the exact same thing with its startkde script -- it specifies LD_BIND=NOW for kdeinit, causing all the libraries that kdeinit will require (which is all of the major KDE ones) to be loaded and resolved immediately, instead of on-demand. This increases start time, but when you load up a konsole or other KDE app the libraries are all already loaded. It even goes a step further and (optionally) starts up a few konqueror browser sessions in the background so that when you call one up it is there immediately.
This isn't a bad thing. Not for MS and not for KDE. Computers are meant to serve people. This library preloading is a good thing.
First, my resume is 404'd because I'm not looking.
Second, It is my understanding that patents do not apply to personal, non-distribution use, in the US or abroad. Patents are a method for someone who has created a work to be paid for said work if you're selling or distributing something that uses their work. I'm not.
Third, I mis-typed. It's their autohinter that I am using anyway, not their bytecode interpreter. So the patent doesn't apply. I apologize for the mis-type.
Indeed most libraries have subversions, but most apps just link to the major version. When an app insists it needs version 6.3.2.4.33 it gets nasty..
Stop spreading FUD. You can access any library you want with LD_PRELOAD. So if libfoo is at 6.3.4 and you have a 6.3.2.4.33 on the system that your app absolutely requires, a simple
LD_PRELOAD=/path/to/libfoo.so.6.3.2.4.33 someapp
will do the trick. In fact, I do this specifically for StarOffice so I can use my local copy of freetype2 with the bytecode hinter turned on instead of the version which comes with StarOffice.
Slashdot Mirror
Gentoo is the Mandrake of Slashdot... You don't learn how to do anything besides run emerge. May as well run apt or urmpi, IMO.
LFS is pretty cool but time-consuming. Slackware seems to strike a very happy medium. Using CheckInstall to make Slackware packages for anything I compile by hand, I get every benefit of Debian or pretty much all the RPM based distros without all the overhead and central control.
A happy Slackware user since '95.
Something you forgot (I too do engineering) is that FETs have practically no resistance while on, and practically infinite resistance when off. All of the current flow (and thus heat) is generated during the transition of off to on, and vice-versa.
In much the same way that SRAM draws next to no current when maintaining state, your processor's FETs draw next to no power when they're not changing state.
Honestly though, I don't know why it's not possible to use the temp-sensing diode built in to the processor and an internal (die) capacitor to build a little 1-bit ADC. Use two of them -- one run from the system clock and one from the output of the multiplied clock. E=dV^e-(t/RC) IIRC, throw the output of the cap to a comparator with the "right" voltage modified by the temperature of the die and you should have an (accurate enough) indicator that the chip is not running at the right frequency.
Or even easier than that, integrate a dead-simple temperature-stabilized frequency-to-voltage convertor (basically what I did above, but there are other methods) and use the output of that to give a go/no go signal. I mean honestly, why use (another) on-chip clock? If you've already got a clock on chip, why not use that instead of requiring the motherboard to supply a clock? Use the on-chip clock to clock the system instead of vice-versa.
I went through practically every Linux client I could find before finding one that I was happy with. Psi is a Qt-based client that acts and feels very much like the original ICQ client. No ads, sidebars, topbars, navbars, barbars... just a regular clean and simple IM client. There is an extensive client list for Win32, Linux and MacOSX which lists the features of each. Psi works on all three, which is another reason I chose it. That, and the fact that, at the time, it was the only NON-Gtk client that looked half assed presentable and the ONLY Linux client that didn't take up a lot of screen real estate, and the ONLY Linux client that did NOT pop up the incoming message, stealing focus from whatever I was typing into.
Psi's Jabber client lib (and ssl comms) have been adopted by KDE for their IM clients too, which is a nice bonus.
What do you do about the 400-700h lifetime of the bulb, and the $400 bulb cost?!
I'm sorry but you are worried about 800x600 on a 21" monitor?!
What about number of weapons per capita? If you take that into account, you Canadians might quiet down a bit... :) (not to mention what that hot air in Texas does to a man's brain, there's a reason fundamentalist christian sects are popular in Texas)
Well a high weapons per capita ratio isn't something I'd personally brag about. Hot air may affect Texans but just think of what frozen nuts do up here... Chretien just won't leave!
What's wrong with TightVNC? It isn't exactly as fast as Cirtix over dialup, but it comes damned close and the price is right.
Bah. If you're going to piss off Texans, may as well show them that Quebec is large enough to encompass four Texases with room to spare. :-)
If someone can get root permission inside a chroot you can break out [bpfh.net]
Sure, but then again who in their right mind runs a web browser, ftp server, cvs site, news server, name server or practically any server as root anymore?
If you're thinking of buying StarOffice for the database, don't bother. Adabas sucks ass. OpenOffice can contact practically any database, including MySQL or Postgres. Personally I suggest the latter.
You should be using afio -- compresses each file individually so if you hit an unrecoverable error it won't zap all the data from that point on to the next compression key table. No I am not making this up.
I'll start selling modchips for Lexmark printers that always report the ink as full, or decrement the counter as usual but have a reset button. Same idea as the PS2 modchips.
Sell 'em on ebay, just like the PS2 modchips.
Speaking of Jeode -- the damn thing (evm, that is) is almost perfect for XWT -- The only class I've found that doesn't exist with evm's AWT implementation is BufferedImage. So close...
ie. an address book.
And even then, you should be using LDAP.
Maybe if the first db you used was MySQL things seem "harder" because Postgres is a little different,
Little different? How about it's doing it the right way since it is conforming to SQL95 specifications? The goddamned '*' autoincrement is but one more blight on MySQL's arse.
other than that, what does PostgreSQL still have on MySQL?
Uh... Performance? IIRC MySQL's benchmarks are horrible for anything other than simple selects. Even its network performance is weak compared to Postgres. If I can find the benchmarks I'll reply here, but IIRC it was even in a previous /. story. :-)
I got around the replication issue (mirror only) by putting a insert/update/delete trigger on the table I wished to replicate. The function simply logged the action into an "audit" table.
That audit table had a delete trigger on it which wrote the deleted tuple to a third table. A cron job ran every five minutes which executed 'DELETE * FROM table_audit;', pg_dump to a textfile and finally 'TRUNCATE TABLE table_audit_copy;'. The resultant textfile was compressed and sent over to the other database, where some postprocessing turned the audit logs into proper queries again and executed them on the mirror DB.
This "double-buffering" is necessary in order to eliminate consistency problems in the database audit log. (e.g. if we just dumped the audit table we wouldn't be able to easily tell which entires were successfully dumped on the most recent pull since new data is coming in all the time, and locking the table while dumping it causes access delays on the table I wanted to replicate.) Using triggers and letting the DB handle it itself is a very clean and efficient way of handling this kind of data consistency problem.
And yeah, I know this isn't the best for performance and doesn't suit everyone, but it does seem to work well. I could have written a function to just log the tuple that changed in the main table to disk directly, but just like perl, TMTOWTDI. :-)
As it turns out, I am not even using this anymore, since it was easier to modify the client that was doing the database work and have it just log the transactions to disk instead. (They were insert/update only.)
Something is also nagging at me that there were some transaction problems with the default transaction isolation level, but I have since forgotten the issue.
Zero-G is not an ideal environment for construction/repair.
I dunno.. the chance of the nut falling down into some inaccessible place sure seems a lot smaller... Of course the bigger problem becomes keeping things put. :-)
Thanks for the link... I do believe that the word "uses" in that text refers to use which allows you to distribute and/or sell your works, which would not be otherwise possible without the patented work.
Example -- the infamous cat excersizer patents -- so long as I'm not making money at it (selling cat excercizers or excercising cats for money with the patented device) there really isn't anything bad to come of it.
It's a matter of semantics and business logic perhaps, but I honestly don't think any company is going to bother wasting their time and money going after someone who's using their patent for personal use -- there's simply no money to gain from it.
Doesn't make it exactly right, perhaps, but with all the bullshit we put up with corporations, it's an edge I'll play.
I don't think there was any 'FUD' in that statement.
The FUD was that Linux (well any OS utilizing ELF-based libraries) has the same DLL hell as Windows.
I completely agree that requiring a specific version of a lib and not any further releases is a design flaw in the application (or perhaps just not a maintained one, if the library API has changed), but that is a far far cry from DLL hell.
It explains exactly what I usually tell everyone that notices that "insecurity". What's next, ls -l reads /etc/passwd? ;-)
Actually, everyone _does_ need to be able to read /etc/passwd. That's where the uid/gid and home directory information is stored. It's also why /etc/shadow was created, which has root.root and 600 perms, and actually holds the passwords. :-)
Actually I think the reason XP takes up so much ram is because it is loading up a ton of USELESS DLL's and COM objects into ram so that IE will load faster and Word XYZ will open immediately,
KDE does the exact same thing with its startkde script -- it specifies LD_BIND=NOW for kdeinit, causing all the libraries that kdeinit will require (which is all of the major KDE ones) to be loaded and resolved immediately, instead of on-demand. This increases start time, but when you load up a konsole or other KDE app the libraries are all already loaded. It even goes a step further and (optionally) starts up a few konqueror browser sessions in the background so that when you call one up it is there immediately.
This isn't a bad thing. Not for MS and not for KDE. Computers are meant to serve people. This library preloading is a good thing.
First, my resume is 404'd because I'm not looking.
Second, It is my understanding that patents do not apply to personal, non-distribution use, in the US or abroad. Patents are a method for someone who has created a work to be paid for said work if you're selling or distributing something that uses their work. I'm not.
Third, I mis-typed. It's their autohinter that I am using anyway, not their bytecode interpreter. So the patent doesn't apply. I apologize for the mis-type.
Indeed most libraries have subversions, but most apps just link to the major version. When an app insists it needs version 6.3.2.4.33 it gets nasty..
Stop spreading FUD. You can access any library you want with LD_PRELOAD. So if libfoo is at 6.3.4 and you have a 6.3.2.4.33 on the system that your app absolutely requires, a simple
will do the trick. In fact, I do this specifically for StarOffice so I can use my local copy of freetype2 with the bytecode hinter turned on instead of the version which comes with StarOffice.
Damn... I started with 3.3, having tried Yggdrasil or sommat just before. Mid-90s for me.