Just to get my 2 cents in, I agree with those who actually like the look of the forum. Maybe it's cause I only access it from a desktop but to me this is much cleaner than Facebook. Last time I logged into Facebook there were so many sections of the screen competing for attention, each using a different widget style. It was really off-putting. I know forums can be a lot of upkeep so if the new software makes it easier I completely understand.
Count me as one of those who would move to the new site if you decide to go that direction. I'd prefer if the accounts are independent and not tied to a service such as G+ since I don't have one of those.
If I was setting up a server right now, I'd go with Ubuntu 12.04 LTS. Debian 6 is really old. It's also about to be replaced in the next few months. So that means Debian 6 will stop being supported in 18 months or so (if I recall correctly), while 12.04 is supported for 4 more years. In general, if you want a server install to last a long time, Ubuntu LTS is going to be a better choice - Debian's support life is usually around 3 years, Ubuntu LTS is 5. The only practical difference between the two is the init system. Upstart is pretty annoying to manage on the server (I'd rather have SysV), but it's rare that you'll need to deal with it.
That's a good argument for Ubuntu over Debian. It's a shame because Debian arguably works harder then anyone to qualify packages for their "stable" releases but it seems all that goes to waste if they spend more time moving a package from unstable to stable then they do supporting it afterwards. One thing I can say in response is that it's very easy to upgrade in place from one release to another. I've gone through several releases on one box without having to re-install with very few issues. Ubuntu might work just as well for this, I'm not sure. Ubuntu has a special "do-release-upgrade" command. For some reason Debian doesn't need that; you can just use aptitude.
Getting help might be a factor. Ubuntu users are always wandering into #debian asking for support. Is something wrong with the Ubuntu channel? Also, getting answers about anything other than basis desktop usage from ubuntuforums.org is an exercise in frustration. I suppose you could always try the Mint forums.
Having argued for both of those, if you're not using Gentoo and customizing your cflags, you're really just wasting your hardware. Don't forget to include --omg-optimized.
If you need to do most things through a terminal interface then Debian has more documentation and community howtos. If you need newer software you can always run testing, unstable or use backports. Also, Ubuntu tends to introduce experimental features to support the desktop at the expense of common server setups such as using upstart to control the boot sequence which no other distro supports and breaks some nfs configs.
I don't think they're necessarily any tamer today. As mentioned there's the patent lawsuits. There's Secure Boot which gives Microsoft a lot more control over the market in the guise of security. On show 305 it was mentioned that Microsoft requires the ability to turn off secure boot. This is only partially true. It's true for the x68 based hardware. On the contrary, Microsoft specifically requires that manufacturers not allow secure boot to be bypassed on the ARM platform, which is powering more and more devices these days.
I use it since it's part of Gnome. For a long time I had a poor opinion of it until I stumbled upon this issue:
The other thing I did was to finally create an asound.conf file which is recommend in a lot of Pulseaudio tutorials. This is an Alsa config file and Alsa says it's not needed but when they say that they're assuming you're using Alsa by itself. I think its purpose is for programs that try to use Alsa directly; it redirects the sound through Pulseaudio. It didn't make sense to me that I should have to create this asound.conf file to make things work. I thought the package install script should take care of this. I'm sure there's some reason they choose to leave this for the user to do.
Since making both of these changes, Pulseaudio has worked flawlessly and I'm very happy with it. The problems I was having with it were really distribution issues and not the fault of Pulseaudio itself.
Well, if we're interested in saving lives it's valid. If we're only interested in saving lives by lowering death rates due to items generally used for self-defence then no, it's not valid.
I guess my point is that most political arguments have more holes than a PGA championship. It's a pointless exercise as no one's going convince each other of anything.
One of my favorite bloggers, Bruce Schneier, like to point out how people tend to over-emphasize rare risks (mass murders) and ignore common ones (slips and falls). I certainly don't mean to speak for Mr. Schneier, he may be very well in favor of stricter gun laws. Even within the mass murder category, quickly glancing at this page http://en.wikipedia.org/wiki/List_of_rampage_killers seems to show the death rate for single incidents involving arson is much higher than ones involving guns.
Your gun figures did surprise me, especially the suicide one, though my intuition tells me those people would have just found another way to commit suicide. My gun figure was taken from an article talking about what the media here calls assault rifles. Those are military style rifles that have been converted to single-fire in order to be legally sold. Those get the most attention from the press here. This emphasizes my point though, why is our press so focused on military style rifles when it's obviously handguns which are usually involved?
No matter what the argument, I'm sure a statistic could be constructed to counter that argument. It's not that one party is lying, but before you can use statistics you've got to choose a metric, and that choice is always going to be subjective.
I love the fact that the US citizen's right to own a car is more important that the child's right not to be killed by one.
50,000 deaths a year by autos vs 500 with guns.
Bit of a no-brainer there.
Fixed that for ya.
Seriously though, this is Linux OUTLAWS. Quit complaining or Fab will fly over there, buy a gun, and put you dogs down.
Fab, are you sure that article you linked to is for the same vulnerability? It seems to be a separate one for the Windows 8 ARM platform and it doesn't mention UEFI.
Bypass code signing by overwriting the boot-loader? How can that work? Isn't the whole point of secure boot that only one matching binary string is allowed to be copied into memory and executed? Maybe they're overwriting one of the later boot stages that for some reason doesn't get verified? That would be pretty stupid of them.
In the end all they did was give rootkit writers more low level resources to work with to write even more sophisticated rootkits. Now all the malware can nicely fit in the BIOS so don't bother erasing your hard drive to try to clean your machine. Oh, and don't forget the increased manufacturing cost and failure potential due to added complexity. Increased system resource usage and backward compatibility loss. But seriously the BIOS mouse thingy is cool.
I don't know of any text editors that support colors, unless you count syntax highlighting
I was going to suggest Edubuntu. That's what a local company here uses to refurbish used PCs and send them to poor kids. Not sure what program they recommend for writing. Why not just get 'em started on vi? Not using it now is only going to make the inevitable switch more difficult.
I never understood how a government operated court system, when one of the two opposing parties is also the government, can possibly be fair. It seems like an inescapable conflict of interest for any judge. A jury partially mitigates this but jurors aren't usually well aware of their rights and so can be easily influenced by a judge's instructions.
I agree with Chaplain and NYbill. It's so disappointing that the mobile OS ports of programs which GNU/Linux desktop users are familiar with are largely paid apps or spyware.
Aren't most open source GUI apps mostly a front end to existing command line utilities? XMMS for example. Shouldn't the Unix philosophy be working for us here?
The biggest problem for Linux phones is the hardware. Most phones need so many binary blobs that Android being open source is basically worthless. I'm interested in how Ubuntu plans to solve this problem.
I predict we'll eventually see commodity hardware with phones. PCs hardware was proprietary for a while before settling with the IBM design.
I can't wait to see the equivlent of jailbreakme.com. Imagine, people would go to unuefime.com with their new Windows 8 computer and click a button which automatically downloads an exploit, cracks UEFI and installs GRUB. Version 2 of the site will have sevaral buttons to automatically download and install your distro of choice. Version 3 gathers information from your Windows system and automatically sends refund requests for your copy of Windows to the hardware vendor and Microsoft.
I actually like the efficiency of the highlight-then-middle-click for copy and paste.
I think X is more Unix-like. It delegates all the look-and-feel aspects to the window manager. It's highly portable, running on all versions of Unix (it even runs on Windows) whereas Wayland will be Linux-only. Wayland itself might be simpler in design but it's pushing a lot of stuff into the kernel so the overall system won't adhere to the Unix philosophy.
This article has some interesting comments. It agree with those that think the network transparency is a cool feature and don't want to loose it. I have an old Pentium III with a bare bones install of Linux. It's setup so that when you start X, it connects over ssh to a newer Core2 computer and runs the whole xfce desktop from the newer computer. It's quite fast and it barely seems to increase the amount of ram used on the Core2 machine.
Ideally Wayland and X could be maintained in parallel. Having many choices for each part of the OS is one of the best features of free software. My only concern is that manufacturers releasing binary-only drivers will choose one or the other. For now, NVIDA says they have no plans to support Wayland.
It's not binary-less. Slackware maintains a small sized repository of binary packages but there's a few community sites with more. I just preferred getting the packages straight from the project websites, including the kernel. I think it was just a more common thing to do back then. Modern kernels support nearly everything by default but I recall having to build my own to add support for "new" features such as USB I had a copy of "Running Linux" so of course all the instructions tried to be distro-agnostic. I remember one day I was trying to build Freedoom. It had so many dependencies that finally I gave up. Just for kicks I installed Debian, quickly read up on apt and tried "apt-get install freedoom". In seconds I had a working game and that was the end of Slackware for me. I continued building my own kernels for a few years even after I switched to Debian but less frequently to a point that my upstream builds were becoming older than the packaged kernels and with the drivers I needed becoming available as loadable modules I switched to the distro kernels.
With Gentoo (and FreeBSD) you shouldn't have to know anything about a package's build system. The whole point is that the ports system is a collection of scripts that fetch the upstream files and build them automatically. Sure each package has optional build instructions but that's only half of it. You can set compiler optimizations for your specific processor that will apply to all builds. The problem is if you have a lot of large ports installed, you'll spend a lot of time recompiling whenever you upgrade and the compiler optimizations are barely noticeable, except to ricers.
Since X was introduced in 1984, wouldn't any modern phone be more powerful than what X ran on for at least its first 15 years? One of the first installs I did was on a 486. It included X and ran quite smoothly. Seems like it's more about what's running on top that makes X seem slow.
Ha, I used Slackware for years in the early 2000's. It's great that new people are rediscovering Slackware. Up to date packages, easy install. To be honest, I don't run it any more, too much work (cause of the dependances). But it's a good learning tool. The init scripts and config files are bare minimum and well documented (inside the scripts). It's a great way to "learn Linux" instead of learning a distribution. Every program I added was by downloading the upstream source and running "./config && make install". Ahh, memories...