inetd.conf sucks Xinet sucks more, and no one knows anything about it
if you install the RPM, yes, GRUB will know about it. So we're not allowed to do anything to our computers that red hat does not dictat? I doubt any one who uses linux very much at all has made it from one version of red hat to another without completely breaking rpm compatibility.
* We don't break binary compatibility between minor releases or at least fail to notice in your extensive testing
If a standard is broken, it needs to be fixed. but not an arbitrary c++ standard that breaks tons of real working code?
most of our config tools try to parse existing config files rather than simply dumping any changes made by the user. Front page says the same thing, I'm sure when its editing HTML
This is intentional to make sure people calling up support can tell them which kernel they're running.
Maybe it's the reverse... Sony ported linux to the PS2 to keep them out of Sadaam Hussein's hands so he can't use them to drill for oil or launch ICBMs.
I enjoy my job. If I had my life to live all over again, I think I would still choose to be King. Look at all those peasants, surely they need someone to rule over them, and luckily, I enjoy being the top dog. What a happy fortune that has allowed one such as my self, who enjoys power and wealth and comfort to be born into this leadership role. And happy coincidence has allowed me, being born into this station, to enjoy my work. What dread it would be if some lowly peasant had the reigns of authority and luxury thrust upon him against his will.
openBSD is only especially secure as a default install, which means, essentially, turning all the services off. Kernel root exploits come about as common as linux, and they're using almost all the same apps
yeah...I'm going to go out and buy me a 32-way pentium. Its marketing hype. There is, in theory, and 8-way Xeon, but you can't find one. It's marketing hype, that in Microsoft's actual code isn't much more than a #define.
Something like this:
/* New and improved command line interface*/
char c[1024];
printf("(A)bort, (R)etry, or (F)ail?");
scanf("%c", &c[0]);
/* this will stop over a thousand times as many stack overruns, rendering windows virtually 100% secure */
wouldn't it be illegal for Intel to reverse engineer the Jericho 4 and find out if it used reverse engineered components from the pentium 4?
Re:Lets see if they get it right this time
on
MySQL 4.0 Released
·
· Score: 1
then use postgres. or mysql, when it has what you need. I don't control development over it either.
But if you took all the goodies out of postgres it would be alot faster and slimmer. Maybe faster than mysql at simple queries and inserts. But there is a place for a database that doesn't have transactions built in.
It would be an interesting exercise to build a modular database, with additional layers performing different levels of functionality, but probably less efficient at what people are used to doing. The difference is that it would be more extensible, and allow you to look at different ways of solving the problem.
Compare an X with Win32.
Re:Lets see if they get it right this time
on
MySQL 4.0 Released
·
· Score: 1
some of us don't want sub-selects, triggers, transactions, procedures, etc. embedded in our queries. Fine, you say, leave them out! But, alas, they still cause orders of magnitude overhead (nomatter the database) that some of us don't need. The database stores and retrieves records, anything else is extraneous. What would be nice is a wrapper layer of libraries around the core DB that can keep track of transactions, can feed one query into another, can compile schema-aware procedures, can detect changes, etc.
Now you cry for performance. True, it wouldn't be as fast, but the majority of queries don't need transactions. You could fetch 100 divergent results, change one of them, keep track of the change and not worry about the rest.
The biggest advantage to all this would be code maintainability. And, it would keep the database simple and allow it to run on slower hardware with less memory. All you need is rollback -- cache a specified set of queries. All you want is a couple of triggers. Lauch dbmonitord and have it keep an eye on those tables. That'll make locking a lot trickier, but be worth it.
MySQL 4.0 was not released. Anthrax is not deliverable by mail. The tooth fairy does not leave dollar bills. I'm getting sick of sensational journalism that is purely lies.
they aren't backing down, they're re-wording it. According to the RIAA spokesman in the article, they're trying to include in the amendment, statements to the fact that they already have permission to do as they please, which they don't. Essentially grandfathering in their future practice retroactively. It's a legalese time-machine.
The difference is that the ISPs are actually just transmitting data over the phone lines anyway. It would be like holding the phone booth company responsible for someone calling dial-a-tune (which would most likely happen if the phone companies didn't own the phone booths already)
and then some people got lazy and decided it was easier to just borrow apples that their neighbors had collected, which the neighbors were fine with, until they discovered they were the only ones picking apples, and they had to spend longer each day picking. They became bitter and decided to teach the lazy people a lesson and went to the apple tree and ate their apples on the spot, bringing none home. This caused bitter feelings in return from the lazy people, but when they got over it and went back to the tree they found the pickers blocking their way to the tree. They felt that since they had been the only ones picking apples for some time that the tree belonged to them and no one else. This upset the hoarders too, who felt like they had done nothing wrong. They didn't have any sympathy for the lazy people either, especially since they had turned to theiving, exactly as the hoarders had predicted. It was such a small effort to go to the tree every day, but now the tree was no longer available to everyone, and the bitter people excluded even those who had hoarded apples partly in revenge for being right, partly because they were blinded by their own bitterness, and in large part because it was in their nature to think that they were better than other people, especially when they saw profit in restricting others.
The reason you see this pattern is because of intellectual property laws. Actually, it has to do with business laws in general (in America, at least) since the same thing happens to other companies.
The difference with FreeBSD is that it is open source, so the developers can go right back to doing what they were before they got bought out, though a brief period of disorientation is to be expected.
It may have been worn out in past years, but maybe bears repeating. In computer terms, an operating system is the part that allows the different parts to interact. The kernel, if you will -- although the linux kernel is alot more than just the bare operating system, hence the term "monolithic" kernel. Programs that run on top of the operating system are called applications.
You could feasibly call the shell (or windowing system -- if that's all you have) that allows direct user interaction with the kernel a part of the OS. The confusion came when, as networking became a more common computing feature, some operating systems did not have that ability built in and so applications had to be written that provided it. Web servers, streaming video players, email clients, and games are all examples of applications, not operating systems.
Linux started about the same time as *BSD on x86. Despite the large code base imported from Berkeley and original AT&T Labs Unix, unsable linux distros (SMS/slack) were around before an ordinary person could install BSD on their home system. On the one hand, it was probably harder to port the original code with all the years of cruft than to create linux once Linus &Co. got the ball rolling, on the other hand, x86 BSD was able to inheret things like a mature scheduler and network stack as well as nice applications like sendmail.
The people who go in and out of the house don't use the internet to track it down. The don't use teleport rays either. The courts conclusion is that because there are pretty curtains on the windows and the defendents wore short skirts in court and they're lawyers knew how to grease the right wheels that there wouldn't be anyone going in and out of the house. Which there are. Lots of people. At odd hours.
Slashdot Mirror
inetd.conf sucks
Xinet sucks more, and no one knows anything about it
if you install the RPM, yes, GRUB will know about it.
So we're not allowed to do anything to our computers that red hat does not dictat? I doubt any one who uses linux very much at all has made it from one version of red hat to another without completely breaking rpm compatibility.
* We don't break binary compatibility between minor releases
or at least fail to notice in your extensive testing
If a standard is broken, it needs to be fixed.
but not an arbitrary c++ standard that breaks tons of real working code?
most of our config tools try to parse existing config files rather than simply dumping any changes made by the user.
Front page says the same thing, I'm sure when its editing HTML
This is intentional to make sure people calling up support can tell them which kernel they're running.
Okay that's funny, but it makes me wonder
Maybe it's the reverse... Sony ported linux to the PS2 to keep them out of Sadaam Hussein's hands so he can't use them to drill for oil or launch ICBMs.
said the happy monarch:
I enjoy my job. If I had my life to live all over again, I think I would still choose to be King. Look at all those peasants, surely they need someone to rule over them, and luckily, I enjoy being the top dog. What a happy fortune that has allowed one such as my self, who enjoys power and wealth and comfort to be born into this leadership role. And happy coincidence has allowed me, being born into this station, to enjoy my work. What dread it would be if some lowly peasant had the reigns of authority and luxury thrust upon him against his will.
Goethe was special because Nietzche liked him and Nietzche's special because you liked him?
sed s/\n/\n#/ etc/inet.d
openBSD is only especially secure as a default install, which means, essentially, turning all the services off. Kernel root exploits come about as common as linux, and they're using almost all the same apps
yeah...I'm going to go out and buy me a 32-way pentium. Its marketing hype. There is, in theory, and 8-way Xeon, but you can't find one. It's marketing hype, that in Microsoft's actual code isn't much more than a #define.
Something like this:
/* New and improved command line interface*/
char c[1024];
printf("(A)bort, (R)etry, or (F)ail?");
scanf("%c", &c[0]);
/* this will stop over a thousand times as many stack overruns, rendering windows virtually 100% secure */
wouldn't it be illegal for Intel to reverse engineer the Jericho 4 and find out if it used reverse engineered components from the pentium 4?
then use postgres. or mysql, when it has what you need. I don't control development over it either.
But if you took all the goodies out of postgres it would be alot faster and slimmer. Maybe faster than mysql at simple queries and inserts. But there is a place for a database that doesn't have transactions built in.
It would be an interesting exercise to build a modular database, with additional layers performing different levels of functionality, but probably less efficient at what people are used to doing. The difference is that it would be more extensible, and allow you to look at different ways of solving the problem.
Compare an X with Win32.
some of us don't want sub-selects, triggers, transactions, procedures, etc. embedded in our queries. Fine, you say, leave them out! But, alas, they still cause orders of magnitude overhead (nomatter the database) that some of us don't need. The database stores and retrieves records, anything else is extraneous. What would be nice is a wrapper layer of libraries around the core DB that can keep track of transactions, can feed one query into another, can compile schema-aware procedures, can detect changes, etc.
Now you cry for performance. True, it wouldn't be as fast, but the majority of queries don't need transactions. You could fetch 100 divergent results, change one of them, keep track of the change and not worry about the rest.
The biggest advantage to all this would be code maintainability. And, it would keep the database simple and allow it to run on slower hardware with less memory. All you need is rollback -- cache a specified set of queries. All you want is a couple of triggers. Lauch dbmonitord and have it keep an eye on those tables. That'll make locking a lot trickier, but be worth it.
MySQL 4.0 was not released. Anthrax is not deliverable by mail. The tooth fairy does not leave dollar bills. I'm getting sick of sensational journalism that is purely lies.
you deserve more than score 2
it was perfected in 1938, but Chamberlains "peace in our time" speech discredited it for a while.
no it isn't.
It's how much money you will continue to be able to donate to the government
Why not use CPRM? Pre-emptive lobotomies at birth. The doc's already doing circumcision
they aren't backing down, they're re-wording it. According to the RIAA spokesman in the article, they're trying to include in the amendment, statements to the fact that they already have permission to do as they please, which they don't. Essentially grandfathering in their future practice retroactively. It's a legalese time-machine.
no, mostly american corporations and gvt.
when was the last time you made an audio cassette recording. You can't make a decent copy with modern equipment, or modern cassettes
The difference is that the ISPs are actually just transmitting data over the phone lines anyway. It would be like holding the phone booth company responsible for someone calling dial-a-tune (which would most likely happen if the phone companies didn't own the phone booths already)
and then some people got lazy and decided it was easier to just borrow apples that their neighbors had collected, which the neighbors were fine with, until they discovered they were the only ones picking apples, and they had to spend longer each day picking. They became bitter and decided to teach the lazy people a lesson and went to the apple tree and ate their apples on the spot, bringing none home. This caused bitter feelings in return from the lazy people, but when they got over it and went back to the tree they found the pickers blocking their way to the tree. They felt that since they had been the only ones picking apples for some time that the tree belonged to them and no one else. This upset the hoarders too, who felt like they had done nothing wrong. They didn't have any sympathy for the lazy people either, especially since they had turned to theiving, exactly as the hoarders had predicted. It was such a small effort to go to the tree every day, but now the tree was no longer available to everyone, and the bitter people excluded even those who had hoarded apples partly in revenge for being right, partly because they were blinded by their own bitterness, and in large part because it was in their nature to think that they were better than other people, especially when they saw profit in restricting others.
The reason you see this pattern is because of intellectual property laws. Actually, it has to do with business laws in general (in America, at least) since the same thing happens to other companies.
The difference with FreeBSD is that it is open source, so the developers can go right back to doing what they were before they got bought out, though a brief period of disorientation is to be expected.
It may have been worn out in past years, but maybe bears repeating. In computer terms, an operating system is the part that allows the different parts to interact. The kernel, if you will -- although the linux kernel is alot more than just the bare operating system, hence the term "monolithic" kernel. Programs that run on top of the operating system are called applications.
You could feasibly call the shell (or windowing system -- if that's all you have) that allows direct user interaction with the kernel a part of the OS. The confusion came when, as networking became a more common computing feature, some operating systems did not have that ability built in and so applications had to be written that provided it. Web servers, streaming video players, email clients, and games are all examples of applications, not operating systems.
No, linux is an elected despot. The BSD teams are hereditary oligarchs. A commitee is not a democracy.
Linux started about the same time as *BSD on x86. Despite the large code base imported from Berkeley and original AT&T Labs Unix, unsable linux distros (SMS/slack) were around before an ordinary person could install BSD on their home system. On the one hand, it was probably harder to port the original code with all the years of cruft than to create linux once Linus &Co. got the ball rolling, on the other hand, x86 BSD was able to inheret things like a mature scheduler and network stack as well as nice applications like sendmail.
The people who go in and out of the house don't use the internet to track it down. The don't use teleport rays either. The courts conclusion is that because there are pretty curtains on the windows and the defendents wore short skirts in court and they're lawyers knew how to grease the right wheels that there wouldn't be anyone going in and out of the house. Which there are. Lots of people. At odd hours.
you're saying that those fascist extremists have gone so far as to give the president FREEDOM OF SPEECH!!?