People like looking for '1234567890' and stuff like that in Pi
Stunning, does the sequence 1234567890 actually appear in the digits of Pi? And does it even appear as frequent as any other 10 digit combination?;-)
Hey, they ought to do that with the binary representation. I bet it won't take long time to find the sequence 10 somewhere in the binary representation of Pi. That would save them a lot of work.
However, you _really_ don't want to do radix conversion on numbers that large if you have the chance of avoiding it.
But if there are too many digits to convert the base what is really the purpose of computing the number in the first place? It is not like there is anything magical about the base 10. It is surely not the easiest base to compute the number in, and it is surely neither the the most usefull base to have the number in for future use.
There is no garantee about binary compatibility for kernel code between any versions. Not even same source compiled with different options are garanteed to be binary compatible. You can however expect most driver sources to be compatible between the 2.2.x kernels.
Lindows is the only Linux distribution
that is excelling in marketing Linux to
consumers.
Is it really so? I have never seen Lindows marketet, but they they are only marketing
it in America.
And how used is the Lindows distribution?
Has it really become the most used distribution?
I know you can buy computers with Lindows preinstalled, but it is not the only distribution
you can buy preinstalled.
Seems Lindows is imitating Windows too much for a good Linux distribution. They have more or less neglected the traditional security of Linux by running everything as root. And they are selling their product on marketing rather than quality.
Will it support pci modems?
Will PCI modems support Linux? Will crappy hardware become better?
Will it get rid of the fucking cli for good and boot DIRECTLY in to X?
That is not a Linux issue. Neither cli nor X is a part of Linux. My distribution has been capable of booting directly into X for more than three years. But my computer has never done that, because I know how to use the command line. And to he who knows the command line it is the most powerfull user interface in existence.
Will it tell Stallman to fuck off for trying to put gnu/ on it.
He never requested GNU to be part of the name of Linux. He just requested that CDs containing 1% Linux and 60% GNU would at least have GNU in the name.
and last but most importantly, will you be able to to swtich kernels with out rebooting (is it that hard?, why dosent the kernel just unload it self from memory and go back to the boot menu?)
Work is being done in that area. I however don't know if kexec will make it for this version. I have previously been using kmonte, but it hasn't been developed since 2.2, and new kernels was changed in ways breaking kmonte for good.
Like fuckin hell I'd replace my perfectly working BIOS with some lame-ass hack bios that is likely to lock up and prevent me from booting my PC....
I have seen more than one BIOS crash if it saw a harddisk of more than 31.49GB. Entering the BIOS setup at boot was possible the first few times I tried, but the HD detection would also crash. Finally I tried manually entering disk geometry, but it would still crash. After a few attempts it started crashing before the memory test. Even removing the HD didn't solve the problem. Luckily the CMOS reset jumper allowed me to boot the system again.
Now I come to the best part. I could tell the BIOS to ignore the drive. Linux would still find the drive and use it without problems. So in my case it certainly was the conventional BIOS causing me trouble, not Linux. The only thing keeping me away from experimenting with a different BIOS is the difficulty of recovering from a broken version. If a new kernel fails to boot I can always go back to the old version or ultimately boot from a backup CD. But what do I do if my BIOS fails to boot? I would worry about that no matter where the BIOS code came from.
Linux has become tainted by the use of non-free tools like BitKeeper and closed source binary 3rd party drivers.
A project doesn't have to inherit the license of the development tools used. If that had been the case no part of the GNU software would be free, because the very first version of gcc was probably compiled with another compiler under a different license.
The 3rd party drivers is of course a minor problem. But the borders are being drawn. It can now explicitly be specified which symbols exported by the kernel can legally be used by such drivers. The kernel is tainted upon load of such drivers, and all bug reports are directed to the author.
It would have been wiser to use more reliable drives for cluster work such as seagates or ibm's.
Yes, they should have bought IBM deskstars instead. They are cheap and they know exactly what they are going to get.
Last year I bought a maxtor harddrive, only thing it ever did for me was crash my BIOS. So I got it replaced with a deskstar, at least I knew that one was going to work. It did.... for half a year. And BTW since then I have only bought seagate drives.
Now, it's quite reasonable that Word Processor 1.0 will choke on the tables in a document that Word Processor 2.0 creates, isn't it?
That depends on how smart you were when designing the original format. At worst you could expect the tables to disapear or just look funny (i.e. not like tables). But you could have been smart and have formating features in the original format that version 2 could use to tell version 1 how this is supposed to look. This is of course not going to help version 1 when editing the tables, but at least it could display the document.
False. The ".doc" format is definitely not simple.
Saying it is simply a memory dump is not the same as saying the format is simple. If it is merely a dump of in memory structures, the format on disk will be as complex as the structures in memory. And the format in memory is probably not simple because it is some compilers representation of whatever structures is defined in the source which are again subject to certain conventions and invariant which are (hopefully) known to the programmer of the project. Understanding such a file format is really little different from understanding the entire application which has generated it, and compatibility can only be achived by duplicating most of the application. But luckily to the people using such methods for saving data, saving and loading it can be a lot easier than understanding the format. It will work as long as the data are loaded in the same program that they were originally saved from.
Since.doc is not 100% incompatible between different versions of word, and since somebody but ms has actually sucessfully loaded a.doc file, the format is probably not as bad as a simple memory dump. But certainly the format doesn't look much better than that. I'm really looking forward to this new specification being released. Finally I can say to all those jokers sending.doc files, that they should be using the X format. (X means I don't know what will be the name of this new format.)
Meanwhile we (the consumer) suffer because we get things like cd's we can't play in our computer.
They may look like CD's, but they are not. Return it and demand to get your money back. (Or an exchange for a real CD which is of course impossible because the title is not available on CD.)
I have been thinking about the amount of time being wasted on spam. I installed an SMTP honeypot looking like an open relay, but in reallity it just acts like a black hole. Once I recieved 35 million spam mails in 4 days. If the average recipient would have spent just one second deleting this spam, I have saved them a total of more than one year of work. Think about it, more than one your of just deleting spam mails!
What have you done to fight spam in general, and not just the spam in your own inbox?
make oldconfig dep clean modules modules_install install
Yes oldconfig is nice when you already have a.config file from a previous kernel. But I have really been missing xoldconfig, that will give me the xconfig interface but with only the questions I'd need to answer when using oldconfig.
I don't know much about Taiwan. Except from the fact that it is there
half the spam comes from. Or is that really a fact? Perhaps China has
somehow been able to forge entire SMTP sessions seeming to come from
Taiwan?
He probably also knows that we know he knows we know... you know?
You got a point there, I see. But does he already know that we think he probably knows that we know he knows we know? Anyway I really don't care what he knows, I just want to know what he is going to do.
Who says the hacker would need more than 8 hours? Why would he even need more than 2 hours? All he has to do is read the disk. If he can read what the reader reads, and he knows what else the reader does, it takes no longer to copy the disk than it takes to read the disk. This is really not a question about cracking a disk, this is all about knowing what your drive and or software does. And you can find out about that beforehand. Once he has the disk in his hands he will already know what to do with it. This will take less than 8 hours.
The convenience to whom? I have always thought about AutoPlay as a security hole. It could be used by vira to infect a system by just inserting an infected media. A similar security hole existed in AmigaOS 1.x, and multiple vira used it. It was fixed in AmigaOS 2.0, which IIRC was released in the early nineties. Approximately five years after the bug was fixed in AmigaOS a similar bug was introduced in Windows (Microsoft has always been lagging behind). I think the only reason this didn't cause an immediate spread of vira as soon as Windows 95 was released is the fact that it only affected CDs which are not written as easy as most other media. The problem in AmigaOS did for sure affect floppies, and AFAIK any other media as well.
Slashdot Mirror
People like looking for '1234567890' and stuff like that in Pi
;-)
Stunning, does the sequence 1234567890 actually appear in the digits of Pi? And does it even appear as frequent as any other 10 digit combination?
Hey, they ought to do that with the binary representation. I bet it won't take long time to find the sequence 10 somewhere in the binary representation of Pi. That would save them a lot of work.
However, you _really_ don't want to do radix conversion on numbers that large if you have the chance of avoiding it.
But if there are too many digits to convert the base what is really the purpose of computing the number in the first place? It is not like there is anything magical about the base 10. It is surely not the easiest base to compute the number in, and it is surely neither the the most usefull base to have the number in for future use.
binary compatibility with any drivers
There is no garantee about binary compatibility for kernel code between any versions. Not even same source compiled with different options are garanteed to be binary compatible. You can however expect most driver sources to be compatible between the 2.2.x kernels.
other comments
The difference is that the comment can get moderated redundant. Why can't the resumes on the main page be moderated?
Lindows is the only Linux distribution that is excelling in marketing Linux to consumers.
Is it really so? I have never seen Lindows marketet, but they they are only marketing it in America. And how used is the Lindows distribution? Has it really become the most used distribution? I know you can buy computers with Lindows preinstalled, but it is not the only distribution you can buy preinstalled.
Seems Lindows is imitating Windows too much for a good Linux distribution. They have more or less neglected the traditional security of Linux by running everything as root. And they are selling their product on marketing rather than quality.
Big time storry when RedHat nullified the difference between Gnome and KDE. Where is the story about Lindows nullifying the difference between GNU/Linux and Windows?
The headline says Linux, the article says Lindows all over. Is Lindows the only GNU/Linux distribution they care about?
Will PCI modems support Linux? Will crappy hardware become better?
That is not a Linux issue. Neither cli nor X is a part of Linux. My distribution has been capable of booting directly into X for more than three years. But my computer has never done that, because I know how to use the command line. And to he who knows the command line it is the most powerfull user interface in existence.
He never requested GNU to be part of the name of Linux. He just requested that CDs containing 1% Linux and 60% GNU would at least have GNU in the name.
Work is being done in that area. I however don't know if kexec will make it for this version. I have previously been using kmonte, but it hasn't been developed since 2.2, and new kernels was changed in ways breaking kmonte for good.
What does this "kernel" program do and where can I download it?
The kernel can obviously be downloaded from kernel.org.
Like fuckin hell I'd replace my perfectly working BIOS with some lame-ass hack bios that is likely to lock up and prevent me from booting my PC....
I have seen more than one BIOS crash if it saw a harddisk of more than 31.49GB. Entering the BIOS setup at boot was possible the first few times I tried, but the HD detection would also crash. Finally I tried manually entering disk geometry, but it would still crash. After a few attempts it started crashing before the memory test. Even removing the HD didn't solve the problem. Luckily the CMOS reset jumper allowed me to boot the system again.
Now I come to the best part. I could tell the BIOS to ignore the drive. Linux would still find the drive and use it without problems. So in my case it certainly was the conventional BIOS causing me trouble, not Linux. The only thing keeping me away from experimenting with a different BIOS is the difficulty of recovering from a broken version. If a new kernel fails to boot I can always go back to the old version or ultimately boot from a backup CD. But what do I do if my BIOS fails to boot? I would worry about that no matter where the BIOS code came from.
Linux has become tainted by the use of non-free tools like BitKeeper and closed source binary 3rd party drivers.
A project doesn't have to inherit the license of the development tools used. If that had been the case no part of the GNU software would be free, because the very first version of gcc was probably compiled with another compiler under a different license.
The 3rd party drivers is of course a minor problem. But the borders are being drawn. It can now explicitly be specified which symbols exported by the kernel can legally be used by such drivers. The kernel is tainted upon load of such drivers, and all bug reports are directed to the author.
It would have been wiser to use more reliable drives for cluster work such as seagates or ibm's.
Yes, they should have bought IBM deskstars instead. They are cheap and they know exactly what they are going to get.
Last year I bought a maxtor harddrive, only thing it ever did for me was crash my BIOS. So I got it replaced with a deskstar, at least I knew that one was going to work. It did.... for half a year. And BTW since then I have only bought seagate drives.
Now, it's quite reasonable that Word Processor 1.0 will choke on the tables in a document that Word Processor 2.0 creates, isn't it?
That depends on how smart you were when designing the original format. At worst you could expect the tables to disapear or just look funny (i.e. not like tables). But you could have been smart and have formating features in the original format that version 2 could use to tell version 1 how this is supposed to look. This is of course not going to help version 1 when editing the tables, but at least it could display the document.
- .doc is a simple dump of the memory state,
- False. The ".doc" format is definitely not simple.
Saying it is simply a memory dump is not the same as saying the format is simple. If it is merely a dump of in memory structures, the format on disk will be as complex as the structures in memory. And the format in memory is probably not simple because it is some compilers representation of whatever structures is defined in the source which are again subject to certain conventions and invariant which are (hopefully) known to the programmer of the project. Understanding such a file format is really little different from understanding the entire application which has generated it, and compatibility can only be achived by duplicating most of the application. But luckily to the people using such methods for saving data, saving and loading it can be a lot easier than understanding the format. It will work as long as the data are loaded in the same program that they were originally saved from.Since
Meanwhile we (the consumer) suffer because we get things like cd's we can't play in our computer.
They may look like CD's, but they are not. Return it and demand to get your money back. (Or an exchange for a real CD which is of course impossible because the title is not available on CD.)
That's before overclocking.
I don't want to overclock my brain.
this is an everyday DOS attack on all of us.
I have been thinking about the amount of time being wasted on spam. I installed an SMTP honeypot looking like an open relay, but in reallity it just acts like a black hole. Once I recieved 35 million spam mails in 4 days. If the average recipient would have spent just one second deleting this spam, I have saved them a total of more than one year of work. Think about it, more than one your of just deleting spam mails!
What have you done to fight spam in general, and not just the spam in your own inbox?
have not yet been invented.
I always had the impression it hasn't been invented because it is basically impossible.
This is easier:
.config file from a previous kernel. But I have really been missing xoldconfig, that will give me the xconfig interface but with only the questions I'd need to answer when using oldconfig.
make oldconfig dep clean modules modules_install install
Yes oldconfig is nice when you already have a
One must also consider the often overlooked cost of not changing over...
Indeed, and that const is not going to get any smaller by waiting.
how will they see outside?!?
You think there is a world outside????
I don't know much about Taiwan. Except from the fact that it is there half the spam comes from. Or is that really a fact? Perhaps China has somehow been able to forge entire SMTP sessions seeming to come from Taiwan?
he doesnt have to go anywhere near Windows Explorer or My Computer, where he has been told by the office geek that he can seriously screw over his PC.
Yeah, people don't want to screw their PC, it is so much easier to have somebody else doing it for them.
He probably also knows that we know he knows we know... you know?
You got a point there, I see. But does he already know that we think he probably knows that we know he knows we know? Anyway I really don't care what he knows, I just want to know what he is going to do.
after 8 hours the hacker would need another disc.
Who says the hacker would need more than 8 hours? Why would he even need more than 2 hours? All he has to do is read the disk. If he can read what the reader reads, and he knows what else the reader does, it takes no longer to copy the disk than it takes to read the disk. This is really not a question about cracking a disk, this is all about knowing what your drive and or software does. And you can find out about that beforehand. Once he has the disk in his hands he will already know what to do with it. This will take less than 8 hours.
the convenience of AutoPlay
The convenience to whom? I have always thought about AutoPlay as a security hole. It could be used by vira to infect a system by just inserting an infected media. A similar security hole existed in AmigaOS 1.x, and multiple vira used it. It was fixed in AmigaOS 2.0, which IIRC was released in the early nineties. Approximately five years after the bug was fixed in AmigaOS a similar bug was introduced in Windows (Microsoft has always been lagging behind). I think the only reason this didn't cause an immediate spread of vira as soon as Windows 95 was released is the fact that it only affected CDs which are not written as easy as most other media. The problem in AmigaOS did for sure affect floppies, and AFAIK any other media as well.