Why does someone NEED to build that kind of rocket. If the hobbyist can do it so can a Terrorist. If we can save just one life it will have been worth it.
Terrorists only win when they manage to terrorize people. You sir are a loser.
These restrictions will save no lives. Real terrorists with real funding will still have the freedom to carry out attacks while real people lose their freedom. A terrorist pulls an attack then you find him and buddies and hand out some hurt. The terrorists' paymasters and masterminds use young indoctrinated hotheads as their tools and mostly don't want to die themselves. See to it they die. This is how you fight terrorists. Taking freedoms away from people who aren't terrorists doesn't do a damn thing. Terrorists will just find another unplugged hole and put on another show. How we react determines whether they win or we win.
Terrorists love the likes of you. You give them victory on a silver platter.
QEMU supports at least two models of emulated network card and two models of video adaptor. It is also fairly modular in the emulated hardware department so "checking for known virtualized hardware" could get really tricky in a hurry as enough hardware cases can be added to QEMU to make that an unreliable method. In the case of VMware, the emulated video adaptor is a "VMware video adaptor". THAT's going to be really hard to miss.....
But you can get a lot of the advantages that you claim for rock-solid, manufacturer determined stable libraries by simply sticking with Debian's big repository, where everything is built together. It's only when you try to bring in something from a second repository that you have to depend on standards.
But sometimes you'll want something that isn't provided by the big repository or a newer version. I have my cake and eat it too with backports. Unless a binary can run directly out of my home directory, I'll just build the software against the -dev libraries from the big repository and then use checkinstall to install that as a Debian package. If the software insists on newer versions of libraries, I build and install those in/usr/local with different names from the distro provided libraries. If the list of build deps makes it too much of PITA to build and install the software then I just give it a pass. I find that well-designed, polished, and mature source code bases aren't too picky about what they need to build against. A list of bleeding edge deps as long as your arm is good sign to stay away for a release or three.
In no case do I let third party repositories overwrite core pieces of my system like libc, X.Org or even libSDL. 95% of the time I can just build against the repository provided libraries and not worry about deps getting out of phase; or just run a binary package out of my home directory. Maybe once a year, I'll have a differently named newer version of a library in/usr/local; most things I want to try out just aren't interesting enough to take that kind of trouble. Any more, I pretty much expect./configure;make;checkinstall to go just as easily as installing a package on Windows. I'm just not interested in futzing around with things that are hard to build. Anyway I still run new games from Happypenguin and nifty utilities from Freshmeat without affecting my ability to stay synced up with the Ubuntu repositories.
The moral of this big story is that with a little care you can have the stability of a big repository and the novelty of exciting new software.
Linux will always be catching up trying to hack togheter hardware drivers until they agree to play nicely with the hardware providrers.
The problem is that "play nicely with the hardware providers" is a synonym for "never make major improvements to the kernel again because you'll break a 5 year old driver."
I find the primary advice of the site editors to be pretty good: Concentrate on moderating good posts up rather than bad ones down. Short of things like speculating about Cmdr. Taco's mating practices, I don't mod posts down. Your screeds may not be getting my nod but I'm not one of the ones knocking you down to oblivion.
I cannot approve of this attraction cause getting disemboweled always makes me kinda mad A huge tyrannosaurus ate our lawyer Well, I suppose that proves... they're really not all bad
These days it is a groupware suite. Email, calendaring, conferencing and so-forth. It is a quite spiffy alternative to Outlook and Notes. Servers and clients are available for Linux, OS X, and Windows.
If it ever had that "BBS Feel", it hasn't since at least FirstClass 4 (up to 8.x now). It seems to be the most popular in education markets.
Rolling back isn't always an option when there are SECURITY FIXES in between. Between 2.6.16 and 2.6.18 there are a few exploits/DoS.
I don't know about Gentoo but other distros backport those security fixes and otherwise disturb as little as possible. Debian and Ubuntu have both been good in this regard.
Does Gentoo truly mandate full kernel version upgrades to get security/bugfixes? I'm not being snarky. I understand they have a "stable" branch as well. I'd think similar practices at least go on there.
And I wouldn't mind if you detailed the update process for Ubuntu... I've been spoiled by that "emerge -uDv world", I suppose;o)
#apt-get update
#apt-get dist-upgrade
The first command updates the database of available packages and their versions.
The second downloads and installs anything that is newer than what you already have.
If I want something a bit more bleeding edge than usual but don't want to risk a wholesale upgrade, I'll add "deb-src" lines from the development distro and "apt-get source packagename" then build the package from source against my otherwise default environment. If it's just a game or something trivial there really isn't much risk. Backporting something like glibc I just won't do. Anymore I just want to use the damn thing and I'm no longer willing to hose large tracts of my system to play a silly little game that just got released yesterday.
And besides, bitching is how things get done in this world.
For the most part, that certainly isn't true in the FOSS word. It is most especially true of the developers who are only doing it because they want to. If I'm a developer with limited time and I get three pleasant requests and a self-entitled bitchy one then guess which one is going straight to/dev/null?
One: You indicated that you had the needed functionality on 2.6.16. Roll back to it fer crying out loud. While we're on the subject, you don't have to upgrade to the latest kernel just because.
Two: You didn't pay anything for Gentoo. See my first paragraph. In the FOSS world bitching that is heeded is something you pay for in either professional grade bug reports, patches, or money. You want someone to be obligated to hear yer bitchin'? Pay for a RHEL or SuSE license.
Puppy Linux is explictly designed for the type of older smaller system you are talking about. Everything from the Kernel to Desktop to every last app has been selected and compiled with smaller, older systems in mind. It runs acceptably on 64 MB systems and the base load can execute entirely from memory on a 128 MB system if run from the LiveCD. The LiveCD has a harddrive installer. If it boots and everything works, just let it have the harddrive.
I run and love Ubuntu but I wouldn't use it on anything more than four years old. It is simply designed with recent hardware in mind.
You have to install new kernels for the same reasons that you have to buy new versions of windows. (You're not still running Windows 3.1, are you?) You get new drivers, methods, and all those fun things you expect from your operating system. I can write you scripts to mostly automate the process of building new kernels, which should take 94% of the pain out of the process, but it will involve answering stupid questions about new drivers. It doesn't know. Hotplugging is our weakness right now.
I haven't built a kernel from source in almost three years. Most desktop oriented distros provide "kernel header packages" which are basically #include files that match your running kernel. From time to time, I have built third party drivers from source. If a third party driver will build against the "kernel headers", you can build and install it without rebooting; most times it is just the "./configure, make, checkinstall" routine. I used to regularly build the nVidia drivers this way but Ubuntu is good about providing "restricted driver" packages that match their supplied end-user kernels (which are pretty much built in "kitchen sink mode" so you don't have to rebuild to get some obscure option). But even if they didn't, automating nVidia driver build-and-install wouldn't be too hard.
VMware Player is another third party item that works just fine with kernel-header packages. Come to think of it, the only thing I've seen lately that won't build without patching kernel source and forcing a kernel rebuild on you are new versions of the sky2 driver. Even there I managed to get things working without resorting to a full kernel rebuild.
Rebuilding kernels is something I used to futz with a lot. It just isn't as necessary these days, especially if your distro pays good attention to end-user issues.
Slashdot Mirror
That's OK. The crowd in the White House and Congress isn't conservative either......
Just paint the copper cylinder pink and turn on a cheap and simple Somebody Else's Problem Field.......
Grandmother will click the update button in Synaptic when the distros include it. Grandmother won't be running a beta.
Were you born a snarky bastard or did you have to work at it?
Are a few extra immigrants really somethign to get worked up over?
Google la reconquista.If you get the result you want with a minimum of effort then why be snarky about the toolchain?
It is kinda hard to see parody when craven little soccer mommies actually talk that way.......
those icky crayfish-like ear thingies from "Star Trek: The Wrath of Khan,"
So that's how Apple maintains their market share!Why does someone NEED to build that kind of rocket. If the hobbyist can do it so can a Terrorist. If we can save just one life it will have been worth it.
Terrorists only win when they manage to terrorize people. You sir are a loser.
These restrictions will save no lives. Real terrorists with real funding will still have the freedom to carry out attacks while real people lose their freedom. A terrorist pulls an attack then you find him and buddies and hand out some hurt. The terrorists' paymasters and masterminds use young indoctrinated hotheads as their tools and mostly don't want to die themselves. See to it they die. This is how you fight terrorists. Taking freedoms away from people who aren't terrorists doesn't do a damn thing. Terrorists will just find another unplugged hole and put on another show. How we react determines whether they win or we win.
Terrorists love the likes of you. You give them victory on a silver platter.
QEMU supports at least two models of emulated network card and two models of video adaptor. It is also fairly modular in the emulated hardware department so "checking for known virtualized hardware" could get really tricky in a hurry as enough hardware cases can be added to QEMU to make that an unreliable method. In the case of VMware, the emulated video adaptor is a "VMware video adaptor". THAT's going to be really hard to miss.....
"We are going to lower you into this vat of Royal Slurm and in a few minutes it will transform you into a Slurm Queen like me."
"But your Highness, she is a commoner and her Slurm will taste awful."
"Yes! We will market it as New Slurm and when everybody hates it, we'll re-introduce the old Slurm as Slurm Classic. We'll make billions!"
If it worked for Coke and Slurm then it oughta work for Vista........
But you can get a lot of the advantages that you claim for rock-solid, manufacturer determined stable libraries by simply sticking with Debian's big repository, where everything is built together. It's only when you try to bring in something from a second repository that you have to depend on standards.
But sometimes you'll want something that isn't provided by the big repository or a newer version. I have my cake and eat it too with backports. Unless a binary can run directly out of my home directory, I'll just build the software against the -dev libraries from the big repository and then use checkinstall to install that as a Debian package. If the software insists on newer versions of libraries, I build and install those in
In no case do I let third party repositories overwrite core pieces of my system like libc, X.Org or even libSDL. 95% of the time I can just build against the repository provided libraries and not worry about deps getting out of phase; or just run a binary package out of my home directory. Maybe once a year, I'll have a differently named newer version of a library in
The moral of this big story is that with a little care you can have the stability of a big repository and the novelty of exciting new software.
"The intelligence of a mob is the intelligence of the stupidest member divided by the number of people in the mob."
Linux will always be catching up trying to hack togheter hardware drivers until they agree to play nicely with the hardware providrers.
The problem is that "play nicely with the hardware providers" is a synonym for "never make major improvements to the kernel again because you'll break a 5 year old driver."
I find the primary advice of the site editors to be pretty good: Concentrate on moderating good posts up rather than bad ones down. Short of things like speculating about Cmdr. Taco's mating practices, I don't mod posts down. Your screeds may not be getting my nod but I'm not one of the ones knocking you down to oblivion.
The parent poster probably means Mary Ann from Gilligan's Island.
http://www.imdb.com/title/tt0057751/
http://www.imdb.com/name/nm0920171/
She was supposed to be the Midwestern "Girl Next Door". Nothing doing. She was hot.
That's funny but it is generally agreed that Spock is the pitcher and Kirk is the catcher. After all, Spock is MUCH stronger than a human.
I cannot approve of this attraction
cause getting disemboweled always makes me kinda mad
A huge tyrannosaurus ate our lawyer
Well, I suppose that proves... they're really not all bad
- "Weird Al" Yankovic
Jurassic Park
Intercontinental Ballmer Missiles (ICBM) incoming!
I didn't know that he could throw that far or that Aerons were viable WMDs.
It is still around:
www.firstclass.com
These days it is a groupware suite. Email, calendaring, conferencing and so-forth. It is a quite spiffy alternative to Outlook and Notes. Servers and clients are available for Linux, OS X, and Windows.
If it ever had that "BBS Feel", it hasn't since at least FirstClass 4 (up to 8.x now). It seems to be the most popular in education markets.
Manhold?
Have you never actually been to school?
Maybe it was one of those British boarding schools. You know what they say....
Rolling back isn't always an option when there are SECURITY FIXES in between. Between 2.6.16 and 2.6.18 there are a few exploits/DoS.
I don't know about Gentoo but other distros backport those security fixes and otherwise disturb as little as possible. Debian and Ubuntu have both been good in this regard.
Does Gentoo truly mandate full kernel version upgrades to get security/bugfixes? I'm not being snarky. I understand they have a "stable" branch as well. I'd think similar practices at least go on there.
And I wouldn't mind if you detailed the update process for Ubuntu... I've been spoiled by that "emerge -uDv world", I suppose ;o)
#apt-get update
#apt-get dist-upgrade
The first command updates the database of available packages and their versions. The second downloads and installs anything that is newer than what you already have.
If I want something a bit more bleeding edge than usual but don't want to risk a wholesale upgrade, I'll add "deb-src" lines from the development distro and "apt-get source packagename" then build the package from source against my otherwise default environment. If it's just a game or something trivial there really isn't much risk. Backporting something like glibc I just won't do. Anymore I just want to use the damn thing and I'm no longer willing to hose large tracts of my system to play a silly little game that just got released yesterday.
And besides, bitching is how things get done in this world.
For the most part, that certainly isn't true in the FOSS word. It is most especially true of the developers who are only doing it because they want to. If I'm a developer with limited time and I get three pleasant requests and a self-entitled bitchy one then guess which one is going straight to /dev/null?
One: You indicated that you had the needed functionality on 2.6.16. Roll back to it fer crying out loud. While we're on the subject, you don't have to upgrade to the latest kernel just because.
Two: You didn't pay anything for Gentoo. See my first paragraph. In the FOSS world bitching that is heeded is something you pay for in either professional grade bug reports, patches, or money. You want someone to be obligated to hear yer bitchin'? Pay for a RHEL or SuSE license.
Puppy Linux is explictly designed for the type of older smaller system you are talking about. Everything from the Kernel to Desktop to every last app has been selected and compiled with smaller, older systems in mind. It runs acceptably on 64 MB systems and the base load can execute entirely from memory on a 128 MB system if run from the LiveCD. The LiveCD has a harddrive installer. If it boots and everything works, just let it have the harddrive.
I run and love Ubuntu but I wouldn't use it on anything more than four years old. It is simply designed with recent hardware in mind.
You have to install new kernels for the same reasons that you have to buy new versions of windows. (You're not still running Windows 3.1, are you?) You get new drivers, methods, and all those fun things you expect from your operating system. I can write you scripts to mostly automate the process of building new kernels, which should take 94% of the pain out of the process, but it will involve answering stupid questions about new drivers. It doesn't know. Hotplugging is our weakness right now.
I haven't built a kernel from source in almost three years. Most desktop oriented distros provide "kernel header packages" which are basically #include files that match your running kernel. From time to time, I have built third party drivers from source. If a third party driver will build against the "kernel headers", you can build and install it without rebooting; most times it is just the "./configure, make, checkinstall" routine. I used to regularly build the nVidia drivers this way but Ubuntu is good about providing "restricted driver" packages that match their supplied end-user kernels (which are pretty much built in "kitchen sink mode" so you don't have to rebuild to get some obscure option). But even if they didn't, automating nVidia driver build-and-install wouldn't be too hard.
VMware Player is another third party item that works just fine with kernel-header packages. Come to think of it, the only thing I've seen lately that won't build without patching kernel source and forcing a kernel rebuild on you are new versions of the sky2 driver. Even there I managed to get things working without resorting to a full kernel rebuild.
Rebuilding kernels is something I used to futz with a lot. It just isn't as necessary these days, especially if your distro pays good attention to end-user issues.