He said "It is a lot like Debian but with a lot of extra value added in. My favorite feature is their kernel compiling setup." I was simply saying that this feature, at least as it was described by the poster, was an instance of "extra value" on top of regular Debian. I did not intend to slight Libranet at all.
After you recompile the kernel it adds the newly recompiled kernel to lilo and keeps the old kernel as a lilo option so you can switch back if you have any problems.
You can do this in regular Debian too, with kernel-package.
The problem with debian's setup is that it leaves you with a system that requires a lot of manual configuration
No, this is simply not true. You get a working Debian system once it's installed, without a need to edit any configuration files. Of course, if you want to make the configuration perfect for you, that's great and you'd have to edit the configuration files in any other distribution as well.
the default settings for X are inadequate in almost any case
I've installed woody on 5 different systems, each with very different hardware configurations, and X has worked properly through the script used in Debian to configure it (no need to edit configuration files).
you need to update all sorts of packages to more recent versions (which are not in stable) and most likely you also need to update the kernel
No, you don't need to update anything. If you want to update some of your software to more recent versions, then obviously you can update them, and with apt-get and the Debian packages it's easier than in any other distribution. The same is true of the kernel.
you also need to manually configure other plug & play stuff such as sound cards, printers, scanners etc Sound cards should work fine without any manual configuration. Printers can be configured easily using the many tools available, some of which are as easy as selecting which printer you have. I have no experience configuring scanners.
Doing so is not easy in a bare bones linux installation and requires manually editing dozens of text based configuration files and running several non trivial commands (for plug and play devices that other linux distros configure automatically).
You don't end up with a bare bones Linux installation when installing Debian. You can select and install any of the tools you want without needing to edit anything. "Dozens" of configuration files to edit is an exaggeration even for arcane hardware (which is equally (non)supported on any other distribution) and, just like the rest of this post, is flamebait.
For stable releases, Debian backports the patches to the version that's in stable, so as not to introduce problems that may result from introducing a relatively heavily modified new release. That's why it's called "stable". From the Debian Security Advisory: "These vulnerabilities have been addressed for Debian 3.0 (woody) in openssl094_0.9.4-6.woody.0, openssl095_0.9.5a-6.woody.0 and openssl_0.9.6c-2.woody.0." So, the link provided is a package that isn't vulnerable.
gcc 2.95 is the standard that everyone has been using for a long time, so that version wouldn't be a problem. You probably mean gcc "2.96" that Mandrake released to be compatible with Red Hat.
Well, actually, Debian allows you to try the latest and greatest, on the same level as Red Hat, and then allows you to also run the latest and greatest, stuff that's newer than Red Hat. So, if that's all you want, Debian has a branch for everyone.:)
It seems he was talking about the proper handling of dependencies. According to Debian policy, the "Recommends" dependency "declares a strong, but not absolute, dependency" and that recommended packages "would be found together with this one in all but unusual installations." Thus, when one installs a package, that packages Recommends dependencies should be satisfied by default, and overridden in "unusual installations." However, apt-get does not satisfy Recommends dependencies. dselect, on the other hand, does satisfy Recommends dependencies, and thus installing using dselect ensures a better installation, without missing important packages.
The software that SuSE makes is also proprietary. Not offering ISO images is purposefully limiting the possibilities of distribution, which is clearly against established practices of "linux ideals".
If it's just a cap on the framerate, it doesn't matter at all. Your eye can't distinguish a difference in framerates at 50 fps anyway. The only reason benchmarks even bother showing high framerates of 150 fps and whatnot is to show the relative performance of the hardware (or in this case, software) for future games.
So what? If there is no fundamental human change to make humans "eat" radiation (which is highly unlikely considering the huge change that would need to occur), then the radiation is still dangerous to them. If there is this highly unlikely change, then being deterred from the site makes no difference to them anyway. So, in the more probable case, the warnings make much sense, and in the less probable case, it doesn't really matter either way.
Yes, the key is that there does have to be some artificial dividing line. The thing is, when you have cameras taking photographs that dividing line is extremely strict, there is no leeway. If you have a cop watching out for your violation, the line is a bit more fuzzy, making the determination of "breaking the law" dependent on the safety of that specific situation, determined by the judgement of the cop.
Slashdot Mirror
Sorry, I was saying that the feature, as described, was NOT an instance of extra value over Debian.
He said "It is a lot like Debian but with a lot of extra value added in. My favorite feature is their kernel compiling setup." I was simply saying that this feature, at least as it was described by the poster, was an instance of "extra value" on top of regular Debian. I did not intend to slight Libranet at all.
Every new version of IE just gets bulkier and slower if you're not running the latest hardware.
You can do this in regular Debian too, with kernel-package.
No it wasn't. It was an insecure piece of shit, with a few nifty closed-source add-ons to make it unique.
gcc3.2 is packaged in Debian testing and Debian unstable.
PGI (from Progeny) is being ported and updated.
The electoral college is rather nice in distributing representation geographically as well as by population.
No, this is simply not true. You get a working Debian system once it's installed, without a need to edit any configuration files. Of course, if you want to make the configuration perfect for you, that's great and you'd have to edit the configuration files in any other distribution as well.
the default settings for X are inadequate in almost any case
I've installed woody on 5 different systems, each with very different hardware configurations, and X has worked properly through the script used in Debian to configure it (no need to edit configuration files).
you need to update all sorts of packages to more recent versions (which are not in stable) and most likely you also need to update the kernel
No, you don't need to update anything. If you want to update some of your software to more recent versions, then obviously you can update them, and with apt-get and the Debian packages it's easier than in any other distribution. The same is true of the kernel.
you also need to manually configure other plug & play stuff such as sound cards, printers, scanners etc
Sound cards should work fine without any manual configuration. Printers can be configured easily using the many tools available, some of which are as easy as selecting which printer you have. I have no experience configuring scanners.
Doing so is not easy in a bare bones linux installation and requires manually editing dozens of text based configuration files and running several non trivial commands (for plug and play devices that other linux distros configure automatically).
You don't end up with a bare bones Linux installation when installing Debian. You can select and install any of the tools you want without needing to edit anything. "Dozens" of configuration files to edit is an exaggeration even for arcane hardware (which is equally (non)supported on any other distribution) and, just like the rest of this post, is flamebait.
How do you know that?
People employed by the government to fight drugs, and companies that supply the government with tools to fight drugs are also beneficiaries.
Since when does marijuana kill brain cells. Please point to a source for this.
For stable releases, Debian backports the patches to the version that's in stable, so as not to introduce problems that may result from introducing a relatively heavily modified new release. That's why it's called "stable". From the Debian Security Advisory: "These vulnerabilities have been addressed for Debian 3.0 (woody) in openssl094_0.9.4-6.woody.0, openssl095_0.9.5a-6.woody.0 and openssl_0.9.6c-2.woody.0." So, the link provided is a package that isn't vulnerable.
gcc 2.95 is the standard that everyone has been using for a long time, so that version wouldn't be a problem. You probably mean gcc "2.96" that Mandrake released to be compatible with Red Hat.
Why would anyone think that?
So?
Well, actually, Debian allows you to try the latest and greatest, on the same level as Red Hat, and then allows you to also run the latest and greatest, stuff that's newer than Red Hat. So, if that's all you want, Debian has a branch for everyone. :)
In Debian, it's also what's behind apt-get: tons and tons of stable and secure packages.
It seems he was talking about the proper handling of dependencies. According to Debian policy, the "Recommends" dependency "declares a strong, but not absolute, dependency" and that recommended packages "would be found together with this one in all but unusual installations." Thus, when one installs a package, that packages Recommends dependencies should be satisfied by default, and overridden in "unusual installations." However, apt-get does not satisfy Recommends dependencies. dselect, on the other hand, does satisfy Recommends dependencies, and thus installing using dselect ensures a better installation, without missing important packages.
azpenguin's grandfather isn't as mentally sharp as he thinks he is.
So why don't you just use woody now?
The software that SuSE makes is also proprietary. Not offering ISO images is purposefully limiting the possibilities of distribution, which is clearly against established practices of "linux ideals".
If it's just a cap on the framerate, it doesn't matter at all. Your eye can't distinguish a difference in framerates at 50 fps anyway. The only reason benchmarks even bother showing high framerates of 150 fps and whatnot is to show the relative performance of the hardware (or in this case, software) for future games.
So what? If there is no fundamental human change to make humans "eat" radiation (which is highly unlikely considering the huge change that would need to occur), then the radiation is still dangerous to them. If there is this highly unlikely change, then being deterred from the site makes no difference to them anyway. So, in the more probable case, the warnings make much sense, and in the less probable case, it doesn't really matter either way.
Yes, the key is that there does have to be some artificial dividing line. The thing is, when you have cameras taking photographs that dividing line is extremely strict, there is no leeway. If you have a cop watching out for your violation, the line is a bit more fuzzy, making the determination of "breaking the law" dependent on the safety of that specific situation, determined by the judgement of the cop.