Sounds like it is your hardware that is at fault. If you disable the onboard sound card in the BIOS then it shouldn't be visible to the operating system in the first place, or so it is with the hardware that I have used.
You can always put 'blacklist nameofmodule' into a file inside/etc/modprobe.d and that will prevent the module from being loaded at boot.
Try archive.debian.org and snapshot.debian.net. The first archives old Debian releases, the second attempts to archive every version of every package ever uploaded. Its history probably does not go back that far, however!
It can't hurt to remove third-party packages before upgrading. You can always install them again after the upgrade. If you have a recent version of aptitude installed, you can run aptitude search '~S~i!~Odebian' to find out which these packages are. If you have the version that shipped with sarge, then comment out any third-party repositories from your sources.list, then run aptitude (which will get you to the interactive, text-mode user interface), and scroll down to 'obsolete & locally created packages', where they should all be listed.
If you don't want to remove most of the packages, you should get by OK as long as you do remove any that ship any files in/usr/X11R6/bin.
Of course, the ususal upgrade procedure still applies--read the release notes before upgrading, pay attention to the steps that aptitude says that it's going to take, don't hit enter blindly, etc.:)
That graph does not take into account the version-tracking info associated with each bug. Try http://people.debian.org/~sesse/bugscan/ instead. From that graph, you can see that etch has been less buggy than sarge for almost a month.:)
These pages will probably continue to be useful once Etch's default kernel gets out of date; although they may not be necessary as I have heard rumours of plans to push out updated Linux kernel image packages from time to time, with point releases of Debian 4.0 (etch).
The bugs tagged with 'security' are probably not important enough to delay the release. They can be fixed at any time with an update from the security team. That leaves five bugs, none of which seem so important that they can't be fixed for 4.0r1.
You hit it right on the head. Did you know that such a tagging system already exists? It's called PICS. It's a great idea. And it's being totally ignored by the morons who come up with these laws that seek to destroy what they cannot understand.
You talk as if the economy and politics have nothing to do with each other, but that is not true. We are mired in economic sclerosis because no European company is free from the greedy, interfering tendrils of the organs (can I say organs on this web site?) of the European Union. Imagine a picture of prehistoric creatures trapped in a tar pit, slowly but inexorably sinking until they suffocate, only the creatures are businesses and the tar is miles and miles and miles of red tape.
The A380 is probably going to be a financial disaster. The number of planes that Airbus needs to sell to break even just keeps going up and up--I believe it is now around 420. When UPS cancelled their order of the freighter model, the total number of orders for the A380 freight dropped to zero, meaning that more passenger models must be sold to recoup the loss... but that isn't going to happen for at least another year, meanwhile the passenger airlines need to increase their capacity now and so they making up the gap with other aircraft...
When countries get together to co-operate on prestige economic projects, take cover. Concorde and the Channel Tunnel spring to mind, both excellent pieces of hardware, but financially unsuccessful. The A380 superjumbo is the latest example. Now that UPS has cancelled its order for the freight version, the A380 has no orders at all. Damian Reece in the Telegraph says that if Airbus had been a real company it would have acted earlier to put right the accelerating problems.
Then again, Airbus would never have built the A380 superjumbo in the first place if it had been a market venture, rather than the instrument of a European political elite with great power illusions.
...
Now the arguments rage over restructuring, with politicians circling like jackals with what Reece calls "a mix of toxic national jealousies and bureaucratic paralysis." The prospects seem bleak. The plane will lose billions, and taxpayers will bale out its parent company. I see no prospect at all for improving it; it's structure puts it in the political domain, not the commercial one, and I don't think anything can save it.
Ah, so it's you I have to blame for this mess. Please write out the following one hundred times:
The DNS does not categorise content. The DNS does not categorise content. The DNS does not categorise content.
If you are at all familiar with computer science then you will perhaps recognise the term "layering violation".
If you want to impose content filtering on everyone then you should push for laws requiring that all pornographic, violent, obscene, etc. content be classified with a labelling system such as PICS. Instead of misusing the DNS as a totally subjective and far too-coarse grained catagorisation system, you should consult those who actually thought about this problem logically and came up with PICS.
With PICS, instead of a subjective and fundamentally inaccurate 'porn/not porn' label, you rate HTTP resources based on their actual content. For further information, consult its website and the excellent RFC 3675 entitled.sex considered harmful.
Your interrogators will just keep pushing you, and you can give them as many passwords as you want, even as many as you can remember or as exist, and they will keep on torturing you until you die.
I'm sure someone here could whip that up in Perl/Tk for loop-aes in an hour or two. I'm no programmer, so I won't bother...
Nooo, that would not be very safe. If you are typing your passphrase into an X11 session then there is nothing to stop another X client from stealing it.;)
1) The industry benefits, because the patent is (theoretically) detailed and recorded, meaning that the knowledge will not be lost, and that knowledge will eventually become public domain.
As you say, theoretically. In practice, software patents are useless for this; they are virtually just checklists that lawyers can use to determine whether they can sue someone.
3) Licensees benefit, because they can develop new inventions that improve upon or use or otherwise rely upon the patented device.
That assumes that the software was only developed because it was possible to patent it!
Only SNTP I'm afraid, which is much less accurate. Accoring to wikipedia, Windows 2003 SP1 finally implements NTP, eleven years after the NTPv3 RFC was published.
Slashdot Mirror
Sounds like it is your hardware that is at fault. If you disable the onboard sound card in the BIOS then it shouldn't be visible to the operating system in the first place, or so it is with the hardware that I have used.
/etc/modprobe.d and that will prevent the module from being loaded at boot.
You can always put 'blacklist nameofmodule' into a file inside
I'll use Solaris once they turn it into a port of Debian.
Try archive.debian.org and snapshot.debian.net. The first archives old Debian releases, the second attempts to archive every version of every package ever uploaded. Its history probably does not go back that far, however!
It installs XFCE instead of GNOME by default.
It can't hurt to remove third-party packages before upgrading. You can always install them again after the upgrade. If you have a recent version of aptitude installed, you can run aptitude search '~S~i!~Odebian' to find out which these packages are. If you have the version that shipped with sarge, then comment out any third-party repositories from your sources.list, then run aptitude (which will get you to the interactive, text-mode user interface), and scroll down to 'obsolete & locally created packages', where they should all be listed.
/usr/X11R6/bin.
:)
If you don't want to remove most of the packages, you should get by OK as long as you do remove any that ship any files in
Of course, the ususal upgrade procedure still applies--read the release notes before upgrading, pay attention to the steps that aptitude says that it's going to take, don't hit enter blindly, etc.
That graph does not take into account the version-tracking info associated with each bug. Try http://people.debian.org/~sesse/bugscan/ instead. From that graph, you can see that etch has been less buggy than sarge for almost a month. :)
FYI, if Grub guesses the correspondance between the order of drives-seen-by-Linux and drives-seen-by-BIOS incorrectly, you can correct it by editing /boot/grub/device.map. See http://www.gnu.org/software/grub/manual/html_node/ Device-map.html for more info.
:(
I have abandoned any hope that we will ever see PCs migrate off the shitty 20-year old architecture that makes this timewasting crap necessary.
Left the upgrade from woody a little late don't you think? ;)
FYI, you could always have used etch's kernel 'backported' to sarge if you went to http://backports.org/. Another option is Kenshi Muto's Backported d-i images archive page.
These pages will probably continue to be useful once Etch's default kernel gets out of date; although they may not be necessary as I have heard rumours of plans to push out updated Linux kernel image packages from time to time, with point releases of Debian 4.0 (etch).
The bugs tagged with 'security' are probably not important enough to delay the release. They can be fixed at any time with an update from the security team. That leaves five bugs, none of which seem so important that they can't be fixed for 4.0r1.
Do you feel the same way about doves?
PS, I suggest you buy a fucking dictionary!
If only the music was available over the web, instead of via the propretary iTunes program. Oh well.
O RLY?
You hit it right on the head. Did you know that such a tagging system already exists? It's called PICS. It's a great idea. And it's being totally ignored by the morons who come up with these laws that seek to destroy what they cannot understand.
The A380 is probably going to be a financial disaster. The number of planes that Airbus needs to sell to break even just keeps going up and up--I believe it is now around 420. When UPS cancelled their order of the freighter model, the total number of orders for the A380 freight dropped to zero, meaning that more passenger models must be sold to recoup the loss... but that isn't going to happen for at least another year, meanwhile the passenger airlines need to increase their capacity now and so they making up the gap with other aircraft...
The Adam Smith institute said it best:
Ah, so it's you I have to blame for this mess. Please write out the following one hundred times:
.sex considered harmful.
The DNS does not categorise content. The DNS does not categorise content. The DNS does not categorise content.
If you are at all familiar with computer science then you will perhaps recognise the term "layering violation".
If you want to impose content filtering on everyone then you should push for laws requiring that all pornographic, violent, obscene, etc. content be classified with a labelling system such as PICS. Instead of misusing the DNS as a totally subjective and far too-coarse grained catagorisation system, you should consult those who actually thought about this problem logically and came up with PICS.
With PICS, instead of a subjective and fundamentally inaccurate 'porn/not porn' label, you rate HTTP resources based on their actual content. For further information, consult its website and the excellent RFC 3675 entitled
Is it not possible that when IBM talks of "THE SYSTEM V WORKS", they are talking about the specific works that SCO allege that Linux infringes upon?
I'm not sure the case will ever come to a Halt.
Your interrogators will just keep pushing you, and you can give them as many passwords as you want, even as many as you can remember or as exist, and they will keep on torturing you until you die.
Sound Blaster Live 5.1 value. Has hardware mixing, so multiple programs can play sounds at once.
apache: 1.3.33-6sarge3
apache2: 2.0.54-5sarge1
You lose the rest of the encrypted block, not the whole drive (I think).
Only SNTP I'm afraid, which is much less accurate. Accoring to wikipedia, Windows 2003 SP1 finally implements NTP, eleven years after the NTPv3 RFC was published.