Screw Desjardins, they are not regulated by bank charter. They made quite a few errors for accounts of a few people I know. Among others lost money, that they never refunded to the owner of the account because it was below a few grands (it was still a few hundred), quality of service vary greatly among every succursalle. While they can't make profit on paper, they can increase operating costs (read have huge beautifully decorated buildings). I'm currently for now with RBC, 'til I find some other place to move my money (I have money in their funds, so when SCOX crash I'll lose money).
The SCO Group (Nasdaq: SCOX) helps millions of customers [snip] with UNIX business solutions.
And here's a quote from Darl's latest interview:
Hundreds of customers like and use SCO's Unix products.
I'm surprised that there are hundred of persons that like SCO Unix. I've seen plently use it, but none that liked it.
Look at this:
Itanium back in '95 at the end of section HP Technical Briefing Report, and you'll see the talk about the PA9000 processor, a VLIW based processor.
In fact the Itanium is much more similar to PA-RISC (could be called PA-RISC 3.0) than to the x86. PA-RISC developpement had been based on need while maintaining a clean architecture. There is also MIPS that architecture changes are apporved by a comitee as another way of design.
That was a simpler file transfer similar to FTP, but based on UDP for faster file transfert.
In it's time most of the sites using it where for trading copyrighted software (warez).
After 1995, I've not seen much of FSP.
PA-RISC processors doesn't suck. They are high performance chip, unlike Sparc processors that have been disapointing. The chip itself was pretty well designed and improvement where made in a logical way. Who in '95 had a workstation that could play mpeg at 30fps with only software decode (PA-7100LC, aka PA-RISC 1.1c)?
The HP9000 are expensive, but made to last. The Sun Netra t1 aAC200 are cheaper, but the failure rate so far has been abysmal (maybe we where unlucky) and performance sucks (barely overperform a P2-400 and cost about 4000$).
For HP-UX, while I have to agree that HP-UX 9.xx and before did suck, it's been quite a while that it's not supported anymore and 10.20 is out (1994). They don't have the latest toy, but are reasonably up to date, managable, predictable and so far the Unix the more stable I've seen.
The Itanium had been made by HP and Intel, it currently run HP-UX and can run HP-UX applications from PA-RISC systems without recompile. The transition was IMHO planned, maybe it could have been called IA64/PA-RISC3.0...
The LVM in HP-UX is base on the one of IBM,
HP instead of developping their own LVM and
Journaling File System they took the best available at the time. Don't reinvent the wheel.
JFS does have ACL (HP-UX 11.00 with JFS installed, free and HP-UX 11i has too).
It just use the Veritas commands for the ACL, not the one for HFS.
LVM on Linux is supposed to be based on the ideas of HP-UX and I think commands are compatible.
Having worked with Linux, Solaris, HP-UX, Irix, UnixWare, a little of FreeBSD, SunOS and OpenServer. I consider that HP-UX is one of the niciest OS I've worked with, easier to administer than Solaris and cleaner than Linux. I still like Linux and like Solaris and also liked the eye candy of Irix.
Sorry, but this is far from the reality.
When programming under DOS (MZ), Unix (ELF) or Win32 (COFF). The debugging info is not in the middle of a text (code) segment.
Under DOS debugging info was in the overlay, under linux it's (if my memory is right) in the.stabs and.symtabs section. COFF should be similar.
Debugging info affect load time, but not execution time.
Usually programs with debug infos have less optimization too.
That's why you can strip a program with debugging infos, it's just remove the ELF/COFF/... sections that contains the debugging info.
By agreeing to this license:
1. You certify that you are not member of:
i) RIAA
ii) Lawyer association
iii) Law enforcement
iv) An artist with copyrighted works
2. That you won't sue us.
should begin with: So you too have been sued by Mattel.
What is needed for real NIC failover.
on
Linux Failover?
·
· Score: 1
For rel NIC failover, you need to have 2 cards (or more) or a dual port card. The OS must support changing the IP address of the 2nd card and reprogramming it's MAC address so the router will see it as the first card. Some routers don't like to see the same IP from a different port with a different MAC address. A real world example would be 2 Cisco Catalyst plugged together. And each computer having one card on each Catalyst. Each Catalyst will have also a link to the outside. Unless the link between the 2 Catalyst is down AND one of the card is down everything will work fine.
SCO UnixWare does support NIC failover (for cards that support MAC address reprogramming), unfortunately it's not one of the most stable OS that I saw.
Sometimes the same computer must complete the transaction, using another one is not an option (telephony come to mind).
Altough some may think otherwise (or are just uninformed)... Microsoft Office (at least 4.3) did exist for the Alpha. As well as Microsoft Word 97 and Excel 97. For the endianess, the Alpha is little endian like x86 chips. If you don't know, just don't assume...
Having worked with multi-lingual Web sites, I must precise a few points.
First you need to remember that a Web site must be designed to work easilly with existing tools you use to develop/maintain Web site. Altough Javascript seem nice, the maintenance seem to me like a nightmare.
Having one directory per language for static pages seem so much easier to maintain for content change. For design change it's more of a pain.
Ask yourself, does your organisation is more likely to change contents or design? Generally I would think in more organisations that content is more likely to change than design. Do your planning accordingly.
PS: For Canadian websites, the Canadian federal governement as a directive that a website MUST be bilingual (English/French) or not to exist at all.
I have access to a HP Vizualize workstation, dual 440 Mhz processor, each is somewhat faster than what a Pentium 3 at 800 would give and architecture is somewhat better and it can use PCI cards and USB components (if drivers exist)...
As for class N machines a recent one will have at least 2 processor (what we have is 2 class N with 4 processors each and a shared Raid Array)... These machine are physically huge, they are extremely fast and extremely expensive. They have much better performance than you can have with any x86-based computer right now. They don't have a great price/performance ratio, but sometime you need the performance they deliver...
A company that won't allow easters eggs and no credits, has IMHO lost his sense of humor and its soul... It was nice when Apple where not only colored computers, we'll miss it...
For precious data, I agree that Raid-0 is insane. but for temporary data that doesn't need to be 100% sure to be kept, that can be a good solution. For a news server spool, if it crash replace the disk and the standard NNTP messages will refill the news spool shortly (depending of the connection speed)... Of course OS disk and what users send and other data that is more important should not be on Raid-0...
Slashdot Mirror
Windows machine pour be more like a lemon tree
Unfortunately goatse the movie exists.
If you look on stileproject.com you can find it, if you really wish. I wouldn't wish that however.
Look this patch for Solaris from Sun:
ROC timezone should be avoided for political reasons
As ilustred by them procrastination can be good.
They could ask Bank of America for more money.
After all BoA should be grateful that SCO didn't sue them.
Screw Desjardins, they are not regulated by bank charter. They made quite a few errors for accounts of a few people I know. Among others lost money, that they never refunded to the owner of the account because it was below a few grands (it was still a few hundred), quality of service vary greatly among every succursalle. While they can't make profit on paper, they can increase operating costs (read have huge beautifully decorated buildings). I'm currently for now with RBC, 'til I find some other place to move my money (I have money in their funds, so when SCOX crash I'll lose money).
I'm surprised that there are hundred of persons that like SCO Unix. I've seen plently use it, but none that liked it.
HP C++ compiler (aCC) is not based on Cfront. The older C++ compiler (forgot the name) that was obsoleted a while ago was.
Look at this: Itanium back in '95 at the end of section HP Technical Briefing Report, and you'll see the talk about the PA9000 processor, a VLIW based processor. In fact the Itanium is much more similar to PA-RISC (could be called PA-RISC 3.0) than to the x86. PA-RISC developpement had been based on need while maintaining a clean architecture. There is also MIPS that architecture changes are apporved by a comitee as another way of design.
That was a simpler file transfer similar to FTP, but based on UDP for faster file transfert.
In it's time most of the sites using it where for trading copyrighted software (warez).
After 1995, I've not seen much of FSP.
PA-RISC processors doesn't suck. They are high performance chip, unlike Sparc processors that have been disapointing. The chip itself was pretty well designed and improvement where made in a logical way. Who in '95 had a workstation that could play mpeg at 30fps with only software decode (PA-7100LC, aka PA-RISC 1.1c)?
The HP9000 are expensive, but made to last. The Sun Netra t1 aAC200 are cheaper, but the failure rate so far has been abysmal (maybe we where unlucky) and performance sucks (barely overperform a P2-400 and cost about 4000$).
For HP-UX, while I have to agree that HP-UX 9.xx and before did suck, it's been quite a while that it's not supported anymore and 10.20 is out (1994). They don't have the latest toy, but are reasonably up to date, managable, predictable and so far the Unix the more stable I've seen.
The Itanium had been made by HP and Intel, it currently run HP-UX and can run HP-UX applications from PA-RISC systems without recompile. The transition was IMHO planned, maybe it could have been called IA64/PA-RISC3.0...
The LVM in HP-UX is base on the one of IBM,
HP instead of developping their own LVM and
Journaling File System they took the best available at the time. Don't reinvent the wheel.
JFS does have ACL (HP-UX 11.00 with JFS installed, free and HP-UX 11i has too).
It just use the Veritas commands for the ACL, not the one for HFS.
LVM on Linux is supposed to be based on the ideas of HP-UX and I think commands are compatible.
Having worked with Linux, Solaris, HP-UX, Irix, UnixWare, a little of FreeBSD, SunOS and OpenServer. I consider that HP-UX is one of the niciest OS I've worked with, easier to administer than Solaris and cleaner than Linux. I still like Linux and like Solaris and also liked the eye candy of Irix.
Sorry, but this is far from the reality. .stabs and .symtabs section. COFF should be similar.
When programming under DOS (MZ), Unix (ELF) or Win32 (COFF). The debugging info is not in the middle of a text (code) segment.
Under DOS debugging info was in the overlay, under linux it's (if my memory is right) in the
Debugging info affect load time, but not execution time.
Usually programs with debug infos have less optimization too.
That's why you can strip a program with debugging infos, it's just remove the ELF/COFF/... sections that contains the debugging info.
By agreeing to this license:
1. You certify that you are not member of:
i) RIAA
ii) Lawyer association
iii) Law enforcement
iv) An artist with copyrighted works
2. That you won't sue us.
should begin with: So you too have been sued by Mattel.
SCO UnixWare does support NIC failover (for cards that support MAC address reprogramming), unfortunately it's not one of the most stable OS that I saw.
Sometimes the same computer must complete the transaction, using another one is not an option (telephony come to mind).
Altough some may think otherwise (or are just uninformed)... Microsoft Office (at least 4.3) did exist for the Alpha. As well as Microsoft Word 97 and Excel 97. For the endianess, the Alpha is little endian like x86 chips. If you don't know, just don't assume...
Having worked with multi-lingual Web sites, I must precise a few points.
First you need to remember that a Web site must be designed to work easilly with existing tools you use to develop/maintain Web site. Altough Javascript seem nice, the maintenance seem to me like a nightmare.
Having one directory per language for static pages seem so much easier to maintain for content change. For design change it's more of a pain.
Ask yourself, does your organisation is more likely to change contents or design? Generally I would think in more organisations that content is more likely to change than design. Do your planning accordingly.
PS: For Canadian websites, the Canadian federal governement as a directive that a website MUST be bilingual (English/French) or not to exist at all.
and decided to make a contribution to the Dead Media Project.
Can we bet on who will win?
was called BLINK.
If M$ would publish the source of Windows, they would surely won... Some unintelligible code that compile and run (sort of)...
As for class N machines a recent one will have at least 2 processor (what we have is 2 class N with 4 processors each and a shared Raid Array)... These machine are physically huge, they are extremely fast and extremely expensive. They have much better performance than you can have with any x86-based computer right now. They don't have a great price/performance ratio, but sometime you need the performance they deliver...
A company that won't allow easters eggs and no credits, has IMHO lost his sense of humor and its soul... It was nice when Apple where not only colored computers, we'll miss it...
For precious data, I agree that Raid-0 is insane.
but for temporary data that doesn't need to be 100% sure to be kept, that can be a good solution.
For a news server spool, if it crash replace the disk and the standard NNTP messages will refill the news spool shortly (depending of the connection speed)...
Of course OS disk and what users send and other data that is more important should not be on Raid-0...