Microsoft added a fake left curling single-quote to most of it's fonts about ten years ago. Toy 'desktop' systems like Word, MS Publisher, BOB use these quotes in order to look 'cool'.
Standards-based browsers: Netscape, Mozilla, Konqueror, Opera don't nesesarily display this non-standard 'quote' the way IE does. They default to showing a question mark when confronted with theis non-standard quote.
The Chronic-Wasting desease is actually caused by fat people, who, evey day, go out into the woods that take a sample bite of what they hope will be chocolate moose.
and lack of adequate health care for all her citizens.
Great, what's next? Entertainment Care?
Cant affrord that Playstation 2 because you've been slacking in the easiest country in the world to make a buck? We have a Government Mandated program for you! Just fill out this form, wait in line, and we'll send you a Playstation 2 Government-Edition* in the next 16 months.
* Governemnt-Edition Playstation 2 will only play Exciting Edu-tainment games like Lilo and Stitch(tm) Teaches the DMCA and Mr. Atom Explaines the Benifit of the V-Chip Impland.
As a practical matter - It's is quite easy to compete with offsore work if your work is tailored exactly to the customer: For example, it would be easy for Microsoft to farm off the next version of Windows to India, but it would be next to impossible for my client, "Bob's Widgits Inc", to farm off "Widgit-Manager V3" to India.
The language, turnaround, and design issues balance the equasion to the programmer working for a small company and for small projects. God help you if your working for Microsoft though.
Amreica is the easiest place to start a small business: File some $200 paperwork, have a good idea and start working. It's the best job security one can, have. In my littls business, because I own the little bugger, I'm the last employee to get fired.
M$ has even given away a couple of Windows XP cd-roms. =D
My god! XP cd-roms! gimme gimme gimme!!
Dear User #581881,
Please make your Astroturfing(tm) a bit more subtle, as your curent methods may arouse suspicion. Instead try somthing anlong the lines of:
Wow! That's real generous of Microsoft! Even at the low price of $295.94, is a great bargin, but for free. That's amazing! Thanks Microsoft.
Or
Nifty! I've always wanted to try the best in opeating system technoloy, and I know Microsoft is the one to give it to me.
We know that you natural reaction is to preaise and worship, but please, keep in mide that if your too obvious you might actually disuage the Slashdot masses from our cause. Under no cercumstances are you to try the following:
XP for free! Thank you glorious leader. I live to serve.
or
Free XP cd-roms? Wow! I hope they give me a stack of them so I can thrust my penis in and out of the hole in the center. I LOVE XP!
Thank you for your attention to this matter.
Certified Atrroturn(tm) Profecctional #2011, Glibert W. Feltcher.
Oh, it's even better than that. You can do these things within transactions.
Good greif, that's cool! Do a whole database transformation in a transaction, and if it borks out, it rolls back? Cool!
Re:Related question re. Database development
on
PostgreSQL 7.3 Released
·
· Score: 3, Informative
Unfotrunatly there is no all-in-one rapid developemnt and flat-file database rolled into one, like Access, in the Unix world. But don't let that stop you from using Access though - it's a great tool for rapid development.
I use it all the time - you rapidly develope the small database, and when it outgrown the Access flat-file.mdb sotrage on about the fith concurent user, migrate the backend database to PostgreSQL and keep the Access front end. Once, the database get's really popular, migrate the Access front end over to Delphiand keep the PostgeSQL back end. The Access to Delphi transition should be done in stages - migrate the data enrty first, then migrate the reporting later.
Once that is donem and your database is really popular - migrate the front end again to Delphi to Delphi/Kylix and you'll be able to support Linux/FreeBSD and Windows desktops. People can VNC into a FreeBSD server that shares the Kylix app over VNC for other systems - Solaris, Mac, Psion.
1. I recently did an Access to MS SQL conversion and ended up with an access database in.adp format which contained the connection string to the SQL server and required no ODBC setup on the clinet PC's. Is this similar in Postgre?
Nope, You do need a PostgreSQL ODBC driver, but the link settings can be managed by your Access databsse if you relink on client startup with a VBA script.
2. In that conversion, the.adp file contained the forms, reports, and macros. The queries from the old access db were stored on the server either as views or Stored Procedures. Is this also similar (or at least compatible)?
You can store the queires as views on the PostgreSQL server - no problem there. In 7.3 procedures can return a set of data now - though, I'm waiting for reports from the field to come back and report that it's working well before I jump on it myself.
3. MS SQL allows you to use your current windows credentials as the authentication to the SQL server. This is nice because then the users don't have to enter/remember another password. Can I do this in Postgre?
I don't think there is any way you can do that in the PosgreSQL ODBC driver - you could rewire the ODBC link on the fly though. Another login is a pain in the ass, but nobody seems to care. It may be possible to get this to work with a Linux server through PAM - if you can get PostgreSQL to work though PAM. I don't know, though.
4. I've found that Access generates absolutely horrid SQL. Fortunately, because all these queries are stored on the SQL server, they can be edited/optimized after the conversion. This question ends up being a two-parter. How compatible is Postre with Access' ugly SQL? And if there's a compatability problem with the generated SQL, can I at least edit it server side and make access not care that that's happened?
Both the PostgreSQL server and ODBC driver can massage the horrid Access built queries into normalacy. Typically you don't have to migrate the queries off of Access and into server views because of this - they just work. It's the KSQO that does the magic, from the docs: Key Set Query Optimizer causes the query planner to convert queries whose WHERE clause contains many OR'ed AND clauses (such as "WHERE (a=1 AND b=2) OR (a=2 AND b=3)...") into a UNION query. KSQO is commonly used when working with products like MicroSoft Access, which tend to generate queries of this form.
This hasen't always been the case, Access queries used to crash PostgreSQL a few years ago becuase they were so odd.
General thoughts on both:
It takes a *bit* longer to get Access to play with PostgreSQL but once it's there, there are no odd bugs to work out. Upgrade Jet to the latest version on the clinet boxes, and set the ODBC time out in the regestry from 600 to 0 - there's a bug in the way Access relinks to a timed-out ODBC session, so by setting the timeout to 0, it never times out.
The Access/ODBC driver sometimes has problems with creating a record using contininous forms - any new record should be created using VBA rather than by filling out the blank entry in an Access continuis form or list of records.
Good luck - I've been very happy with the migration myself.
Oh, setup an hourly cron job to dump the database to a file then gzip it and stash it on a NFS server. Easy hourly backups! Never had to use them, but it's nice to know that we'll never loose more than an hours worth of work!
There's a fully capable SSH server for Windows, and you can do one hell of a lot from CMD.EXE... Perhaps you should read the manual for NETSH etc.?
I'm sure you can clidge an NT enviroment to work like Unix, but then I'd just rather run Unix. You can cludge a Honda Civic into going fast - I'd just rather have the Corvette.
Why the HELL would you want a server to boot diskless? If you're talking about clients, what do you THINK PXE boot roms are for?
A cluster of computational boxes. Render farm.
Hah. More like Unix has had 25 years to get it right on proprietry hardware. It's easy if you control hardware as well as software. Just look at how great Solaris is on x86... NOT.
Solaris on X86 is better then Windows NT on Sparc.
Because PostgreSQL and Oracle are designed to be a 24/7 live database. With most of the othere databse packages, you have to disconnect everybody then rename/drop columns. This feature is not terrably usefull if you can't do it while the database is running.
As an aside, you alway could do this with a down PostgreSQL database: dump the database, then rename, then reload.
You can *now* do this with a *live* PostgreSQL database.
And you can rename tables and colums on the fly too!
And the default identifier length is 63! ForReallyLongAndDescriptingColumnNames!
For all you people out there with Access who think this is old hat - the tables and column renaming and droping can happpen while people are connected to the PostgreSQL database - you don't have to kick anybody off the database.
If you're considering migrating your Aceess database to MS SQL Servier - do consider PostgreSQL. From experience, the amount of suffering is about the same for both transitions, but when your done, PostgrSQL is more robust, less expensive and less buggy.
I coulden't find an SSH clinet to run of a Revo - though there are several for the Netbook. and anyways SSH over a 2400 connection would take forever for the key excahange, and I'm impatient.
The Iridium system encrypts it's signal untill it gets to the POTS system, from there it goes to a modem connected to a OpenBSD server at my house. From there I SSH out.
The weak links are from the Revo to the Satelite Phone, and from the Iridium gateway to my modem on the server. I'm not too worried about phone taps, and I trust the Iridium people to do their encryption correctly, and not to be snoopy.
S/Key helps with the Telnet login.
I suppose there's an SSH client for the Revo out there, but my extensive search of last year came up with nothing.
The whole system is for emergency use - so I the risk of a few telnet logins over POTS doesen't seem too risky.
If you have One NT server and One *nix Server, and you're stupid, the NT server *is* easier to administrate. Just noodle around with the mouse and find the settings.
If you have more than one server, *nix is always faster to adminitrate.
Examples:
I can fully administrate any of my FreeBSD/OpenBSD servers from anywhere in the workd using my Iridium Phone and a Psion Revo with an SSH client. Windows 'remote-desktop' won't work at all over the Iridium phone's 2400 baud connection. There goes my hike and I scurry back to civilisation.
I can compile a versions of Samba for any arcatecture on one box, and deploy the new version remotely, without user intervention. Try getting your NT on Aplha box to deply a change to Windows-2000 box on AMD, without user intervention.
Try pulging in a laptop into your COM1 port and see what you get on Windows - on my Unix boxes you get a shell that you can log into, and fully administer your computer. If you lucky - and did major hacking, you might be able to get a cmd.exe over COM1 - but cmd.exe is useless.
Can you get your Widnows servers to bood diskless over a network? Nope.
The fact is Unix has had 25 years to get it right on some of the most advanced hardware in the world. Windows 7 year old a cludgy GUI layer on a bad VMS clone on PC hardware. No wonder is sucks.
That was intentional, most people understand the relationship between client/server in the same manor as VNC, PcAnywhere and Citrix. I propbably shound not have done that - dumbing things down to make them more accessable is can buy a dumb idead in itself. If you note, I expalined the descremency that at the end of my post:
*X uses odd client/server terminology. It makse sense in an odd way, but I used the 'traditional' meening here.
X Windows is designed for a clinet* to pull the information to display applications over the network from a server. Some of those applications are video, or video like, and some of those networks use compression.
X is *really* old and has roots to 1984.
*X uses odd client/server terminology. It makse sense in an odd way, but I used the 'traditional' meening here.
If the issus ever comes up, we all just fall back to Tribal/Nation names. hard to confuse "Tlingit" with "Bangalore."
My rather nasty point was that the PC movment of renaming "Natives" and "Indians" to "Native Americans" wasen't spawned by any Indian I know - just a bunch of nurotic self-hating white guys with too much time on their hands. I'm sure they probably ment well, but it looked like was just another case of pretending to care just to fell better. Of all the issuses that daily effect the group of natives that I work for, silly naming issues fall on the last of the list.
Be carefull there, pussy and weed sometimes don't mix. You might get a little bit too happy and choose the wrong pussy. It might leave a bad taste in your mouth....
Its clients, inside the company, uses a Windows front-end writen in Delphi; To the web, we simply recompiled the data abstraction layer and created some small formating code and we had a full-featured apache-linux webserver app, with little effort.
Fun stuff...
The nastiest trick I've done with Deplhi/Kylix is that I was tired of buggy Windows workstations making my app look bad, so I put the front-end of the app on a FreeBSD server and shared the app with VNC. So any computer that has a VNC viewer: Apple, Windows, Be - you name it, can use the app. And if the workstations crashes, the app is waiting them where they left off.
Interesting aside, apparently the curent crop of people we consider "Native Americans" are actually the third wave of people on the shores of this continente. You can guess where the previous two groups wound up.
Aside to an Aside, I work for a company of "Indians" and never, once, have they refered of them selves at "Native Americans". "Natives" once and a while, but almost alsway "Indian."
It's only the sickly pussy-whipped white males driving beat up Volvos and listening to Chomsky's books on 8-Track, who smoke too much of the good herb that use the term "Native American."
Each node has a spare 20GB partition that is currently doing *nothing*. I would simply love to find a filesystem solution that can handle stripping or mirroring for a nice 32*20/x GB of filespace
That easy. Create a partition on each box and export it via NFS. Then plunk down a NetBSD box on the network and RAID the partitions with RAIDframe. Export *that* partition via NFS as well. Export it via Samba and even the little Windows boxes can play.
FreeBSD has RAIDframe as well, but the NetBSD version is marginally more robust and has worked over NFS are far back as '98.
I use, delpoy and love OpenBSD and FreeBSD both. I view both *BSD's (and NetBSD) as slightly more reliable than Linux. But increasingly enough, I'm starting to find the diferences between the free Unix varients almost irelevent - it's the user-space applications that I care most about:
Example: If FreeBSD dropped off the face of the eart and I could only use Linux - i'd just shrug. But if PostgreSQL or Samba died, then I'd really be pissed.
Even more weird, increasingly, I'm finding the diferences between Windows and Unix almost becoming moot - If they both have Mozilla, Emacs and can run OpenOffice then, increasingly, Windows is becoming irrelevent to any of my needs. It's just another OS.
Get a very good intellectual property lawyer, or better yet, a lawyer in a firm that deals with business issues and has IP specialists on staff.
This is VERY true! Hire a lousy lawyer at $60 per hour and he'll make the contract for you in twenty hours. Hire a good lawyer ay $400 per hour, and he'll say "We did this before, here's a standard contract for this sort of thing" and he'll bill you for an hour.
Slashdot Mirror
Microsoft added a fake left curling single-quote to most of it's fonts about ten years ago. Toy 'desktop' systems like Word, MS Publisher, BOB use these quotes in order to look 'cool'.
Standards-based browsers: Netscape, Mozilla, Konqueror, Opera don't nesesarily display this non-standard 'quote' the way IE does. They default to showing a question mark when confronted with theis non-standard quote.
But you, and Mr "Pro Life" (irony) above swallowed that one hook, line, and sinker.
Why do you asume I'm "pro life?" I'm not.
That's called a straw-man argument, and it's rude, as well as stupid.
Spend a little time coming up with ideas, rather than just making foolist ad-hominim attacks and casting people as the deamons you expect.
The Chronic-Wasting desease is actually caused by fat people, who, evey day, go out into the woods that take a sample bite of what they hope will be chocolate moose.
It never works out, but the keep on trying.
and lack of adequate health care for all her citizens.
Great, what's next? Entertainment Care?
Cant affrord that Playstation 2 because you've been slacking in the easiest country in the world to make a buck? We have a Government Mandated program for you! Just fill out this form, wait in line, and we'll send you a Playstation 2 Government-Edition* in the next 16 months.
* Governemnt-Edition Playstation 2 will only play Exciting Edu-tainment games like Lilo and Stitch(tm) Teaches the DMCA and Mr. Atom Explaines the Benifit of the V-Chip Impland.
Want Health Care? Get a job and buy some.
As a practical matter - It's is quite easy to compete with offsore work if your work is tailored exactly to the customer: For example, it would be easy for Microsoft to farm off the next version of Windows to India, but it would be next to impossible for my client, "Bob's Widgits Inc", to farm off "Widgit-Manager V3" to India.
The language, turnaround, and design issues balance the equasion to the programmer working for a small company and for small projects. God help you if your working for Microsoft though.
Amreica is the easiest place to start a small business: File some $200 paperwork, have a good idea and start working. It's the best job security one can, have. In my littls business, because I own the little bugger, I'm the last employee to get fired.
M$ has even given away a couple of Windows XP cd-roms. =D
My god! XP cd-roms! gimme gimme gimme!!
Dear User #581881,
Please make your Astroturfing(tm) a bit more subtle, as your curent methods may arouse suspicion. Instead try somthing anlong the lines of:
Wow! That's real generous of Microsoft! Even at the low price of $295.94, is a great bargin, but for free. That's amazing! Thanks Microsoft.
Or
Nifty! I've always wanted to try the best in opeating system technoloy, and I know Microsoft is the one to give it to me.
We know that you natural reaction is to preaise and worship, but please, keep in mide that if your too obvious you might actually disuage the Slashdot masses from our cause. Under no cercumstances are you to try the following:
XP for free! Thank you glorious leader. I live to serve.
or
Free XP cd-roms? Wow! I hope they give me a stack of them so I can thrust my penis in and out of the hole in the center. I LOVE XP!
Thank you for your attention to this matter.
Certified Atrroturn(tm) Profecctional #2011, Glibert W. Feltcher.
Oh, it's even better than that. You can do these things within transactions.
Good greif, that's cool! Do a whole database transformation in a transaction, and if it borks out, it rolls back? Cool!
Unfotrunatly there is no all-in-one rapid developemnt and flat-file database rolled into one, like Access, in the Unix world. But don't let that stop you from using Access though - it's a great tool for rapid development.
I use it all the time - you rapidly develope the small database, and when it outgrown the Access flat-file
Once that is donem and your database is really popular - migrate the front end again to Delphi to Delphi/Kylix and you'll be able to support Linux/FreeBSD and Windows desktops. People can VNC into a FreeBSD server that shares the Kylix app over VNC for other systems - Solaris, Mac, Psion.
Cool stuff.
1. I recently did an Access to MS SQL conversion and ended up with an access database in
Nope, You do need a PostgreSQL ODBC driver, but the link settings can be managed by your Access databsse if you relink on client startup with a VBA script.
2. In that conversion, the
You can store the queires as views on the PostgreSQL server - no problem there. In 7.3 procedures can return a set of data now - though, I'm waiting for reports from the field to come back and report that it's working well before I jump on it myself.
3. MS SQL allows you to use your current windows credentials as the authentication to the SQL server. This is nice because then the users don't have to enter/remember another password. Can I do this in Postgre?
I don't think there is any way you can do that in the PosgreSQL ODBC driver - you could rewire the ODBC link on the fly though. Another login is a pain in the ass, but nobody seems to care. It may be possible to get this to work with a Linux server through PAM - if you can get PostgreSQL to work though PAM. I don't know, though.
4. I've found that Access generates absolutely horrid SQL. Fortunately, because all these queries are stored on the SQL server, they can be edited/optimized after the conversion. This question ends up being a two-parter. How compatible is Postre with Access' ugly SQL? And if there's a compatability problem with the generated SQL, can I at least edit it server side and make access not care that that's happened?
Both the PostgreSQL server and ODBC driver can massage the horrid Access built queries into normalacy. Typically you don't have to migrate the queries off of Access and into server views because of this - they just work. It's the KSQO that does the magic, from the docs: Key Set Query Optimizer causes the query planner to convert queries whose WHERE clause contains many OR'ed AND clauses (such as "WHERE (a=1 AND b=2) OR (a=2 AND b=3)
This hasen't always been the case, Access queries used to crash PostgreSQL a few years ago becuase they were so odd.
General thoughts on both:
It takes a *bit* longer to get Access to play with PostgreSQL but once it's there, there are no odd bugs to work out. Upgrade Jet to the latest version on the clinet boxes, and set the ODBC time out in the regestry from 600 to 0 - there's a bug in the way Access relinks to a timed-out ODBC session, so by setting the timeout to 0, it never times out.
The Access/ODBC driver sometimes has problems with creating a record using contininous forms - any new record should be created using VBA rather than by filling out the blank entry in an Access continuis form or list of records.
Good luck - I've been very happy with the migration myself.
Oh, setup an hourly cron job to dump the database to a file then gzip it and stash it on a NFS server. Easy hourly backups! Never had to use them, but it's nice to know that we'll never loose more than an hours worth of work!
There's a fully capable SSH server for Windows, and you can do one hell of a lot from CMD.EXE... Perhaps you should read the manual for NETSH etc.?
I'm sure you can clidge an NT enviroment to work like Unix, but then I'd just rather run Unix. You can cludge a Honda Civic into going fast - I'd just rather have the Corvette.
Why the HELL would you want a server to boot diskless? If you're talking about clients, what do you THINK PXE boot roms are for?
A cluster of computational boxes. Render farm.
Hah. More like Unix has had 25 years to get it right on proprietry hardware. It's easy if you control hardware as well as software. Just look at how great Solaris is on x86... NOT.
Solaris on X86 is better then Windows NT on Sparc.
Oh wait....
Because PostgreSQL and Oracle are designed to be a 24/7 live database. With most of the othere databse packages, you have to disconnect everybody then rename/drop columns. This feature is not terrably usefull if you can't do it while the database is running.
As an aside, you alway could do this with a down PostgreSQL database: dump the database, then rename, then reload.
You can *now* do this with a *live* PostgreSQL database.
And you can rename tables and colums on the fly too!
And the default identifier length is 63! ForReallyLongAndDescriptingColumnNames!
For all you people out there with Access who think this is old hat - the tables and column renaming and droping can happpen while people are connected to the PostgreSQL database - you don't have to kick anybody off the database.
If you're considering migrating your Aceess database to MS SQL Servier - do consider PostgreSQL. From experience, the amount of suffering is about the same for both transitions, but when your done, PostgrSQL is more robust, less expensive and less buggy.
I coulden't find an SSH clinet to run of a Revo - though there are several for the Netbook. and anyways SSH over a 2400 connection would take forever for the key excahange, and I'm impatient.
The Iridium system encrypts it's signal untill it gets to the POTS system, from there it goes to a modem connected to a OpenBSD server at my house. From there I SSH out.
The weak links are from the Revo to the Satelite Phone, and from the Iridium gateway to my modem on the server. I'm not too worried about phone taps, and I trust the Iridium people to do their encryption correctly, and not to be snoopy.
S/Key helps with the Telnet login.
I suppose there's an SSH client for the Revo out there, but my extensive search of last year came up with nothing.
The whole system is for emergency use - so I the risk of a few telnet logins over POTS doesen't seem too risky.
If you have One NT server and One *nix Server, and you're stupid, the NT server *is* easier to administrate. Just noodle around with the mouse and find the settings.
If you have more than one server, *nix is always faster to adminitrate.
Examples:
I can fully administrate any of my FreeBSD/OpenBSD servers from anywhere in the workd using my Iridium Phone and a Psion Revo with an SSH client. Windows 'remote-desktop' won't work at all over the Iridium phone's 2400 baud connection. There goes my hike and I scurry back to civilisation.
I can compile a versions of Samba for any arcatecture on one box, and deploy the new version remotely, without user intervention. Try getting your NT on Aplha box to deply a change to Windows-2000 box on AMD, without user intervention.
Try pulging in a laptop into your COM1 port and see what you get on Windows - on my Unix boxes you get a shell that you can log into, and fully administer your computer. If you lucky - and did major hacking, you might be able to get a cmd.exe over COM1 - but cmd.exe is useless.
Can you get your Widnows servers to bood diskless over a network? Nope.
The fact is Unix has had 25 years to get it right on some of the most advanced hardware in the world. Windows 7 year old a cludgy GUI layer on a bad VMS clone on PC hardware. No wonder is sucks.
You have the Client and Server in X reversed
That was intentional, most people understand the relationship between client/server in the same manor as VNC, PcAnywhere and Citrix. I propbably shound not have done that - dumbing things down to make them more accessable is can buy a dumb idead in itself.
If you note, I expalined the descremency that at the end of my post:
*X uses odd client/server terminology. It makse sense in an odd way, but I used the 'traditional' meening here.
the metaphor falls short with the fact that you cannot send people to harvest the Moon
I don't know about you, but I sure enjoy this tasty moon-cheese.
X Windows is designed for a clinet* to pull the information to display applications over the network from a server. Some of those applications are video, or video like, and some of those networks use compression.
X is *really* old and has roots to 1984.
*X uses odd client/server terminology. It makse sense in an odd way, but I used the 'traditional' meening here.
If the issus ever comes up, we all just fall back to Tribal/Nation names. hard to confuse "Tlingit" with "Bangalore."
My rather nasty point was that the PC movment of renaming "Natives" and "Indians" to "Native Americans" wasen't spawned by any Indian I know - just a bunch of nurotic self-hating white guys with too much time on their hands. I'm sure they probably ment well, but it looked like was just another case of pretending to care just to fell better. Of all the issuses that daily effect the group of natives that I work for, silly naming issues fall on the last of the list.
Be carefull there, pussy and weed sometimes don't mix. You might get a little bit too happy and choose the wrong pussy. It might leave a bad taste in your mouth....
Cheers.
Its clients, inside the company, uses a Windows front-end writen in Delphi; To the web, we simply recompiled the data abstraction layer and created some small formating code and we had a full-featured apache-linux webserver app, with little effort.
Fun stuff...
The nastiest trick I've done with Deplhi/Kylix is that I was tired of buggy Windows workstations making my app look bad, so I put the front-end of the app on a FreeBSD server and shared the app with VNC. So any computer that has a VNC viewer: Apple, Windows, Be - you name it, can use the app. And if the workstations crashes, the app is waiting them where they left off.
I too would love for native Mac support.
The best thing about Delphi/Kylix is that you can dabble in Linux, and still use it to pay the bills.
Aside, Kylix programs work wonderfully in FreeBSD with FreeBSD's Linux compatibility layer.
Interesting aside, apparently the curent crop of people we consider "Native Americans" are actually the third wave of people on the shores of this continente. You can guess where the previous two groups wound up.
Aside to an Aside, I work for a company of "Indians" and never, once, have they refered of them selves at "Native Americans". "Natives" once and a while, but almost alsway "Indian."
It's only the sickly pussy-whipped white males driving beat up Volvos and listening to Chomsky's books on 8-Track, who smoke too much of the good herb that use the term "Native American."
Each node has a spare 20GB partition that is currently doing *nothing*. I would simply love to find a filesystem solution that can handle stripping or mirroring for a nice 32*20/x GB of filespace
That easy. Create a partition on each box and export it via NFS. Then plunk down a NetBSD box on the network and RAID the partitions with RAIDframe. Export *that* partition via NFS as well. Export it via Samba and even the little Windows boxes can play.
FreeBSD has RAIDframe as well, but the NetBSD version is marginally more robust and has worked over NFS are far back as '98.
I use, delpoy and love OpenBSD and FreeBSD both. I view both *BSD's (and NetBSD) as slightly more reliable than Linux. But increasingly enough, I'm starting to find the diferences between the free Unix varients almost irelevent - it's the user-space applications that I care most about:
Example: If FreeBSD dropped off the face of the eart and I could only use Linux - i'd just shrug. But if PostgreSQL or Samba died, then I'd really be pissed.
Even more weird, increasingly, I'm finding the diferences between Windows and Unix almost becoming moot - If they both have Mozilla, Emacs and can run OpenOffice then, increasingly, Windows is becoming irrelevent to any of my needs. It's just another OS.
Get a very good intellectual property lawyer, or better yet, a lawyer in a firm that deals with business issues and has IP specialists on staff.
This is VERY true! Hire a lousy lawyer at $60 per hour and he'll make the contract for you in twenty hours. Hire a good lawyer ay $400 per hour, and he'll say "We did this before, here's a standard contract for this sort of thing" and he'll bill you for an hour.
And of course Doller is a basterdised version of the Thaler wich is a basterdised version of Joachimsthaler.
more info